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.

MSP430FR6045: Break at address "0x33ffe" with no debug information available, or outside of program code.

Part Number: MSP430FR6045

Development is in progress using MSP430FR6045.
The source is being developed based on the USS_Water_Demo source provided by TI.

Sometimes the operation stops with "Break at address "0x39b5c" with no debug information available, or outside of program code". The address here is randomly generated.

As a result of debugging, it is assumed that the MCU operation stops when a timer interrupt occurs while the __bis_SR_register(mode) function is running inside the commonWaitForconversion function (LPM0).

Execution path : USSLibGUIApp_Engine -> USS_startLowPowerUltrasonicCapture -> USS_commonTriggerSingleCapture -> commonWaitForconversion -> __bis_SR_register(mode)

If you check the USSSWLIB_USS_interrupt_status variable when the operation stops, USS_SAPH_SEQ_ACQ_DN_INTERRUPT is set.
The timer uses CCTL2 of Timer A1 used in USS.

Please tell me how to solve this

The CCS Version in use is 11.2.0.00007.

  • Hi Jung,

    The function that you mention here is very well tested, I doubt that the function itself is the issue. It is not impossible but we should look elsewhere first.

    The address your program has jumped to is not a valid address for the device (see section 9.16 in the datasheet for memory map). Is it possible that your stack is corrupted?

    Have you edited the example code that you mentioned? Or are you running the example exactly as it was downloaded?

    We have some errata regarding entering and exiting some LPMs with this device. Are you sure that it is using LPM0? See our errata sheet to check if any changes you have made violate an errata.

  • The source I'm using now only added a timer from the downloaded source.

    I don't directly access or change the stack.

    Even if you check the errata sheet, the violation is not confirmed.

    Have you tested it? If you haven't tried it, please test it.

  • Are you using a timer interrupt? If so, did you use the correct vector?

  • Yes, I am using TA1 CCTL2 and CCR2.

    It doesn't stop unconditionally in the Timer interrupt, it only happens in the situation mentioned above.

  • Jung,

    I'd again like to ask you if you can confirm that you are entering LPM0, or another LPM. PMM31 and PMM32 could apply in the case that you are going into LPM2/3/4.

    Did you use the USS Gas demo, or the template example?

    I have just programmed my own device with the USS gas demo, and added the TA1 CCR2 peripheral. I am still able to use the USS Design Center, and the program does not hang.

    When you say you've added the timer, does that mean you added an interrupt vector as well? The demo code has already defined most of them so I am wondering what you changed.

  • Hi.

    I didn't make a feature to enter another LPM.
    What I have confirmed is that the point where the MCU stopped working is the __bis_SR_register function part in commonWaitForconversion.

    I am using the USS Water Demo.

    I didn't add the timer myself. USSLIB_HAL_TIMER_INT_CCRn from USS_lib_HAL source is being used.

  • The code shown bugs me because it disables interrupts and THEN does __bis_SR_register(mode). Leaving only non maskable interrupts around to cause an exit from the low power mode.

  • Could you share what exactly you changed? I can see that this interrupt vector, and TA1CCR2 specifically, are already used for critical functions in the demo. Depending on what you changed this could be the issue.

  • I shared it with you through a private message.

    I didn't find using TA1CCR2 unless I changed the definition condition in the USS Water Demo source.

    Is there a place that is being used?

  • For others who come across this post: 

    We have continued the discussion in private messages as it includes private project details. I will update this thread with a general solution for future readers when we reach one.

**Attention** This is a public forum