Only one USB serial is showing up!

[smartboyathome]

I am trying to access my sheevaplug as shown on here and here. Neither of those seem to help, as I always only get one serial interface. I even tried rmmod'ing and then modprobing ftdi_sio, and that didn't help. Here is what dmesg says about the sheevaplug after I put it in:

Code:

usb 7-2: new full speed USB device using uhci_hcd and address 6
usb 7-2: configuration #1 chosen from 1 choice
usb 7-2: Ignoring serial port reserved for JTAG
ftdi_sio 7-2:1.1: FTDI USB Serial Device converter detected
usb 7-2: Detected FT2232C
usb 7-2: FTDI USB Serial Device converter now attached to ttyUSB0

It seems like it is ignoring the jtag interface? I am on Arch Linux with the most up-to-date stuff in the stable repositories (testing not enabled).

EDIT: I tested it with GtkTerm, and in fact I am able to get the uBoot message. So for some reason it hates the jTag.

[debio]

I would investigate this line:
usb 7-2: Ignoring serial port reserved for JTAG

There's probably some new method for accessing JTAG that was added in the new kernel or something. It knows it's there, it just won't use it as a serial console.

EDIT:
A quick google shows that if you really want to access JTAG, you should investigate openocd. The serial driver was revised so it doesn't treat JTAG interfaces as serial consoles.

[smartboyathome]

I would investigate this line:
usb 7-2: Ignoring serial port reserved for JTAG

There's probably some new method for accessing JTAG that was added in the new kernel or something. It knows it's there, it just won't use it as a serial console.

EDIT:
A quick google shows that if you really want to access JTAG, you should investigate openocd. The serial driver was revised so it doesn't treat JTAG interfaces as serial consoles.

Ok, thanks. I was just wondering why it was showing one ttyUSB instead of two. If I need JTAG, I will use OpenOCD.

[debio]

Are you using the standard kernel26 package? I'm on Arch, and when I connect my plug, two USB ttys show up and I can't seem to get OpenOCD to access JTAG. I'm not sure what could be different.

[draimus]

Has anyone here with only 1 serial port showing gotten OpenOCD to work.  I'm running Ubuntu 9.10 with kernel 2.6.31 and I get the same dmesg note about ignoring the JTAG interface.  I seem to recall 9.04 allowed me to see both usb interfaces on the sheeva as ttyUSB interfaces. 

I have never gotten the sheeva-installer to work at all (on 9.04 and now).  I always get a JTAG error "Error: JTAG communication failure: check connection, JTAG interface, target power etc.".

So what is considered the proper configuration prior to running OpenOCD.  Having 2 ttyUSB interfaces or just the 1?

[superpat]

Hi,

I too am puzzled about serial USB enumeration.

I have just got around to trying a RFXCOM  433Mhz receiver for X10 and various sensors.

When I  plugged it into the Sheevaplug USB type A socket, the kernel  ( bog standard from Installer v1.0  V 2.6.30.2 ) showed this:-

usb 1-1: new full speed USB device using orion-ehci and address 3

usb 1-1: configuration #1 chosen from 1 choice

ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected

usb 1-1: Detected FT232RL

usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0

root@ubuntu:/var/log#

Now the funny thing is that I am already using /dev/ttyUSB0  to connect to the Sheevaplug with PUTTY,   looking at /dev

root@ubuntu:/var/log# dir /dev

block    null   ram4     tty24  tty53    ttype

bus    port   ram5     tty25  tty54    ttypf

char    ppp    ram6     tty26  tty55    ubi0

console    psaux  ram7     tty27  tty56    ubi0_0

core    ptmx   ram8     tty28  tty57    ubi_ctrl

cpu_dma_latency     pts    ram9     tty29  tty58    urandom

fd    ptyp0  random   tty3   tty59    usbdev1.1

full    ptyp1  rtc0     tty30  tty6     usbdev1.1_ep00

initctl    ptyp2  serial   tty31  tty60    usbdev1.1_ep81

input    ptyp3  shm    tty32  tty61    usbdev1.3

kmem    ptyp4  sndstat  tty33  tty62    usbdev1.3_ep00

kmsg    ptyp5  stderr   tty34  tty63    usbdev1.3_ep02

log    ptyp6  stdin    tty35  tty7     usbdev1.3_ep81

loop0    ptyp7  stdout   tty36  tty8     vcs

loop1    ptyp8  tty    tty37  tty9     vcs2

loop2    ptyp9  tty0     tty38  ttyS0    vcs3

loop3    ptypa  tty1     tty39  ttyS1    vcs4

loop4    ptypb  tty10    tty4   ttyUSB0  vcs5

loop5    ptypc  tty11    tty40  ttyp0    vcs6

loop6    ptypd  tty12    tty41  ttyp1    vcsa

loop7    ptype  tty13    tty42  ttyp2    vcsa2

mapper    ptypf  tty14    tty43  ttyp3    vcsa3

mem    ram0   tty15    tty44  ttyp4    vcsa4

mtd0    ram1   tty16    tty45  ttyp5    vcsa5

mtd0ro    ram10  tty17    tty46  ttyp6    vcsa6

mtd1    ram11  tty18    tty47  ttyp7    xconsole

mtd1ro    ram12  tty19    tty48  ttyp8    zero

mtdblock0    ram13  tty2     tty49  ttyp9

mtdblock1    ram14  tty20    tty5   ttypa

net    ram15  tty21    tty50  ttypb

network_latency     ram2   tty22    tty51  ttypc

network_throughput  ram3   tty23    tty52  ttypd

root@ubuntu:/var/log#

You can see that there is only one ttyUSB.

So my question is how do I set up udev rules  ( I suppose ) to enumerate a ttyUSB for the RFXCOM receiver.


I tried  another experiment,  I disconnected my min usb cable and the PUTTY terminal, and used SSH to look at what was going on when I plugged my RFXCOM receiver in to the type A port.

What happened was that the kernel "found " the ftdi device, and connected it to ttyUSB0 again!.  However  although the receiver was supposed to be pumping out loads of ascii text, there was nothing from /dev/ttyUSB0.    When I reconnected the PUTTY cable to the min slot and used ttyUSB0, it picked up where it left off, connected as a Linux console! So I assume that the data structure for ttyUSB0 originally set up on first connection of the PUTTY cable to the "jtag" port has persisted through the disconnection

Advice gratefully received

cheers

Patrick

[superpat]

@myself

Just found this:-

Re: USB to Serial Cable -- no data from ttyUSB0
Quote:
Originally Posted by ramjet_1953 View Post
I don't know why, but the Ubuntu developers see fit to install brltty as a default.

This is a package that allows blind people to use a Braille reader.

Unfortunately, it interferes with serial communications for other uses.

Go into Synaptic package manager and ensure that these 3 packages are NOT installed:

1. brltty
2. brltty-flite
3. brltty-x11

Hopefully, after they are removed your USB to Serial will come to life.

Regards,
Roger

Thanks!! This fixed my problem with my serial connection also!!

Just going to see if this is the problem

cheers
P

EDIT

No  No britty or derivatives installed!

onward!