How to print this page

1. Products to Be Updated
   High-performance Embedded Workshop V.3.00.00 through V.4.04.01

   High-performance Embedded Workshop is bundled with the compilers and 
   other software products that it manages.
   To check to see the version number of your High-performance Embedded 
   Workshop, open the Help menu and select the About High-performance 
   Embedded Workshop command.

2. Descriptions of Revision
2.1 Functions Improved and Modified
    (1) Making Builds
        (a) Customization of linking order
            - Linking order can be imported and exported.
            - More than one file can be moved at a time by using the 
              Linkage Order dialog box.
            - The size of the Linkage Order dialog box is variable.
        (b) Build of projects
            When the dependencies of the child projects have been specified, 
            the build of their parent project is prohibited if a build error 
            arises in a child project.
        (c) Custom project types
            When you create a new project by selecting a custom project 
            type, the build options and the settings of linking order 
            are inherited from the selected project type to the newly 
            created project.

    (2) Saving information managed by High-performance Embedded Workshop
        In Windows Vista(R), the Program Files directory is protected 
        by user rights to ensure security and stability.
        The information managed by High-performance Embedded Workshop 
        has previously been saved by default on the directory where High-
        performance Embedded Workshop resides, which is under Program 
        Files.

        From now, the information is saved on the user profile
        directory so that the settings of High-performance Embedded 
        Workshop environment information can be done account by account of 
        the users who log on.

    (3) Administering tools
        As described in (2) above, the Program Files directory in Windows 
        Vista(R) is protected by user rights to ensure security and 
        stability. So the Uninstaller button in the Tools Administration
        dialog box has been removed in order that the files 
        of the development tools that are installed by administrators 
        under Program Files and managed by High-performance Embedded 
        Workshop cannot be removed by using High-performance Embedded 
        Workshop.

    (4) Debugging target programs
        (a) Introduced has been the option not to execute batch files 
            even if the settings of executing batch files are done in 
            the Debug Settings dialog box when modules are loaded.
            This option is effective when you right-click a module name 
            in the Workspace window and click Download(debug Data Only).
        (b) When you open the Debug menu and click Disconnect, the 
            screens of all windows are maintained. So if you open the 
            Debug menu and click Connect after having clicked Disconnect
            on the Debug menu, the screens of all windows before disconnected 
            are restored.

    (5) Synchronously debugging target programs between High-performance 
        Embedded Workshop applications and between target platforms
        (a) Synchronous-debugging functions between High-performance 
            Embedded Workshop applications have been removed by 
            eliminating the Launch Slave HEW command on the Tools menu 
            and the Launch Slave HEW button on the standard toolbar.
        (b) Synchronous-debugging functions between target platforms 
            have also been removed by eliminating the Synchronized Debug tab 
            in the Debug Sessions dialog box and the change_sub_session 
            command.

    (6) The Command Line window
        (a) Step-execution of batch files supported: Batch files can be 
            executed line by line.
        (b) Halting execution of batch files at breakpoints supported: 
            Execution of batch files can be halted at the place where 
            a breakpoint has been set.

    (7) The Status window
        The initial position where the Status window is displayed has been 
        changed from the upper left of the Main window of High-performance 
        Embedded Workshop to its lower left.

    (8) The IO window
        (a) The selected I/O register can be displayed in the IO window.
        (b) The update of display in the IO window can be suppressed.
        (c) The search capability of the I/O register in the IO window has 
            been supported.
        (d) When full module names are not displayed in the IO window, 
            the full name of any module can be referred to in the 
            pop-up window expanded by pausing the mouse pointer on 
            a module name.

    (9) The Image window
        Changes have been made so that image data cannot be read when 
        a workspace is opened.

    (10) License Manager
        The License Manager provides a simple way to configure and  
        add licenses for Renesas toolchains which are based on 
        the Sentinel(TM) RMS V.8.1 system.
        When you select the "Europe or United States of America" 
        region at the installation, you can use this feature.

    Corresponding software:
        All software tools under mass production that are corresponding 
        to High-performance Embedded Workshop.

