Welcome! Log In Create A New Profile

Advanced

Help, Pogogplug E02 , No LED,serial cable connected ,what next?

Posted by Looker 
Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 19, 2014 05:08PM
Hi,
I messed up my pogoplug E02 while installing Archlinux and updationg the Kirkwood files somewhere along the line. No LED lights on fornt panel but I did connect an Rs232/usb cable to the jtag connector on the box and was able to get the following:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
No link on egiga0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
u-boot>>

What can I do next to revive this box if possible. I do have the original Pogoplug MTxx files that I backed up before attempting the mod if that helps. I'd really like to try and revive this machine instead of tosssing it out.

Any help of direction would be appreciated.

Thank you
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 19, 2014 05:14PM
Looker,

You are in good shape as long as you can see the u-boot prompt like that! I think your u-boot envs might have been messed up for whatever reason. So the first step is to get a listing for that at the u-boot prompt
> printenv

Most definitely, you only need to adjust u-boot envs to correctly boot the Arch rootfs on USB.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 19, 2014 07:02PM
Thanks Bodhi for the fast response!

Following your advice I received the following after typing " printenv" :

u-boot>> printenv
baudrate=115200
bootargs=root=/dev/nfs nfsroot=: ip=::::::off
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
ethact=egiga0
ethaddr=00:25:31:04:88:1D
machid=dd6
stderr=serial
stdin=serial
stdout=serial
usb_rootfstype=ext3

Environment size: 359/131068 bytes
u-boot>>


Where do I go from here?

Thanks again.
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 19, 2014 09:26PM
Looker,

Yes, the u-boot envs that are needed to boot USB drive are not defined at all, they were gone! Below are what usually defined:
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_device=0:1
usb_root=/dev/sda1
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
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
if_netconsole=ping $serverip
ipaddr=192.168.0.221
serverip=192.168.0.220
arcNumber=3542
usb_rootfstype=ext3
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

At u-boot console you need to set these one by one. You can save time by preparing these statements in a text file, and then cut/paste it at serial console. For example:
setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'
setenv usb_scan_list '1 2 3 4'

and so on. You can see the syntax of setenv: put everything after the first = into a single-quote string. And setenv does not use =.

And since this is my Pogo E02 envs, the ipaddr=192.168.0.221 and serverip=192.168.0.220 are specific to my local network setup. You can adjust them to your own IP addresses. They are only needed to run netconsole, and other command in tftp, nfs,… But really it's not necessary to worry about them yet.

And don't do saveenv in serial console. After you can boot successfully into Arch or Debian, use fw_setenv command to set them for real.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 19, 2014 10:01PM
Thanks,but that's way over my head. Hardware I have no issue with but code I'm a newbie. Any
chance you can walk me through it. Pogo's MAC address doesn't show up in my router anymore as having an ip either.

Thanks
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 20, 2014 12:46AM
OK. Let's go back to the basic. The idea is to make the output of your printenv looks like mine.

yours:
baudrate=115200 
bootargs=root=/dev/nfs nfsroot=: ip=::::::off 
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm 
bootdelay=5 
ethact=egiga0 
ethaddr=00:25:31:04:88:1D 
machid=dd6 
stderr=serial 
stdin=serial 
stdout=serial 
usb_rootfstype=ext3

mine:
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_device=0:1
usb_root=/dev/sda1
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
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
if_netconsole=ping $serverip
ipaddr=192.168.0.221
serverip=192.168.0.220
arcNumber=3542
usb_rootfstype=ext3
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
So do you see that
console=ttyS0,115200

is not on your list? to set it so it will appear on your list, at the U-Boot prompt u-boot>> type this command:
u-boot>> setenv console 'ttyS0,115200'

now to verify that you have set it, at the u-boot prompt u-boot>>, type this command:
u-boot>>printenv

Now the output of your printenv will include the variable console listed as:
console=ttyS0,115200

And do this for the rest of other variables on my list, that are not on your list. After you've done, do printenv again and copy the output into a notepad to save it for future usage (important).

Once you've finished doing this, post that output of printenv here and we'll go from there.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 20, 2014 08:17PM
Hello Bodhi,

Thank you for your help so far, I have oe immediate question regarding the "ethaddr=", does this need to be the mac address off the bottom of the device?

Thanks
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 20, 2014 08:29PM
Looker Wrote:
-------------------------------------------------------
> Hello Bodhi,
>
> Thank you for your help so far, I have oe
> immediate question regarding the "ethaddr=", does
> this need to be the mac address off the bottom of
> the device?
>
> Thanks

