Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I've followed the serial howto to install a serial port, and am now trying to install debian, but I can't break into the UBoot command line.
I can run kermit succesfully, and when I boot the DNS I see the startup data, with the "Hit any key to stop autoboot" message, but no amount of key pressing seems to make any difference, whether I try the "SPACE 1" sequence, or anything else.
I'm assuming that the serial cable is ok, or I wouldn't see the boot messages - is it possible that a dodgy cable would only transmit data one way?
Here's the start of the output from the kermit session:
# kermit -l /dev/ttyS0 -b 115200 C-Kermit 8.0.211, 10 Apr 2004, for Linux Copyright (C) 1985, 2004, Trustees of Columbia University in the City of New York. Type ? or HELP for help. (/root/dns/etch/) C-Kermit>set carrier-watch off (/root/dns/etch/) C-Kermit>c Connecting to /dev/ttyS0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- ** LOADER ** ** MARVELL BOARD: RD-88F5182-NAS-2 LE U-Boot 1.1.1 (Dec 20 2006 - 15:49:31) Marvell version: 1.7.3 DRAM CS[0] base 0x00000000 size 64MB DRAM Total size 64MB [8192kB@ff800000] Flash: 8 MB Addresses 20M - 0M are saved for the U-Boot usage. Mem malloc Initialization (20M - 16M): Done *** Warning - bad CRC, using default environment Soc: MV88F5182 Rev 2 CPU: ARM926 (Rev 0) running @ 500Mhz SysClock = 166Mhz , TClock = 166Mhz USB 0: host mode USB 1: host mode PCI 0: PCI Express Root Complex Interface PCI 1: Conventional PCI, speed = 33000000 Hit any key to stop autoboot: 0 ## Booting image at ff820000 ... Image Name: Linux-2.6.12.6-arm1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1426456 Bytes = 1.4 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK
The firmware is version 1.03. If anyone has any ideas what may be wrong I'd really appreciate it.
Regards,
Barney
Offline
baarney wrote:
I'm assuming that the serial cable is ok, or I wouldn't see the boot messages - is it possible that a dodgy cable would only transmit data one way?
Regards,
Barney
Yes it is - it is also possible that the terminal configuration could be incorrect, try setting flow control to none
RS232 comms can be something of a black art at times, baud rate, parity and stop bits must always match, and then depending on the devices you are connecting you have to pay attention to RTS/CTS, DSR/DTR and flow control - occasionally one device will not use these terms and you'll need to insert jumpers to "fake" the term.
Offline
fordem wrote:
try setting flow control to none
Doh! That would do it. I got so hung up in checking the cable, that I overlooked the simple things!
Thanks. Much appreciated.
Offline
Glad I could help - I don't deal with that stuff as much as I used to, but at the same time still often enough that a serial port is a mandatory requirement on my laptop.
Offline