[U-Boot-Users] I2C eeprom utilities

[U-Boot-Users] I2C eeprom utilities

[Rahmat M]

Hi,

I ported and enabled the eeprom commands to u-boot.

[U-Boot-Users] I2C eeprom utilities

[S. Egbert]

> 
> I ported and enabled the eeprom commands to u-boot.
>>From the readme file, it expects a bin file to be
> loaded into ram and then using the "eeprom write"
> command we should be able to program the eeprom. 
> => tftp 100000 eeprom.bin  
> => md 100000
> => eeprom write 100000 0 100
> => eeprom read 150000 0 100
> => md 150000
> However, when I try the above and check the eeprom
> content only the last few bytes are programmed. Any
> idea? How to generate this bin file? Also, the "imd"
> command is not working properly on my set up.
> 
> I am using u-boot version 1.1.2 on a custom board with
> mpc8541 cpu.
> 
>

Only last few bytes are written in flash after a sequential write block?

Usually indicates that the flash bus has a SMALLER bus width support
(i.e., 8 or 16-bit) and software operation is performing 32-bit
operations instead.

S. Egbert

[U-Boot-Users] I2C eeprom utilities

[Wolfgang Denk]

In message <440F0C1C.20907@sbcglobal.net> you wrote:
>
> > I ported and enabled the eeprom commands to u-boot.
...
> > idea? How to generate this bin file? Also, the "imd"
> > command is not working properly on my set up.
...

> Only last few bytes are written in flash after a sequential write block?

No, not flash, but an EEPROM on the I2C bus.

> Usually indicates that the flash bus has a SMALLER bus width support
> (i.e., 8 or 16-bit) and software operation is performing 32-bit
> operations instead.

No.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Q:  Why do mountain climbers rope themselves together?
A:  To prevent the sensible ones from going home.

[U-Boot-Users] I2C eeprom utilities

[Rahmat M]

Hi Wolfgang,

Thank you for your response!! Everything is working as
expected now. You were correct as I found some issues
with my configuration parameters. To start with atmel
at24c64a eeprom expects a 2-byte offset and so forth. 
So for the record here are the needed configuration to
get the eeprom utilities working.
#define CFG_I2C_EEPROM_ADDR_LEN 2
#define CFG_EEPROM_PAGE_WRITE_DELAY_MS  10  
#define CFG_EEPROM_PAGE_WRITE_BITS      4

Regards,
Rahmat



--- Wolfgang Denk <wd@denx.de> wrote:

> In message <440F0C1C.20907@sbcglobal.net> you wrote:
> >
> > > I ported and enabled the eeprom commands to
> u-boot.
> ...
> > > idea? How to generate this bin file? Also, the
> "imd"
> > > command is not working properly on my set up.
> ...
> 
> > Only last few bytes are written in flash after a
> sequential write block?
> 
> No, not flash, but an EEPROM on the I2C bus.
> 
> > Usually indicates that the flash bus has a SMALLER
> bus width support
> > (i.e., 8 or 16-bit) and software operation is
> performing 32-bit
> > operations instead.
> 
> No.
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> Software Engineering:  Embedded and Realtime
> Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80
> Email: wd at denx.de
> Q:  Why do mountain climbers rope themselves
> together?
> A:  To prevent the sensible ones from going home.
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[U-Boot-Users] I2C eeprom utilities

[Wolfgang Denk]

In message <20060308163943.21311.qmail@web30513.mail.mud.yahoo.com> you wrote:
> 
> I ported and enabled the eeprom commands to u-boot.
> From the readme file, it expects a bin file to be
> loaded into ram and then using the "eeprom write"
> command we should be able to program the eeprom. 
> => tftp 100000 eeprom.bin  
> => md 100000
> => eeprom write 100000 0 100
> => eeprom read 150000 0 100
> => md 150000
> However, when I try the above and check the eeprom
> content only the last few bytes are programmed. Any
> idea? How to generate this bin file? Also, the "imd"
> command is not working properly on my set up.

Then you misconfigured your EEPROM interface  (address  length,  page
size, ...)

> I am using u-boot version 1.1.2 on a custom board with
> mpc8541 cpu.

I wonder why everybody seems so eager to use old code...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Landru! Guide us!
	-- A Beta 3-oid, "The Return of the Archons", stardate 3157.4