Hardware Debugging Tools

In-Circuit Emulators - ICEs

JTAG Debuggers

BDM Debuggers

During the 15 years period that we've been dealing in the emulators market, we have aquired an undisputable reputation of first-rate, top-quality tools suppliers. This is due to the fact that we always endeavour to provide our customers with the best products money can buy: powerful, easy-to-operate, complying to state-of-the-art standards, fully-equipped for stand-alone and in-target debugging.
Emulators can be used for both target and code debugging, thus offering the best and most efficient capabilities for both HW and SW development.

In-Circuit Emulators - ICEs

• In-Circuit Emulators: can be plugged-in into the CPU target socket, act like a CPU and work together with the target board
• Real-time Emulators: code is running as with a regular CPU, without any additional delay
• Overlay or Emulation Memory: RAM memory located in the emulators; here can be downloaded
  • all of code/data
    • when running in stand-alone mode
    • when there are no memory devices on the target board
  • code that is usually programmed in EPROM devices and might be modified in the debugging process; downloading to Emulation Memory avoids repeated programming of the EPROM devices
• Breakpoints System:
  • the emulator can be stopped at certain set-by-user points in the program
    • on performing a Fetch
    • on performing Memory/I/O Access: Data Read and/or Write, DMA, I/O Read and/or Write, a.s.o; these breakpoints can be conditionned and/or passed-over a pre-set number of times
  • Hardware breakpoints
  • Software breakpoints
  • Single Step
  • Step Over Procedures
  • Run Until Return
• Trace Buffer
  • Every Bus-Cycle is recorded in a Frame
  • Trace Data can be displayed as Raw/Assembly/Source code
  • Trace Information shown: Frame#, Address#, Assembly Instruction, Bus Status, Time Stamp
  • Recorded Data can be filtered by:
    • Trace Trigger: when the Trace begins to record
    • Trace Qualifier: what is recorded in the Trace
  • Signals external to CPU can be recorded and viewd, as Bytes and/or Waveforms
  • Other Functions:
    • Code Coverage: finds not-executed code
    • Profiler: shows, in %, the time spent to execute functions, procedures

• Powerful Debugger
  • Source Level Debugging
  • Windows Interface (95/Nt, 3.11)
  • Special Windows for:
    • Source Files
    • Disassembly
    • Watches
    • Real Watches
    • Local Variables
    • SFR's
    • Memory\Dump
    • Project Files
    • Trace
    • Stack
  • Several C-Compilers Compatibility
  • Direct Acces to Compiling Tools
  • Direct Source File Editting

JTAG Debuggers, BDM Debuggers

• use the CPU internal debgging module
• do not have overlay memory
• use target memory to download code and store data
• do not interfere with customer's application
• communicate with target via JTAG\BDM connector
• oftenly offer the option to add capabilities like:
  • trace
  • port analyzer
  • logic analyzer
• have many of the In-Circuit Emulators features

Supported Processors/CPU's and their In-Circuit Emulators (ICE), HW Debuggers (JTAG\BDM), SW Debuggers (ROM-Monitors, Simulators), Compilers, RTOS's

•  8,16,32,64 Bit: AMD(8,16,32 bit), ARM(32 bit), ATMEL(8, 32 bit), DALLAS(8 bit), FASELEC(8 bit), HITACHI(8,16,32 bit), IBM(32,64 bit), IDT(64 bit), INFINEON(8,16,32 bit), INTEL(8,16,32,64 bit), MHS(8 bit), MITSUBISHI(16 bit), MOTOROLA(8,16,32,64 bit), NEC(8,16 bit), NS(16 bit), OKI(8 bit), PHILIPS(8,16 bit), SGS-THOMPSON(16 bit),SMC(8 bit), TOSHIBA(8,16 bit), ZILOG(8 bit)

• DSP: MOTOROLA(56xxx), TI(TEXAS INSTRUMENTS - TMS320)

Home   About Itec   Contact Info  Bus Analyzers   Programmers
   Debuggers (ROM-Monitors, Simulators)    Editors/CASE TOOLS/Compilers/RTOS
Development Boards  What's New

©1999 Itec Ltd.
Questions? Comments? Suggestions? webmaster@itec.co.il
last modified: 09/01/05
URL: http://www.itec.co.il