Use netconsole to troubleshoot uBoot without a serial cable

Re: Use netconsole to troubleshoot uBoot without a serial cable

Quinten — Mon, 04 Mar 2013 15:03:33 -0500

I am trying to get netconsole set up on a SeaGate GoFlex. I already followed this guide: http://forum.doozan.com/read.php?3,14,14

but I think that I followed it too early, as it does not work for me. It was suggested that I try upgrading uboot, but I guess because it's already been altered, the md5sum is different and the script here: http://projects.doozan.com/uboot/ refuses to run.

Here's the output of fw_printenv:

=====================================
fw_printenv output:
=====================================
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:

${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
serverip=192.168.0.103
ipaddr=192.168.0.107
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout

nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
=======================================

I'd like to force an upgrade of uboot, I guess. How can I do it manually, without using the script?

Re: Use netconsole to troubleshoot uBoot without a serial cable

Dave Gilbert — Sat, 23 Feb 2013 16:45:12 -0500

Hmm first time I've had to use netcat with uboot; I'm finding a few weird things:
1) It's rare for me to be able to interrupt the boot during the 3.2.1 countdown - just carries on; unplugging the boot device stops it and I can interact.
2) printenv in uboot causes nc to exit, even though from wireshark the box sent all the data (Hint: wireshark has a thing to extract the whole stream; very nice).

both of these seem true with both nc and socat (on Ubuntu raring).

Dave

netconsole no joy dockstar

Martin Espinoza — Wed, 13 Feb 2013 08:59:01 -0500

Latest u-Boot from here, followed netconsole instructions, no output.

bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
baudrate=115200
usb_rootdelay=10
bootdelay=8
serverip=192.168.1.5
ipaddr=192.168.1.2
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

Help?

Re: Use netconsole to troubleshoot uBoot without a serial cable

bodhi — Wed, 12 Dec 2012 19:33:39 -0500

If you want to use Arch and be able to set UBoot envs, I'd suggest to use only blparam to do that (don't use fw_setenv). See if it works without corrupting the envs, I think it is very likely the reason that it got booted back to stock.

Another thought: did you check dmesg after executing fw_setenv?

Re: Use netconsole to troubleshoot uBoot without a serial cable

winestock — Wed, 12 Dec 2012 18:45:00 -0500

After I modified /etc/fw_env.config I executed fw_printenv which listed the u-boot enviroment without an errors given. After I install Arm Linux, blparam does not exist. I have to install the package pogoplug-blparam.

