SLAZ758 November   2024 MSPM0G3519

 

  1.   1
  2.   Abstract
  3. 1Functional Advisories
  4. 2Preprogrammed Software Advisories
  5. 3Debug Only Advisories
  6. 4Fixed by Compiler Advisories
  7. 5Device Nomenclature
    1. 5.1 Device Symbolization and Revision Identification
  8. 6Advisory Descriptions
    1. 6.1  ADC_ERR_05
    2. 6.2  ADC_ERR_06
    3. 6.3  CPU_ERR_01
    4. 6.4  FLASH_ERR_01
    5. 6.5  I2C_ERR_05
    6. 6.6  PMCU_ERR_07
    7. 6.7  PMCU_ERR_10
    8. 6.8  SPI_ERR_02
    9. 6.9  SPI_ERR_04
    10. 6.10 SPI_ERR_05
    11. 6.11 SRAM_ERR_01
    12. 6.12 SYSOSC_ERR_01
    13. 6.13 SYSOSC_ERR_02
    14. 6.14 TIMER_ERR_06
    15. 6.15 UART_ERR_01
    16. 6.16 UART_ERR_02
  9. 7Trademarks
  10. 8Revision History

6.13 SYSOSC_ERR_02

SYSOSC Module

Category

Functional

Function

MFCLK does not work when Async clock request is received in an LPM where SYSOSC was disabled in FCL mode

Description

MFCLK will not start to toggle in below scenario:
1. FCL mode is enabled and then MFCLK is enabled
2. Enter a low power mode where SYSOSC is disabled (SLEEP2/STOP2/STANDBY0/STANDBY1).
3. Now async requst is received from some peripherals which use MFCLK as functional clock.
This is happening because on receiving async request, SYSOSC gets enabled and ulpclk becomes 32MHz. But the SYSOSCTRIM FSM does not move from DISABLE state. Due to this, the FCL bases MFCLK is gated off and it does not toggle at all.

Workaround

Avoid using this scenario condition.