Code Composer fails to allow debugging

Richard Strazdas

Other Parts Discussed in Thread: MSP430F5338

I've been debugging successfully for some time, and now Code Composer fails to bring me to main() when I debug.
It has something to do with code size because I can debug one code snapshot. But adding one line of code

signed short int any_var = 50;

leaves me in some debug limbo when I try to debug. If I suspend, I'm in memcpy() or auto_init(). I never get to main().

Debug view while waiting for main()

Debug view while suspended

Environment:
CCS 5.1.0.09000, licensed
MSP-FET430UIF to MSP430F5338 devkit
large data memory model (required by driverlib.lib)

without that extra initialization code, the link map and Debug Console are as follows
link map:
         name            origin    length      used     unused   attr    fill
---------------------- -------- --------- -------- -------- ---- --------
...
RAM                   00002400   00004000 0000096c 00003694 RWIX
FLASH                 00008000   00007f80 00005d82 000021fe RWIX
Debug console:
MSP430: Program loaded. Code Size - Text: 20122 bytes Data: 3826 bytes

after adding one line of code, I can't debug:
link map:
         name            origin    length      used     unused   attr    fill
---------------------- -------- --------- -------- -------- ---- --------
...
RAM                   00002400   00004000 0000096e 00003692 RWIX
FLASH                 00008000   00007f80 00005d8a 000021f6 RWIX
Debug console:
MSP430: Program loaded. Code Size - Text: 20122 bytes Data: 3834 bytes

There's lots of unused RAM and FLASH. What threshold am I crossing? How do I know?

Thanks for any assistance.

Rich

over 14 years ago

0 Richard Strazdas over 14 years ago

Prodigy 70 points

So the images didn't show up. Here are the two Debug views:

Debug view while waiting for main()

my_code [Code Composer Studio - Device Debugging]

TI MSP430 USB1/MSP430 (Running)

Debug view while suspended

my_code [Code Composer Studio - Device Debugging]

TI MSP430 USB1/MSP430 (Suspended)

memcpy(void *,void *, unsigned long)() 0x00D53E (memcpy has only skeletal debug info)

0 AndyW over 14 years ago in reply to Richard Strazdas

TI__Genius 16510 points

Is there any chance your WDT is triggering before you reach main()?

0 Richard Strazdas over 14 years ago in reply to AndyW

Prodigy 70 points

Thanks, Andy, but I don't think that's happening.

I did find a workaround, though.

Rather than initialize variables at the declaration:

int my_var = 50;

I initialize them in the code:

int my_var;

main()

{

my_var = 50;

}

This brought me back across the threshold that I don't see.

If anyone at TI is willing to test my before and after code, I'd certainly be willing to send it.

0 AndyW over 14 years ago in reply to Richard Strazdas

TI__Genius 16510 points

If you send the code to the email in my profile, I'll have a look. The closest device I have access to at the moment is a 5438. This has less RAM, but hopefully it demonstrates the issue.

0 AndyW over 14 years ago in reply to AndyW

TI__Genius 16510 points

Rich,

As discussed offline, this application has a fair bit of static initialization and this takes long enough that the WDT triggers before the initialization completes. The most feasible way to address this particular case in this application is to move part of the initialization to another part of the application.

0 Archaeologist over 14 years ago in reply to AndyW

TI__Guru* 84285 points

You could also disable the WDT inside _system_pre_init. See this forum thread:

http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/t/73308.aspx

Code Composer Studio™︎

Code Composer Studio forum

Code Composer fails to allow debugging