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

LAUNCHXL-F28379D: DCSM Security Tool

William Carmichael
Prodigy 20 points
Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE, SYSCONFIG, UNIFLASH, CCSTUDIO

Tool/software:

I'm looking to implement a one zone DCSM that protects the memory of the entire device. The preliminary testing is being done on the LAUNCHXL-F28379D. I imported the DCSM Security tool project example from: C2000Ware_4_00_00_00\driverlib\f2837xd\examples\cpu1\dcsm . I updated the sysconfig as shown below and programed the device. It programmed successfully. After the initial program I was unable to program the device again. I put the password in the debug configurations window (shown below), but it still didn't work. I'm getting the error connecting to the target shown below, but when I run the test connection through the target config ccxml, the JTAG DR Integrity scan-test succeeds.  I think I'm missing something simple, but I'm not sure what. The design intent is to have all the memory protected on the device once it is released to production. I've looked in the TRM for the device and the DCSM Security Tool app guide, but can't figure out what's wrong.

  • 0
    TI__Mastermind 23140 points

    Hi William,

    When you provide the CSM passwords in the On-Chip flash tool and then select "Unlock", does the DSCM unlock successfully?

    Thank you,
    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    No, I've tried through the uniflash program and through CCS & I get the following error:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    C28xx_CPU1: Unlocking device...
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x00078000@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x00078004@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x00078008@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F000@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781F0@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781F2@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781F4@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781F6@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781F8@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781FA@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781FC@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x000781FE@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F010@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F012@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F014@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F016@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F019@Data: target is not connected
    C28xx_CPU1: Lock status: 1
    C28xx_CPU1: Error unlocking device. Device still locked. Please recheck the entered password.
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Somehow, after I programmed the device, I'm not able to connect to it anymore at all.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    Is the device configured to use wait boot or flash boot? If flash boot, you won't be able to connect to the device due to ECSL protection when the flash is secured.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    I was initially running in Emulation Boot, but also tried Wait boot.

    I noticed that the dcsm security tool seems to have the wrong address for boot control. TRM shows Z1-BOOTCTRL is 0x7801E while the autogenerated dcsm.cmd file has z1 boot control as 0x7801C. I didn't select the boot control section in the sys config file, so that section of the dcsm.asm file is commented out. I would think that since the dcsm_opt_z1_bootctrl is commented out, this would not have caused a problem. I'm not sure what should be stored at 0x7801C. I'm including the entire dcsm.asm & dcsm.cmd files for reference as well as the conflicting TRM snippet. The only thing changed is the actual password text in the dcsm.asm file.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    ;----------------------------------------------------------------------
    ; Zone 1
    ;----------------------------------------------------------------------
    .sect "dcsm_otp_z1_linkpointer"
    .retain
    .long 0x1FFFFFFF
    .long 0xFFFFFFFF ;Reserved
    .long 0x1FFFFFFF
    .long 0xFFFFFFFF ;Reserved
    .long 0x1FFFFFFF
    .long 0xFFFFFFFF ;Reserved
    .sect "dcsm_otp_z1_pswdlock"
    .retain
    .long 0xFFFFFFF0
    .long 0xFFFFFFFF ;Reserved
    .sect "dcsm_otp_z1_crclock"
    .retain
    .long 0xFFFFFFFF
    .long 0xFFFFFFFF ;Reserved
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    /* this linker command file is to be included if user wants to use the DCSM feature on the device
    * DCSM means Dual Zone Code Security Module.
    * This linker command file works as an addendum ot the already existing Flash/RAM linker command file
    * that the project has.
    * The sections in the *_ZoneSelectBlock.asm source file is linked as per the commands given in the file
    * NOTE - please note fill=0xFFFF, this helps if users include this file in the project by mistake and
    * doesn't provide the needed proper *_ZoneSelectBlock.asm sources .
    * Please refer to the Blinky DCSM example in the controlsuite examples for proper usage of this.
    *
    * Once users are confident that they want to program the passwords in OTP, the DSECT section type can be removed.
    *
    */
    MEMORY
    {
    PAGE 0 : /* Program Memory */
    /* Z1 OTP. LinkPointers */
    DCSM_OTP_Z1_LINKPOINTER : origin = 0x78000, length = 0x00000C
    /* Z1 OTP. GPREG1/GPREG2 */
    DCSM_OTP_Z1_GPREG : origin = 0x7800C, length = 0x000004
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    Since you're using default boot settings, it's still possible that you've selected flash boot via the boot mode select pins:

    Can you make sure GPIO72 and GPIO84 are configured to use wait boot?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    Yes, I used the switches on the launchpad to configure GPIO72 & GPIO 84 to wait boot.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Could you try the following steps and let me know if this works:

    1. Make sure boot mode select pins are configured for wait boot
    2. click View -> Target Configurations
    3. Right click on your target config file and select launch
    4. In the Debug window, right click on CPU1 and click Connect to Target

    Are you still unable to connect after following these steps?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    Yes, after doing that I'm still unable to connect to the device. Is it possible the boot control register not matching between the TRM and the security tool is part of the problem? I'm wondering if I've changed the boot configuration / pins.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    The address in the TRM is incorrect, this will be corrected in the next release of the TRM.

    Can you try power cycling the device after configuring the wait boot pins and repeating the steps I shared above?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    I have the same problem when I cycle power before trying to connect to the target.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    Do you have another device to test with? I'm not sure what could be causing you to not be able to connect based on your DCSM settings. Could you update your C2000Ware to the latest version, program DCSM settings using SysConfig and see if you get the same issue?

    Let me loop in a JTAG expert to see if they have any ideas what could cause the debugger to not be able to connect.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    Yes, I have another device to test with, but I was looking to see what could have been my problem before I repeat the same steps and lock myself out of the entire device again.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    Understood, I will attempt to recreate this issue on my side using the latest C2000Ware and CCS versions, I'll be back in office on January 6th to test this.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    Ok, thank you! I appreciate the help.

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hi William,

    I think I've recreated the issue on my side. After programming I am able to reconnect but I'm unable to reprogram, I will look into the root cause of this issue and let you know once I have an update.

    Thank you,

    Luke

  • +1 in reply to Luke Jones
    TI__Mastermind 23140 points

    Hi William,

    I've tested this issue on my side and was successfully able to unlock and reprogram the locked device. Couple of questions:

    Did you changed the switches on the launchpad to:

    SW1: off

    SW2: on

    SW3: on

    If you're still unable to program, could you modify the GEL file's ECSLUnlock function to use your custom passwords?

    Could you make sure the "reset target before flash programming operations" option in the On-Chip flash tool is unchecked before attempting to program?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 20 points

    I didn't initially have the switches set to Off, on, on, but I did try that when I was trying to reprogram. I'll try again with C2000Ware Version: 5.04.00.00. & CCStudio Version: 20.0.1.

    There's no prohibited passwords correct?

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    As long as you do not set any bits that were a 0 by default to a 1, there are no prohibited passwords. Try to flip 0s to 1s will result in a programming failure anyways.

    Also, a password of all 0s will result in the zone being permanently locked.

    Make sure to power cycle after adjusting the switches so that the boot mode takes effect.

  • 0 in reply to Luke Jones
    Prodigy 20 points

    When I unchecked the "reset target before flash programming" selection, I was able to reprogram the device. I didn't see any ECSL Unlock function in the GEL file. Is that something that I should add?

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    Hey William,

    I don't think that's needed for what you're trying to do. Some devices may not have the ECSL unlock function in the GEL file which is OK. Let me know if you have additional questions.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    TI__Mastermind 23140 points

    By the way, the reason "Reset target before flash programming operations" would've prevented you from programming is because the DCSM always gets re-enabled upon a device reset which would prevent flash programming.

  • 0 in reply to Luke Jones
    Prodigy 20 points

    Yeah, that clicked once I saw that. I didn't think about the reset being the default operation when I was working on this, but it definitely makes sense now. Thank you for you help!

  • 0 in reply to William Carmichael
    TI__Mastermind 23140 points

    of course, glad you were able to get the issue solved :)