IAR Information Center for Renesas V850

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

Important information

• Read the V850 IAR C-SPY Debugging Guide for detailed information about this product component.

• Latest emulator firmware and other software updates from Renesas can be found here.

• How to free up a breakpoint used by the system
  The debugger uses one common breakpoint for terminal I/O support and for being able to halt execution at the program exit label. If none of these functions are needed, this breakpoint can be released by:
  1. Under Project options->Linker->Output, turn off With runtime control modules, and With I/O emulation modules.
  2. Add an own __exit function to your project. Example:
  
  void __exit()
  {
  for(;;){}
  }
  
  Also note that by checking Run to main in Project options->Debugger->Setup, the debugger temporary uses a breakpoint.

• V850MINICUBE2
  • Interrupts must be enabled by the application due to the fact that the debug-monitor on the device needs the interrupts of the serial interface to communicate with the debugger. If interrupts are not enabled, it will not be possible to break manually from C-SPY while the application is running.
  • If a device, e.g. V850ES IE2, requires enabling of internal RAM (IMS = 1;), a warning message will be shown after download. Example:
    Verify error, Failed to write memory at address 3FFD800
    The address is the first of the internal RAM. This warning message indicates that the internal RAM must be enabled by the application or in another way.

• V850NWIRE
  • Some processors support both "break-before-execution" breakpoints and "break-after-execution" breakpoints. For example V850E/ME2 supports 2 break-before-execution and 8 break-after-execution breakpoints. The latter 8 can be used as normal debugger breakpoints only by defining events that are used as breakpoints:
    1) Create an event on in the Emulator->Events dialog
    2) Select the event and use it in the Edit->Breakpoints dialog
  • The N-Wire driver supports devices that do not have internal flash memory and/or timers.

New features

• None

Known Problems

• [EW13277] When editing an event in the Edit Breakpoints dialog box, Events tab, it is sometimes not possible to exit the dialog box with the OK button, but only Cancel.

• [EW18005] When pressing the Find First or Find Next button in the Find In Trace dialog box, the highlighted frame in the Trace window is sometimes not correct. The Current frame list shows the correct frame number.

• [EW10959] The Live Watch and Realtime windows are updated faster if the Terminal I/O window remains closed during debug.

• [EW18634] If the same name is used for a data type and a data object, the data object is not displayed in the Watch window.

• [EW21558] When using the Live Watch window, the Trace window will only show op-fetch accesses (no data accesses) which is a limitation in the IECUBE. When closing the Live Watch window, the Trace Window will still only show op-fetch accesses until next debug session.

Program Corrections

• [EWV850-460] The CMOV instruction is not correctly implemented in the C-SPY simulator.

User guide corrections

• Using C-SPY in batch mode, section "STARTING CSPYBAT"
  The subdirectory that needs to be added to the path environment variable when running cspybat is v850\config\renesas\execs. Further, the file extension of the saved hardware settings file has changed from *.dni to *.dnx in version 5.10 and onwards. Therefore the part describing howto set up the environment variable CSPYBAT_INIFILE needs to be updated accordingly.

Miscellaneous

• Nothing.

Release history

2018-12-11 V5.10.1

New features

• Enhanced Registers and Symbols windows in C-SPY
  The C-SPY Symbols and Registers windows have been re-designed with new features. The Symbols window now has a filtering function and a new column displaying to which program module a certain symbol belongs. Some of the new features in the Registers window are drag-and-drop support from source code windows, detailed register tool-tip information, and improved handling of user-defined registers groups.

2016-05-17 V4.20.2

Program corrections

• [EW25121] The IDE sometimes crashes when using Live Watch in combination with single stepping.

• [EW25775] Wrong address area for the internal RAM memory is listed in the C-SPY E1 Hardware Setup dialog box.

New features

• The number of message boxes that appear when Verify download errors occur are reduced to a minimum and instead, the rest of the verify errors are now showed in the Debug log window only.
• The number of error dialog boxes that must be responded to when a fatal error occurs have been reduced significantly.

2015-10-22 V4.20.1

Program corrections

• [EW25121] The IDE often crashes when using Live Watch in combination with single-stepping.

• [EW25740] The IDE sometimes hangs if you change the value of an SFR in the Register window by changing the high or low part only.

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.

2014-06-26 V4.10.3

Program corrections

• [EW24669] It is not possible to set the ID code in the Hardware Setup dialog box for Minicube and E1.

• [EW24439] The C-SPY driver is using the wrong memory type when mapping extension memory for the V850ES core.

2013-07-12 V4.10.2

New features

• It is now possible to select JTAG clock speed under Project Options>Debugger for MINICUBE.

2013-05-30 V4.10.1

Program corrections

