TASKING VX-toolset for RH850 v2.2r1
Release Note

Scope

This release note covers the TASKING VX-toolset for RH850 v2.2r1. It describes what has been changed compared to v2.1r1.

Contents

• New in v2.2
• Fixed Issues in v2.2r1
• License Information

New in v2.2

Device support

Device support has been updated with the last status of the Renesas documentation:

• Added RH850/C1H
• Added RH850/C1M
• Added RH850/E1L
• Added RH850/E1M-S
• Added new devices to RH850/P1x
• Added new devices to RH850/R1x

Update of Eclipse IDE

The Eclipse platform and CDT have been updated to the Luna releases (Platform 4.4.1 and CDT 8.5.0). For more information, start Eclipse and open "Help" > "Help Contents". Then navigate to "Workbench User Guide" > What's new" or to "C/C++ Development User Guide" > "What's new in CDT"

Important note: In version v2.1r1 the file name suffixes for object files and libraries were incorrect .obj and .lib. This has been changed into .o and .a to match the command line tools.

Code Compaction

This release adds the Code Compaction optimization, also often known as reverse inlining. This is a size optimization. The optimization is enabled when using -O3 or with a custom optimization setting. Using the trade-off between size and speed option the effect of this optimization can be influenced.

See the User Guide options -O3 and -Or for more information

MIL Linking / Link time optimizations

The compiler now supports link-time optimizations, using the intermediate compiler code format (MIL). This allows the compiler to do a multi-file optimization. The optimization can easily be enabled in Eclipse

See the User Guide 9.1. MIL Linking for more information

Profiling support

Static (compile-time) and dynamic (run-time) profiling has been added. See the User Guide, Chapter 10. Profiling, for more information.

Hardware debugging support

Hardware debugging support has been added, using the Renesas E1 Emulator, supporting the RH850/F1x devices. To use hardware debugging a license for the Professional Edition of the TASKING VX-toolset for RH850 is required.

For debugging using the E1 Emulator it is required to install the Renesas E1-Series USB drivers before using the debugger. These drivers can be installed from the CD that comes with the E1 Emulator or from the Renesas website:
E1USBDRIVER.exe

Fixed issues for v2.2r1

New Features

• RH850VX-69 - Code compaction
• RH850VX-84 - Build for application wide optimizations (MIL linking)
• RH850VX-93 - Add profiling support
• RH850VX-248 - Update Eclipse/CDT to Luna
• RH850VX-263 - Enable mil-linking, code compaction and profiling from Eclipse
• RH850VX-280 - Add Professional Edition
• RH850VX-375 - Add board support to the debugger

Improvements

• RH850VX-252 - Update TASKING LM to v1.2
• RH850VX-290 - Optimisation : 64bit shifts can be better
• RH850VX-327 - Improve license check during installation.
• RH850VX-357 - Add .alias directive to assembler
• RH850VX-360 - Enable subscript strength reduction
• RH850VX-367 - forward store needs tuning
• RH850VX-371 - Add new C1x, E1x, P1x and R1x devices

Fixed Problems

• RH850VX-142 - interrupts : EIPC etc. need DWARF number
• RH850VX-167 - add_support for __set_EP()
• RH850VX-209 - New Welcome screen
• RH850VX-215 - Incorrect assembly when generating @ha()+@lo() combos
• RH850VX-216 - downloading fails if no section .debug_info
• RH850VX-219 - Using a 32x32->64 MUL causes internal error S 917
• RH850VX-227 - no error reported when breakpoint cannot be placed
• RH850VX-228 - 'Break on exit' does not work correctly
• RH850VX-235 - breakpoints disappear after reloading application
• RH850VX-236 - adding breakpoint via source line in Disassembly view may not work properly
• RH850VX-237 - stack breakpoint only works once
• RH850VX-241 - Assembler accepts illegal code (r0)
• RH850VX-266 - Incorrect order of parameters of .PAGE control in the manual
• RH850VX-316 - Assigning value to multi-register variable may fail (silently)
• RH850VX-324 - Remove "Generate lookup tables" (--switch=lookup) from Eclipse
• RH850VX-326 - Computer ID calculation for node locked client may fail
• RH850VX-335 - control program passes -g incorrectly to compiler
• RH850VX-338 - control program --ignore-default-library-path incorrect
• RH850VX-339 - control program --no-default-libraries option should not suppress library paths
• RH850VX-349 - __START conflicts with interrupts 0 and 1
• RH850VX-376 - Eclipse object filename suffix should be .o instead of .obj

The list of open issues for v2.2r1 can be found on the internet.

License Information

The TASKING VX-toolset for RH850 uses the TASKING license management software. In order to be able to run this toolset, you will need a license key.

See section 1.1.2.1 in the Getting Started with the TASKING VX-toolset for RH850 guide for information on obtaining a license.

Local TASKING License Server

Important Information (not applicable to evaluation licenses)

If you have ordered a TASKING product with a floating license, you can have it serviced by the Remote TASKING License Server (the most convenient solution) or through a Local TASKING License Server (in case you have no external network access for example). Consult your Altium representative for assistance on deciding what the best setup would be for your situation.

If you like to setup up a local license server, we kindly refer you for more information to Support for TASKING License Management System (TLM) on our website. Here you can also download the Local TASKING License Server package.