[Noisebridge-discuss] linux-y question. Also info on Android Tablets hooking up to FTDI devices.

[Taylor Alexander]

Oh neat! I had no idea. I already soldered up a USB cable by hand so I can
easily hit those pins. I'll see if my device has /dev/ttySAC2. I left it at
home today though. :-/

Unfortunately that's only a partial solution. Our plan was to use a USB hub
to connect both an FTDI and a flash drive (the tab works just fine with a
hub).

With the above trick, the Accessory ID line gets a 150k resistor across it,
but it needs 20k to go into USB mode, so they can't both be used at once it
would seem.

I'll try it though. The guy seemed to be unclear on if the 150k resistor was
necessary. With any luck USB and serial can be used simultaneously.

Thanks.

-Taylor

On Tue, Aug 30, 2011 at 11:56 AM, David Rorex <drorex at gmail.com> wrote:

> You might also investigate existing serial ports on the device, I have no
> experience with the galaxy tab, but a quick google came up with this page
> saying there's already a serial port, and you just need some tricky
> soldering skills to access it:
> http://forum.xda-developers.com/showthread.php?t=1010314
>
> This way you wouldn't need to worry about any extra drivers, according to
> the post it shows up as /dev/ttySAC2
>
> On Sat, Aug 27, 2011 at 3:38 PM, Taylor Alexander <tlalexander at gmail.com>wrote:
>
>> Hey,
>> Yeah I've used Bluetooth before but this will be all integrated into a
>> special case on the tablet (the FTDI is actually for hooking up an Xbee
>> module, as all we're trying to do is use the tablet to talk to some remote
>> Xbee sensors).
>>
>> We will use Bluetooth if we have to, but apparently the tablet supports
>> FTDI devices somewhat readily (with the instructions given on that site),
>> I'm just missing... something. So I'd like to get that working if possible.
>>
>> Additionally, this is a custom product that will be sold with the tablet,
>> so other device support isn't a concern.
>>
>> Really it's just that hosting is the right solution, and I had a tutorial,
>> so not doing it would be annoying.
>> On Aug 27, 2011 3:30 PM, "Jake" <jake at spaz.org> wrote:
>> > Is there a particular reason why it has to be wired to an FTDI device? I
>>
>> > assume you're looking for serial communications, and apparently it's a
>> lot
>> > easier to deal with bluetooth serial interfaces from android than trying
>>
>> > to recognize a hardware USB serial port plugged into the phone.
>> >
>> > bluetooth serial modules are only $5 !!!! Robby has been using one in
>> his
>> > phone-controlled RC car, and i'm using one on a radiation detector. You
>> > just solder up a couple resistors and an LED to it, and give it 3.3
>> volts.
>> >
>> > Another nice thing is that you can do this even with phones that are not
>>
>> > rooted or jailbroken, and have no actual USB host capabilities, like the
>>
>> > G1 (which are available very cheaply these days)
>> >
>> > -jake
>> >
>> > Taylor said:
>> >
>> > I saw the other thread about serial ports and linux and realized I
>> should
>> > ask my question here too (I am under the impression this is an
>> appropriate
>> > use of the mailing list?)
>> >
>> > I have been messing with getting my Samsung Galaxy Tab 10.1 Android
>> > Honeycomb tablet to talk to FTDI devices. It is apparently capable but
>> > requires compiling and loading some kernel modules.
>> >
>> > I followed a tutorial on building the kernel modules, got them loaded
>> up,
>> > and lsmod shows the module is running, but I still get "unknown USB
>> > device"
>> > when I plug it in, I don't get a ttyUSB0 device, and dmesg shows the
>> > correct
>> > VID and PID but claims it is not supported.
>> >
>> > The tutorial I followed is above my comments here:
>> > http://android.serverbox.ch/?p=285&cpage=1#comment-468
>> >
>> > And I started a thread on XDA but haven't gotten any responses yet.
>> >
>> > Since we all might be interested in Android devices hosting FTDI
>> devices,
>> > and clearly someone here knows about linux and serial a bit, I thought
>> I'd
>> > ask here as well.
>> >
>> > Really my biggest questions are:
>> > Would the module even load if I compiled it incorrectly?
>> > And if it would not load unless it was correct, and I did compile and
>> load
>> > it correctly, then what else could be wrong?
>> >
>> > Thanks.
>> > -Taylor
>> >
>>
>> _______________________________________________
>> Noisebridge-discuss mailing list
>> Noisebridge-discuss at lists.noisebridge.net
>> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20110830/3a8fc35b/attachment-0003.html>