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

TMS320F28377S: How to apply DCSM in TMS320F28377S

GukHyun Lee
Intellectual 260 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: TEST2, UNIFLASH

Dear, C2000 expert.

I'm working DCSM with a TMS320F28377S custom board and having difficulties because it is so confused for me.

I had followed the APP NOTE, named "C2000Tm DCSM Security Tool", one by one, but I'm not sure DCSM is working.

The steps I followed are:

1. Launched CCS 11.0

2. Imported "DCSM Security Tool" Project.

3. Changed 3 places in "dcsm_security_tool.syscfg" (checked red color).

4. Then, I built the "DCSM Security Tool" Project.

5. And I added 'environment variable' and 'path' as specified in the APP NOTE.

5. I copied the dcsm_security_tool.syscfg file to my test project.

   My test project only consists of main.c that print just "hello world".

6. I built my test project successively

7. I programmed test2.out using XDS200. But i got the error message below in the process of programming.

I just followed the APP NOTE, But I couldn't succeed the procedures.

I would say that 'mytest' project is not problem, because it successfully completed programming 'mytest' without dcsm_security_tool.syscfg file copied.

Please Help me, It looks like I missed some steps.

Please let me know what I misunderstood.

Really Thanks.

  • 0
    TI__Guru** 115431 points

    Hi,

    Did you get this error Ist time or made some change in configuration and tried to program the device again ? Asking this because security settings are stored in USER OTP which can only be programmed once so if you are planning to change any configuration then it will not work. What you could do is check the value of USER OTP on device via CCS memory watch view and compare the same with the values in dcsm.asm file and see if it's matching. 

    Regards,

    Vivek Singh 

  • +1 in reply to Vivek Singh
    Intellectual 260 points

    Thank you for your reply.

    You're right. The first programming was successful, but after that I get the errors.

    Ok. I see, I knew that this chip is secured well according to your comment.

    I have several questions in this stage.

    1. With using CCS or Uniflash, I can still view memory address 0x0007_8028, which has password specific for the chip and should be protected from debugging. I can't understand reading those memory data is possible in even secure mode.

    I attach my CCS view. The password I used is :

    0x1FFF_FFFF 0XFFFF_FFFF 0XFFFF_FFFF 0XFFFF_FFFF

    And I can see it in memory viewer

    2. If the USER OTP can be programmed at first, does it mean that user can never change password?

    3. I want to re-program .out file after being secured. So I tried unlocking with Uniflash successfully. And then, is it correct that I should program only pure .out file : it means those not including 'syscfg' file.

     

    Really appreciate.

  • 0 in reply to GukHyun Lee
    TI__Guru** 115431 points

    Hi,

    GukHyun Lee said:
    1. With using CCS or Uniflash, I can still view memory address 0x0007_8028, which has password specific for the chip and should be protected from debugging. I can't understand reading those memory data is possible in even secure mode.

    We have password lock feature which disable access to password value only after user programs the PSWDLOCK fields with value other than 0xF. This feature is provided to avoid accidental locking of the device. Unless PSWDLOCK is programmed, user can see the password and unlock the device. Please refer the DCSM section in TRM for all these details. Once you enable the PSWDLOCK, these values will not be visible.

    GukHyun Lee said:
    2. If the USER OTP can be programmed at first, does it mean that user can never change password?

    Again, please go through the TRM. We have link pointer concept to select the address for active security settings. User need to change the link pointer value to select new address for security settings and program new password values and other security settings.

    GukHyun Lee said:
    3. I want to re-program .out file after being secured. So I tried unlocking with Uniflash successfully. And then, is it correct that I should program only pure .out file : it means those not including 'syscfg' file.

    You only need to unlock and provide the password value in Tools itself (Uni-flash or CCS flash plug-in). You can still have the syscfg files as part of the project and .out as long as you are not programming different values at same location. 

    Hope this is clear.

    Regards,

    Vivek Singh