• Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1129 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.

Reset handling vector code for MSP430 Family

Nitesh Padiyar77
Genius 3745 points

Other Parts Discussed in Thread: TIDM-FRAM-CTPL, MSP430F5659

Hi All,


Need help in handling reset vector code with TI RTOS.

How to enable the reset handing for MSP430 controllers using TI RTOS?

Can i do it in .cfg file? Please help me.

Any reset vector code available for reference to handle the brownout reset and other reset types?

Thanks and regards
Nitesh

  • TI__Guru**** 223427 points
    Hi Nitesh,

    Please see if the following E2E post answers your question: e2e.ti.com/.../455518

    MSP430 SYS/BIOS Wiki page: processors.wiki.ti.com/.../BIOS_for_the_MSP430

    Moving this to the TI-RTOS forum for their expert advice.

    Regards,
    Ryan
  • in reply to Ryan Brown1
    TI__Mastermind 30830 points

    Nitesh,


    I'm not sure I understand your question. As described in the wiki link provided by Ryan, the reset vector of a SYS/BIOS MSP430 project is routed to 'c_int00' which is boot code that does low level initialization, then C environment initialization, then OS level initialization, then jumps to main.

    Are you needing to plug other vectors in the vector table?

    Alan

  • in reply to Alan DeMars
    Genius 3745 points

    Hi Alan,

    My question was, if my system reset whether i can handle the some of my existing routine and do the EEPROM update before reset?

    If so where or in which ISR i can use to update the my device state on reset?

    Any ISR i can access on reset except watchdog?

    Thanks,

    Nitesh 

  • in reply to Nitesh Padiyar77
    TI__Guru**** 223427 points
    Based on your other posts my best guess is that you are using a MSP430F5659 device. As you don't know when or by what means a system reset will occur, you are not guaranteed enough time to perform a routing and do the required EEPROM update before the device ceases to operate code instructions. There are some workarounds like using the SVSH to monitor DVCC levels and interrupt accordingly if the power supply is failing, but these depend on the nature of the reset (for example, this wouldn't help if the RST line is pulled low or a software reset occurred). The SYSRSTIV register can be evaluated to identify the last cause of a reset but this is after-the-fact and may not do you any good. MSP430 FRAM devices offer advanced save state and the TIDM-FRAM-CTPL library if your need is great enough to consider an alternative MSP derivative.

    Regards,
    Ryan