[casper] BEE2 enclosure
Hi everyone, Does anyone have an off-the-shelf solution for a rack-mountable BEE2 case? Thanks, Laura
[casper] ROACH start-up issues.
Dear CASPERites, We received our ROACH board from Digicom, and I am trying to get the basic communication going. The Xport web interface shows up when I connect to 192.168.4.20, and I used that to configure the serial interface to talk at 115200 bauds, 8N1. However, when I connect a serial terminal (ckermit running on Ubuntu) and restart the ROACH system, I see no activity on the serial port. I ruled out problems with the serial cable by short-circuiting pins 2/3 and 7/8 to create a loop-back - this should simply echoed back what I typed and it did. When I telnet to 192.168.2.40, port 10001, I do not see any uBoot prompt. Any clues on what is going wrong with this board? Do I have start all over again and use a usbWiggler as described in http://casper.berkeley.edu/wiki/ROACH_Bringup? cheers, Ramesh
Re: [casper] ROACH start-up issues.
Hi Ramesh, Are you sure you're using a null modem cable? ( http://casper.berkeley.edu/wiki/Equipment_Cables) Also, I haven't tried ckermit, you may want to try using minicom or picocom. Power cycling after you've tried to connect. Mark On Wed, Sep 8, 2010 at 2:19 PM, Ramesh Karuppusamy ram...@mpifr.de wrote: Dear CASPERites, We received our ROACH board from Digicom, and I am trying to get the basic communication going. The Xport web interface shows up when I connect to 192.168.4.20, and I used that to configure the serial interface to talk at 115200 bauds, 8N1. However, when I connect a serial terminal (ckermit running on Ubuntu) and restart the ROACH system, I see no activity on the serial port. I ruled out problems with the serial cable by short-circuiting pins 2/3 and 7/8 to create a loop-back - this should simply echoed back what I typed and it did. When I telnet to 192.168.2.40, port 10001, I do not see any uBoot prompt. Any clues on what is going wrong with this board? Do I have start all over again and use a usbWiggler as described in http://casper.berkeley.edu/wiki/ROACH_Bringup? cheers, Ramesh
Re: [casper] ROACH start-up issues.
Hi Ramesh, Is there a setting in ckermit to turn off flow control? Thanks, Henry On 9/8/2010 1:41 PM, Ramesh Karuppusamy wrote: Hi Mark, hi Sean: Thank you very much for the quick response. Yes, a null-modem cable solved the issue partly. I see the messages from the roach unit in my C-Kermit terminal emulation software. But I am unable to interrupt the boot procedure at Hit any key to stop autoboot: point. Once booted, I am unable to type anything at the roach login: prompt too? Am I missing something obvious? I am attaching the serial console messages with this mail. Any ideas? Thanks again. Cheers, Ramesh On Sep 8, 2010, at 8:29 PM, Mark Wagner wrote: Hi Ramesh, Are you sure you're using a null modem cable? (http://casper.berkeley.edu/wiki/Equipment_Cables) Also, I haven't tried ckermit, you may want to try using minicom or picocom. Power cycling after you've tried to connect. Mark On Wed, Sep 8, 2010 at 2:19 PM, Ramesh Karuppusamy ram...@mpifr.de mailto:ram...@mpifr.de wrote: Dear CASPERites, We received our ROACH board from Digicom, and I am trying to get the basic communication going. The Xport web interface shows up when I connect to 192.168.4.20, and I used that to configure the serial interface to talk at 115200 bauds, 8N1. However, when I connect a serial terminal (ckermit running on Ubuntu) and restart the ROACH system, I see no activity on the serial port. I ruled out problems with the serial cable by short-circuiting pins 2/3 and 7/8 to create a loop-back - this should simply echoed back what I typed and it did. When I telnet to 192.168.2.40, port 10001, I do not see any uBoot prompt. Any clues on what is going wrong with this board? Do I have start all over again and use a usbWiggler as described in http://casper.berkeley.edu/wiki/ROACH_Bringup? cheers, Ramesh
Re: [casper] ROACH start-up issues.
Hi Mark, Great, picocom works fine. Appears like both ckermit had some strange setting that simply prevented it from talking to the Xport device. And Henry, yes kermit has a command to turn-off flow control (set flow-control none at the kermit prompt). Thanks folks, now I can go sleep in peace! Cheers, Ramesh On Sep 8, 2010, at 11:10 PM, Mark Wagner wrote: Hi Ramesh, Can you confirm that your terminal client is set to: BAUD = 115200, 8 Bits, no parity, stop bit, no flow control If this is the case, then i'm not sure what the problem is. Do you have the same problem with a different client? For instance, I use picocom: $ sudo apt-get install picocom $ picocom --baud 115200 /dev/ttyUSB0 (where /dev/ttyUSB0 is the serial device) Thanks, Mark On Wed, Sep 8, 2010 at 4:41 PM, Ramesh Karuppusamy ram...@mpifr.de wrote: Hi Mark, hi Sean: Thank you very much for the quick response. Yes, a null-modem cable solved the issue partly. I see the messages from the roach unit in my C-Kermit terminal emulation software. But I am unable to interrupt the boot procedure at Hit any key to stop autoboot: point. Once booted, I am unable to type anything at the roach login: prompt too? Am I missing something obvious? I am attaching the serial console messages with this mail. Any ideas? Thanks again. Cheers, Ramesh On Sep 8, 2010, at 8:29 PM, Mark Wagner wrote: Hi Ramesh, Are you sure you're using a null modem cable? (http://casper.berkeley.edu/wiki/Equipment_Cables) Also, I haven't tried ckermit, you may want to try using minicom or picocom. Power cycling after you've tried to connect. Mark On Wed, Sep 8, 2010 at 2:19 PM, Ramesh Karuppusamy ram...@mpifr.de wrote: Dear CASPERites, We received our ROACH board from Digicom, and I am trying to get the basic communication going. The Xport web interface shows up when I connect to 192.168.4.20, and I used that to configure the serial interface to talk at 115200 bauds, 8N1. However, when I connect a serial terminal (ckermit running on Ubuntu) and restart the ROACH system, I see no activity on the serial port. I ruled out problems with the serial cable by short-circuiting pins 2/3 and 7/8 to create a loop-back - this should simply echoed back what I typed and it did. When I telnet to 192.168.2.40, port 10001, I do not see any uBoot prompt. Any clues on what is going wrong with this board? Do I have start all over again and use a usbWiggler as described in http://casper.berkeley.edu/wiki/ROACH_Bringup? cheers, Ramesh
