This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Bootloading from EEPROM: location in ram of code

I'm using the CC28346 controlCARD that has 64kB of EEPROM connected to the micro by I2C.  In order to bootload from the EEPROM, I understand there needs to be some additional information than the .out file that is loaded from the EEPROM.  This includes the destination (in RAM, I presume) of "blocks" of bootloaded code.

The image I'm using (.out) is less than 64kB, so I intend to load the entire file onto the on-board EEPROM and boot from I2C.  Since the "block" size inputs during boot are 16 bits, I was going to try to put all the code (the .out file) in one "block".  However, I'm unsure of what destination I should use.  In the memory map for the project, the "codestart" section's origin is 0x00000000; does this mean I can load the entire .out file (binary data) to this location and successfully boot from the EEPROM?

Additionally, assuming the code should be loaded to address 0x0, is there any reason to split up the code into different "blocks"?

 

Regards,

TG

  • Trey,

    I am afraid that you are on a wrong path. You cannot use the out-file as a boot image, you have to convert it first into one of the downloadable data formats. The hex2000 utility will do the trick (see spru963a, page 62ff).

    Also the adresses, which are used for the download are fixed by the linker commands of the project, that created the out-file. You cannont load the image to other adresses because all address relations are fixed in that file. Actually the download is uaually split into various parts, specified by the linker commands.

    Regards