What is interesting is if I try to revert back to the stock Pogoplug OS using this proceedure (http://archlinuxarm.org/platforms/armv5/pogoplug-series-4#qt-platform_tabs-ui-tabs3) it won't work for me. Nothing happens and I am still running out the Arm Linux u-boot for the PPv4. This is one of the reasons why I was hoping to use netconsole on the PPv4 so I can why this is failing for me.

Re: Use netconsole to troubleshoot uBoot without a serial cable

bodhi — Wed, 12 Dec 2012 18:12:36 -0500

Without seeing your log and the exact output, I can only make educated guess. It probably messed up your UBoot envs, so UBoot used the default envs, therefore it was booted back to stock in NAND.

The file /etc/fw_env.config should have the correct info for where the uboot envs are in NAND. One easy way to verify it is by executing fw_printenv, if you see all envs that you'd expected, and you get no Bad CRC error then your fw_setenv should work fine.

After you've first installed ALARM using the instruction at Arch site, you should only use blparam to list envs:

/usr/local/cloudengines/bin/blparam

and set envs:

/usr/local/cloudengines/bin/blparam envname=value
or
 /usr/local/cloudengines/bin/blparam envname='...'  (if the value contain a script)

So if your fw_printenv gave you error, then use blparam to list the envs to see if it works OK.

Re: Use netconsole to troubleshoot uBoot without a serial cable

winestock — Wed, 12 Dec 2012 17:45:25 -0500

I was hoping to be able to use netconsole on the PPv4 with needing a physical serial cable. Oh well.

Maybe you can answer a question for me. When I use fw_setenv after I have installed Arm Linux and reboot my PPv4 I end up being back at the Pogoplug OS. I have two PPv4 and this happens with both. Any idea why that happens?

Re: Use netconsole to troubleshoot uBoot without a serial cable

bodhi — Wed, 12 Dec 2012 16:51:53 -0500

@winestock,

I dont think that UBoot version support netconsole. It's basically the same as the stock UBoot from Cloud Engines. Kevin (ALARM developer) said that he only recompiled and configured it to boot Arch, but did not add anything new.

Davy's UBoot version, which has netconsole, works with everything but SATA. And currently, it can only be flashed through serial console, per his procedure.

I've figured out how to boot Debian on PogoV4 SATA using ALARM's UBoot version, without using serial console. Basically, you just install ALARM, and then add/modify the UBoot envs through command line to enable booting with Debian kernel on either SATA or USB drive. I'll write it up and post here if that's what you're looking for!

Re: Use netconsole to troubleshoot uBoot without a serial cable

winestock — Wed, 12 Dec 2012 10:12:03 -0500

Hi,

I would like to know if the u-boot for the Pogoplug Series 4 supports netconsole. The u-boot that I have installed comes from http://archlinuxarm.org/os/ppv4/ppv4-install.sh. I would like to know if I perform the following commands will I be able to use netconsole from the Pogoplug Series 4 u-boot:

fw_setenv serverip 192.168.1.2 
fw_setenv ipaddr 192.168.1.100 
fw_setenv if_netconsole 'ping $serverip' 
fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;' 
fw_setenv preboot 'run if_netconsole start_netconsole'

Re: Use netconsole to troubleshoot uBoot without a serial cable

lcg — Wed, 28 Nov 2012 16:44:26 -0500

Thanks, after enabling netconsole and struggling with nc netconsole works very well (concretely: using 'nc -klup 6666 &' and 'socat STDIO UDP-SENDTO:192.168.1.14:6666', everything else failed). I don't want to do double-postings, so if anyone can help me to get Wheezy or Squeeze to work/ boot, please answer here: http://forum.doozan.com/read.php?2,9256,10757#msg-10757.

In short, the problem is that after installing successfully RescueV2 (in flash) via Jeff's embed-debian (booted from USB) the install scripts of wheezy (adjusted to kernel 3.2.0-4) and squeeze (adjusted for debootstrap, see script from shyd) both went fine without any error, but they do not come to a stage where ping/ssh and therefor remote access is possible. DavyGravy's NSA rootfs-image does not boot too. However, RescueV2 (from flash), RescueV3 (from USB with kernel 3.3.2), Jeff's embed-debian (from USB) boot perfectly well. As RescueV3 boots, it should not be related to kernel-version per se.

"Not booting" means the netconsole shows all boot perfectly, ie. "Starting kernel..." and successfully loading "uImage" and "uInitrd", but then no ping nor ssh is possible (IP is received via dhcp & MAC, so that's not the problem I think). It is not the USB stick (tried different sticks with different images on it) and I don't know how to see any logfiles/ messages. Netconsole ends with the message "Starting kernel...", so no messages after that. Is it possible to get further messages?

Comment: installing RescueV2 from within RescueV3 failed with error "uboot too old/ not latest" although Jeff's uboot script tells definitely "up to date". RescueV2 was therefor installed from embed-debian (bootet from USB) without any problem. arcNumber is correctly set to 2998 (Dockstar).

Question: Can the whole thing be related to "usb_root=/dev/sda1 ro" as Bodhi mentions that read-only is unsual (I did not set that myself)?

Again, please answer on the other thread to avoid double posting unless this seems to be a problem related to uboot or can be solved via netconsole.

Re: Use netconsole to troubleshoot uBoot without a serial cable

bodhi — Mon, 26 Nov 2012 16:57:30 -0500

Yes, it is safe to set up netconsole right after a successful UBoot install. As long as you have installed the new UBoot, and it reported as successful, print out the fw envs like you did above and see all envs are set properly.

Your UBoot envs has rootfs-related setting that were not normal (read only) I think because of the failed "kernel too old". But it should not prevent the Dockstar to boot the new UBoot, so you can use netconsole to stop it at the countdown. The worse case is: with the new UBoot, you can download Davy's rootfs and boot the Dockstar with it.

My observation is based on the assumption that your UBoot installation was successful. Your UBoot envs look good for booting until the point before loading the kernel. Do you keep the log of your installation? can you see it on the terminal now?

Re: Use netconsole to troubleshoot uBoot without a serial cable

lcg — Mon, 26 Nov 2012 09:33:34 -0500

Hello,

is it possible and safe to enable netconsole directly after installing uboot BUT BEFORE doing a reboot? Problem is that (see thread under "Debian" but unfortunately unanswered, maybe my question was seen as too easy) the Debian Wheezy install script from Jeff failed with "kernel too old" error AFTER uboot was already installed by the script. I used a clean new Dockstar. Thus, as far as I can see fw_* commands are already there but netconsole is not set (and I did not reboot yet because the install failed).

So to set the commands now is ok and then reboot and then netconsole is working immediately? ie.

fw_setenv serverip 192.168.1.2
fw_setenv ipaddr 192.168.1.100
fw_setenv if_netconsole 'ping $serverip'
fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
fw_setenv preboot 'run if_netconsole start_netconsole'

here the environment:

-bash-3.2# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_rootfstype=ext2
usb_rootdelay=10
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:1A:DD:43
arcNumber=2097
usb_root=/dev/sda1 ro
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/sbin/init-ro
-bash-3.2#

thanks,
leo

Re: Use netconsole to troubleshoot uBoot without a serial cable

juan — Tue, 02 Oct 2012 23:46:46 -0400

try ncat instead. i had no problem using just ncat -lu 6666. ncat is part of the nmap suite

i get connection, hit enter to interrupt and i am dropped into a marvel shell. can type commands and not get disconnect.

get ncat here: http://nmap.org/ncat/

Re: Use netconsole to troubleshoot uBoot without a serial cable

Brian M — Sat, 29 Sep 2012 13:03:10 -0400

Hi Jeff,
Sorry to bother, but I'm in a spot of same. (I'm a Linux noobie, & old PC hack)
Got a GoFlex Home running Arch Linux and had been happily running until a pacman upgrade a few days ago that went AWOL (glibc errors etc.)
I've got back to a stage of solid green light, and can get nc to talk and see your U Boot but cannot get it to halt process.
Tried running two sessions, as suggested, but think I'm missing something in trying this?

ubuntu@ubuntu:~$ nc -lu 6666 &
[1] 8823
ubuntu@ubuntu:~$ nc -lu 10.10.10.5 6666

U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:   2   1  0 
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

Hope you can point me in the right direction.
Thanks
Brian

Re: Use netconsole to troubleshoot uBoot without a serial cable

sambul14 — Tue, 28 Aug 2012 15:13:58 -0400

How do you configure bootargs in Uboot environment to post kernel messages in the same Netconsole window after Uboot messages are finished posting? I've Dockstar with ArchLinux ARM 3.5.2 installed and running. Should anything be configured for this in ArchLinux too?

Re: Use netconsole to troubleshoot uBoot without a serial cable

tempest69 — Mon, 27 Aug 2012 12:17:48 -0400

maybe it can save some headache...
i have to stop and unplug/plug my dockstar to make the netconsole work !
(a reboot was not sufficient)

Re: Use netconsole to troubleshoot uBoot without a serial cable

floodo1 — Mon, 13 Aug 2012 19:54:33 -0400

I have the exact same problem. Had everything working perfectly off SATA, then a 'halt' later and everything appears fine from the uboot output (finds kernel image, and initramfs and says 'starting kernel') but then nothing!

~~~~~~~~~

Actually I don't have the same problem. Seems that your uInitrd file wasn't found during boot. My system finds that as well as uImage.

Re: Use netconsole to troubleshoot uBoot without a serial cable

Sagittarius — Fri, 20 Jul 2012 16:38:01 -0400

I have installed u-boot and rescue system on a GFH for a friend.
The GFH worked very well until a shutdown -h now. I can't get access via SSH when the disk is on its support. Rescue works. I've tried to reinstall the system, same behavior: it boots but after some halt / reboot, 2 or 3 times ;-) no more ssh access, no ip.

