Other Parts Discussed in Thread: MMWAVEICBOOST, ,
I'm having an issue where I cannot use CCS to debug my program. When the debugger is used, the software will crash every time. However, the exact same program when uploaded through the bootloader and loaded from the local QSPI flash works perfectly fine. This would seem to indicate that something is fundamentally wrong with how the debugger interacts with the chip.
[Cortex_R4_0] **********************************************
Debug: Launching the MMW Demo on MSS
**********************************************
Debug: Launched the Initialization Task
Debug: mmWave Control Initialization was successful
Debug: mmWave Control Synchronization was successful
Debug: CLI is operational
[C674X_0] Debug: DPM Module Sync is done
[Cortex_R4_0] Debug: Sending rlRfSetLdoBypassConfig with 0 0 0
{module#9}: "C:/TI/mmwave_industrial_toolbox_4_5_1/labs/automated_doors_and_gates/68xx_automated_doors/src/mss/mss_main.c", line 2431: error {id:0x10000, args:[0x237fc, 0x237fc]}
xdc.runtime.Error.raise: terminating execution
Which is thrown by:
static int32_t MmwDemo_eventCallbackFxn(uint16_t msgId, uint16_t sbId, uint16_t sbLen, uint8_t *payload)
{
uint16_t asyncSB = RL_GET_SBID_FROM_UNIQ_SBID(sbId);
/* Process the received message: */
switch (msgId)
{
case RL_RF_ASYNC_EVENT_MSG:
{
/* Received Asychronous Message: */
switch (asyncSB)
{
case RL_RF_AE_CPUFAULT_SB:
{
MmwDemo_debugAssert(0);
break;
}
This behavior also changes to a complete lockup at this point unless the chip is reset via hardware for subsequent debug sessions. This may be an issue on our part for hooking up the JTAG port, but I'll include the schematic to show you what we did. We are using the TI 20-pin to ARM Cortex 10-pin converter included with the XDS110. (If possible, I'd like to get a schematic for that adapter.)
[C674X_0] Debug: DPM Module Sync is done [Cortex_R4_0] ********************************************** Debug: Launching the MMW Demo on MSS ********************************************** Debug: Launched the Initialization Task
The debugger also has this bizarre behavior where if the target is disconnected or loses power while debugging, I not only have to unplug the XDS110 from my computer, but I also have to restart CCS in order to get debugging to work at all. When reconnecting power and trying again immediately after failure, this error occurs:
Then if the XDS110 is reconnected, you get this error:
Which won't go away until CCS is completely restarted.
