CodeWarrior TAP High Performance Probe Base Unit

The CodeWarrior TAP enables target system debugging via a standard debug port (usually JTAG) while connected to a developer’s workstation via Ethernet or USB. Using the CodeWarrior TAP’s Ethernet connection, you can debug systems remotely or effectively share a single system with multiple developers When a shared system is not needed, CodeWarrior TAP connects directly to a workstation with a single USB cable via which power is supplied The CodeWarrior TAP is designed to work with CodeWarrior development tools and processors It is a critical debug tool in all phases of the project and is necessary for debugging systems prior to running a fully debugged operating system.

• The CodeWarrior TAP allows either USB or Ethernet (10/100 ) host connection for the developer workstation
• USB powered, even when using Ethernet
• Low cost removable probe tips sold separately
• Supports debugging via JTAG interface
• Automatically supports system voltage levels from 1.2 to 3.3
• Supports all available core speeds and voltages for supported NXP processors
• As a convenience feature, the CodeWarrior can connect to a target systems serial port allowing telnet access to a remotely located system and control of the U-boot program.
• In conjunction with the CodeWarrior development system, the CodeWarrior TAP:
  • Programs system flash memory during debug and development phases of the project, including most popular flash memories, but specifically all flash memories used with NXP development systems
  • Controls the target development system even when the system may have crashed during development
  • Offers complete system visibility and control, including reading/writing of CPU registers, memory mapped registers, block reading/writing of memories, single step debugging, setting software and hardware breakpoints, and monitoring target system status
  • Gives control over the target system execution, including control of one or all cores, and resets
• Contact NXP if you are interested in:
  • Integrating this probe into your software
  • Utilizing this probe as your target debug probe