• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 939 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.

TMS320F28075: DCSM CRCLOCK

Ricky Zhang
Genius 9520 points
Part Number: TMS320F28075

Hi, Champs,

There's very few description for CRCLOCK defined in DCSM on F28075.

What's the content for the CRC calculation? Is it the entire flash and OTP, or only DCSM OTP locations?

How can we calculate it? With VCU-II or by software?

I did see there's an short introduction on section 2.13.1.8 SafeCRC which mentions EXEONLY memory CRC calculation.

Best Regards,

Ricky Zhang

  • 0
    TI__Guru** 115271 points
    Hi Ricky,

    CRCLOCK feature is provided for user to permanently disable the CRC calculation via VCU on secure memories.
    User can always have their own CRC algorithm in SW to calculate CRC on their secure data provided they are following all the security rules (e.g. to read the data to calculate the CRC, SW need to run from same secure zone).

    Since EXEONLY memory can not be read even from code running from same secure zone, TI provides secure function (SafeCRC ) which can be called by user to calculate CRC on EXEONLY memories (provided CRCLOCK is not enabled). This is only for EXEONLY memories.

    Regards,
    Vivek Singh
  • 0 in reply to Vivek Singh
    TI__Genius 9520 points

    Vivek,

    Thanks for your explanation. It's very clear and I'll close this post.

    Best Regards,

    Ricky Zhang