• [EW23261] It is not possible to restore an srec/hex file via the debugger using the Debugger>Memory>Restore>Memory Restore command.

• [EW23937] The C-SPY feature Loading multiple images fails with an error message.

• [EW23623] In some cases the C-SPY simulator terminates unexpectedly when stopping at a breakpoint with a condition and/or action to be executed.

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.
• Custom SFR window
  It is now possible to define custom SFR's (special function registers) in C-SPY with selectable access size and type.
• 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.

2013-01-16 V3.81.4

New features

• Serial OCD debugging support for MINICUBE2 and V850E2 has been added.
• C-SPY download time has been improved for devices with small flash blocks.

2012-05-10 V3.81.3

Program corrections

• [EW23194] The C-SPY macros __setCodeBreak() and __clearBreak() are now working again also for the E2 core emulators.

2012-05-08 V3.81.2

Program corrections

• [EW23200] The C-SPY macros __setCodeBreak(), __setSimBfreak() and __clearBreak() are now working again.

New features

• The debugger API and IAR C-SPY emulator driver now support also the V850E2/Jx4-L family.

2012-03-15 V3.81.1

Program corrections

• [EW22721] When saving memory in a range that includes the address 0x10000, data above 0x10000 was not saved while data below 0x10000 was saved.

• [EW22394] A malfunctioning automatic horizontal scroll feature when dragging a selection from the editor window to the left or the right has been turned off.

• [EW22660] The uC/OS-II plugin generated an error "Unable to access the Registry!" when running under Windows 7. This has been corrected.

New features

• The IAR C-SPY Debugger now supports Renesas E20 emulator.

2011-03-31 V3.80.1

Program corrections

• [EW21696] The IDE could in some situations crash when a Go command was issued while Trace was in browse mode.

• [EW21569] A "live watch" variable outside the automatically mapped memory area was not updated even if the option Use read break was selected.

• [EW21154] Negative values of long long type greater than (2^31)-1 (absolute) could not be entered in the Watch window.

New features

• The IAR C-SPY Debugger now supports Renesas E1 emulator.
• Data Flash memory window and possibility to set flash mask options is now implemented for IECUBE2 for V850E2.
• Two new C-SPY macros have been added; __isBatchMode() and __targetDebuggerVersion()

2010-03-31 V3.71.2

Program corrections

• Trace support has been added for IECUBE2 for V850E2 and cycle counter presentation both for IECUBE2 and MINICUBE for V850E2.

2010-02-01 V3.71.1

Program corrections

• [EW21484] Adding a non-existing variable to the Live Watch window and thereafter restarting the debug session resulted in an error.

• [EW21485] If an array was displayed (expanded) in the Live Watch window, the debug log showed the message "syntax error, unexpected '['] column 1" with every single step or run of the program.

2009-10-28 V3.70A

2009-08-04 V3.61A (update)

2009-06-10 V3.60B

Program corrections

• [EW21091]The debugger did not stop execution at a conditional breakpoint even if the condition came true. After breaking manually, also the value of the variable which triggered the conditonal breakpoint was not displayed correctly in the Watch window.

2009-04-20 V3.60A

Program corrections

• [EW20602] The IDE sometimes crashed with a fatal error message after a debug session with an IE type emulator.

• [EW20705] Value of bit-field variables located in the anonymous structure/union could be incorrectly shown in the Live Watch window.

2008-06-20 V3.50A

Program corrections

• [EW19470] Variables in the Live Watch window were not updated correctly for MINICUBE.

• [EW19541] Download of 32Kbytes to a flash memory area was not handled correctly in the C-SPY driver and also gave warning messages. This was due to that the last tag was not restored.

• [EW19938] If you modified both the mapping and error emulation address in the Data Flash Emulation dialog box, it could cause a range error even if the settings were correct.

2008-02-22 V3.40C

Program corrections

• [EW19731] The Data Flash memory window was not enabled for all C-SPY drivers.

2007-06-13 V3.40A

Program corrections

• [EW18054] Due to a display error, the hardware setup window for MINICUBE/N-Wire showed wrong mapping of RAM for certain devices.

• [EW18781],[EW19057] The MUL and MULU instructions were not simulated correctly for certain input values.

2006-08-28 V3.30B (patch)

Program corrections

• [EW18347] A temporary stop requested by a plugin via the DkExecutor::Stop function in the C-SPY SDK, resulted in a full stop instead.

2006-05-12 V3.30A

Program corrections

• [EW17864] It was not possible to connect to a target without sub-clock. This information is now read from the .ddf file and if not present, sub-clock cannot be selected in HW-setup.

• [EW17073] An error in the Trace save dialog box, Browse function, caused the IDE to crash on certain occasions.

• [EW17627] It was not possible to initialize the clock in the hardware setup for IECUBE.

