3.2.2.12.8. Debug Information

3.2.2.12.8.1. Low Power Modes

As described in the S/W Architecture section, implementing Low Power Modes like Deep Sleep requires a synchronization between multiple software components. Debugging a LPM issue requires finding out which component (Linux, TF-A, TIFS or DM R5) might be at fault.

The comprehensive way of debugging Deep Sleep starts by looking at all the commands that have been executed by the DM R5. The steps for getting this trace and interpreting the logs has been documented in the following FAQ: How can we debug Deep Sleep on AM62x/AM62A/AM62P using SYSFW Trace?