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.

Question on MSP430f5418A bootloader

Hello

I am a question on the boot loader:

I have designed a boot loader and splitter MSP430 memory image into 2 parts: main image and secondary image.

I am using interrupt jump table to re-direct CPU to jump between images.

The image arrives from the air.

I see that write an image correctly yet the following is a problem:

I am using IAR toolchain and compile with short data model.

The image I send is the one from the output of IAR when compile using map-txt format

What I have noticed is that the TXT file received from IAR and the image read back after i download using IAR are different at some bytes...The difference is at the are of functions __data16_memcpy and other system functions.

Why there is a difference between the TXT file and the image file downloaded from IAR?

This is urgent issue so appreciate a quick reply.

Thanks

  • May be it is because of debug information generated by IAR?

  • The source file may contain information that is not sent to the MSP. However, the TXT files usually do not contain anything but the plain binary data.
    So unless your code changes part of the flash during execution, the parts you read back from flash should 1:1 match the TXT file (if it is form the same build) and what IAR sent to the MSP.

    Try the following:
    Download the free Elprotronic flashing software.

    With it, upload the TXT file to the MSP, run it a few times, then read the flash content back (or simply do a verify with this program). You should have a 100% match.
    If not, then somehow the flash content changed.

  • Hi

    I thanks a lot for response.

    I think that while using IAR, and generating TI TXT image, there is no debug information. While compiling d43 image, there is a debug information added and thus d43 image will be different from TXT file generated without the debug...

    I will also try your advice.

    Thanks again

    Igor

  • Right. The TI TXT file is the plain extracted binary code from the linker-generated output file (which contains debug information, binary data, cross-references, mapping tables etc).

    On CCS, the complete linker output is in .out or .elf files. But other than the file format, the content is more or less the same as for the IAR .d43 file.

**Attention** This is a public forum