Re: [beagleboard] Can't connect to USB serial port (FTDI module isn't loaded, ttyUSB device isn't created)

[Gerald Coley]

Just so you know. There is no FTDI part on the BeagleBone Black. There are no FTDI drivers to install.

If you have an USB to TTL FTDI cable plugged into a USB port and the other end plugged into the 6 pin header on the BeagleBoard Black, then that should work.

Gerald

On Mon, May 13, 2013 at 3:25 PM, Mike Mogenson <michael....@gmail.com> wrote:

I'm having trouble connecting to the USB serial terminal of my new BeagleBone Black with the stock version of Angstrom that shipped on the board.  I'm running a virtual machine of Ubuntu 12.04 LTS 32bit in VirtualBox on Windows 7 Pro 64 bit.  I've installed the USB 2.0 drivers from the VirtualBox extension pack, I've disabled auto-mounting USB devices in Windows 7 by entering "mountvol /N" in the command prompt, and I've attached the USB Device "Circuitco BeagleBoneBlack [0308]" to the virtual Ubuntu machine.

If I run "lsusb" in Ubuntu I see "Bus 001 Device 007: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget" however no ttyUSB devices are created so I ran the mkudevrule.sh script from /media/BEAGLEBONE/Drivers/FTDI, logged out and reinserted the BBB.  Still no ttyUSB entries in /dev.  I noticed that the mkudevrule script is for a USB vendor id of 0403 and product id of a6d0 but the BBB entry in lsusb has a vendor id of 1d6b and a product id of 0104.  So I changed them in the udev rule, reloaded the udev rules, logged out for good measure, and reinserted the BBB.  Still no ttyUSB entries in /dev and no ftdi_sio or usbserial module in lsmod.

I decided to do things manually.  I entered "sudo modprobe ftdi_sio vendor=0x1d6b product=0x0104".  This loaded the FTDI module but didn't create the ttyUSB entries in /dev.  I checked "cat /proc/devices | grep -i 'ttyUSB'" which gave me "188 ttyUSB".  I then checked "sudo cat /proc/tty/driver/usbserial" which gave me "usbserialinfo:1.0 driver:2.0" but no entries for FTDI serial devices.

At this point I'm admitting I'm stuck.  Does anyone having any advice on how to access the USB serial port of the BeagleBone Black?  Is my assumption about the different USB vendor id and product id correct?  Am I (hopefully) missing something really trivial that will make this all work?

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Gerald

 

ger...@beagleboard.org

g-co...@ti.com

http://beagleboard.org/

http://circuitco.com/support/

[Mark Lazarewicz]

I know for the evm335x (Sitara) I saw a note no virtual OS drivers emulation  is too slow I was also told not to ask for help on here when building from vmware its not opensource either (-: --- On Mon, 5/13/13, Mike Mogenson <michael....@gmail.com> wrote:

[Mike Mogenson]

I understand I can use an FTDI cable on the J1 serial debug header but I've read numerous guides about using Putty, HyperTerminal, or the "screen" command with a baud rate of 115200 to connect to the BeagleBone's COM port or ttyUSB port as a USB serial device.  Does this functionality no exist in the BeagleBone Black?

On Monday, May 13, 2013 4:44:09 PM UTC-4, alberto.mar...@gmail.com wrote:

As far as I know, no serial over USB in BBB.

[Gerald Coley]

It does not currently. We are working on this feature so you can do this over USB. I hope it is in the next release which is a week away. That is our plan at the moment.

Gerald

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[evilwulfie]

while your at it  heres 2 more errors that need fixing in the current image


dropbearkey -t dss -f dropbear_dss_host_key
touch /var/log/lastlog

these need to be done to take care of 2 errors in syslog when logging in via SSH

[Gerald Coley]

There is no FTDI device on the board as is clearly indicated. 

We are working to get a serial connection over the USB in the next release if all goes well.

Gerald

On Tue, May 14, 2013 at 10:55 PM, <mod...@gmail.com> wrote:

I too was disappointed when I could not get a serial connection even though a COM5 port named Gadget Serial appeared on my Win 7 box. I was successful however with SSH. Just use Putty and open a SSH session to https://192.168.7.2 port 22.
Mike

On Monday, May 13, 2013 2:25:56 PM UTC-6, Mike Mogenson wrote:

I'm having trouble connecting to the USB serial terminal of my new BeagleBone Black with the stock version of Angstrom that shipped on the board.  I'm running a virtual machine of Ubuntu 12.04 LTS 32bit in VirtualBox on Windows 7 Pro 64 bit.  I've installed the USB 2.0 drivers from the VirtualBox extension pack, I've disabled auto-mounting USB devices in Windows 7 by entering "mountvol /N" in the command prompt, and I've attached the USB Device "Circuitco BeagleBoneBlack [0308]" to the virtual Ubuntu machine.

If I run "lsusb" in Ubuntu I see "Bus 001 Device 007: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget" however no ttyUSB devices are created so I ran the mkudevrule.sh script from /media/BEAGLEBONE/Drivers/FTDI, logged out and reinserted the BBB.  Still no ttyUSB entries in /dev.  I noticed that the mkudevrule script is for a USB vendor id of 0403 and product id of a6d0 but the BBB entry in lsusb has a vendor id of 1d6b and a product id of 0104.  So I changed them in the udev rule, reloaded the udev rules, logged out for good measure, and reinserted the BBB.  Still no ttyUSB entries in /dev and no ftdi_sio or usbserial module in lsmod.

I decided to do things manually.  I entered "sudo modprobe ftdi_sio vendor=0x1d6b product=0x0104".  This loaded the FTDI module but didn't create the ttyUSB entries in /dev.  I checked "cat /proc/devices | grep -i 'ttyUSB'" which gave me "188 ttyUSB".  I then checked "sudo cat /proc/tty/driver/usbserial" which gave me "usbserialinfo:1.0 driver:2.0" but no entries for FTDI serial devices.

At this point I'm admitting I'm stuck.  Does anyone having any advice on how to access the USB serial port of the BeagleBone Black?  Is my assumption about the different USB vendor id and product id correct?  Am I (hopefully) missing something really trivial that will make this all work?

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.