Hi All,
I've had problems before with flashing/debugging on other targets but that was explainable afterwards (unstable voltage supply), but I'm having strange behavior on two different boards with both a TMS320F28334 CPU on which I'm working for several weeks now (stable!). On a fresh booted system I'll run through the following steps with the reported results:
I'm just starting CCS5 and go for debug, the system compiles and erases the flash (well, it says it erases flash) and then it hangs on flashing (0%). Then it fails with the error:
And in the console I get the messages:
C28xx: Writing Flash @ Address 0x0033FFF6 of Length 0x00000003
C28xx: Erasing Flash Sector A
C28xx: GEL output:
ADC Calibration not complete, device is secure
C28xx: Can't run target CPU: Error 0x20000020/-1041 Severve Error during: Execution, device driver: Problem with Emulation Controller. It's recommended to Reset Emulator.......
C28xx: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx: Error writing Flash @ Address 0x0033FFF6 of Length 0x00000002
I push on "Cancel" and CCS5 hangs (Not responding). So I've to kill the program and restart.
So, to be sure it's not the debugger or the target I'll try the RAM build an example project LEDBLINK and debug on the target. This RAM program is running fine, so I reconfigure the program for Flash (CMD file) and again start a new debug session. You would think that it's a code security issue, so if that's the case I should not be able to flash the CPU with blinky when build for flash, nor see the content of the flash memory. Now the result is a running Blinky project in Flash..
So, yesterday I've spend 6 hours rebuilding, rebooting, un- en re-plugging the XDS510 JTAG, trying other examples, trying other boards, trying to lower my blood pressure and now I'm able to load the flash, I'm able to run the code and I'm able to see the content of the Flash. Or.. Am I able to erase the flash for real? I try this by using the on-chip flash tool for all sectors (including A: 0x33C000 - 0x33FFFF) and hit the button "erase flash". And now the erase works again..!? On memory location 0x0033FFF6 the memory browser shows FFFF FFFF. Also on line 0x0033FFF8 (pswd) shows: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Then why is it sooooooo difficult flashing a systems that's NOT protected by CSM!?! I read more posts about failed flashing and locked up debuggers and that it's so fragile.. I think it is very fragile compared to CSS3 and the F280x DSPs. Never had problems like this, unless you did something real stupid.
Could someone explain to me what I'm doing wrong, if I'm doing something wrong, or how I troubleshoot next time more efficiently not spending 6hours with rising blood pressure.
Best regards,
Tjarco