• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 554 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.

Original question:

CC2652R: NMI vector is not as configured

CC1352R: ROV BIOS error "NMI vector is not as configured" when watchdog open

AlexTim
Expert 1270 points

Part Number: CC1352R
Other Parts Discussed in Thread: SYSBIOS

I have the same issue like

https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1077953/cc2652r-nmi-vector-is-not-as-configured/4006814

The issue is also can be reproduced in the basic SDK 5.20 "watchdog" example as well.

How could it be fixed?

  • +1
    TI__Mastermind 20412 points

    Hi Alex,

    The watchdog example is functional. You can see the red LED blinking, if you just run the code. 

    I see that the BIOS scan for errors module prints the message "NMI vector is not as configured! Should be: ti_sysbios_family_arm_m3_Hwi_excHandlerAsm__I". This is because the ROV expects the vector Label for NMI to be "ti_sysbios_family_arm_m3_Hwi_excHandlerAsm__I". 

    In the watchdog example, the watchdog defines its own handler for the NMI, specifically, you can see this by stepping over the Watchdog_open(). 

    And the ROV sees that it is not labelled as ti_sysbios_family_arm_m3_Hwi_excHandlerAsm__I and raises an error. But it is still functional. 

    Regards,

    Sid

  • 0 in reply to Sid
    Expert 1270 points

    Hi Sid,

    Thanks! Yes, we see that the watchdog works in our project, but we are preparing our device for production and the ROV message worries us a little bit. Is there any way to fix this error in the ROV?

    Regards,

    Sid

  • +1 in reply to AlexTim
    TI__Mastermind 20412 points

    Hi Alex,

    I spoke to the RnD team and it is not trivial to fix this issue in ROV without actually modifying the ROV source code.

    But like I mentioned before, this is an issue with how the ROV parses the data and not the watchdog itself.

    It should have been a "note" or even maybe a "warning", but the error is not the appropriate label for this. Please disregard this. 

    Regards,

    Sid