Yes, it needs to be that MAC address on the sticker.
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 27, 2014 08:35PM
Hi Bodhi,

Haven't had much time to work on this as other work was too demanding of my time. I'm having an issue and I want to make sure i''ve understood your immediate directive. For clarification, you want me to match ALL your environment variables with yours, correct? That said, I'm having an issue allready with some, I set them with no errors but they don't save when I check them after reboot via the "printenv" command e.g. "led_init=green blinking", using "setenv led_init 'green blinking' " it will except the command and verify with the "printenv
' command but if I reboot it's gone. This only happens with some commands.

Thanks
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 28, 2014 05:03AM
Yes. When you reboot they will be gone. The idea is not to save the envs until after you have successfully booted into Debian. Just to avoid mistake in typos. However, you can save them in serial console, too, if you're sure that the envs were entered correctly. Given you have serial console, it's Ok to save ithem now with u-boot command:
>> saveenv

Just be careful not to execute any other u-boot command without knowing exactly what they are for because a wrong command could lock you out! I'm overly cautious because you're not familiar with u-boot: I think the safest way for someone who is still learning their way around is not to save envs in serial console, just save your log and reenter the commands in Debian.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 28, 2014 08:12PM
Hi Bodhi,

First of all, thank you for your help! I don't know where you get the stamina to put up with newbies like me, I'd go crazy!

Here are the items I'm going to cut and paste into the serial console. I only replaced the first " = " with a space per line, do I need to replace all the " = " with a space on each line? Is it only possible to edit the environment line by line as oppossed to pasting the entire contents all at once? Once I've successfully pasted all the lines how do I test it to boot without unplugging it? Then what?

Thank you again

setenv ethact ‘egiga0’
setenv bootdelay’3’
setenv baudrate ‘115200’
setenv mainlineLinux ‘yes’
setenv console ‘ttyS0,115200’
setenv led_init ‘green blinking’
setenv led_exit ‘green off’
setenv led_error ‘orange blinking’
setenv mtdparts ‘mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)’
setenv mtdids ‘nand0=orion_nand’
setenv partition ‘nand0,2’
setenv stdin ‘serial’
setenv stdout ‘serial’
setenv stderr ‘serial’
setenv rescue_installed ‘0’
setenv rescue_set_bootargs ‘setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params’
setenv 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’
setenv pogo_bootcmd ‘if fsload uboot-original-mtd0.kwb; then go 0x800200; fi’
setenv force_rescue ‘0’
setenv 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’
setenv ubifs_mtd ‘3’
setenv ubifs_set_bootargs ‘setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params’
setenv 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’
setenv 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’
setenv usb_scan_list ‘1 2 3 4’
setenv usb_scan_1 ‘usb=0:1 dev=sda1’
setenv usb_scan_2 ‘usb=1:1 dev=sdb1’
setenv usb_scan_3 ‘usb=2:1 dev=sdc1’
setenv usb_scan_4 ‘usb=3:1 dev=sdd1’
setenv usb_device ‘0:1’
setenv usb_root ‘/dev/sda1’
setenv usb_rootdelay ’10’
setenv usb_set_bootargs ‘setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params’
setenv usb_bootcmd ‘run usb_init; run usb_set_bootargs; run usb_boot’
setenv 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’
setenv start_netconsole ‘setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;’
setenv preboot ‘run if_netconsole start_netconsole’
setenv if_netconsole ‘ping $serverip’
ipaddr=
serverip=
setenv arcNumber ‘3542’
setenv usb_rootfstype ‘ext3’
setenv bootcmd ‘usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset’



Edited 1 time(s). Last edit at 05/28/2014 08:32PM by Looker.
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 28, 2014 08:52PM
@Looker

You got it. The first = means "asign the entire string that appears after the = symbol to mtdparts variable". Any = symbol that appears in the string means a literal =, not an assignment.

Regarding ippaddr and serverip, you can keep them like this (later when you get to know how to use them, they should be changed to conform to your local network):
ipaddr=192.168.0.221
serverip=192.168.0.220

To boot into Debian, you can can prepare a Debian rootfs on USB stick. See this thread for the instruction to do that:
http://forum.doozan.com/read.php?2,12096

