• State
  • Replies 18 replies
  • Subscribers 85 subscribers
  • Views 363 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F280037C: Programming DCSM OTP to Standalone boot from Flash using Sysconfig

Jacob Myers
Prodigy 30 points
Part Number: TMS320F280037C
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Tool/software:

I have a question regarding setting up the DCSM OTP so that the device standalone boots from Flash.

I understand that the Boot Mode Select Pins for the F28003x MCUs are defaulted to GPIO24 and GPIO32 and that these should be pulled HIGH to set the boot mode configuration to FLASH. However, I would like to utilize these GPIO pins for other functions, so I am attempting to configure the boot mode per section 4.5.3.1 Zero Boot Model Select Pins in the TMS320F28003x TRM in addition to the DCSM Security Tool guide SPRACP8A, but I am getting the following error when attempting to flash.

I am setting the ZONE1 header in sysconfig to use 0 Boot pins and for the BOOTDEF0 to be FLASH entry address 0x00080000. I am not configuring the Linkpointer and I am leaving Zone 2 as is. This is the first time I have attempted to flash a build that incorporates the dcsm.asm and dcsm.cmd files generated by sysconfig, so I don't get why it is informing me that I am attempting to program locations that have already been programmed.

Possible causes/fixes for this error?

Is there a method for retrieving the DCSM OTP settings in realtime from the device?

Current Sysconfig Settings:

Keep in mind that I am using v4.03.00 of C2000ware and v12.3.0 of CCS.

