my pogoplug pink cannot update uboot

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

my pogoplug pink cannot update uboot

Postby ffan » Sun Jan 06, 2013 7:10 am

hi guys, i am new to arch linux arm and i need your help. I bought two pogoplug-e02. first pinkpogo is perfect fine by following the instructions, and i even make the /boot partition and move / to second ext4 partition. but the second pinkpogo i have problems. i searched internet extensively but no remedy found. (i do not know how to summarize the problems)

i followed the instructions exactly but it does not boot from USB drive.(no fancy separate /boot and ext4 / this time) with USB hard drive plugged in, it does not boot at all. then i unplugged USB drive, it boot up ok, and i notice that when i login, it was still root/ceadmin, not root/root. so i did this:

mount / -o remount,rw
passwd
mount / -o remount,ro

i successfully changed root password, now it is root/root, but the prompt sigh is still $ not #.
i think root should have # not $.

--------------------------------------------------------------------------------------------------------------------
Pogoplug:/usr/sbin$ mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (ro)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
Pogoplug:/usr/sbin$ mount / -o remount,rw
Pogoplug:/usr/sbin$ mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
Pogoplug:/usr/sbin$ mount / -o remount,ro
Pogoplug:/usr/sbin$ mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (ro)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
Pogoplug:/usr/sbin$
--------------------------------------------------------------------------------------------------------------------


then i re-run these steps:

wget http://jeff.doozan.com/debian/uboot/ins ... ot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh



--------------------------------------------------------------------------------------------------------------------
Pogoplug:~$ ./install_uboot_mtd0.sh


!!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
Seagate Dockstar
Seagate GoFlex Net
Seagate GoFlex Home
Pogoplug v1
Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5 100% |*******************************| 1133 --:--:-- ETA
## Valid uBoot detected: [pinkpogo davygravy-2012-02-20-current]
## The newest uBoot is already installed on mtd0.


You are already running the latest uBoot.
Your current uBoot environment should be reasonable. However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] y

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************| 32 --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment 100% |*******************************| 128k --:--:-- ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************| 32 --:--:-- ETA

# uBoot installation has completed successfully.
Pogoplug:~$
--------------------------------------------------------------------------------------------------------------------


i tried 'rw' root and also 'ro' root, but it always come back login as 'pogoplug' not 'alarm'.

here are more ino:

--------------------------------------------------------------------------------------------------------------------
Pogoplug:/usr/sbin$ ./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_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
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:03:07:2D
arcNumber=2097
Pogoplug:/usr/sbin$
--------------------------------------------------------------------------------------------------------------------

and i also notice the mac address changed, i forgot at what point. now the mac address is not same as the one on the sticker at the bottom of the pogoplug. it is 00:50:43:00:02:02 now.

pls help. thanks.
ffan
 
Posts: 2
Joined: Sun Jan 06, 2013 6:31 am

Re: my pogoplug pink cannot update uboot

Postby moonman » Sun Jan 06, 2013 3:24 pm

Looks like your u-Boot installed fine. Get the hdd from the pogoplug that works and try to boot from it on the pogoplug that you think is not working. If it boots fine then it's your second hdd that doesn't play nice with the pogoplug (try reinstalling from scratch and/or change the hdd completely). I would also get netconsole working to see what's going on at boot (instructions how to get it to work in this thread: viewtopic.php?f=18&t=3355)
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: my pogoplug pink cannot update uboot

Postby WarheadsSE » Sun Jan 06, 2013 4:01 pm

Setting the mac back is simple:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_setenv ethaddr [mac from bottom]')
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: my pogoplug pink cannot update uboot

Postby ffan » Mon Jan 07, 2013 2:30 am

thanks for your replies. i tried USB HD from 1st pogopink, and another USB HD, and another 2 USB memory sticks, they were all failed to boot. and i suspect pogopink did not save my uboot updates properly, since it is still "pogoplug" not "alarm" at prompt.
ffan
 
Posts: 2
Joined: Sun Jan 06, 2013 6:31 am

Re: my pogoplug pink cannot update uboot

Postby WarheadsSE » Mon Jan 07, 2013 3:43 pm

The kirkwood line is configured to boot to the stock environment if no suitable rootfs & uImage was found. You might want to try setting up netconsole.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 253 guests