I've been running into an issue where the flash programmer in CCS is failing. I have a secure zone setup, but this issue occurs when my secure zone is unlocked as well. The flash programmer fails trying to erase sector A, my secure zone is sector B and the debug configuration is setup to not erase that sector. It seems like it cannot set a break point. Here is my console output:
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: Error: Failed unlocking device (zone 2) during Flash Operation.
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc15f: (Error -1066 @ 0xC15F) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.507.0)
C28xx_CPU1: Note: The missing clock status flag was detected as set, and needed to be cleared to lock the PLL.
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc591: (Error -1066 @ 0xC591) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.507.0)
C28xx_CPU1: Flash Programmer: Error erasing Sector A. Operation Cancelled.
C28xx_CPU1: GEL: File: D:\Work\TIv5_CLA\F2837x_Simulations\Position_CPU_UTIL\cpu01\ccs\CPU1_FLASH\position_cpu_util.out: Load failed.
I've attached the CCS debug server logs as well. 3146.140929_f377d_flash_programming_error.zip
This error only occurs if I launch the debugger in the CCS Edit perspective. I can get it to successfully program if I start the debugger via the target configuration file, connect to CPU1, run the BootROM, then load in my code via the Run->Load->Load Program dialog.
I have already tried changing the bootmode pins on the controlcard without success.