• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 99 subscribers
  • Views 62 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.

MSPM33C321A: Clarification on Configuring MSPM33 Device to Operate Fully in Non-Secure Mode

Naveen G
Prodigy 10 points

Part Number: MSPM33C321A

Dear TI Support Team,

I am currently working with an MSPM33 device (1 MB flash variant) and would like to clarify a few points regarding TrustZone configuration and memory attribution.

My objective is to configure the device such that the entire application runs in the Non-Secure domain. I intend to use the full 1 MB flash starting from address 0x00000000 for a Non-Secure application.

I would appreciate clarification on the following points:

  1. What is the way to do the partition as mentioned ?

  2. What is the recommended method to verify that the system is now operating entirely in the Non-Secure state (for example, through debugger registers or runtime checks)?

  3. When operating in this mode, what should be the linker configuration?

  4. Are there any regions on the MSPM33 that will remain permanently Secure?

  5. Is there any recommended reference example for the same?

  6. Also where can i find a detailed explanation of memory mapping for the MSPM33C321A since the RM contains a generic memory map followed by ARM.

Any guidance or recommended documentation references would be greatly appreciated.

Thank you for your support.

Kind regards,
Naveen G