PQIII Debugger

PQIII Debugger

PQIII Debugger TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... ICD In-Circuit Debugger ................................................................................................................ Processor Architecture Manuals .............................................................................................. PQIII .......................................................................................................................................... PQIII Debugger ..................................................................................................................... 1 Introduction ....................................................................................................................... 4 Brief Overview of Documents for New Users 4 Warning .............................................................................................................................. 5 Target Design Requirement/Recommendations ............................................................ 6 General 6 Quick Start ......................................................................................................................... 7 Troubleshooting ................................................................................................................ 8 SYStem.Up Errors 8 FAQ ..................................................................................................................................... 9 Configuration ..................................................................................................................... 10 System Overview 10 PowerPC MPC85XX/QorIQ specific Implementations .................................................... 11 Breakpoints 11 Software Breakpoints 11 On-chip Breakpoints 11 Breakpoints on Program Addresses 12 Breakpoints on Data Addresses 12 Breakpoints on Data Access at Program Address 13 Breakpoints on Data Value 13 Access Classes 15 Access Classes to Memory and Memory Mapped Resources 15 Access Classes to Other Addressable Core and Peripheral Resources 16 Cache 16 Memory Coherency 16 MESI States and Cache Status Flags 18 Viewing Cache Contents 18 Debugging Information 19 ©1989-2021 Lauterbach GmbH PQIII Debugger 1 Multicore Debugging e500 cores 20 SMP Debugging 20 AMP Debugging 20 Synchronous stop of both e500 cores Programming Flash on MPC85XX / QorIQ P10XX/P20XX, PSC93XX 21 On-chip Trace on MPC85XX/QorIQ 21 PowerPC MPC85XX/QorIQ specific SYStem Commands .............................................. 23 SYStem.BdmClock Set BDM clock frequency 23 SYStem.CONFIG.state Display target configuration 23 SYStem.CONFIG Configure debugger according to target topology 24 SYStem.CONFIG.CHKSTPIN Control pin 8 of debug connector 27 SYStem.CONFIG.DriverStrength Configure driver strength of TCK pin 28 SYStem.CONFIG.QACK Control QACK pin 28 SYStem.CPU Select the target processor 29 SYStem.LOCK Lock and tristate the debug port 29 SYStem.MemAccess Run-time memory access (non-intrusive) 30 SYStem.Mode Select operation mode 31 CPU specific SYStem.Option Commands ....................................................................... 32 SYStem.Option.CINTDebug Enable debugging of critical interrupts 32 SYStem.Option CoreStandBy On-the-fly breakpoint setup 32 SYStem.Option DCFREEZE Prevent data cache line load/flush in debug mode 32 SYStem.Option DCREAD Read from data cache 33 SYStem.Option DUALPORT Implicitly use run-time memory access 33 SYStem.Option FREEZE Freeze system timers on debug events 34 SYStem.Option HOOK Compare PC to hook address 34 SYStem.Option ICFLUSH Invalidate instruction cache before go and step 34 SYStem.Option ICREAD Read from instruction cache 35 SYStem.Option IMASKASM Disable interrupts while single stepping 35 SYStem.Option IMASKHLL Disable interrupts while HLL single stepping 35 SYStem.Option MMUSPACES Separate address spaces by space IDs 36 SYStem.Option NoDebugStop Disable JTAG stop on debug events 36 SYStem.Option NOTRAP Use alternative software breakpoint instruction 37 SYStem.Option OVERLAY Enable overlay support 38 SYStem.Option.PERSTOP Stop on-chip peripherals in debug mode 38 SYStem.Option RESetBehavior Set behavior when target reset detected 39 SYStem.Option SLOWRESET Relaxed reset timing 39 SYStem.Option STEPSOFT Use alternative method for ASM single step 39 CPU specific MMU Commands ........................................................................................ 41 MMU.DUMP Page wise display of MMU translation table 41 MMU.List Compact display of MMU translation table 43 MMU.SCAN Load MMU table from CPU 45 MMU.Set Set an MMU TLB entry 46 ©1989-2021 Lauterbach GmbH PQIII Debugger 2 CPU specific BenchMarkCounter Commands ................................................................ 47 BMC.FREEZE Freeze counters while core halted 47 BMC.<counter>.FREEZE Freeze counter in certain core states 47 BMC.<counter>.SIZE No function 48 CPU specific TrOnchip Commands .................................................................................49 TrOnchip.CONVert Adjust range breakpoint in on-chip resource 49 TrOnchip.DISable Disable NEXUS trace register control 49 TrOnchip.ENable Enable NEXUS trace register control 50 TrOnchip.RESet Reset on-chip trigger settings 50 TrOnchip.Set Enable special on-chip breakpoints 51 TrOnchip.VarCONVert Adjust HLL breakpoint in on-chip resource 52 TrOnchip.state View on-chip trigger setup window 53 MPC85XX/QorIQ Specific On-chip Trace Settings ......................................................... 54 Onchip.Mode.IFSel Select interface to be traced 54 JTAG Connector ................................................................................................................ 55 Mechanical Description 55 JTAG Connector MPC85XX (COP) 55 ©1989-2021 Lauterbach GmbH PQIII Debugger 3 PQIII Debugger Version 30-Apr-2021 Introduction This document describes the processor specific settings and features of TRACE32-ICD for the following CPU families: • Freescale PowerQuicc III Series MPC85XX • Freescale QorIQ P101x, P102x, P2010, P2020 • Freescale Qonverge PSC91XX, PSC92XX series Please keep in mind that only the Processor Architecture Manual (the document you are reading at the moment) is CPU specific, while all other parts of the online help are generic for all CPUs supported by Lauterbach. So if there are questions related to the CPU, the Processor Architecture Manual should be your first choice. If some of the described functions, options, signals or connections in this Processor Architecture Manual are only valid for a single CPU or for specific families, the name(s) of the family(ies) is added in brackets. Brief Overview of Documents for New Users Architecture-independent information: • “Debugger Basics - Training” (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger. • “T32Start” (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows. • “General Commands” (general_ref_<x>.pdf): Alphabetic list of debug commands. Architecture-specific information: • “Processor Architecture Manuals”: These manuals describe commands that are specific for the processor architecture supported by your debug cable. To access the manual for your processor architecture, proceed as follows: - Choose Help menu > Processor Architecture Manual. • “OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating system-aware debugging. The appropriate OS Awareness manual informs you how to enable the OS-aware debugging. ©1989-2021 Lauterbach GmbH PQIII Debugger 4 Warning Signal Level NOTE: The debugger drives the output pins of the BDM/JTAG/COP connector with the same level as detected on the VCCS pin. If the debug/trace I/O pins of the processor are operating at e.g. 3.3 V, then VCCS should be connected to 3.3 V as well. See also System.up Errors. ESD Protection WARNING: To prevent debugger and target from damage it is recommended to connect or disconnect the debug cable only while the target power is OFF. Recommendation for the software start: 1. Disconnect the debug cable from the target while the target power is off. 2. Connect the host system, the TRACE32 hardware and the debug cable. 3. Power ON the TRACE32 hardware. 4. Start the TRACE32 software to load the debugger firmware. 5. Connect the debug cable to the target. 6. Switch the target power ON. 7. Configure your debugger e.g. via a start-up script. Power down: 1. Switch off the target power. 2. Disconnect the debug cable from the target. 3. Close the TRACE32 software. 4. Power OFF the TRACE32 hardware. ©1989-2021 Lauterbach GmbH PQIII Debugger 5 Target Design Requirement/Recommendations General • Locate the BDM/JTAG/COP connector as close as possible to the processor to minimize the capacitive influence of the trace length and cross coupling of noise onto the JTAG signals. Don’t put any capacitors (or RC combinations) on the JTAG lines. • Connect TDI, TDO, TMS and TCK directly to the CPU. Buffers on the JTAG lines will add delays and will reduce the maximum possible JTAG frequency. If you need to use buffers, select ones with little delay. Most CPUs will support JTAG above 30 MHz, and you might want to use high frequencies for optimized download performance. • Ensure that JTAG HRESET is connected directly to the HRESET of the processor. This will provide the

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    55 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us