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

TMS320F28386D: Secure Code Copy Reset

W Z
Expert 2120 points
Part Number: TMS320F28386D

The documentation on 3.3.9 Secure Code Copy Reset (SCCRESET) is not consistent with the Table 3-1. Reset Signals.

However, the security reset also resets the debug logic to deny access to a potential attacker.

  • 0
    TI__Mastermind 23380 points

    Hi W Z,

    I am not clear what part of the table is not consistent with the highlighted statement. Could you explain what exactly is wrong in the table?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Expert 2120 points

    I marked with red rectangle 

  • 0 in reply to W Z
    TI__Mastermind 23380 points

    Hi W Z,

    Thank you for clarifying, I have contacted our JTAG experts to get clarification on what the correct value in the table should be. I will get back to you before the end of the day tomorrow.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Expert 2120 points

    I am following this question.  Is there update?

  • 0 in reply to W Z
    TI__Mastermind 23380 points

    Hi W Z,

    I have heard back from our DCSM experts on this issue, and they have verified that the table in this figure is correct. SCCRESET occurs when an interrupt is serviced during the secure copy code function, hence the TRM's advisory to disable interrupts when using the secure copy code function.

    I am awaiting clarification on whether the highlighted statement is inaccurate and should be removed from the TRM. I will get back to you once they have provided a response.

  • +1 in reply to Luke Jones
    TI__Mastermind 23380 points

    Hi W Z,

    The highlighted statement you pointed out is incorrect, I will make sure this is removed from our next release of the TRM. Let me know if you have any other questions.

    Thank you,

    Luke