virtual JTAG interface

Veloce vProbe App

A virtual Joint Test Action Group (JTAG) solution for debugging and testing embedded systems in emulation and enterprise prototyping. Veloce vProbe provides a software-based debug interface that can be used to connect to a target system and perform various debug operations,


Get in touch with our sales team 1-800-547-3000

Connecting a computer interface using a screwdriver.

Why the Veloce vProbe App?

Veloce vProbe enables software developers and hardware/software validation teams with a consistent framework to shift-left firmware/embedded software validation that is consistent with their post-silicon content validation. Veloce vProbe App accelerates your software development on HAV emulation and enterprise prototyping systems. By being able to develop, debug and execute your software-based workloads, vProbe is a key component in your software-based validation flow. Fully integrated with industry-leading debuggers, Veloce Vprobe provides a consistent and congruent flow from emulation to prototyping to silicon. For hardware verification teams, vProbe helps validate critical debug logic of your SoC, ensuring your debug flow is ready for your post-Si bring-up.

  • Integration with third-party software debuggers like TRACE32, Arm DS, CSAT, OpenOCD
  • Connect to standard debug interfaces and trace ports like Joint Target Action Group (JTAG), Serial Wire Debug (SWD), debug access port - advanced peripheral bus (DAP-APB), advanced high-performance bus (AHB), advanced extensible interface (AXI) or trace-port interface unit (TPIU) and more.

Key attributes

Flexibility and Scalability

The Veloce vProbe solution is designed to be highly flexible and customizable, allowing users to tailor the debug interface to their specific needs. It is also designed to be highly scalable, allowing users to debug complex systems with multiple processors and peripherals.

Engineer debugging a system on mutiple monitors.

vProbe components

Veloce vProbe consists of the server, the client and the Bus Functional Model (BFM). The vProbe server runs on the target system and provides an interface, while the vProbe client runs on a host system and provides a user interface for interacting with the debug interface.

Debugging a computer board using a hardware probe.

Debugger support

Flexibility in choosing software debuggers, such as Trace 32, OpenOCD and ARM DS, is crucial for optimizing development workflows as part of your SoC validation efforts. Veloce vProbe supports all three.

Screenshot of Veloce Visualizer debugging a design.

Discover more about the Veloce ecosystem

Related resources