Appreciate any help.

  • 0 in reply to Aswin P
    TI__Mastermind 23690 points

    Hi Jacob,

    Apologies for the delayed reply. I am confused as to why you are seeing this error as well. Could you connect to the device and look at the memory browser at address 0x78000 onward and send a screenshot of what you see?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    See the screenshots for what you requested below:

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Hi Jacob,

    Perhaps your dcsm.asm file is attempting to program all Fs at address 0x78004. Could you share the generated dcsm.asm and dcsm.cmd files as well?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    See below.

    dcsm.cmd:

    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. Z1 password locations / Flash and RAM partitioning */
    DCSM_OTP_Z1_LINKPOINTER : origin = 0x78000, length = 0x00006
    DCSM_OTP_Z1_JLM_ENABLE : origin = 0x78006, length = 0x00002
    DCSM_OTP_Z1_GPREG : origin = 0x78008, length = 0x00008
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    dcsm.asm:

    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 0x00003FFF
    ;; .long 0x00003FFF
    ;; .long 0x00003FFF
    ;;
    .sect "dcsm_otp_z1_jlm_enable"
    .retain
    .long 0xFFFF000F ;Z1OTP_JLM_ENABLE
    ;; .sect "dcsm_otp_z1_jtag_pswdh"
    ;; .retain
    ;; .long 0x4BFFFFFF ;Z1OTP_JTAGPSWDH0
    ;; .long 0x3FFFFFFF ;Z1OTP_JTAGPSWDH1
    .sect "dcsm_otp_z1_cmac_key"
    .retain
    .long 0x00000000 ;Z1OTP_CMACKEY0
    .long 0x00000000 ;Z1OTP_CMACKEY1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Hi Jacob,

    I see the issue. Your linkpointer values are commented out in dcsm.asm. When this happens, CCS will attempt to program all Fs at address 0x78000 which will fail since you cannot program bits to a 1 if they are already programmed to a 0.

    To fix this you must enable the Zone Header block in SysConfig so that the linkpointer values will not be commented out in your generated code. Make sure you do not program any values in the zone header with unintended values since they will be permanently programmed on the device (with the exception of JTAGLOCK / JLM_ENABLE)

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    After implementing your suggestion for modifying the sysconfig file to include linkpointer values, I am still seeing a flash error unfortunately. However, I am not seeing the error that I am attempting to program memory locations that have already been programmed now, so I think its a step in the right direction. See below for flash error:

    My sysconfig file is as follows:

    And the new resulting dcsm.asm and dcsm.cmd files are below:

    dcsm.asm:

    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 0x00003FFF
    .long 0x00003FFF
    .long 0x00003FFF
    .sect "dcsm_otp_z1_jlm_enable"
    .retain
    .long 0xFFFF000F ;Z1OTP_JLM_ENABLE
    ;; .sect "dcsm_otp_z1_jtag_pswdh"
    ;; .retain
    ;; .long 0x4BFFFFFF ;Z1OTP_JTAGPSWDH0
    ;; .long 0x3FFFFFFF ;Z1OTP_JTAGPSWDH1
    .sect "dcsm_otp_z1_cmac_key"
    .retain
    .long 0x00000000 ;Z1OTP_CMACKEY0
    .long 0x00000000 ;Z1OTP_CMACKEY1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    dcsm.cmd:

    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. Z1 password locations / Flash and RAM partitioning */
    DCSM_OTP_Z1_LINKPOINTER : origin = 0x78000, length = 0x00006
    DCSM_OTP_Z1_JLM_ENABLE : origin = 0x78006, length = 0x00002
    DCSM_OTP_Z1_GPREG : origin = 0x78008, length = 0x00008
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Appreciate any help.

    Thanks,

    Jacob

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Have you changed any settings under "Configure Boot Setting" in SysConfig(inside of Zone Header block)? It seems you have already programmed the GPREG block which is affected by these GUI fields.

  • 0 in reply to Luke Jones
    Prodigy 30 points

    This is the first instance that I have tried to flash the MCU with "Configure Boot Setting" Sysconfig fields populated, so I'm not sure how this OTP would have been programmed already if that's the case. Is there any way to check the contents of the GPREG block to see if it is configured for Zero BMSP and to boot from flash?

    If Zone1 has been programmed somehow, then if Zone2 is programmed this should override the settings in Zone1 correct? So, I could potentially still be able to configure this as Zero BMSP to boot from flash by programming the Zone2 header?

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Hi Jacob,

    You can confirm whether values have been programmed at GPREG by observing the contents of the memory browser starting at address 0x78000. Could you take a screenshot of this and share it on this thread?

    You're correct, programming custom settings in zone 2 will override settings in zone 1, however I'd recommend not doing this until you confirm what is going on with zone 1 and save the zone 2 method as a last resort.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    If I try to program with the dcsm .asm and .cmd files included in the build, then I receive the flash program error that I have posted below and the memory browser is blank.

    If I exclude the dcsm .asm and .cmd files from the build and flash, then the memory browser does populate with the values shown below after the flash operation is complete.

    Thanks,

    Jacob

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Hey Jacob, it appears you've programmed custom GPREG values at addresses 0x7800C and 0x7800E. You won't be able to reprogram the GPREG values with your current .cmd and .asm file. 

    If you uncheck "Configure Boot Setting" in SysConfig, do all of the GPREG values get commented out in the generated dcsm.asm? This is the expected behavior. If this is the case I'm not sure how the GPREG values would've been programmed with the 0x5AFFFFFF values you're seeing in the memory browser.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    That is unfortunate that they have already been programmed. I don't recall doing this. The asm file does comment out the GPREG values when I uncheck the Configure Boot Setting box.

     

    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 0x00003FFF
    .long 0x00003FFF
    .long 0x00003FFF
    .sect "dcsm_otp_z1_jlm_enable"
    .retain
    .long 0xFFFF000F ;Z1OTP_JLM_ENABLE
    ;; .sect "dcsm_otp_z1_jtag_pswdh"
    ;; .retain
    ;; .long 0x4BFFFFFF ;Z1OTP_JTAGPSWDH0
    ;; .long 0x3FFFFFFF ;Z1OTP_JTAGPSWDH1
    ;;
    ;; .sect "dcsm_otp_z1_cmac_key"
    ;; .retain
    ;; .long 0x00000000 ;Z1OTP_CMACKEY0
    ;; .long 0x00000000 ;Z1OTP_CMACKEY1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    My only course of action now would be to flash to the Zone2 location with the desired header and linkpointer values correct?

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Yes, programming custom boot settings in Zone 2 will override the custom settings in Zone 1. After this the boot settings will be permanent.

    To test your boot configuration you can use emulation boot before programming the values permanently in OTP.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    I tried setting the EMU boot memory to match the Zero BMSP configuration using the EMU_BOOT_FLASH script defined in the F280037.gel file. With the emulator connected, the device is not booting from flash as I understand it should. See below for memory browser for the contents of the EMU boot registers:

    Is there another GEL script I need to run to get the board to boot from flash with emulator connected?

    I would like to get this to work prior to setting Zone 2 OTP values.

    Thanks,

    Jacob

  • 0 in reply to Jacob Myers
    TI__Mastermind 23690 points

    Are you triggering a CPU reset in the CCS GUI after configuring the emulation boot registers?

    Yes let's make sure this works before you program Zone 2

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Luke,

    When i attempt to trigger a CPU reset in the CCS GUI, I am getting a No Source Available error and it appears to not complete the reset:

    The OnReset() GEL function is called once a Debug session is initiated, correct? I say this because I see the GEL_TextOut print statements in SetupDCSM() which is called in the OnReset() in the console once i execute a debug session. So if that is the case then the emulation boot registers should be getting read if an emulator is connected during boot, which does not seem to be the case otherwise the device would boot from flash.

    When I take a look at the 0x0D00 in the memory browser which should be the EMU-BOOTPIN-CONFIG register, I do see that it contains 0x5AFFFFFF and the EMU-BOOTDEF-LOW registers contains 0x00000003, which should cause the bootloader to boot using a Zero BMSP configuration from Flash at entry point CPU Bank 0, Sector 0 (0x0008 0000) as I understand it.

    Is there any way to step through the execution of the boot mode process to ensure it is following the emulation boot flow as defined in Figure 4-2 of the TRM?

    Are there any obvious reasons as to why I would be getting the No Source Available error when executing a CPU reset in the CCS GUI? I can obtain the Disassembly code if it is necessary.

    Thanks,

    Jacob

  • 0 in reply to Jacob Myers
    TI__Mastermind 34655 points

    Jacob,

    You can load the boot rom sources and symbols from C2000Ware under libraries/boot_rom/f28003x/rev0.  This would allow you to step through to the bootrom execution.

    Regards,

    Joseph