• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 1435 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Code update through EEPROM

Salman Liaquat

Hi,

i am planning to work on secondary bootloader using IAP to update code from extrnal EEPROM on I2C.
In order to do that, i first need to write the code(may be hex file) in to EEPROM.
I know how to write some data to EEPROM but i am confused about what file needs to be written to EEPROM if i had to use it for firmware update of ARM7 LPC2138.

Is it a hex file of that firmware or some other file and should i write that to eeprom as it is or with some modification or what..?

Regards,
Salman.

Parents
  • 0 in reply to Salman Liaquat

    The hex file is more than twice as large as the real data, since every byte is encoded as two characters 0..9, A..F. Then you have some extra characters to encode record type, address, checksum.

    You can convert the hex file to binary and just transfer and store this data. This is, after all, what your secondary boot loader have to write into the flash - the processor can't run any Intel-hex data.

Reply
  • 0 in reply to Salman Liaquat

    The hex file is more than twice as large as the real data, since every byte is encoded as two characters 0..9, A..F. Then you have some extra characters to encode record type, address, checksum.

    You can convert the hex file to binary and just transfer and store this data. This is, after all, what your secondary boot loader have to write into the flash - the processor can't run any Intel-hex data.

Children
No data