Thanks for your reply restamp. I was only trying to be brief and was not sure if the added info was important. Here is more detailed information if it helps:
I was in the process of updating the Ubuntu OS on the Sheeva (GTI version) via LAN when I lost power. Now I am not able to ping the Sheeva via LAN (Destination Host Unreachable) using the IP address the DHCP server assigned (no, the IP address has not changed) to the Sheeva to be able to restart the update. I have tried to do both a hard and soft reboot of the Sheeva, but with no luck. The network lights on the Sheeva do blink so it is seeing the LAN signal, but I believe the LAN driver on the Sheeva has become corrupt. And yes, the LAN cable is unplugged from the Sheeva when I am using the serial/USB connection.
I am trying to reflash the system to fix the LAN drivers so I can gain LAN connectivity to the Sheeva again and be able to update the Ubuntu OS again.
Since I had not needed to use the serial interface until now, I was not sure if the U-Boot screen came up on it's own when the connection with PuTTY was established, or if I had to invoke the U-Boot screen via a command line using PuTTY. I did not find any documentation indicating which way to go about obtaining the U-Boot screen, which was the idea behind posting my question. I have come to find out, that the U-Boot screen will come up on it's own when the Sheeva and PuTTY are properly setup and connected to the host system.
I am using Linux Mint 8 (Helena x64) as my host.
I have setup PuTTY as needed:
- 115200 Baud rate
- 8 Data bits encoding each character
- N Parity (none/no)
- 1 Stop bit
- 0 Flow control (none)
I have removed brltty. (Notes for Ubuntu karmic, may be applicable to other versions) You may not get any response on the /dev/ttyUSBx interface(s). In that case, you may need to remove brltty using:
sudo apt-get remove brltty
I have created the file for loading the serial drivers automatically and rebooted. (Thanks for the link, I did not know about this one.
I have been able to obtain the following line:
[375087.475359] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0
I have verified ttyUSB0 has loaded in the /dev folder. It unloads this file when I disconnect the Sheeva, and automatically reloads the file when the Sheeva is plugged back in.
I am still unable to open the serial port, as PuTTY gives me a Fatal Error dialog box indicating this. I will do some more reading /digging within the forum to see what I am missing. If you are able to push me in the right direction I would appreciate it. If I find a solution I will post again in case the information would be useful to someone.
After a little more digging I believe I know what the problem is. http://www.openplug.org/plugwiki/index.php/Serial_terminal_program
indicates the FTDI FT2232D provides two serial ports via USB:
- port 0 (*A) is the JTAG interface
- port 1 (*B) is the console (/dev/ttyS0 on the plug; default 115200 baud, 8N1, no flow control)
Since I am needing to access the console (port 1) the ttyS0 file in my /dev should be recognized (an un X'ed icon). The ttyS0 file is there but has the X'ed icon. So if I am understanding things correctly, the problem is the ttyS0 file does not seem to be loading (during boot of the host system?) which (I think) is why PuTTY is not being allowed to connect to the Sheeva.
The ttyUSB0 un X'ed icon is showing, which is a good thing I think.
Here is the result of my dmesg, if it helps. The ttyS0 file is not showing up as being loaded:
[ 9146.600024] usb 4-1: new full speed USB device using uhci_hcd and address 4
[ 9146.878171] usb 4-1: configuration #1 chosen from 1 choice
[ 9146.886362] usb 4-1: Ignoring serial port reserved for JTAG
[ 9146.891160] ftdi_sio 4-1:1.1: FTDI USB Serial Device converter detected
[ 9146.891205] usb 4-1: Detected FT2232C
[ 9146.891209] usb 4-1: Number of endpoints 2
[ 9146.891213] usb 4-1: Endpoint 1 MaxPacketSize 64
[ 9146.891216] usb 4-1: Endpoint 2 MaxPacketSize 64
[ 9146.891219] usb 4-1: Setting MaxPacketSize 64
[ 9146.892124] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0
I did follow the instructions in the post I found here: http://openplug.org/plugforum/index.php?topic=2.0
(see reply's six, seven and eight.)
But ttyS0 still does not load / recognize the Sheeva, so PuTTY and U-Boot will not connect. I'll keep looking around the forum for solutions and will post back here if I find anything.
Let me know if anyone has any ideas, or knows of a post which will help.