Re: Failsafe booting to alternate linux image/fs

[Brendan Simon (eTRIX)]

I came across the "Boot Count Limit" feature in the U-Boot wiki, and it
looks like it will do exactly what I want.

https://www.denx.de/wiki/view/DULG/UBootBootCountLimit


However, it also states that the "feature is available only for MPC8xx,
MPC82xx and MPC5200 Power Architecture® processors"

Is that accurate?  Is it not available for ARM processors (e.g. A9 CPU
system within Xilinx Zynq 7000 series SoCs) ?

Thanks, Brendan,

--

On 28/5/20 5:14 pm, Brendan Simon (eTRIX) wrote:
> Hi,
>
> Before I embark on my own implementation of a failsafe bootloading
> process from my embedded system (Xilinx Zynq board booting from SD
> Card), I thought I'd quickly ask the experts if there are any standard
> implementations in u-boot.
>
> The current u-boot being used is from 2015.  It probably needs to be
> updated (for various reasons).  It is loaded from the first partition
> (64MB/FAT32) of an SD Card as part of a file called `BOOT.BIN`.  The
> `Env.txt` file contains settings for two linux root systems (including
> kernel and dtb) on separate partitions (ext4/1GB).  The first
> statement in `Env.txt` has a `part=2` or `part=3` to indicate, which
> partition to boot from (load kernel and set cmdline for rootfs, etc).
>
> My simple approach was to store a env var for the number of reboot
> attempts.  On every boot attempt, the env var would be incremented. 
> If linux booted successfully it would set the env var to zero (I
> believe there are linux tools to do that).  If linux didn't boot
> successfully, eventually the reboot count env var would reach some
> value, where the alternative partition would be selected as an attempt
> to get something booting and up and running.
>
> NOTE: the devices are remote and need to be up as much as possible so
> they can be monitored/managed.
>
> *Does this type of functionality exist already in u-boot?*  I'm
> guessing/hoping it does (and hope to use it directly or leverage the
> features that make sense) rather than reinventing the wheel.
>
> *Where is the best place to go to get information/documentation on this?*
>
> Finally, I'm looking at migrating to EMMC, maybe with a golden image
> for failsafe use, and two partitions for current filesystem and
> next/upgrade filesystem.
>
> *Is there any documentation that might be a useful in this use case?*
>
> Thanks, Brendan.
>

Failsafe booting to alternate linux image/fs

[Brendan Simon (eTRIX)]

Hi,

Before I embark on my own implementation of a failsafe bootloading
process from my embedded system (Xilinx Zynq board booting from SD
Card), I thought I'd quickly ask the experts if there are any standard
implementations in u-boot.

The current u-boot being used is from 2015.  It probably needs to be
updated (for various reasons).  It is loaded from the first partition
(64MB/FAT32) of an SD Card as part of a file called `BOOT.BIN`.  The
`Env.txt` file contains settings for two linux root systems (including
kernel and dtb) on separate partitions (ext4/1GB).  The first statement
in `Env.txt` has a `part=2` or `part=3` to indicate, which partition to
boot from (load kernel and set cmdline for rootfs, etc).

My simple approach was to store a env var for the number of reboot
attempts.  On every boot attempt, the env var would be incremented.  If
linux booted successfully it would set the env var to zero (I believe
there are linux tools to do that).  If linux didn't boot successfully,
eventually the reboot count env var would reach some value, where the
alternative partition would be selected as an attempt to get something
booting and up and running.

NOTE: the devices are remote and need to be up as much as possible so
they can be monitored/managed.

*Does this type of functionality exist already in u-boot?*  I'm
guessing/hoping it does (and hope to use it directly or leverage the
features that make sense) rather than reinventing the wheel.

*Where is the best place to go to get information/documentation on this?*

Finally, I'm looking at migrating to EMMC, maybe with a golden image for
failsafe use, and two partitions for current filesystem and next/upgrade
filesystem.

*Is there any documentation that might be a useful in this use case?*

Thanks, Brendan.

Failsafe booting to alternate linux image/fs

[Brendan Simon (eTRIX)]

Hi,

Before I embark on my own implementation of a failsafe bootloading
process from my embedded system (Xilinx Zynq board booting from SD
Card), I thought I'd quickly ask the experts if there are any standard
implementations in u-boot.

The current u-boot being used is from 2015.  It probably needs to be
updated (for various reasons).  It is loaded from the first partition
(64MB/FAT32) of an SD Card as part of a file called `BOOT.BIN`.  The
`Env.txt` file contains settings for two linux root systems (including
kernel and dtb) on separate partitions (ext4/1GB).  The first statement
in `Env.txt` has a `part=2` or `part=3` to indicate, which partition to
boot from (load kernel and set cmdline for rootfs, etc).

My simple approach was to store a env var for the number of reboot
attempts.  On every boot attempt, the env var would be incremented.  If
linux booted successfully it would set the env var to zero (I believe
there are linux tools to do that).  If linux didn't boot successfully,
eventually the reboot count env var would reach some value, where the
alternative partition would be selected as an attempt to get something
booting and up and running.

NOTE: the devices are remote and need to be up as much as possible so
they can be monitored/managed.

*Does this type of functionality exist already in u-boot?*  I'm
guessing/hoping it does (and hope to use it directly or leverage the
features that make sense) rather than reinventing the wheel.

*Where is the best place to go to get information/documentation on this?*

Finally, I'm looking at migrating to EMMC, maybe with a golden image for
failsafe use, and two partitions for current filesystem and next/upgrade
filesystem.

*Is there any documentation that might be a useful in this use case?*

Thanks, Brendan.

[U-Boot] [PATCH] arm: ls102xa: Fix RGMII phy-connection-type FDT fixup

[Brendan Shanks]

In ft_fixup_enet_phy_connect_type(), use strlen() instead of sizeof() on
the pointer result of phy_string_for_interface().
sizeof() was returning the size of the pointer (4 bytes), resulting in
the phy-connection-type being set to "rgmi" rather than "rgmii-id".

Signed-off-by: Brendan Shanks 
Cc: York Sun 
---
 arch/arm/cpu/armv7/ls102xa/fdt.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/cpu/armv7/ls102xa/fdt.c b/arch/arm/cpu/armv7/ls102xa/fdt.c
index 6c3caf8..8bf9c42 100644
--- a/arch/arm/cpu/armv7/ls102xa/fdt.c
+++ b/arch/arm/cpu/armv7/ls102xa/fdt.c
@@ -64,8 +64,8 @@ void ft_fixup_enet_phy_connect_type(void *fdt)
do_fixup_by_path(fdt, enet_path, "phy-connection-type",
 phy_string_for_interface(
 PHY_INTERFACE_MODE_RGMII_ID),
-sizeof(phy_string_for_interface(
-PHY_INTERFACE_MODE_RGMII_ID)),
+strlen(phy_string_for_interface(
+PHY_INTERFACE_MODE_RGMII_ID)) + 1,
 1);
}
 }
-- 
2.7.4

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] How to validate ext4load file size (not null)?

[brendan]

I have stored multiple device trees in my emmc (ext4 formatted) partition
and I want to load a certain device tree file from emmc, but if this fails
(i.e. the device tree file doesn't exist) it should default to a device tree
that is stored in memory. 

For example if I run this: 

I get a return of: if test  != null; then run ; else run ; fi

I have seen the 
 command however using the example above, if I did 
 it does not set the filename environment variable therefore I cannot check
the size as  always returns true.  

I have tried other if statements such as:
 and they have not given me the true/false check that I am after.  

Does uBoot offer functionality for what I am after?  or should I be
approaching it with a different method. 

Thanks 




--
View this message in context: 
http://u-boot.10912.n7.nabble.com/How-to-validate-ext4load-file-size-not-null-tp282782.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] How to validate ext4load file size (not null)?

[brendan]

I have stored multiple device trees in my emmc (ext4 formatted) partition and
I want to load a certain device tree file from emmc, but if this fails (i.e.
the device tree file doesn't exist) it should default to a device tree that
is stored in memory. 

For example if I run this: 


I get a return of:


Is there a way I can parse this return from ext4load to check if the size is
null or not null?

The aim (in pseudo code) is 

Does uBoot offer functionality for what I am after?  or should I be
approaching it with a different method. 

Thanks





--
View this message in context: 
http://u-boot.10912.n7.nabble.com/How-to-validate-ext4load-file-size-not-null-tp282781.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Assigning u-boot environment variables from memory

[brendan]

I am storing some information regarding my board within EEPROM (in memory
after I use the >eeprom read command) and I was wondering if it was possible
for me to somehow read from memory and store the values into an environment
variable.

I have done a search but could not find anything of relevance.  

Thanks



--
View this message in context: 
http://u-boot.10912.n7.nabble.com/Assigning-u-boot-environment-variables-from-memory-tp281788.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] How to test watchdog timer values and ensuring it is working as intended

[brendan]

Hello,

I am using an Freescale/nxp mx6solo and I want to test that the watchdog
timer is working as intended.  I have enabled it on my board and have
confirmed it during boot

> U-Boot SPL 2015.04-g0f11429-dirty (Jan 18 2017 - 05:42:24)
> 
> Part number: VSM-SOLO-102
> Assembly: AS151004858
> Date of production: 2016 Feb 08
> NAND : 512 MiB
> 
> 
> U-Boot 2015.04-g0f11429-dirty (Jan 18 2017 - 05:42:24)
> 
> CPU:   Freescale i.MX6SOLO rev1.2 at 792 MHz
> CPU:   Temperature 53 C
> Reset cause: POR
> Board: Variscite VAR-SOM-MX6 SOM-Solo 792 MHz
>
*
> Watchdog enabled
*
> I2C:   ready
> DRAM:  1 GiB
> NAND:  512 MiB
> MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> auto-detected panel VAR-WVGA MX6CB-R
> Display: VAR-WVGA MX6CB-R (800x480)
> UBI init error 22
> Error: no valid bmp image at 1810
> In:serial
> Out:   serial
> Err:   serial
> eMMC:  3.5 GiB
> Net:   using phy at 7
> FEC [PRIME]
> Normal Boot
> Hit any key to stop autoboot:  0 

I have just initialised the watchdog and using the provided timeout values
in /drivers/watchdog/imx_watchdog.c which are 


> void hw_watchdog_init(void)
> {
> struct watchdog_regs *wdog = (struct watchdog_regs
> *)WDOG1_BASE_ADDR;
> u16 timeout;
> 
> /*
>  * The timer watchdog can be set between
>  * 0.5 and 128 Seconds. If not defined
>  * in configuration file, sets 128 Seconds
>  */
> #ifndef CONFIG_WATCHDOG_TIMEOUT_MSECS
> #define CONFIG_WATCHDOG_TIMEOUT_MSECS 128000
> #endif
> timeout = (CONFIG_WATCHDOG_TIMEOUT_MSECS / 500) - 1;
> writew(WCR_WDZST | WCR_WDBG | WCR_WDE | WCR_WDT | WCR_SRS |
> SET_WCR_WT(timeout), >wcr);
> hw_watchdog_reset();
> }
> #endif

I want to confirm that this is working so I was wondering how I am able to
test that the system is not kicking the watchdog.

Thanks



--
View this message in context: 
http://u-boot.10912.n7.nabble.com/How-to-test-watchdog-timer-values-and-ensuring-it-is-working-as-intended-tp279083.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Enabling Watchdog Service on Variscite VAR-SOM-MX6 Solo

[Brendan Ta]

Hello,

I am looking to enable the Watchdog Timer on my Freescale iMX6 board and 
I am following the documentation supplied by NXP which states as follows:


---
The following sequence should be performed for WDOG initialization.
• PDE bit of Watchdog Miscellaneous Control Register (WDOG_WMCR) should 
be cleared to disable the power down counter.
• WT field of Watchdog Control Register (WDOG_WCR) should be programmed 
for sufficient timeout value.
• WDOG should be enabled by setting WDE bit of Watchdog Control Register 
(WDOG_WCR) so that the timeout counter loads the WT field value of 
Watchdog Control Register (WDOG_WCR) and starts counting

---

I've noticed that in /drivers/watchdog/imx_watchdog.c there is no 
support for the WDOG_WMCR.


Is there another way to initialise and enable the Watchdog Timer on an 
iMX board?  I am new to this and just following the reference manual as 
supplied by NXP 
(http://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6SDLRM.pdf)


Any help would be greatly appreciated.

Regards,
Brendan


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Enable redundant u-boot environment for iMX6 (Yocto)

[brendan]

Hello,

I'm looking to enable a redundancy enabled "ping-pong" u-boot environment
for my iMX6 (VAR-SOM-MX6 CPU: NXP/Freescale iMX6) to ensure that if there
was system failure that there will always be a CRC checked and valid
environment available in NAND flash.  I have read the documentation and
noticed that there is the available functionality of CONFIG_ENV_ADDR_REDUND
and CONFIG_ENV_SIZE_REDUND.

My questions are; how do I determine my redundant address and size?  Should
they just match my original defines?  I am using a custom mtd partition
sizing which I have configured by the use of a sw-description file (using
swupdate to handle the update process), will there be any issues that can be
foreseen?

Also, because I am using Yocto (I know this is outside the scope of u-boot)
would it be wise to add a patch or append file within Yocto?  or simply host
this in a separate repository?

Any help would be greatly appreciated, I cannot find any in depth
documentation relating to this so I am looking for any resources available.

Regards,
Brendan



--
View this message in context: 
http://u-boot.10912.n7.nabble.com/Enable-redundant-u-boot-environment-for-iMX6-Yocto-tp276498.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] VAR-SOM-MX6 - Boot Count Limit support?

[brendan]

Hello,

I have a VAR-SOM-MX6 with the following details:

Board: Variscite VAR_SOM_MX6 SOM-Solo
SOC_FAMILY = "mx6:mx6q:mx6dl"
PREFERRED_PROVIDER_virtual/kernel_var-som-mx6 ?= "linux-variscite"
PREFERRED_VERSION_linux-imx_mx6 = "4.1.15"

and the following u-boot details:

U-Boot SPL 2013.10-00027-g58782ac (Mar 09 2015 - 13:33:44)
i.MX6SOLO SOC DDR EEPROM configuration
Part number: VSM-SOLO-102
Assembly: AS151004858
Date: 2016 Feb 08
Ram size 1024
Boot Device: NAND
NAND: 512 MiB


U-Boot 2013.10-00027-g58782ac (Mar 09 2015 - 13:33:44)

CPU:   Freescale i.MX6SOLO rev1.2 at 792 MHz
CPU:   Temperature 51 C, calibration data: 0x5744e269
Reset cause: POR
Board: Variscite VAR_SOM_MX6 SOM-Solo
I2C:   ready
DRAM:  1 GiB
NAND:  512 MiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
In:serial
Out:   serial
Err:   serial
Board: Variscite VAR_SOM_MX6 SOM-Solo
Net:   using phy at 7


I am using Yocto to create my images (.swu) to update my board through 
swupdate   .  The update
process and loading process via NFS and NAND causes no issues. 

I am trying to implement a system whereby if the board fails to boot, it
should boot to a recovery configuration where the user is presented with the
swupdate landing page to allow for an image (.swu) upload to update or boot
to a recovery .img (uImage, .dtb, rootfs stored on MMC or NAND). 

I have read about uboot's  Boot Count Limit
   which is along the
lines of what I would like to implement i.e. after x failed boot attempts
use an alternate boot action.  However this functionality is not supported
by my board.  

I am new to this and was wondering if anyone could shed any light on what I
need to look at or how I can somehow implement the Boot Count Limit
functionality or similar.  

Thanks for your help.






--
View this message in context: 
http://u-boot.10912.n7.nabble.com/VAR-SOM-MX6-Boot-Count-Limit-support-tp276107.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] u-boot retries with fallback to other images

[Brendan Simon (eTRIX)]

Hi Wolfgang,

On 7/12/2015 5:23 PM, Wolfgang Denk wrote:
> Dear Brendan,
>
> In message <5663b74e.7000...@etrix.com.au> you wrote:
>> Is there any documentation or u-boot support for having a list of boot
>> images to try, starting with the first in the list, trying 1, 2 or 3
>> times, then trying the next in the list.
>>
>> e.g. boot kernel at mmcblk0p3, then mmcblk0p2, then mmcblk1p2, then
>> tftp/nfs last resort fallback ?
>> or
>> boot off partition 3 of eMMC, then partition2 of eMMC, then
>> partition 2 of SD card, then tftp/nfs ?
> Define a set of boot commands, say bootcmd1, bootcmd2, ...
> and then simply do
>
>   run bootcmd1; run bootcmd2; ...
>
> The furst one that succeeds will not return.
>
> Note that the key problem with such a simplistic approach is that it
> will not help you in case an image looks OK, but hangs during boot -
> in that case, you need a watchdow and support for the bootcount
> feature.
>
> Best regards,
> Wolfgang Denk

Yes, the watchdog and bootcount feature is the advanced stuff I'm
looking for.
I would think this has been implemented numerous times, and I didn't
want to reinvent the wheel if there was some commonly used
infrastructure to support this.
If software does boot, then at some stage would set a u-boot variable to
say everything booted ok, so that it can be used again on next boot.

My use case is not that uncommon -- lots of embedded devices installed
in remote locations that are not easily accessible, but require remote
monitor and software updates.

Is there anything that is "standard" in u-boot to support this?
Or any work that is published that has attempted this?

Thanks,
Brendan.

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] fw_env.config settings for Digilent ZedBoard (Zynq 7020 Soc)

[Brendan Simon (eTRIX)]

Hi.  see inline comments below ...

On 7/12/2015 8:35 PM, Anatolij Gustschin wrote:
> On Sun, 6 Dec 2015 12:01:08 +1100
> "Brendan Simon (eTRIX)" <brendan.si...@etrix.com.au> wrote:
>
>> Here is info from /proc/mtd and my /etc/fw_env.config.
>>
>> root@bjs:~# cat
>> /proc/mtd
>>  
>>
>> dev:size   erasesize  name
>> mtd0: 0050 0001 "boot"
>> mtd1: 0002 0001 "bootenv"
>> mtd2: 0002 0001 "config"
>> mtd3: 00a8 0001 "image"
>> mtd4: 0104 0001 "spare"
>>
>> root@bjs:~# cat
>> /etc/fw_env.config   
>>   
>>
>> # Configuration file for fw_(printenv/setenv) utility.
>> # Up to two entries are valid, in this case the redundant
>> # environment sector is assumed present.
>> # MTD device name   Device offset   Env. size   Flash sector size
>> # /dev/mtd1   0x  0x2 0x4
>> # /dev/mtd1   0x  0x2 0x2
>> # /dev/mtd1   0x  0x2 0x1
>> # /dev/mtd2   0x  0x2 0x4
>> # /dev/mtd2   0x  0x2 0x2
>>  /dev/mtd2   0x  0x2 0x1
>>
>> Does anyone have any insight into what the correct fw_env.config
>> settings should be from the above info?
> Using /dev/mtd2 in /etc/fw_env.config might be wrong. First, you need to 
> figure
> out which mtd partition contains the sectors with U-Boot environment 
> variables.
> According to /proc/mtd info it could be the mtd1, if the mtd partitions layout
> under linux is correct. To check it, just run
>
>   dd if=/dev/mtd1 | hexdump -C
>
> If the dumped data looks like environment variables, e.g.
>
>     a5 72 49 1b 01 61 64 64  63 6f 6e 73 3d 73 65 74  
> |.rI..addcons=set|
>   0010  65 6e 76 20 62 6f 6f 74  61 72 67 73 20 24 7b 62  |env bootargs 
> ${b|
>   0020  6f 6f 74 61 72 67 73 7d  20 63 6f 6e 73 6f 6c 65  |ootargs} 
> console|
>   0030  3d 24 7b 63 6f 6e 73 6f  6c 65 7d 2c 24 7b 62 61  
> |=${console},${ba|
>   ...
>
> then the mtd1 device is correct. Use it in fw_env.config.
> To determine other parameters for fw_env.config you need to check the
> used environment configuration in the U-Boot source, in the board's config
> file (include/configs/zyng_zed.h, include/configs/zynq-common.h). Search
> for CONFIG_ENV_SIZE, CONFIG_ENV_SECT_SIZE and CONFIG_ENV_OFFSET macros.
So u-boot sources tell me the ENV_OFFSET is at 0xE and the ENV_SIZE
is (128 << 10) = 0x2
I tried dd with "bs=1 skip=917504" and could not find anything in mtd1
or mtd2 ...
I finally tried mtd0 and found env vars :)
I updated /etc/fw_env.config to the following and now fw_printenv works
and no crc errors are reported.  Yay :)

 /dev/mtd0   0xE  0x2 0x2

Is it normal for the environment to not be at offset 0x0 and not be in
it's own dedicated mtd partition?

>> How can I find out the correct settings.  Is there a command in u-boot
>> itself which will report the correct information?
> for ZedBoard, you probably can not. It depends on the U-Boot configuration.
> If the "mtd" command support is compiled in and the "mtdparts" environment
> variable is set properly, then it could be possible to output some
> info.
"mtd" command is not compiled in.  Might try a custom build of u-boot.

Thanks,
Brendan.

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] u-boot retries with fallback to other images

