• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 162 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSPM0L1306: Flash plugin write protection for driver lib functions

Munan Xu
Expert 4440 points
Part Number: MSPM0L1306

Hello,

I have a customer who's writing a flash plugin for the ROM BSL. From our understanding we need to enable flash write protection to the region with the flash plugin code in order to prevent the mass_erase command from wiping out the flash plugin itself. 

However, if the customer uses driverlib API calls as part of their flash plugin, they need to write protect that as well. Do you have any suggestions on how to define a section for driver lib object placement so that they can write protect a specific range of flash and be guaranteed that the linker places the driver lib code in that section?

Or is there a way to force the linker to inline all the function calls for the flash plugin?

Munan

  • 0
    TI__Mastermind 33245 points

    Hi Munan,

    Preventing the mass erase command from erasing the flash plugin code itself. It sounds interesting to me. Why not use the sector erase command instead of using the mass erase command? It could avoid this issue. 

    If customer insist on using the mass erase command, I do not have any ideas to avoid it for now. 

    Best regards,

    Cash Hao