[U-Boot-Users] PATCH: RPXlite configuration fixes

[Sam Song]

--- Yuli Barcohen <yuli at arabellasw.com> wrote:
> No, I used CFG_ENV_SECT_SIZE instead of
> CFG_ENV_SIZE. It's not the same. BTW, the original 
> comment mentioned "Total Size of Environment
> Sector" which is not CFG_ENV_SIZE.

Ummm, CFG_ENV_SIZE is really a misleading config item.
No matter how small the ENV size is, it take up one
or several FLASH sectors. I have no idea when we use
CFG_ENV_SIZE:-)

> Sam> from 0x4000 to 0x40000. Is it your flash
> > sector size?
> 
> Yes, it is. There are four Am29LV800BB chips so you
> can't have 0x4000 bytes in sector (this would 
> require 4KB sector on individual flash chip
> while in fact the smallest sectors are 8KB). The
> board is configured for high boot (don't know why
> Embedded Planet designers used high boot with
> bottom boot block flashes) so the U-Boot "lives" at
> 0xFFF00000. I put 

So they produce other kind of rpxlite to work right in
low boot mode with bottom boot block flashes later:-)

> the environment to the next sector. The sector's
> size is 4x64KB = 0x40000. With the original
> configuration, saveenv must fail and it
> indeed failed. 

Well, it failed on your rpxlite board but doesn't
mean it would fail on Yoo.Jonghoon's rpxlite board:-)

> Have you got an RPXlite board with different flash
> configuration?

Yeah, I got one. It uses 4 AM29DL323DB90VI devices
(4x8bit) in 16MB(4x4MB) and leaves the u-boot
home at 0xff000000. I ported u-boot on this one
and named RPXlite DW as 2.4 Linux code did.