Welcome! Log In Create A New Profile

Advanced

Pogoplug pink Boot loop Problems

Posted by droidbox 
Pogoplug pink Boot loop Problems
December 15, 2014 03:23PM
Hi everyone, after some hacks on the uboot i have the following problem:

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
## Error: "force_rescue_bootcmd" not defined
## Error: "ubifs_bootcmd" not defined
## Error: "usb_bootcmd" not defined
stopping USB..
## Error: "rescue_bootcmd" not defined
## Error: "pogo_bootcmd" not defined
resetting ...
How can i fix it?

droidbox



Edited 1 time(s). Last edit at 12/15/2014 03:25PM by droidbox.
Re: Pogoplug pink Boot loop Problems
December 15, 2014 03:30PM
u-boot>> printenv 
arcNumber=3542
baudrate=115200
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=02:50:43:e6:fc:df
if_netconsole=ping $serverip
ipaddr=192.168.178.61
machid=dd6
preboot=run if_netconsole start_netconsole
serverip=192.168.178.24
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start; if ext2load usb 0:1 0x800000 /boot/uImage; then setenv usb_device 0:1; setenv usb_root /dev/sda1; elif ext2load usb 1:1 0x800000 /boot/uImage; then setenv usb_device 1:1; setenv usb_root /dev/sdb1; elif ext2load usb 2:1 0x800000 /boot/uImage; then setenv usb_device 2:1; setenv usb_root /dev/sdc1; elif ext2load usb 3:1 0x800000 /boot/uImage; then setenv usb_device 3:1;setenv usb_root /dev/sdd1;fi;
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=sda3
usb_scan_2=usb=1:1 dev=sdb3
usb_scan_3=usb=2:1 dev=sdc3
usb_scan_4=usb=3:1 dev=sdd3

Environment size: 1577/131068 bytes

Re: Pogoplug pink Boot loop Problems
December 15, 2014 05:18PM
Take a look at this post:
http://forum.doozan.com/read.php?3,16148,16148#msg-16148

And use it as a guide to fix your missing envs,

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug pink Boot loop Problems
December 16, 2014 05:35AM
Hey bodi,

thanks for your answer. I read the guide, but it is for a Pogo V4/Mobile Device.
I have a Pogoplug E02.

It is right?

droidbox
Re: Pogoplug pink Boot loop Problems
December 16, 2014 03:04PM
droidbox Wrote:
-------------------------------------------------------
> Hey bodi,
>
> thanks for your answer. I read the guide, but it
> is for a Pogo V4/Mobile Device.
> I have a Pogoplug E02.
>
> It is right?
>
> droidbox

Yes. Just use it as a guide for comparing bootcmd. Pogo V4 has different mtdparts, archNumber, machid (so don't use that). But booting USB uses the same envs commands. If you'd like, fix them and post your envs here and I'll double check.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug pink Boot loop Problems
December 16, 2014 03:25PM
Nice. The pogoplug runs.

Thank you very much.

I take a new threath with a bad block error on another plug.

droidbox
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: