• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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:

CC430F5137 in not working state with stopped LFXT1 and Vcore 0V

CC430F5137: CC430F5137 Vcore level produce program error

rafael flores
Intellectual 270 points
Part Number: CC430F5137

Hi , I'm experimenting some problem using CC430F5137 with RF runing. I have a lot of boards working but sometimes i get the microcontroller stuck in some boards and the only way to fix it  is reprograming the microcontroller, reading the errata I found out that there are some problem with PMM, it is possible that changes or noise in the supply voltage can produce a prgram corruption?

EDIT: I read the program from the stuck boards and there is a part of the main block getting erased

  • 0
    TI__Mastermind 26420 points

    Hey Rafael,

    It is possible that noise on the power lines could be causing issues. How much noise are you seeing on the rail?  Can you try to mitigate it?  

    Also, How fast is the MCU running?  I would say that the most common issue in these cases is Mclk vs Vcore violations.  Basically, noise/dips on the power rail cause dips on Vcore and the device is running faster than can be supported and unknown issues happen.  Figure 5.1 shows the Vcore vs Mclk frequency requirements.  

    Thanks,

    JD

  • 0 in reply to JD Crutchfield
    Intellectual 270 points

    Hi, the Vcore level is set to 2 and the MCU is running at 1MHZ provided by default.

    by now I couldn't see significant noise in VCC, I could get an over voltage of around 30V in some conditions but the protections component are working well, I tried to replicate the fail but the MCU it doesnt get affected.

    my question now is how can the MCU get a part of flash erased? I read the program from the boards I get MCU stuck and in deed there is a part of the main erased (exactly a 512 bytes wich is a segment I think) wich makes the MCU get stuck until I re-programe it.

  • 0 in reply to rafael flores
    TI__Mastermind 26420 points

    Hey Rafael,

    I would label any unexpected change to the flash as "flash corruption".   This can have a few causes, but most commonly are issues with Voltage or running the device out of spec.  Flash writes usually require 2.7V to be successful.  

    Is any part of the application performing flash writes?  

    As we talked about noise but that doesn't seem to be a factor, another common issue is brownouts on the MCU.  Basically, when power is applied or removed the chip can spend some time in low voltage states which can cause issues.  I feel like this is more common with slower voltage ramps up and down.  

    How do the power rails look when you are applying and removing power?  Are you using the built in SVS?  

    Thanks,

    JD