IAR Information Center for Renesas RX

• Important information
• New features
• Known problems
• Program corrections
• User guide corrections
• Miscellaneous
• Release history

Important information

• EZ-CUBE2 On-Chip Debug Emulator
  The EZ-CUBE2 On-Chip Debug Emulator is a new hardware product that has not yet been fully tested.

• Trace mode for the E20 emulator
  Trace support for the E20 emulator is for some device groups limited to the trace mode Trace output – Do not output (internal buffer used) as the only working mode.

New features

• None

Known Problems

• [EWRX-651] Due to limitations in J-Link software, there is currently no C-SPY support for RXv3 core devices.

• [EWRX-577] Setting and/or reading the RX MPU registers via the C-SPY Registers window is not possible using the J-link driver.

• [EW24004] C symbols are displayed in the Disassembly window without the extra underscore required by the Renesas ABI.

Program Corrections

• None

User guide corrections

• EZ-CUBE2 On-Chip Debug Emulator
  The EZ-CUBE2 On-Chip Debug Emulator is currently not documented in the C-SPY Debugging Guide but has a feature set identical to the E2 Lite emulator.

Miscellaneous

• Hot-plug adapter
  The Attach to program (hot plug-in) feature must be used with a so called "Hot-plug adapter" which allows you to connect the E1 emulator to a running user system without turning off the power. For the E20 emulator, no additional adapter is required.

• J-Link and the FINE interface
  If you are using the FINE debug interface for J-Link and get the error message "Could not detect CPU clock speed", try again with a lower FINE baud rate. If you still cannot connect you need to switch to the JTAG interface.

Release history

4.13.1 2019-11-20

New features

• EZ-CUBE2 On-Chip Debug Emulator support
  The EZ-CUBE2 On-Chip Debug Emulator, primarily targeted for the Chinese market, is now supported.

4.12.1 2019-06-18

4.11.1 2019-02-18

Program corrections

• [EWRX-588] The bool data type is not displayed with a correct value in the debugger watch windows.

4.10.2 2018-11-28

Program corrections

• [EWRX-565] It is not possible to create a new data breakpoint by choosing New Breakpoint>Data from the context menu in the Breakpoints window, because of a problem with creating correct default values for the breakpoint parameters.

4.10.1 2018-06-29

New features

• E2 emulator support
  C-SPY now supports the Renesas E2 emulator.

• Improved RTOS awareness plug-in for Amazon FreeRTOS
  Now with full control of the execution at the task level and enabling display of the local execution context for each individual task.

3.10.7 2018-01-30

Program corrections

• [EWRX-531] The byte order cannot be changed when the J-Link debug probe is used.

3.10.6 2017-11-14

3.10.4 2017-08-31

New features

• The device RX130/R5F51308 is now supported by J-Link.

3.10.3 2017-06-14

3.10.2 2017-05-15

• [EW26573] The IDE crashes for E1/E20 when the option Flash writing mode is used together with the option Execute the user program after ending the debugger.

3.10.1 2017-04-20

New features

• The add-on product C-RUN for runtime analysis is now supported.
• Enhanced Registers and Symbols windows in C-SPY.

2.90.4 2016-10-26

Program corrections

• [EW26255] C-SPY cannot to process a given USD file to upload content to a parallel flash memory for E1/E20.

New features

• The IAR C-SPY J-Link Emulator driver now also supports RX24T, RX130, RX651 and RX65N.

2.90.3 2016-07-06

Program corrections

• [EW26116] Changing the OFS1 register ends the debugging session with a fatal error for E1/E20.

• [EW26134] The device R5F51103 is using the wrong MCU file, R5F51101.MCU instead of R5F51103.MCU.

2.90.1 2016-06-08

Program corrections

• [EW26067] If C-SPY fails to set a software breakpoint during download, the debug session sometimes ends with a fatal error.

• [EW25791] RXv2 devices with more memory than 64 Kbytes are not erased and programmed correctly with J-Link.

New features

• The C-SPY J-Link driver has been re-written to support RXv2 devices.

2.80.3 2015-10-19

Program corrections

• [EW25626] The emulator message "The writing data for OFS1 register was modified to disable gStartup Voltage Monitoring 1 Reseth" is treated as a fatal error for E1/E20 but should be a warning only.

2.80.1 2015-06-30

