Charles Brokish Field Design Applications ABSTRACT software devel

The Datasheet Archive - 100 Million Datasheets from 7500 Manufacturers.

Charles Brokish Field Design Applications ABSTRACT software devel

Datasheet Thumbnail

Top Searches for this datasheet

Emulation Fundamentals TI's Solutions
Charles Brokish Field Design Applications
ABSTRACT software development, perhaps most critical, least predictable stage process debugging. Many factors come into play when debugging software applications. Among these factors, time utmost importance. Texas Instruments (TI) emulator saves time integrating hardware software portions user's application. Time required debug software application have major impacts time-to-market, meeting customer expectations, ultimately, financial impact well developed product which captures market share. debuggers allow extensive visibility into processors, their registers, application's software. This visibility allows software engineer understand what changes taking place inside processor application executes. software engineer breakpoints application based hardware signal values software locations within application. these breakpoints, user understand state processor data determine their application still operating correctly. They also perform benchmarking (timing analysis) profiling (CPU loading) their application software within emulator. Multiprocessor debug allow user debug software several processors same time, provides method stopping multiple processors based condition another processor: allowing user capture entire system state time question. capabilities mentioned, many more within debuggers greatly reduce debugging time software development cycle. This paper will explain fundamentals emulation logic emulation tools work together with digital signal processors. understanding fundamentals emulation, will able accelerate process setting performing software debug. This knowledge will also troubleshooting potential problems your debugging setup. This paper will explain setup emulator hardware systems single multiprocessor applications. will also explain system components interact during debug. troubleshooting guide will provided assist commonly found setup problems. Contents Hardware Setup Introduction General Understanding Signal Descriptions Software Setup Board Configuration Information Single Processor Debug Multiprocessor Debug 2.3.1 Homogeneous Multiprocessor Debug 2.3.2 Heterogeneous Multiprocessor Debug Scanning through Non-debug JTAG devices
SPRA439A
Establishing Communication With Your Emulation Hardware Target Hardware Setup Physical Space Your Emulation Hardware Invoking Emulation-Reset Invoking Emulation Debugger Using Parallel Debug Manager Troubleshooting Emulation Setup Errors Emulation Reset Errors Emulator Errors Troubleshooting Guide Other Debugging Diagnostic Tools Third Party Tools Bulletin Board Tools Future Tools Development References List Figures
Figure Connecting XDS510 Card Your Target System Figure Connecting XDS510-PP Your Target System Figure Connecting XDS510-WS Your Target System Figure Emulator Connections Without Signal Buffering Figure Emulator Connections With Signal Buffering Figure Startup Screen Code Composer Studio Setup Figure Specifying Board Name Within CC_Setup Figure Specifying Physical Address Emulation Hardware With CC_Setup Figure Specifying Processor Configuration Within CC_Setup Figure Viewing System Configuration Within CC_Setup Figure Emulator Connections Multiprocessor Systems Figure Specifying Multiprocessor Configuration Within CC_Setup Figure Viewing Multiprocessor Configuration Within CC_Setup Figure Specifying Heterogeneous Multiprocessor Configuration Figure Specifying Processors Heterogeneous Multiprocessor Configuration Figure Viewing Heterogeneous Multiprocessor Configuration Figure Specifying NON-Emulation Devices BYPASS Mode Figure Opening Debug Sessions from Parallel Debug Manager Figure Parallel Debug Manager List Tables Table Table Table Table Table Standard Controller JTAG Signals Connection Verification JTAG Signals Advanced Emulation JTAG Signals Signal Activity Connectivity Verification Troubleshooting Guide Emulation Errors
Emulation Fundamentals TI's Solutions
SPRA439A
Hardware Setup
understand workings emulation logic processors, first necessary understand what emulation consists This section will cover setup hardware into your host operating system.
Introduction
When using debugger software debugging hardware platform, necessary perform setup procedures ensure proper working target processor with XDS510. emulation setup comprised tools: emulator (XDS510), which controls information flow from target, debugger, which user interface this information. Beyond emulation setup target processor. emulation logic within processors uses Joint Test Action Group (JTAG) standard connection procuring debug information from within processor. This section intended cover basics ensuring proper communication setup between emulation hardware target processor.
General Understanding
Debug hardware performed stopping core enable information scanned into device JTAG header. This information transferred serially through JTAG port following IEEE 1149.1 JTAG specifications. important understand that this debug method near real time, intrusive, require that core halted scan information. While connection JTAG header same, scan chains used emulation purposes different from those used boundary scan. Internally processor, there various serial scan chains which information scanned into control which scan chain used what information contained each scan chain, performed microprocessor. This "scan manager" task controlling this information scanned from various processors scan chain, directing from various debugger windows. host emulator acts scan manager controls delivery scan information from target debugger window. operating system JTAG connection being made through card (Figure XDS510PP (Figure host emulation hardware microprocessor (i.e., Pentium processor). However, JTAG connection through another hardware interface operating system UNIX workstation (Figure JTAG connection utilizes separate processor control scan information. When host CPU, separate processor controls JTAG scan information, they need supplied with information regarding devices included scan chain.
Pentium trademark Intel Corporation.
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Connecting XDS510 Card Your Target System
Figure Connecting XDS510-PP Your Target System
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Connecting XDS510-WS Your Target System This information regarding scan control available host Dynamically Linked Libraries, otherwise known files. information passed XDS510-WS form separate file when performing emulation reset. We'll discuss this utility more section 3.3. Additional information regarding physical connection XDS510 debugger interfaces available documentation that shipped with product. Other helpful information found other locations within Texas Instruments, such Bulletin Board Internet Homepage. third parties making other emulation interfaces available, including PCMCIA Ethernet connections. With these connection methods, scan management performed host computer external processor, respectively.
Signal Descriptions
There five standard signals ground used JTAG connections control JTAG Test Access Port (TAP) Controller, defined IEEE 1149.1 standard. These signals shown Table also uses other signals provided JTAG header method confirming proper connection emulation hardware (Table Presence Detect signal Test Clock Return used confirm presence target device proper functioning signals from XDS510 pod. will discuss their functionality further when discuss EMURST trouble-shooting hardware problems.
Emulation Fundamentals TI's Solutions
SPRA439A
Table Standard Controller JTAG Signals
Signal Name TRST Input, Output Description Test Reset Test Mode Select Test Data Input Test Data Output Test Clock clock provided XDS510 pod) Ground Emulator Signal Type* Target Signal Type*
Table Connection Verification JTAG Signals
Signal Name Description Emulator Signal Type* Target Signal Type*
TCK_RET
Test Clock Return (Buffered un-buffered connection coming back from target) Presence Detect
PD(Vcc) Input, Output
Additionally, Texas Instruments adds more signals JTAG header, which used advanced emulation capability. These signals, shown Table provide capability perform benchmarking, software profiling multiprocessor emulation with interprocessor breakpoint capabilities. Table Advanced Emulation JTAG Signals
Signal Name EMU0 EMU1 Input, Output Description Emulation Emulation Emulator Signal Type* Target Signal Type*
signals detailed source debugger user's guide your platform. These signals used emulator provide clocking information performing software benchmarking software profiling. They also used with ANALYSIS window debugger assist multiprocessor debugging. Setup these signals multiprocessor debugging done within Parallel Debug Manager (PDM), which will discussed further section 3.5. signals both input output target. They used output driven device result breakpoint conditions being met. They also used inputs monitored debugging logic. This allows core signal, another device devices) break result.
Emulation Fundamentals TI's Solutions
SPRA439A
Figure demonstrates common connection these signals user's hardware design. processor inches more from JTAG header, there could degradation signal loading signal path. this case, should buffers drive signals maintain suitable signal quality ensure proper emulation (Figure
Figure Emulator Connections Without Signal Buffering
Figure Emulator Connections With Signal Buffering
Software Setup
software your computer must recognize devices that physically located within JTAG scan-chain. tool used perform this function called Code Composer StudioSetup. typically installed within your desktop icon executes program called "CC_Setup.exe". this section, will explain designate which specific target[s] have within your system.
Code Composer Studio trademark Texas Instruments.
Emulation Fundamentals TI's Solutions
SPRA439A
Board Configuration Information
information regarding scan chain entered through Code Composer Studio Setup (CC_Setup). This program allows user enter their names target processors, default names simply indicate which processor[s] scan chain. When starting CC_Setup, user will screen with three sections that allow user enter information regarding board System Configuration, available board/simulator types, driver installation shown Figure selecting dragging available device from center column into left-hand column, user begin process describing their system configuration.
Figure Startup Screen Code Composer Studio Setup
Single Processor Debug
only single device included scan chain, signals connected shown Figure Figure this case, debugger specifying device family target processor, then providing information regarding physical connection emulation hardware. also possible software debug multiple targets. will discuss this further next section. When specifying target device, should able find descriptor device family connection method from center column. example, will show TMS320C55x device being connected XDS510 hardware. will start dragging appropriate target from center column left column dropping under System". Upon doing this, will dialog asking additional information. First description Board Name. default, select (Figure
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Specifying Board Name Within CC_Setup Next, need specify physical address which emulation hardware connected within host computer. default address hardware address 0x240 (Figure
Figure Specifying Physical Address Emulation Hardware With CC_Setup
Emulation Fundamentals TI's Solutions
SPRA439A
must then enter processor configuration. single-processor setup, this simply means selecting device from processor family have chosen, clicking "Add Single". accept default processor name, create (Figure
Figure Specifying Processor Configuration Within CC_Setup When finished, click "Finish" button your setup should shown left-hand column (Figure 10).
Figure Viewing System Configuration Within CC_Setup
Emulation Fundamentals TI's Solutions
SPRA439A
Multiprocessor Debug
When multiple devices included scan chain, data needs scanned serially through devices. signals connected shown Figure
Figure Emulator Connections Multiprocessor Systems discussed section 1.2, scan manager controls bits that scanned into scan chain that information directed correct target processor well data coming being directed proper debugger session. this reason, imperative that scan manager know exactly which devices scan chain what order they Devices should entered order which they physically located within JTAG scan chain (from TDO).
2.3.1
Homogeneous Multiprocessor Debug
When multiple processors same type used same scan chain, each processor must have unique name, must have same definition that processor. this case, either "Add Multiple" button from Figure ("Specifying Processor Configuration within CC_Setup"), which case processor names will simply named sequentially, enter names specify "Add Single" after each name entered shown Figure stated earlier, devices should entered order which they physically located within JTAG scan chain (from TDO).
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Specifying Multiprocessor Configuration Within CC_Setup resulting System Configuration this system shown Figure
Figure Viewing Multiprocessor Configuration Within CC_Setup
2.3.2
Heterogeneous Multiprocessor Debug
When multiple processors debugged from different processor families, necessary system "Heterogeneous Multi-Processor Debug". Each processor must have unique name, must have appropriate definition that processor. When setting system Heterogeneous Debug, "Available Board/Simulator Type" selected must capable supporting processors from different families. specifically identify which families supported within driver selected viewing right-hand window pane details driver, including "Processors Supported" (Figure 14).
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Specifying Heterogeneous Multiprocessor Configuration processors that using your heterogeneous processor system listed being supported with available drivers, please contact Texas Instruments Technical Support more assistance. Figure shows system setup with TMS320C54xDSP device TMS470R1x microcontroller device. this case, select device from "Available Processors", either select default name enter name before pressing "Add Single". Upon completing entry individual devices within scan chain, your system configuration should complete (Figure 16).
TMS320C54x trademark Texas Instruments.
Emulation Fundamentals TI's Solutions
SPRA439A
Figure Specifying Processors Heterogeneous Multiprocessor Configuration
Figure Viewing Heterogeneous Multiprocessor Configuration Upon exiting CC_Setup, information contained System Configuration converted into binary format emulation scan manager.
Scanning Through Non-debug JTAG devices
also possible scan information through JTAG ports devices that being debugged Emulator. This condition arises customer wants perform Boundary Scan devices within their target board. Boundary scan performed using JTAG header well, uses different software than used TI's emulation. When devices included JTAG scan path being emulated, possible scan emulation information through these devices putting them BYPASS mode. first necessary understand large their JTAG Instruction Registers are.
Emulation Fundamentals TI's Solutions
SPRA439A
Figure shows example design which devices exist JTAG scan path that being emulated, placed BYPASS mode.
Figure Specifying NON-Emulation Devices BYPASS Mode this case, bypass devices named "Other" have JTAG instruction register bits length. This information passed scan manager such that JTAG registers bypass through these devices. Note also, that chip front descriptor this case "Boundary Scan Device") bypass devices shows with "?", indicating that emulation software knows nothing device other than JTAG instruction register length.
Establishing Communication With Your Emulation Hardware Target
Once have installed your emulator hardware your board configuration, time establish communication with hardware from your host computer. This section will explain some files used confirm connectivity hardware.
Hardware Setup
Before executing files, make sure that your emulator according directions that were included shipping. Make sure that 14-pin JTAG header connected from emulator target, that emulator connected your host computer appropriate means (ISA card, Parallel Port, SCSI bus, etc.), depending which emulator using.
Emulation Fundamentals TI's Solutions
SPRA439A
Physical Space Your Emulation Hardware
sure confirm physical address emulator your host computer. using slot XDS510 will require bytes space comes shipped with default setting 0x0240 0x025F. this space already taken within your board addressed elsewhere space (0x0280, 0x0320, 0x0340). Similarly, using XDS510-PP, default address will 0x0378. default SCSI address XDS510-WS address XDS510 card XDS510-WS will require changing switches hardware default location available host computer. older versions debuggers, necessary enter environment variables specify physical address emulation hardware. However, should necessary environment variables this purpose when using Code Composer Studio that information entered within CC_Setup.
Invoking Emulation-Reset
able invoke Emulation-Reset software. Depending which debugging software using, emulation-reset software have different name. program that ships with Code Composer Studio ResetXDS510.exe, while older debuggers included software EMURST.exe. addition resetting internal emulation debugging logic, this software several other functions. functions performed emulation-reset software are: Checks correct address emulator hardware. Verifies that there debugger currently running multiprocessor mode (OS/2). Resets Test Controller. Checks power exists Presence Detect pin. not, pulls TRST_ high generates error message "CANNOT DETECT TARGET POWER". power, then software pulls TRST_ low, then high. device Test Logic Reset (TLR). Check device TLR. not, create error message "XDS510 RESET FAILED". external processor performing scan management (XDS510-WS), then download specified .OUT file scan manager. most cases, this setup goes smoothly, ready begin debugging your software starting emulator.
Invoking Emulation Debugger
When invoking emulation debugger, simply need double-click Code Composer Studio icon which should execute CC_App.exe. There several parameters that passed when invoking CC_App, including specification desired GEL-file, other options. Please refer user's guide that shipped with your debugging software more information these options.
Emulation Fundamentals TI's Solutions
SPRA439A
Using Parallel Debug Manager
When debugging systems that have more than device defined, will required Parallel Debug Manager (PDM). Parallel Debug Manager provides method synchronous debugging your multiprocessor application. have configured multiprocessor system within CC_Setup, Parallel Debug Manager will automatically invoked when start CC_App. After Parallel Debug Manager invoked, spawn emulator sessions from within environment similar they invoked from icon single-processor system configuration (Figure 18). provisions that allow grouping processors within JTAG scan path, that provide debugging commands select processors, without processors being affected.
Figure Opening Debug Sessions from Parallel Debug Manager Parallel Debug Manager will allow single-point control starting stopping several processors synchronously. Synchronous debug includes ability synchronously start, stop, step processors (Figure 19). also includes ability perform global breakpoints through signals detailed section 1.3.
Figure Parallel Debug Manager Additional details Parallel Debug Manager available Source Debugger User's Guide specific processor using.
Troubleshooting Emulation Setup Errors
Emulation Reset Errors
have into errors when invoking emulation reset software, first check setup physical connection host computer make sure that power supplied target. Also, make sure that signals board buffered device more that inches from JTAG header, shown Figure also want inspect TCK_RET signal oscilloscope. This will indicate integrity signals board terms cleanliness well magnitude. weak signal TCK_RET indicate that buffers needed your system accommodate long paths. absence TCK_RET indicates connectivity problem within setup.
Emulation Fundamentals TI's Solutions
SPRA439A
Before invoking emulator, should:
Make sure note settings your physical XDS510 board regarding space that addressed. Make sure space address accordingly within Code Composer Setup. using parallel port debugger, make sure that address correctly, that parallel port your support mode which intend (i.e., SPP4, SPP8, ECP). Please refer manufacturer's instructions parallel port setup.
Errors emulation hardware address will result error message: "CANNOT DETECT TARGET POWER". Make sure inspect that have XDS510 correctly before looking errors target.
Emulator Errors
Occasionally, target will pass emulation-reset, yield errors when invoking emulator. will address some these errors possible setup conditions that might yield errors. most common problems encountered when starting emulator system configuration errors. System configuration errors will cause variety other errors. example, devices that defined within CC_Setup same, even wrong order those physical target, data errors. These errors include zeros, ones viewing data), repetitive patterns throughout registers memory displays. appears that board configuration correct within CC_Setup bits being displayed emulator zeros ones, physical connection JTAG signals should investigated. solder short across JTAG header cause signals shorted give erroneous information pin. Make sure test each JTAG signals described Table Table Monitor each signal oscilloscope determine appropriate level, changing should Table shows standard signals included JTAG header that should investigated, level that should expected each pin, depending mode operation.
Emulation Fundamentals TI's Solutions
SPRA439A
Table Signal Activity Connectivity Verification
JTAG Signal TCK_RET Level Both Both Both TRST Both Both Conditions Vcc, target board power 10.368 square-wave clock signal coming from JTAG XDS510 Duplicate TCK. this signal dirty attenuated, buffers should used JTAG signals shown Figure Controls state machine. should change every time another debug operation performed. device Run-Test/Idle mode. device Test Logic Reset state. Active-low signal. Emulation logic should reset perform emulation. This signal information that being scanned into target from emulator pod. should change levels data scanned through target. This signal reading internal information from target, should changing reflect data that being scanned out. This signal should clean zero volts.
viewing signals shown above oscilloscope, determine signals changing they should during normal emulation emulation start-up. cannot your emulator started errors, make sure monitor these signals time invoking emulator, determine there activity them.
Troubleshooting Guide
event that your emulator tools cause errors understand, have provided table allowing determine some commonly found errors emulation setup. Look first column determine error seeing, then track down possible errors listed column two.
Emulation Fundamentals TI's Solutions
SPRA439A
Table Troubleshooting Guide Emulation Errors
Problem Possible Solution Make sure that target proper voltage supplied Check that emulator board securely installed. Check that cabling securely connected between emulator target. Make sure that port address emulator hardware correctly. Make sure that emulator hardware setting port address corresponds that entered within CC_Setup. Make sure don't have another device conflicting same space your host computer.
Error Message: "CANNOT DETECT TARGET POWER"
Error Message: "CANNOT INITIALIZE TARGET!!"
Make sure that target proper voltage supplied Make sure processor RESET. Make sure that port address emulator hardware correctly(as explained above). Check that cabling securely connected between emulator target. Make sure have correctly entered board information within CC_Setup. Emulation Reset software before invoking emulator verify that emulation logic proper state.
Error Message: "Processor access timeout"
External device holding hardware HOLD signal. Processor waiting READY signal from external peripheral. Check solder connections JTAG header short circuits. Check board schematics insure proper routing JTAG signals. Make sure using correct board configuration within CC_Setup.
Data debugger screen displays zeros
Data debugger screen displays repetitive bit-patterns Data debugger screen displays random bit-patterns where specific data expected
Make sure using correct board configuration file. Check dirty signals JTAG header. Check memory definition with that debugger initialization file ensure that there memory present. Make sure that target proper voltage supplied Check that emulator board securely installed. Check that cabling securely connected between emulator target.
Error Condition: Code Composer Studio halts splash screen.(Windows only)
Emulation Fundamentals TI's Solutions
SPRA439A
Other Debugging Diagnostic Tools
Third Party Tools
Texas Instruments extensive Third Party network that develops tools Solutions. Occasionally, these companies will create their tools verifying connectivity XDS510 emulation. These tools used additional aids information described this document. Support these tools, well questions regarding their use, should directed through third party.
Bulletin Board Tools
Texas Instruments also develops special tools perform specific tasks, places them Electronic Bulletin Board free access. These tools downloaded used user's discretion. These tools provided free, such, supported. Among these tools Bulletin Board tool called XDS_DIAG.EXE. This tool very effective tool confirming connectivity XDS510, confirming devices present JTAG scan chain, verifying correctness board configuration defined CC_Setup. XDS_DIAG utility performs following functions:
Checks D_OPTIONS environment variable (used older debuggers) reports settings Detects previous Power Loss conditions Toggles TRST Resets Scan Controller Checks reports Scan Controller revision Checks scan configuration file output CC_Setup displays information about expected devices scan path, (such device part number, manufacturer etc.) also reports board configuration file found. Verifies scan path integrity Verifies core revisions various devices scan path Continuously scans pattern through scan path, allowing user hook logic analyzer oscilloscope verify signals.
XDS_DIAG utility found Bulletin Board, accessed following address browser:
Emulation Fundamentals TI's Solutions
SPRA439A
Future Tools Development
Texas Instruments dedicated development industry-leading development debug tools. such, continually developing capabilities, allowing customers increased flexibility visibility software development. Keep touch with your local distributor and/or representative stay abreast newest tools technology available. also monitor Bulletin Board Internet Homepage find capabilities announces additional developments.
References
IEEE 1149.1 (JTAG) Testability Primer (SSYA002), 1997. XDS51x Emulator Installation Guide (SPNU070), 1996. JTAG/MPSD Emulation Technical Reference (SPDU079), 1994. White Mountain DSP, MTN-510/LT Trek-510, http://www.wmdsp.com/ XDS51x Emulator Installation Guide, (SPNU070), 1996.
Emulation Fundamentals TI's Solutions
IMPORTANT NOTICE Texas Instruments subsidiaries (TI) reserve right make changes their products discontinue product service without notice, advise customers obtain latest version relevant information verify, before placing orders, that information being relied current complete. products sold subject terms conditions sale supplied time order acknowledgment, including those pertaining warranty, patent infringement, limitation liability. warrants performance products specifications applicable time sale accordance with TI's standard warranty. Testing other quality control techniques utilized extent deems necessary support this warranty. Specific testing parameters each device necessarily performed, except those mandated government requirements. Customers responsible their applications using components. order minimize risks associated with customer's applications, adequate design operating safeguards must provided customer minimize inherent procedural hazards. assumes liability applications assistance customer product design. does warrant represent that license, either express implied, granted under patent right, copyright, mask work right, other intellectual property right covering relating combination, machine, process which such products services might used. TI's publication information regarding third party's products services does constitute TI's approval, license, warranty endorsement thereof. Reproduction information data books data sheets permissible only reproduction without alteration accompanied associated warranties, conditions, limitations notices. Representation reproduction this information with alteration voids warranties provided associated product service, unfair deceptive business practice, responsible liable such use. Resale TI's products services with statements different from beyond parameters stated that product service voids express implied warranties associated product service, unfair deceptive business practice, responsible liable such use. Also see: Standard Terms Conditions Sale Semiconductor Products. www.ti.com/sc/docs/stdterms.htm
Mailing Address: Texas Instruments Post Office 655303 Dallas, Texas 75265
Copyright 2001, Texas Instruments Incorporated

Charles Brokish Field Design Applications ABSTRACT software devel

Top Searches for this datasheet

Other recent searches