[Brendan Simon (eTRIX)]

Hi,

Is there any documentation or u-boot support for having a list of boot
images to try, starting with the first in the list, trying 1, 2 or 3
times, then trying the next in the list.

e.g. boot kernel at mmcblk0p3, then mmcblk0p2, then mmcblk1p2, then
tftp/nfs last resort fallback ?
or
boot off partition 3 of eMMC, then partition2 of eMMC, then
partition 2 of SD card, then tftp/nfs ?

I've seen some info on google that says this is possible.  I'm just
looking for good documentation that can explain how to set it all up.

Thanks,
Brendan.

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] fw_env.config settings for Digilent ZedBoard (Zynq 7020 Soc)

[Brendan Simon (eTRIX)]

Hi,

I'm using a Digilent ZedBoard with a Xilinx Zynq 7020 SoC.  The kernel
is from Analog Devices and is a fork of 4.0.0 (according to the Makefile).

I am struggling to work out the fw_env.config file required to use with
fw_printenv/fw_saveenv.
fw_printenv continually gives me CRC error and uses the defaults.

Google hasn't provided much assistance, with some people reporting that
the settings required are different to what /proc/mtd shows.

Here is info from /proc/mtd and my /etc/fw_env.config.

root@bjs:~# cat
/proc/mtd   
  