New features

• E2 Lite emulator support
  C-SPY now supports the Renesas E2 Lite on-chip debugging emulator.
• External flash support
  You can now write data through the E1/E20 emulators to the external flash memory embedded in the system. As input, C-SPY is using external flash definition files (USD files) prepared with the External Flash Definition Editor tool from Renesas.

2.70.1 2015-02-23

Program corrections

• [EW25238] A value of a boolean variable is shown as "unavailable" in the Live Watch window.

• [EW25184] The list of external memory areas are not correctly displayed in the C-SPY E1/E20 and J-Link emulators Hardware Setup dialog box.

New features

• Saving C-SPY Watch window content
  In the C-SPY Watch window family, you can now choose Save All to File from the context menu to save the contents of the current window to a text file.

2.60.6 2014-11-04

Program corrections

• [EW25076] The debug session for E1/E20 is ended after P/E mode is set because a return code from the low level interface is treated as fatal error instead of a warning.

2.60.4 2014-09-02

Program corrections

• [EW24894] The Flash ROM and Data flash ROM memory areas are not erased properly if the Internal flash memory overwrite list box in the Hardware Setup dialog box is left empty.

• [EW24832] If cspybat is used in flash writing mode, a popup dialog is shown instead of writing the information to the console.

2.60.3 2014-06-23

Program corrections

• [EW24656] The debugger issues a fatal error if a hardware breakpoint is set while the MCU is in standby mode, deep standby or in sleep mode. This has been changed to a warning and the debugging session can continue.

• [EW24792] The emulator trace mode is not initialized correctly for the E1 and J-Link emulators.

2.60.2 2014-09-02

Program corrections

• [EW24761] The C-SPY macro __setLogBreak does not work for the C-SPY emulator drivers.

2.60.1 2014-04-15

New features

• C-SPY data trace support
  Data trace information from stack operations, data transfers, string operations, arithmetical operations, logical operations, bit operations, FPU and exceptions, is now collected and displayed in the C-SPY Trace window for hardware debugger drivers.
• New windows for C-SPY macros
  Two new C-SPY windows have been added to easier manage C-SPY macros. The Macro Registration window controls which macro files are loaded and the Debugger Macros window shows a list of all macros available in the debugger.

2.50.1 2013-12-03

2.42.2 2013-06-26

Program corrections

• [EW24181] Saving collected trace data to a text file does not work for the emulators.

2.42.1 2013-04-19

Program corrections

• [EW23830] The C-SPY features Trace and Function Trace are not working for the RX200 and RX100 series.

New features

• Sampled Graphs in C-SPY
  It is now possible to specify variables for which you want to collect data samples. You can view the sampled data either in table format in the Data Sample window or as graphs in the Sampled Graphs window.

2.41.2 2012-12-13

New features

• New core option for RX100
  
• Download changed flash blocks only
  A new project option has been added under Project Options>Debugger>E1/E20 Emulator>Download called Download changed flash blocks only. This option makes it possible to program only these flash blocks that have actually changed.
• Emulator Information window
  The new Emulator Information window shows version information about the debugger API as well as the actual emulator.

2.41.1 2012-11-27

New features

• Macro Quicklaunch window
  The new Macro Quicklaunch window makes it possible to evaluate expressions and to launch C-SPY macros. The return value from the evaluated macro or expression is shown in a separate column and the user can re-trigger the evaluation at any given point.

Program corrections

• [EW23404] The Memory Restore command did not work in some cases for the Motorola format.

2.40.2 2012-08-09

Program corrections

• [EW23392] The emulator driver was not prepared for connecting and downloading in User Boot mode. This has now been corrected. Note however that the Segger debugger API does not yet support User Boot Mode.

2.40.1 2012-06-01

New features

• Custom SFR window
  It is now possible to define custom SFR's (special function registers) in C-SPY with selectable access size and type.
• C-SPY start/stop function support
  The start/stop function available for the E1/E20 emulators makes it possible to execute specified routines of the user application immediately before starting and immediately after halting program execution.

2.30.6 2012-02-24

New features

• The progress bar shown at download is now closed if another dialog appears.

Program corrections

• [EW23037] When using the 38-pin to 14-pin conversion adapter for the E20 emulator the error message "The specified trace mode is not corresponding to the current pin count" was issued.

