Welcome! Log In Create A New Profile

Advanced

correct uEnv.txt for recovering pogoplug v4 mobile environment

Posted by pengu 
Forum List Message List New Topic
pengu
correct uEnv.txt for recovering pogoplug v4 mobile environment
June 22, 2015 05:25PM
I've successfully updated U-Boot on it and I'm using bodhi's rootfs.
A fiew days ago I noticed that I have a limited environment so I changed it via fw_setenv like on other devices but it doesn't came up again.

atm I couldn't use serial connection because there are no pins to plug my cable on it.
some weeks ago I tried to change this but it wasn't stable and now unusable.
I've created a uEnv.txt and put it where it should be stored but no luck ;-(
Reply Quote
bodhi
Re: correct uEnv.txt for recovering pogoplug v4 mobile environment
June 23, 2015 12:18AM
pengu,

See the u-boot installation thread. The uboot.2014.07-tld-2.environment.bodhi.tar tarball has the envs in text format.

Quote

B. Flashing default u-boot envs image

This section describes how to flash a default set of u-boot envs. The bootcmd in this setup is set to boot from USB, MMC, and SATA in this order (USB will be tried first, if unsuccessful then MMC will be tried, and then if unsuccessfull SATA will be tried).

NOTE: this default envs are for non-FDT kernel. After finishing this section, please see section C below for further modification if booting FDT kernel.

a. Download the default u-boot envs at Dropbox:

uboot.2014.07-tld-2.environment.bodhi.tar
md5
0671567388d3553610a8b1bef63945e0

This tarball includes 2 files:

uboot.2014.07-tld-2.environment.img (the default envs image to be flashed)
uboot.2014.07-tld-2.environment (the content of the default envs in text format)

Copy this file to uEnv.txt 
cp -a uboot.2014.07-tld-2.environment /boot/uEnv.txt

annd edit this file to adjust envs that are specific to the Pogo Mobile, and your own network.

This default envs set will boot the rootfs that has the DTB embedded inside uImage as described in section 4b in the kernel thread:

Quote

4b. Boot with DTB file embedded in the kernel image (no U-Boot envs changes are needed if your system already booting on USB or HDD)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
pengu
Re: correct uEnv.txt for recovering pogoplug v4 mobile environment
June 26, 2015 02:56PM
thanks a lot but this didn't help

I had a similar U-Boot config working for weeks.
Like on my other kirkwood devices with your U-Boot I wanted to load the dtb seperately.
I also noticed that I couldn't boot kernels > 3.18.5.

The only things I have changed in the uEnv.txt is the network part for netconsole.
For testing, I just pinged the device when plugging in but no response.
Perhaps the error in my U-Boot env prevents the uEnv.txt from loading :-(

This is also shown by the LED:
After plugging it starts to blink for 33 seconds, then it turns red.

think I had to resolder the pins but now this is more difficult as first
Reply Quote
bodhi
Re: correct uEnv.txt for recovering pogoplug v4 mobile environment
June 27, 2015 01:00AM
pengu,

> The only things I have changed in the uEnv.txt is
> the network part for netconsole.

Netconsole is not scriptable in uEnv.txt, atm. I plan to revise the default envs so that it can be.


> This is also shown by the LED:
> After plugging it starts to blink for 33 seconds,
> then it turns red.

This indicated that the kernel files have not been loaded successfully.

I would try the same steps I've suggested above using uEnv.txt again with a tested rootfs (created from scratch).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
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: