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

Original question:

TMS320F28378S: After enabling DCSM no access to flash bank 1

TMS320F28378S: Issue with Locking Bank 1 Using C2000 DCSM Security Tool

Listen Su
Prodigy 30 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi Team

I am currently using the recommended version of C2000Ware_5_03_00_00 and have updated Code Composer Studio to version 12.8.0. Following the instructions in the Application Report C2000Tm DCSM Security Tool, I included the dcsm_security_tool.syscfg from the Example DCSP into my project, which generated two files: dcsm.asm and dcsm.cmd. These files seem to have been generated by the .syscfg file, and I am unable to modify them directly.

However, I noticed that this tool does not include an option to lock Bank 1. As a result, I am currently unable to lock Bank 1 using this tool. Actually, the tool sets GRAB_BANK1 bit:29-28 to 00, which means  Flash BANK1 is inaccessible.

Could you please advise me on how to proceed to successfully lock Bank 1 to Zone1 with this tool?

Thank you for your support.

Best regards,

  • 0
    TI__Mastermind 28220 points

    Hi Listen,

    This capability unfortunately does not exist in the DCSM tool at this time, this will be corrected in the next version of C2000Ware. You can refer to the register definitions in the DCSM chapter to determine the correct GRABSECT values to secure bank 1.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Hi Luke,
    Thank you for your response. Initially, I was unsure how to disable the automatic build of dcsm.asm and dcsm.cmd from the dcsm_security_tool.syscfg. However, I have now figured out how to disable the automatic build and manually include dcsm.asm and dcsm.cmd files, modifying the GRABSECT contents accordingly. It looks like this has resolved my issue.

    Thank you again for your assistance.