• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 931 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/MSP430F5529: Break at address 0x240f no debug information found.

Deepak Kushwaha
Prodigy 110 points
Part Number: MSP430F5529

Tool/software: Code Composer Studio

Hello Team,

I am facing this issue "Break at address 240f no debug information found". This issue comes after sometime when system runs. I googled this issue forums suggested that because of memory leaks. I have cross checked my code for memory leaks. I have also increases my vcore to 2 as per example Slac300k.  I am using TimerA0 interrupt, UART interrupt USCI_A1 and I2C USCI_B0 interrupt and I am driving stepper motor based on data input from UART and I2C

Now I am explaining my code flow:

1. Increased Vcore and set clock for 16Mhz.

2. Configured UART, TIMER and I2C interrupt.

3. Using I2C for accelerometer.

4. UART for taking command.

I tried a lot to resolve this issue. I have also seen my memory map file to find out that 240f location where code is getting stuck up. For your reference I am attaching my memory map file.

Please help me to come out from this problem.memoryMapfile.txt

 

  • 0
    TI__Mastermind 29105 points

    Hey Deepak,

    How does this present at a high level?  Does your code run for a while and eventually stop working?  Then, when you pause the debugger it's pointing to this location?  

    If so, it probably means that your code is running off in the weeds at some point.  When that happens, then ending location when the CPU finally hangs isn't always very helpful in figuring out where the issue originated.  

    It looks like 0x240F is associated with your .data section and is in your RAM.  Do you know what it's trying to read there or how it gets there?   

    Your stack is in RAM at 0x4360 with a length of A0.  You can view this section of memory while debugging with the memory viewer.  Can you confirm that your stack hasn't overflowed?  

    Thanks

    JD

  • 0 in reply to JD Crutchfield
    Prodigy 110 points

    Hi JD,

    Yes, I am running the code in debug mode it works fine for some time and my motor is running. After some time motor stops working. At that moment after pausing then it is pointing to that memory location. Control is not going inside while(1) loop it only serves interrupt routine.

    How can I judge from where it is reading or writing.

    Please suggest.

    Regards

    Deepak

  • 0 in reply to Deepak Kushwaha
    Prodigy 110 points

    Hey JD,

    Waiting for any response from your side. I am continuously working on this issue but could not be able to identify.

    Can I expect any help from TI side on this.

    Regards

    Deepak 

  • 0 in reply to Deepak Kushwaha
    TI__Mastermind 29105 points

    Hey Deepak,

    Sorry for the delay from my side.  Were you able to make any progress while I was away? 

    Were you able to confirm that your stack hasn't overflowed?    

    Thanks,

    JD

**Attention** This is a public forum