SLAZ741A march   2023  – april 2023 MSPM0L1105 , MSPM0L1106 , MSPM0L1303 , MSPM0L1304 , MSPM0L1305 , MSPM0L1306 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346

 

  1.   Abstract
  2. 1Functional Advisories
  3. 2Preprogrammed Software Advisories
  4. 3Debug Only Advisories
  5. 4Fixed by Compiler Advisories
  6. 5Device Nomenclature
    1. 5.1 Device Symbolization and Revision Identification
  7. 6Advisory Descriptions
    1. 6.1  ADC_ERR_01
    2. 6.2  ADC_ERR_02
    3. 6.3  COMP_ERR_01
    4. 6.4  GPIO_ERR_01
    5. 6.5  I2C_ERR_01
    6. 6.6  IO_ERR_01
    7. 6.7  PMCU_ERR_01
    8. 6.8  PMCU_ERR_02
    9. 6.9  PMCU_ERR_03
    10. 6.10 PWREN_ERR_01
    11. 6.11 SPI_ERR_01
    12. 6.12 SYSOSC_ERR_01
  8. 7Revision History

GPIO_ERR_01

GPIO wakeup edges may be lost in STANDBY mode

Revisions Affected

Rev C

Details

After waking up once through a single GPIO edge, subsequent GPIO wakeup edges can be missed in STANDBY modes.

  • Case 1: STANDBY0 wakeup - IF the MCU is set into STANDBY0 mode before one cycle of LFCLK AND you set the IO back to the “non-wake” state for <1 LFCLK cycle AND THEN assert it again, the next wakeup edge will not be detected. This issue is because the GPIO module never sees the IO "clear" to the "non-asserted" state AND so it thinks that the pin was always asserted.
  • Case 2: STANDBY1 wakeup - IF a GPIO edge is used to wakeup AND the GPIO pulse is still active when the device returns to STANDBY1 THEN the device will not detect any subsequent wakeup edges.

Workaround

  • Case 1:
    • Set GPIO wakeup edge to both falling and rising edges
    • OR Ensure GPIO wakeup pulse is longer than one LFCLK cycle
  • Case 2:
    • Set GPIO wakeup edge to both falling and rising edges
    • OR Ensure GPIO wakeup pulse is not active before entering STANDBY1