M3T-PD308 M3T-PD30 PC4701 REJ10J0024-0100Z PD308 PC4701L PC4701U/M/HS PC4701U - Datasheet Archive

 

M3T-PD30 V.8.00 Emulator Debugger for PC4701 System User's Manual Rev. 1.00 May 1, 2003 REJ10J0024-0100Z Active X, Microsoft,

 

M3T-PD308 M3T-PD308 V.5.00 M3T-PD30 M3T-PD30 V.8.00 Emulator Debugger for PC4701 PC4701 System User's Manual Rev. 1.00 May 1, 2003 REJ10J0024-0100Z REJ10J0024-0100Z Active X, Microsoft, MS-DOS, Visual Basic, Visual C+, Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Keep safety first in your circuit designs! Renesas Technology Corporation and Renesas Solutions Corporation put the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. Trouble with semiconductors may lead to personal injury, fire or property damage. Remember to give due consideration to safety when making your circuit designs, with appropriate measures such as (i) placement of substitutive, auxiliary circuits, (ii) use of nonflammable material or (iii) prevention against any malfunction or mishap. Notes regarding these materials These materials are intended as a reference to assist our customers in the selection of the Renesas Technology product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to Renesas Technology Corporation, Renesas Solutions Corporation or a third party. Renesas Technology Corporation and Renesas Solutions Corporation assume no responsibility for any damage, or infringement of any third-party's rights, originating in the use of any product data, diagrams, charts, programs, algorithms, or circuit application examples contained in these materials. All information contained in these materials, including product data, diagrams, charts, programs and algorithms represents information on products at the time of publication of these materials, and are subject to change by Renesas Technology Corporation and Renesas Solutions Corporation without notice due to product improvements or other reasons. It is therefore recommended that customers contact Renesas Technology Corporation, Renesas Solutions Corporation or an authorized Renesas Technology product distributor for the latest product information before purchasing a product listed herein. The information described here may contain technical inaccuracies or typographical errors. Renesas Technology Corporation and Renesas Solutions Corporation assume no responsibility for any damage, liability, or other loss rising from these inaccuracies or errors. Please also pay attention to information published by Renesas Technology Corporation and Renesas Solutions Corporation by various means, including the Renesas home page (http://www.renesas.com). When using any or all of the information contained in these materials, including product data, diagrams, charts, programs, and algorithms, please be sure to evaluate all information as a total system before making a final decision on the applicability of the information and products. Renesas Technology Corporation and Renesas Solutions Corporation assume no responsibility for any damage, liability or other loss resulting from the information contained herein. Renesas Technology semiconductors are not designed or manufactured for use in a device or system that is used under circumstances in which human life is potentially at stake. Please contact Renesas Technology Corporation, Renesas Solutions Corporation or an authorized Renesas Technology product distributor when considering the use of a product contained herein for any specific purposes, such as apparatus or systems for transportation, vehicular, medical, aerospace, nuclear, or undersea repeater use. The prior written approval of Renesas Technology Corporation and Renesas Solutions Corporation is necessary to reprint or reproduce in whole or in part these materials. If these products or technologies are subject to the Japanese export control restrictions, they must be exported under a license from the Japanese government and cannot be imported into a country other than the approved destination. Any diversion or reexport contrary to the export control laws and regulations of Japan and/or the country of destination is prohibited. Please contact Renesas Technology Corporation or Renesas Solutions Corporation for further details on these materials or the products contained therein. For inquiries about the contents of this document or product, fill in the text file the installer generates in the following directory and email to your local distributor. ¥SUPPORT¥Product-name¥SUPPORT.TXT Renesas Tools Homepage http://www.renesas.com/en/tools Contents Contents Setup 1. 1 STARTTING THE DEBUGGER 3 1.1 FEATURES OF PDXX . 3 1.2 ABOUT PC4701 PC4701 EMULATOR . 4 1.3 BEFORE STARTING THE DEBUGGER . 4 1.4 STARTING THE DEBUGGER . 9 2. SETUP DEBUGGER 10 2.1 MCU TAB. 10 2.2 DEBUGGING INFORMATION TAB . 16 2.3 CLOCK TAB . 17 2.4 F/W AND WORK AREA TAB . 17 2.5 MEMORY EXTENSION MODE TAB . 18 2.6 RESET TAB . 20 2.7 RESUME TAB . 21 2.8 METHOD OF MAKING MCU FILE . 22 3. SET THE TARGET INFORMATION 24 3.1 PD308 PD308 . 24 3.2 PD30 . 28 4. ENVIRONMENTAL SETTING OF DEBUGGER 29 4.1 SHORTCUT KEY TAB. 30 4.2 DOWNLOAD TAB . 32 4.3 FONT TAB . 33 4.4 PATH TAB . 34 4.5 TOOL ENTRY TAB . 35 4.6 OTHER TAB . 36 4.7 CUSTOMIZING OF TOOLBAR . 39 5. ENDING THE DEBUGGER 41 Reference 43 i 1. WINDOWS/DIALOGS 45 1.1 PDXX WINDOW . 46 1.2 PROGRAM WINDOW . 50 1.3 SOURCE WINDOW . 55 1.4 REGISTER WINDOW. 55 1.5 RAM MONITOR WINDOW . 58 1.6 ASM WATCH WINDOW. 60 1.7 CALL STACK WINDOW. 64 1.8 SCRIPT WINDOW . 65 1.9 PROTECT WINDOW . 66 1.10 TRACE POINT SETTING WINDOW . 67 1.11 H/W BREAK POINT SETTING WINDOW . 73 1.12 TRACE WINDOW . 74 1.13 DATA TRACE WINDOW . 80 1.14 COVERAGE WINDOW . 82 1.15 TIME MEASUREMENT WINDOW . 83 1.16 MR WINDOW . 85 1.17 MR TRACE WINDOW . 86 1.18 MR ANALYZE WINDOW . 89 1.19 MR TASK PAUSE WINDOW . 91 1.20 TASK TRACE WINDOW . 92 1.21 TASK ANALYZE WINDOW . 94 1.22 GUI INPUT WINDOW. 95 1.23 GUI OUTPUT WINDOW . 96 1.24 S/W BREAK POINT SETTING WINDOW . 97 1.25 H/W BREAK POINT SETTING DIALOG BOX(PC4701L PC4701L) . 99 2. TABLE OF SCRIPT COMMANDS 100 2.1 TABLE OF SCRIPT COMMANDS . 100 2.2 TABLE OF SCRIPT COMMANDS (ALPHABETICAL ORDER) . 103 3. ERROR MESSAGES 106 ii Set Up 1 2 1 Startting the Debugger 1. Startting the Debugger 1.1 Features of PDxx The PD308 PD308 and PD30 have the following functions. 1.1.1 Real-Time RAM Monitor Function This function allows changes of memory contents to be inspected without impairing the realtime capability of the target program execution. The PC4701 PC4701 emulator system contains a 1-Kbyte RAM monitor area (which cannot be divided into smaller areas). 1.1.2 Break Functions · Software Break This function causes the target program to stop immediately before executing the instruction at a specified address. Up to 64 breakpoints can be set. If multiple breakpoints are set, the program breaks at one of the breakpoints that is reached. · Hardware Break This function causes the target program to stop upon detecting a data read/write to memory, instruction execution, or the rising/falling edge of the input signal fed from an external trace cable. The contents of events that can be set vary with each target MCU. Specified hardware break events can be used in one of the following combinations: - Break when all specified break points are effected.(And) - Break when all specified break points are effected simultaneously.(And(Same Time) - Break when any one of the specified break points is effected.(Or) - Break on transition in state to a break state.(State Transition) Protect Break This function causes the target program to stop upon detecting a data write to the ROM area or an access to an unused area (read/write or instruction execution). · 1.1.3 Real-Time Trace Function This function records a target program execution history. Up to 32K cycles of execution history can be recorded. This record allows inspecting the bus information, executed instructions, and source program execution path for each cycle. 1.1.4 Time Measurement Function This function measures the minimum, maximum, and average execution time and the number of executions performed in a specified interval. Measurements can be taken in up to four intervals at the same time. 1.1.5 Coverage Function This function records the addresses executed (accessed) by the target program (C0 coverage). This 3 function helps to keep track of unexecuted addresses after the program has stopped running. Use of this coverage measurement function in the test process makes it possible to keep track of the test items that have been omitted. 1.1.6 Real-Time OS Debugging Function This function debugs the realtime OS-dependent parts of the target program that uses the realtime OS. This function helps to show the status of the realtime OS and inspect a task execution history, etc. 1.1.7 GUI Input/Output Function This function simulates the user target system's key input panel (buttons) and output panel on a window. Buttons can be used for the input panel, and labels (strings) and LEDs can be used for the output panel. 1.1.8 Customize Function This function adds the user-exclusive functions (custom commands or custom windows) to the PDxx. To create these custom commands and custom windows, use the CBxx (Customer Builder for PDxx) included with the PDxx. 1.2 About PC4701 PC4701 Emulator The PC4701 PC4701 emulator system is a generic term used for the 8/16-bit MCU emulators. It can be used in combination with the emulation pod for the PC4701 PC4701 to debug application programs for each MCU. 1.2.1 Function table The supported functions vary with the type of emulator used. Function RAM Monitor S/W Break H/W Break Real-Time Trace C0 Coverage Time Measurement Protect Break Emulator PC4701U/M/HS PC4701U/M/HS PC4701L PC4701L 1K bytes area 64 points 6 points 32K Cycles 256K bytes area Go to Stop / 4 points interval Access Protect 1.3 Before starting the Debugger Before you can start the Debugger, the following tasks must be completed. 4 1 point G0 to Stop - 1 Startting the Debugger 1.3.1 Communication method by emulator The supported communication methods vary with the type of emulator used. Emulator I/F PC4701U PC4701U PC4701M PC4701M PC4701HS PC4701HS PC4701L PC4701L USB O X X X LAN O X O X LPT O O X X Proprietary X X O O parallel Serial X O O O 1.3.1.1 USB Interface Supported only when using the PC4701U PC4701U emulator. · The supported host computer OS is Windows Me/98/2000/XP. USB communication cannot be used in any other OS. · Compliant with USB Standard 1.1. · Connections via USB hub are not supported. · By connecting the host computer and the PC4701U PC4701U emulator with USB cable, it is possible to install the supported device drivers using a wizard (The PDxx that supports USB connections must be installed before this installation can be performed.). See "1.3.3.1 USB communication with PC4701U PC4701U" for details. · The necessary cable is included with the PC4701U PC4701U emulator. 1.3.1.2 LAN Interface Supported only when using the PC4701U/HS PC4701U/HS emulator. The IP address, etc. must be set in the emulator before it can be connected in a LAN. To communicate with the emulator via a LAN on Windows Me/98/2000/XP, Windows' registry information must partly be modified. See "1.3.3.4 LAN communication with emulators by Windows Me/98/2000/XP" for details. · The PC4701U PC4701U emulator in a LAN can be connected to the PC4701Us on another network connected to the LAN via a router. See "1.3.3.2 LAN communication with PC4701U PC4701U" for details. · The emulators PC4701U PC4701U and PC4701HS PC4701HS use different LAN cables. Specifically, the PC4701U PC4701U uses LAN cable (10BASE-T 10BASE-T only) generally available on the market, whereas the PC4701HS PC4701HS uses the LAN cable (10BASE-T/5 10BASE-T/5) included with it. · The host computer and the emulator can be connected directly. See "2.1.2.5 Setting of the LAN Interface" for details. · · 1.3.1.3 LPT Interface Supported only when using the PC4701U/M PC4701U/M emulator. · · · This communication uses the host computer's parallel (printer) interface. The necessary cable is included with the PC4701U/M PC4701U/M emulator. Four communication modes are supported that include ECP, EPP, Byte, and Nibble. Communication modes that can be supported depend on the host computer's BIOS settings. (Communication modes may not always be used even when they are supported by BIOS.) 1.3.1.4Proprietary Parallel Interface Supported only when using the PC4701HS/L PC4701HS/L emulator. The host computer must have a dedicated interface board, the PCA4202G02 PCA4202G02, incorporated in it (only the ISA bus is supported). The necessary cable is included with the PC4701HS/L PC4701HS/L emulator. · When using this communication on Windows NT 4.0/2000/XP 0/2000/XP, a device driver must separately be set. See "1.3.3.3 Proprietary parallel communication with emulators by Windows NT · 5 4.0/2000/XP 0/2000/XP" for details. 1.3.1.5 Serial Interface Supported only when using the PC4701M/HS/L PC4701M/HS/L emulator. · · This communication uses the host computer's serial interface. The necessary cable is included with the PC4701HS/L PC4701HS/L emulator. 1.3.2 Download of Firmware It is necessary to down-load the firmware which corresponds to connected Emulation Pod when the debugger is started to the emulator. · · · You have changed your emulation pod. You have setup PDxx for the first time. You have upgraded emulator debugger PDxx. Press the system reset switch within two seconds after powering up the PC4701 PC4701 to establish the maintenance mode. PDxx searches the version of the firmware downloaded to the emulator at start. Also when the firmware downloaded to the emulator is of old version, a mode which drives PDxx to download firmware is set. When PDxx gets started while the emulator is set in the mode which drives PDxx to download firmware forcedly, the following dialog is opened at start. Click the OK button to download the firmware. ATTENTION It is only the PC4701U PC4701U that the firmware can be downloaded in a LAN connection. Before the firmware can be downloaded by the PC4701U PC4701U in a LAN connection, the IP address, etc. must first be registered in the PC4701U PC4701U. (Setup method) If the emulator being used is the PC4701HS PC4701HS, use other communication methods (dedicated parallel or serial) to download the firmware. 1.3.3Setting before emulator starts 1.3.3.1 USB communication with PC4701U PC4701U Connection of USB devices is detected by Windows' Plug & Play function. The device driver needed for the connected USB device is automatically installed. For details, see "Installing USB Device Driver". > The USB devices connected are detected by Windows' Plug & Play function. The installation wizard for USB device drivers starts after the device had been detected. The following shows the procedure for installing the USB device drivers. 1. 2. Connect the host computer and the PC4701U PC4701U emulator with USB cable. Set the PC4701U PC4701U emulator's communication interface switch (on the rear panel) to the "USB" 6 1 Startting the Debugger 3. position. Then turn on the power to the emulator. The dialog box shown below appears. Go on following the wizard, and a dialog box for specifying the setup information file (inf file) is displayed. Specify the musbdrv.inf file stored in a location below the directory where the PDxx is installed (e.g., c:¥mtool¥pdxx¥drivers). ATTENTION · · · · Before the USB device drivers can be installed, the PDxx you use must already be installed. Install the PDxx first. USB communication can be used only in Windows Me/98/2000/XP, and cannot be used in any other OSs. When using Windows 2000/XP 2000/XP, a user who install the USB device driver need administrator rights. During installation, a message may be output indicating that the device driver proper musbdrv.sys cannot be found. In this case, specify the musbdrv.sys which is stored in the same directory as is the musbdrv.inf file. 1.3.3.2 LAN communication with PC4701U PC4701U Before the emulator can be connected in a LAN, the IP address, etc. must first be registered in the emulator. For the PC4701U PC4701U emulator in default settings, the utility "setip.exe" included with the PDxx may be used to set the IP address, etc. in the emulator. For details, see "Setting of the LAN Interface using the SETIP.EXE" > The utility "SETIP" included with the PDxx may be used to set the IP address, etc. in the PC4701U PC4701U emulator while in default settings. SETIP detects the PC4701Us in default settings that are connected to the same network. SETIP is stored in a location below the directory where the PDxx is installed (e.g., c:¥mtool¥pdxx¥utility). The file name is "setip.exe". To register the IP address in the PC4701U PC4701U, follow the procedure described below. 1. Connect the PC4701U PC4701U emulator with LAN cable to the same network (same subnet) as the host computer is connected. 2. Set the PC4701U PC4701U emulator's communication interface switch (on the rear panel) to the "LAN" position. Then turn on the power to the emulator. 3. Start SETIP. When SETIP has started up, the dialog box shown below appears, showing information on the PC4701U PC4701U connected to the network. (This information consists of the MAC address followed by the PC4701U PC4701U serial number.) 4. To register the IP address, click the Next button. To cancel registration, click the Close button. If not displayed, check whether the communication interface switch is set correctly and after temporarily turning off the power, turn it back on again. Then click the Search button. Click the Next button, and the dialog box shown below appears. Set the IP address, subnet 7 mask, port number, and default gateway IP address. When using the PC4701U PC4701U on the same network's same subnet mask, the default gateway IP address may be omitted. 5. 6. Use any 4-digit number to specify the port number. (Enter that number when starting the PDxx.) For details about the contents of the IP address, subnet mask, and default gateway to be specified, contact your network administrator. Click the Set button on the dialog box. The IP address, etc. that have been set are registered in the PC4701U PC4701U emulator. When registered correctly, the dialog box shown below appears. After checking the contents of the dialog box, click the OK button. Temporarily turn off the power to the PC4701U PC4701U emulator and turn it back on again. The registered IP address becomes effective after the emulator is powered up again. ATTENTION · · If multiple PC4701Us in default settings are connected on the same network, only the first PC4701U PC4701U detected is displayed. The PC4701Us which have had an IP address already set cannot be detected by SETIP. In such a case, connect to the emulator through another communication interface and re-register the IP address from the Init dialog box that appears. For details on how to set IP addresses from the Init dialog box, see "Setting of the LAN Interface." 1.3.3.3 Proprietary parallel communication with emulators by Windows NT 4.0/2000/XP 0/2000/XP If you are using PDxx in a combination of Windows NT 4.0/2000/XP 0/2000/XP + the parallel I/F, you need to specify the start address of I/O addresses (7 bytes) to the device driver for PCA4202G02 PCA4202G02, (The I/O address for PCA4202G02 PCA4202G02 is set to 100h initially.) You can set this setting with setPca4202.exe included with PDxx. The above programs are installed in the directory where PDxx is installed. (ex. c:¥mtool¥PDxx¥utility) At the first time of using PDxx,or when you want to change the I/O address for PCA4202G02 PCA4202G02 because of conflict with other devices, please follow the procedure of the setting described below. 1. Execute setPca4202.exe included with PDxx. The dialog box shown below will appear. 8 1 Startting the Debugger 2. 3. Find the I/O address that is set on the PCA4202G02 PCA4202G02 parallel board and input it in hexadecimal into the I/O Address input field. Click "OK" button. Restart Windows NT 4.0/2000/XP 0/2000/XP. ATTENTION · Make sure setPca4202.exe is executed by one who is authorized as an Administrator No one but Administrator. the user who has the authority of an Administrator can install the device driver. 1.3.3.4 LAN communication with emulators by Windows Me/98/2000/XP Please exexute registry setting program (Sack.exe) before starting PDxx. It is necessary for LAN communication with emulators by Windows Me/98/2000/XP to set the following registry. OS Key Data Windows Me/98 HKEY_LOCAL_MACHINE¥System¥CurrentControlSet¥ 0(REG_SZ) Services¥VxD¥MSTCP¥SackOpts Windows 2000/XP 2000/XP HKEY_LOCAL_MACHINE¥SYSTEM¥CurrentControlSet¥ 0(REG_DWORD) Services¥Tcpip¥Parameters¥SackOpts You can clear the registry with executing the program "UnSack.exe". The above programs are installed in the directory where PDxx is installed. (ex. c:¥mtool¥PDxx¥utility) ATTENTION Make sure Sack.exe and UnSack.exe is executed by one who is authorized as an Administrator.(Windows 2000/XP 2000/XP) No one but the user who has the authority of an Administrator can Administrator install the device driver. Note Windows Me/98/2000/XP TCP supports "Selective Acknowledgments (SACK)" as documented in RFC 2018. SACK gives higher performance in the network which have high bandwidth and long round-trip delays like satellite channels. SACK support is enabled by default in Windows Me/98/2000/XP. It is necessary for LAN communication with emulators by Windows Me/98/2000/XP to disable SACK support. Setting the above registry can disable SACK support. Note that when you use the network which have high bandwidth and long round-trip delays like satellite channels, the performance with SACK support disabled is lower than with enabled. 1.4 Starting the Debugger Click the Windows start button, then select menu Program (P) -> [RENESAS-TOOLS] -> [PDxx V.x.xx Release x] -> [PDxx] 9 2. Setup Debugger The Init dialog box is provided for setting the items that need to be set when the debugger starts up. The contents set from this dialog box are also effective the next time the debugger starts. The data set in this dialog remains effective for the next start. Tab Name MCU Debugging Information Reset Clock Resume F/W and Work Area Memory Extention Mode Product Name PD308 PD308 PD30 O O O O O O O O O O X O X O To keep the Init dialog closed next time the debugger is started, check "Next Hide" at the bottom of the Init dialog. You can open the Init dialog using either one of the following methods: · · After the debugger gets started, select Menu - [Environment] -> [Init.]. Start PDxx while holding down the Ctrl key. 2.1 MCU Tab The specified content becomes effective when the next being start. If the contents are set newly again from the Init dialog box after startup, new settings do not take effect unless you restart PDxx. 10 2 Setup Debugger Following figures are examples of displaying PD30. 2.1.1 Specifying the MCU file Click the "Refer" button. The File Selection dialog is opened. Specify the corresponding MCU file. An MCU file is saved under the directory in which PDxx is installed. (For example: c:¥mtool¥pdxx¥mcufiles). · An MCU file contains the information specific to the target MCU. · The specified MCU file is displayed in the MCU area of the MCU tab. If the corresponding MCU file is not contained in the debugger/emulation pod, you must create a new MCU file. To do this, see the following: · Method of making MCU file(PD30) 2.1.2 Setting of the Communication Interface The displayed data varies depending on the specified communication interface. (The figure below shows the data when special parallel communication is selected.) The available communication interface varies depending on the products. The following shows the setting for each communication interface. · USB Interfece(PC4701U PC4701U) · LPT Interfece(PC4701U/M PC4701U/M) · Proprietary parallel Interfece(PC4701HS/L PC4701HS/L) · Serial Interfece(PC4701M/HS/L PC4701M/HS/L) · LAN Interfece(PC4701U/HS PC4701U/HS) 2.1.2.1 Setting of the USB Interface(PC4701U PC4701U only) Interface(PC4701U PC4701U USB communication uses the personal computer's USB interface. USB communication can only be 11 used on the PC4701U PC4701U emulator. It is compliant with USB 1.1. > Before USB communication can be performed, the computer must have a dedicated device driver installed in it. For details on how to install USB device drivers, see "Install of USB device driver." For connection by USB communication, click the "USB" radio button on the MCU tab. The currently USB-connected emulators are listed in the Serial No. area. Select the serial No. of the emulator you want to connect. 2.1.2.2 Setting of the LPT Interface LPT communication uses a parallel interface (printer interface) of the personal computer. This communication method is available when the emulator PC4701U/M PC4701U/M is used. > To set the LPT communication, click the "LPT" radio button of the MCU tab in the Init dialog. The setting looks like the figure below. Specify the mode for data transfers in the Type field. · The LPT interface has four modes for data transfers, Nibble, Byte, ECP, and EPP. Their modes are documented in the IEEE-1284 IEEE-1284 standard. The mode possible to use depends on the PC with the PDxx. · When selecting AUTO, the PDxx detect the LPT interface at the start and select a mode possible to use which give better performance automatically. In some PC, the PDxx cannot detect the most suitable mode. Check the mode which the LPT interface in the PC have and select it from Nibble, Byte, ECP or EPP, if cannot. · Specify the I/O address of the used LPT port in the I/O Address field. · Start the BIOS setup program of the PC for checking the mode possible to use. How to start and use the BIOS setup program depends on each PC, so refer the manuals of the PC. Display of BIOS Setup SPP, Standard Parallel Port, Output Only Bidirectional, Bi-directional ECP, Extended Capabilities Port EPP, Enhanced Parallel Port Communication Mode Nibble Byte ECP EPP The address displayed in the parallel port base address field is the I/O address. Specify the I/O address set in the BIOS setup program, in the I/O Address field. (The following addresses are possible to be specified) · · 378h 278h ATTENTION The C compiler made by IAR also uses this printer (parallel) port. 12 2 Setup Debugger When using PDxx and the emulator PC4701U/M PC4701U/M in the ECP mode on the LPT communication, a problem that the data cannot be complied by the IAR C compiler will arise. If this happens, take one of the following countermeasures: · Connect PDxx to the emulator PC4701U/M PC4701U/M in any mode other than the ECP mode. · Start compilation when PDxx has been terminated. 2.1.2.3 Setting of the Parallel Interface Special parallel communication uses a special parallel interface board PCA4202G02 PCA4202G02 (option), which is inserted in the extension slot (ISA bus) of the personal computer. This communication method is available when the emulator PC4701HS PC4701HS or PC4701L PC4701L is used. > To set the parallel communication, click the "Parallel" radio button of the MCU tab in the Init dialog. The setting looks like the figure below. Specify the I/O address in the I/O Address field. which is the I/O address set on the parallel interface board, in hexadecimal (Don't describe prefix which shows a cardinal number ). · Please specify the value of the hexadecimal number for the I/O address. (Don't describe prefix which shows a cardinal number) ATTENTION Combination of Windows NT 4.0/2000/XP 0/2000/XP and Parallel Interface It is necessary to set the I/O address used for the device driver for a parallel communication. Please refer to "Setting before emulator starts" before starting PDxx. 2.1.2.4 Setting of the Serial Interface Serial communication uses a serial interface (RS-232C RS-232C) of the personal computer. This communication method is available for all the PC4701 PC4701 emulator series. > To set the Serial communication, click the "Serial" radio button of the MCU tab in the Init dialog. The setting looks like the figure below. Specify the communications port in the Port field and the baud rate in the Baud Rate field. 2.1.2.5 Setting of the LAN Interface LAN communication uses a LAN interface (10 Base-T or 10 Base-5) of the personal computer. Before using LAN, you must register the emulator IP address, port number and subnet mask to the emulator itself (Otherwise, LAN is not available). Then, set LAN communication. This communication method is available when you are using the emulator PC4701U/HS PC4701U/HS. 13 LAN communication with emulators by Windows Me/98/2000/XP It is necessary for LAN communication with emulators by Windows Me/98/2000/XP to set the registry. For details, see "Setting before emulator starts". > Start PDxx using other communication method. After it gets started, select Menu - [Environment]>[Init .] to open the Init dialog. Then, click the Target button of MCU tab. The Target dialog will be opened. Specify the emulator IP address in the IP Address field, port number in the Port field, and subnet mask in the SubNetMask field. (The emulator IP address must be registered in the network environment in advance.) When the PC4701U PC4701U it is used, the Default Gateway area becomes effective. Please specify the IP address of the default gateway. When the PC4701U PC4701U it is used on the identical sub net mask of identical network, it is possible to omit the IP address of the default gateway. · Specify the IP address, subnet mask and Default Gateway in decimal byte by byte, by separating every 4 bytes with a period. For details on the IP address and subnet mask, consult with your network manager. · A port number set in the Port field is used to identify the communication process of the server (emulator) in LAN (TCP/IP) communications. Specify the port number which has been set in the emulator in hexadecimal. (Do not add a prefix which shows a base.) Click the "OK" button in the Target dialog. The Target dialog is then closed and the Init dialog appears again. Click the "OK" button. Then, exit from PDxx. > To set the LAN communication, click the "LAN" radio button of the MCU tab in the Init dialog. The setting looks like the figure below. Specify the IP address of the connected emulator in the IP address field. Specify the IP address, in bytes, in decimal. Delimit each 4 bytes with a period. The port No. is the ID No. for the communication process of the server (emulator) on the LAN (TCP/IP). Specify, in hexadecimal (Don't describe prefix which shows a cardinal number), the port No. set on the emulator. > Emulators PC4701U/HS PC4701U/HS can be connected by LAN (TCP/IP) to a commercially available LAN card inserted in a PC by using a cross conversion cable for 10BASE-T 10BASE-T (also commercially available). A HUB is not necessary in this case. The cross conversion cable for 10BASE-T 10BASE-T converts the male connector of the 10BASE-T 10BASE-T of a straight 14 2 Setup Debugger LAN cable that is included with the emulators to that of a cross LAN cable. Connect a cross conversion cable to the male connector of the 10BASE-T 10BASE-T of the straight LAN cable connected to the emulator; then, connect the male connector of the cross conversion cable to the LAN card. The LAN communications can be set up the same way as normal one. 2.1.3 Executing Self-Check Specify this option to execute self-check* on the emulator when the debugger starts up. Be sure to select the above check box only when you want to perform self-check at startup. Specify this option in the following cases: · · · When the firmware cannot be downloaded When although the firmware is successfully downloaded, the debugger does not start When the MCU goes wild or something is wrong with the trace results and you want to check whether the emulator is operating normally. Select the check box to close the Init dialog box. After connecting to the emulator and confirming the firmware, the debugger will immediately start self-check on the emulator. (Self-check takes about 30 seconds to 1 minute.) If an error is found in this self-check, the debugger displays the content of the error and is finished. When the self-check terminated normally, the dialog box shown below is displayed. When you click OK, the debugger starts up directly in that state. This specification is effective only when the debugger starts up. *Self-check refers to the function to check the emulator's internal circuit boards for memory condition, etc. Refer to the user's manual of your emulator for details about the self-check function. 2.1.4 Specifying Clock Frequency Specify the operation clock of the target MCU within the MCU Clock field in the Time Count Resource group (in units of MHz). Specify the MCU clock and the clock divide ratio. If you are using the MCU at 10 MHz divided by 4, for example, enter "10" on the left side and "4" on the right side of the text box. If no values are set in the clock divide ratio specifying area, it is assumed that the clock is not divided (i.e., the same as you would specify the value 1). 15 2.1.5 Using/unusing the watchdog timer This specification exist for PD308 PD308 only. Specify whether or not to use the watchdog timer. (By default, the watchdog timer is unused.) When debugging the target system that uses a watchdog timer, select the check box shown above. 2.2 Debugging Information Tab The specified content becomes effective when the next being download. 2.2.1 Specifying the compiler used and its object format Specify the compiler used and its object file format. · Compiler Select the compiler used in your application. (By default, this is the C Compiler of our company.) · Object Format Select the format of object files output by the compiler used. 2.2.2 Specify the Storing of Debugging Information To save the debugging information, two methods are available: On Memory which saves the information in memory and On Demand which saves the information in the temporary file. On Memory On Demand Allows high-speed process because of use of memory. Minimizes use of memory. Select the saving method. (On Memory is set by default.) 16 2 Setup Debugger To select On Demand, specify the temporary file saving directory in the Temp Dir field. If you do not specify the directory, the system creates a temporary file in the directory in which the downloaded load module file is saved. 2.3 Clock Tab The specified content becomes effective when the next being start. 2.3.1 Specify the Target Clock Change the setting by synchronizing with the clock used by the target microcomputer. (Internal is set by default.) Select Internal to set the internal clock, and External to set the external clock. 2.4 F/W and Work Area Tab In this tab, only PD30 exists. The specified content becomes effective when the next being start. 17 2.4.1 Select the Firmware File Usually, click the Default radio button in the F/W group. Click the Select radio button when you have to download firmware different from the one described in the MCU file. The F/W Name list box is enabled only when you click the Select radio button. 2.4.2 Specify the Work Area In the Work Area Start Address field in the Work Area group, specify the top address of the area to be used as the work area. The emulator uses the MCU internal reservation area (unused area) as the debugging work area (about 10 bytes). Specify the work area so that it is accommodated in its MCU internal reservation area. The default work area top address is 2C00h. To debug a microcomputer (ex. 20K-byte RAM version if the M16C/62 M16C/62 group) whose work area is within the internal RAM area, you must change the work area. 2.5 Memory Extension Mode Tab This tab enabled only when the MCU tab in the Init dialog is used to specify the MCU file of the microcomputer (M16C/62 M16C/62 group) which supports the memory space expansion function. In this tab, only PD30 exists. The specified data remains effective for the next start. 18 2 Setup Debugger 2.5.1 Select the Memory Space Extension Mode Select the memory space extension mode. · · · When you use a normal mode, Please click the "Normal" radio button. When you use extension mode 1, Please click the "Ext1" radio button. When you use extension mode 2, Please click the "Ext2" radio button. The data of the eighth line of the selected MCU (data which specifies whether or not memory extension mode is required) is used to determine whether or not memory extension mode has to be selected. If the eighth line contains a '1', The memory extension mode selection area is active. If the line contains a '0' or nothing, the memory extension mode selection area is inactive. ATTENTION The functions may be restricted depending on the type of memory space expansion mode. Extension Mode 1 · When the memory space expansion area is displayed in the dis-assemble mode in the Program window or the Source window, the displayed data may be different from what you would expect through the operation accompanying redrawing of the window, such as up/down scroll, during execution of the target program. · The following emulator functions are implemented by analyzing the bus information (address bus, data bus). - RAM monitor function (RAM Monitor window, C Watch window) - Coverage measurement function (Coverage window, Coverage command) - Memory protect function (Protect window, Protect command) · MCU accesses the program bank if Fetch (command) is specified for the bank duplicated area, and the data bank if Read/Write is specified for the bank duplicated area. In above cases, a signal which can distinguish which bank accesses the bus information is not output. Therefore, the above function may not work as expected. · The memory reference commands are added, which reference the internal ROM in the bank duplicated area in the dump format (see the table below). You cannot use the DA command during execution of the target program. Command name Abbreviation Description DumpByte2 DB2 DumpByte with bank designation DumpWord2 DW2 DumpWord with bank designation DumpLword2 DL2 DumpLword with bank designation 19 · If you use the Memory Reference/Change command for the bank duplicated area before MCU is switched from the normal mode to the memory space expansion mode1 by the target program, the function may not work as expected. · The memory map shows the following data after PD30 gets started. Start Address End Address Map Attention 00000 003FF 003FF External 00400 03FFF 03FFF Internal The internal RAM area cannot be changed. 04000 2FFFF External Cannot be changed. 30000 FFFFF Internal Extension Mode 2 · The memory reference commands are added, which reference the internal ROM in the bank duplicated area in the dump format (see the table below). A memory reference command with the bank specification is added. The memory reference/the change to the bank repetition area must use the following commands. Command name Abbreviation Description with bank designation DumpByte2 DB2 DumpByte with bank designation DumpWord2 DW2 DumpWord with bank designation DumpLword2 DL2 DumpLword with bank designation SetMemoryByte2 MB2 SetMemoryByte with bank designation SetMemoryWord2 MW2 SetMemoryWord with bank designation SetMemoryLword2 ML2 SetMemoryLword with bank designation FillByte2 FB2 FillByte with bank designation FillWord2 FW2 FillWord with bank designation FillLword2 FL2 FillLword with bank designation Move2 Move with bank designation MoveWord2 MoveW2 MoveWord with bank designation · The following emulator functions are implemented by analyzing the bus information (address bus, data bus). - RAM monitor function (RAM Monitor window, C Watch window) - Coverage measurement function (Coverage window, Coverage command) - Memory protect function (Protect window, Protect command) - Hardware event (H/W break event*, Real-time trace event*, Time measurement event) MCU switches the bank to be accessed based on the value in the bank selection register. A signal which can distinguish which bank accesses the bus information is not output. Therefore, the above function may work as expected. *By specifying Simultaneous And (AND logic) (same time) for the hardware event and the bank selection register, both of which are detected as the combined condition in the State Transient Break/Trace window, the hardware event for the bank duplicated area can be detected. · If you use the Memory Reference/Change command for the bank duplicated area before MCU is switched from the normal mode to the memory space expansion mode 2 by the target program, the function may not work as expected. · The memory map shows the following data after PD30 gets started. Start Address End Address Map Attention 00000 003FF 003FF External 00400 3FFFF Internal The internal RAM area cannot be changed. 40000 BFFFF External Cannot be changed. C0000 C0000 FFFFF Internal 2.6 Reset Tab The specified content becomes effective when the next being start. 20 2 Setup Debugger 2.6.1 Target Reset after Down-loading Specify whether you want to reset the target immediately after the target program is downloaded. Do Reset Do Not Reset Reset.(Default) Not Reset. 2.7 Resume Tab The specified content becomes effective when the next being start. 2.7.1 Automatically Execute the Script Commands To automatically execute the script command at start of Debugger, click the "Refer" button to specify the script file to be executed. 21 By clicking the "Refer" button, the File Selection dialog is opened. The specified script file is displayed in the "Init File:" field. To disable auto-execution of the script command, erase a character string displayed in the "Init File:" field. 2.7.2 Restore the Window Status To restore the window status (window position, window size) after the previous debugger program is terminated, check the "Resume" check box. (Resume is ON by default.) 2.7.3 Re-download a Load Module To re-download a load module (target program), check the "AutoDownLoad" check box. (Re-download is OFF by default.) 2.8 Method of making MCU file 2.8.1 PD30 The following content is sequentially described in the MCU file. Specify the MCU name to the file name, and specify "mcu" to the file extension. 1. Start address of SFR area 2. End address of SFR area 3. Start address of internal RAM area 4. End address of internal RAM area 5. Start address of ROM area 6. End address of ROM area 7. File name of the Firmware *1 8. MCU type (whether memory space extension mode has to be specified or not)*2 Specify the addresses in hex format, and don't add any prefix which describe its radix. *1 Specify the firmware file name (referring to the following tables), and don't add the end of "m.s", "h.s", "l.s", which describe the type of emulator. MCU M16C/60 M16C/60 group M16C/61 M16C/61 group M16C/62 M16C/62 group M16C/20 M16C/20 group Firmware file name M30600 M30600 group M30600 M30600 group M30620B M30620B series M30620B M30620B There is a case that the emulation pod need the different firmware from the listed firmware, when the emulation pod is re-modeled. *2 Specify whether the MCU: supports the memory space extension function or not. When the MCU supports the function (EX: M16C/62 M16C/62 group), specify "1" , the other case, specify "0". 22 2 Setup Debugger Only when "1" is specified, the setting for memory space extension mode is available in Memory Extension Mode tab of INIT Dialog ATTENTION · · The areas specified as the ROM in the MCU file are write-protected from the program. Even if the write command is executed to the area, no value is written. However, you can use the Dump command to write values to memory. (This is enabled only when the Internal area is mapped by the MAP command.) If the RAM is assigned to the same area, you must change the setting of the MCU file. 2.8.1.1 Example 0 3FF 400 2BFF F0000 F0000 FFFFF M30600 M30600 0 23 3. Set the Target Information Setting information of the target for debugging is different according to the product. 3.1 PD308 PD308 In the Emem dialog box, setting information on the user target. The Emem dialog box opens after closing the Init dialog box. To keep the Emem dialog box closed next time the debugger is started, check "Next Hide" at the bottom of the Emem dialog box. You can open the Emem dialog box using either one of the following methods: After the debugger gets started, select Menu - [Environment] -> [Emem.]. 3.1.1 Status Tab (PD308 PD308) The specified content becomes effective when the next being start. 24 3 Set the Target Information 3.1.1.1 Select the Processor Mode Specify the processor mode for the target system. Either the following can be specified. · Single-chip Mode Single-chip Mode · Memory Expansion Memory Expansion Mode · Microprocessor Microprocessor Mode 3.1.1.2 Inspecting the MCU status Clicking this tab displays the status of each MCU pin. It allows to check whether the MCU pin status matches the processor mode to be set. If the slider is at the middle position, it means that the value is indeterminate. 3.1.2 Emulation Memory Tab (PD308 PD308) The specified content becomes effective when the next being start. 25 3.1.2.1 Debug monitor's bank address settings This product allocates a 64-Kbyte contiguous address area as the emulator's work area for use by the debug monitor. Specify any bank that the target system does not use. The debug monitor uses a 64-Kbyte area from the start address of the specified bank. (Example: If the specified bank is "F0," then the debug monitor uses a 64-Kbyte area beginning with address F000000h.) · · · · · The bank specified here cannot have its contents referenced or set. The contents of this area when displayed in the Memory window or the Program/Source window's disassemble display mode may not be correct. The following bank addresses cannot be specified: MCU internal resources (e.g., SFR and RAM areas) DRAM area and multiplexed area Interrupt vector area 3.1.2.2 Automatic emulation memory allocation for the internal ROM When single-chip or memory extension mode is selected, emulation memory is automatically allocated to the internal ROM area. The automatically allocated internal ROM address range is displayed in this field. 3.1.2.3 Emulation memory allocation for an extended area When memory extension or microprocessor mode is selected, emulation memory can be allocated to the extended area to be debugged (in up to four areas). Here, allocate memory for the debug target area and specify its mapping information. 26 3 Set the Target Information Follow the procedure described below. Specify the bank address of the debug target area to be allocated in Bank (Set bank address) hexadecimal. If specified as C0, C00000h is the start address of the debug target area. Specify the size of the debug target area (256 bytes or 1 Mbytes). Length (Specify size of area) If Length is specified to be "256 bytes," banks 00, 04, 08, and up to FC (every four banks) are specified for Bank; if Length is specified to be "1 Mbytes," banks 00, 10, 20, and up to F0 (every 16 banks) are specified for Bank. Specify the mapping information ("Internal" or "External") for the specified Map (Specify area map) area. If no area is specified, select "No Use." · Internal The area specified to be "Internal" is mapped into the internal area (emulation memory). · · · · · External The area specified to be "External" is mapped into the external area (external resources in the target system). Areas for which "No Use" is selected for Map and those not specified here are mapped into external areas. If compared to the case where areas are explicitly specified to be "External," the only difference is a download speed. (Downloading into these areas is slower than downloading into the areas specified to be "External.") The internal ROM area is automatically mapped into the emulation memory. Therefore, there is no need to set here. Be careful that the debug areas will not overlap. Make sure the total size of the specified debug target areas does not exceed the emulation memory size of the emulation pod used. The size of emulation memory that can be allocated varies with each emulation pod. (Consult the user's manual of your emulation pod.) The setting of the emulation memory area varies depending on the specified processor mode. Single-chip Mode You do not need to specify the area to be assigned as the emulation memory. The internal ROM area is automatically mapped into the emulation memory. The address range of the automatically mapped area is displayed in the Internal ROM Area: field. · Memory Expansion Mode(8bit and 16bit) If you have an area to be assigned as the emulation memory in addition to internal ROM area, specify it specify it separately. The internal ROM area is automatically mapped into the emulation memory. The address range of the automatically mapped area is displayed in the Internal ROM Area: field. · Microprocessor Mode(8bit and 16bit) Specify the area to be assigned separately. (There is no area which is automatically assigned.) · ATTENTION · The mapping setting data specified using the Map command is not reflected to the Emem dialog 27 · box. Set the emulation memory areas in the order of usage priority. The emulation memory areas to be set by the Map command are numbered, ignoring the unused (Not Use) areas. Accordingly, the emulation memory areas set in the Emem dialog box and the emulation memory area numbers set by the Map command will be mismatched. 3.2 PD30 3.2.1 Specify the Memory Mapping Please set the memory mapping as follows. Area Mapping Note SFR External Internal RAM Internal Internal ROM Internal External ROM External Memory Expansion Mode, Microprocessor Mode Please use the MAP command to change the memory mapping. Note · · · · · · The emulator temporarily uses the area from FFFCh to FFFFh as a stack. Set this area as Internal. If you want to set this area to External be sure to prepare read-/write-unprotected memory for the area. When using the memory space expansion function on the M16C/62 M16C/62 Series microcomputer, set the areas whose addresses are duplicated to External (The duplicated area depends on memory). Memory space expansion mode 1: 4000h to 2FFFFh Memory space expansion mode 2: 40000h to BFFFFh 28 4 Environmental Setting of Debugger 4. Environmental Setting of Debugger Specify debugger environment setting in the Customize dialog. You can open this dialog by selecting menu - [Environment] -> [Customize.]. The data set in this dialog remains effective for the next start. Please click the tab name about details. Tab Contents Shortcut Key Register the menus to the shortcut keys Download Automatically Down-load of the Load Module Setting the number of load module download histories Font Specify the font Specify the Displaying Tab Width Path Specify the Search Path of Source Files Specify the Saving Directory of Information File Tool Entry Secify the make file Specify the Editor Other Display the Termination Confirmation Dialog Debugger Forced Ending when Error Occurs Target Continuance Execution when Debugger Ends Display the Absolute Path of Source File 29 Control the Display Mode Switching of Program Window Execution History of Script Command Number of Label Displays of Address Setting Area You can also customize the buttons in the tool bar. 4.1 Shortcut Key Tab The specified content becomes effective when the next being start. 4.1.1 Register the menus to the shortcut keys You can register the menus to the shortcut keys. You can also register execution of the script file and opening of the Custom window to the shortcut keys. · Assignable shortcut keys are any one key*, or combination of Shift/Ctrl/Alt keys + any one key*. *Any one key covers the following. - Alphabet key - Numeric key - Function key - Symbol key(",", "@", ":" etc.) · When the shortcut key information is changed, the following dialog appears when exiting from the Customize dialog (when clicking the "OK" button). asking you whether you want to save the changed data or not. When you save the changed data, the data is automatically loaded at the next start of PDxx. > 30 4 Environmental Setting of Debugger Key Assign Group Category combo box Displays the menu category. The enabled menus in the selected category are displayed in the Menu List list box. · The category name [Main Menu] indicates all the menus except the option menus of each window. · When the category of the window name is selected, the menu options available in that window become enabled. · When the category name [Custom Window] is selected, the registered Custom windows become enabled. · When the category name [Script Command] is selected, the registered script commands become enabled. Menu List list box Lists the menus enabled in the menu category selected in the Category combo box. The listed menus are sorted in the alphabet order. Key Edit box Specifies the shortcut key to be assigned to the menu selected in the Menu List list box. Current Key Assign list box Displays the shortcut key to be assigned to the menu selected in the Menu List list box. ADD button Enables the shortcut key specified in the Key Edit box. DEL button Disables the shortcut key selected from the Current Key Assign list box. Current Shortcut Key List group Lists the preset shortcut keys. SAVE button Saves the shortcut key information displayed in the Current Shortcut Key List group in a file. LOAD button Reads the shortcut key information from a file. SCR button Registers a script to be assigned to the shortcut key. CB button Registers the Custom window to be assigned to the shortcut key. > 1. Select the category of the menu to be registered in the Category combo box in the Key Assign group. The menus available for the category are displayed in the Menu List list box. 2. Select the menu to be registered from the Menu List list box and click the Key exit box. PDxx is now waiting for the entry of shortcut key. 3. Press the shortcut key to be assigned. The content of the shortcut key is displayed in the Key edit box. 4. Click the ADD button below the Current Key Assign list box. > 1. Select the shortcut key to be deleted using one of the following methods: · Select the shortcut key from the list in the Current Shortcut Key List group. · Select the Menu List list box in the Key Assign group. 2. Click the DEL button in the Current Shortcut Key List group. > To use (save/read) the assigned shortcut key information separately, you need to specify the file. 31 Click the SAVE button and specify the file name. To read the shortcut key information, click the LOAD button and specify the file name. All of the registered shortcut key information is deleted. ATTENTION · · · You cannot assign the same shortcut key to multiple menus. If you register the assigned key, the information on the previously assigned shortcut key is overwritten. The shortcut key is enabled only for the active window. If two or more same windows are opened, the shortcut key is not reflected to all of them. If the same menu (Change Font, etc.) exists between the windows, the menu is enabled in all the windows having that menu. 4.2 Download Tab The specified content becomes effective when the next being start. 4.2.1 Automatically Down-load of the Load Module When the downloaded load module is updated by re-compile assemble, the file can be autodownloaded. The load module is updated at timing when it is operated by a command of execution group (Go, Step, etc.). In the Auto Download group, select any one of the following ("Disable" is selected by default.) Enable (with confirmation) Asks for confirmation at auto-download. Enable (without confirmation) Does not ask for confirmation at auto-download. 32 4 Environmental Setting of Debugger Disable Does not auto-download the load module file. 4.2.2 Setting the number of load module download histories You can set the number of load module download histories ("4" is set by default). Specify the number of histories in the File History Number field in the File History group. You can specify the number from 1 to 16. Furthermore, if the debugger fails to redownload a file from the download history, you can choose whether or not to leave the history of that file. (By default, the file is left.) If you want to delete the history, select the check box shown above. 4.3 Font Tab The specified content becomes effective when the next being start. 4.3.1 Specify the font Specify the default font for the characters displayed by PDxx. Click the "Font." button. The font selection dialog opens. Enter the font and font size. Note You can set the font independently in each window. With the target window active, select [Option]>[Font.] from the menu in the PDxx Window to open the font selection dialog. 4.3.2 Specify the Displaying Tab Width In a window which displays the source files (Program Window, Coverage source window, etc.), you can specify the display tab width. Specify the default tab values for the Program Window, Source Window. You can specify TAB values between 1 and 32. Note You can set the tab width by window. Select the PDxx window Menu - [Option] -> [TAB] while the target window is active. The TAB designation dialog is opened. 33 4.4 Path Tab The specified content becomes effective when the next being start. 4.4.1 Specify the Search Path of Source Files You can specify the directory position (search path) of the source file to be displayed in a window such as the Program Window. This method is useful when the source file does not exist in the current directory or divided into multiple directories. To register the search path, click the Add. button in the File Search Path group. The folder selection dialog is opened. Specify the directory in which the source file exists. To delete a certain search path, click the target search path and click the Delete button. To delete all the search paths, click the Delete All button. 4.4.2 Specify the Saving Directory of Information File You can specify the directory in which the ASM/C watch point information file and other information file are saved. Other files cover the following: · Script command execution history file · Break information file The default saving destination directory of the ASM/C watch point information file is a directory in 34 4 Environmental Setting of Debugger which the load module exists. The default saving destination directory of other information file is a directory in which PDxx has been installed (example: c:¥mtool¥pdxx(sim). To change the directory in which the ASM/C watch point information file is saved, reset a check mark from the "Use the same directory as the absolute module file" check box in the Directory Setting group. Then, the "Watch Points:" field is enabled. Click the Refer. button on the right of the "Watch Points:" field and specify the saving destination directory from the Directory Selection dialog. To change to directory in which other information file is saved, click the Refer. button on the right of the "Other Settings:" field and specify the saving destination directory from the Directory Selection dialog. 4.5 Tool Entry Tab The specified content becomes effective when the next being start. 4.5.1 Starting the make command First, prepare a PIF file from which to start the make command. To create a PIF file, see "Creating a PIF file". Click the Refer button in the Make group. The Directory Selection dialog is opened. Specify the directory in which the Make file exists. Name the PIF file to be registered in the PIF Filename field. 4.5.1.1 Create a PIF File 1. 2. 3. 4. Create a keyboard shortcut for command.com located in the Windows directory. Command.com is in the Windows directory in Windows95/98. It is in the system32 directory (The example:¥winnt¥system32) under the Windows directory in Windows NT 4.0/2000/XP 0/2000/XP. For the keyboard shortcut thus created, assign a file name xxxxx.pif(xxxxx denotes a name specified by the user) and moves the file into the directory that contains makefile. Open the property dialog box for PIF files and enter the make command to execute on the command line. 35 4.5.2 Specify the Editor You can start the Editor in a window which displays the source file (Program window, Coverage source window). Click the Refer button in the Editor group. The File Selection dialog is opened. Specify the item file of the editor to be used. Specify the editor parameter in the Argument field. File names are stored in "%F", and line numbers are stored in "%L". To specify the editor options, see the Editor Manual/Help. 4.6 Other Tab The specified content becomes effective when the next being start. 36 4 Environmental Setting of Debugger 4.6.1 Display the Termination Confirmation Dialog The on-completion confirmation dialog box can be disabled from being opened when the debugger is closed. (By default, it is opened.) To keep the dialog closed, remove a check mark from the above check box in the Exit group. 4.6.2 Debugger Forced Ending when Error Occurs You can set a parameter so that the debugger will not be forced to end when an communication error occurs. (The debugger is forced to end by default.) To do this, remove a check mark from the above check box in the Exit group. 4.6.3 Target Continuance Execution when Debugger Ends When exiting from the debugger during execution of the target program, you can select to continue execution or stop execution of the emulator. (The emulator is stopped by default.) To continue execution, remove a check mark from the above check box in the Exit group. ATTENTION The target program which is executed continuously cannot be re-controlled next time the debugger gets started. To start the debugger, press the system reset switch on the emulator to reset the target program. 4.6.4 Enabling multiple startup Multiple PDxx startup can be enabled (By default, multiple startup is disabled.). 37 To enable multiple startup, check the above check box included in the Exit group. 4.6.5 Display the Absolute Path of Source File If the file name is shown with a path on the title bar of the Program (Source) window, you can choose to omit the path and show only the file name. To hide the file path, check the above check box in the Other Setting group. 4.6.6 Control the Display Mode Switching of Program Window You can set switching of the display mode at stop of the target program to "Suppress" (keep the current display mode) in the Program window. (However, the display mode may be switched depending on where the target program is stopped.) To control the display mode switching, check the above check box in the Other Setting group. 4.6.7 Execution History of Script Command You can save the execution history of the script command. (Ten sets of history data are saved by default.) To change the history of script commands, specify the number of history in the Number of Commands field. (0 to 100) To clear history of script commands, remove a check mark from the above check box in the Other Setting group. 4.6.8 Source file update warning If any source file exists that has been updated after creating the target program, an warning dialog box can be displayed when issuing the commands associated with target execution. (Warned, by default) If source file update warnings are unnecessary, uncheck the above check box. If the check box is checked, the warning dialog box shown below appears. Choosing "No" in this warning dialog box cancels the target execution command that was going to be issued. Build and download the target program. Choosing "Yes" accepts the target execution command that was going to be issued, so that the command is processed normally. From the next time on (until the next time downloading is processed), 38 4 Environmental Setting of Debugger no warnings will be displayed even when using target execution commands. If the warning dialog box is closed by checking the Next Hide check box, no source file update warnings are displayed from the next time on (This is the same as when the Warn to update the target program check box is unchecked.). 4.6.9 Label List Display in Address Setting Field It is possible to cease to display the label list in the address setting field of each dialog. (For the default, up to 30,000 labels are displayed in the label list.) To cease to display the label list, remove the check mark from the above check box. To change the number of label displays, designate the number of labels in the "Number of Labels" field (0-30,000). 4.7 Customizing of Toolbar The toolbar buttons on each window can be customized. To customize any button, right-click on the window's toolbar. The popup menu shown below appears. Flat Style Flattens the button when checked. Text Labels Shows text below the button when checked. Labels on right side Shows text to the right of the button when checked. Customize. Opens a toolbar customize dialog box. For details about the toolbar customize dialog box, see "Assigning Buttons to the Toolbar." 4.7.1 Assigning Buttons to the Toolbar To do this, double-click an area in which no button is placed in the tool bar in the window. The Customize Tool Bar dialog opened. · · The buttons corresponding to the option menus in the window are provided. You can only add the buttons which are enabled in each window. You cannot add the buttons for other windows. 39 4.7.2 Adding a button Click the buttons to be added in the "Available Button" list box at right of the Customize Tool Bar dialog. Then, click the "Add" button in the center of the dialog. 4.7.3 Deleting a button Click the button to be deleted int "Tool Bar Button" list box at left of the Customize Tool Bar dialog. Then, click the "Delete" button in the center of the dialog. 4.7.4 Changing the button display order Use the "Up" button or "Down" button at right of the dialog to change the display order. Click the button for which the display order is to be changed in the "Tool Bar Button" list box at left of the Customize Tool Bar dialog. Then, click the "Up" or "Down" button to change the display position. 4.7.5 Resetting the display buttons Click the "Help" button at right of the dialog. The display buttons are reset to the default settings. 40 5 Ending the Debugger 5. Ending the Debugger To ending the debugger, select Menu - [File] -> [Exit]. The Confirmation dialog opens. When ending the PDxx, click the "OK" button. To keep the dialog closed, refer to "Other Tab of Customize Dialog". 41 [MEMO] 42 Reference 43 44 1 Windows/Dialogs 1. Windows/Dialogs · Windows The window of this debugger is shown below. When the window name is clicked, the reference is displayed. Emulator PC4701U/M/HS PC4701U/M/HS PC4701L PC4701L Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support Window Name PDxx Window Program Window Source Window Register Window Memory Window RAM Monitor Window ASM Watch Window C Watch Window Call Stack Window *1 Script Window S/W Break Point Settiong Window H/W Break Point Settiong Window Trace Point Setting Window Protect Window Trace Window Data Trace Window Coverage Window Time Measurement Window MR Window MR Trace Window MR Analyze Window MR Task Pause Window Task Trace Window Task Analyze Window GUI Input Window GUI Output Window · Dialogs The dialog of this debugger is shown below. When the dialog name is clicked, the reference is displayed. Dialog Name H/W Break Point Setting Dialog Box[L] Emulator PC4701U/M/HS PC4701U/M/HS PC4701L PC4701L Support 45 1.1 PDxx Window The PDxx Window is the main window for PDxx. This window displays the main commands on a toolbar. You can click on the buttons on this toolbar to run the target program in normal or one-step mode. The main display area accommodates windows such as the Target Program Window. 1.1.1 Configuration of PDxx Window · · · · · · · · The main commands, such as execution/stop of the target program and step execution, are allocated to the tool bar. The Option menu is dependent on the active window. When the active window is changed, the Option menu is automatically changed. The status bar at the bottom of the PDxx window shows the following information: Explanation/display of menus and buttons Display the communication interface Execution time required from start to end of the target program execution Execution state of the target program (during execution or execution stopped) Display the Cause of the Program Stoppage 1.1.2 Tool Bar A basic operation is allocated to the toolbar. 46 1 Windows/Dialogs Button Button Name Go Contents Execute target Program Come Execute the target program from the value in the program counter to the position of the cursor Step One-step execution of target program Over Step over function/subroutine call Return Run the program up to the higher routine Stop Stop execution of the target program Break Set the position of the cursor in the window as the software breakpoint Reset Reset the target program SW Set S/W breakpoint HW Set H/W breakpoint 1.1.3 Option In the PDxx window, the following menus are prepared. File Operation Menu Menu Options File Download Load Module. Memory Image. Symbol. Rom Data. Reload. Upload. Save Disasm. (Download File) Exit Editing Menu Edit Display Menu Function Download target program. Download machine language data and debugging information. Download only machine language data . Download only debugging information. Additional download machine language data Reload target program. Upload target program. Save disassembly result. List the file name of target program downloaded. Terminate PDxx. Menu Options Copy Paste Cut Delete Undo Find. Function Copy character strings specified to clipboard. Paste character strings of clipboard. Cut character strings specified to clipboard. Cut character strings specified Undo of edit Find character strings. Menu Options Function 47 View Tool Bar Status Bar Tool Bar(Child) Setup Menu Menu Options Environment Init. Start Up. Customize. Switch display or non-display of toolbar. Switch display or non-display of status bar. Switch display or non-display of toolbar(child window). Function Environment setup(open the Init dialog box) Startup function settings Open Customize dialog box. Debugging (Basic) Menu Menu Options Debug Go Go Go Option. GoFree Come Step Step Step Option. Over Over Over Option. Return Reset Stop Break Point S/W Break Point. H/W Break Point. Break Trace Point. Scope. Make Function Start target program. Run from current program counter. Run from specified address. Free-run target program. Run to cursor position. Step execution. Execute one step. Execute specified No. of steps. Over-step execution. Execute one over-step. Execute specified No. of over-steps. Execute until return from current subroutine. Reset target program. Stop target program. Set break point. Open S/W Break Point Setting Window. Open H/W Break Point Setting Window. Set/cancel software break at cursor. Open Trace Point Setting Window. Open Scope Setting dialog box Make target program Debugging (Option) Menu Menu Options Function Option The content of option menu depends on the active window. The content of the menu changes automatically when an active window changes. Please refer to the reference of each window for the content of the menu of each window. Window Operations (Basic Window) Menu Menu Options Basic Cascade Windows Tile Arrange Icon Program Window Source Window Register Window Memory Window RAM Monitor Window ASM Watch Window C Watch Window Call Stack Window Function Cascade windows. Tile windows. Arrange icons. Make Program Window active. Open Source Window. Open Register Window. Open Memory Window. Open RAM Monitor Window. Open ASM Watch Window. Open C Watch Window. Open Call Stack Window 48 1 Windows/Dialogs Script Window Open Script Window Window Operations (Optional Window) Menu Menu Options Optional Protect Window Windows H/W Break Point Setting Window Trace Point Setting Window Trace Window Data Trace Window Coverage Window Time Measurement Window Realtime OS Windows MR Window* MR Trace Window* MR Analyze Window* MR Task Pause Window* Task Trace Window Task Analyze Window GUI Windows GUI Input Window GUI Output Window Custom Windows Option (Custom Window) *Does not exist according to the product. Help Menu Help Menu Options Contents Active Window About. Function Open Protect Window. Open H/W Break Point Setting Window. Open Trace Point Setting Window. Open Trace Window. Open Data Trace Window. Open Coverage Window Open Time Measurement Window Real-time OS Windows Open MR Window Open MR Trace Window Open MR Analyze Window Open MR Task Pause Window Open Task Trace Window Open Task Analyze Window GUI Widows Open GUI Input Window Open GUI Output Window Custom Windows Entry Custom Window Open the custom window Function Display Help. Display Help of Active Window. Display version information 1.1.4 Display the Cause of the Program Stoppage If the program is stoped by the emulator's debug function, the cause of the stoppage is displayed in the PDxx window's status bar. Display Forced, Program, Event, Combination, The cause of the stoppage Forced break from the front end Hardware break, logical combination AND or AND(same time) condition was met Event, Combination, Ax, Hardware break, logical combination OR condition was met (Ax:The event number of which condition was met.) Event, Sequential, from xx, Hardware break, State Transition condition was met (from xx:previous state (start, state1, state2) Event, Sequential, Timeout, Hardware break, State Transition, Time Out condition was met Event, Access Error, Protect break 49 1.2 Program Window The Program window always displays the source file corresponding to the current program counter position. This window is opened automatically at start. The background of the program counter position is displayed in yellow. This window allows you to execute the source program up to the cursor position, set/reset the software breakpoint, and perform line assemble. The Program window provides the three display modes as below: · Source display mode Displays the source file of the target program.Can also be used to edit the source file. · Disassemble Mode Displays the disassemble result of the target program. · MIX display mode Displays the source file of the target program and its disassemble result in a mixed style. 1.2.1 Configuration of Source Display Mode The program window has the following two source display modes. These display modes can be changed from menus on the program window. · Debug mode This mode is used to debug (e.g., run or stop) the target program. · Edit mode This mode is used to edit the source file. The program window's source display mode (debug mode) is configured as shown below. · · · You can switch "Display/Hide" for the line number display area/address display area. You can change the source file to be displayed by double-clicking the line number display area. You can change the display start address/display start line by double-clicking the address display 50 1 Windows/Dialogs · · · · · · · · · · · · area. You can set/reset the breakpoint by clicking (or double-clicking) the breakpoint display area(Contents of breakpoint display area). By staying the mouse cursor on a C language variable for a given period of time (about 0.5 second), the variable data is popped up. You can drag the function name and then click the mouse right button to display the source file corresponding to the function. You can drag the C language variable and then click the mouse right button to register the variable as the C watch point. You can drag the assembler symbol and then click the mouse right button to register the symbol as the ASM watch point. You can open the displayed source file on the editor. (You must have registered the editor name.) The source file being displayed can be edited. The source file can also be edited on an external editor. (The editor name must be registered.) You can display the coverage measurement result by specifying the option. (It is not displayed by default.) (PD32R/PD32RM PD32R/PD32RM does not support this.) You can line-assemble the clicked position. The program window's source display mode (edit mode) is configured as shown below. The line number display, address display, and breakpoint display areas are not shown. The right-click menu changes for exclusive use in edit mode. The status bar on the PDxx window shows the line and column numbers of the cursor position. 1.2.2 Configuration of MIX Display Mode The mix display mode of the window is the following configurations. 51 · · · · · · · · · · You can switch "Display/Hide" for the line number display area/address display area/object code display area. You can change the source file to be displayed by double-clicking the line number display area. You can change the display start address/display start line by double-clicking the address display area. You can set/reset the breakpoint by clicking (or double-clicking) the breakpoint display area. You can change the display ratio between the object code display area and the label display area, and between the label display area and the program display area, using the mouse. You can open the displayed source file on the editor. (You must have registered the editor name.) You can display the coverage measurement result by specifying the option. (It is not displayed by default.) The MIX display result can be saved as a text file. You can line-assemble the clicked position. You can scroll the display up/down in units of source line. 1.2.3 Configuration of Disassemble Display Mode The disassemble display mode of the window is the following configurations. 52 1 Windows/Dialogs · · · · You can switch "Display/Hide" for the address display area/object code display area. · You can display the coverage measurement result by specifying the option. (It is not displayed by default.) · You can line-assemble the clicked position. You can change the display start address by double-clicking the address display area. You can set/reset the breakpoint by clicking (or double-clicking) the breakpoint display area. You can change the display ratio between the object code display area and the label display area, and between the label display area and the program display area, using the mouse. 1.2.4 Extended Menus The Program window provides the following menu when being active. (This menu is called Program window option.) Menu Menu Options Function Option Font. Change font. TAB. Set source file display tabs. Color. Change display color View Change contents of display. Display from specified source file or function. Source. Display from specified address or line No. Address. Display from current program counter. Program Counter Mode Switch display mode. Switch to source display mode. Source Mode Switch to MIX display mode. Mix Mode Switch to disassemble display mode. Disasm Mode 53 Layout Line Area Address Area Code Area Line Assemble. Save Mix. Coverage On/Off Base. Clear Refresh Edit On Save Save As. Save All Set layout. Switch display or non-display of line No. area. Switch display or non-display of address area. Switch display or non-display of object code area. Open Line Assemble dialog. Saves MIX display result Set Coverage measurement. Switch display or non-display of Measurement result. Change coverage base address Initialize coverage measurement result Update display of coverage measurement result Edit functions Turns editing on or off Saves the edited contents by overwriting Saves the edited contents with another name Saves all of the edited contents by overwriting 1.2.5 Shortcut Menu The Program window provides the shortcut menu by clicking the mouse right button within the window. (This menu is called Program window right-click menu.) The menu content varies depending on the clicked position. When right-clicking the line number display area or address display area The shortcut menu same as the option menu appears. When right-clicking the breakpoint display area The shortcut menu does not appear. Hardware break can be set. When right-clicking other area The following shortcut menu appears. (Debug Mode) Menu Menu Options Right-Click Jump to function Open Source Window Set PC here Add C Watch. Add C Watch Pointer. Add ASM Watch BitAdd ASM Watch Open Editor Line Assemble. Save Mix. Edit On (Edit mode) Menu Right-Click Menu Options Copy Paste Cut Delete Undo Find Function Display the selected function Display the selected function (by Source Window) Sets the PC at the cursor position Register the C watch point on selected variable Register the C watch point on selected pointer variable Register the ASM watch point on selected symbol Register the ASM watch point on selected bit symbol Open the source file by the editor Open the Line Assemble dialog. Saves MIX display result Edit functions Turns editing on or off Function Same [Edit]->[Copy] menu. Same [Edit]->[Paste] menu. Same [Edit]->[Cut] menu. Same [Edit]->[Delete] menu. Same [Edit]->[Undo] menu. Find character strings. 54 1 Windows/Dialogs Font Tab Edit On Save Save As. Save All Change font. Set source file display tabs. Edit functions Turns editing on or off Saves the edited contents by overwriting Saves the edited contents with another name Saves all of the edited contents by overwriting 1.3 Source Window The Source window continuously displays any position of the source file. (The Program window always displays the source file corresponding to the current program counter position.) When the program counter points the displayed source file position, its background is displayed in yellow. Like the Program window, the Source window allows you to execute the source program up to the cursor position, set/reset the software breakpoint and perform line-assemble. You can open up to 30 Source windows. 1.3.1 Configuration of Source Window The Source Window configuration, toolbar and option menu is the same as that in the Program Window. Please refer to Program Window. 1.4 Register Window The Register window displays the register data and flag data. You can change a register/flag value from the window. 1.4.1 Configuration of Register Window The figure below shows a Register window of the debugger PD30 for M16C/60 M16C/60, 20 series. 55 · · · · · If a register/flag value is changed, the value is displayed in red. Double-clicking the register display line opens a dialog, which allows you to change a register value. You can change a flag value by clicking the button corresponding to the flag. The right-click menu allows you to change the display radix point and the register bank. (Only PD308 PD308(F/SIM) and PD30(SIM) support the register bank switching function.) You can change the display ratio between the register name display area and the register value display area, and between the register value display area and the radix point display area, using the mouse. 1.4.2 Extended Menus The Register window provides the following menu when being active. (This menu is called Register window option.) Menu Option Menu Options Bank0 Bank1 Layout Hide Radix Hide FLAGs Font. Function Display registers of bank 0. Display registers of bank 1. Set layout Switch display or non-display of radix. Switch display or non-display of flags display area. Change font. 1.4.3 Shortcut Menu Press the right button on the register display area in Register Window to display shortcut menu. Menu Right Click Menu Options Hex Dec Bin Function Display in hexadecimal. Display in decimal. Display in binary. 56 1 Windows/Dialogs Bank0 Bank1 Layout Hide Radix Hide FLAGs Font. Display registers of bank 0. Display registers of bank 1. Set layout. Switch display or non-display of radix Switch display or non-display of flags display area. Change font. 1.4.4 Memory Window The Memory Window displays the contents of contiguous memory in "address", "label", and "data (contents of memory)" formats. The display is updated after each command is executed. Data can be displayed in binary, decimal, hexadecimal, and ASCII. You can open up to 30 Memory Windows. You can use the Memory Windows to modify the contents of memory, and also to fill and move specified blocks of memory. 1.4.5 Configuration of Memory Window · · · · · The display start address and memory contents can be changed by in-place editing. Different memory areas can be inspected at the same time by dividing the window into halves. It is possible to keep track of the stack pointer position (by default, not tracked). Coverage measurement results can be displayed. Memory contents can be stored in a text file. 1.4.6Option Menu The Memory window provides the following menu when being active. (This menu is called Memory window option.) Menu Menu Options Function 57 Option Set data at specified address. Set. Fill specified memory block with data. Fill. Move specified memory block to Move. Save Memory Contents. Saving Memory Contents in a Text File Address. Specify display starting address. Specify scroll range. Scroll Area. Starting address to value of the register. Register (Product dependence menu) (xxxxx) *1 Followed Stack Pointer. Keep tracking of the stack pointer position. Startup label settings Set Start Up Symbol. Refresh display. Refresh Data Length Specify data length. Byte Display in 1-byte units. Word Display in 2-byte units. Lword Display in 4-byte units. Radix Specify data radix. Display in hexadecimal. Hex Display in decimal. Dec Display in binaly. Bin Specify data code. Code Display as ASCII characters. ASCII Display as SJIS characters. SJIS Display as JIS characters. JIS Set layout. Layout Switch display or non-display of Label area. Label Switch display or non-display of Register area. Register Changing the number of digits displayed Column. Coverage Set Coverage measurement. Switch display or non-display of Measurement result Enable Change coverage base address Base Initialize coverage measurement result Clear Font. Change font Change display color Color. These menus can be selected even by the short cut menu by a right click in the window. *1 Product Dependence Menu Product Menu PD308 PD308 FB PD30 SB USP ISP Function Starting address to value of FB register. Starting address to value of SB register. Starting address to value of USP register. Starting address to value of ISP register. 1.5 RAM Monitor Window The RAM monitor window is a window in which changes of memory contents are displayed while running the target program. The relevant memory contents are displayed in dump form in the RAM monitor area (in varying sizes depending on the emulator used) by using the realtime RAM monitor function. The displayed contents are updated at given intervals (by default, every 100 ms) while running the target program. For the PC4701 PC4701, up to 10 windows can be opened. 58 1 Windows/Dialogs · · · The RAM monitor area can be changed to any desired address range. Refer to "Setting the RAM monitor area" for details on how to change the RAM monitor area. The default RAM monitor area is mapped into a 1-Kbyte area beginning with the start address of the internal RAM. The display content updating interval can be set for each window individually. The actual updating interval at which the display contents are actually updated while running the target program is shown in the title field of the Address display area. The background colors of the data display and code display areas are predetermined by access attribute, as shown below. Access attribute Background color Read accessed address Green Write accessed address Red Non-accessed address White The background colors can be changed. ATTENTION · · · · · · · The RAM monitor window shows the data that have been accessed through the bus. Therefore, changes are not reflected in the displayed data unless they have been accessed via the target program as in the case where memory is rewritten directly from an external I/O. If the data in the RAM monitor area are displayed in lengths other than the byte, it is possible that the data will have different memory access attributes in byte units. If bytes in one data have a different access attribute as in this case, those data are enclosed in parentheses when displayed in the window. In that case, the background color shows the access attribute of the first byte of the data. The interval time at which intervals the display is updated may be longer than the specified interval depending on the operating condition (shown below). Host machine performance/load condition Communication interface Window size (memory display range) or the number of windows displayed The displayed access attributes are initialized by downloading the target program. 1.5.1 Extended Menus The RAM Monitor window provides the following menu when being active. (This menu is called RAM Monitor window option.) 59 Menu RAM Monitor Area. Sampling Period. Clear Up Down Address. ScrollArea. Data Length Radix Code Layout Column. Font. Color. Byte Word Lword Hex Dec Bin ASCII SJIS JIS Label Register Function Sets RAM monitor area A window or dialog box in which you can change the RAM monitor area is displayed. Sets display updating interval Sets an interval time at which intervals you want the display to be updated while running the target program. Clears access attribute The data in all RAM monitor areas are cleared, as are the displayed access attributes. Moves display position to the immediately preceding RAM area (smaller address) The display position is moved forward (toward smaller addresses) to the beginning of the RAM monitor area that immediately precedes the current display position. Moves display position to the immediately following RAM area (larger address) The display position is moved backward (toward larger addresses) to the beginning of the RAM monitor area that immediately follows the current display position. Display from specified address. Specify scroll range. Display in 1-byte units. Display in 2-byte units. Display in 4-byte units. Display in hexadecimal. Display in decimal. Display in binary. Display as ASCII characters. Display as SJIS characters. Display as JIS characters. Switch display or non-display of Label area. Switch display or non-display of Register area. Set up the number of column displayed on one line. Change font. Set color of access attribute display. These menus can be selected even by the short cut menu by a right click in the window. 1.6 ASM Watch Window The ASM watch window is a window in which you can register specific addresses as watchpoints and inspect memory contents at those addresses. If a registered address resides within the RAM monitor area, the memory content at that address is updated at given intervals (by default, every 100 ms) during program execution. The toolbar buttons may be used to perform the main functions. 60 1 Windows/Dialogs 1.6.1 Overview of ASM Watch Window · · · · · · · · · The addresses to be registered are called the "watchpoints." One of the following can be registered: Address (can be specified using a symbol) Address + Bit number Bit symbol The registered watchpoints are stored in an environment setup file when the ASM watch window is closed and are automatically registered in the debugger when the window is reopened. If symbols or bit symbols are specified for the watchpoints, the watchpoint addresses are recalculated when downloading the target program. The invalid watchpoints are marked by "-" when displayed on the screen. The order in which the watchpoints are listed can be changed by a drag-and-drop operation. The watchpoint symbols, sizes and radixes can be changed by in-place editing. ATTENTION · · The RAM monitor obtains the data accessed through the bus. Any change other than the access from the target program will not be reflected. If the display data length of the RAM monitor area is not 1 byte, the data's access attribute to the memory may varies in units of 1 byte. In such a case that the access attribute is not unified within a set of data, the data's access attribute cannot be displayed correctly. In this case, the background colors the access attribute color of the first byte of the data. 1.6.2 Extended Menus When the ASM watch window is active, the following menus can be used. Menu Add. Add Bit. Remove Remove All. Function Add watch point. Add bit-level watch point. Remove selected watch point. Remove all watch points. Set. Radix Bin Set new data to selected watch point. Change display radix. Display value in binary. 61 Display value in decimal. Dec Display value in hexadecim