Other Parts Discussed in Thread: UNIFLASH, CODECOMPOSER
Device: TM4C123G6PM
Programmer: Spectrum Digital XDS200.
Uniflash: 3.4.1.00012
CCS (which programs in Debug ok): 6.1.2
I came across the following which seemed to have the same problem as me, but the solutions didn't help.
https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/324782
“The problem is that, after programming with Uniflash, the code doesn't execute.”
Option A:
uniflash -ccxml <pathToYourCCXML> -program <pathToYourProgram> -targetOp run // (or restart or reset)
What I get:
…
CORTEX_M4_0: Writing Flash @ Address 0x000052cc of Length 0x00000020
CORTEX_M4_0: Writing Flash @ Address 0x0000534c of Length 0x00000018
CORTEX_M4_0: Writing Flash @ Address 0x000053b0 of Length 0x00000020
CORTEX_M4_0: Writing Flash @ Address 0x00005430 of Length 0x0000001a
> Finish Loading.
> Running target.
> Disconnecting from target.
SEVERE: CORTEX_M4_0: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is l
ocked up in Hard Fault or in NMI. Reset the device, and retry the operation. If
error persists, confirm configuration, power-cycle the board, and/or try more re
liable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.228.0)
<END: 09:22:15 GMT+0100 (BST)>
<Operation Time: 25.89s>
<Total Time: 29.934s>
Option B:
cd <installDir>\uniflashv2\ccs_base\scripting\examples\loadti\
loadti -c <pathToCCXML> <pathToProgram>
What I get:
START: 09:28:34 GMT+0100 (BST)
Configuring Debug Server for specified target...
Done
TARGET: Texas Instruments XDS2xx USB Onboard Debug Probe_0
Connecting to target...
testEnv.outFiles: D:\Projects\OBC_1500\04-SoftwareUnitEngineering\OBC_1500_Charg
e_Control\Debug\OBC_1500_Charge_Control_DEBUG.hex
Loading D:\Projects\OBC_1500\04-SoftwareUnitEngineering\OBC_1500_Charge_Control\
Debug\OBC_1500_Charge_Control_DEBUG.hex
Done
Target running...
Interrupt to abort . . .
SEVERE: Profile Clock event id <-1> is invalid. Valid events are:
Error code #4013, error encountered during program execution!
Aborting!
In no situation would it seem to program where a manual reset then caused it to run. If I load on the software by Debugging from CodeComposer, that works and it programs and runs fine.
I've tried creating a ccxml file using Uniflash, and I've used the ccxml file that my CodeComposerStudio successfully uses as a Target Config to program and execute in Debug. No success.