The latest rootfs is Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (15 April 2014). So scroll down to that section and follow the instruction to download, format,and extract. You will need another Linux computer to prepare rootfs. If you don't have one then google Linux Live CD to download and preprare a CD to run it on your PC/Mac.

If you want to boot ArchLinux then you can get a simlilar rootfs at Arch site.

To summarize:

- Prepare the rootfs on a new USB stick
- Insert the USB rootfs to the Pogo, power up
- Interrupt serial console
- Enter the set of good U-Boot envs
- At serial console prompt, execute boot command:
u-boot>> boot

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 28, 2014 10:17PM
Bodhi,

Can I use a USB stick from another working pogo E02 with Archlinux up and working great or does it need to be an stick dedicated to this box?

Thank you
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
May 28, 2014 10:44PM
Looker,

> Can I use a USB stick from another working pogo
> E02 with Archlinux up and working great or does it
> need to be an stick dedicated to this box?
>
> Thank you

That stick can be used on any Pogo E02. Settings need to change or match:

1. MAC address needs to macth this PogoE02:
- look in Arch network interfaces, if it is defined (I recall it is)
- that MAC address should be the same as this Pogo U-Boot env ethaddr

2. If Static IP is defined, then change it to other IP for this Pogo.

3. The rootfs file system needs to be Ext3 (I believe it is Ext3 using Arch official installation procedure)

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 05/28/2014 10:47PM by bodhi.
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
June 15, 2014 11:44AM
Hi Bodhi,

I.m having some issues when entering the lon environment strings from your list, e.g. the following environment variables eithe rgive me "syntax error" or just a ">" prompt without "u-boot>>". Do you see an error in any of these?

Thanks

setenv 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’

setenv 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’

setenv 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’

setenv 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_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’
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
June 15, 2014 11:53PM
Looker,

You've missed the single quote at the end:
setenv 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";

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
July 13, 2014 03:47PM
Bodhi,

I finally got all the lines typed in and when I try to boot from a known working Archlinux RootFS I get the following:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Unknown command '‘setenv' - try 'help'
incorrect device type in ‘nand0=orion_nand’
Error initializing mtdparts!
## Error: "usb_init" not defined
Unknown command '‘setenv' - try 'help'
** Invalid boot device, use `dev[:part]' **
** Invalid boot device, use `dev[:part]' **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
incorrect device type in ‘nand0=orion_nand’
incorrect device type in ‘nand0=orion_nand’
resetting ...

Here is my printenv:

baudrate=115200
bootargs=root=/dev/nfs nfsroot=: ip=::::::off
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=5
console=‘ttyS0,115200’
ethact=egiga0
ethaddr=00:25:31:04:88:1D
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
if_netconsole=ping $serverip
led_error=‘orange blinking’
led_exit=‘green off’
led_init=‘green blinking’
machid=dd6
mainlineLinux=‘yes’
mtdids=‘nand0=orion_nand’
mtdparts=‘mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)’
partition=‘nand0,2’
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
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
rescue_installed=‘0’
rescue_set_bootargs=‘setenv bootargs console=‘ttyS0,115200’ ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs ‘mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)’ €™
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
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
ubifs_mtd=‘3’
ubifs_set_bootargs=‘setenv bootargs console=‘ttyS0,115200’ ubi.mtd=‘3’ root=ubi0:rootfs rootfstype=ubifs ‘mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)’ €™
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
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=‘0:1’
usb_root=‘/dev/sda1’
usb_rootdelay=’10’
usb_rootfstype=ext3
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_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_scan_list=1 2 3 4
usb_set_bootargs=‘setenv bootargs console=‘ttyS0,115200’ root=‘/dev/sda1’ rootdelay=’10’ rootfstype=ext3 ‘mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)’ €™

Environment size: 2817/131068 bytes


Any idea what I didn't do correctly?

Thanks
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
July 13, 2014 10:20PM
Looker,

Some of your u-boot envs have incorrect syntax:

correct:
usb_scan_list=1 2 3 4

incorrect:
console=‘ttyS0,115200’

When you list the envs with printenv, there should be no single quote. For example, the correct setting for the variable console above is:
console=ttyS0,115200

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help, Pogogplug E02 , No LED,serial cable connected ,what next?
July 14, 2014 11:38AM
Bodhi,

Thank you so very much for all your help! Everything is working great.

Don't know how those single quotes ended up in there, originally I pasted them from a saved text file, there must have been some hidden markup codes in there. When I typed it by hand everything entered correctly. Anyway thanks again.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: