English is currently available.
Silicon Labs MCUs DISCUSSION
A low-power wireless board meets its MCU sleep-current target but still has excessive total standby current. How can the external sensor rail and interface lines be investigated without confusing chip-level and board-level measurements?
Reference: Silicon Labs: Energy Profiler (https://www.silabs.com/software-and-tools/simplicity-studio/energy-profiler).
Measure the board input and, where the hardware permits, the individual sensor rail. Confirm the regulator's quiescent current and each device's actual standby configuration. A sensor left in continuous conversion can outweigh the savings from a correctly sleeping MCU.
Inspect signals crossing between powered and unpowered devices. Pull-ups or driven GPIOs can feed current into a disabled rail through interface protection paths. Review voltage tolerance and power sequencing in both devices' documentation before using rail switching as the power-saving strategy.
Capture the full measurement cycle after any change, including settling and initialization. Power cycling a sensor may save standby energy but add startup cost and delay. Compare total charge per valid measurement rather than only the lowest observed sleep current.
