- Important information
- New features
- Known problems
- Program corrections
- User guide corrections
- Miscellaneous
- Release history
Important information
- All C-SPY hardware debugger drivers
- If the windows Live Watch, Live Memory or Sampled Graphs fail in displaying values while your application is executing, try using the 2-wire connection type (TOOL0+TOOL1 in the Hardware Setup dialog box).
- When you use the option Verify download on a flash device, errors might be reported for the some monitor and/or option byte specific addresses.
- When you use the debugger Stack window, the stack area must not be initialized by the application startup code. By then, the stack plugin has already written it's pattern, which is used to determine stack usage, to the stack area.
- Please refer to the C-SPY Debugging Guide for 78K for detailed information about this product part.
- The latest emulator firmware and other software updates from Renesas can be found here.
- 78K0IECUBE
To initialize the IECUBE, the following low_level_init example can be used as a template:
#include <io78f0822.h>
#include <intrinsics.h>
int __low_level_init()
{
IMS = 0xCC; // RAM 1024 bytes, ROM 48 Kbytes
IXS = 0x04; // XRAM 4096 bytes
WDTM = 0x77; // Watchdog
PCC = 0x00; // Clock control
while (OSTC < 0x1F){ // Wait
}
return 1;
}
New features
- None
Known Problems
- All C-SPY hardware debugger drivers
- The displayed value of an SFR might differ between the Memory window and the Register window because certain SFR's must be read with a specific access size and this is only checked for in the Register window. [EW21932]
- On rare occasions, you can get an error message that says:
Fatal Error: Emulator message: No response from the CPU. Failed to set SOC RSU info.
Workaround: Exit the IDE and delete the settings subfolder, the *.dep file and the *.ewd file in your project folder. Alternatively, use the Renesas programmer to erase the device. [EW19775] - 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. [EW18005]
- If both the SFR and Memory windows are open, incorrect SFR values are sometimes displayed. This behavior occurs when Peripheral break is enabled in the Hardware setup dialog box. [EW19785]
Program Corrections
- None
User guide corrections
- None
Miscellaneous
- Nothing.
Release history
2015-05-22 V4.80.3
Program corrections
- The Data Flash window sometimes shows the wrong content after application download. [EW25176]
2014-04-23 V4.80.2
Program corrections
- Instructions of the type BR 100 and BR $+100 are regarded as equal instead of one absolute address and one relative address when placed in an ASEG type of segment with a known start address. [EW24018]
2014-04-23 V4.80.2
New features
- The option Erase flash before next ID check has been added in the Hardware Setup dialog box.
2012-11-01 V4.80.1
Program corrections
- The value of constant data located in 78K0R7Fx3 data flash memory is now correctly displayed in the Watch window. The DATA FLASH/EEPROM area is now also handled as a read-only memory zone. [EW23348]
- Using Run To a function for the MINICUBE2 emulator now works also for other functions than main(). [EW22911]
New features
- Startup time and statement step speed has been improved for the E1 emulator.
2011-08-11 V4.71.2
Program corrections
- When installing on a computer with a non-English Windows operating system, a warning message concerning emulator drivers appeared in some cases. [EW22543]
- The C-SPY macro __driverType now works for all emulator drivers. [EW22558]
2011-07-04 V4.71.1
Program corrections
- In case of using the single wire interface for MINICUBE2, an error no longer occurs if you switch to the low speed oscillator as CPU clock followed by a manual break (or any other C-SPY command). [EW22509]
- If multiple images are downloaded in one debug session, C-SPY now gets the correct PC value after reset. [EW22412]
- A pulse at the RESET-OUT signal no longer causes a communication error between C-SPY and MINICUBE2. [EW22241]
- Pseudo Emulation can now be manually triggered during program execution. [EW22036]
2010-06-20 V4.70.1
New features
- Added emulator feature support in C-SPY
Data Flash Emulation, Direct Memory Modification, Snap Shot function, and the possibility to execute so called stub functions, are some of the new features in C-SPY.
Program corrections
- When resetting a 78K application without first stopping it, an "outside stack range" warning was sometimes generated. [EW21515], [EW21278]
2009-12-22 V4.62.4
2009-07-01 V4.62.1
- When you use IECUBE with a 78K0R device, cstartup no longer generates an incorrect warning. [EW20767]
- The symbol lookup can now distinguish between variables and registers with the same name. [EW20763]
2008-07-02 V4.60A
- The EXEC debuger API for 78K0R has been updated to solve the error that if an application larger than 2 KBytes was downloaded to a target-hardware via MINICUBE2, the last 512 bytes of the application were not written to the FLASH memory. [EW20255]
2008-05-20 V4.60A
- When next statement to execute was set in C-SPY, using the Set-Next-Statement command, the high byte of PC addresses above 0xFFFF are no longer masked off. [EW19308]
- When writing to the register PC, the highest 8 bits are no longer masked off when you use the 78K0R IECUBE/MINICUBE/TK emulator. [EW19255]
- The 78K0R IECUBE driver now supports the OP-fetch before execution event. [EW19193]
- Placing a variable using the '@' operator at an address outside the defined address space no longer causes the debugger to exit unexpectedly. [EW18463]
- When a target system was running, the items in the context menu in the Live Watch window were sometimes disabled. When they were enabled and you selected a new display format, it was sometimes not accepted. [EW18407]
- Qualified trace on variables with a size greater than 1 byte did not work correctly for 78K0R. [EW20020]
2007-05-11 V4.50B
2007-03-02 V4.50A
- With the Realtime Memory window open, C-SPY periodically stopped the application to update the window content. [EW18447]
- Illegal SFR accesses could cause a fatal C-SPY error which additionally crashed the complete IDE. [EW18464]
- In the Hardware Setup Window for the 78K0 MINICUBE emulator, the system clock was always displayed as the main clock. If an oscillator is mounted at the internal socket CLK1, the clock board shall be displayed as the main clock. [EW18514]
- If in the disassembly window, the memory area SFR was selected, the debugger generated the fatal error unknown exception in driver (#M1) and the debug session was closed. [EW18536]
- Using the EW78K 16Kbytes Kickstart version with the MINICUBE emulator caused a very long downloading time. [EW18541]
- In case of using an external clock as the main clock, the frequency input field did allow entering a user-defined value. In addition to this, a crash problem when selecting illegal values has been corrected which is possibly relevant also for other 78K C-SPY emulator drivers. It is now possible to enter a user-defined value when using the external clock as main clock. [EW18657]
- Entering a too high value for near_const_size for 78K0R could result in a fatal error in C-SPY. A size check of the entered value has been implemented to avoid this. [EW18761]
2006-10-20 V4.40C (Update)
- Memory read was blocked when executing a C-SPY macro from a breakpoint during execution. [EW18570]
- If an Event-breakpoint was deleted in the Breakpoint Window while the Event Window was open, the breakpoint was only removed form the Breakpoint Window, but not deleted. [EW18503]
- Code Coverage in banked memory for the IECUBE emulator did not work correctly. [EW18493]
2006-10-11 V4.40B (Update)
- With the Live Memory Window open, C-SPY periodically stopped the application to update the window content. [EW18447]
2006-07-07 V4.40A
- Read-access from un-initialized RAM caused an error for the IECUBE driver due to that the WRKSEG segment was not initialized (zeroed) in cstartup. [EW18154]
- The Suppress download feature did not work correctly for the 78K0-MINICUBE. [EW17912]
- The content of the memory window IROM area was not updated when a breakpoint was reached. [EW17896]
- Due to wrong setup of the EXEC API by C-SPY, times did not stop counting even though the application was stopped. [EW17886]
- An error occured if internal target voltage was configured in the emulator HW-setup and a debug session with external target voltage was started. [EW17876]
- Due to an error in XLINK (EW17601), the C-SPY MINICUBE driver terminated with a fatal error if the compiler option --library_module was used. [EW17526]
- The register window always showed registers in register bank 0. This is now corrected to show registers in the current register bank instead. [EW17354]
- In tight program loops with a conditional code breakpoint, a user break could be ignored due to lack of time. [EW17273]
2006-01-11 V4.30F (patch release)
- The sub clock selection Clock board was always disabled for the IECUBE emulator. [EW17631]
2005-11-13 V4.30E (patch release)
- Buffer-RAM access was not supported by the driver. Also, only 16 byte read access was done in the Memory window. [EW17472]
- Code banking was not supported with MINICUBE. [EW17475]
- The extended SFR area available in some MCU series, was not supported. [EW17487]
2005-10-27 V4.30D (patch release)
- When using the debugger option Run to main and having a lot of data being initialized by the C-startup code, the error message User program is running could be generated due to a timing problem in the initialization phase. [EW17422]
- Memory view of SFR:s could show incorrects values for short (2 byte) SFR:s. [EW17350]
- RAM areas other than Internal RAM and Extended Internal RAM was incorrectly blocked from access. [EW17087]
2005-08-11 V4.30B (patch release)
- Applications built with the XLINK --image_input option (pure binary files linked in addition to ordinary input files) could not be loaded by the debugger. [EW17056]
2005-07-15 V4.30A
- The Autostep function could cause the debugger to hang. [EW16774]
2005-01-17 V4.20B
- Selecting the option Target connected in the hardware setup for IECUBE did not set vdd_mode to EX_VDD_TARGET as expected. [EW16378]
2004-10-26 V4.20A
- The device file df0354y.78k was not up to date causing the error message "The FPGA configuration file could not be read". [EW15938]
2004-05-14 V4.11A
- First release of V4.xx