What is the SnapShot debugger?
Software and hardware problems occur in a target system during development. You often want to preserve the states of such problems.
PARTNER-Jet SnapShot Debugger can store CPU status, physical memory contains, and real-time trace data as a SnapShot file just like taking a snapshot. By creating SnapShot files, you can preserve the states of problem occurrences.
Then the SnapShot debugger reproduces the states without using the target system, by loading the snapshot file into a virtual target.
The SnapShot debugger can be used for the following cases.
-Checking and sharing the saved states of a target by multiple persons.
-Analyzing problems by utilizing the saved data.
-Utilizing the information as bug database.
-Having a distant person remotely check the saved status of a target via the network.
* The SnapShot debugger is a standard debug feature of PARTNER ver. 5.6 and later.
* It is necessary to connect PARTNER-Jet to use the SnapShot debugger.
* It is possible to use PARTNER-Jet and optional debugging software features with the SnapShot debugger.
What can the SnapShot debugger store? (In case of ARM CPU)
- CPU status
General-purpose register, Floating point register, Status register, CP15 co-processor register
- Source debug information
The name of a debug data file that was loaded in PARTNER-Jet when a SnapShot file was created.
- Physical memory
It is possible to save noncontiguous plural spaces.
- ETM trace data
The trace data in PARTNER-Jet is saved when a SnapShot file is created.
How to create SnapShot files
- 1. Set a breakpoint when the problem is occurred (e.g. System reboot handler).
- 2. When the break occurred at the breakpoint, create a SnapShot file with the debugger command.
How to refer a SnapShot file
- 1. Launch PARTNER debugger with SnapShot mode.
- 2. Load a SnapShot file with the debugger command.
Things that the SnapShot debugger can do
- Refer to/ modify the CPU Registers.
- Refer to the executed trace (ETM, AUD, etc.).
- Display the result of disassemble in the specified area.
- By loading source debug information and refer to address by symbol name and inspect display of variables.
- Supports Event Tracker
- Display the transition of task, process and thread.
- Display the user information when it is available.
- It is possible to use trace cooperation feature when it is effective.
- OS debug support (Required to have each OS debug option).
- Display the transition of task, process and thread.
- Refer to the memory of virtual machine of the process by attaching user space in Linux and Windows CE. It is possible to attach to the arbitrary process that was executed when SnapShot file was created.
- Refer to the memory in the area that the page was existed of the page on physical memory.
- Reproduce the executed trace in user space on Linux and Windows CE.
Things that the SnapShot debugger cannot do
- Execute or stop a program
- Set breakpoints (Both S/W break point and H/W breakpoint cannot be set)
- Refer to I/O register around peripherals
- Rewrite a flash memory
KMC, the KMC logo, PARTNER, PARTNER-Jet, PARTNER-JetM, exeGCC, JTAG-Ether, and Eclipse for PARTNER Cross DevKit are trademarks of Kyoto Microcomputer Co., Ltd. Product and company names mentioned herein may be trademarks of their respective companies. Product specifications are subject to change without notice. This material is provided for informational purposes only; KMC assumes no liability related to its use.
