• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 84 subscribers
  • Views 107 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.

TMS320F28P550SJ: detailed documentation or guidance on how to properly configure and use the DCSM banks under EABI to avoid ESTOPs or boot issues?

Chris Yorkey
Genius 15855 points
Part Number: TMS320F28P550SJ

Tool/software:

Team,

Our customer is currently working on the hardware definition, and it's likely that the TMS320F28P550SJ with a 128-pin QFP package will be used in the new design.

In parallel, they're migrating their project from the legacy COFF format to EABI, which is looking quite promising. That said, we have a question regarding the use of the DCSM Z1/Z2 security zones for locking the flash memory during production. In their EABI linker file, they've currently disabled the DCSM section to prevent a crash during the initial boot sequence when jumping to main(). Do you know if there’s more detailed documentation or guidance on how to properly configure and use the DCSM banks under EABI to avoid ESTOPs or boot issues?

This E2E Forum seems a great place to start here - especially with the relative newness of the F28P55.

TY,

CY

  • 0
    TI__Mastermind 27380 points

    Hi CY,

    Is the customer using JTAGLOCK or programming custom CSM passwords as part of their DCSM settings? If so, they will need to have the "Verify flash after programming" option disabled during the first time programming of the OTP. I would recommend the customer programs their flash first with verify enabled and then programs the OTP with the verify option disabled.

    Thank you,

    Luke