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.

MSPM0L1105: Checksum for Productionization

Part Number: MSPM0L1105
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Dear Dennis Sir,

We are using MSPM0 series MCU, and we are required to generate a checksum of our final hex code, to keep the track of version control and documentation for production. We use standalone command line for flash loading, which was generated with help of Uniflash. Can you please help on how to obtain the checksum for the HEX file using Uniflash?  

Thanks and Regards.

  • Hi,

    Let me involve SDTO team for uniflash operation.

    Thanks

  • Can you please help on how to obtain the checksum for the HEX file using Uniflash?  

    Are you looking to generate a checksum for a hex file from the command-line? If so, you can use any standalone checksum utility like certutil which comes with Windows

    certutil -hashfile <file> MD5

  • Hello,

    We have got into a different problem, though our main objective remains the same.

    Let me brief with the timeline:

    1. We were using .out format image file for pilot batch manufacturing using UNIFLASH.

    2. For final release we are required to generate checksum for version control.

    3. But we found that any standalone checksum utility cannot use .out format for checksum calculation.

    3. So we enabled the hex file utility in CCS and generated an intel format .hex file for both firmware loading and checksum calculation.

    4. It turns out that the .hex generated and programmed via UNIFLASH doesn't properly program the MCU, MCU also becomes inaccessible any further.

    So we would like to resolve this issue, which image format to use for production programming and checksum calculation.

    Since our production is also involved please help us with this urgently.

    Thanks and Regards.

  • 3. But we found that any standalone checksum utility cannot use .out format for checksum calculation.

    Why not? Is it because you only care about the checksum of the actual target code and not debug symbols?

    3. So we enabled the hex file utility in CCS and generated an intel format .hex file for both firmware loading and checksum calculation.

    4. It turns out that the .hex generated and programmed via UNIFLASH doesn't properly program the MCU, MCU also becomes inaccessible any further.

    It sounds like you are not passing in the correct options to the hex utility. I will bring this thread to the attention of the device experts for further diagnosis.

  • A. We tried using J-Flash for checksum of .out file but it is not supported.

    B. Yes we are only interested in checksum of the actual target code. 

    Regards.

  • For 'intel hex', please add '--memwidth=8 --romwidth=8' in 'Arm Hex Utility'

  • Excuse me for delay in confirmation, it is taking a while to get it worked out at production.

    I will update as soon as we find everything is working fine.

    Thanks and Regards.

  • OK, waiting for your good news

  • Hii,

    We have confirm successful programming using .HEX on multiple samples. We can now generate the checksum for the same.

    Thanks for the support.

    Best Regards.