Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: UNIFLASH
Hello,
Up until fairly recently I have had no problems on a custom board with the P65x. A few weeks ago I began development on a SSBL and noticed that a bunch or issues arrose with debugging and flashing the controller after 4-6 months of no problems.
lash banks that the user would like the flash plugin to erase (in the CPU1 flash plugin GUI and the CPU2 flash plugin GUI)
C28xx_CPU1: Warning: Failed unlocking device (zone 1) after reset.
C28xx_CPU1: Warning: Failed unlocking device (zone 2) after reset.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x10058: (Error -1066 @ 0x10058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 20.0.0.3283)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: GSxMSEL register configured correctly
C28xx_CPU1: BankMuxSel register configured correctly
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x1010c: (Error -1066 @ 0x1010C) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 20.0.0.3283)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
After doing some research, it looks like the device cannot unlock specific zones in flash to program but I have never worked with the DCSM? It seems the only way to fix this is to perform a bunch of memory operations via Uniflash (don't know why this works is it a different GEL file maybe?) like erasing all of flash and reflashing several times and if I am lucky it will recover. I also noticed that most of the scripts on Uniflash require me to manually reset the controller with our push button or else they hang on OnTargetConnect().
I tried to revert all my changes from _cint00 and the linker cmd file back to what they were and now none of my projects can load or flash.
Any suggestions on how to proceed with debugging if / how the device was locked would be great. I followed the instructions in a similar forum with no success.
