• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 82 subscribers
  • Views 1113 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.

Lockout on Flash?

Gene Falendysz
Prodigy 140 points

I am using a TMS320F28375DPZPT on two different board designs. On one I am able to load code with my XDS200 through Code Composer with the other the writes fail and Code Composer skips the erase step. (I'm using the same target configuration on both.)

Does anyone know if there is a hardware lockout mode on the flash memory?

  • 0
    TI__Guru** 116421 points
    Hi Gene,

    What is the error you are getting ?

    We have security feature on this device and security settings are programmed in USER OTP. If these settings are programmed by mistake then flash programming will have issue. You could check the content at address location 0x78000 to 78030 and 0x78200 to 0x78230 and if the values are not 0xFFFF_FFFF (please post the values) then there is issue.

    I am assuming you are able to connect to CCS and view the value in memory watch window. If not then please change the bootmode pin setting to WaitBoot and try to connect.

    Regards,

    Vivek Singh
  • 0 in reply to Vivek Singh
    Prodigy 140 points
    The values at those ranges are all 0xffff. If I cheat and move the probe from the working device to the one that doesn't work without exiting debug mode, and then reconnect, I can then write the flash on the problem board.
    The error that is reported when it fails does not seem to relate to the problem.
    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x9d139: (Error -1066 @ 0x9D139) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)
    I have no breakpoints set.
    If I verify with the same file I get:
    C28xx_CPU1: File Loader: Data verification failed at address 0x000A88E8 Please verify target memory and memory map.
  • 0 in reply to Gene Falendysz
    TI__Guru** 116421 points
    Gene, It's good that values are as expected in USER OTP.
    Also on which pin you are connecting the probe which solve this issue. Also once you are able to program the device with valid code, does it work next time without probe?

    Breakpoint is inserted by CCS to halt the code execution after entry to main() so that user can step through their code.

    Regards,
    Vivek Singh
  • 0 in reply to Vivek Singh
    Prodigy 140 points
    Hi Vivek,
    By probe I was referring to the XDS200 connected to the JTAG pins.
  • 0 in reply to Gene Falendysz
    TI__Guru** 116421 points
    Ok got it.

    It look like device is going through reset cycle while connecting to CCS which happen when a fresh device (Flash erased) boots up with boot-pin settings as BOOT to Flash. To program the fresh device it's recommended to power-up the device in "WaitBOOT" (GPIO72 = 1 AND GPIO84 = 0). Please try that and see if that helps.

    Regards,
    Vivek Singh
  • 0 in reply to Vivek Singh
    Prodigy 140 points

    I now have code on the devices and I can run them without the JTAG. I used the method I described above where I start with the XDS200 connected to the board that works and then without exiting or powering off move the JTAG to the failing board and reconnect. When I do this I am able to program the device one time. So at this time the flash is not erased. Here are the messages that come up in the Console:

    C28xx_CPU1: GEL Output:

    Memory Map Initialization Complete

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Process CIO" at 0xa2f56: (Error -1066 @ 0xA2F56) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x9d139: (Error -1066 @ 0x9D139) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)

    A second attempt gave this output:

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Process CIO" at 0xa2f56: (Error -1066 @ 0xA2F56) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)

    C28xx_CPU1: Trouble Removing Breakpoint with the Action "Process CIO" at 0xa2f56: (Error -2044 @ 0xA2F56) Internal error: Requested breakpoint does not exist. Restart the application. If error persists, please report the error. (Emulation package 5.1.232.0)

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Process CIO" at 0xa2f56: (Error -1066 @ 0xA2F56) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x9d139: (Error -1066 @ 0x9D139) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)


  • 0 in reply to Gene Falendysz
    TI__Guru** 116421 points
    Gene,

    Before programming the device, could you just look at the value at these address locations (e.g. 0xA2F56) via CCS memory watch window after connecting to CCS and see what value it's showing?

    Regards,
    Vivek Singh
  • 0 in reply to Vivek Singh
    Prodigy 140 points
    A2F56 - 7700 8BBE FF69 0006 B2BD C5A4 D000 BE07 D100 8F00 0540
    9D139 - FE18 761F 001D 8F00 CAFE 0E2B 0FA4 ED1F 761F 001C 9206