Functional Description

This chapter lists the supported and unsupported features of vVIRTUALtarget. If a feature needs a workaround, this chapter links to a detailed description.

This section uses three classes to describe how well vVIRTUALtarget supports specific features:

  • Supported Features
    Fully functional in vVIRTUALtarget with only minor deviations from the behavior on the hardware.

  • Representable Features
    Supported API-wise, but the behavior may (considerably) deviate from hardware behavior. Representable features may, for example, not allow the simulation of a malfunction. Representable features may also require the implementation of a workaround to function.

  • Unsupported Features
    Hardware target features causing errors in the case of vVIRTUALtarget, either during configuration, code generation, compilation or runtime

Supported Features

The Technical References of the vVIRTUALtarget modules list their supported features (see references).

Representable Features

The following table gives an overview of features that vVIRTUALtarget currently supports only partially.

Table 1. Representable Features with Limited Support
BSW Module Feature Limitation Workaround

OS

Background Tasks

In background tasks the simulation time must be manually advanced. Long-running tasks that do not advance simulation time are detected by the runtime kernel and the simulation is stopped.

See Background Tasks

MCU

Handling Different MCU Clock Offsets

Offset mismatches between hardware MCU and virtual MCU must be handled by adapting code.

See Handling Different MCU Clock Offsets

NvM

NvM Block Length Strict Check

NvM Block Length Strict Check is not supported in dual-target projects due to compiler-dependent variable size differences.

See NvM Block Length Strict Check

Unsupported Features

  • Post-Build Loadable
    You can select post-build loadable as an implementation variant in VTT modules. However, vVIRTUALtarget does not support the post-build-time flash process, so you must test it on the hardware.

  • Ethernet Driver Features
    vVIRTUALtarget does not support the Ethernet feature Forwarding and Queuing for Time-Sensitive Streams (FQTSS).

  • Multiple Instances of Drivers
    You cannot instantiate virtual OS/MCAL modules multiple times in a single configuration project.

  • AUTOSAR 4.3 Crypto Driver Hardware Support
    vVIRTUALtarget does not support a Crypto driver (HW) according to AUTOSAR 4.3.

  • SoAd BSD Socket
    vVIRTUALtarget does not support BSD Socket.