Pogoplug Mobile/V4 uboot-env tools

[bodhi]

Hi guys,

I've acquired a used Pogoplug Mobile and installed ALARM. Pretty decent for the price . My question:
I've installed uboot-env tools with
pacman -S uboot-env

Now when I looked at /etc/fw_env.config, I am not sure what to put in for the MTD parameters?

$this->bbcode_second_pass_code('', '# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
#/dev/mtd2 0x0000 0x20000 0x20000

# dockstar:
# /dev/mtd0 0xc0000 0x20000 0x20000

# iomega iconnect
# /dev/mtd0 0xa0000 0x20000 0x20000')

Thanks!

[moonman]

Try them one by one and then issue fw_printenv. If you get an error move on to the next one. I personally don't know what which you need to use.

[bodhi]

@moonman,
I've uncommented one by one, both gave me error! the Dockstar settings gave "Bad CRC" error, and the iomega gave the list of envs, but also gave me "uncorrectable error " in dmesg. So I figured neither is usable.

@kimelich, could you give us some pointers?

[bodhi]

Anyone with Pogoplug V4 or Mobile has tried to use fw_printenv ?

[sambul13]

Are you able to boot the device? What dmesg and cat /proc/mtd, or similar device FS commands post? Take it from there.

[bodhi]

Thanks for reponsding guys!

I looked at these outputs and comparing them with the Dockstar. But one crucial piece of information missing is Device Offset. We know what the value for Dockstar (0xc0000), but I could not find it on the Dockstar various places such as dmesg, /proc/mtd, or /proc/partitions, so I don't have a way to deduce what the value should be for the Pogoplug V4/Mobile!

[moonman]

@sambul13 It is not possible to get it from /proc/mtd as it only shows the partition arrangement.

@bodhi. I looked at the ppv4 installation script:

$this->bbcode_second_pass_code('', 'echo "# Erasing mtd0 @ 0x100000 for 4 erase blocks (new U-Boot location)"
/usr/sbin/flash_erase /dev/mtd0 0x100000 4
')

I dunno if the offset for the environment is this.

[WarheadsSE]

That is not the location of the environment, that is the location of the new uboot itself.

[bodhi]

Thanks, I've realized that, too. It basically erases and writes the entire uboot image. But we don't know how the image was structured. What is the size of the envs part?

[moonman]

Yeah, that's what I thought as well. Though Jeff's installation script has the address for uboot environment, the one for ppv4 flashes uboot and environment at once as a single image?