SLAAET8A April   2025  – December 2025 MSPM0C1103 , MSPM0C1103-Q1 , MSPM0C1104 , MSPM0C1104-Q1 , MSPM0C1105 , MSPM0C1106 , MSPM0C1106-Q1 , MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0G3529-Q1 , MSPM0H3216 , MSPM0H3216-Q1 , MSPM0L1105 , MSPM0L1106 , MSPM0L1116 , MSPM0L1117 , MSPM0L1227 , MSPM0L1227-Q1 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2227 , MSPM0L2227-Q1 , MSPM0L2228 , MSPM0L2228-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2EMC and EMC Standards
    1. 2.1 EMC
      1. 2.1.1 EMS
      2. 2.1.2 EMI
    2. 2.2 EMC Standards
      1. 2.2.1 EMC Standards Category
    3. 2.3 EMC and IC Electrical Reliability in TI
  6. 3EMC Improvement Guidelines Summary
    1. 3.1 PCB Design Guidelines
    2. 3.2 Firmware Guidelines
  7. 4EMC Improvement Features on MSPM0
    1. 4.1 Susceptibility Protection Features
      1. 4.1.1 POR and BOR
      2. 4.1.2 NMI and Hard Fault
      3. 4.1.3 I/O ESD and Settings
    2. 4.2 Emission Reduction Features
      1. 4.2.1 Clock Source
      2. 4.2.2 Power Modes
      3. 4.2.3 Package
  8. 5Analysis for EMS Test
    1. 5.1 Root Cause Analysis
      1. 5.1.1 Permanent Damage
      2. 5.1.2 Recoverable Malfunction
    2. 5.2 Debug Flow
  9. 6Analysis for EMI Test
    1. 6.1 Root Cause Analysis
      1. 6.1.1 Power Line
      2. 6.1.2 External Vcore
    2. 6.2 Debug Flow
  10. 7Summary
  11. 8References
  12. 9Revision History

5.2 Debug Flow

The key idea for the EMS debug flow is to classify the EMS failure into a typical root cause category in Table 5-1. Then, find the propagation path with assert signals or dirct checking. Lastly, use software and hardware change to help overcome the electrical stress.

  1. Make sure to consistently recreate the EMS failure and locate the process point where the issue happens.
  2. Check whether an oscilloscope or a logic analyzer can be used without being affected by test noise. If this is possible, then you can check the IO signals, power and reset pin directly to find the overspec conditions, without using assert signals. This can help to find the propagation path directly.
  3. Check whether this is a permanent damage issue or a recoverable malfunction issue. If this is a permanent damage issue, MCU function check can easily find the propagation path through locating the MCU damage point (Pin or VDD). The next step is to find a solution to overcome the issue, using IO status software change or hardware modifications. For a recoverable malfunction issue, we still need to find the propagation path or the the overspec conditions through the steps bellow.
  4. Disable BSL in NONMAIN configuration and then check if the MCU is in a reset state or has entered the default handler with an assert signal. If MCU enters the default handler and reset is acceptable, please add a software reset in the default handler. Here are some methods to check the MCU states.
    • MCU is in a reset state:
      1. Output clock signal to see whether the signal stops for a while.
      2. Add a GPIO toggle at the top of main function to see if the GPIO toggles.
      3. Connect the device without re-programming or resetting, and then check RSTSOURCE register to know the reset source.
    • MCU has entered the default handler, triggered by NMI or Hard Fault:
      1. Output clock signal to see whether the signal does not stop.
      2. Connect the device without programming or a reset to check whether the code is running in default handler and read the stack to know from where CPU jumps to hard fault handler.
  5. Check whether IO status software change can fix the issue.
    • Only enable a GPIO to toggle and keep other GPIOs in default state (Hiz mode). This GPIO is used to show whether the device still reset or enter the default handler. If the EMS failure disappears, then enable functions one by one to see which IO is the propagation path.
  6. Do temporary hardware modifications.
    • Firstly, check whether the noise is from power line. Add strong protections to MCU power using the passive protection components as shown in Table 3-2. If the problem is solved, then enable functions one by one to see whether the problem is solved.

    • Secondly, physically isolate MCU IOs by removing the resistors or NPNs one by one to find which IO is the propagation path. Then add passive protection components shown in Table 3-2 to check whether the problem is solved.