The FTDI chip will show up as four serial devices -- the third is the one you want. (eg. on my system it's ttyUSB2). The serial settings are summarised here (https://casper.berkeley.edu/wiki/ROACH_NFS_guide)-- basically 115200 bps, 8N1, no hardware flow control.
On 12 February 2014 20:58, Richard Black <[email protected]> wrote: > Jack and all, > > Well, using the *right* connector on the ROACH-2 board (USB-B), I'm able to > get the "USB-OK" LED to light up. However, I still see nothing in the > minicom terminal (using RHEL 6.5). I earlier read on the mailing list that > there were some rule issues with serial communications with RHEL, but it > didn't seem to be completely resolved. > > I've also noticed something peculiar. If I power-up the ROACH-2 while having > minicom open on the PC, the ROACH-2 fault LED lights up and does not turn > off until I terminate minicom. Any idea why this might be happening? > > Thanks all, > Richard > > > On Wed, Feb 12, 2014 at 1:37 PM, Jack Hickish <[email protected]> wrote: >> >> Yeah, it's not great naming. "host" and "slave" or something like that >> would probably have been better. I'm pretty sure FTDI is just the >> brand name for the chip which provides USB to rs232. I didn't know >> this, but it seems it stands for future technology devices >> international :) >> >> On 12 February 2014 20:32, Richard Black <[email protected]> wrote: >> > Jack, >> > >> > I've been connecting to the USB-A (the one that is named PPC USB). I >> > assumed >> > that that was the correct port since the PPC was booting up. >> > >> > I'll try again with the FTDI connector. >> > >> > For the sake of curiosity, what does FTDI stand for? I haven't been able >> > to >> > find any documentation on the wiki about what it means. >> > >> > Thanks again, >> > >> > Richard Black >> > >> > >> > On Wed, Feb 12, 2014 at 1:28 PM, Jack Hickish <[email protected]> >> > wrote: >> >> >> >> Hi Richard, >> >> >> >> There are two USB connectors on the board -- the USB B one is the one >> >> which will show up to a PC as a serial device. The USB A one for >> >> adding slave devices to the power pc (eg booting a file system from >> >> usb) -- are you connecting to the right one? >> >> >> >> Cheers, >> >> Jack >> >> >> >> On 12 February 2014 20:20, Richard Black <[email protected]> wrote: >> >> > Hi all, >> >> > >> >> > We've been trying to get the serial link between the ROACH-2 and a >> >> > PC, >> >> > and >> >> > we haven't had any success at all. >> >> > >> >> > These are the cable configurations we've tried: >> >> > >> >> > 1. USB-A Male (ROACH)/USB-A Male (PC) >> >> > 2. USB-A Male (ROACH)/USB-Serial Adapter/DB9 Female (PC) >> >> > 3. RS232 Pin Headers on-board/DB9 Male Connector/DB9 Female (PC) >> >> > >> >> > Unfortunately, none of these register any activity on the PC. These >> >> > configurations have been tested on the following operating systems: >> >> > >> >> > 1. RHEL 6.5 >> >> > 2. Ubuntu 11.04 >> >> > >> >> > When I connect the cables up and run dmesg, I see no activity. I've >> >> > tried >> >> > listening on ttyS#, ttyUSB# for anything and nothing happens in my >> >> > minicom >> >> > terminal. >> >> > >> >> > Also, our USB-Serial Adapter has a status LED to indicate that it is >> >> > powered >> >> > for conversion, but the LED does not light when connected to the >> >> > ROACH-2. >> >> > This makes me suspicious that the USB connector on the ROACH-2 is not >> >> > functioning. >> >> > >> >> > Has anybody else had a problem with this, or do we unfortunately have >> >> > a >> >> > couple of faulty ROACH-2 boards? >> >> > >> >> > Thanks guys, >> >> > Richard Black >> > >> > > >
