Support Overview

Supported Compilers

For information about supported EWRISCV (Embedded Workbench for RISC-V) compiler/environment versions, see Compilers.

Importing Projects

You can import projects by using the cpptesttrace utility. See Importing Projects for more information.

Support Components

The following components are provided to facilitate the testing of IAR Embedded Workbench projects:

• Compiler configurations for specific supported versions of IAR compiler for RISC-V (listed above).
• "IAR_iccriscv32.mk" – Runtime library build configuration file for building the C++test Runtime Library with IAR RISC-V compiler versions starting from v. 3.30.x using 'make'. This version targets 32-bit RISC-V processors.
  • By default, this configuration targets RV32GC and a full DLIB configuration. It is expected that you customize the core configuration and C++ library being used.
• "IAR_iccriscv64.mk" – Runtime library build configuration file for building the C++test Runtime Library with IAR RISC-V compiler versions starting from v. 3.30.x using 'make'. This version targets 64-bit RISC-V processors.
  • By default, this configuration targets RV64GC and a full DLIB configuration. It is expected that you customize the core configuration and C++ library being used.
• Test configurations prepared for launching Unit & App Testing on C-SPY Simulator:
  • Run IAR EW Tests (Batch Template) - uses EW-generated batch scripts ('.cspy.bat') to launch the simulator.
  • Run IAR EW Application with Mem Monitoring (Batch Template) - uses EW-generated batch scripts ('.cspy.bat') to launch the simulator.
  • Run IAR RISC-V Tests - a pure manual simulator configuration.
    • The default core configuration is RV32IMAFDCN. It is expected that you customize this configuration.
  • Run IAR RISC-V Application with Mem Monitoring - a pure manual simulator configuration.
    • The default core configuration is RV32IMAFDCN. It is expected that you customize this configuration.