SLAZ447AB October   2012  – September 2021 MSP430F5338

 

  1.   1
  2.   2
  3.   3
  4.   4
  5.   5
    1.     6
    2.     7
      1.      8
      2.      9
    3.     10
  6.   11
    1.     12
    2.     13
    3.     14
    4.     15
    5.     16
    6.     17
    7.     18
    8.     19
    9.     20
    10.     21
    11.     22
    12.     23
    13.     24
    14.     25
    15.     26
    16.     27
    17.     28
    18.     29
    19.     30
    20.     31
    21.     32
    22.     33
    23.     34
    24.     35
    25.     36
    26.     37
    27.     38
    28.     39
    29.     40
    30.     41
    31.     42
    32.     43
    33.     44
    34.     45
    35.     46
    36.     47
    37.     48
    38.     49
    39.     50
    40.     51
    41.     52
    42.     53
    43.     54
    44.     55
    45.     56
    46.     57
    47.     58
    48.     59
    49.     60
    50.     61
  7.   62

6.26 LDO1

noUSB Module

Category

Functional

Function

LDOI detection may fail after power-up

Description

In rare cases, internal 3.3V LDO enabled MSP430 devices may experience a failure in the bandgap that aids in detecting the presence of sufficient LDO input voltage on the LDOI pin. Two primary effects of this are:
1. The LDOBGVBV bit fails to show the presence of a valid voltage on the LDOI pin.
2. The integrated 3.3V LDO fails to start.

Workaround

This error state can be "reset" by clearing all the bits in the LDOPWRCTL register, which (among other actions) disables the internal 3.3V LDO regulator. They can then be set again normally, and the device will function properly.

However, if the integrated 3.3V LDO (the output of the LDOO pin) is used to power the device DVCC pin, and if the rare bandgap error occurs, the CPU will fail to power up because the internal 3.3-V LDO fails to start. The problem might be resolved by cycling power to the LDOI pin. The bandgap failure is also known to occur more often with slow DVCC ramps (>200ms); for example, when there is excessive capacitance on the DVCC pin, in excess of what the LDO specification allows. However, the only sure way to prevent the problem from occurring is to avoid making DVCC power reliant on LDOO.