2.2 Functions Improved in Debuggers
    The functions of debuggers managed by High-performance Embedded 
    Workshop have also been improved as follows:

    (1) The MR Analyze window (OS debug feature)
        (a) The statistics of execution history can be saved on a file.
        Corresponding debugger:
             Simulator Debugger for M32C Series
             M32C PC7501 Emulator Debugger
             M32C PC4701 Emulator Debugger
             Simulator Debugger for M16C Series and R8C Family
             M16C R8C PC7501 Emulator Debugger
             M16C PC4701 Emulator Debugger

    (2) Coverage window   
        (a) The Code Coverage window
            - When information about sessions is read, the option to read 
              coverage information files is selectable.
            - When the program is exited, the option to automatically 
              calculate coverage ratio is selectable.
            - In the Editor and Disassemble windows opened in Mixed or 
              Disassemble mode, the column for displaying the result of 
              code coverage has been introduced.
            - The C0/C1 coverage ratio is presented in percentage with 
              two decimal places.
        (b) The Data Coverage window
            The data coverage ratio is presented in percentage with 
            two decimal places.
        Corresponding debugger:
             E100 Emulator Software
             E200F Emulator Software
             E6000H Emulator Software for AE-5 Series
             E6000 Emulator Software for AE-4 Series

    (3) The Realtime Profile window
        (a) Double-clicking a function name in the window displays the 
            source code of the function.
        Corresponding debugger:
             E100 Emulator Software
             E200F Emulator Software

    (4) The Watch functions
        (a) The Watch window
            - The destinations of referencing symbols can be specified 
              scope by scope. The destinations that can be specified are 
              the scopes referenced with the addresses pointed to by the 
              program counter, the global symbols, and the static symbols 
              within each file.
              This function is available when you open the Debug Settings 
              dialog box and select Elf/Dwarf2 in the Debug format list.
            - The names of registered symbols can be edited.
            - The values of pointer variables can be edited.
            - Within the same scope, the settings of the real-time updating 
              functions are maintained when expansion of symbols is closed.
            - Dragging a symbol into the Memory window easily switches 
              the beginning address for displaying the Memory window to the 
              address of the symbol.
            - The option not to compare the address of a symbol with that 
              of another has been introduced in the Test Support facility.
            - The option to add timestamps to the information outputted into 
              a file has been introduced in the recording history of updating 
              values of registered symbols.
        (b) Instant Watch
            - The size of the Instant Watch dialog box is variable.
        (c) The watch_display command
            The Scope column has been introduced to display the results 
            of execution of the command.
        (d) The watch_record command
            As a parameter of a timestamp, [] has been introduced.
        Corresponding debugger:
             Simulator Debugger for SuperH Family
             Simulator Debugger for H8SX, H8S, and H8 Families
             E10A-USB Emulator Software
             E8a Emulator Software
             E8 Emulator Software
             E10T-USB Emulator Software
             E100 Emulator Software
             E200F Emulator Software
             E6000H Emulator Software
             E6000 Emulator Software

    (5) The coverage command
        (a) The coverage command
            The initial value has been changed from Enable to Disable.
        (b) The coverage_range command
            The initial range has been changed from 00000000-00000000 
            to No Range.
        Corresponding debugger:
             Simulator Debugger for SuperH Family
             Simulator Debugger for H8SX, H8S, and H8 Families

    (6) The Trace window
        (a) The adjusting function between Branch trace (varies from one 
            target MCU to MCU) allows the source code corresponding to 
            the adjusted addresses to be displayed.
        Corresponding debugger:
             E10A-USB Emulator Software
             E200F Emulator Software

2.3 Problems Fixed
    The following known problems have been fixed:
    (1) With setting breakpoints
        This problem has been described in Item 3. (3) "Operation of tool 
        products while Windows Aero used," in "Information on Compatibility 
        of Renesas's Software Development Tool Products and Windows 
        Vista (R), No. 2."
        For details see RENESAS TOOL NEWS Document No. 070516/tn3, 
        published on May 16, 2007, at:
          http://tool-support.renesas.com/eng/toolnews/070516/tn3.htm
    (2) With transferring load modules from PC to debugging platform
        For details see RENESAS TOOL NEWS Document No. 080316/tn1, 
        published on March 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/080316/tn1.htm
    (3) On the function for tree view of source files displayed when 
        debug-only project is used
        For details see RENESAS TOOL NEWS Document No. 080916/tn1,
        published on September 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/080916/tn1.htm
    (4) With searching more than one file for a character string
        For details see RENESAS TOOL NEWS Document No. 081001/tn1, 
        published on October 1, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081001/tn1.htm
    (5) With adding files to a project
        For details see RENESAS TOOL NEWS Document No. 081001/tn2, 
        published on October 1, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081001/tn2.htm
    (6) With referencing local variables
        For details see RENESAS TOOL NEWS Document No. 081001/tn3, 
        published on October 1, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081001/tn3.htm
    (7) With the order of loaded modules
        For details see RENESAS TOOL NEWS Document No. 081016/tn2, 
        published on October 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081016/tn2.htm
    (8) With loading modules when the IDE and the target platform linked
        For details see RENESAS TOOL NEWS Document No. 081016/tn3, 
        published on October 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081016/tn3.htm
    (9) With the syntax of build options for custom build phases
        For details see RENESAS TOOL NEWS Document No. 081016/tn4, 
        published on October 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081016/tn4.htm
   (10) With the build options for custom build phases after the version 
        of a toolchain has been changed
        For details see RENESAS TOOL NEWS Document No. 081016/tn5, 
        published on October 16, 2008, at:
          http://tool-support.renesas.com/eng/toolnews/081016/tn5.htm

