• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 195 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

MSPM0G3507: Combo hex flashing using UniFlash

MSPM0G3507: MSPM0G3507

Rohini Jadhav
Prodigy 60 points
Part Number: MSPM0G3507


Tool/software:

Hi team,
https://software-dl.ti.com/codegen/docs/tiarmclang/compiler_tools_user_guide/compiler_manual/hex_utility_description/description-of-the-object-formats-stdz0792390.html#binary-object-format-binary-option

As suggested above link, we tried using the following configuration in the linker(.cmd) file:

.version_info 0x0000F000 :
{
   KEEP(*(.version_info))
} > FLASH
Using ROM directive, we are able to generate bin file with .version_info section(custom string) is written correctly to the specified flash location . But during the build process, we encountered the following warnings:

I would like to clarify:

  1. Does this mean that the .BCRConfig and .BSLConfig sections are excluded from the final binary file?
  2. Is it possible to write to a non-main memory region using a .bin file, given that unlike .hex files, .bin files do not contain address mapping information?
  3. If these sections are essential for device configuration (BSL invoke pin setting in our case) or boot, what is the recommended way to include them in the .bin output?
Please refer the snapshots of binary generated after using ROM directive in which .BCRConfig and .BSLConfig sections are excluded,
And normal binary with .BCRConfig and .BSLConfig sections included,
 
  • 0
    TI__Mastermind 46765 points

    Hi,

    1. Yes. That should indicate .BCRConfig and .BSLConfig sections are excluded from the final binary file from my view. 

    2. I do not think a .bin file can contain non-main memory region without address information

    3. The nonmain data is essential during the MCU boot. User should keep a correct data in the nonmain memory. I would suggest to use a different output format like .hex and .txt to contain the nonmain information.

    Best regards,

    Cash Hao