2.30.5 2012-02-16

New features

• E1/E20 debug support for the RX63x and RX21x groups has been added.
• C-SPY support for multiple devices on a JTAG scan chain via the J-Link emulator has been added. One device at a time can be debugged.
• Debug support for the RX63x and RX21x groups has been added for the J-Link emulator.
• The Segger J-Link software has been updated to v4.41g.

Program corrections

• [EW22761] An error in the download caching system could in rare cases cause the flash memory download to hang for E1/E20.

• [EW22713] Writing to external memory via C-SPY for E1/E20 did not work. This has now been corrected.

2.30.1 2011-06-28

New features

• Performance counters for E1 and E20
  The performance measurement facility in RX, capable of measuring execution time in specified sections of your application, is now supported in C-SPY.
• Hot Plugin for E1 and E20
  C-SPY now allows you to connect an E1 or E20 emulator to a running system to inspect it without interrupting program execution.
• Flash writing mode for E1 and E20
  It is now possible to let the emulator operate as a flash memory programmer through the flash writing mode which is now supported by C-SPY.

Program corrections

• [EW22402] When trying to load additional debug files (images), only the first image was loaded into the target.

2.20.4 2011-04-08

New features

• Mode Pin Setting E1/E20
  Set the MCU operation mode based on pin settings. The available options depend on which RX group is used. Typical options are Single-chip mode and User boot mode. The default setting is Single-chip mode.
• Register Setting E1/E20
  Set the MCU operation mode based on register settings. The available options depend on which RX group is used. Typical options are Single-chip mode, Internal ROM-enabled extension mode and Internal ROM-disabled extension mode. The default setting is Single-chip mode.
• Endian E1/E20
  Set the MCU endian type. This is available for the RX63x and RX21x groups only which do not have a fixed endian. For RX61x and RX62x the endian depends on the user system and cannot be changed by the software.
• FINE debug interface E1/E20
  Support has been added for the FINE debug interface. This is available for the RX63x and RX21x groups only.
  
• The Segger J-Link software has been updated to v4.24c.

Program corrections

• [EW22330] The emulator modes On-chip ROM enabled extended mode and On-chip ROM disabled extended mode did not work correctly. Byte order and bus width selection are now also saved and loaded through the project.dni settings file.

2.20.2 2011-01-10

Program corrections

• [EW22166] Too many registers in the debugger SFR file for the RX630 group could cause the IDE to freeze.

2.20.1 2010-12-20

New features

• Power debugging with J-Link
  Power debugging is a methodology that provides software developers with information about how the software implementation in an embedded system affects system-level power consumption. By coupling source code to power consumption, testing and tuning for power optimization is enabled. The debug probe samples the momentary current drawn by the system and feeds it to the debugger where the measured current is synchronized with time-stamped program counter values. This allows the debugger to present power consumption directly correlated to the source code. The debugger supports power data from the following sources:
  • J-Link Ultra
    Power data is measured with high accuracy at the board level. Supports calibration.
  • J-Link
    Power data is measured with low accuracy at the board level. Does not support calibration.
• C-SPY E1/E20 emulator debugger improvements
  • Live Memory and Live Watch support.
  • Possibility to set breakpoints during program execution.
  • Complex data breakpoints that are triggered when data is accessed at a specified location and under a specified condition.
  • Statistic application profiling either based on trace data (non realtime) or PC samples (realtime).
  • New Trace modes Fill until stop and Fill until full to select which data to use from the trace buffer.
  • Trace triggers - Trace Start and Trace Stop breakpoints - to specify for example a code section for which you want to collect trace data.
  • Trace output setting to select whether CPU execution or full trace acquisition shall have priority. (E20 only)
  • Data coverage support in the memory window via the RAM-monitor feature (E20 only).

Program corrections

• [EW22006] Random data is no longer programmed in the memory block 0xFFFF84000-0xFFFF8FFF for the emulators if no code is linked there.

2.10.2 2010-10-21

New features

• Live memory and Live Watch support
  Live Memory and Live Watch are now supported via the RAM-monitor feature in E20.
• Support for the RX630 Group
  Device file support as well as C-SPY E1/E20 emulator support for RX630 has been added.

2.10.1 2010-06-02

1.12 2010-01-15

1.11 2009-10-05

1.10 2009-05-05

• Initial release.