From: michaelamgelo <mic...@gm...> - 2011-04-30 19:00:08
|
I am new to Gumstix. I got a Overo Fire and Palo43 recently. I tried to connect to the FTDI on the Palo43 to my laptop running Ubuntu 10.04. I got a green LED (for console) on the board, but the FTDI is not detected when I check with lsusb. I try this with or without the uSD card in which I put the pre-built desktop image. On the host machine, I have modprobe the usbserial and ftdi_sio. Is the FTDI chip broken? Or, am I doing something wrong? Thanks. -- View this message in context: http://old.nabble.com/Palo43-FTDI-not-detected-on-Ubuntu-10.04-tp31511002p31511002.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Bob C. <bco...@ve...> - 2011-04-30 20:35:21
|
On your Ubuntu system, are you a member of these groups: dialout uucp You need to be a member of at least the above groups. On a Fedora 14 box you need to be a member of wheel as well. But I believe Ubuntu works differently. Bob Cochran On 04/30/2011 03:00 PM, michaelamgelo wrote: > I am new to Gumstix. I got a Overo Fire and Palo43 recently. I tried to > connect to the FTDI on the Palo43 to my laptop running Ubuntu 10.04. I got a > green LED (for console) on the board, but the FTDI is not detected when I > check with lsusb. I try this with or without the uSD card in which I put the > pre-built desktop image. On the host machine, I have modprobe the usbserial > and ftdi_sio. Is the FTDI chip broken? Or, am I doing something wrong? > > Thanks. |
From: Michael L. <mic...@gm...> - 2011-05-01 03:07:37
|
Thank you Cochran for your reply. I was in dialout but not uucp, but that does not fix it. According to the Getting Started Guide (http://www.gumstix.org/getting-started.html), the FTDI chip should be detected even before I connect the power. I have tried different orders of connecting things but nothing worked. When I checked dmesg, no entries were made by connecting to the FTDI. I also tried using Windows XP. I expect a new device message but nothing shows up. I wonder what others would see when connecting to the FTDI console port for the first time. What are the requirements to get the FTDI detected? Thanks. |
From: Bob C. <bco...@ve...> - 2011-05-01 12:26:02
|
Hi Michael, Feel free to call me Bob. That is my first name. (smile.) Did you log out of Ubuntu and then log back in again after joining the dialout group? Group memberships are not effective till after you log in. At this point it sounds like you are only trying to verify that your FTDI chip is recognized. I would go further and try to make an actual console connection take place. Question: are you sure you snapped in the Overo board correctly on the Palo board? You should not be able to see the Hirose connectors on the Overo if it is snapped in properly. Be gentle but firm. Consider taking the Overo out of the Palo and snapping it in again. I can't remember where Ubuntu keeps it's log, it is probably in /var/log/messages. Why not tail this as root: open a terminal window tail -f /var/log/messages ...and then plug in the USB cable, at the host end, which is connected to the console connector of the Palo board. Then post the log messages that have been generated. (ctrl-c will break you out of tail's output.) The USB connection give the FTDI chip 5v of power. Anyhow, post your log output so we can see what is happening. Thanks Bob Cochran On 04/30/2011 11:07 PM, Michael Lam wrote: > Thank you Cochran for your reply. I was in dialout but not uucp, but > that does not fix it. According to the Getting Started Guide > (http://www.gumstix.org/getting-started.html), the FTDI chip should be > detected even before I connect the power. I have tried different orders > of connecting things but nothing worked. When I checked dmesg, no > entries were made by connecting to the FTDI. > > I also tried using Windows XP. I expect a new device message but nothing > shows up. > > I wonder what others would see when connecting to the FTDI console port > for the first time. What are the requirements to get the FTDI detected? > > Thanks. > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2011-05-01 19:47:46
|
Hi guys, On Sun, May 1, 2011 at 5:25 AM, Bob Cochran <bco...@ve...> wrote: > Hi Michael, > > Feel free to call me Bob. That is my first name. (smile.) > > Did you log out of Ubuntu and then log back in again after joining the > dialout group? Group memberships are not effective till after you log in. Also, use the id command to verify that you are actually a member of the dialout group. -- Dave Hylands Shuswap, BC, Canada http://www.davehylands.com |
From: Michael L. <mic...@gm...> - 2011-05-01 21:52:25
|
Hi all, > At this point it sounds like you are only trying to verify that your > FTDI chip is recognized. I would go further and try to make an actual > console connection take place. I am trying to make a connection, but ttyUSB* does not show up. So, I try to see if the FTDI is detected. > Question: are you sure you snapped in the Overo board correctly on the > Palo board? You should not be able to see the Hirose connectors on the > Overo if it is snapped in properly. Be gentle but firm. Consider taking > the Overo out of the Palo and snapping it in again. I think it is properly snapped. After connecting the power, the LEDs on the Overo Fire blinks occasionally. And, I got the "heartbeat" LED on the Palo board, too. > tail -f /var/log/messages Here's the print out of my log: May 1 14:02:38 michael-dual kernel: [ 16.826299] vga16fb: not registering due to another framebuffer present May 1 14:02:38 michael-dual kernel: [ 16.848118] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input8 May 1 14:02:38 michael-dual kernel: [ 16.884565] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input9 May 1 14:02:38 michael-dual kernel: [ 16.899571] hda_codec: ALC268: BIOS auto-probing. May 1 14:02:38 michael-dual kernel: [ 16.899936] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10 May 1 14:02:38 michael-dual kernel: [ 16.944367] Console: switching to colour frame buffer device 160x50 May 1 14:02:39 michael-dual kernel: [ 17.374138] vboxdrv: fAsync=0 offMin=0x1cc offMax=0x6b8 May 1 14:02:39 michael-dual kernel: [ 17.374652] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. May 1 14:02:39 michael-dual kernel: [ 17.651707] ppdev: user-space parallel port driver May 1 14:03:46 michael-dual kernel: [ 84.001056] CE: hpet increasing min_delta_ns to 15000 nsec No new entries were made by connecting to the console port on the Palo. I tried different USB cables that are working for other devices. I also tried removing the Overo Fire from the Palo. Then, I tried again with manually starting usbserial and ftdi_sio: May 1 14:25:06 michael-dual kernel: [ 1364.561647] usbcore: registered new interface driver usbserial May 1 14:25:06 michael-dual kernel: [ 1364.561777] USB Serial support registered for generic May 1 14:25:06 michael-dual kernel: [ 1364.562388] usbcore: registered new interface driver usbserial_generic May 1 14:25:06 michael-dual kernel: [ 1364.562394] usbserial: USB Serial Driver core May 1 14:25:21 michael-dual kernel: [ 1379.475232] USB Serial support registered for FTDI USB Serial Device May 1 14:25:21 michael-dual kernel: [ 1379.477247] usbcore: registered new interface driver ftdi_sio May 1 14:25:21 michael-dual kernel: [ 1379.477254] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver Again, no entries were made by connecting to the console port. Here's result of the id command as suggested by Dave: uid=1000(michael) gid=1000(michael) groups=4(adm),10(uucp),20(dialout),24(cdrom),46(plugdev),105(lpadmin),119(admin),122(sambashare),1000(michael) Finally, as suggested by Scott, I tried different cables, usb ports and even computers. The result is the same. No USB enumeration. Bad Palo board? Thanks, Michael |
From: Bob C. <bco...@ve...> - 2011-05-01 23:17:44
|
Hi Michael, It looks to me like you do have a bad Palo board. If you have a different expansion board like the Summit, you can test the console connection on that. Bob On 05/01/2011 05:52 PM, Michael Lam wrote: > Hi all, > >> At this point it sounds like you are only trying to verify that your >> FTDI chip is recognized. I would go further and try to make an actual >> console connection take place. > I am trying to make a connection, but ttyUSB* does not show up. So, I > try to see if the FTDI is detected. > >> Question: are you sure you snapped in the Overo board correctly on the >> Palo board? You should not be able to see the Hirose connectors on the >> Overo if it is snapped in properly. Be gentle but firm. Consider taking >> the Overo out of the Palo and snapping it in again. > I think it is properly snapped. After connecting the power, the LEDs on > the Overo Fire blinks occasionally. And, I got the "heartbeat" LED on > the Palo board, too. > > > tail -f /var/log/messages > > Here's the print out of my log: > > May 1 14:02:38 michael-dual kernel: [ 16.826299] vga16fb: not > registering due to another framebuffer present > May 1 14:02:38 michael-dual kernel: [ 16.848118] input: PS/2 Mouse as > /devices/platform/i8042/serio1/input/input8 > May 1 14:02:38 michael-dual kernel: [ 16.884565] input: AlpsPS/2 ALPS > GlidePoint as /devices/platform/i8042/serio1/input/input9 > May 1 14:02:38 michael-dual kernel: [ 16.899571] hda_codec: ALC268: > BIOS auto-probing. > May 1 14:02:38 michael-dual kernel: [ 16.899936] input: HDA Digital > PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10 > May 1 14:02:38 michael-dual kernel: [ 16.944367] Console: switching > to colour frame buffer device 160x50 > May 1 14:02:39 michael-dual kernel: [ 17.374138] vboxdrv: fAsync=0 > offMin=0x1cc offMax=0x6b8 > May 1 14:02:39 michael-dual kernel: [ 17.374652] vboxdrv: TSC mode is > 'synchronous', kernel timer mode is 'normal'. > May 1 14:02:39 michael-dual kernel: [ 17.651707] ppdev: user-space > parallel port driver > May 1 14:03:46 michael-dual kernel: [ 84.001056] CE: hpet increasing > min_delta_ns to 15000 nsec > > No new entries were made by connecting to the console port on the Palo. > I tried different USB cables that are working for other devices. I also > tried removing the Overo Fire from the Palo. > > Then, I tried again with manually starting usbserial and ftdi_sio: > > > May 1 14:25:06 michael-dual kernel: [ 1364.561647] usbcore: registered > new interface driver usbserial > May 1 14:25:06 michael-dual kernel: [ 1364.561777] USB Serial support > registered for generic > May 1 14:25:06 michael-dual kernel: [ 1364.562388] usbcore: registered > new interface driver usbserial_generic > May 1 14:25:06 michael-dual kernel: [ 1364.562394] usbserial: USB > Serial Driver core > May 1 14:25:21 michael-dual kernel: [ 1379.475232] USB Serial support > registered for FTDI USB Serial Device > May 1 14:25:21 michael-dual kernel: [ 1379.477247] usbcore: registered > new interface driver ftdi_sio > May 1 14:25:21 michael-dual kernel: [ 1379.477254] ftdi_sio: v1.5.0:USB > FTDI Serial Converters Driver > > Again, no entries were made by connecting to the console port. > > Here's result of the id command as suggested by Dave: > > uid=1000(michael) gid=1000(michael) > groups=4(adm),10(uucp),20(dialout),24(cdrom),46(plugdev),105(lpadmin),119(admin),122(sambashare),1000(michael) > > Finally, as suggested by Scott, I tried different cables, usb ports and > even computers. The result is the same. No USB enumeration. > > Bad Palo board? > > > Thanks, > Michael > > > > > > > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Michael L. <mic...@gm...> - 2011-05-02 00:28:16
|
Hi Bob, I do not have another board. I will contact Gumstix to see if I can get a replacement. Thanks, Michael On 05/01/2011 04:17 PM, Bob Cochran wrote: > Hi Michael, > > It looks to me like you do have a bad Palo board. If you have a > different expansion board like the Summit, you can test the console > connection on that. > > Bob > > > |