Problems trying to debug Tiva TM4C129X Dev board with CCS 5.5

Jeff,

Do you see these messages only when loading your application, or when loading the example projects in TivaWare as well? If you haven't tried one of the examples recently, would you mind giving one of the examples for this board a try and let us know how that goes?

You may also want to take a look at these threads that might be helpful (check this and this).

I am able to debug the TivaWare example programs. Hmmm. How can the contents of my.bin file seemingly corrupt the debug interface making it unusable?

While the links you provide are similar to what I am seeing, I don't think are exactly the same.

Any other ideas or suggestions?

Thanks 

Upon further investigation, I have found that if I remove (comment out) the following code, I can debug all I want.

// Setup Watchdog
ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_WDOG0);

// Enable the watchdog interrupt.
ROM_IntEnable(INT_WATCHDOG);

// Set the period of the watchdog timer.
ROM_WatchdogReloadSet(WATCHDOG0_BASE, g_ui32SysClock);

// Enable reset generation from the watchdog timer.
ROM_WatchdogResetEnable(WATCHDOG0_BASE);

// Enable the watchdog timer.
ROM_WatchdogEnable(WATCHDOG0_BASE);

I then loaded the TivaWare watchdog example project and I now get the same error messages that I was seeing in my project. Eureka!

Should this issue remain on this forum or should I start a new thread on the Tiva forum?

Thanks,

Jeff

Jeff,

I don't have that specific development kit to test the watchdog example but your issue sound like the ones reported in these threads:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/285442/1003480.aspx#1003480
http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/286801/1003474.aspx#1003474

The users in those threads were using different devices than yours, however it sounds like your symptoms are also watchdog related. Could you try the workaround suggested in those threads and let us know if it helps? Basically replace the CortexM3_util.gel in the CCS installation with the modified version posted by Chester in the second thread (please make sure to make a backup copy of the original GEL file in case you need to revert back). What this basically does is disable the watchdog prior to loading the program. Let us know if this helps with the issue.

Also could you please let us know the exact steps that allow you to recreate the error with the watchdog example in TivaWare? I will try to get access to the development kit or find someone that has access so we can reproduce it here. Once we are able to reproduce it we should be able to verify if it is the same or related bug and fix it.

I tried using the file from Chester and I got a new error related to trying to read from the address specified in the OnPreFileLoaded( ) function. I check the Tiva datasheet and the register (SRCR0) specified in the gel  file does not exist in the Tiva device. I found a similar register (SRWD) for the Tiva device, and changed the code within the OnPreFileLoaded( ) function and that seems to work. Here is the updated function:

// Reset the WATCHDOG0 and WATCHDOG1 modules prior to loading a file, so that
// the watchdog doesn't corrupt downloading to flash
#define SYSCTL_SRCR0_R 0x400FE500 //0x400FE040
#define SYSCTL_SRCR0_WDT1 0x00000010 // 0x10000000 // WDT1 Reset Control
#define SYSCTL_SRCR0_WDT0 0x00000001 // 0x00000008 // WDT0 Reset Control

#define WR_MEM_32(addr, data) *(unsigned int*)(addr) = (unsigned int)(data)
#define RD_MEM_32(addr) *(unsigned int*)(addr)
OnPreFileLoaded()
{
  //WR_MEM_32 (SYSCTL_SRCR0_R, RD_MEM_32(SYSCTL_SRCR0_R) | (SYSCTL_SRCR0_WDT1 | SYSCTL_SRCR0_WDT0));
  //WR_MEM_32 (SYSCTL_SRCR0_R, RD_MEM_32(SYSCTL_SRCR0_R) & ~(SYSCTL_SRCR0_WDT1 | SYSCTL_SRCR0_WDT0));
  WR_MEM_32 (SYSCTL_SRCR0_R, (SYSCTL_SRCR0_WDT1 | SYSCTL_SRCR0_WDT0));
}

I changed the define values as needed and now only write to the register as only two bits have any meaning.

To get the TivaWare watchdog example to fail, do this:

1. Load project into workspace.
2. Build project
3. Click Run -> Debug. Program should load and run fine.
4. Stop debugger.
5. Click Run -> Debug. Errors should appear and JTAG interface will be broke, requiring unlocking.

Thanks for the help!

Jeff