RTBx data logger

Trace longer, sample faster

The RTBx data logger provides a cost-effective, easy-to-use solution for collecting and timestamping long streams of verification data from software tests run on embedded hardware. It is target-independent, supporting a wide variety of target architectures, and provides an excellent way of collecting trace data for use by RVS.

Key features

High-speed continuous processing

Log and timestamp trace data produced at high rates for days on end.

Automatically timestamp data

Remove the need for on-target timestamping procedures or hardware that causes bottlenecks in your testing.

Flexible connection strategies

Connect to almost any embedded target with a range of connection strategies.

Web-based manager

Manage the RTBx easily through a web client.

Automated tracing

Integrate into your existing continuous build environment to collect data from tests automatically.

On-the-fly filtering

RTBx filters data as it collects it, reducing downstream processing time.

Specifications

Specification	RTBx 2220	RTBx 2320^*	RTBx 2240^*	RTBx 2340^*
Signal input	Up to 32 bit		Up to 64 bit
Maximum sustained tracing rate (million ipoints/second)	250	720	250	720
Minimum ipoint separation	4 ns	2 ns	4 ns	2 ns
Sampling frequency	250 MHz	720 MHz	250 MHz	720 MHz
Storage capacity^†	500 GB
Typical continuous tracing duration	Days
Electrical signal	LVDS/TTL^‡

^*Currently under development; specification of the final model may change. ^†Additional capacity available on request. ^‡Using an adapter.

Related content

How do I connect RTBx to my target?

We supply standard cables to connect the RTBx to LVDS or TTL I/O ports. If these ports are unavailable, you may need to install adapters on your embedded board. Rapita Systems provides support on the best way to connect the RTBx to your target.

What if I don’t have a spare I/O port?

You can connect RTBx to an address bus that runs at up to 250 MHz. To do this, you must reserve a range of addresses for ipoints, with one bit reserved to indicate that the value on the address bus is an ipoint. The ipoint instrumentation writes a value to a specific address in that region to denote a specific ipoint. This approach reduces the maximum trace duration of the RTBx.

How do I collect timestamped data with the RTBx?

The RTBx automatically timestamps data it collects, using either an internal clock or that on embedded hardware. This removes the need to configure a timestamping procedure on the embedded target itself, which would incur code size and execution time overheads.

Compared to other hardware that can be used for timestamping such as debuggers and logic analyzers, the RTBx can collect trace data for far longer, meaning that it doesn't become a bottleneck in your testing.

What is the “maximum sustained tracing rate”?

This is the maximum tracing rate that can be sustained over time, calculated from the number of ipoints the RTBx can process per second. The RTBx can support a higher tracing rate for short periods of time, provided that the minimum separation between instrumentation points is met.

Will the RTBx support my processor running at x MHz?

This depends on the number of CPU cycles it takes to output successive ipoints, and the rate ipoints are written at. For example, RTBx 2220 can collect trace data via an I/O port with a minimum separation of 4 ns (250 MHz). This model can therefore support a 1 GHz CPU that outputs trace data once every 4 cycles.

Next steps

Interested in finding out more out more about the RTBx?

Schedule a call »Ask a question »

Search form