uboot environment variables size for Yosemite board.

uboot environment variables size for Yosemite board.

[Leonid]

[-- Attachment #1: Type: text/plain, Size: 619 bytes --]

Hi:

 

I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded
this uboot from DENX site. It uses EEPROM to store environment
variables. Since EEPROM on Yosemite board is only 512 bytes, there can
not be more environment variables which is not very convenient.

 

There is theoretical possibility to save these variables on flash (64M
from which I use only part) and yosemite.h header file even has defines,
allowing this option. But is it going work in reality? What is simplest
way for Yosemite board to increase environment variables storage space?

 

Thanks,

 

Leonid. 


[-- Attachment #2: Type: text/html, Size: 3286 bytes --]

Re: uboot environment variables size for Yosemite board.

[Wolfgang Denk]

In message <FAB00A8DC59FAB42B13C2B3B0F6877010D14478B@ehost011-3.exch011.intermedia.net> you wrote:
> 
> I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded

Note that this is off topic here. You should have posted this on  the
U-Boot-Users mailing list instead.

> this uboot from DENX site. It uses EEPROM to store environment
> variables. Since EEPROM on Yosemite board is only 512 bytes, there can
> not be more environment variables which is not very convenient.

Thisi s wrong. The Yosemite configuration uses (like most (all?) AMCC
eval boards - two redundand flash sectors to store  the  environment.
And available environment size is 8 kB:

	=> print
	...
	Environment size: 1355/8187 bytes

> There is theoretical possibility to save these variables on flash (64M
> from which I use only part) and yosemite.h header file even has defines,
> allowing this option. But is it going work in reality? What is simplest
> way for Yosemite board to increase environment variables storage space?

I have no idea where you got your board configuration from, but it is
definitely   not   current   code,   nor   the   binary   image    at
ftp://ftp.denx.de/pub/u-boot/images/amcc/yosemite/u-boot.bin

The current code does use (redundand) flash for environment storage.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The idea of male and female are universal constants.
	-- Kirk, "Metamorphosis", stardate 3219.8

Re: uboot environment variables size for Yosemite board.

[John Otken]

Wolfgang Denk wrote:
> In message <FAB00A8DC59FAB42B13C2B3B0F6877010D14478B@ehost011-3.exch011.intermedia.net> you wrote:
>> I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded
> 
> Note that this is off topic here. You should have posted this on  the
> U-Boot-Users mailing list instead.
> 
>> this uboot from DENX site. It uses EEPROM to store environment
>> variables. Since EEPROM on Yosemite board is only 512 bytes, there can
>> not be more environment variables which is not very convenient.
> 
> Thisi s wrong. The Yosemite configuration uses (like most (all?) AMCC
> eval boards - two redundand flash sectors to store  the  environment.
> And available environment size is 8 kB:

He has an older Yosemite.  The original Yosemite U-Boot used the EEPROM
for environment variables.

> 	=> print
> 	...
> 	Environment size: 1355/8187 bytes
> 
>> There is theoretical possibility to save these variables on flash (64M
>> from which I use only part) and yosemite.h header file even has defines,
>> allowing this option. But is it going work in reality? What is simplest
>> way for Yosemite board to increase environment variables storage space?
> 
> I have no idea where you got your board configuration from, but it is
> definitely   not   current   code,   nor   the   binary   image    at
> ftp://ftp.denx.de/pub/u-boot/images/amcc/yosemite/u-boot.bin
> 
> The current code does use (redundand) flash for environment storage.
> 
> Best regards,
> 
> Wolfgang Denk
>