• [EW16815] Stepping through a program containing multiple C/C++ statements within single macro could lead to a debugger crash.

2005-06-20 V3.20A

Program corrections

• [EW16839] A timing problem in the debugger driver caused slow Live Watch response time.

• [EW16342] The relative time stamp offset in the trace window was wrong (by one) for IECUBE.

• [EW16159] During run, the Live Watch window did not show the correct values for 8-bit variables located on odd addresses.

• [16147] The C-SPY Memory Window earlier read the memory byte-wise by default. Memory access type can now be selected in the emulator hardware setup.

• [EW16379] An internal buffer in the disassembler could overflow when to many, >100 depending on length, labels was found at the same address. This caused a debugger crash.

2004-11-09 V3.10B

Program corrections

• [EW16084] Simulation of the saturation instructions, SATADD, SATSUB, SATSUBR, sometimes gave incorrect results.

• [EW16379] An internal buffer in the disassembler could overflow when to many, >100 depending on length, labels were found at the same address. Note: This is corrected in the processor module for V850, v850proc.dll.

2004-10-20 V3.10A

Program corrections

• [EW15252] The EW user guide had an error in the description of __setSimBreak.

2004-03-25 V2.31A

2004-01-22 V2.30A

Program corrections

• [EW14329] C-SPY now checks if the device ROM size is available and if not, selects the next higher valid size.

• [EW13227] Cstartup now has a branch instruction after HALT that jumps back to the __exit label. This is to avoid that execution continues beyond the label.

2003-08-26 V2.21D

Program corrections

• Changes in common code was done due to that support was addedd for the IE-V850E1-CD-NW N-Wire interface.

2003-05-28 V2.21C (un-official)

2003-03-10 V2.21B

Program corrections

• [EW13688] While RTOS debugging on an emulator, the fatal error "Already running" occurred at random intervals.

• [EW13985] The execution of MUL and MULU was not performed correctly in the simulator. The error appeared when the result of a multiplication exceeded 0xFFFFFFFF.

2003-01-08 V2.21A

Program corrections

• [EW11683] Device description files for ROMLESS CPU devices were not accepted by C-SPY.

• [EW12118] Using profiling on larger applications caused C-SPY to exit with an fatal error. From now, the error only disables the profiling function. Since current emulator driver components have a limited number of 100 breakpoints, only smaller applications or parts of large applications, compiled with debug information, can be run with the profiler.

• [EW12120] Invalid memory block sizes for a certain emulator can no longer be selected in the hardware setup dialog.

• [EW12308] The start address of the internal RAM was incorrectly displayed in the hardware setup dialog. For some CPU's, a somewhat larger RAM size than selected will be mapped to cover the real CPU's RAM area. This is done because of a limitation in the emulator.

• [EW12309] The Code Coverage and Profiling plug-in's were not set up in the Windows registry when using EWV850-LE together with V850EMU.

• [EW13267] A break generated by the emulator, caused by a Sequencer Event Breakpoint, did not halt program execution.

2002-07-04 V2.20D

Program corrections

• [EW12269] C-Spy erroneously issued an error message because the mapping overlapped the internal memory area at 0x3FFC000-0x3FFEFFF

2002-03-25 V2.20C

Program corrections

• [EW11850] The IAR Embedded Workbench crashed when the Hardware Setup dialog box was closed. This problem only appeared for IAR C-SPY Emulator Driver V2.20B.

• [EW10800] For IE-V850E-MC emulator series, setting ROMLESS16 or ROMLESS8 mode did not work. Emulator was set up in single chip mode instead.

2002-02-28 V2.20B

Program corrections

• [EW11581] V850EMU V2.20A could not be used together with an EWV850-LE installation.

2002-01-15 V2.20A

Program corrections

• [EW10056],[V850DEW0003] Clicking on 'Scroll down' button of the 'Emulator Trace Window' scrollbar scrolled the window contents up instead of down.

• [EWH133] Enabling, disabling or removing breakpoints while the user application was executing could lead to a debugger crash.

• [EW10272],[EWH4] Signficant window states (like scroll position, expanded states, splitter panes etc.) was not restored with the desktop.

• [EW10027],[V850DEW0004] 'Remove All Breakpoints' did not work properly with 'Event' Breakpoints.

• [EW10030] The 'Trace' dialog was not reentrant if the 'Trace Operation' was set to anything else than 'Full trace'.

• [EW10031] The trace setup dialog has been fixed so that it opens up in a correct initial state.

• [EW10032] Some strange behaviour of the Edit Event dialog has been removed.

• [EW10037] Under some circumstances the trace window contents was not displayed correctly.

2001-11-26 V2.19A (unofficial)

2001-04-03 V2.11A