• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 394 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.

CC430F5137: how to reduce the start-up time of the cc430f 5137

lee Peng
Intellectual 720 points

Part Number: CC430F5137

My application needs a very fast start-up time. However, I found that the start-up time of my cc430f5137 is about 12ms which is very long. I measure the start-up time by meausre the voltage of a gpio P3out=0x0 at the head of the main function. I know the start-up time is decided by both hardware and software. I just want to know how to improve the start-up time by modify the code such as putting the initiallization into the start-up file? Regards
  • 0
    TI__Mastermind 48611 points

    Li,

    There is a fixed hardware wake-up and hardware initialization time that you won't be able to change. What you can try shortening is the reset duration by experimenting with the RC component values and the application code load time, which is dependent on the image size.

    BR,

    Seong

  • 0 in reply to Seong Kim
    Guru 117855 points

    Greetings,

    Beyond Mr. Kim's suggestion (shorten the time in which the MCU is "held in Reset") might you:

    • REALLY insure that your power supply has sufficient current capacity - to rapidly & fully charge (all) board supply caps
    • Determine if the hardware initialization may be simplified (i.e. reduced) AT ALL - enabling "speed-up"
    • Employ a more precise (and robust) MCU Supervisor IC - enabling a "Faster & more consistent" POR (and other) MCU Reset.    R-C components DO age - and their "board to board variance" usually forces you to "lengthen" the Reset's duration to insure proper Reset

    For completeness - we've not been told, "Why you initially expressed such concern Re: Start-Up Current!"   That concern may result from "Battery Powered application" - as the current surge is likely to add to the battery's drain.   However - if "More Rapid Start-Up" is your prime objective - cannot you, "Maintain (some) "Very Low-Powered" Sleep (or near Sleep) Mode of Operation - which (most always) enables the FASTER TRANSITION to "Fully UP & Running?"   

    Indeed - this "Trades Current Draw for Start-Up Quickness" - yet we've not been told your "Real Objective..."   (i.e. Current Reduction vs. Start-Up Quickness!)    Such proves helpful (perhaps necessary) - does it not?