3. How to Update Your Product
   Online update is available free of charge. Use either of the following 
   ways to update yours:
   (1) Download the update program of the product from the Web site at:
         http://www.renesas.com/hew_download
       This site is opened from November 25 on.
   (2) Use AutoUpdate Utility to obtain the update program and execute it.
       This service is available on and after November 26.

   NOTES:
     Two types of update program are available. Use either of them 
     as you like. They are as follows:
     (a) Full update program
         The components of High-performance Embedded Workshop to which 
         changes have been made in and after V.3.00.00 are updated; 
         that is, V.3.00.00 and later can be updated.
     (b) Differential update program
         The components of High-performance Embedded Workshop to which 
         changes have been made in and after V.4.04.01 are updated; 
         that is, V.4.04.01 and later can be updated.

4. Notices
   (1) The above two types of update program do not update any components 
       except those of High-performance Embedded Workshop itself 
       (C compilers, emulator debuggers, and others not updated).

   (2) If you are using any of the AutoUpdate Utility programs V.1.00.00 
       through V.1.03.00, begin to update yours to V.1.04.00 and then to 
       V.4.05.00. AutoUpdate Utility was revised to V.1.04.00 on July 1, 
       2007. For details of V.1.04.00, see RENESAS TOOL NEWS Document 
       No. 070701/tn1 at:
         http://tool-support.renesas.com/eng/toolnews/070701/tn1.htm

   (3) Problem with uninstalling High-performance Embedded Workshop 
       V.4.05.00
       When you are using Install Manager V.1.00.00 or V.1.02.00, 
       you will not uninstall the High-performance Embedded Workshop 
       updated by either of the above two update programs even if you 
       select the IDE and click the Uninstall button.
       Workaround:
       To uninstall High-performance Embedded Workshop, perform the 
       following steps:
       (a) In the upper list in the Maintenance window of Install Manager,
           select the High-performance Embedded Workshop to be uninstalled 
           and then click the Switch active environment button.
       (b) Use Add/Remove Programs in Control Panel of Windows(R) and 
           remove High-performance Embedded Workshop.
       Schedule of fixing the problem:
       We plan to fix this problem in the next version of Install Manager.
       To check to see the version number of your Install Manager, open 
       the Maintenance window of Install Manager and then click the 
       About Install Manager button.
       If the About Install Manager button does not appear, your Install 
       Manager is of V.1.00.00.

   (4) Operations on Windows Vista(R)
       (a) Standard rights can run High-performance Embedded Workshop 
           V.4.05.00 on Windows Vista(R).
           However, run Manual navigator with administrative privileges.
       (b) The following problems in High-performance Embedded Workshop 
           V.4.04.01 and earlier have been fixed:
           - High-performance Embedded Workshop must be executed by 
             administrators.
           - With Windows Aero being enabled, software breakpoints cannot 
             properly be set in the Editor and Disassemble windows.
       (c) Sharing projects through the network
           In Windows Vista(R), network protection functionality is improved 
           for security and stability. So the functions for sharing projects 
           through the network cannot be used on Windows Vista(R).

       NOTICE:
         If you use your emulator debuggers and others in combination with 
         High-performance Embedded Workshop V.4.05, they cannot run 
         properly on Windows Vista(R). You need to use any of the compiler 
         packages and emulator debuggers that will be released from now and 
         supported by High-performance Embedded Workshop V.4.05.
         For compatibility of each tool product and Windows Vista(R), go to:
           http://tool-support.renesas.com/eng/toolnews/p_tool.htm#environment