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.

RTOS/MSP430FR5969: Example TI-RTOS Project is not running on evaluation board

Part Number: MSP430FR5969
Other Parts Discussed in Thread: SYSBIOS, MSP-EXP430FR5969, MSP430FR6989, , MSP-EXP430FR6989

Tool/software: TI-RTOS

When I Debug the TI-RTOS project it hangs at vector 54   "__interrupt Void ti_sysbios_family_msp430_Hwi54(Void)"  

It looks like this is happening somewhere in Task.c maybe in Task_postInit or Task_SupportProxy_start.

I am using the MSP-EXP430FR5969 evaluation board

I am using Code Composer Studio Version: 7.3.0.00019  and tirtos_msp43x2_20_00_06

I have the two available TI-RTOS Examples "Empty (Minimal) project" and "Empty Project" 

Any help would be appreciated, we are moving to the MSP430FR5969, I have TI-RTOS running on an MSP430FR6989 without any issues. 

Thank you

-Kevin

  • Hi Kevin,

    Do you know which flag is triggering the System NMI interrupt? The vacant memory access (VMAIFG) or MPU segment violation (MPUSEGxIFG) are most susceptible since the memory organization between the two device variants are different.

    Regards,
    Ryan
  • I am not sure yet, I may need to put some code in to capture this value,
    It looks like it is set to 0x16 which would be JMBOUTIFG JTAG mailbox output, is this an artifact of me looking at it after it is already in the ISR?

    0x00019A SYS__System_Module_SYSUNIV
    0x00019A 0004
    0x00019C SYS__System_Module_SYSSNIV
    0x00019C 0016
    0x00019E SYS__System_Module_SYSRSTIV
    0x00019E 0002 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF

    -Kevin
  • I put in some code to verify that the address 0x19C is set to 0x16 when the HWI is entered.

    I am new with the MSP430s and TI-RTOS and probably need a bit extra hand holding to figure this out.
    I am running an unmodified launchpad example.

    what should I try next if this is indeed a JMBOUTIFG JTAG mailbox output?
    Do I need to change my debug configuration? it is not running when I power cycle it without running the debugger?
    Is there something I should be modifying in the example project?

    Thanks for the help,

    -Kevin
  • Is JMBOUTIE and GIE also set? And this issue occurs while running an unmodified example intended for the MSP-EXP430FR5969? Are you using the native compiler intended for the project?

    Regards,
    Ryan
  • Hi Ryan,

    Yes this is with unmodified examples for the MSP430fr5969, I am running them on the MSP-EXP430FR5969 evaluation board. I am using a windows VM inside of Linux, but I can use the MSP-EXP430FR6989 without issue from my setup so I do not think this would be the issue.

    I am using compiler version TI V16.9.4.LTS, I think this is the native, should I try the GNU option?

    Status Register
    SR 0x0004 Core
    GIE 0 General interrupt enable. This bit, when set, enables maskable interrupts. When reset, all maskable interrupts are disabled.

    SFRIE1 Register
    SFRIE1 0x00BA Interrupt Enable 1 [Memory Mapped]
    JMBOUTIE 1 JTAG Mail Box output Interrupt Enable

    Thanks for looking into this

    -Kevin
  • I do not know if it was clear in my response

    Yes JMBOUTIE is set

    No GIE is not set

    I I have some more general questions

    Should the Launchpad TI-RTOS examples run on the MSP-EXP430FR5969?

    Does anyone have TI-RTOS running on this processor? Or is this an issue with my Code Composer Studio Setup?

    If it used to would should I be reverting to older versions of CCS and TI-RTOS?

    Thanks for the help

    -Kevin

  • Your response was clear Kevin, I've been trying to loop in a TI-RTOS expert to help answer your question. TI-RTOS LaunchPad examples should run on the MSP-EXP430FR5969. TI-RTOS is supported for the MSP430FR5969 and has operated on this device several times before without issue. You can try using different CCS or TI-RTOS versions, please be sure to report your findings.

    Regards,
    Ryan
  • rolled back to CCS V7.1 and issue was solved
  • That's valuable feedback, thanks for the update.

    Ryan

**Attention** This is a public forum