Here is what gives me nc -lu -p 6666:

# nc -lu -p 6666

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: ST31000528AS Firm: CC46 Ser#: 5VP6VQAG
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2857200 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.1.10-12-ARCH
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2857136 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

I am wondering why there are these lines:

Seagate GoFlexNet (should'nt it be GoFlexHome?)

UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22

Your help wellcome.

For info:

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
rescue_installed=1
arcNumber=3089
ipaddr=192.168.1.16
ethaddr=00:10:75:2a:17:fd
serverip=192.168.1.18
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
sata_device=0:1
sata_root=/dev/sda1
sata_rootfstype=ext3
sata_rootdelay=10
sata_set_bootargs=setenv bootargs console=$console root=$sata_root rootdelay=$sata_rootdelay rootfstype=$sata_rootfstype $mtdparts $sata_custom_params
sata_boot=ide reset; mw 0x800000 0 1; ext2load ide $sata_device 0x800000 /boot/uImage; if ext2load ide $sata_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_bootcmd=run sata_set_bootargs; run sata_boot
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset

EDIT: I have seen this post: http://forum.doozan.com/read.php?4,3192,3192#msg-3192
Seems my UBI errors are not important. I am trying to understand why the GoFlex Home does not boot more than 2 or 3 times on a SATA drive. :(

Re: Use netconsole to troubleshoot uBoot without a serial cable

rudici — Mon, 21 May 2012 21:05:48 -0400

Jeff,
Woud you mind telling me what version of u-boot was used to configure netconsole and what files were modified to get it to work on the dockstar ? I ask simply because I am looking to use to troubleshoot a freescale processor (mpc5125) to be exact. I haven't had too much sucess using a different processor.

Re: Use netconsole to troubleshoot uBoot without a serial cable

rudici — Thu, 17 May 2012 21:21:13 -0400

Hi davygravy
I 'm not sure I understand what you mean by "working well enough to send commands and receive output". I just have the target connected to the host. I can ping the host from the target but not the other way around since the target is still in the booting stage. So, I would say there's definite connectivity, doubly so when you consider that the => prompt from the target does get accross to the host. But that is the only character that I see on the host coming out the target. I do not see any other ouput nor am I able to interact with the boot.

Re: Use netconsole to troubleshoot uBoot without a serial cable

davygravy — Thu, 17 May 2012 07:54:33 -0400

Is it working well enough to send commands and receive output?

Re: Use netconsole to troubleshoot uBoot without a serial cable

rudici — Wed, 16 May 2012 20:59:23 -0400

It is a private network with only the target and the host machine attached to it. There are no other machines to worry about. So, by interrupting the u-boot process and waiting at the => prompt, it is safe to assume that the target is not trying to send any packets to the host. Therefore, I would say that the network is neither busy nor noisy.

Re: Use netconsole to troubleshoot uBoot without a serial cable

davygravy — Wed, 16 May 2012 19:49:27 -0400

Sounds like you have some sort of intermittent connectivity issue. If you can see the prompt even a little bit then it is connected. Is it a busy or noisy network?

Re: Use netconsole to troubleshoot uBoot without a serial cable

rudici — Wed, 16 May 2012 10:41:53 -0400

Hi DavyGravy,
Thanks for your reply.
I have also tried "socat STDIO UDP-LISTEN:6666" but with no success. Since I can ping successfully from the target to the host, I'm confident that my serverip and ipaddr are set correctly.
However, it's worth noting that i have not been able to ping the other way around, that is from the host to the target.
Also, I feel compelled to point out that at times the prompt => from the boot does make it to the console on the host.

Re: Use netconsole to troubleshoot uBoot without a serial cable

davygravy — Wed, 16 May 2012 04:41:16 -0400

try

socat STDIO UDP-LISTEN:6666

... and... also, are your network and your desktop/laptop set on the proper ip addresses/ranges to make this work? Make sure you've set your serverip and ipaddr correctly...

Re: Use netconsole to troubleshoot uBoot without a serial cable

rudici — Tue, 15 May 2012 23:45:28 -0400

When following the above procedure, the only character that appers to make it from the target to the host is the prompt character which is
=>
Afterwards, if I try issuing the printenv command, I see absolutely nothing.

Here's what I type on the host
$ nc -l -u 6666 &

$ nc -u 192.168.10.12 6666

Any ideas?

Could this be related to the baud rate setting of my terminal?

Re: Use netconsole to troubleshoot uBoot without a serial cable

davygravy — Sun, 06 May 2012 20:17:19 -0400

It (nc) comes with most (all?) unix distros.

socat STDIO UDP-LISTEN:6666

using socat

Re: Use netconsole to troubleshoot uBoot without a serial cable

tikblang — Sun, 06 May 2012 17:52:28 -0400

Can I use this uboot on ZyXEL NSA310? If not, where can I get the source to compile?

cat /proc/cpuinfo
Processor : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS : 1199.30
Features : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part : 0x131
CPU revision : 1

Hardware : Feroceon-KW
Revision : 0000
Serial : 0000000000000000

Many thanks,

Tik

Re: Use netconsole to troubleshoot uBoot without a serial cable

laprjns — Fri, 30 Mar 2012 22:41:04 -0400

Sorry about bring up an old thread but I wanted to confirm a few of restamp's findings on bidirectional netconsole communication with a dockstar / PogoPlug V2. I was trying to get a reliable bidirectional netconsole setup before trying to reflash my dockstars and pogoplugs with davygravy's new uboot for the 3.2 kernel but couldn't get uboot to escape out of the count down to the Marvell prompt. Well I found that rapidly hitting the enter key during the count down will eventually result in getting to the Marvell prompt. I am able to do this with both nc and stocat:

nc -lup 6666

socat STDIO UDP-LISTEN:6666

But like restamp I ran into the instability of both nc and socat exiting for no apparent reason. This exiting was consistently repeatable while using printenv. Unfortunately the version of nc that include with my Salix distro (slackware derivative) did not have the -k option. I eventually found and installed a package called nc.openbsd and by using this command

nc.openbsd -klu 6666

I was able to communicate with uboot without the exiting problems.

Re: Use netconsole to troubleshoot uBoot without a serial cable

iceman2k — Thu, 05 Jan 2012 09:45:58 -0500

Hi,

I'am french and also know EDF (D faut default :p).

for your Linux problem, use a live CD (any ubuntu distribution is a live cd by default, just click on try/test and not install on boot), if you look for ready made VM, look for ubuntu or debian image for vmware, should work on windows virtual pc.

You could also make the image yourself using this link : http://haacked.com/archive/2007/05/06/installing-ubuntu-on-virtual-pc-for-windows-lovers.aspx

http://virtualboximages.com/Ubuntu-9.10-amd64 for vm image of ubuntu.

regards

iceman2k