• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 464 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Debug and low power modes

halo
Expert 1030 points
Other Parts Discussed in Thread: MSP430F5529

When I pause my msp430f5529 execution in debug mode, a new window opens up in the editor. The new page has a hexadecimal number like 0x216 on its tab and a single line that says: No source available for "0x261" . Does this mean the CPU is in low power mode and doesn't know what line to display? Thanks, anyone.

  • 0
    Guru 227245 points

    No, it means that the debug interface reports the CPU to be stopped with R0 (PC) being 0x0216. Which is of course no address where it should be. And where no source code is that could be shown in the tab.
    It may be a misinterpretation due to LPM. Or a problem with your code (like stack overflow or stack corruption due to out-of-bounds array writes). More likely the second, as in case of LPM, the error usually is something like “cannot communication with CPU, CPU off?”

  • 0 in reply to Jens-Michael Gross
    Expert 1030 points

    Hi,

    I read somewhere recently, I think it may have been in "Creating IoT Solutions with the Tiva C Series ..." that sometimes when the MCU is in a while loop like, e.g.,

    while (1) {

      // some code that may include something like SysCtlDelay()

    }

    that the MCU can spend a lot of time in some function for which there is only library code, i.e., no editor file. Could this also at least partially explain the result? Thanks.

  • 0 in reply to halo
    Guru 92251 points

    halo said:
    that the MCU can spend a lot of time in some function for which there is only library code, i.e., no editor file. Could this also at least partially explain the result? Thanks.

    It depends upon if the reported program counter address is within the flash or not.

    For your example 0x261 is an address in peripheral space and so isn't a valid value for the program counter and so isn't explained by the processor being inside library code.

    Is the program operating correctly before execution is paused in the debugger?

  • 0 in reply to Chester Gillon
    Expert 1030 points

    Hi Chester. The problem seems to have gone away after some changes and a recompile. While it is interesting and I would like to get to the bottom of it, I should press on with other more important matters like getting my USB connection to work. Thanks for your help - it has been useful.

**Attention** This is a public forum