Olimex Support Forum

OLinuXino Android / Linux boards and System On Modules => A10s => Topic started by: sagt3k on July 24, 2013, 11:35:20 pm

Title: FTDI USB-RS232 and PROLIFIC not recognized on board micro-A10S on USB-host
Post by: sagt3k on July 24, 2013, 11:35:20 pm
Hi
I bought a board OlinuXino A10S-micro . Great board, I have already developed small software. I started with this image "A10S_debian_GPIO_LAN_USB_SDs_HDMI_LCD_I2C_100KHz_4G_release_2", I managed to install everything, mySQL, Wordpress, PHP etc.. What I can not understand is why when plugged in a USB-RS232 FTDI or PROLIFIC, they aren't seen by the operating system. These two hardware should be already present in the debian kernel on A10S?
Thanks for you precious support
Title: Re: FTDI USB-RS232 and PROLIFIC not recognized on board micro-A10S on USB-host
Post by: ctkd17 on June 08, 2014, 08:50:42 pm
HI!

I had the same problem and i can fix it.

You must create a file with this name:

android.hardware.usb.host.xml

in this file you must write this:

   <permissions>
      <feature name="android.hardware.usb.host"/>
   </permissions>

and save this file in sys/etc/permissions/

Next step is find a file in this place that his name is :
tablet_core_hardware.xml

Open this and put in permission section this line:

<feature name="android.hardware.usb.host" />

save this and restart!

I hope that i can help you and sorry for my english,

Regards,

Ctkd
Title: Re: FTDI USB-RS232 and PROLIFIC not recognized on board micro-A10S on USB-host
Post by: kbro on June 18, 2014, 05:33:48 pm
Note that /system is a read-only filesystem, so in order for the changes to persist through a reboot you need to make it writable before copying the file to /system/etc/permissions.  I usually do this by running "adb shell" to get a login session on the board and then "mount -o remount,rw /system".

If you're feeling tidy you can "mount -o remount,ro /system" when you've made the change, but if the next thing you do is "reboot" then it doesn't really matter, as it will be back to read-only after booting anyway.