At Rapita, our main interest in writing to output ports of microcontrollers is to provide an efficient means of measuring code execution times or code coverage (via our RapiTime or RapiCover tools – both part of RVS). Typically, we’d have some way of logging the values written to the output port, for example the RTBx or a logic analyzer. How do you set up an MPC5xx IO port to collect data?

It's been over a year since the release of RVS 3.0 and the introduction of RapiCover, our tool for on-target code coverage. The good news is our development team has been busy since September 2011 - and today we are proud to launch RVS 3.1. So what can you look forward to from this release? Here is an outline of the top 5 new features and improvements.

In a conversation with a colleague, I found myself wondering what was the impact of running code under Windows vs a "bare metal" x86 box. One of the nice things about working for a tool vendor is that you have the tools to hand to perform these kind of experiments "for fun".

Nested “case” labels are an obscure feature of C, and not often seen. However, examples do exist, typically hidden deep in standard library functions and our customers come across them from time to time. Here's a little article about how we recently brought support for them into RVS.

Find out about our support for continuous RVS reporting through Jenkins.

Our RVS integration with the Deos RTOS promises to offer an out-of-the-box solution, significantly reducing the effort needed to analyze timing and scheduling behavior of software hosted on Deos.