To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology C
8.1.2.6. Properties...77 8.1.2.7. Set as cur
84 CKP This shows the multiplier of the peripheral clock for the input clock. Clock Mode This shows the clock mode. 8.5.2 Communications Tab This sh
85 If this is checked, the default Baud Rate will be used. (This option should be set only when the RenesasEvaluation Board or Evaluation Development
86 Interface If the target is connected directly to the host computer, the connection interface should be selected to ‘Direct Connection’. Alternativ
87 Device Protection This allows the user to select either automatic protection (Automatic) or interactive protection (Interactive) to protect the FL
88 project to work with many Generic Boot devices. If this option is set to "Query", FDT will ask you to select whether to reinterrogate th
89 8.6 S-Record Properties Window This dialog is invoked by clicking the Properties toolbar button or from the Right-Click, Properties Menu when the
90 8.6.3 Selection Value This tab shows various representations of the data that is currently selected. The display depends upon whether the selecti
91 8.7.4 Allow Docking With this option checked the Output window is capable of being docked within the FDT application window. With the option unch
92 multiple tabs simultaneously. Normal S-record and binary files (and uploads via address) will only have data for one flash area at a time, which w
93 8.8.6 Display Unit Invokes the cascaded menu as follows: Byte - view the data as 8-bit bytes. Word - view the data as 16-bit words. DWord - view
8.8.8 Toggle ASCII Column...93 8.8.9 Create Selection...
94 8.8.15 Data EntryNote When entering data in the ‘Find’, ‘Replace’ or ‘Fill’ dialog boxes only hexadecimal or ASCII values can be used, based on t
95 Selecting the Commands tab allows the user to select and add buttons to the new toolbar. The user can place the new toolbar anywhere on the GUI by
96 8.10 Customise – Menu Invoked by [Tools->Customise...] and then select the Menu tab in the ‘Customise’ dialog box. Figure 8-19 Customise Men
97 Figure 8-20 Add Tool Dialog New menu options are added to the bottom of the list (i.e. bottom of the tools menu) by default. The order of menu o
98
99 Chapter 9 Simple Interface Mode Invoked by [Tools->Simple Interface...]. This is used to simplify the look and feel of FDT once a project is c
100 9.1 Options Menu 9.1.1 Login... This allows changing of which user is logged in to FDT. The hotkey Ctrl+Shift+U also invokes the Login dialog. 9
101 9.2 Dialog Controls 9.2.1 Back to Project This returns to the full FDT view. This will be disabled if the user currently logged in to FDT does n
102
103 Chapter 10 Basic Simple Interface Mode Invoked from the start menu “Flash Development Toolkit3.07 Basic”. This is used to simplify the look and
10.2 Dialog Controls ...105 10.2.1 Exit
104 10.1 Options Menu 10.1.1 Login... This allows changing of which user is logged in to FDT. The hotkey Ctrl+Shift+U also invokes the Login dialog.
105 10.2 Dialog Controls 10.2.1 Exit Clicking this will exit FDT and FDT will start up in the Simple Interface Mode next time it is loaded. This wil
106
107 Chapter 11 Field Programming This is a feature designed to assist FDT users to send their FDT projects to other FDT users. Once a project is co
108 11.1 Options Menu 11.1.1 Login... This allows changing of which user is logged in to FDT. The hotkey Ctrl+Shift+U also invokes the Login dialog.
109 11.2 Dialog Controls 11.2.1 Back to Project This returns to the full FDT Workspace view. This will be disabled if the user currently logged in t
110
111 Chapter 12 E8 Update When connecting to an E8 interface adaptor board, FDT will check that the E8 firmware (adaptor software) is the correct ve
112 Level 1 only update: E8 target power has been set to ON at 5.0V Connecting to device 'R5F21174' on 'E8' Configuration: &apo
113 Chapter 13 E8Direct The E8 is an existing USB interface board, which has been used to implement the communications protocol for programming R8C
i i. Cautions Renesas neither warrants nor grants licenses of any rights of Renesas’ or any third party’s patent, copyright, trademark, or other intel
114 Preparing for re-enumeration of E8 to E8Direct... Sending re-enumeration command... Request sent successfully, closing E8 Comms... At this point
ii ii. Preface About this guide This guide explains the use of the Renesas Flash Development Toolkit(hereafter referred to as FDT). Chapter 1 , Intro
iii iii. Abbreviations Target / Device Refers to the programmable microcontroller or microcomputer that is connected to the PC ready for programming.
iv iv. Document Conventions This manual uses the following typographic conventions: CONVENTION MEANING [Menu->Menu Option] Bold text with ‘->’
1 Chapter 1 Introduction The RenesasFlash Development Toolkit (FDT) is an on-board FLASH programming tool for Renesas F-ZTAT microcomputers that pro
3 Chapter 2 System Overview FDT provides a method of programming, erasing and reading from Renesas Flash devices. Workspaces and Projects can be use
Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to chang
4 2.1 User Interface The FDT Graphical User Interface is a Windows® application that presents a work environment, which allows the user to program FL
5 Figure 2-2 Menu Ellipsis If a menu item can also be invoked by pressing a hot key (a combination of keys), then the hot key is displayed to the r
6 2.1.2 Toolbars FDT has several toolbars located below the Menu bar. This provides quick access to FDT features by clicking the respective button wi
7 FDT toolbar Figure 2-7 FDT Toolbar Connect - connects the device to the interface. Disconnect - disconnects the device from the interface. Erase
8 S Record toolbar Figure 2-8 S Record Toolbar View as Bytes - view the file data as 8 bit bytes. View as Words - view the file data as 16 bit word
9 Automatic Protection – Set QzROM security protection automatically on disconnect (if more than one option is available a dialog will appear to sele
10 2.1.4 Pop-up menus Many windows have local pop-up menus in order to make commonly used features easier to access. These menus are invoked by click
11 2.3 Hot Keys There are various hot keys for frequently used operations. These are as follows by category:- Description Hot Key Help Help F1 Fil
12 Description Hot Key Window View as ASCII Alt+A View as Bytes Alt+1 View as Word Alt+2 View as Dword Alt+4 Align to 8 Bytes Alt+8 Device
13 Chapter 3 Using FDT 3.1 Quickstart The stages required in order to program a device are as follows: 1) Start FDT by selecting ‘Start’->‘Progr
Renesas FLASH Development Toolkit 3.07(for Windows® 98SE/Me, Windows NT® 4.0, Windows® 2000 and Windows® XP)User’s ManualUser’s Manual Rev.9.00 2006
14 3.2.2 What is the difference between Boot Mode and User Mode? The Renesas Flash devices have different modes of operation which are controlled by
15 User Mode – The User Mode Test Program and User Mode Micro-Kernel need to be already programmed and executing on the device. The initial Bit Rate
16 for changing settings such as fine tuning of timeouts, requires the Local Machine Administrator rights to save the settings. Password administrati
17 3.2.9 Can I modify the User Mode kernels to work for a different clock frequency? It is recommended that the original kernel is copied to another
18 3.3.3 Starting FDT by double clicking on a workspace file FDT can be started by double clicking on a workspace file from Windows® Explorer. This
19 This is the method used when an FDT workspace is double clicked in Windows® Explorer 3.3.9.3. Opening data files from the command line with Acces
20 3.4 Creating a New Workspace and Project When FDT is started in full mode (not FDT Basic Simple Interface Mode), a workspace and project must be
21 3.4.2 Choose Device and Kernel (not Generic Boot*) Select the device you wish to use from the drop-down list. It is possible to have more than on
22 3.4.3 Communications Port Select the port (and interface if available) from the drop-down list, then click the ‘Next’ button. Note that in additi
23 3.4.4 Device Settings Enter values for the device settings; enter the input clock, then select the main and peripheral clock multipliers from the
1. This document is provided for reference purposes only so that Renesas customers may select the appropriate Renesas products for their us
24 3.4.5 Connection Type Select whether the connection is for Boot Mode or User Mode in the ‘Connection Type’ dialog. Additionally, for a connection
25 3.4.6 Programming Options Select the protection level for programming the FLASH ROM and the messaging level, then click the ‘Finish’ button, or i
26 Figure 3-8 FDM Pin Settings Figure 3-9 E8Direct Pin Settings
27 3.4.8 Reset Pin Settings [Only if the FDM or E8Direct is selected] Select the ‘Operating Mode’ and ‘Clock Mode’ and if ‘User Defined’, set the Re
28 Figure 3-11 E8DirectRESET Pin Settings
29 3.5 Configuring a Project for a Generic Boot Device It is also possible to connect to a Generic Boot Renesas Device - where you do not need a ker
30 3.5.2 Generic Boot - Choose Device and Kernel Select ‘Generic Boot Device’ (or a device supported by Generic Boot) and click ‘Next’. Figure 3-13
31 3.5.3 Generic Boot - Communications Port Select the port (and interface if available) from the drop-down list, then click the ‘Next’ button. Fi
32 Note Setting the mode pins using the FDM requires caution. Please confirm the pin settings with the hardware manual even if a default setting is
33 Figure 3-19 E8DirectGeneric Device Pin Settings Note Setting the mode pins using the E8Direct requires caution. Please confirm the pin settings
Table of Contents i. Cautions... i ii. Preface...
34 3.5.6 Generic Boot - Confirmation FDT then waits for you to confirm that the device is connected and powered, and if not using the FDM or E8Direc
35 3.5.8 Generic Boot – Select Clock Mode Because some devices have a number of Clock Modes, a list is provided of all possible Clock Modes. The use
36 3.5.9 Generic Boot – Setup Complete Having selected the Clock Mode, the Generic wizard completes as below. Figure 3-24 Generic Boot setup compl
37 3.6 Connecting to the device This is achieved by selecting the Device->Connect to Device menu item, using the Ctrl-Alt-C hotkey, or clicking t
38 3.6.3 Locking For devices which support locking of erase blocks FDT may also check with the user whether to unlock the device. This is dependent
39 3.7.4 Programming multiple files to the User Boot Area 1. Add all the required target files to the project by selecting [Project->Add Files..
40 3.8 Erasing Data from the FLASH ROM 1. Select [Device -> Erase FLASH blocks...] to display the ‘Erase Blocks’ dialog box. 2. Select the bloc
41 3.9 Uploading the FLASH ROM Data 1. Display the ‘Upload Image’ dialog box from [Device -> Upload Image...].either 2. Select the Address tab
42 Figure 3-30 Upload Image Dialog – Tree The Upload via erase block has the same selection functionality as the Erase block dialog itself, i.e. ‘S
43 Chapter 4 Wait For Script 4.1 Wait For Script Overview This mode allows FDT to be automated and controlled by a text file containing a script of
3.3.9.3. Opening data files from the command line with Access Rights password security enabled...
44 4.2.1.1. Description This is an optional text description that may be used to describe, e.g. who created the file, why it was created, what it do
45 4.2.2.1. Log File Directory Enter the directory that the optional log file should be created in. FDT can insert additional details into the direc
46 4.2.3.3. Save This saves the FDT Script Configuration file (with the default extension .w4f). FDT will prompt to ask if you want to execute the sa
47 Alert output|** Please reset the board and regenerate the script to retry ** Alert output|********************************************************
48 4.3 Wait For Script – Edit Configuration... This is invoked from the ‘Tools’, ‘Wait For Script’, ‘Edit Configuration...’ menu and allows you to e
49 4.5.1 Workspace Description = loads a specified workspace into FDT (Note: a valid workspace and configured project must be opened to use any of t
50 Connect USB|0x000D|0 Connect USB|FDM|SN: 93506 Connect USB|E8|0001|5.0|0.0 4.5.3 Download Description = download the selected project image
51 4.5.5 BlankCheck Description = check if the device is blank Arguments: “userboot” Optional Tells FDT to check the user boot area of flash (if s
52 4.5.8 Disconnect Description = disconnect from a device. Note that issuing of a disconnect command even if FDT is not connected is allowed. This
53 4.5.11 Alert Description = indicate to the user that something has happened Arguments: “beep” FDT will output a warning beep “output” Required (
Chapter 4 Wait For Script... 43 4.1 Wait For Script Overview...
54 4.5.14 Move \ Copy Description = move or copy the script file. NB: FDT will process the script no further than this line Arguments: “$script” Re
55 4.6 Wait For Script – Example Script File What follows is an example of how a script file for FDT may look. This highlights some of the available
56 # Display message in output window alert output|This text will be displayed in the output window and the log file # delete this script # (will
57 Chapter 5 Access Rights 5.1 Access RightsOverview To prevent accidental changing of settings when using FDT to program devices (especially in a m
58 5.3.1 Disable All This button allows disables all user accounts and switches off Access Rights password security 5.3.2 Modify User This button a
59 5.3.4 Delete User This button allows deletion of user accounts. 5.3.5 Reset Pwd This button allows setting of the password for the selected user
60
61 Chapter 6 Configuring the User Interface When the user interface for FDT was designed an attempt was made to make frequently used operations quic
62 2. A specific window can also be selected by clicking on the tab containing the file name at the bottom of the Editor window. If the window is no
63 6.6 Customising the Toolbar The selection and arrangement of buttons displayed on the Toolbar can be customised to suit a user’s requirements. To
5.3.6 Close...59 Chapter 6 Configur
64
65 Chapter 7 Menus Figure 7-1 FDT Menus 7.1 File Menu The ‘File’ menu is used for aspects of the program that access data files. 7.1.1 Close Thi
66 7.1.6 Open an S-Record... Launches the ‘Open an S-Record’ dialog box allowing the user to open an existing file. The file may be an S-Record file
67 7.2.8 Find In Files... This launches a dialog to allow data to be located in files external to the active file. 7.2.9 Replace... This will launc
68 Figure 7-2 File Extensions Dialog 7.4.5.1. File Extensions Add... Selecting ‘Add...’ allows FDT to handle files of new extension types Figure
69 7.4.5.2. File Extensions Modify... Selecting ‘Modify...’ allows selection of how FDT handles files of this extension type. Figure 7-4 Modify Fi
70 7.5 Tools Menu The ‘Tools’ menu is used to launch additional FDT features, which are not related to either projects or target devices. 7.5.1 Admi
71 7.6 Window Menu The ‘Window’ menu is used to alter the display of currently open windows within the FDT GUI. Files displayed in the Editor window
72 7.7.4 Blank check This launches a blank check on the device FLASH and reports back to the Output window. 7.7.5 Upload Image This launches the ‘U
73 7.8.3 About... Launches the ‘About Flash Development Toolkit’ dialog box, through which additional information regarding FDT can be accessed: •
7.4.8 Field Programming...69 7.5 Tools Menu ...
74
75 Chapter 8 Windows This chapter describes each child window type, the features each supports and the options available through their associated po
76 8.1.1.2. Allow Docking Invoking this option allows the user to select if the window is docked, or if it can “float” around the main window. 8.1.1
77 8.1.2 Project The Project is the next item in the hierarchy below the Workspace. In the following example, the Workspace is called “Industrial Co
78 8.1.2.7. Set as current Project Sets the highlighted project as the current active project. This option is not available if the highlighted proje
79 8.2 Device File The Device File is the item containing the data to Flash into the device. Figure 8-5 Device File The pop-up menu for Device File
80 8.2.6 Properties... Launches the device file properties dialog box. 8.2.7 Display Block usage... Launches the ‘S-Record Properties’ dialog box a
81 8.2.13 Compare File->Device (Complete Device) This mode would compare the data in the device flash (starting at the device start address) to t
82 8.4 Project Properties Invoked from the Project pop-up menu item Properties... The ‘Properties’ dialog box shows details of: • The name of the p
83 8.5 Configure Flash Project (Flash Properties) The ‘Configure Flash Project’ dialog box can be invoked from the ‘Configure Flash Project’ toolbar
Komentarze do niniejszej Instrukcji