Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 349 subscribers
  • Views 1260 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cortex M55 Trustzone recommendations before jumping to next level software

TexCorJC

Hello,

I'm still working on my bare metal firmware on new product based on Cortex M55 with Trustzone enabled (secure and non secure firmware are running).

I have an issue , hardfault occurs,  when secure firmware would like to jump to next level secure software and I have issue to debug it (I mean I did not know why but it;s working when I debug it with Lauterbach but failing ).

 I built the next level software by having a vector table with reset_handler which is the entry point. the jump address is the address of new vector table, which corresponds to the address of stack (first element)  and reset_handler is next element , ie jump address + 4.

What is recommended to do before jumping to it ? Is it needed / required to :  disable NVIC interrupt, set new vector table before jumping, clear current msp and psp, set new msp , any requirement to disable non secure vector table, ....

Could I find somewhere code example on it ?

Thanks for your help,

Best Regards,

TexCorJC