# Debug AOP script

Source: [https://docs.qualcomm.com/doc/80-88500-3/topic/82_Debug_AOP_script.html](https://docs.qualcomm.com/doc/80-88500-3/topic/82_Debug_AOP_script.html)

1. Save dump
    - In a live debug setup, from the AOP TRACE32 window, stop the process and run the following command to save a dump.

            do <aop build>\aop_proc\core\bsp\aop\scripts\aop_dump.cmmCopy to clipboard
    - An AOP dump is also a part of the RAM dump collected after a system crash.
2. Load dump
    - Run the following command to load an AOP dump into a TRACE32 simulator.

            do <aop build>\aop_proc\core\bsp\aop\scripts\aop_load_dump.cmm <dump path>Copy to clipboard
3. Parse AOP `ulog`
    1. Run the following command from AOP TRACE32 – live or simulator.

            do <aop build>\aop_proc\core\power\ulog\scripts\aop_ulogdump.cmm <output path>Copy to clipboard
    2. Run the following command from an MS-DOS console.

            <aop build>\aop_proc\core\bsp\aop\scripts\aop_log_hfam.py -f "<path>\AOP External Log.ulog“ -tbl <aop build>\aop_proc\core\api\debugtrace\tracer_event_tbl.h  > AOP_ulog_parsed.txtCopy to clipboard

**Parent Topic:** [RPMh debugging](https://docs.qualcomm.com/doc/80-88500-3/topic/81_RPMh_hardening_and_debugging_.html)

Last Published: Sep 26, 2023

[Previous Topic
Debug with Hansei RAM dump parser](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/debug_with_hansei_ram_dump_parser.md) [Next Topic
Debug ARC (RPMh hardware block)](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/debugging_rpmh_hardware_block_arc.md)