IAR Embedded Workbench for Renesas RH850

• Library support for the C++17 language standard
• Additional GNU C language extensions
• Editor and IDE enhancements including Dark Mode
• Iarbuild enhancements
• 64-bit Windows application
• Visual Studio Code support
  The IAR Build and IAR C-SPY Debug extensions available on Microsoft Marketplace enable you to work in Visual Studio Code (with IAR Embedded Workbench installed) to:
• Build IAR Embedded Workbench projects
• Run the C-STAT static analysis tool
• Debug applications using the same range of hardware/debug probes as in IAR Embedded Workbench
• Updated device support
• Updated user documentation

Support for position-independent code and ready-only data (ROPI)

When using position-independent code and ROPI, the compiler in IAR Embedded Workbench for RH850 will generate code that uses PC-relative references for addressing code and read-only data.

Updated device support

The device support files have been updated to the most recent version from Renesas.

Updated user documentation

The C/C++ Development Guide, and IDE Project Management and Building Guide have been updated to reflect the product changes.

• Updated device support
  Support has been added for the RH850/U2A, C1x, D1x, E1x and E2x series of microcontrollers.
• C18 support
  The default Standard C is now C18 (ISO/IEC 9899:2018).
• C++17 support
  The compiler now supports almost all C++17 features. The C++ library supports C++14 with no C++17 additions.
• Extended coverage of CERT C
  The static analysis tool C-STAT has extended its coverage of the SEI CERT C Coding Standard. The SEI CERT C Coding Standard's goal is to provide rules for developing safe, reliable and secure systems in the C programming language, with support for C11 constructs.
• Improved Source Browser
  The following improvements have been made to the Source Browser:
  - The source browser data is generated faster as it is now running as a separate thread.
  - New Source Browser Log window.
  - Status indicator in the status bar.
  - Enhanced feedback in case source browsing data cannot be generated.

• Documentation Comments support in the editor
  The editor can distinguish comments that start with /**, /*!, /// or //! as Documentation Comments. Inside a Documentation Comment, the editor can recognize keywords that begin with \ or @. If the keyword is recognized as a doxygen keyword, the Documentation Comment will appear in tooltips and parameter hints for variables and functions. See IAR Embedded Workbench IDE Project Management and Building Guide for more information.

• IAR Embedded Workbench IDE Project Management and Building Guide
• IAR C/C++ Development Guide
• IAR Assembler Reference Guide
• C-SPY Debugging Guide
• IAR Embedded Workbench MISRA C:2004 Reference Guide
• IAR Embedded Workbench MISRA C:1998 Reference Guide
• C-STAT Static analysis guide

Emulator support

• Renesas E1 emulator
• Renesas E20 emulator
• C-SPY Debugger simulator
• C-SPY Debugger plugin SDK available for 3rd party debuggers

RTOS support

• RTOS-aware debugging with built-in plugins.
• Micrium µC/OS-II
• OSEK Run Time Interface (ORTI)
• Segger embOS
• Express Logic
• FreeRTOS
• CMX

Each RTOS plugin installs a number of new windows in C-SPY, most importantly the task or thread list windows where task-specific breakpoints can be specified and task-specific steps executed. Different inspector windows display the contents of the internal data structures of the RTOS such as timers, queues, semaphores, resources and mailboxes.

The IAR C/C++ compilers offer different dialects of the C and C++ programming languages, as well as different extensions specific for embedded programming (please note that not all language standards are supported for all target implementations). The compiler can be instructed to disable extensions for strict conformance to the standards. 

A wide range of industry-standard debug and image formats compatible with most popular debuggers and emulators are supported. This includes ELF/DWARF where applicable.

ISO/ANSI C/C++ Compliance

The IAR C/C++ compilers adhere to a freestanding implementation of the following C programming language standards:

• INCITS/ISO/IEC 9899:2018, known as C18 (Latest version only).
• The compiler supports all C++17 features. The C++ library supports C++14 with no C++17 additions.  (Latest version only).
• ISO/IEC 14882:2015, known as C++14
• INCITS/ISO/IEC 9899:2012, known as C11
• ANSI X3.159-1989, known as C89

The ISO/ANSI C/C++ Compliance level varies between the different compilers. For complete information, please refer to the IAR C/C++ Compiler user documentation in your chosen product.

IEEE 754 standard

IAR Embedded Workbench supports the IEEE 754 standard for floating-point arithmetic.

MISRA C

MISRA C is a software development standard for the C programming language developed by MISRA, The Motor Industry Software Reliability Association. Its aims are to facilitate code safety, portability and reliability in the context of embedded systems, specifically those systems programmed in ISO C.

The first edition of the MISRA C standard, "Guidelines for the use of the C language in vehicle based software", was produced in 1998. In 2004, a second edition was produced with many substantial changes to the guidelines, including a complete renumbering of the rules. Additionally MISRA C:2012 with extended support and MISRA C++:2008 for identifying unsafe code constructs in the C++ standard have also been added to the standards.

IAR Embedded Workbench features an add-on product C-STAT so you can check compliance with rules as defined by MISRA C:2004, MISRA C++:2008 and MISRA C:2012.

Test validation

We use the following commercial test suites to test conformance of our tools to the standards:

• Plum Hall Validation test suite for ISO/IEC C conformance
• Perennial EC++ Validation Suite for C++ conformance
• Dinkum C++ Proofer to test how our libraries conform to the C and C++ standard as well as test our STL implementation against the C++ standard.

In addition to the commercial suites, we use several in-house test suites for testing new features, regression testing, corrected errors, etc.