Latest uBoot for Pogoplug Mobile?

I just picked up 4 Pogoplug Mobiles from Ebay for a little less than $6 each shipped.

What's the latest and greatest uBoot for the Pogoplug Mobile?

Would it be davygravy's posted here - http://forum.doozan.com/read.php?3,7477? Is there a nice simple script to install the uBoot with the appropriate env variables? If not, why not? Just curious since a script makes it so much simpler and less error prone.

Thanks

gray

@gray,

This is how you can install davygravy's U-boot build (I think this is at the moment the one to use, for simplicity and expediency).
http://forum.doozan.com/read.php?2,11663

And you can also use ebbes's build (newer):
http://forum.doozan.com/read.php?3,14697,15533#msg-15533

or

malc's build (variant of stock):
http://forum.doozan.com/read.php?3,15091

And yes, there is no script. It was not implemented by anybody because no final U-boot build has been provided. Jeff's script does not cover the Pogo V4/Mobile since it was developed before its time.

Also as mentioned in a diffrent thread, I will release the Pogo V4/Mobile 2014.07 U-boot image within a next couple weeks.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/10/2014 12:30PM by bodhi.

Hi @bodhi,

Thanks for the reply and info regarding the various options I have. I'm in no rush and looking for something a little more officially supported, so I'll just wait for your release.

Here are the features I'm looking for, hopefully all supported with the new uBoot.

- SD Card Boot (not for me personally, but people always ask)
- Netconsole
- NAND/Internal Flash boot (I'm looking at running OpenWRT on the internal flash if possible)
- Ability to boot stock Pogoplug OS (for downloading, formatting and reinstallation of rootfs on a new/corrupted USB drive or I guess for simply going back to running the stock Pogoplug service).

Gray,

The last option is possible, but no procedure/setup is avalable for Debian. I suspect U-boot version has little or nothing to do with it (any version will work). But I am not interested in booting Pogo OS so never looked into this setup.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I went ahead and successfully installed davygravy's uboot using @bodhi instructions this weekend on one of my PP mobile.

Now I'm trying to figure out how to boot back into the default Pogoplug OS. Not sure what the proper bootcmd setting should be. Any help is appreciated. Thanks

Another quick question...

I was able to successfully boot Debian from my SD Card, using the rootfs provided by @bodhi in this thread (http://forum.doozan.com/read.php?2,12096), however, I'm not able to boot ALARM using the rootfs provided on the ALARM site.

Any ideas what's going on? Anything special I need to do to get ALARM working from SDCard? Thanks

Gray,

Verify u-boot bootm and bootargs. They are slighly different between Debian and Arch.

bootm:

bootcmd_mmc=mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd
bootcmd=run bootcmd_usb; bootm 0x00800000 0x01100000

Is your mmc bootm similar to the above? For ALARM, bootm needs only uImage (there is no uInitrd), so bootm 0x00800000 has only one argument.

bootargs:

usb_set_bootargs=setenv bootargs console=$console root=???

The root argument needs the specific drive letter of the SD card (you can't use label root=LABEL=rootfs like you would with Debian).

If you'd like, print your u-boot envs and post it here and I'll take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the reply as always.

Below is my uboot env. Looks like the mmc_boot variable has some logic to handle the existent of the /boot/uInitrd file or not. Also, can I assume that the default location of /boot/uImage is okay as long as the file is actually there?

Ideally, it would be nice to be able to boot either ALARM or DEBIAN without modifying the uboot env.

arcNumber=3960
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run mmc_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:AA:AA:AA
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
ipaddr=192.168.100.115
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_bootcmd=mmc init; mmc init; run mmc_set_bootargs; run mmc_boot
mmc_root=/dev/mmcblk0p1
mmc_rootfstype=ext3
mmc_set_bootargs=setenv bootargs console=$console root=$mmc_root rootfstype=$mmc_rootfstype $mtdparts
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ncip=192.168.100.160
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=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.100.160
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
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=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
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_init=run usb scan
usb_root=/dev/sda1
usb_rootdelay=10
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=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_rootfstype=ext2

Hi Gray,

It does look sane to me. I think it's time to watch netconsole/serial console boot log! I can only think off the only thing that might have happened: perhaps the drive letter of the mmc was somehow mis-assigned to something other than mmcblk0p1.

Yes, ext2load mmc 0:1 0x00800000 /boot/uImage would load correctly if the SD card is plugged in. And your u-boot env mmc_boot is handling both Debian and Arch automatically.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the confirmation.

Netconsole doesn't tell me much, kernel loads and that's about it.

I already had plans on soldering in a serial connection anyways, so I guess once I do that, I can figure out what's going on.

Thanks again for the help. Definitely learning a lot about uBoot and the linux boot up process lately.