Zero-footprint RVS tools such as RapiCoverZero reconstruct information on the behavior of an application when it runs by using branch trace information captured from the hardware the application is running on and combining this with information obtained from a disassembly of the application.
For zero-footprint RVS tools to be able to analyze an application, the combination of the target and any debuggers being used must be capable of streaming a branch trace without gaps to ensure that the full program trace can be reconstructed. A Platform Support Package (PSP) is also needed for RVS to interface with the development environment, including the target hardware and trace capture mechanisms, in order to convert the branch trace into a format that the RVS tool understands. The OS being used also needs to make context switches visible. For some systems, supporting this may require modifications to be made to the OS.
Here are some examples of PSPs that we've prepared:
- No OS on x86 in QEMU*
- No OS on ZCU102 with Lauterbach® TRACE32® debugger
- FreeRTOS on ARM M3 in QEMU*
- FreeRTOS on R-Car Salvator-X with PARTNER-Jet2 debugger
- FreeRTOS on ZCU102 with Lauterbach TRACE32 debugger
- RV850 RTOS on RT850G4M with Lauterbach TRACE32 debugger
- eMCOS on R-Car Salvator-X with PARTNER-Jet2 debugger
* Modified version of QEMU, which is available within RVS. A patch is also available to update existing versions of QEMU to be compatible.
For more information, and to see if we can add support for your development environment, contact email@example.com.