dev:size   erasesize  name
mtd0: 0050 0001 "boot"
mtd1: 0002 0001 "bootenv"
mtd2: 0002 0001 "config"
mtd3: 00a8 0001 "image"
mtd4: 0104 0001 "spare"

root@bjs:~# cat
/etc/fw_env.config  
   

# Configuration file for fw_(printenv/setenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# MTD device name   Device offset   Env. size   Flash sector size
# /dev/mtd1   0x  0x2 0x4
# /dev/mtd1   0x  0x2 0x2
# /dev/mtd1   0x  0x2 0x1
# /dev/mtd2   0x  0x2 0x4
# /dev/mtd2   0x  0x2 0x2
 /dev/mtd2   0x  0x2 0x1

Does anyone have any insight into what the correct fw_env.config
settings should be from the above info?

How can I find out the correct settings.  Is there a command in u-boot
itself which will report the correct information?

Thanks,
Brendan.


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Hi, you are invited to uniqueBidWin.com - new reverse auction in North America

[Brendan]

Hi, hope everything is well.
I would like to invite you to www.uniqueBidWin.com . An auction where new 
Iphone 32Gs is sold for $7.07
Find a bonuss just for yourself.
Want to make money from home, visit http://uniquebidwin.com/affiliate/
Best

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot