Hitachi Microcomputer Development Environment H8/3048-Series, H8/3048F Emulator E7000 HS3048EPD70H User's Manual HITACHI HS3048EPD70HE Preface Thank you for purchasing the emulator for Hitachi's H8/3048-series and H8/3048F original microcomputers. The H8/3048-series and H8/3048F emulator (hereafter abbreviated to the H8/3048 emulator) is an efficient software and hardware development tool for systems based on Hitachi's H8/3048, H8/3047, H8/3044, and H8/3048F original microcomputers (hereafter abbreviated to MCU). By exchanging the emulator pod, this emulator can also be used for other H-series microcomputers. The H8/3048 series includes three types of microcomputers: H8/3048, H8/3047, and H8/3044. The H8/3048F has the same functions as the H8/3048 except that it has flash memory instead of internal ROM. The descriptions in this manual apply to all MCUs unless otherwise specified. There are two types of H8/3048 emulator: the E7000 and the E7000PC, which is used only with the IBM PC. This manual describes the functions and operating procedures of the E7000 and E7000PC for the MCU. To use the E7000, please read Part I, E7000 Guide, and Part III, Emulator Function Guide. To use the E7000PC, please read Part II, E7000PC Guide, and Part III, Emulator Function Guide. Please read this manual carefully in order to gain a full understanding of the emulator's performance. In particular, be sure to read section 1.1, Warnings, in Part I, E7000 Guide, or in Part II, E7000PC Guide before use. Two 3.5-inch floppy disks are provided together with the emulator pod. The E7000 system disk is marked with "E7000" below the HITACHI mark on the label, and the E7000PC disk is marked with "E7000PC". H8/3048 E7000PC SYSTEM H8/3048 E7000 SYSTEM 1. SYSTEM (HS3048EPD70SF) Vn.m 1. SYSTEM (HS3048EPD70SF) Vn.m 2. PC I/F 2. DIAGNOSTIC TEST (HS7000EII01SF) 3. DIAGNOSTIC TEST XX.XX.XX Vn.m Vn.m Vn.m HITACHI E7000PC (1) E7000PC system disk XX.XX.XX HITACHI E7000 (2) E7000 system disk The E7000 system floppy disk must be backed up to another floppy disk using the E7000. For details, refer to section 3.6, Floppy Disk Backup, in Part I, E7000 Guide. The contents of the E7000PC system floppy disk must be installed (copied) to the personal computer connected to the emulator. For details, refer to section 3.4, System Software Installation, in Part II, E7000PC Guide. Related Manuals: H8/300 Series Cross Assembler User's Manual H Series Linkage Editor User's Manual H Series Librarian User's Manual H8/300H E7000 Graphical User Interface Software User's Manual H8/300H E7000PC Graphical User Interface Software User's Manual H8/300 Series C Compiler User's Manual HS7000EST01H Manual HS7000ESTP1H Manual LAN Board Manual Description Notes on Using the IBM PC Interface Board (HS7000EII01H) Memory Board Manual Bus Monitor Manual Bus Monitor Interface Board Manual When the E7000 is configured in remote mode, as described in section 2.3.2, RS-232C Interface System Configuration in Part I, E7000 Guide, refer to the following manual: H-Series Interface Software User's Manual Notes: 1. Ethernet is a registered trademark of Xerox Corporation. 2. IBM PC is a registered trademark of International Business Machines Corporation. 3. MS-DOS is a registered trademark and Windows is a trademark of Microsoft Corporation. 4. SPARC is a registered trademark of SPARC International, Inc. Contents Part I E7000 Guide Section 1 1.1 1.2 1.3 Overview ..................................................................................................... Warnings ........................................................................................................................ Environmental Conditions .............................................................................................. Components .................................................................................................................... 1.3.1 E7000 Emulator Station.................................................................................. 1.3.2 E7000 Emulator Pod....................................................................................... 1.3.3 Options............................................................................................................ 1-1 1-4 1-5 1-6 1-6 1-7 1-8 Section 2 2.1 2.2 2.3 Components ................................................................................................ 2-1 E7000 Hardware Components........................................................................................ 2-1 2.1.1 Emulator Station Components........................................................................ 2-2 2.1.2 Emulator Pod Components ............................................................................. 2-5 E7000 Software Components ......................................................................................... 2-7 System Configuration ..................................................................................................... 2-9 2.3.1 System Configuration Using LAN Interface .................................................. 2-9 2.3.2 System Configuration Using RS-232C Interface ........................................... 2-10 Section 3 3.1 3.2 3.3 3.4 3.5 Preparation before Use ............................................................................ E7000 Preparation .......................................................................................................... E7000 Connection .......................................................................................................... 3.2.1 Connecting Emulator Pod............................................................................... 3.2.2 External Probe Connector............................................................................... 3.2.3 Clock Selection............................................................................................... 3.2.4 Connecting System Ground............................................................................ System Connection ......................................................................................................... 3.3.1 Connecting to a Console................................................................................. 3.3.2 Setting up Console Interface........................................................................... 3.3.3 Connecting to a Host System ......................................................................... 3.3.4 Connecting to a Printer ................................................................................... 3.3.5 Connecting to a LAN Interface....................................................................... 3.3.6 System Connection Examples ........................................................................ Power-On Procedure for the E7000................................................................................ 3.4.1 Power-On Procedure for LAN Interface......................................................... 3.4.2 Power-On Procedure for RS-232C Interface.................................................. E7000 Monitor Commands............................................................................................. 3.5.1 E7000 Monitor Initiation ................................................................................ 3.5.2 S ...................................................................................................................... 3.5.3 R...................................................................................................................... 3-1 3-1 3-2 3-2 3-4 3-5 3-7 3-8 3-8 3-9 3-11 3-12 3-12 3-14 3-19 3-19 3-23 3-24 3-24 3-26 3-27 3.6 3.7 3.5.4 B...................................................................................................................... 3.5.5 F ...................................................................................................................... 3.5.6 L...................................................................................................................... 3.5.7 T...................................................................................................................... Floppy Disk Backup ....................................................................................................... 3.6.1 Floppy Disk Formatting.................................................................................. 3.6.2 Floppy Disk Backup and Verification ............................................................ E7000 System Program Initiation................................................................................... 3.7.1 Initiation on E7000 Monitor ........................................................................... 3.7.2 Automatic Initiation of E7000 System Program ............................................ Section 4 Operating Examples ................................................................................. 3-28 3-31 3-32 3-34 3-35 3-35 3-36 3-39 3-39 3-42 Basic Examples............................................................................................................... 4.1.1 Preparing for Connection of LAN Host System............................................. 4.1.2 Specifying the MCU Operating Mode............................................................ 4.1.3 Allocating Standard Emulation Memory and Specifying Attributes.............. 4.1.4 Loading the User Program.............................................................................. 4.1.5 Executing Program ......................................................................................... 4.1.6 PC Break......................................................................................................... 4.1.7 Single-Step Execution .................................................................................... 4.1.8 Setting Hardware Break Conditions ............................................................... 4.1.9 Displaying Trace Information......................................................................... Application Examples..................................................................................................... 4.2.1 Break with Pass Count Condition................................................................... 4.2.2 Conditional Trace ........................................................................................... 4.2.3 Parallel Mode.................................................................................................. 4.2.4 Searching Trace Information .......................................................................... 4.2.5 Sequential PC Break ....................................................................................... 4-1 4-3 4-3 4-5 4-6 4-7 4-9 4-10 4-11 4-12 4-13 4-14 4-14 4-15 4-16 4-17 4-18 Appendix A Floppy Disk Drive Specifications ........................................................ A-1 Appendix B Connector Specifications ........................................................................ B-1 B-1 B-2 B-3 B-5 B-6 B-7 B-8 4.1 4.2 B.1 B.2 B.3 B.4 B.5 B.6 B.7 Console Connector.......................................................................................................... Host System Connector .................................................................................................. Printer Connector............................................................................................................ LAN Connector ............................................................................................................. E7000 to Console Connection ........................................................................................ E7000 to Host System Connection ................................................................................. Printer Cable Connection................................................................................................ Part II E7000PC Guide Section 1 1.1 1.2 1.3 Overview ..................................................................................................... Warnings ........................................................................................................................ Environmental Conditions .............................................................................................. Components .................................................................................................................... 1.3.1 E7000PC Emulator Station............................................................................. 1.3.2 E7000PC Emulator Pod.................................................................................. 1.3.3 IBM PC Interface Board................................................................................. 1.3.4 Options............................................................................................................ Section 2 2.1 2.2 2.3 E7000PC Hardware Components ................................................................................... 2.1.1 E7000PC Emulator Station Components........................................................ 2.1.2 E7000PC Emulator Pod Components............................................................. E7000PC Software Components .................................................................................... System Configuration ..................................................................................................... Section 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 Components ................................................................................................ Preparation before Use ............................................................................ E7000PC Preparation...................................................................................................... E7000PC Connection...................................................................................................... 3.2.1 Connecting Emulator Pod............................................................................... 3.2.2 External Probe Connector............................................................................... 3.2.3 Clock Selection............................................................................................... 3.2.4 Connecting System Ground............................................................................ System Connection ......................................................................................................... 3.3.1 IBM PC Interface Board Specifications ......................................................... 3.3.2 Setting the Switches on the IBM PC Interface Board .................................... 3.3.3 Installing the IBM PC Interface Board........................................................... 3.3.4 Connecting the IBM PC Interface Board to the E7000PC Emulator Station . System Software Installation .......................................................................................... 3.4.1 E7000PC System Disk.................................................................................... 3.4.2 Installation ...................................................................................................... Power-On Procedure for the E7000PC........................................................................... E7000PC Monitor Commands........................................................................................ 3.6.1 E7000PC Monitor Initiation ........................................................................... 3.6.2 E7000PC System Program Initiation.............................................................. Interface Software Operations ........................................................................................ 3.7.1 Initiating Interface Software ........................................................................... 3.7.2 Initiating from Windows................................................................................. 3.7.3 Emulation Support Function........................................................................... 3.7.4 Notes ............................................................................................................... 1-1 1-4 1-5 1-6 1-6 1-7 1-7 1-8 2-1 2-1 2-2 2-5 2-7 2-9 3-1 3-1 3-2 3-2 3-4 3-5 3-7 3-8 3-8 3-9 3-12 3-13 3-14 3-14 3-15 3-16 3-17 3-17 3-19 3-23 3-23 3-24 3-24 3-27 Section 4 4.1 4.2 Operating Examples ................................................................................. Basic Examples............................................................................................................... 4.1.1 Preparing for Connection of IBM PC............................................................. 4.1.2 Specifying the MCU Operating Mode............................................................ 4.1.3 Allocating Standard Emulation Memory and Specifying Attributes.............. 4.1.4 Executing Program ......................................................................................... 4.1.5 PC Break......................................................................................................... 4.1.6 Single-Step Execution .................................................................................... 4.1.7 Setting Hardware Break Conditions ............................................................... 4.1.8 Displaying Trace Information......................................................................... Application Examples..................................................................................................... 4.2.1 Break with Pass Count Condition................................................................... 4.2.2 Conditional Trace ........................................................................................... 4.2.3 Parallel Mode.................................................................................................. 4.2.4 Searching Trace Information .......................................................................... 4.2.5 Sequential PC Break ....................................................................................... Part III Section 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 4-1 4-3 4-3 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-12 4-13 4-14 4-15 4-16 Emulator Function Guide Emulator Functions ................................................................................. Overview ........................................................................................................................ Specification ................................................................................................................... Realtime Emulation ........................................................................................................ 1.3.1 Normal Mode.................................................................................................. 1.3.2 Cycle Reset Mode........................................................................................... 1.3.3 Parallel Mode.................................................................................................. Break Function................................................................................................................ 1.4.1 Hardware Break .............................................................................................. 1.4.2 PC Break ........................................................................................................ 1.4.3 Forced Break................................................................................................... 1.4.4 Write Protect/Guarded Break ......................................................................... Realtime Trace Function................................................................................................. 1.5.1 Trace Timing .................................................................................................. 1.5.2 Trace Condition Setting ................................................................................. 1.5.3 Trace Display.................................................................................................. Single-Step Function ...................................................................................................... 1.6.1 Single-Step Execution .................................................................................... 1.6.2 Setting Display Information ........................................................................... 1.6.3 Termination of Single-Step Function ............................................................. Execution Time Measurement........................................................................................ Trigger Output ................................................................................................................ Memory Access Function ............................................................................................... 1-1 1-1 1-2 1-9 1-9 1-10 1-12 1-15 1-15 1-24 1-27 1-27 1-28 1-28 1-30 1-33 1-34 1-34 1-35 1-35 1-35 1-38 1-40 1.10 1.11 1.12 1.13 1.14 1.15 MCU Control and Status Check .................................................................................... Emulation Monitoring Function ..................................................................................... Operating Voltage and Frequency .................................................................................. Flash Memory Usage...................................................................................................... 1.13.1 On-Board Programming ................................................................................. 1.13.2 Flash Memory Operation................................................................................ Symbolic Debugging ...................................................................................................... 1.14.1 Defining Symbols .......................................................................................... 1.14.2 Symbol Reference........................................................................................... 1.14.3 Symbol Deletion ............................................................................................ 1.14.4 Symbol Display .............................................................................................. Assembly Function ......................................................................................................... 1.15.1 Overview......................................................................................................... 1.15.2 Instruction Format .......................................................................................... 1.15.3 Definition of Label Names as Symbols .......................................................... 1.15.4 Label Name Reference ................................................................................... 1.15.5 Disassembly.................................................................................................... Section 2 2.1 2.2 2.3 2.4 2.5 Differences between the MCU and the Emulator ........................... Flash Memory (H8/3048F) ............................................................................................. 2.1.1 On-Board Programming Modes ..................................................................... 2.1.2 Flash Memory Operating Modes .................................................................... Register Values at Reset ................................................................................................. User Interface.................................................................................................................. Crystal Oscillator ............................................................................................................ Load Capacitance............................................................................................................ Section 3 3.1 3.2 3.3 3.4 3.5 3.6 MCU Function Support ........................................................................... Setting the MCU Operating Mode.................................................................................. Memory Space ................................................................................................................ 3.2.1 Internal ROM Area ........................................................................................ 3.2.2 Internal RAM Area ......................................................................................... 3.2.3 Internal I/O Area............................................................................................. 3.2.4 Unusable Area ................................................................................................ 3.2.5 External Memory Area ................................................................................... 3.2.6 Reserved Areas ............................................................................................... 3.2.7 Flash Memory Area ........................................................................................ Low-Power Mode (Sleep, Hardware Standby, and Software Standby) ......................... 3.3.1 Hardware Standby Mode ................................................................................ 3.3.2 Sleep and Software Standby Modes ............................................................... Interrupts ........................................................................................................................ Control Input Signals (RES, WAIT, BREQ).................................................................. Watchdog Timer (WDT) ................................................................................................ 1-41 1-43 1-45 1-46 1-46 1-47 1-49 1-49 1-50 1-50 1-51 1-51 1-51 1-52 1-55 1-55 1-56 2-1 2-1 2-1 2-1 2-3 2-3 2-3 2-3 3-1 3-1 3-2 3-2 3-3 3-3 3-3 3-3 3-4 3-4 3-5 3-5 3-5 3-5 3-5 3-6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 Integrated Timer Pulse Unit (ITU) and Programmable Timing Pattern Controller (TPC)............................................................................................................. Serial Communications Interface ................................................................................... DMAC ........................................................................................................................ Wait State Controller ...................................................................................................... I/O Port ........................................................................................................................ A/D and D/A Converter.................................................................................................. Refresh Controller .......................................................................................................... Clock Pulse Generator .................................................................................................... Section 4 User System Interface Circuit ............................................................... 4-1 Troubleshooting ......................................................................................... Internal System Test Using the E7000 ........................................................................... Internal system Test Using the E7000PC ....................................................................... Troubleshooting Procedure............................................................................................. 5-1 5-1 5-5 5-8 Section 5 5.1 5.2 5.3 Section 6 6.1 6.2 Command Input and Display ................................................................. Command Syntax............................................................................................................ 6.1.1 Command Input Format.................................................................................. 6.1.2 Help Function ................................................................................................. 6.1.3 Word Definition.............................................................................................. Special Key Input ........................................................................................................... 6.2.1 Command Execution and Termination .......................................................... 6.2.2 Display Control............................................................................................... 6.2.3 Command Re-entry......................................................................................... 6.2.4 Cursor Control and Character Editing ............................................................ Section 7 7.1 7.2 3-6 3-6 3-6 3-6 3-6 3-7 3-7 3-7 Emulation Commands ............................................................................. Overview ........................................................................................................................ Emulation Commands .................................................................................................... 7.2.1 .<register>....................................................................................................... 7.2.2 !<symbol> or &<symbol> .............................................................................. 7.2.3 ABORT........................................................................................................... 7.2.4 ASSEMBLE ................................................................................................... 7.2.5 BREAK........................................................................................................... 7.2.6 BREAK_CONDITION1,2,3,4 ....................................................................... 7.2.7 BREAK_SEQUENCE ................................................................................... 7.2.8 CHECK........................................................................................................... 7.2.9 CLOCK........................................................................................................... 7.2.10 COMMAND_CHAIN .................................................................................... 7.2.11 CONVERT ..................................................................................................... 7.2.12 DATA_CHANGE........................................................................................... 6-1 6-1 6-1 6-1 6-2 6-4 6-4 6-5 6-5 6-6 7-1 7-1 7-3 7-4 7-7 7-9 7-10 7-13 7-17 7-26 7-29 7-31 7-33 7-35 7-37 7.2.13 7.2.14 7.2.15 7.2.16 7.2.17 7.2.18 7.2.19 7.2.20 7.2.21 7.2.22 7.2.23 7.2.24 7.2.25 7.2.26 7.2.27 7.2.28 7.2.29 7.2.30 7.2.31 7.2.32 7.2.33 7.2.34 7.2.35 7.2.36 7.2.37 7.2.38 7.2.39 7.2.40 7.2.41 7.2.42 7.2.43 7.2.44 7.2.45 7.2.46 7.2.47 7.2.48 7.2.49 DATA_SEARCH ........................................................................................... DISASSEMBLE ............................................................................................. DISPLAY_COVERAGE................................................................................ DUMP............................................................................................................. END ................................................................................................................ EXECUTION_MODE.................................................................................... FILL................................................................................................................ GO................................................................................................................... HELP .............................................................................................................. HISTORY ....................................................................................................... ID .................................................................................................................... LED1,2,3,4 ..................................................................................................... LED_OUT1,2 ................................................................................................ MAP................................................................................................................ MEMORY ...................................................................................................... MODE............................................................................................................. MOVE............................................................................................................. MOVE_TO_RAM .......................................................................................... PERFORMANCE_ANALYSIS ..................................................................... PRINT............................................................................................................. QUIT............................................................................................................... RADIX............................................................................................................ REGISTER ..................................................................................................... RESET ............................................................................................................ RESULT ......................................................................................................... SET_COVERAGE ......................................................................................... SHORT_SYMBOL......................................................................................... STATUS ......................................................................................................... STEP ............................................................................................................... STEP_INFORMATION ................................................................................. STEP_OVER .................................................................................................. SYMBOL........................................................................................................ TRACE ........................................................................................................... TRACE_CONDITION ................................................................................... TRACE_MEMORY ....................................................................................... TRACE_MODE ............................................................................................. TRACE_SEARCH ......................................................................................... 7-39 7-41 7-44 7-47 7-50 7-51 7-58 7-60 7-69 7-72 7-73 7-74 7-77 7-79 7-83 7-86 7-89 7-91 7-92 7-96 7-98 7-101 7-103 7-104 7-105 7-107 7-108 7-110 7-113 7-119 7-122 7-126 7-130 7-138 7-146 7-148 7-150 Floppy Disk Utility ................................................................................... Overview ........................................................................................................................ Floppy Disk Format........................................................................................................ Files ........................................................................................................................ 8.3.1 File Names ...................................................................................................... 8-1 8-1 8-2 8-2 8-2 Section 8 8.1 8.2 8.3 8.4 8.3.2 File Configuration........................................................................................... Floppy Disk Utility Commands...................................................................................... 8.4.1 FILE_COPY ................................................................................................... 8.4.2 FILE_DIRECTORY ....................................................................................... 8.4.3 FILE_DUMP .................................................................................................. 8.4.4 FILE_ERASE ................................................................................................ 8.4.5 FILE_LOAD................................................................................................... 8.4.6 FILE_RENAME ............................................................................................ 8.4.7 FILE_SAVE ................................................................................................... 8.4.8 FILE_TYPE.................................................................................................... 8.4.9 FILE_VERIFY ............................................................................................... 8.4.10 FLOPPY_CHECK.......................................................................................... 8.4.11 FLOPPY_FORMAT....................................................................................... Section 9 9.1 9.2 9.3 9.4 Overview ........................................................................................................................ Host System Interface Modes and Operating Procedures .............................................. 9.2.1 Transparent Mode........................................................................................... 9.2.2 Local Mode..................................................................................................... 9.2.3 Remote Mode.................................................................................................. Data Transfer Control ..................................................................................................... 9.3.1 Control Methods ............................................................................................. 9.3.2 Timeouts ......................................................................................................... Host-System Related Commands ................................................................................... 9.4.1 HOST.............................................................................................................. 9.4.2 LOAD ............................................................................................................. 9.4.3 SAVE.............................................................................................................. 9.4.4 TERMINAL.................................................................................................... 9.4.5 TRANSFER.................................................................................................... 9.4.6 VERIFY.......................................................................................................... 9.4.7 INTFC_LOAD................................................................................................ 9.4.8 INTFC_SAVE ................................................................................................ 9.4.9 INTFC_TRANSFER ...................................................................................... 9.4.10 INTFC_VERIFY ............................................................................................ Section 10 10.1 10.2 Data Transfer from Host System Connected by RS-232C Interface .............................................................................. 8-3 8-4 8-5 8-8 8-10 8-13 8-15 8-17 8-18 8-20 8-21 8-23 8-24 9-1 9-1 9-2 9-2 9-3 9-5 9-7 9-7 9-7 9-8 9-9 9-12 9-16 9-19 9-21 9-25 9-28 9-31 9-33 9-35 Data Transfer from Host System Connected by LAN Interface ...................................................................................... 10-1 Overview ........................................................................................................................ LAN Data Transfer ......................................................................................................... 10.2.1 Setting the Data Transfer Environment .......................................................... 10.2.2 Data Transfer .................................................................................................. 10.2.3 Notes on FTP Interface .................................................................................. 10-1 10-3 10-3 10-4 10-4 10.3 LAN Commands............................................................................................................. 10.3.1 ASC................................................................................................................. 10.3.2 BIN ................................................................................................................. 10.3.3 BYE ................................................................................................................ 10.3.4 CD................................................................................................................... 10.3.5 CLOSE............................................................................................................ 10.3.6 FTP ................................................................................................................. 10.3.7 LAN ................................................................................................................ 10.3.8 LAN_HOST.................................................................................................... 10.3.9 LAN_LOAD ................................................................................................... 10.3.10 LAN_SAVE.................................................................................................... 10.3.11 LAN_TRANSFER.......................................................................................... 10.3.12 LAN_VERIFY................................................................................................ 10.3.13 LS.................................................................................................................... 10.3.14 OPEN.............................................................................................................. 10.3.15 PWD ............................................................................................................... 10.3.16 STA................................................................................................................. 10.3.17 LOGOUT........................................................................................................ Section 11 11.1 11.2 11.3 Data Transfer between E7000PC and IBM PC ................................ Overview ........................................................................................................................ E7000PC and IBM PC System Connection.................................................................... E7000PC-Related Data Transfer Commands ................................................................. 11.3.1 LOAD ............................................................................................................. 11.3.2 SAVE.............................................................................................................. 11.3.3 VERIFY.......................................................................................................... 10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-13 10-14 10-18 10-22 10-23 10-25 10-27 10-28 10-30 10-31 10-32 11-1 11-1 11-1 11-3 11-4 11-7 11-9 Section 12 12.1 12.2 Error Messages .......................................................................................... 12-1 E7000 Error Messages.................................................................................................... 12-1 IBM PC Interface Software Error Messages .................................................................. 12-12 Appendix A Emulator External Dimensions and Weight ...................................... A-1 Appendix B Memory Map .............................................................................................. B-1 Appendix C ASCII Codes............................................................................................... C-1 Figures Part I E7000 Guide 1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 4-1 B-1 B-2 B-3 B-4 B-5 B-6 B-7 B-8 H8/3048-Series, H8/3048F E7000 Emulator.................................................................. E7000 Emulator Hardware Components ....................................................................... E7000 Emulator Station Front Panel ............................................................................. E7000 Emulator Station Rear Panel .............................................................................. E7000 Emulator Pod ...................................................................................................... E7000 Emulator Software Components ........................................................................ System Configuration Using LAN Interface ................................................................. System Configuration Using RS-232C Interface .......................................................... E7000 Preparation Flow Chart ...................................................................................... Connecting Station-Pod Interface Cables to Emulator Station ...................................... Connecting Station-Pod Interface Cables to Emulator Pod ........................................... Connecting External Probe ............................................................................................ Installing Crystal Oscillator............................................................................................ Connecting System Ground ........................................................................................... Connecting Frame Ground ............................................................................................ Console Interface Switches ............................................................................................ Ethernet Interface ........................................................................................................... Cheapernet Interface ...................................................................................................... Connection in Stand-Alone Mode ................................................................................. Connection in Transparent Mode .................................................................................. Connection in Local Mode ............................................................................................ Connection in Remote Mode ......................................................................................... Printer Connection ......................................................................................................... Power-On Procedure for LAN Interface ........................................................................ Power-On Procedure for RS-232C Interface ................................................................. Program Execution Flow ............................................................................................... Console Connector Pin Locations ................................................................................. Host System Connector Pin Locations .......................................................................... Printer Cable Connector Pin Layouts ............................................................................ Data Output Timing ....................................................................................................... LAN Connector Pin Locations ...................................................................................... Console to E7000 Wiring .............................................................................................. Host System to E7000 Wiring ....................................................................................... Host System Wiring (Using Other Cable) ..................................................................... 1-2 2-1 2-2 2-3 2-5 2-8 2-9 2-10 3-1 3-2 3-3 3-4 3-5 3-7 3-7 3-9 3-14 3-15 3-16 3-16 3-17 3-18 3-18 3-19 3-23 4-18 B-1 B-2 B-3 B-4 B-5 B-6 B-7 B-7 Part II E7000PC Guide 1-1 2-1 2-2 2-3 2-4 2-5 2-6 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 4-1 H8/3048-Series, H8/3048F E7000PC Emulator............................................................. E7000PC Emulator Hardware Components .................................................................. E7000PC Emulator Station Front Panel ........................................................................ E7000PC Emulator Station Rear Panel ......................................................................... E7000PC Emulator Pod ................................................................................................. E7000PC Emulator Software Components ................................................................... E7000PC Emulator System Configuration .................................................................... E7000PC Preparation Flow Chart ................................................................................. Connecting Station-Pod Interface Cables to Emulator Station ...................................... Connecting Station-Pod Interface Cables to Emulator Pod ........................................... Connecting External Probe ............................................................................................ Installing Crystal Oscillator............................................................................................ Connecting System Ground ........................................................................................... Connecting Frame Ground ............................................................................................ Memory Areas Allocatable for the IBM PC Interface Board ........................................ Switches on the IBM PC Interface Board ...................................................................... Installing IBM PC Interface Board ................................................................................ Connecting IBM PC Interface Board to E7000PC Emulator Station ............................ E7000PC System Disk ................................................................................................... Power-On Procedure for the E7000PC .......................................................................... Program Execution Flow ............................................................................................... 1-2 2-1 2-2 2-3 2-5 2-8 2-9 3-1 3-2 3-3 3-4 3-5 3-7 3-7 3-9 3-10 3-12 3-13 3-14 3-16 4-16 Part III Emulator Function Guide 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 1-11 1-12 1-13 1-14 1-15 1-16 1-17 Cycle Reset Mode .......................................................................................................... Trigger Signal Output Timing ....................................................................................... Transition to Parallel Mode ........................................................................................... Parallel Mode ................................................................................................................. Break with Address Bus Value ...................................................................................... Break with Data Bus Value ........................................................................................... Break with Read/Write .................................................................................................. Multibreak Function ...................................................................................................... Break with External Interrupt ........................................................................................ Break with NOT Condition ........................................................................................... Break with the Number of Times Break Condition is Satisfied .................................... Break with Delay Count Specification .......................................................................... Break with Sequential Specification .............................................................................. Break Timing ................................................................................................................. Normal Break (PC Break) ............................................................................................. Sequential Break ............................................................................................................ Sequential Break (with Reset Point Specification) ........................................................ 1-10 1-11 1-12 1-13 1-16 1-16 1-17 1-18 1-19 1-20 1-21 1-21 1-22 1-23 1-24 1-25 1-26 1-18 1-19 1-20 1-21 1-22 1-23 1-24 1-25 1-26 1-27 1-28 1-29 1-30 1-31 1-32 4-1 4-2 4-3 4-4 4-5 5-1 7-1 7-2 8-1 8-2 9-1 9-2 9-3 9-4 9-5 10-1 11-1 11-2 A-1 A-2 B-1 B-2 B-3 B-4 External Probe Trace Signal Example ........................................................................... Free Trace Execution ..................................................................................................... Subroutine Trace Specification ...................................................................................... Trace Acquisition Condition Specification ................................................................... Trace Stop Condition Specification ............................................................................... Subroutine Display ........................................................................................................ Normal Mode Time Measurement Range ..................................................................... Time Interval Measurement Mode 1 ............................................................................. Time Interval Measurement Mode 2 ............................................................................. Pulse Output Timing ...................................................................................................... Allowable Operating Range of Emulator ....................................................................... Boot-Mode Flowchart .................................................................................................... User Program Mode Flowchart ..................................................................................... Assembly Function ........................................................................................................ Label Name Definition .................................................................................................. Basic Bus Cycle Timing in Expanded Mode ................................................................. 1-Wait Inserted Bus Cycle Timing ................................................................................ DRAM Read/Write Cycle Timing (2WE Mode)............................................................ DRAM Refresh Cycle Timing (2WE Mode).................................................................. User Interface Circuit .................................................................................................... Troubleshooting PAD .................................................................................................... Emulation Command Description Format...................................................................... Display Range Specified by Instruction Pointers .......................................................... Record Format ............................................................................................................... Format of Floppy Disk Utility Command Description .................................................. Configuration and Data Transfer in Transparent Mode ................................................ Configuration and Data Transfer in Local Mode .......................................................... Configuration and Data Transfer in Remote Mode ....................................................... Format of Host-System Related Command Description ............................................... TERMINAL Command Processing ............................................................................... Format of LAN Command Description ......................................................................... Flow of Data Transfer .................................................................................................... Format of E7000PC-Related Data Transfer Command Description ............................. E7000 External Dimensions and Weight ....................................................................... E7000PC External Dimensions and Weight .................................................................. H8/3048 Memory Map After Reset................................................................................ H8/3047 Memory Map After Reset ............................................................................... H8/3044 Memory Map After Reset................................................................................ H8/3048F Memory Map After Reset ............................................................................. 1-29 1-30 1-31 1-32 1-33 1-34 1-36 1-36 1-37 1-39 1-45 1-46 1-47 1-51 1-55 4-2 4-2 4-3 4-4 4-5 5-9 7-3 7-131 8-3 8-4 9-2 9-3 9-5 9-8 9-19 10-5 11-1 11-3 A-1 A-1 B-2 B-4 B-6 B-8 Tables Part I E7000 Guide 1-1 1-2 1-3 1-4 2-1 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 A-1 B-1 B-2 B-3 B-4 B-5 Environmental Conditions ............................................................................................. E7000 Emulator Station Components ........................................................................... E7000 Emulator Pod Components ................................................................................. Optional Component Specifications .............................................................................. Contents of E7000 System Disk .................................................................................... Console Interface Specifications ................................................................................... Console Interface Switch Settings ................................................................................. Host System Interface Specifications ............................................................................ Ethernet and Cheapernet Specifications ........................................................................ Recommended Transceiver and Transceiver Cable ...................................................... Recommended BNC T-Type Connector and Thin-Wire Cable .................................... E7000 Monitor Commands ............................................................................................ E7000 System Program Initiation Commands .............................................................. 3.5-Inch Floppy Disk Drive Specifications ................................................................... Signal Names and Usage of Console Connector ........................................................... Signal Names and Usage of Host System Connector .................................................... Printer Cable Connector Pin Assignment ...................................................................... Pin Numbers and Signal Names in LAN Connector ..................................................... Pin Numbers and Signal Names in Printer and E7000 .................................................. 1-5 1-6 1-7 1-8 2-7 3-8 3-10 3-11 3-12 3-14 3-15 3-25 3-39 A-1 B-1 B-2 B-3 B-5 B-8 Part II E7000PC Guide 1-1 1-2 1-3 1-4 1-5 2-1 3-1 3-2 3-3 3-4 3-5 3-6 Environmental Conditions ............................................................................................. E7000PC Emulator Station Components ....................................................................... E7000PC Emulator Pod Components ............................................................................ IBM PC Interface Board................................................................................................. Optional Component Specifications .............................................................................. Contents of E7000PC System Disk ............................................................................... IBM PC Interface Board Specifications ........................................................................ Available Interrupts ....................................................................................................... Memory Allocation and Switch Settings ....................................................................... Interrupts and Switch Settings ....................................................................................... E7000PC Monitor Commands ....................................................................................... E7000PC System Program Initiation Commands........................................................... 1-5 1-6 1-7 1-7 1-8 2-7 3-8 3-10 3-11 3-11 3-18 3-19 Part III Emulator Function Guide 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 2-1 3-1 4-1 4-2 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22 7-23 7-24 7-25 7-26 Differences between the H8/3048 Series and H8/3048F Functions............................... Emulation Functions ...................................................................................................... Floppy Disk Utility Functions ....................................................................................... Host System Interface Functions ................................................................................... Execution Status Display ............................................................................................... Execution Status Display ............................................................................................... User System Power and Clock Status ............................................................................ List of Symbol Attributes .............................................................................................. Assembler Directives ..................................................................................................... Operand Description ...................................................................................................... Differences between the MCU and the Emulator .......................................................... H8/3048-Series, and H8/3048F MCU Operating Modes .............................................. Bus Timing (Reference Value at 5-V and 18-MHz Operation) .................................... Refresh Controller Bus Timing (Reference Value at 5-V and 18-MHz Operation) ...... Emulation Commands ................................................................................................... Display Formats of Symbol Contents ............................................................................ Subcommands for Line Assembly ................................................................................. Relationship between GO Command Option and BREAK_CONDITION1,2,3,4 Command ..................................................... Specifiable Conditions (BREAK_CONDITION1) ....................................................... Specifiable Conditions (BREAK_CONDITION2,3,4) ................................................. Mask Specifications (BREAK_CONDITION1,2,3,4) .................................................. MCU Pin Test ................................................................................................................ Cycle Reset Times ......................................................................................................... Restrictions for Realtime Emulation Modes .................................................................. Causes of GO Command Emulation Termination ......................................................... Execution Status Display ............................................................................................... MEMORY Command Options ...................................................................................... Operating Mode Selection Pin Status and Display ........................................................ Emulation Information Saved with the QUIT Command .............................................. Radix and Input Examples ............................................................................................. Causes of STEP Command Emulation Termination ..................................................... Causes of STEP_OVER Command Emulation Termination ........................................ Symbol Attributes and Related Display Start Columns ................................................ Symbol Attribute Display .............................................................................................. MA Display ................................................................................................................... R/W Display .................................................................................................................. ST Display ..................................................................................................................... VCC Voltage Display ..................................................................................................... Specifiable Conditions (TRACE_CONDITION) .......................................................... Mask Specifications (TRACE_CONDITION) .............................................................. 1-1 1-2 1-7 1-8 1-42 1-43 1-44 1-49 1-53 1-54 2-3 3-1 4-1 4-1 7-1 7-7 7-11 7-17 7-18 7-20 7-23 7-29 7-61 7-62 7-64 7-65 7-84 7-87 7-99 7-101 7-115 7-123 7-127 7-127 7-133 7-133 7-133 7-134 7-140 7-144 7-27 7-28 8-1 8-2 8-3 8-4 8-5 8-6 8-7 9-1 10-1 11-1 12-1 12-2 12-3 12-4 12-5 12-6 12-7 Specifiable Conditions (TRACE_SEARCH) ................................................................ Mask Specifications (TRACE_SEARCH) .................................................................... Floppy Disk Utility Commands ..................................................................................... Floppy Disk Format ....................................................................................................... File Name Specifications ............................................................................................... Wild Card Characters .................................................................................................... Target File Name Short Formats ................................................................................... FILE_DUMP Subcommands ......................................................................................... Rename Short Formats .................................................................................................. E7000 Commands for Host System ............................................................................... LAN Commands ............................................................................................................ E7000PC-Related Data Transfer Commands ................................................................ Emulator Error Messages .............................................................................................. Host I/O Error Codes ..................................................................................................... Floppy Disk I/O Error Codes ......................................................................................... Floppy Disk Error Messages ......................................................................................... LAN I/O Error Messages ............................................................................................... Process Code for LAN I/O Error Messages .................................................................. Interface Software Error Messages ................................................................................ 7-151 7-154 8-1 8-2 8-2 8-3 8-5 8-11 8-17 9-1 10-2 11-1 12-1 12-7 12-8 12-9 12-9 12-11 12-12 Part I E7000 Guide Section 1 Overview This system is an efficient software and hardware development support tool for application systems using the H8/3048 series or H8/3048F microcomputer (abbreviated to MCU) developed by Hitachi, Ltd. The H8/3048 series includes three types of MCUs: H8/3048, H8/3047, and H8/3044. They contain the following components on a single chip: * * * * * * * * * High-speed CPU Internal RAM Internal ROM Timers Serial communication interface (including one channel for smart card interface) Refresh controller DMAC I/O ports A/D and D/A converters The H8/3048F has the same functions as the H8/3048 except that it has flash memory instead of internal ROM. When the E7000 is connected to a user system, it operates in place of the MCU and performs realtime emulation of the user system. Additionally, the E7000 provides functions for efficient software and hardware debugging. The E7000 consists of an emulator station, emulator pod, and user system interface cable, as shown in figure 1-1. The emulator pod should be connected to the user system via the user system interface cable. 1-1 E7000 Station-pod interface cables User system interface cable Emulator pod HITACHI Emulator station Figure 1-1 H8/3048-Series, H8/3048F E7000 Emulator 1-2 The E7000 provides the following features: * Realtime emulation of MCU * A wide selection of emulation commands, promoting efficient system development * Help functions to facilitate command usage without a manual * Efficient debugging enabled by variable break functions and mass-storage trace memory (32 kcycles) * Command execution during emulation, for example: -- Trace data display -- Emulation memory display and modification * Measurement of subroutine execution time and frequency for evaluating the execution efficiency of user programs * An optional LAN board for interfacing with workstations, enabling high-speed downloading (1 Mbyte/min) of user programs The LAN board contains Ethernet* (10BASE5) and Cheapernet (10BASE2) interfaces. Ethernet is a registered trademark of the Xerox Corporation in the United States. Note: Ethernet is a registered trademark of Xerox Corporation. * E7000 graphical user interface software (E7000 GUI: option) can be loaded into the workstation to enable: -- Graphic display operations in a multi-window environment -- Source level debugging -- Graphic display of trace information * Operation as a stand-alone system when connected to a console * An RS-232C host system interface * A Centronics printer interface * A 3.5-inch floppy disk drive, which facilitates: -- Loading, saving, and verifying user programs -- Saving emulation results -- Input and execution of commands using a floppy disk for external storage 1-3 * 512 kbytes of emulation memory as substitute user system memory. An optional 1-Mbyte or 4-Mbyte emulation memory board can also be installed in the emulator station. * By connecting the user system interface and providing a low-voltage power supply of 2.7 to 5.5 V, emulation can be performed in user systems with any supply voltage in the range 2.7 to 5.5 V. 1.1 Warnings Before using the E7000, carefully read the following warnings. If the E7000 is not used correctly, breakdowns may occur. Before System Initiation: 1. Check all components with the component list after unpacking the E7000. 2. Never place heavy objects on the casing. 3. Observe the following conditions in the area where the E7000 is to be used: * Make sure that the internal cooling fans on the sides of the emulator station are at least 20 cm (8") away from walls or other equipment. * Keep out of direct sunlight or heat. Refer to section 1.2, Environmental Conditions. * Use in an environment with constant temperature and humidity. * Protect the E7000 from dust. * Avoid subjecting the E7000 to excessive vibration. Refer to section 1.2, Environmental Conditions. 4. Protect the E7000 from excessive impacts and stresses. 5. Before using the E7000's power supply, check its specifications such as power output, voltage, and frequency. For details on power supply, refer to section 1.2, Environmental Conditions. 6. When moving the E7000, take care not to vibrate or otherwise damage it. Pay special attention to exposed parts such as the power switch and I/O connectors. 7. After connecting the cable, check that it is connected correctly. For details, refer to section 3, Preparation before Use. 8. Supply power to the E7000 and connected parts after connecting all cables. Cables should not be connected or removed when the power is on. 9. For details on differences between the MCU and the E7000, refer to section 2, Differences between the MCU and the Emulator in Part III, Emulator Function Guide. 1-4 Floppy Disk: If the floppy disk is removed when a file is being accessed, the file may be damaged and processing may fail. 1.2 Environmental Conditions Observe the conditions listed in table 1-1 when using the E7000. Table 1-1 Environmental Conditions Item Specifications Temperature Operating: +10 to +35C Storage: -10 to +50C Humidity Operating: 35 to 80% RH (no condensation) Storage: 35 to 80% RH (no condensation) Vibration Operating: 2.45 m/s2 max Storage: 4.9 m/s2 max Transportation: 14.7 m/s2 max AC input power Voltage: 100/200 VAC 10% Frequency: 50/60 Hz Power consumption: 200 VA Ambient gases Must be no corrosive gases 1-5 1.3 Components The E7000 consists of the emulator station and emulator pod. Check all the components after unpacking. 1.3.1 E7000 Emulator Station Table 1-2 E7000 Emulator Station Components Item Configuration Quantity Remarks Hardware Emulator station 1 Power supply, 3.5-inch floppy disk drive, control board, and trace board Station-pod interface cables 2 50 cm Console interface cable 1 3m RS-232C AC power cable 1 E7000 HITACHI Fuse 1 Spare 1 HS7000EST01HE (3 A) Documentation HS7000EST01H Description Notes 1-6 1.3.2 E7000 Emulator Pod Table 1-3 E7000 Emulator Pod Components Item Configuration Quantity Remarks Hardware Emulator pod 1 Fitted with two boards External probe set 1 Signal input: 8 GND: 1 Trigger output: 1 Floppy disks 1 E7000 system program 1 E7000PC system program (cannot be used with the E7000) 1 HS3048EPD70HE Software E7000 E7000PC Documentation H8/3048-series, H8/3048F E7000 Emulator User's Manual 1-7 1.3.3 Options In addition to the emulator station and pod components, the options listed in table 1-4 are also available. Refer to each option manual for details on these optional components. Table 1-4 Optional Component Specifications Item Model Name Specifications LAN board HS7000ELN01H * TCP/IP communications protocol * Ethernet (10BASE5) * Cheapernet (10BASE2) 1-Mbyte emulation memory board HS7000EMS11H 1-Mbyte SRAM is used 4-Mbyte emulation memory board HS7000EMS12H 4-Mbyte SRAM is used QFP-100 user system interface cable HS3042ECH71H For H8/3002, H8/3042 series, H8/3048 series, and H8/3048F (FP-100B) Host system interface cable HS7000EHT71H RS-232C interface Printer cable HS7000EPR71H Centronics interface Bus monitor interface board for E7000 HS7000EXR10H For connecting the E7000 bus monitor board E7000 bus monitor board HS7000EBR01H For installing the D/A converter 1-8 Section 2 Components 2.1 E7000 Hardware Components As shown in figure 2-1, the E7000 consists of an emulator station (including two RS-232C interface cables and a printer cable), an emulator pod, and a user system interface cable. By installing a LAN board (option), the emulator station can be connected to a workstation. To provide additional memory, optional 1-Mbyte and 4-Mbyte SRAM boards are available. The E7000 contains another slot into which you can insert either one of these boards or a bus monitor interface board. Optional 1-Mbyte or 4-Mbyte emulation memory board, or bus monitor interface board LAN board (optional) Centronics printer cable (optional) RS-232C host system interface cable (optional) E7000 RS-232C console interface cable 3.5-inch floppy disk drive Station-pod interface cables HITACHI Emulator pod E7000 emulator station User system interface cable (optioanl) External probe User system Figure 2-1 E7000 Emulator Hardware Components 2-1 2.1.1 Emulator Station Components Front Panel: E7000 2 3 POWER 1 HITACHI Figure 2-2 E7000 Emulator Station Front Panel 1. Power lamp: Lights when the E7000 power is on. 2. 3.5-inch floppy disk drive: For loading the E7000 system program, as well as loading, saving, and verifying the contents of the user system memory. 3. Station-pod interface cable connectors: For connecting the emulator pod to the emulator station. 2-2 Rear Panel: S W I LAN 4 P R I N T E R POWER 8 CRT 5 1 BNC 9 250V 3A 6 2 AC INPUT 3 7 TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz 13 12 11 10 Figure 2-3 E7000 Emulator Station Rear Panel 1. Power switch: Turning this switch to I (input) supplies power to the E7000 (emulator station and pod). 2. Fuse box: Contains a 3-A 250 VAC fuse. 3. AC power connector: For an 100/200 VAC power supply. 4. Console interface switch: For changing the transfer speed, data bit length, stop-bit length, parity specifications, and LAN interface settings when interfacing with a console. Marked SW1. 5. Printer connector: For a printer conforming to Centronics specifications. Marked PRINTER. 2-3 6. Console connector: For an RS-232C console. Marked CRT. 7. Host system connector: For RS-232C communication with a host system. Marked HOST. 8. Ethernet connector: 9. Cheapernet connector: For a Cheapernet cable. Marked BNC. For an Ethernet cable. Marked LAN. 10. Control board slot: For installing the control board. 11. LAN board slot: For installing the optional LAN board. 12. Emulation memory/bus monitor interface board slot: For installing the optional emulation memory board or bus monitor interface board. 13. Trace board slot: For installing the trace board. 2-4 2.1.2 Emulator Pod Components 2 1 s H S 3 0 4 8 E P D 7 0 H 4 5 (Top view) 3 7 6 (Bottom view) Figure 2-4 E7000 Emulator Pod 1. External probes: Can be used for the following during user system emulation -- Hardware break condition input -- Realtime trace input -- Multibreak detection 2. Trigger output pin: Outputs a low-level pulse in the following states: -- When a hardware break condition is satisfied (whether to break or not can be selected) -- When cycle reset mode is specified with the GO command and an RES signal is input to the MCU 2-5 -- When trigger output is specified with the TRACE_CONDITION command, and the set conditions are satisfied, this pin can be used as the trigger signal of the oscilloscope or the logic analyzer 3. Crystal oscillator installation socket: For installing the crystal oscillator which provides a clock to the MCU. 4. User system interface cable: For connection to the MCU socket on the user system, to enable the E7000 to operate in place of the MCU. 5. Station-pod interface cables: For connecting the emulator station to the emulator pod. 6. User system interface cable connector: For connection of the user system. 7. External probe connector: For connection of the external probe. Note: When a user system interface cable is connected, power supply voltage must be provided from the VCC pin on the user system interface cable to operate the E7000. Therefore, when using the E7000 on its own, be sure to disconnect the user system interface cable. 2-6 2.2 E7000 Software Components The E7000's software components are illustrated in figure 2-5. The emulator pod contains two 3.5inch floppy disks: the E7000 emulator system disk has "E7000" written under "HITACHI" on its label. The system disk files are described in table 2-1. To display the file names, use the FILE_DIRECTORY command. Take care not to erase the following files with the FILE_ERASE command. Table 2-1 Contents of E7000 System Disk File Name Contents Description E7000.SYS E7000 system program Controls the emulator pod and processes commands, such as emulation commands. Loaded into the E7000 memory after the E7000 system program is activated. H8POD348.SYS MCU control program Controls the MCU within the emulator pod. Loaded into the E7000 memory after the E7000 system program is activated. H8CNF348.SYS Configuration file Contains MCU operating mode and MAP information. Loaded with the E7000 system program. LANCNF.SYS LAN configuration file Stores the host system name and IP address information when the E7000 is connected to a workstation by a LAN interface. DIAG.TM Diagnostic program Loaded into the emulator station memory for testing and maintenance. 2-7 E7000 E7000 system program (Provided with the emulator pod) Loadable file types: * S-type files * HEX-type files * SYSROF-type files * Text files HITACHI E7000 graphical user system interface software H-series interface software C compiler Cross assembler Linkage editor Personal computer Workstation (SPARCstation)* 1 Notes: 1. 2. C compiler Cross assembler Linkage editor PC-9801/VM (NEC)* 2 SPARC is a registered trademark of SPARC International, INC. (United States). SPARCstation is a registered trademark of SPARC International, INC. (United States) and has permission of monopolistic use granted by Sun Microsystems Corporation (United States). PC-9801/VM is a registered trademark of NEC Corporation. Figure 2-5 E7000 Emulator Software Components 2-8 2.3 System Configuration The E7000 can be connected with the host system via a LAN or an RS-232C interface. 2.3.1 System Configuration Using LAN Interface By installing an optional LAN board in the emulator station, the E7000 can be connected to a workstation through a LAN interface. The LAN interface employs the TCP/IP protocol and the LAN board contains connectors for both Cheapernet (10BASE2) and Ethernet (10BASE5). The system configuration using a LAN interface is shown in figure 2-6. Cheapernet Interface Ethernet Interface E7000 emulator E7000 emulator BNC BNC LAN LAN Workstation Workstation Figure 2-6 System Configuration Using LAN Interface Cheapernet Interface: This is achieved by connecting a coaxial cable (referred to as the Cheapernet thin-wire cable) between the BNC connector in the LAN board and the workstation. Ethernet Interface: This is achieved by connecting transceivers and transceiver cables between the D-SUB connector in the LAN board and the workstation. 2-9 2.3.2 System Configuration Using RS-232C Interface Using an RS-232C interface, the E7000 system can be configured in any of the ways shown in figure 2-7. Stand-Alone Mode Transparent Mode Console Console E7000 E7000 CRT CRT HOST HOST PRINTER PRINTER Host system Printer Printer Local Mode Remote Mode Personal computer Console E7000 Interface software E7000 CRT CRT HOST HOST PRINTER Personal computer, EPROM programmer, etc. PRINTER Printer Printer Figure 2-7 System Configuration Using RS-232C Interface 2-10 Stand-Alone Mode: Configuration in which the E7000 is connected to the console and operates alone. Transparent Mode: Configuration in which the console connected to the E7000 can also serve as a console for the host system. The console allocation is switched using the TERMINAL command. Local Mode: Configuration which allows data transfer between the E7000 and a personal computer. In this mode, data can be sent using the standard commands of the personal computer. This configuration can also be used to connect to an EPROM programmer. Remote Mode: Configuration in which a personal computer can be used as the console or the host machine for data transfer. Interface software must be loaded in the personal computer. 2-11 Section 3 Preparation before Use 3.1 E7000 Preparation Unpack the E7000 and prepare it for use as follows: Reference Unpack the E7000 Check the components against the component list Component list Install the optional LAN board, Each board's user's manual emulation memory board, or bus monitor interface board Connect the emulator pod to the emulator station Section 3.2.1 Connect the external probe Section 3.2.2 Connect the user system interface cable Each user system interface cable manual Install the crystal oscillator Section 3.2.3 Connect the system ground Section 3.2.4 LAN interface Transparent or local mode Stand-alone or remote mode Connect the console interface cable Section 3.3.1 Connect the console interface cable Section 3.3.1 Connect the console interface cable Section 3.3.1 Set the console interface switches Section 3.3.2 Set the console interface switches Section 3.3.2 Set the console interface switches Section 3.3.2 Connect with the LAN interface Section 3.3.5 Connect the host Section system interface cable 3.3.3 Connect the printer cable Section 3.3.4 Connect the printer cable Section 3.3.4 Power-on Section 3.4 Figure 3-1 E7000 Preparation Flow Chart 3-1 3.2 E7000 Connection 3.2.1 Connecting Emulator Pod The emulator pod and the emulator station are packed separately. Use the following procedure to connect the emulator pod to the emulator station, or to disconnect it when moving the E7000: (1) Check that the E7000 power is off by ensuring that the power lamp on the left side of the emulator station front panel is extinguished. (2) Remove the AC power cable for the emulator station from the outlet. (3) Connect station-pod interface cables P1 and P2 to station-pod interface connectors J1 and J2 on the right side of the emulator station, respectively. Insert the longer screw of each cable to the connector screw hole without a spacer, and the shorter screw to the hole with a spacer. Tighten the longer screw first until the shorter screw reaches the spacer, then alternately tighten the longer and shorter screws. Figure 3-2 shows how to connect the station-pod interface cables to the emulator station. Note: When connecting the cables, prevent the upper or lower side of the cables from lifting off the connector. Tighten the screws and push the cables gradually toward the connector. Station-pod interface connector J2 J2 Spacers J1 Station-pod interface connector J1 Emulator station right side Longer screws Station-pod interface cable P1 Station-pod interface cable P2 Figure 3-2 Connecting Station-Pod Interface Cables to Emulator Station 3-2 (4) Connect station-pod interface cables P1 and P2 to station-pod interface connectors J1 and J2, respectively, in the same way as connection to the emulator station. Tighten the screws in the same way as in step (3). See figure 3-3 for details. Pod Station-pod interface connector J1 J1 Station-pod interface connector J2 J2 Spacers Station-pod interface cable P1 Station-pod interface cable P2 Longer screws Figure 3-3 Connecting Station-Pod Interface Cables to Emulator Pod 3-3 3.2.2 External Probe Connector When an external probe is connected to the emulator pod, it enables external signal trace, break using an external signal, and multibreak detection. Figure 3-4 shows the external probe connection. External probe connector Cover External probe Bottom of emulator pod Figure 3-4 Connecting External Probe 1. Slide back the cover on the bottom of the emulator pod. 2. Insert the external probe into the external probe connector, making sure they are aligned correctly. For connecting a user system interface cable, refer to the user system interface cable manual. 3-4 3.2.3 Clock Selection Three types of clocks are supported; a crystal oscillator signal from the emulator pod, an external clock from the user system, and the E7000 emulator internal clock. Each clock type is specified with the CLOCK command. X (crystal oscillator) U (user system clock) E7000 emulator internal clock CLOCK command 13 (13 MHz) 18 (18 MHz) Crystal Oscillator: Using this function, a user program can be executed with user system operating frequency without connecting the user system. A crystal oscillator is not provided with the E7000. Use one with the same frequency as the user system (o clock). The frequency of the crystal oscillator used as the MCU input clock is 8 to 18 MHz. To use a frequency outside this range, supply an external clock from the user system. Install the crystal oscillator using the following procedure: 1. Check that the E7000 power is turned off. 2. Install the crystal oscillator into the crystal oscillator socket on the side of the emulator pod (figure 3-5). 3. After turning on the E7000, specify X with the CLOCK command. Cover XTAL Bottom of emulator pod Figure 3-5 Installing Crystal Oscillator 3-5 User System Clock: Specify a user system clock using the following procedure. 1. Check that the E7000 power is off. 2. Supply a TTL-level clock through the EXTAL pin at the end of the user system interface cable. 3. After turning on the E7000 power, specify U with the CLOCK command. E7000 Emulator Internal Clock: Specify 13 (13 MHz) or 18 (18 MHz) with the CLOCK command. Note: When the emulator system program is initiated, the emulator automatically selects the MCU clock source according to the following priority. 1. U (user system clock) when supplied from the user system. 2. X (crystal oscillator) when installed in the emulator pod. 3. 13-MHz E7000 emulator internal clock. 3-6 3.2.4 Connecting System Ground The E7000's signal ground is connected to the user system's signal ground via the emulator pod. In the emulator station, the signal ground and frame ground are connected (figure 3-6). At the user system, connect the frame ground only; do not connect the signal ground to the frame ground. If it is difficult to separate the signal ground from the 100-V frame ground, ground the user system at the same outlet as the E7000's power supply (figure 3-7). Signal line Emulator station Emulator pod Signal line User system Logic Power Signal ground Signal ground Frame ground Figure 3-6 Connecting System Ground E7000 power cable User system power cable Outlet Ground AC power supply Figure 3-7 Connecting Frame Ground The user system must be connected to an appropriate ground so as to minimize noise, ground loops, and other adverse effects. Confirm that the ground pins of the user system interface cable are firmly connected to the user system's ground. 3-7 3.3 System Connection This section describes how to connect the E7000 to a workstation, personal computer, console, and printer. Connectors for each of these are located on the emulator station as shown in figure 2-3. 3.3.1 Connecting to a Console The console connector (marked CRT) located on the emulator station rear panel conforms to the RS-232C specifications (table 3-1). A console can be connected to this by the console interface cable supplied with the E7000, making it possible to input commands and check their results on the console. This connection is also used to specify the IP address before connecting a workstation via the LAN interface. Table 3-1 Console Interface Specifications Item Specification Signal level RS-232C High: +5 to +15 V Low: -5 to -15 V Transfer rate 2400/4800/9600/19200 bps Synchronization method Asynchronous method Start bits 1 bit Data bits 7/8 bits Stop bits 1/2 bits Parity Even/odd or none Control method X-ON/X-OFF control (Refer to 9.3.1, Control Methods, in Part III, Emulator Function Guide.) bps: Bits per second For the console connector pin assignment and signal names, refer to section B.1, Console Connector. For console interface cable connection, refer to section B.5, Console Interface Cable Connection. 3-8 3.3.2 Setting up Console Interface The transfer rate, number of data bits, number of stop bits, and parity can be changed using the console interface switches (SW1) on the emulator station rear panel. One of these switches selects either the console interface or LAN interface. Eight console interface switches (S1 to S8) are arranged as shown in figure 3-8. When a switch is pushed to the right, it turns on, and when it is pushed to the left, it turns off. 1 S1 2 S2 3 S3 4 S4 5 S5 6 S6 7 S7 8 S8 (a) On (b) Off SW1 Figure 3-8 Console Interface Switches The console interface settings are changed by turning these switches on or off as shown in table 3-2. 3-9 Table 3-2 Console Interface Switch Settings Transfer rate Transfer Rate S1 S2 S3 19200 bps On On Off 9600 bps Off On Off* 4800 bps On Off Off 2400 bps Off Off Off Number of stop bits Stop Bits S4 1 bit Off* 2 bits On Number of data bits Data Bits S5 7 bits Off 8 bits On* Parity Parity S6 None Off* Even/odd On Even/odd parity (only valid if parity switch is on) Parity S7 Even Off* Odd On Console/LAN interface selection Interface S8 Console Off* LAN On Note: * indicates setting at shipment. 3-10 3.3.3 Connecting to a Host System This section describes how to set the host system interface when the E7000 is connected to a host system such as a personal computer or EPROM programmer. The host system connector (marked HOST) located on the emulator station rear panel conforms to the RS-232C specifications (table 3-3). Connecting a host system to this connector enables data transfer between the E7000 and the host system. Table 3-3 Host System Interface Specifications Item Specifications Signal level RS-232C High: +5 to +15 V Low: -5 to -15 V Transfer rate 2400/4800/9600/19200/38400 bps Synchronization method Asynchronous method Start bits 1 bit Data bits 7/8 bits Stop bits 1/2 bits Parity Even/odd or none Control method X-ON/X-OFF control, RTS/CTS control bps: Bits per second Host System Interface Settings at E7000 Start-Up: When the E7000 is turned on, or when the E7000 system program is initiated, the host system interface settings are determined by the console interface switches in the same way as the console interface (control method will be X-ON/X-OFF control). For details, refer to section 9.3.1, Control Methods, in Part III, Emulator Function Guide. Changing Host System Interface Settings: The transfer rate, number of data bits, number of stop bits, parity, and control method can be changed with the HOST command. For details, refer to section 9.4.1, HOST, in Part III, Emulator Function Guide. For the host system connector pin assignments and signal names, refer to section B.2, Host System Connector. For connection of optional host system interface cable, refer to section B.6, Host System Interface Cable Connection. 3-11 3.3.4 Connecting to a Printer The printer connector (marked PRINTER) is located on the emulator station rear panel. Connecting a printer to this connector enables the command execution results to be printed. The printer interface conforms to the Centronics specifications. For the printer connector pin assignments and signal names, refer to section B.3, Printer Connector. For connection of the optional printer cable, refer to section B.7, Printer Cable Connection. 3.3.5 Connecting to a LAN Interface The LAN board for the E7000 supports Ethernet (10BASE5) and Cheapernet (10BASE2) interfaces conforming to Ethernet specifications V.2.0. The LAN board communicates with a workstation according to the TCP/IP protocol, and the workstation transfers files and commands according to the FTP/TELNET protocol. The LAN board specifications at each layer of the OSI model are as follows. Physical and Data Link Layers: The LAN board communicates with Ethernet and Cheapernet. Table 3-4 shows the Ethernet and Cheapernet specifications. Table 3-4 Ethernet and Cheapernet Specifications Item Ethernet Cheapernet Transfer rate 10 Mbits/second 10 Mbits/second Maximum distance between segments 500 m 185 m Maximum network length 2500 m 925 m Maximum nodes in one segment 100 30 Minimum distance between nodes 2.5 m 0.5 m Network cable Diameter: 0.4 inch (1.02 cm) 50- shielded coaxial cable Diameter: 0.25 inch (0.64 cm) 50- coaxial cable (RG-58A/U) Network connector N-type connector BNC connector Transceiver cable Diameter: 0.38 inch (0.97 cm) Ethernet cable to be connected to 15-pin D-SUB connector 3-12 Network Layer: * IP (Internet Protocol) -- Transmits and receives data in datagram format. -- Does not support IP options. -- Does not have subnet mask functions. -- Does not support broadcast communications. * ICMP (Internet Control Message Protocol) Supports only echo reply functions. * ARP (Address Resolution Protocol) Calculates Ethernet addresses from IP addresses by using broadcast communications. Transport Layer: * TCP (Transmission Control Protocol) Logically connects the E7000 to the workstation. * UDP (User Diagram Protocol) Not supported. Session, Presentation, and Application Layers: * FTP (File Transfer Protocol) The E7000 operates as a client. * TELNET (Teletype Network) The E7000 operates as a server. Note: The E7000 does not communicate through routers or gateways. 3-13 3.3.6 System Connection Examples Some examples of system configuration are shown below. Ethernet Interface: The LAN board has a 15-pin D-SUB connector for the Ethernet transceiver cable. Figure 3-9 shows an example of Ethernet system configuration. Use commercially available Ethernet transceivers and transceiver cables. Table 3-5 shows a recommended transceiver and transceiver cable. Ethernet transceivers LAN board Ethernet S W I LAN P R I N T E R POWER CRT 250V 3A BNC Ethernet transceiver cable AC INPUT TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz Workstation Emulator station rear panel Figure 3-9 Ethernet Interface Table 3-5 Recommended Transceiver and Transceiver Cable Item Product Type Manufacturer Transceiver HBN-200 series Hitachi Cable, Ltd. Transceiver cable HBN-TC-100 Hitachi Cable, Ltd. For setting up Ethernet, refer to the LAN board user's manual. 3-14 Cheapernet Interface: The LAN board of the E7000 has a transceiver and a BNC connector for Cheapernet interface. Figure 3-10 shows an example of Cheapernet system configuration. Use a commercially available Cheapernet BNC T-type connector with a characteristic impedance of 50 and an RG-58A/U thin-wire cable or its equivalent. Table 3-6 shows a recommended BNC T-type connector and thin-wire cable. LAN board Cheapernet thin-wire cable Cheapernet BNC T-type connentor S W I LAN P R I N T E R POWER CRT 250V 3A BNC AC INPUT TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz Workstation Emulator station rear panel Figure 3-10 Cheapernet Interface Table 3-6 Recommended BNC T-Type Connector and Thin-Wire Cable Item Product Type Manufacturer BNC T-type connector HBN-TA-JPJ Hitachi Cable, Ltd. Thin-wire cable HBN-3D2V-LAN Hitachi Cable, Ltd. For setting up Cheapernet, refer to the LAN board user's manual. 3-15 Stand-Alone Mode: A console is connected to the E7000 as shown in figure 3-11. Console P R I N T E R LAN Console connector POWER CRT 250V 3A BNC AC INPUT Console interface cable (supplied) TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz Emulator station rear panel Figure 3-11 Connection in Stand-Alone Mode Transparent Mode: A console and host system are connected to the E7000 as shown in figure 3-12. Console LAN P R I N T E R Console connector POWER CRT 250V 3A BNC Host system connector AC INPUT Console interface cable (supplied) TRACE Host system AC100-120V/ AC200-240V HOST 2A 50/60Hz Emulator station rear panel Host system interface cable (option) Figure 3-12 Connection in Transparent Mode 3-16 Local Mode: A console and host system are connected to the E7000 as shown in figure 3-13. Console LAN P R I N T E R Console connector POWER CRT 250V 3A BNC Host system connector AC INPUT Console interface cable (supplied) TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz Emulator station rear panel Host system interface cable (option) Host system (Personal computer, EPROM programmer) Figure 3-13 Connection in Local Mode 3-17 Remote Mode: A host system is connected to the E7000 as shown in figure 3-14. The control method in remote mode is X-ON/X-OFF. Interface software S W I Host system (Personal computer) LAN P R I N T E R Console connector POWER CRT 250V 3A BNC AC INPUT Console interface cable (supplied) AC100-120V/ AC200-240V TRACE HOST 2A 50/60Hz Emulator station rear panel Figure 3-14 Connection in Remote Mode Printer: A printer is connected to the E7000 as shown in figure 3-15. Printer connector S W I LAN Printer P R I N T E R POWER CRT 250V 3A Printer cable (option) BNC AC INPUT TRACE AC100-120V/ AC200-240V HOST 2A 50/60Hz Emulator station rear panel Figure 3-15 Printer Connection 3-18 3.4 Power-On Procedure for the E7000 The E7000 power-on procedure differs in each system configuration. Power on the E7000 in the appropriate way for the system configuration, as shown below. 3.4.1 Power-On Procedure for LAN Interface Figure 3-16 shows the power-on procedure when the LAN interface is used. (1) Check that no floppy disk is inserted. (2) Turn off (to the left) S8 in SW1 on the emulator station rear panel. (3) Power on the console connected to the E7000. (4) Power on the emulator station. Internal system test is executed. (5) Console messages are displayed. Test result OK? No Yes (6) E7000 monitor command input wait state (6) Error message is displayed. (7) Specify L to set the IP address of the emulator station. (8) Insert the system floppy disk into the floppy disk drive of the emulator station. See section 5, Troubleshooting in Part III, Emulator Function Guide. (9) Select S or R. When the E7000 enters command wait state and displays a colon (:), enter the LAN_HOST command. (10) Specify host names and IP addresses. (11) After storing the host names and IP addresses to the LANCNF.SYS file, terminate the system software execution. (12) Turn off the emulator station. Host system connection mode? Only workstation used Console also connected (13) Turn on (to the right) S8 in SW1 on the emulator station rear panel. (13) Turn off (to the left) S8 in SW1 on the emulator rear panel. (14) Power on the emulator station. Figure 3-16 Power-On Procedure for LAN Interface 3-19 The following describes the power-on procedure shown in figure 3-16. Steps (1) to (7): The optional LAN board supports the TCP/IP protocol. When the host system is connected to the E7000 with the LAN interface, the IP address (internet address) of the E7000 must be specified. To specify the address, turn off console interface switch S8 in switch set SW1 on the emulator station rear panel, and connect the E7000 to a console with the console interface cable supplied with the E7000. Check that no floppy disk is in the floppy disk drive. Turn on the power at the emulator station rear panel. The console displays the following messages and the E7000 waits for command input. E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. TESTING RAM 0123 ** E7000 SYSTEM LOADING ** *** FD NOT READY START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ After the above messages are displayed, press L and then the (RET) key. The E7000 prompts IP address input. The 32-bit IP address, which is generally expressed in hexadecimal, is displayed in four bytes in decimal. For example, when the IP address has been specified as H'80000001 (H' represents hexadecimal), the E7000 will display the address as follows: : IP ADDRESS = 128.0.0.1 _ Enter the IP address. For example, to specify H'80000002, enter as follows: : IP ADDRESS = 128.0.0.1 128.0.0.2 (RET) After entering the IP address, press the (RET) key. The console will display a message, which shows that IP address specification has been completed. 3-20 The host system name and IP address of the E7000 must be specified in the network database for the host system. When the host system uses UNIX*, the host name and IP address should generally be specified in the /etc/hosts file. For details, refer to the host system user's manual. Note: UNIX is a registered trademark of UNIX System Laboratories, Inc. Steps (8) to (12): To transfer data between the host system and the E7000, initiate the FTP server to connect the host system to the E7000. Before the FTP server is initiated, the host name and the IP address of the host system must be stored in the LANCNF.SYS file in the E7000 system disk. The following describes how to specify the host name and IP address. Insert the E7000 system disk into the floppy disk drive of the emulator station and enter S or R to initiate the system program while messages are displayed on the console. The system disk must be write-enabled. When the E7000 prompts for input with a colon (:), enter the LAN_HOST command. : LAN_HOST; S (RET) When the LAN_HOST command is entered, the following message is displayed on the console. NO <HOST NAME> 01 xxxxxx 03 xxxxxx 05 xxxxxx 07 xxxxxx 09 xxxxxx PLEASE SELECT NO ? _ <IP ADDRESS> xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx NO 02 04 06 08 <HOST NAME> xxxxxx xxxxxx xxxxxx xxxxxx <IP ADDRESS> xxxxxx xxxxxx xxxxxx xxxxxx Up to nine pairs of host names and IP addresses can be specified. Input a number from 1 to 9. PLEASE SELECT NO ? 1 (RET) The E7000 prompts for the host name. Enter a name with six characters. 01 HOST NAME xxxxxx <name of host system> (RET) After that, the E7000 prompts for the IP address. Enter the IP address in decimal. 01 IP ADDRESS xxxxxx <IP address of host system> (RET) 3-21 After the IP address has been specified, the E7000 will prompt for another selection number. When connecting more than one host system, continue specifying the host names and IP addresses. To terminate input, enter as follows: PLEASE SELECT NO ? . (RET) After (RET) is entered, the E7000 enters overwrite confirmation wait state. To store the host names and IP addresses, enter as follows: OVER WRITE(Y/N) ? Y (RET) The specified host names and IP addresses are stored in the LANCNF.SYS file in the E7000 system disk. Once they have been stored, remove the system disk from the floppy disk drive, set write protection to the disk, and then turn off the E7000. Steps (13) and (14): The host system can be connected to the E7000 in the following two modes. * Only workstation is used The TELNET server is used. -- Turn on (to the right) SW1-S8 on the emulator station rear panel. -- Power on the E7000. -- Execute the TELNET command on the workstation. Note: After initiating the E7000, enter as follows to cancel local echo on the workstation: (CTRL) +] telnet>mode character (RET) Some workstations sometimes do not accept (CTRL) + S or (CTRL) + Q key input. In this case, when the TELNET supports a toggle localflow function, specify it. * Console connected in addition to workstation The console is connected to the RS-232C connector on the emulator station. -- Turn off (to the left) SW1-S8 on the emulator station rear panel. -- Power on the console. -- Power on the E7000. After the system program is initiated, the FTP server can be initiated from the console. For operations after power-on, refer to section 3.5.1, E7000 Monitor Initiation, section 3.6, Floppy Disk Backup, and section 3.7, E7000 System Program Initiation. 3-22 3.4.2 Power-On Procedure for RS-232C Interface Figure 3-17 shows the power-on procedure when the RS-232C interface is used. Stand-alone, transparent, or local mode Remote mode (1) Check that no floppy disk is inserted. (1) Check that no floppy disk is inserted. (2) Turn off (to the left) S8 in SW1 on the emulator station rear panel. (2) Turn off (to the left) S8 in SW1 on the emulator station rear panel. (3) Initiate the interface software on the host system. (3) Power on the console connected to the E7000. Refer to the interface software manual. (4) Power on the emulator station. Internal system test is executed. (5) Console messages are displayed. Test result OK? No Yes (6) E7000 monitor command input wait state (6) Error message is displayed. See section 5, Troubleshooting in Part III, Emulator Function Guide. Figure 3-17 Power-On Procedure for RS-232C Interface For operations after power-on, refer to section 3.5.1, E7000 Monitor Initiation, section 3.6, Floppy Disk Backup, and section 3.7, E7000 System Program Initiation. 3-23 3.5 E7000 Monitor Commands 3.5.1 E7000 Monitor Initiation The E7000 supports the six monitor commands listed in table 3-7. These commands load the E7000 system program or diagnostic program, format or back up floppy disks, and set an IP address. When the E7000 is turned on, it displays the following message and waits for the monitor command input. Enter a command to be executed (table 3-7). If the system disk is inserted when the E7000 is turned on, the E7000 automatically loads the system program without entering the command input wait state. When the E7000 is turned on without the system floppy disk, the following messages are displayed. Console Messages: E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. (a) Licensed Material of Hitachi, Ltd. TESTING RAM 0123 ** E7000 SYSTEM LOADING *** FD NOT READY (b) ** (c) START E7000 S:START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ (d) Descriptions: (a) E7000 monitor start message. Vn.m is the E7000 monitor's version number. If this message is not displayed, determine what is wrong by reading section 5, Troubleshooting, in Part III, Emulator Function Guide. (b) The E7000 internal system is being tested. A number from 0 to 3 is displayed when each of the four MCU internal RAM blocks has been tested. If an error occurs, the following messages are displayed: *** RAM ERROR ADDR = xxxxxxxx W-DATA = xxxxxxxx R-DATA = xxxxxxxx *** xxxxx REGISTER ERROR W-DATA = xxxx R-DATA = xxxx 3-24 If these messages are displayed, refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. (c) E7000 system program load message. Because the system floppy disk is not inserted, *** FD NOT READY is displayed. (d) List of E7000 monitor commands. Enter the required command at the cursor position. These commands are described in table 3-7. When a B, F, or L command is specified, the E7000 will prompt for another command after execution is completed. The QUIT command ends the system program execution and returns the E7000 monitor to command input wait state. Table 3-7 E7000 Monitor Commands Command Function Reference Section S E7000 system program initiation Initiates the system program. When the system program has not been loaded, loads it from the floppy disk and then initiates the system. Section 3.7, E7000 System Program Initiation R E7000 system program reload Loads and initiates a different system program from the loaded system program. Section 3.7, E7000 System Program Initiation B Floppy disk backup and verification Backs up or verifies a floppy disk. Section 3.6.2, Floppy Disk Backup and Verification F Floppy disk format Formats a floppy disk. Section 3.6.1, Floppy Disk Formatting L IP address specification Specifies the IP address. Section 3.4.1, Power-On Procedure for LAN Interface T Diagnostic Program Initiation Loads and initiates the diagnostic program in the E7000 system floppy disk. If a problem occurs, use this command to initiate the diagnostic program. Attached diagnostic program manual Each monitor command is described in the following pages. The input format for monitor commands is generally as follows: <command name> (RET) (RET): (RET) key input 3-25 S 3.5.2 S Initiates the E7000 system program Command Format * Initiation : S (RET) Description * Initiation Loads the E7000 system program from the system disk. If the system program has already been loaded, it initiates the E7000 system program. Use this command to re-initiate the E7000 system program after modifying the operating environment with the LAN_HOST or MODE command. Also use this command to load and initiate the E7000 system program in normal cases, with the following exceptions. -- An illegal system program is loaded by mistake. -- A system program is reloaded due to system error. Refer to section 3.5.3, R, for details on system program initiation for the above two exceptions. Example To initiate the E7000 system program: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? S (RET) ** E7000 SYSTEM LOADING ** 3-26 3.5.3 R Reloads and initiates the E7000 system program R Command Format * Initiation : R (RET) Description * Initiation Loads the E7000 system program from the system disk and initiates it even if the system program has already been loaded. Use this command to reload the E7000 system program due to system program error or to initiate another E7000 system program whose parameters are different from those in the program that has been loaded. Example To reload and initiate the E7000 system program: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? R (RET) ** E7000 SYSTEM LOADING ** 3-27 B 3.5.4 B Backs up and verifies the E7000 system program Command Format * Backing up : B (RET) * Verification : B; V (RET) Description * Backing up Backs up the E7000 system disk. Use the E7000 system disk backed up with this command. First, format the backup disk with the F command (section 3.5.5) before backing it up with this command. Since the E7000 has only one floppy disk drive, the user must back up the floppy disk, alternately exchanging the source disk with the target disk. Note that the original floppy disk is called the source floppy disk and the disk to be backed up or verified is called the target floppy disk. (S/R/B/F/L/T) ? B (RET) *** FD BACKUP *** SET SOURCE FD (Y/N) (a) (RET) SET TARGET FD (Y/N) (b) (RET) SET NEXT TARGET FD (Y/N) (c) (RET) (a) The source floppy insertion confirmation message. Insert the source floppy disk, and enter Y and the (RET) key to read data from the source floppy disk to the E7000 memory. Enter N to terminate this command. (b) The target floppy disk insertion message displayed after the source floppy disk has been read. Exchange the target floppy disk with the source floppy disk, and enter Y and the (RET) key to write data from the E7000 memory to the target floppy disk. Enter N to terminate this command. (c) Another target floppy disk insertion confirmation message displayed after backup. Insert another target floppy disk, and enter Y and the (RET) key to write data from the E7000 memory to another target floppy disk. Enter N to terminate this command. 3-28 B * Verification Verifies the floppy disk in a manner similar to floppy disk back-up. If a verification error occurs, the following error message is displayed. <SECTOR> <OFFSET> <SOURCE> <TARGET> 0004 045 FF'.' 42'B' (a) (b) (c) (d) (a) (b) (c) (d) Serial number of sector containing a verification error Offset from the sector containing a verification error Source floppy disk data (hexadecimal and ASCII) Target floppy disk data (hexadecimal and ASCII) Examples 1. To back up the E7000 system program: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? B (RET) *** SET SET SET *** FD BACKUP *** SOURCE FD (Y/N) Y (RET) TARGET FD (Y/N) Y (RET) NEXT TARGET FD (Y/N) N (RET) BACKUP END *** START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T)? 3-29 B 2. To verify the E7000 system program: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? B;V (RET) *** SET SET SET *** FD VERIFY *** SOURCE FD (Y/N) Y (RET) TARGET FD (Y/N) Y (RET) NEXT TARGET FD (Y/N) N (RET) VERIFY END *** START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T)? 3-30 F 3.5.5 F Formats the floppy disk Command Format * Formatting : F (RET) Description * Formatting Formats the floppy disk. To back up the system disk, use a disk formatted with this command. Set the floppy disk to be formatted and enter this command. The following messages are displayed to confirm the volume label name and format. (S/R/B/F/L/T) ? F (RET) VOLUME LABEL : <volume label> START FORMAT (Y/N) (b) (RET) (a) (a) <volume label> is displayed. A space is displayed if the floppy disk has no volume label label. (b) Format confirmation message is displayed. Y: Starts formatting N: Terminates this command Example To format a floppy disk: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? F (RET) VOLUME LABEL : WORK START FORMAT (Y/N) Y (RET) 3-31 L 3.5.6 L Sets an E7000 IP address Command Format * Setting : L (RET) Description * Setting Sets an E7000 IP address. This is required to connect the E7000 to the host system through the optional LAN board. For details, refer to section 3.4.1, Power-on Procedure for LAN Interface, and the manual provided with the LAN board. If the L command is entered, the E7000 displays the current IP address and waits for a new IP address input. Note that the IP address must be entered in decimal. (S/R/B/F/L/T) ? L (RET) :IP ADDRESS = xxx.xxx.xxx.xxx (a) (RET) (a) A new IP address in decimal. To not change the IP address, enter only the (RET) key. Example: 128.1.1.101 3-32 L Example To set an E7000 IP address: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? L (RET) :IP ADDRESS = 0.0.0.0 128.1.1.9 (RET) START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? 3-33 T 3.5.7 T Initiates the diagnostic program Command Format * Initiation : T (RET) Description * Initiation Loads the diagnostic program from the system disk and initiates it. Example To initiate the diagnostic program: START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? T (RET) ** E7000 TM LOADING ** 3-34 3.6 Floppy Disk Backup Before using the E7000 system floppy disk, prepare a backup in case the original is damaged. This section describes the disk formatting and backup procedure. 3.6.1 Floppy Disk Formatting Format a backup disk for the E7000 system according to the messages displayed on the console, using the procedure shown below. Only use 2HD (double sided, high density, double track) floppy disks. Do not remove the disk while the disk drive is operating. Procedure Console Messages 1. E7000 monitor command prompt. START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ 2. 3. 4. Insert the floppy disk to be formatted. Enter F and (RET). A volume label is displayed if there is a volume on the floppy disk. Format start confirmation message. Enter Y (RET) to format, otherwise enter N (RET). The E7000 monitor prompts for another command after formatting is completed. 5. 6. (S/R/B/F/L/T) ? F (RET) VOLUME LABEL : xx . . . . . . . . . xx START FORMAT (Y/N) ? Y (RET) If an error occurs during formatting, refer to section 12, Error Messages, in Part III, Emulator Function Guide, for details. 3-35 3.6.2 Floppy Disk Backup and Verification Use the following procedures to back up and verify a floppy disk. Backup: Procedure Console Messages 1. E7000 monitor command prompt. START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ 2. Enter backup command B (RET). (S/R/B/F/L/T) ? B (RET) 3. Backup start message and source floppy disk insertion request message. 4. Insert the source floppy disk. 5. Enter Y (RET). Data is read from the source floppy disk into the E7000 internal RAM. SET SOURCE FD (Y/N) ? Y (RET) 6. When read is completed, the target floppy disk insertion message is displayed. Exchange the floppy disk. SET TARGET FD (Y/N) ? _ 7. Enter Y (RET). The E7000 internal RAM contents are written to the target floppy disk. SET TARGET FD (Y/N) ? Y (RET) 8. When write is completed, the E7000 asks whether to back up another target floppy disk or complete backup operation. SET NEXT TARGET FD (Y/N) ? _ 9. To make a backup on another target floppy disk, insert the new target disk and then enter Y (RET). Repeat steps 6 to 9. SET NEXT TARGET FD (Y/N) ? Y (RET) *** FD BACKUP *** SET SOURCE FD (Y/N) ? _ 10. Enter N (RET) to complete backup operation. SET NEXT TARGET FD (Y/N) ? N (RET) 11. Backup completion message. The E7000 monitor prompts for another command. *** BACKUP END *** 3-36 Verification: Procedure Console Messages 1. E7000 monitor command prompt. START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ 2. Enter verification command B;V (RET). 3. Verification start message and source floppy disk insertion request message. 4. Insert the source floppy disk. 5. Enter Y (RET). Data is read from the source floppy disk into the E7000 internal RAM. SET SOURCE FD (Y/N) ? Y (RET) 6. When read is completed, the target floppy disk insertion message is displayed. Exchange the floppy disk. SET TARGET FD (Y/N) ? _ 7. Enter Y (RET). The contents of E7000 internal RAM are compared with the contents of the target floppy disk. SET TARGET FD (Y/N) ? Y (RET) 8. When comparison is completed, the E7000 asks whether to verify another target floppy disk or complete verification operation. SET NEXT TARGET FD (Y/N) ? _ 9. To verify another target floppy disk, insert the new target disk and then enter Y (RET). Repeat steps 6 to 9. SET NEXT TARGET FD (Y/N) ? Y (RET) (S/R/B/F/L/T) ? B;V (RET) *** FD VERIFY *** SET SOURCE FD (Y/N) ? _ 10. Enter N (RET) to complete verification operation. SET NEXT TARGET FD (Y/N) ? N (RET) 11. Verification completion message. The E7000 monitor prompts for another command. *** VERIFY END *** 3-37 Notes: 1. Any differences in the contents of the disks are displayed in the following format: <SECTOR> xxxx (a) (a) (b) (c) (d) (e) (f) <OFFSET> xxx (b) <SOURCE> xx 'x' (c) (d) <TARGET> xx 'x' (e) (f) Serial number of sector containing the difference, beginning at 0 (hexadecimal) Offset in the sector containing the difference (hexadecimal) Source floppy disk contents (hexadecimal) Source floppy disk contents in ASCII characters Target floppy disk contents (hexadecimal) Target floppy disk contents in ASCII characters 2. During both backup and verification, entering N (RET) in response to the floppy disk insertion request message terminates command execution and returns the E7000 to command input wait state. 3. If a floppy disk error occurs during backup or verification, an error message is displayed and command execution is aborted. Refer to section 12, Error Messages, in Part III, Emulator Function Guide, for details. 3-38 3.7 E7000 System Program Initiation When the E7000 system floppy disk is not inserted after the E7000 is turned on, the E7000 monitor enters command input wait state and the E7000 system program must be loaded and initiated by monitor commands. If the system floppy disk is inserted immediately after power-on, the system program is automatically loaded and initiated. 3.7.1 Initiation on E7000 Monitor If S or R is entered, followed by (RET), when the E7000 is in monitor command input wait state, the E7000 system program is loaded from the system disk and initiated. Table 3-8 E7000 System Program Initiation Commands Command Description S Loads and initiates the system program from the E7000 system disk. If the E7000 system program is already loaded, the system program is initiated immediately.* R Reloads and initiates the E7000 system program. Note: This situation occurs when the system program is initiated and then terminated with the QUIT command. However, if the E7000 monitor F (format), or B (backup or verification) command has been executed, or when the system program has been forcibly terminated by a clock error, the system program is reloaded. Display at E7000 System Program Initiation START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD (a) L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? S (RET) R {} ** E7000 SYSTEM LOADING ** (b) H8/xxxx E7000 (HSxxxxEPDxxSF) Vn.m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. 3-39 (c) CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHEC POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz MCU NAME = H8/xxxx MODE=x PIN=xxx (MD x-x=x) REMAINS EMULATION MEMORY S=xxxxx/Exxxxxx (d) (e) (f) (g) (h) (i) (j) (k) (l) WARM OR COLD START file name : WARM START return : COLD START (file name/return) ? <file name> (RET) (RET) : (m) { } (n) Description (a) E7000 command input request message. Insert the E7000 system disk and enter S. Enter R if loading another E7000 system program. (b) The E7000 system program is being loaded from the floppy disk. (c) Start message of the E7000 system program. Vn.m is the version number. (d) Configuration file is being loaded. (e) IP address file for the LAN is being loaded. (f) Emulator station hardware test start message. If there is an error in the emulator station, an error message is displayed. For details, refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. (g) The program to be executed in the emulator pod is being loaded from the floppy disk. (h) Emulator pod test start message. If there is an error in the emulator pod, an error message is displayed. For details, refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. (i) An RES signal has been input to the MCU. (j) Specified clock. If the user system is ready, the user system's clock (U) is used. If not, but the crystal oscillator (X) is ready, the crystal oscillator is used. If neither the user system clock or the oscillator clock is ready, the 13-MHz E7000 internal clock is used. 3-40 (k) MCU type, MCU operating mode, number of pins, and user system mode selection pin state. They are previously set with the MODE command (saved in configuration file). For details, refer to section 7.2.28, MODE, in Part III, Emulator Function Guide. (l) Remaining emulation memory size. (m) Specify either WARM START*1 or COLD START*2 as follows: WARM START: Specify the file name containing recovery information. COLD START: Press the (RET) key. (n) E7000 system program prompt. An E7000 system program command can now be entered. Notes: 1. WARM START recovers the information saved in a file when the E7000 system program was terminated by a QUIT command. (For details, refer to section 7.2.33 QUIT, in Part III, Emulator Function Guide.) The recovery information is listed below. * * * * * PC breakpoints Hardware break conditions, and trace stop and acquisition conditions Memory map information Configuration information Performance analysis information 2. COLD START initializes the above emulation information. 3-41 3.7.2 Automatic Initiation of E7000 System Program If the E7000 system disk is inserted after E7000 internal system test at power-on has been completed, the E7000 system program is automatically loaded. Console Display Procedure E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. After E7000 power-on, insert the system disk when this message is displayed. TESTING RAM 0123 ** E7000 SYSTEM LOADING E7000 system program is being loaded. ** H8/xxxx E7000 (HSxxxxEPDxxSF) Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. Vn.m System program is initiated. (Refer to section 3.5.1, E7000 Monitor Initiation.) CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz M C U NAME = H8/xxxx MODE=x PIN=xxx (MD x-x=x) REMAINS EMULATION MEMORY S = xxxxx/Exxxxxx WARM OR COLD START file name : WARM START return : COLD START (file name/return) ? <file name> (RET) (RET) { } : 3-42 Section 4 Operating Examples Section 4.1, Basic Examples, and section 4.2, Application Examples, include explanations based on the following user program. ADDR 000100 000106 000108 00010A 00010C 00010E 000110 000112 000116 CODE 7A0700FF FF0E F800 F900 8802 8901 A90A 46F8 6A881000 40FE LABEL MNEMONIC MOV.L OPERAND #00FFFF0E:32,ER7 MOV.B MOV.B ADD.B ADD.B CMP.B BNE MOV.B BRA #00:8,R0L #00:8,R1L #02:8,R0L #01:8,R1L #0A:8,R1L 00010A:8 R0L,@1000:16 000116:8 These examples assume that the emulator station is connected to the LAN host system with the Telnet and that the user program is downloaded from the host system to the E7000. Therefore, store the program in the host system before initiating the E7000. In these examples, the host name is HITACHI, and the IP address is 128.0.0.1. Initiate the E7000 by the following procedure: Operations Console Message 1. E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. Insert the E7000 system disk into the floppy disk drive of the emulator station, and turn on the power. TESTING RAM 0123 4-1 2. The console displays the message shown on the right when the E7000 starts operation normally. (If the console does not display this message, take corrective action as described in section 5, Troubleshooting.) ** E7000 SYSTEM LOADING ** H8/xxxx E7000 (HSxxxxEPDxxSF) Vn.m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz MCU NAME = H8/xxxx MODE=x PIN=xxx (MD x-x=x) REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx WARM OR COLD START file name: WARM START return 3. Enter (RET). : COLD START (file name/return) ? (RET) :_ 4-2 4.1 Basic Examples 4.1.1 Preparing for Connection of LAN Host System Before connecting the host system, specify the host name and the IP address by the following procedure: Operations Console Message 1. :LAN_HOST;S (RET) Specify the IP address of the host system to which the E7000 is to be connected by the FTP command. Enter LAN_HOST;S (RET), and the console will display the host names and IP addresses already specified and wait for the user to enter a selection number. :LAN_HOST;S (RET) NO <HOST NAME> <IP ADDRESS> NO <HOST NAME> <IP ADDRESS> 01 HOST_A 128.1.1.0 02 HOST_B 128.1.1.1 03 HOST_C 128.1.1.2 04 HOST_D 128.1.1.3 05 HOST_E 128.1.1.4 06 HOST_F 128.1.1.5 07 HOST_G 128.1.1.6 08 HOST_H 128.1.1.7 09 HOST_I 128.1.1.8 PLEASE SELECT NO? _ 2. Enter 1 (RET) as the selection number, HITACHI (RET) as the host name, and 128.0.0.1 (RET) as the IP address. After that, the console prompts the user to select another number. Enter . (RET) to exit interactive input mode. After the host name and IP address have been specified, the console asks if the specified name and address should be overwritten to the LANCNF.SYS file in the system disk. To store them, enter Y (RET). PLEASE SELECT NO? 1 (RET) 01 HOST NAME HOST_A HITACHI (RET) 01 IP ADDRESS 128.1.1.0 128.0.0.1 (RET) PLEASE SELECT NO? . (RET) OVERWRITE (Y/N)? Y (RET) 4-3 3. After the name and address have been stored in the LANCNF.SYS file, the E7000 system program automatically terminates. Therefore, restart the E7000 system. START E7000 S : START E7000 R : RELOAD & START E7000 B : BACKUP FD F : FORMAT FD L : SET LAN PARAMETER T : START DIAGNOSTIC TEST 4. Enter S (RET) to re-initiate the system. (S/R/B/F/L/T) ? S (RET) WARM OR COLD START file name: WARM START return 5. Enter (RET). Note: : COLD START (file name/return) ? (RET) The above host name and IP address are examples. Specify the actual host name and IP address according to the system. 4-4 4.1.2 Specifying the MCU Operating Mode Specify the E7000 operating mode and the MCU operating mode by the following procedure: Operations Console Message 1. Enter MODE;C (RET) to specify the E7000 operating mode. :MODE;C (RET) 2. The console displays the message. MCU NAME (1:H8/3048,2:H8/3047,3:H8/3044,4:H8/3048F) ? _ 3 Enter 1 (RET) to select the H8/3048. MCU NAME (1:H8/3048,2:H8/3047,3:H8/3044,4:H8/3048F) ? 1 (RET) 4 Enter 3 (RET) to select MCU operating mode 3. OPERATION MODE ? 5. After the above specification has been completed, the console asks if the mode settings should be stored in the configuration file. To store the mode settings, enter Y (RET). After that, the E7000 operates in the mode specified above whenever initiated with this system disk. To correct a mis-typed mode number, return to step 1 above before entering Y (RET) and repeat the procedure. Remove the write protect from the system floppy disk before storing the mode settings in the configuration file. CONFIGURATION WRITE OK ? (Y/N) ? _ OPERATION MODE ? 3 (RET) CONFIGURATION WRITE OK ? (Y/N ) ? Y(RET) START E7000 S : START E7000 R : RELOAD & START E7000 6. After the mode settings have been stored in the configuration file, the E7000 system program automatically terminates. B : BACKUP FD F : FORMAT FD L : SET LAN PARAMETER T : START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ 7. Enter S (RET) to re-initiate the system program. (S/R/B/F/L/T) ? S (RET) WARM OR COLD START file name: WARM START return : COLD START (file name/return) ? _ 8. (file name/return) ? (RET) Enter (RET). 4-5 4.1.3 Allocating Standard Emulation Memory and Specifying Attributes In order to load the user program to memory, allocate the standard emulation memory in the pods by the following procedure: Operations Console Message Enter MAP 0 1FFFF;S (RET) to allocate the standard emulation memory to addresses H'0 to H'1FFFF. The console displays the message shown on the right, which indicates that the memory allocation has been completed. Enter MAP (RET) and the console displays the attributes of all the memory areas. :MAP 0 1FFFF;S (RET) REMAINS EMULATION MEMORY S=60000/E=000000 :MAP (RET) 000000 - 01FFFF;S 020000 - FFFFFF;U INTERNAL RAM = FFEF10 - FFFF0F INTERNAL I/O = FFFF1C - FFFFFF REMAINS EMULATION MEMORY S=60000/E=000000 4-6 4.1.4 Loading the User Program Load the user program from the host system to the E7000 by the following procedure: Operations Console Message 1. Enter FTP <host name> (RET) to connect the E7000 and the host system with the FTP server. :FTP <host name> (RET) 2. The console asks for the user name. Enter <user name> (RET). Username : _ The console asks for the password. Enter <password> (RET). Password : _ The console displays the message shown on the right, which indicates that the E7000 and the host system have been connected. login command success To load the program, enter LAN_LOAD;S:<file name> (RET). This example assumes that the load module is S type. While loading, the console displays the address to which the program is being loaded as shown on the right. FTP>LAN_LOAD;S:<file name> (RET) When the program has been loaded, the console displays the start address of the program (TOP ADDRESS), and its end address (END ADDRESS). TOP ADDRESS = xxxxxx Entering BYE (RET) terminates the FTP server connection. The console will display the message shown on the right. FTP>BYE (RET) 3. 4. 5. 6. 7. Username : <user name> (RET) Password : <password> (RET) FTP>_ LOADING ADDRESS xxxxxx END ADDRESS = xxxxxx FTP>_ bye command success Note: The following operations can be performed even when the BYE command is not executed and the FTP prompt is displayed. In this case, be sure not to power down the E7000 before executing the BYE command. 4-7 8. The DISASSEMBLE command displays the loaded program. Enter DISASSEMBLE 100 117 (RET). :DISASSEMBLE 100 117 (RET) ADDR CODE 000100 7A0700FF LABEL MNEMONIC OPERAND MOV.L #00FFFF0E:32,ER7 #00:8,R0L FF0E 000106 F800 MOV.B 000108 F900 MOV.B #00:8,R1L 00010A 8802 ADD.B #02:8,R0L 00010C 8901 ADD.B #01:8,R1L 00010E A90A CMP.B #0A:8,R1L 000110 46F8 BNE 00010A:8 000112 6A881000 MOV.B R0L,@1000:16 000116 40FE BRA 000116:8 4-8 4.1.5 Executing Program Execute the loaded program by the following procedure: Operations Console Message 1. : .SP (RET) Enter .SP (RET) then FFFF0E (RET) as the SP value to set the stack pointer (SP) to H'FFFF0E. The console then asks for the program counter (PC) value. Enter 100 (RET) as the program counter value. The console then asks for the condition code register (CCR) value. In this example, the condition code register need not be set or changed, therefore, enter . (RET) to exit this interactive mode. ER7(SP) =00FFFF1A ? _ ER7(SP) =00FFFF1A ? FFFF0E (RET) PC = FFFFFF ? _ PC = FFFFFF ? 100 (RET) CCR = 80:I****** ? _ CCR = 80:I****** ? .(RET) :_ Note: In interactive mode, entering only (RET) makes no change to the currently displayed item, and the next item is displayed. In the above example, entering only (RET) to the condition code register prompt can complete the register modification procedure. The register value can also be directly input without using the interactive mode. For example, to set the stack pointer value directly, enter .SP FFFF0E (RET). 2. 3. Enter GO (RET) to execute the program from the address pointed by the PC. While the program is executed, the console displays the current program counter value (shown as xxxxxx on the right). :GO (RET) Enter (BREAK) key or (CTRL) + C keys to terminate program execution. The console displays the contents of the program counter, condition code register, and the general registers ER0 to ER7 at termination. RUN - TIME shows the duration of program execution from the GO command execution to (BREAK) or (CTRL) + C key input. BREAK KEY shows that the execution has been terminated because (BREAK) or (CTRL) + C was entered. (BREAK) ** PC = xxxxxx PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:01S:049705US BREAK KEY : _ 4-9 4.1.6 PC Break Program execution can be stopped at a particular address by setting a breakpoint as follows: Operations Console Message 1. Enter BREAK 10C (RET) to terminate program execution when the instruction at address H'10C in the program is executed. :BREAK 10C (RET) 2. Restart program execution from address H'100. This can be done in two ways: one is to enter the start address directly, and the other is to first set the program counter to H'100, then enter GO, as described in section 4.1.5, Executing Program. :GO 100 (RET) The program execution terminates when the instruction at address H'10C is executed. The console displays the data shown on the right. The BREAK POINT 00010C shows that the program execution was terminated because of a PC breakpoint at H'10C. PC = 00010E 3. ** PC = xxxxxx CCR=80:I******* ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000014US BREAK POINT 00010C : _ 4-10 4.1.7 Single-Step Execution A single instruction can be executed using the single-step function by the following procedure: Operations Console Message 1. The program counter points to the next address to be executed when the program execution terminates in the example of section 4.1.6, PC Break. Here, entering STEP (RET) executes only one instruction, and the console displays the information as shown on the right. 00010E CMP.B #0A:8,R1L shows the executed address and mnemonic code, and STEP NORMAL END shows that the single-step execution has terminated. :STEP (RET) To repeat single-step execution, enter only (RET). This can be repeated until another command is executed. :(RET) 2. PC = 000110 CCR=A9:I*H*N**C ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E 00010E CMP.B #0A:8,R1L STEP NORMAL END :_ PC = 00010A CCR=A9:I*H*N**C ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E 000110 BNE STEP NORMAL END :_ 4-11 00010A:8 4.1.8 Setting Hardware Break Conditions Various hardware break conditions can be specified by the following procedure: Operations Console Message 1. Enter BREAK - (RET) to cancel the breakpoint set in the example in section 4.1.6, PC Break. :BREAK - (RET) 2. To confirm the cancellation, execute the BREAK command (enter BREAK (RET)). *** 45: NOT FOUND shows that no PC breakpoint is set. :BREAK (RET) 3. To specify that program execution should terminate when data is written to address H'1000, enter BREAK_ CONDITION1 A = 1000 W (RET). :BREAK_CONDITION1 A = 1000 W (RET) 4. Enter GO 100 (RET) to start executing the program from address H'100. When the break condition is satisfied, the console displays the information shown on the right. BREAK CONDITION1 shows that the program execution has terminated because the break condition was satisfied. :GO 100 (RET) *** 45: NOT FOUND ** PC = xxxxxx PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000093US BREAK CONDITION1 :_ 4-12 4.1.9 Displaying Trace Information Trace information acquired during program execution can be displayed by the following procedure: Operations Console Message 1. :TRACE (RET) Enter TRACE (RET) to see the trace information. The console will display the instruction mnemonic information. IP ADDR LABEL 000100 MOV:L #00FFFF0E:32,ER7 *-D'00043 000106 MOV.B #00:8,R0L *-D'00042 000108 MOV.B #00:8,R1L *-D'00041 00010A ADD.B #02:8,R0L 00010C ADD.B #01:8,R1L : To display the trace information in buscycle units, enter TRACE;B (RET). BP * AB DB MA R/W 000100 : : :TRACE;B (RET) ST IRQ MOV.L NMI RES RA PROB VCC CLK #00FFFF0E:32,ER7 -D'00123 000100 79 EXT R PRG 111111 1 1 11 11111111 1 08 -D'00122 000101 07 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00121 000102 79 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00120 000103 07 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00119 000104 FF EXT R PRG 111111 1 1 11 11111111 1 06 -D'00118 000105 FE EXT R PRG 111111 1 1 11 11111111 1 06 -D'00117 000106 F8 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00116 000107 00 EXT R PRG 111111 1 1 11 11111111 1 06 * 000106 MOV.B : 3. OPERAND *-D'00044 *-D'00040 2. MNEMONIC To temporarily stop the trace information display, enter (CTRL)+S. To continue the display, enter (CTRL)+Q. (CTRL)+S and (CTRL)+Q are also effective on other information display. #00:8,R0L : : (CTRL)+S (CTRL)+Q 4-13 4.2 Application Examples 4.2.1 Break with Pass Count Condition The pass count condition can be set to a breakpoint by the following procedure: Operations Console Message 1. Enter BREAK 10A 5 (RET) to terminate program execution when address 10A is passed five times. :BREAK 10A 5 (RET) 2. To start execution from address H'100, enter GO 100 (RET). :GO 100 (RET) 3. When execution terminates after address H'10A is passed five times, the console displays the data shown on the right. ** PC = xxxxxx PC = 00010C CCR=80:I******* ER0 - ER3 0000000A 00000004 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000058US BREAK POINT 0010A :_ 4. Entering BREAK (RET) displays (a) the breakpoint address, (b) the specified count, and (c) the pass count as shown on the right. The pass count is cleared when the GO command is entered again. :BREAK (RET) ADDRESS CNT PASS 00010A 0005 0005 (a) (b) (c) 4-14 SYMBOL 4.2.2 Conditional Trace The following procedure can be used to limit the acquisition of trace information during program execution. Operations Console Message 1. To cancel the breakpoint set in the example of section 4.2.1, Break with Pass Count Condition, enter BREAK - (RET). :BREAK - (RET) 2. Enter TRACE_CONDITION A =100:106;R (RET) to get trace information only while the program counter is between addresses H'100 and H'106. :TRACE_CONDITION A= 100:106;R (RET) 3. Enter GO 100 (RET) to start executing the program, then (BREAK) key or (CTRL) + C keys to terminate the execution. :GO 100 (RET) ** PC = xxxxxx PC = 000116 (BREAK) CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:01S:049705US BREAK KEY :_ 4. Enter TRACE (RET) to display the trace information acquired under the specified condition. :TRACE (RET) IP ADDR * D'***** 000100 * D'***** 000106 LABEL : 4-15 MNEMONIC OPERAND MOV.L #00FFFF0E:32,ER7 MOV.B #00:8,R0L 4.2.3 Parallel Mode During program execution in parallel mode, the memory contents can be displayed or modified by the following procedure: Operations Console Message 1. :GO 100 (RET) After executing the GO command, enter (RET) to move to parallel mode. ** PC = xxxxxx (RET) #_ 2. Enter DUMP 1000 100F (RET) to display the memory contents from H'1000 to H'100F. <ADDR> #DUMP 1000 100F (RET) <D A T A> <ASCII CODE> 001000 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3. Enter MEMORY 117 EE (RET) to modify the contents of memory address H'117 into EE. #MEMORY 117 EE (RET) 4. To exit from parallel mode, enter END (RET). #END (RET) To terminate program execution, enter (BREAK) key or (CTRL) + C keys. (BREAK) ". . . . . . . . . . . . . . . ." ** PC = xxxxxx 5. PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:07M:25S:441007US BREAK KEY :_ 6. Enter DISASSEMBLE 100 117 (RET) to confirm that the program has been changed by memory modification in parallel mode. : DISASSEMBLE 100 117 (RET) 4-16 ADDR CODE 000100 7A0700FF LABEL MNEMONIC OPERAND MOV.L #00FFFF0E:32,ER7 #00:8,R0L FF0E 000106 F800 MOV.B 000108 F900 MOV.B #00:8,R1L 00010A 8802 ADD.B #02:8,R0L 00010C 8901 ADD.B #01:8,R1L 00010E A90A CMP.B #0A:8,R1L 000110 46F8 BNE 00010A:8 000112 6A881000 MOV.B R0L,@1000:16 000116 40EE BRA 000106:8 4.2.4 Searching Trace Information The TRACE_SEARCH command can be used to search for a particular part of the acquired trace information. Console Message Operations Enter TRACE_SEARCH A=116 (RET), and the console will only display those parts of the trace information in which the address bus value is H'116. BP AB :TRACE_SEARCH A=116(RET) DB MA R/W ST IRQ NMI RES RA PROB VCC CLK -D'04077 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 -D'03964 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 -D'03851 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 : : : : : : 4-17 4.2.5 Sequential PC Break A break can be generated when specified addresses are passed in a specified order, using the BREAK_SEQUENCE command as follows: Operations Console Message 1. :BREAK_SEQUENCE 110 10A (RET) Enter BREAK_SEQUENCE 110 10A (RET), which terminates program execution when the instructions at addresses H'110 and H'10A are executed consecutively in that order, as shown in figure 4-1. ADDR CODE LABEL 000100 7A0700FF FF0E 000106 F800 000108 F900 00010A 8802 00010C 8901 00010E A90A 000110 46F8 000112 6A881000 000116 40EE MNEMONIC MOV.L Program execution flow OPERAND #00FFFF0E:32,ER7 MOV.B MOV.B ADD.B ADD.B CMP.B BNE MOV.B BRA #00:8,R0L #00:8,R1L #02:8,R0L #01:8,R1L #0A:8,R1L 00010A:8 R0L,@1000:16 000106:8 Figure 4-1 Program Execution Flow 2. Enter GO 100 (RET) to execute the program. When the specified condition is satisfied, execution terminates, and the console displays the data shown on the right. The BREAK SEQUENCE shows that execution has terminated because the condition specified in the BREAK_SEQUENCE command has been satisfied. :GO 100 (RET) ** PC = xxxxxx PC = 00010C CCR=80:I******* ER0 - ER3 00000004 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000028US BREAK SEQUENCE :_ 4-18 3. Enter TRACE (RET) to confirm the executed instructions. :TRACE (RET) MNEMONIC OPERAND *-D'00007 IP ADDR 000100 MOV.L #00FFFF0E:32,ER7 *-D'00006 000106 MOV.B #00:8,R0L *-D'00005 000108 MOV.B #00:8,R1L *-D'00004 00010A ADD.B #02:8,R0L *-D'00003 00010C ADD.B #01:8,R1L *-D'00002 00010E CMP.B #0A:8,R1L *-D'00001 000110 BNE 00010A:8 * D'00000 00010A ADD.B #02:8,R0L :_ 4-19 LABEL Appendix A Floppy Disk Drive Specifications Table A-1 summarizes the specifications of the 3.5-inch floppy disk drive installed in the E7000. Table A-1 3.5-Inch Floppy Disk Drive Specifications Item Specification Storage capacity Approx. 1.2 Mbytes (512 bytes x 15 sectors x 160 tracks) Double-sided, high density, double tracks Recording method MFM type Recording format IBM format (512 bytes/sector, 15 sectors/track) Recommended disks MF2-256HD (Maxell) A-1 Appendix B Connector Specifications This section describes console connector pin locations and console connecting methods. B.1 Console Connector Figure B-1 shows pin locations in the console's connector. Table B-1 lists signal names and their usages. CRT 13 12 11 10 9 8 7 25 24 23 22 21 20 19 6 5 4 3 2 18 17 16 15 14 1 Figure B-1 Console Connector Pin Locations Table B-1 Signal Names and Usage of Console Connector Pin No. Signal Name Usage 1 Frame Ground (FG) Connected to the E7000's frame ground 2 Receive Data (RD) Data receive line 3 Transmit Data (TD) Data transmit line 4 Clear To Send (CTS) Not used 5 Request To Send (RTS) High when E7000's power is on 6 Data Terminal Ready (DTR) High when E7000's power is on 7 Signal Ground (SG) Signal ground 8 Data Carrier Detect (DCD) High when E7000's power is on 9-19 Not connected -- 20 Data Set Ready (DSR) Not used 21-25 Not connected -- B-1 B.2 Host System Connector Figure B-2 shows pin locations in the host system's connector. Table B-2 lists signal names and their usages. 13 12 11 10 9 8 7 25 24 23 22 21 20 19 6 5 4 3 2 18 17 16 15 14 1 HOST Figure B-2 Host System Connector Pin Locations Table B-2 Signal Names and Usage of Host System Connector Pin No. Signal Name Usage 1 Frame Ground (FG) Connected to E7000 frame ground 2 Transmit Data (TD) Data transmit line 3 Receive Data (RD) Data receive line 4 Request To Send (RTS) RTS control 5 Clear To Send (CTS) CTS control 6 Data Set Ready (DSR) Not used 7 Signal Ground (SG) Signal ground 8-19 Not connected -- 20 Data Terminal Ready (DTR) High when E7000 power is on 21-25 Not connected -- B-2 B.3 Printer Connector The layouts of the connector pin at the E7000 end of the provided printer cable is shown in figure B-3. Signal names and pin assignments are given in table B-3. 26 24 22 20 18 16 14 12 10 8 25 23 21 19 17 15 13 11 9 7 6 5 4 3 2 1 P R I N T E R Figure B-3 Printer Cable Connector Pin Layouts Table B-3 Printer Cable Connector Pin Assignment Pin No. Signal Name Pin No. Signal Name 1 FAULT 14 GND 2 0 V 15 ACKNLG 3 DATA STROBE 16 GND 4 GND 17 BUSY 5 DATA1 18 GND 6 DATA2 19 PE 7 DATA3 20 GND 8 DATA4 21 SELECT 9 GND 22 GND 10 DATA5 23 INPUT PRIME 11 DATA6 24 GND 12 DATA7 25 NC 13 DATA8 26 NC B-3 * Signal functions Signal functions listed in table B-3 are described below. DATA1 to DATA8: Data is output by these lines. DATA STROBE: Data is output from the data output lines when this signal goes low. BUSY: The E7000 will not send the next data as long as this signal is high. ACKNLG: This signal goes low and the E7000 outputs the next data. PE: If this signal goes high, the E7000 stops data outputs and displays the error message ***8: PAPER EMPTY. SELECT: If this signal is low, the E7000 sends no data and outputs the error message ***7: PRINTER NOT READY. FAULT: If this signal is low, the E7000 sends no data and outputs an error message. If the PE signal is high, the E7000 outputs the error message ***8: PAPER EMPTY If the PE signal is low, the E7000 outputs the error message ***7: PRINTER NOT READY INPUT PRIME: The E7000 forces this signal low when it starts up. * Data output timing Data output timing of the E7000 is shown in figure B-4. DATA1-DATA8 DATA STROBE 5 s 5 s BUSY ACKNLG Note: Since the E7000 checks the BUSY and ACKNLG signals, make sure that they are connected in the printer interface cable. Figure B-4 Data Output Timing B-4 B.4 LAN Connector Figure B-5 shows pin locations in the LAN connector. Table B-4 lists pin numbers and signal names. LAN 8 15 7 6 14 13 5 4 12 11 3 10 2 9 1 Figure B-5 LAN Connector Pin Locations Table B-4 Pin Numbers and Signal Names in LAN Connector Pin Signal Name 1 NC 2 COL+ 3 TX+ 4 -- 5 RX+ 6 GND 7 -- 8 -- 9 COL- 10 TX- 11 -- 12 RX- 13 +12 V 14 -- 15 -- B-5 B.5 E7000 to Console Connection Figure B-6 shows the wiring for the console connection. A console is connected to the console connector on the E7000 emulator station rear panel with the provided console interface cable. Console FG TD RD RTS CTS DSR SG DCD DTR E7000 (console connector) 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 DCD*2 20 20 DSR*1 FG RD Notes: 1. There is no need to connect these pins since they are not used by the E7000. TD 2. High when E7000's power is on. There is no need to connect these pins if they are not used at the console end. CTS*1 RTS*2 DTR*2 3. Pins 9-19, 21, and the following are not connected. SG (Numbers are connector pin numbers) Figure B-6 Console to E7000 Wiring B-6 B.6 E7000 to Host System Connection Figure B-7 shows the wiring for the E7000 to host system connection when the optional host system interface cable is used. Host system FG TD RD RTS CTS DSR SG DCD DTR E7000 (host system connector) 1 1 2 2 3 3 4 4 5 5 6 6 7 7 FG RD Notes: 1. There is no need to connect these pins since they are not used by the E7000. TD CTS*1 RTS*2 DTR*2 SG 8 8 DCD*2 20 20 DSR*1 2. High when E7000's power is on. There is no need to connect these pins if they are not used at the host system end. 3. Pins 9-19, 21, and the following are not connected. (Numbers are connector pin numbers) Figure B-7 Host System to E7000 Wiring Note that provided host system interface cable may not be suitable for some host systems. In that case, use the wiring shown in figure B-8. Host system FG TD RD 1 2 3 E7000 (host system connector) 1 FG 2 TD 3 RD FG TD RD RTS CTS SG SG 7 7 E7000 (host system connector) Host system 1 1 2 2 3 3 4 4 5 5 7 7 FG TD RD RTS CTS SG SG DSR (Numbers are connector pin numbers) 6 * 20 DSR (Numbers are connector pin numbers) Note: High when E7000's power is on. If this pin is not being used by the host system, there is no need to connect it at the host system end. (a) X-ON/X-OFF Control (b) RTS/CTS Control Figure B-8 Host System Wiring (Using Other Cable) B-7 B.7 Printer Cable Connection Table B-5 shows the signal names and their corresponding printer and E7000 pin numbers. Table B-5 Pin Numbers and Signal Names in Printer and E7000 Pin No. Signal Name Printer E7000 1 DATA STROBE GND 1 19 3 4 2 DATA1 GND 2 20 5 4 3 DATA2 GND 3 21 6 16 4 DATA3 GND 4 22 7 9 5 DATA4 GND 5 23 8 9 6 DATA5 GND 6 24 10 18 7 DATA6 GND 7 25 11 20 8 DATA7 GND 8 26 12 14 9 DATA8 GND 9 27 13 14 10 ACKNLG GND 10 28 15 16 11 BUSY GND 11 29 17 18 12 PE GND 12 29 19 20 13 SELECT GND 13 20 21 22 14 INPUT PRIME GND 31 30 23 24 15 FAULT 0 V 32 16 1 2 16 FG FG 17 FG FG 18 FG FG Remarks The cable shield and line pairs 16, 17, and 18 are all held to the frame ground. At the printer end, they are all connected to pin 17. B-8 Part II E7000PC Guide Section 1 Overview This system is an efficient software and hardware development support tool for application systems using the H8/3048 series or H8/3048F microcomputer (abbreviated to MCU) developed by Hitachi, Ltd. The H8/3048 series includes three types of MCUs: H8/3048, H8/3047, and H8/3044. They contain the following components on a single chip: * * * * * * * * * High-speed CPU Internal RAM Internal ROM Timers Serial communication interface (including one channel for smart card interface) Refresh controller DMAC I/O ports A/D and D/A converters The H8/3048F has the same functions as the H8/3048 except that it has flash memory instead of internal ROM. When the E7000 is connected to a user system, it operates in place of the MCU and performs realtime emulation of the user system. Additionally, the E7000 provides functions for efficient software and hardware debugging. The E7000 consists of an emulator station, emulator pod, and user system interface cable, as shown in figure 1-1. The emulator pod should be connected to the user system via the user system interface cable. 1-1 E7000 PC User system interface cables Station-pod interface cables Emulator pod HITACHI Emulator station Figure 1-1 H8/3048-Series, H8/3048F E7000PC Emulator 1-2 The E7000PC provides the following features: * Realtime emulation of MCU * A wide selection of emulation commands, promoting efficient system development * Help functions to facilitate command usage without a manual * Efficient debugging enabled by variable break functions and mass-storage trace memory (32 kcycles) * Command execution during emulation, for example: -- Trace data display -- Emulation memory display and modification * Measurement of subroutine execution time and frequency for evaluating the execution efficiency of user programs * An optional IBM PC board for interfacing with an IBM PC*, enabling high-speed downloading (1 Mbyte/min) of user programs Note: IBM PC is a registered trademark of International Business Machines Corporation. * E7000PC graphical user interface software (E7000PC GUI: option) can be loaded into the personal computer to enable: -- Graphic display operations in a window environment -- Source level debugging -- Graphic display of trace information * 512 kbytes of emulation memory as substitute user system memory. An optional 1-Mbyte or 4-Mbyte emulation memory board can also be installed in the emulator station. * By connecting the user system interface and providing a low-voltage power supply of 2.7 to 5.5 V, emulation can be performed in user systems with any supply voltage in the range 2.7 to 5.5 V. 1-3 1.1 Warnings Before using the E7000PC, carefully read the following warnings. If the E7000PC is not used correctly, breakdowns may occur. 1. Check all components with the component list after unpacking the E7000PC. 2. Never place heavy objects on the casing. 3. Observe the following conditions in the area where the E7000PC is to be used: * Make sure that the internal cooling fans on the sides of the emulator station are at least 20 cm (8") away from walls or other equipment. * Keep out of direct sunlight or heat. Refer to section 1.2, Environmental Conditions. * Use in an environment with constant temperature and humidity. * Protect the E7000PC from dust. * Avoid subjecting the E7000PC to excessive vibration. Refer to section 1.2, Environmental Conditions. 4. Protect the E7000PC from excessive impacts and stresses. 5. Before using the E7000PC's power supply, check its specifications such as power output, voltage, and frequency. For details on power supply, refer to section 1.2, Environmental Conditions. 6. When moving the E7000PC, take care not to vibrate or otherwise damage it. Pay special attention to exposed parts such as the power switch and I/O connectors. 7. After connecting the cable, check that it is connected correctly. For details, refer to section 3, Preparation before Use. 8. Supply power to the E7000PC emulator and connected parts after connecting all cables. Cables should not be connected or removed when the power is on. 9. For details on differences between the MCU and E7000PC, refer to section 2, Differences between the MCU and the Emulator, in Part III, Emulator Function Guide. 1-4 1.2 Environmental Conditions Observe the conditions listed in table 1-1 when using the E7000PC emulator. Table 1-1 Environmental Conditions Item Specifications Temperature Operating: +10 to +35C Storage: -10 to +50C Humidity Operating: 35 to 80% RH (no condensation) Storage: 35 to 80% RH (no condensation) Vibration Operating: 2.45 m/s2 max Storage: 4.9 m/s2 max Transportation: 14.7 m/s2 max AC input power Voltage: 100/200 VAC 10% Frequency: 50/60 Hz Power consumption: 200 VA Ambient gases Must be no corrosive gases 1-5 1.3 Components The E7000PC emulator consists of the emulator station and emulator pod. Check all the components after unpacking. 1.3.1 E7000PC Emulator Station Table 1-2 E7000PC Emulator Station Components Item Configuration Quantity Remarks Hardware E7000PC emulator station 1 Power supply, control board, and trace board Station-pod interface cables 2 50 cm AC power cable 1 Fuse 1 Spare (3 A) HS7000ESTP1H Description Notes 1 HS7000ESTP1HE E7000 PC HITACHI Documentation 1-6 1.3.2 E7000PC Emulator Pod Table 1-3 E7000PC Emulator Pod Components Item Configuration Quantity Remarks Hardware Emulator pod 1 Fitted with two boards External probe set 1 Signal input: 8 GND: 1 Trigger output: 1 Floppy disks 1 E7000 system program (cannot be used with E7000PC emulator) 1 E7000PC/IBM PC system program 1 HS3048EPD70HE Software E7000 E7000PC Documentation H8/3048-series, H8/3048F E7000 Emulator User's Manual 1.3.3 IBM PC Interface Board Table 1-4 shows the specifications of the interface board. Table 1-4 IBM PC Interface Board Item Model Name Specifications IBM PC interface board HS7000EII01H * AT-bus specifications * Interface cable 1-7 1.3.4 Options In addition to the emulator station and pod components, the options listed in table 1-4 are also available. Refer to the option manual for details on the optional components. Table 1-5 Optional Component Specifications Item Model Name Specifications 1-Mbyte emulation memory board HS7000EMS11H 1-Mbyte SRAM is used 4-Mbyte emulation memory board HS7000EMS12H 4-Mbyte SRAM is used QFP-100 user system interface cable HS3042ECH71H For H8/3002, H8/3042 series, H8/3048 series, and H8/3048F (FP-100B) Bus monitor interface board for E7000 HS7000EXR10H For connecting the E7000 bus monitor board E7000 bus monitor board HS7000EBR01H For installing the D/A converter 1-8 Section 2 Components 2.1 E7000PC Hardware Components As shown in figure 2-1, the E7000PC emulator consists of an emulator station (having a PC interface), an emulator pod, and an IBM PC interface board. Note: Optional LAN boards cannot be installed in the E7000PC. Optional 1-Mbyte or 4-Mbyte emulation memory board, or bus monitor interface board E7000 PC IBM PC interface board PC interface cable Station-pod interface cables HITACHI Emulator pod E7000PC emulator station Optional user system interface cable External probe User system Figure 2-1 E7000PC Emulator Hardware Components 2-1 2.1.1 E7000PC Emulator Station Components Front Panel: E7000 PC 2 POWER 1 HITACHI Figure 2-2 E7000PC Emulator Station Front Panel 1. Power lamp: Lights when the E7000PC power is on. 2. Station-pod interface cable connectors: For connecting the emulator pod to the emulator station. 2-2 Rear Panel: 4 POWER CRT 1 250V 3A 2 AC INPUT 3 5 TRACE 9 Figure 2-3 PC 8 7 AC100-120V/ AC200-240V 2A 50/60Hz 6 E7000PC Emulator Station Rear Panel 1. Power switch: Turning this switch to I (input) supplies power to the E7000PC (emulator station and pod). 2. Fuse box: Contains a 3-A 250 VAC fuse. 3. AC power connector: For an 100/200 VAC power supply. 4. Console connector: For future use. Marked CRT. 2-3 5. Personal computer connector: For connection to the IBM PC console. Marked PC. 6. Control board slot: For installing the control board. 7. Extension slot: For system extension. 8. Emulation memory/bus monitor interface board slot: For installing the optional emulation memory board or bus monitor interface board. 9. Trace board slot: For installing the trace board. 2-4 2.1.2 E7000PC Emulator Pod Components 2 1 s H S 3 0 4 8 E P D 7 0 H 4 5 (Top view) 3 7 6 (Bottom view) Figure 2-4 E7000PC Emulator Pod 1. External probes: Can be used for the following during realtime user system emulation -- Hardware break condition input -- Real-time trace input -- Multi-break detection 2. Trigger output pin: Outputs a low-level pulse in the following states: -- When a hardware break condition is satisfied (whether to break or not can be selected) -- When cycle reset mode is specified with the GO command and an RES signal is input to the MCU 2-5 -- When trigger output is specified with the TRACE_CONDITION command, and the set conditions are satisfied, this pin can be used as the trigger signal of the oscilloscope or the logic analyzer 3. Crystal oscillator installation socket: For installing the crystal oscillator which provides a clock to the MCU. 4. User system interface cable: For connection to the MCU socket on the user system, to enable the E7000PC to operate in place of the MCU. 5. Station-pod interface cables: For connecting the emulator station to the emulator pod. 6. User system interface cable connector: For connection of the user system. 7. External probe connector: For connection of the external probe. Note: When user system interface cable is connected, power supply voltage must be provided from the VCC pin on the user system interface cable to operate the E7000PC. Therefore, when using the E7000PC on its own, be sure to disconnect the user system interface cable. 2-6 2.2 E7000PC Software Components The E7000PC emulator's software components are illustrated in figure 2-5. The emulator pod contains two 3.5-inch floppy disks; the E7000PC emulator system disk has "E7000PC" written under "HITACHI" on its label. The system disk files are described in table 2-1. Table 2-1 Contents of E7000PC System Disk File Name Contents Description E7000.SYS E7000PC system program Controls the emulator pod and processes commands, such as emulation commands. Loaded into the E7000PC memory after the E7000PC system program is activated. H8POD348.SYS MCU control program Controls the MCU within the emulator pod. Loaded into the E7000PC memory after the E7000PC system program is activated. H8CNF348.SYS Configuration file Contains MCU operating mode and MAP information. Loaded with the E7000PC system program. LANCNF.SYS LAN configuration file Contains the host name and IP address information when the E7000PC is connected to a workstation via a LAN interface. DIAG.TM Diagnostic program Loaded into the emulator station memory for testing and maintenance. IPI. EXE H-series interface software Executes on an IBM PC to interface with the E7000PC. 2-7 E7000 PC E7000PC system program (Provided with the emulator pod) Loadable file types: * S-type files * HEX-type files * SYSROF-type files * Text files HITACHI H-series interface software (Provided with the emulator pod) IBM PC (IBM) C compiler Cross assembler Linkage editor Figure 2-5 E7000PC Emulator Software Components 2-8 2.3 System Configuration By installing an IBM PC interface board in the personal computer conforming to IBM PC AT-bus specifications, the E7000PC can be connected to the personal computer through the interface cable supplied with the IBM PC interface board. The system configuration is shown in figure 2-6. Install an IBM PC interface board in the personal computer E7000PC emulator PC IBM PC personal computer Figure 2-6 E7000PC Emulator System Configuration 2-9 Section 3 Preparation before Use 3.1 E7000PC Preparation Unpack the E7000PC and prepare it for use as follows: Reference Unpack the emulator Check the components against the component list Component list Install the optional emulation memory board, or bus monitor Each board's manual interface board Connect the emulator pod to Section 3.2.1 the emulator station Connect the external probe Section 3.2.2 Connect the user system interface cable Each user system interface cable manual Install the crystal oscillator Section 3.2.3 Connect the system ground Section 3.2.4 Set the IBM PC interface board switches Section 3.3.2 Install the IBM PC interface board Section 3.3.3 Connect the PC interface cable Section 3.3.4 Section 3.5 Power-on Figure 3-1 E7000PC Preparation Flow Chart 3-1 3.2 E7000PC Connection 3.2.1 Connecting Emulator Pod The emulator pod and the emulator station are packed separately. Use the following procedure to connect the emulator pod to the emulator station, or to disconnect it when moving the E7000PC: (1) Check that the E7000PC power is off by ensuring that the power lamp on the left side of the emulator station front panel is extinguished. (2) Remove the AC power cable for the emulator station from the outlet. (3) Connect station-pod interface cables P1 and P2 to station-pod interface connectors J1 and J2 on the right side of the emulator station, respectively. Insert the longer screw of each cable to the connector screw hole without a spacer, and the shorter screw to the hole with a spacer. Tighten the longer screw first until the shorter screw reaches the spacer, then alternately tighten the longer and shorter screws. Figure 3-2 shows how to connect the station-pod interface cables to the emulator station. Note: When connecting the cables, prevent the upper or lower side of the cables from lifting off the connector. Tighten the screws and push the cables gradually toward the connector. Station-pod interface connector J2 J2 Spacers J1 Station-pod interface connector J1 Emulator station right side Longer screws Station-pod interface cable P1 Station-pod interface cable P2 Figure 3-2 Connecting Station-Pod Interface Cables to Emulator Station 3-2 (4) Connect station-pod interface cables P1 and P2 to station-pod interface connectors J1 and J2, respectively, in the same way as connection to the emulator station. Tighten the screws in the same way as in step (3). See figure 3-3 for details. Pod Station-pod interface connector J1 J1 Station-pod interface connector J2 J2 Spacers Station-pod interface cable P1 Station-pod interface cable P2 Longer screws Figure 3-3 Connecting Station-Pod Interface Cables to Emulator Pod 3-3 3.2.2 External Probe Connector When an external probe is connected to the emulator pod, it enables external signal trace, break using an external signal, and multibreak detection. Figure 3-4 shows the external probe connection. External probe connector Cover External probe Bottom of emulator pod Figure 3-4 Connecting External Probe 1. Slide back the cover on the bottom of the emulator pod. 2. Insert the external probe into the external probe connector, making sure they are aligned correctly. For connecting a user system interface cable, refer to the user system interface cable manual. 3-4 3.2.3 Clock Selection Three types of clocks are supported; a crystal oscillator signal from the emulator pod, an external clock from the user system, and the E7000PC emulator internal clock. Each clock type is specified with the CLOCK command. X (crystal oscillator) U (user system clock) E7000PC emulator internal clock CLOCK command 13 (13 MHz) 18 (18 MHz) Crystal Oscillator: Using this function, a user program can be executed with user system operating frequency without connecting the user system. A crystal oscillator is not provided with the E7000PC. Use one with the same frequency as the user system (o clock). The frequency of the crystal oscillator used as the MCU input clock is 8 to 18 MHz. To use a frequency outside this range, supply an external clock from the user system. Install the crystal oscillator using the following procedure: 1. Check that the E7000PC power is turned off. 2. Install the crystal oscillator into the crystal oscillator socket on the side of the emulator pod (figure 3-5). 3. After turning on the E7000PC, specify X with the CLOCK command. Cover XTAL Bottom of emulator pod Figure 3-5 Installing Crystal Oscillator 3-5 User System Clock: Specify a user system clock using the following procedure. 1. Check that the E7000PC power is off. 2. Supply a TTL-level clock through the EXTAL pin at the end of the user system interface cable. 3. After turning on the E7000PC power, specify U with the CLOCK command. E7000PC Emulator Internal Clock: Specify 13 (13 MHz) or 18 (18 MHz) with the CLOCK command. Note: When the emulator system program is initiated, the emulator automatically selects the MCU clock source according to the following priority. 1. U (user system clock) when supplied from the user system. 2. X (crystal oscillator) when installed in the emulator pod. 3. 13-MHz E7000PC emulator internal clock. 3-6 3.2.4 Connecting System Ground The E7000PC's signal ground is connected to the user system's signal ground via the emulator pod. In the emulator station, the signal ground and the frame ground are connected (figure 3-6). At the user system, connect the frame ground only; do not connect the signal ground to the frame ground. If it is difficult to separate the signal ground from the 100-V frame ground, ground the user system at the same outlet as the E7000PC's power supply (figure 3-7). Signal line Emulator station Emulator pod Signal line User system Logic Power Signal ground Signal ground Frame ground Figure 3-6 Connecting System Ground E7000PC power cable User system power cable Outlet Ground AC power supply Figure 3-7 Connecting Frame Ground The user system must be connected to an appropriate ground so as to minimize noise, ground loops, and other adverse effects. Confirm that the ground pins of the emulator pod are firmly connected to the user system's ground. 3-7 3.3 System Connection This section describes how to connect the E7000PC to an IBM PC via an IBM PC interface board. 3.3.1 IBM PC Interface Board Specifications Table 3-1 IBM PC Interface Board Specifications Item Specification Target personal computer IBM PC conforming to an AT bus or compatible computer System bus AT bus Memory requirement 16 kbytes Memory allocation By switches Memory for the interface board can be allocated within the address range from H'A0000 to H'FFFFF at any 16-kbyte boundary. Interrupt One interrupt must be selected from IRQ03, IRQ05, IRQ11, and IRQ12; unnecessary, however, if not used by application software*2. Interrupt selection By switches I/O area No I/O area for this IBM PC interface board Note: In this manual, application software refers to software such as IBM PC interface software that uses the IBM PC interface board. 3-8 3.3.2 Setting the Switches on the IBM PC Interface Board Allocating the Memory Area: The IBM PC interface board uses 16 kbytes of memory on the IBM PC. This memory must be allocated to a memory area on the IBM PC using switches on the IBM PC interface board. Specifically, it can be allocated to any 16-kbyte block within the address range H'A0000 to H'FFFFF (figure 3-8). Note that the allocated memory area must not overlap memory already allocated to other boards. At shipment, the memory area of the IBM PC interface board is allocated to the address range from H'D0000 to H'D3FFF. H'A0000 H'A4000 H'A8000 H'AC000 H'B0000 H'B4000 H'B8000 H'BC000 H'C0000 H'C4000 H'C8000 H'CC000 H'D0000 At shipment H'D4000 H'D8000 H'DC000 H'E0000 H'E4000 H'E8000 H'EC000 H'F0000 H'F4000 H'F8000 H'FC000 H'FFFFF Figure 3-8 Memory Areas Allocatable for the IBM PC Interface Board 3-9 Selecting an Interrupt: One of four IBM PC interrupts can be selected by switches on the IBM PC interface board for application software that uses IBM PC interrupts. Make sure that application software for this board uses IBM PC interrupts before setting the switches. Available interrupts are listed in table 3-2. Select one interrupt level in table 3-2 which is not used for other boards on the IBM PC. IRQ11 is set at shipment. Table 3-2 Available Interrupts Interrupt Remarks IRQ11 At shipment IRQ12 IRQ03 IRQ05 Setting the Switches: Eight switches are provided on the IBM PC interface board to allocate memory and select an interrupt. Figure 3-9 shows how to set these switches. The switch select conditions are listed in tables 3-3 and 3-4. Switch 8 is reserved for future use and must be closed. IBM PC interface board DSW1 DSW1 1 2 3 4 5 6 7 8 OPEN O P E N O P E N (a) Open Figure 3-9 Switches on the IBM PC Interface Board 3-10 (b) Closed Table 3-3 Memory Allocation and Switch Settings Switch Settings IBM PC Address Range 1 2 3 4 5 H'A0000 to H'A3FFF Closed Closed Closed Open Closed H'A4000 to H'A7FFF Open Closed Closed Open Closed H'A8000 to H'ABFFF Closed Open Closed Open Closed H'AC000 to H'AFFFF Open Open Closed Open Closed H'B0000 to H'B3FFF Closed Closed Open Open Closed H'B4000 to H'B7FFF Open Closed Open Open Closed H'B8000 to H'BBFFF Closed Open Open Open Closed H'BC000 to H'BFFFF Open Open Open Open Closed H'C0000 to H'C3FFF Closed Closed Closed Closed Open H'C4000 to H'C7FFF Open Closed Closed Closed Open H'C8000 to H'CBFFF Closed Open Closed Closed Open H'CC000 to H'CFFFF Open Open Closed Closed Open H'D0000 to H'D3FFF Closed Closed Open Closed Open H'D4000 to H'D7FFF Open Closed Open Closed Open H'D8000 to H'DBFFF Closed Open Open Closed Open H'DC000 to H'DFFFF Open Open Open Closed Open H'E0000 to H'E3FFF Closed Closed Closed Open Open H'E4000 to H'E7FFF Open Closed Closed Open Open H'E8000 to H'EBFFF Closed Open Closed Open Open H'EC000 to H'EFFFF Open Open Closed Open Open H'F0000 to H'F3FFF Closed Closed Open Open Open H'F4000 to H'F7FFF Open Closed Open Open Open H'F8000 to H'FBFFF Closed Open Open Open Open H'FC000 to H'FFFFF Open Open Open Open Open Remarks At shipment Table 3-4 Interrupts and Switch Setting Interrupt Switch 6 Switch 7 Remarks IRQ11 Closed Closed At shipment IRQ12 Closed Open IRQ03 Open Closed IRQ05 Open Open Notes: 1. Set switches 6 and 7 closed (default at shipment) when interrupts are not used by application software that runs on the IBM PC interface board. 2. Switch 8 is reserved for future use and must be closed. 3-11 3.3.3 Installing the IBM PC Interface Board Open the IBM PC cover and install the IBM PC interface board into an expansion slot conforming to AT bus specifications. Gently push the IBM PC interface board into the connector and fasten the board with the IBM PC screw (figure 3-10). IBM PC screw PC interface cable IBM PC IBM PC interface board Slot conforming to AT-bus specifications Figure 3-10 Installing IBM PC Interface Board 3-12 3.3.4 Connecting the IBM PC Interface Board to the E7000PC Emulator Station To use the E7000PC emulator, connect the IBM PC interface board to the E7000PC emulator station via the supplied PC interface cable, as shown in figure 3-11. E7000PC emulator station (rear side) IBM PC IBM PC interface board CRT EML PC PC interface cable Figure 3-11 Connecting IBM PC Interface Board to E7000PC Emulator Station 3-13 3.4 System Software Installation 3.4.1 E7000PC System Disk The E7000PC system program must be installed in the IBM PC because the E7000PC does not have a floppy disk drive. Two system disks are provided with the H8/3048 emulator pod. Use the E7000PC system disk labelled as E7000PC under the HITACHI label; the one labeled as E7000 is for the E7000 and cannot be used for the E7000PC (figure 3-12). H8/3048 E7000PC SYSTEM H8/3048 E7000 SYSTEM 1. SYSTEM (HS3048EPD70SF) Vn.m 1. SYSTEM (HS3048EPD70SF) Vn.m 2. PC I/F 2. DIAGNOSTIC TEST (HS7000EII01SF) 3. DIAGNOSTIC TEST XX.XX.XX Vn.m Vn.m Vn.m HITACHI XX.XX.XX E7000PC HITACHI E7000 (2) E7000 system disk (1) E7000PC system disk Figure 3-12 E70000PC System Disk The E7000PC system disk is formatted as a 1.44-Mbyte disk on the IBM PC, and includes the following five files: * * * * * E7000.SYS H8POD348.SYS H8CNF348.SYS DIAG.TM IPI.EXE (IBM PC interface software) These files must be installed on the IBM PC. To use the E7000PC, interface software must be running on the IBM PC. IBM PC interface software is in the E7000PC system disk supplied with the emulator pod. 3-14 3.4.2 Installation Copying E7000PC System Program: Copy all files in the E7000PC system disk to the IBM PC. Specify the copy destination directory in an environment variable when using the interface software*1. Setting Environment Variable: Before using the interface software, specify the interface software memory address in an environment variable. The most convenient way to do this is to add the following command to the file AUTOEXEC.BAT. SET E7000SYS = [<directory name>] [,[<termination code>] ,[<board address]] (a) (b) (c) (d) (a) The environment variable used by this interface software. The environment variable at default is E7000SYS*2. Input it using upper-case letters. (b) To connect Hitachi's E7000PC emulator using this interface software, input the name of the directory on which the E7000PC system program file exists. Do not input a back slash after the last directory name. (c) Input a termination code for this interface software in hexadecimal. When omitted, the default value is H'1B (ESC). (d) Input the eight high-order bits (in hexadecimal) of the segment address of the memory where the interface board is installed. When the board address is omitted, the memory where the interface board is installed will be searched from the DIP switch settings shown in table 3-3. Example: Input the following when the E7000PC system program file is in the directory C:\E7000\H8300H, the termination code is 04 ((CTRL) + D), and the interface board is installed at the address D8000:0000: C>SET E7000SYS=C:\E7000\H8300H, 04, D8 (RET) Copying Interface Software: Copy the interface software (IPI.EXE) and specify the path name for the directory. Notes: 1. The E7000PC system disk contains this interface software (IPI.EXE). However, the interface software can be copied to another directory. 2. It is also possible to specify an environment variable with a name other than E7000SYS when starting up the IBM PC interface software (IPI.EXE). Example: C:\>SET E7000SYS=C:\E7000,1B,D0 ..........Specify the default environment variable C:\>SET E7000=C:\E7000\H8300H,1B,D4 ...Specify E7000 as the environment variable C:\>IPI E7000 .................................................Initiate the IPI (with E7000 as the environment variable) C:\>IPI ............................................................Initiate the IPI (with the default environment variable) 3-15 3.5 Power-On Procedure for the E7000PC Figure 3-13 shows the E7000PC power-on procedure. 1. Initiate the interface software on the IBM PC. 2. Power on the emulator station. Internal system test is executed. 3. Console messages are displayed. Test result OK? No Yes 4. E7000PC monitor command input wait state 4. Error message is displayed. Refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. Figure 3-13 Power-On Procedure for the E7000PC For initiating the interface software, refer to section 3.7.1, Initiating Interface Software. For operations after power-on, refer to section 3.6.1, E7000PC Monitor Initiation, and section 3.6.2, E7000PC System Program Initiation. 3-16 3.6 E7000PC Monitor Commands 3.6.1 E7000PC Monitor Initiation When the E7000PC is turned on and the interface software is activated, the following messages are displayed. Console Messages: E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. (a) Licensed Material of Hitachi, Ltd. TESTING RAM 0123 (b) START E7000 S:START E7000 R: RELOAD & START E7000 L: DISPLAY LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/L/T) ? _ (c) Descriptions: (a) E7000PC monitor start message. Vn.m is the E7000PC monitor's version number. If this message is not displayed, determine what is wrong by reading section 5, Troubleshooting in Part III, Emulator Function Guide. (b) The E7000PC internal system is being tested. A number from 0 to 3 is displayed when each of the four MCU internal RAM blocks has been tested. If an error occurs, the following messages are displayed: *** RAM ERROR ADDR = xxxxxxxx W-DATA = xxxxxxxx R-DATA = xxxxxxxx *** xxxxx REGISTER ERROR W-DATA = xxxx R-DATA = xxxx If these messages are displayed, refer to section 5, Troubleshooting in Part III, Emulator Function Guide. (c) List of E7000PC monitor commands. Enter the required command at the cursor position. These commands are described in table 3-5. When an L command is specified, the E7000PC will prompt for another command after execution is completed. After the system program has been loaded by an S or R command, the QUIT command ends the system program execution and returns the E7000PC monitor to command input wait state. 3-17 Table 3-5 E7000PC Monitor Commands Command Function Reference Section S E7000PC system program initiation Section 3.6.2, E7000PC Initiates the system program. When the system System Program Initiation program has not been loaded, this command loads it from the floppy disk and then initiates the system. R E7000PC system program reload Loads and initiates a different system program from the loaded system program. Section 3.6.2, E7000PC System Program Initiation L IP address display Displays the E7000PC IP address. This command is reserved for future use. T Diagnostic Program Initiation Attached diagnostic Loads and initiates the diagnostic program in the program manual E7000 system floppy disk. If a problem occurs, use this command to initiate the diagnostic program. 3-18 3.6.2 E7000PC System Program Initiation The E7000PC system program must be loaded and initiated before initiating the E7000PC. If S or R is entered, followed by (RET), when the E7000PC is in monitor command input wait state, the E7000PC system program is loaded from the IBM PC and initiated. Table 3-6 E7000PC System Program Initiation Commands Command Description S Loads and initiates the system program from the IBM PC. If the E7000PC system program is already loaded, the system program is initiated immediately.* R Reloads and initiates the E7000PC system program. Note: This situation occurs when the system program is initiated and then terminated with the QUIT command. However, when emulator monitor command T (diagnostic program initiation) has been executed or when the system program has been forcibly terminated by a clock error, the system program is reloaded. 3-19 Display at E7000PC System Program Initiation START E7000 S: START E7000 R: RELOAD & START E7000 L: DISPLAY LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/L/T) ? S (RET) R { ** (a) } E7000 SYSTEM LOADING ** (b) H8/xxxx E7000 (HSxxxxEPDxxSF) Vn.m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. (c) CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xxxx MCU NAME=H8/xxxx MODE=x PIN=xxx (MD x-x=x) REMAINS EMULATION MEMORY S=xxxxx/xxxxxx (d) (e) (f) (g) (h) (i) (j) (k) (l) WARM OR COLD START file name: WARM START return : COLD START <file name> (RET) (file name/return) ? (RET) : (m) { } 3-20 (n) Description (a) E7000PC monitor command input request message. Enter S. Enter R if loading another E7000PC system program. (b) The E7000PC system program is being loaded from the IBM PC. (c) Start message of the E7000PC system program. Vn.m is the version number. (d) Configuration file is being loaded from the IBM PC. (e) IP address file for the LAN is being loaded from the IBM PC. (Note that the LAN cannot be used by the E7000PC.) (f) Emulator station hardware test start message. If there is an error in the emulator station, an error message is displayed. For details, refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. (g) The program to be executed in the emulator pod is being loaded from the IBM PC. (h) Emulator pod test start message. If there is an error in the emulator pod, an error message is displayed. For details, refer to section 5, Troubleshooting, in Part III, Emulator Function Guide. (i) An RES signal has been input to the MCU. (j) Specified clock. If the user system is ready, the user system's clock (U) is used. If not, but the crystal oscillator (X) is ready, the crystal oscillator is used. If neither the user system clock or the oscillator clock is ready, the 13-MHz E7000PC internal clock is used. (k) MCU type, MCU operating mode, number of pins, and user system mode selection pin state. They are previously set with the MODE command (saved in configuration file). For details, refer to section 7.2.28, MODE, in Part III, Emulator Function Guide. (l) Remaining emulation memory size (m) Specify either WARM START*1 or COLD START*2 as follows: WARM START: Specify the file name containing recovery information. COLD START: Press the (RET) key. (n) E7000PC system program prompt. An E7000PC system program command can now be entered. 3-21 Notes: 1. WARM START recovers the information saved in a file when the E7000PC system program was terminated by the QUIT command. (For details, refer to section 7.2.33 QUIT, in Part III, Emulator Function Guide.) The recovery information is listed below. * * * * * * PC breakpoints Hardware break conditions, trace stop conditions, and trace acquisition conditions Memory map information Performance analysis information Configuration information Symbol information 2. COLD START initializes the above emulation information. 3-22 3.7 Interface Software Operations 3.7.1 Initiating Interface Software The IBM PC interface software is initiated by inputting the IPI command. An example is shown below. C>IPI<RET> (a) H-SERIES PC INTERFACE (HS7000EII01SF) Ver n.m Copyright(c) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. (b) INTERFACE BOARD ADDRESS=yyyy:zzzz,TERMINATE CODE=tt (c) (E7000PC commands can be entered here) (d) <Termination key> (e) C> Description: (a) Initiate the interface software. (b) The interface software start-up message is displayed. Ver n.m represents the interface software version number. (c) Memory address where the interface board is allocated. yyyy indicates the segment, zzzz indicates the offset, and tt indicates the interface software termination code. (d) The E7000PC operations can start here. When the E7000PC power is turned on, the E7000PC will enter the state described in section 3.6.1, E7000PC Monitor Initiation. (e) Enter the termination key to terminate the interface software and return the E7000PC to the IBM PC command input wait state. For more details on the termination key, refer to section 3.4.2, Installation. 3-23 3.7.2 Initiating from Windows*1 To initiate the interface software under Windows, initiate from MS-DOS*2 prompt in the main group of Window's program manager. Note that multiple copies of the software cannot be initiated. If virtual EMS driver (EMM386.EXE) is installed with the CONFIG.SYS file, the CONFIG.SYS file must be modified. Set the memory address range to be accessed by the IBM PC interface software outside the EMS driver management range. The following example sets the memory address range of IBM PC interface software from D000:0000 to D3FF:0000 outside the EMS driver management range. DEVICE = C:\WINDOWS\EMM386.EXE M9 /X = D000-D3FF Notes: 1. Windows is a trademark of Microsoft Corporation. 2. MS-DOS is a registered trademark of Microsoft Corporation. 3.7.3 Emulation Support Function This interface software provides two emulation support functions: automatic command input from IBM PC files, and logging acquisition of the console output to IBM PC files or a printer. These functions can only be invoked when the E7000PC is in the command input wait state, not in the data input wait state. Examples of the command input wait state and the data input wait state are shown below. * Command input wait state : # * The E7000PC is in the command input wait state when it provides either of these prompts. Data input wait state (MEMORY command) :MEMORY 100(RET) 00000100 00 ? 11(RET) 00000101 00 ? Input data in the data input wait state Data input wait state 3-24 Automatic Command Input: (1) To specify a command file (input file), input < and a file name without any space between the two as shown below. Example: : <FILENAME(RET) (2) Commands from the specified command file will be automatically input and sent to the E7000PC. When the command file is specified as shown in the example below, the MAP, MEMORY, and CLOCK commands from the specified command file will be automatically executed. When additional data is required within a command as in the MEMORY command, this data will also be automatically input. Example: File contents: MAP 0 1FFFF;U MEMORY 100 30 . CLOCK Execution results: :<FILENAME(RET) :MAP 0 1FFFF;U REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx :MEMORY 100 00000100 00 ? 30 00000101 00 ?. :CLOCK CLOCK=USER : (Next command input wait state) (3) Commands will be automatically input from the command file until the end of the file is reached or (CTRL) + C keys are input. Pressing (CTRL) + C keys forcibly terminates command execution and displays the following message, asking whether or not the automatic command input should be continued. INTFC ERROR - STOP COMMAND CHAIN ? (Y/N) : (a) (a): Input Y to terminate or N to continue automatic command input. 3-25 (4) Logging acquisition can be specified from the command file. For details, refer to the description on logging in this section. (5) If the interface software displays the following confirmation message during command execution, it will only accept a reply from the keyboard. INTFC ERROR - FILE ALREADY EXISTS OVERWRITE ? (Y/N) : (a) (a): Input Y to overwrite the existing file or N to terminate the transfer. (6) Command files cannot be nested. Logging: (1) To specify logging, the E7000PC must be in the command input wait state. Input > followed by a file name without any space between the two. Examples of starting and quitting logging are shown below. Examples: : >FILENAME(RET) To overwrite a file : >>FILENAME(RET) To add to a file : >-(RET) To quit logging (2) If logging acquisition is specified with this command, the subsequent command input, execution results, and error messages will be displayed on the console and output to the file with the specified file name. If PRN is specified for the file name, the output will be sent to the printer. (3) The following message will be displayed if you attempt to overwrite an existing file. INTFC ERROR - FILE ALREADY EXISTS OVERWRITE ? (Y/N) : (a) (a): Input Y to overwrite the file or N to quit. (4) The following messages will not be logged. -- The program counter during GO command execution -- Addresses during loading, saving, and verifying 3-26 3.7.4 Notes (1) The MS-DOS may display an error message during file transfer. When the error message is displayed before file transfer starts, such as when no floppy disk has been inserted to the specified drive, when an access to an unformatted floppy disk is specified, or when writing on a write-protected floppy disk is specified, remove the cause of the error and then enter R to recover. When the error message is displayed during file transfer, file transfer may not be completed successfully even after recovery from the error (R) is specified. Entering A to terminate the error processing terminates the interface software. (2) Pressing the (BREAK), (STOP), or (CTRL) +C keys during file transfer forcibly terminates the file transfer. Pressing the termination key during file transfer has no meaning. (3) If the save operation results in an error, the interface software displays the received data and waits for the E7000PC command input. (4) When a file is written to the IBM PC disk, it is first created as a temporary file with file type $$$, and will only be renamed with the specified file type when it is closed normally. At this stage, the existing file, if any, will be erased. If a forced termination occurs while writing the file, the temporary file will be erased, and the existing file will be left behind. (5) When the E7000PC is initiated before the interface software, the message issued by the E7000PC before the interface software initiation cannot be displayed. 3-27 Section 4 Operating Examples Section 4.1, Basic Examples, and section 4.2, Application Examples, include explanations based on the following user program. ADDR 000100 000106 000108 00010A 00010C 00010E 000110 000112 000116 CODE 7A0700FF FF0E F800 F900 8802 8901 A90A 46F8 6A881000 40FE LABEL MNEMONIC MOV.L OPERAND #00FFFF0E:32,ER7 MOV.B MOV.B ADD.B ADD.B CMP.B BNE MOV.B BRA #00:8,R0L #00:8,R1L #02:8,R0L #01:8,R1L #0A:8,R1L 00010A:8 R0L,@1000:16 000116:8 These examples assume that the emulator station is connected to the host system (IBM PC) via the PC interface, that the E7000PC system program has been installed in the host system, and that the user program is downloaded from the host system to the E7000PC. Therefore, store the program in the host system before initiating the E7000PC. Initiate the E7000PC by the following procedure: Operations Console Message 1. C> IPI (RET) Input the IPI command to the IBM PC. 4-1 2. Turn on the power on the E7000PC emulator station. The console displays the message shown on the right when the PC interface program operates. H-SERIES PC INTERFACE (HS7000EII01SF) Ver n. m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. INTERFACE BOARD ADDRESS=yyyy:zzzz, TERMINATE CODE=tt E7000 MONITOR Vn. m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. TESTING RAM 0123 START E7000 S : START E7000 R : RELOAD & START E7000 L : DISPLAY LAN PARAMETER T : START DIAGNOSTIC TEST 3. Enter S and (RET) to start up the E7000PC system. (S/R/L/T) ? S (RET) 4-2 4.1 Basic Examples 4.1.1 Preparing for Connection of IBM PC Before connecting the host system, specify the host name and the IP address by the following procedure: Operations Console Message 1. C>IPI (RET) To start up the PC interface software, enter the IPI command at the IBM PC. The console displays the message shown on the right and the E7000PC enters the monitor command input wait state. H-SERIES PC INTERFACE (HS7000EII01SF) Ver n. m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. INTERFACE BOARD ADDRESS=yyyy:zzzz, TERMINATE CODE=tt E7000 MONITOR Vn. m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. TESTING RAM 0123 START E7000 S : START E7000 R : RELOAD & START E7000 L : DISPLAY LAN PARAMETER T : START DIAGNOSTIC TEST 2. Enter S (RET) to re-initiate the system. (S/R/L/T) ? S (RET) ** E7000 SYSTEM LOADING ** H8/xxxx E7000 (HSxxxxEPDxxSF) Vn. m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz 4-3 MCU NAME = H8/xxxx MODE=x PIN=xxx (MD x-x=x) REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx WARM OR COLD START file name: WARM START return 3. Enter (RET). : COLD START (file name/return) ? (RET) :_ 4-4 4.1.2 Specifying the MCU Operating Mode Specify the E7000PC operating mode and the MCU operating mode by the following procedure: Operations Console Message 1. Enter MODE;C (RET) to specify the E7000 operating mode. :MODE;C (RET) 2. The console displays the message. MCU NAME (1:H8/3048,2:H8/3047,3:H8/3044,4:H8/3048F) ? _ 3 Enter 1 (RET) to select the H8/3048. MCU NAME (1:H8/3048,2:H8/3047,3:H8/3044,4:H8/3048F) ? 1 (RET) 4 5. Enter 3 (RET) to select MCU operating mode 3. OPERATION MODE ? OPERATION MODE ? 3 (RET) After the above specification has been completed, the console asks if the mode settings should be stored in the configuration file. To store the mode settings, enter Y (RET). After that, the E7000 operates in the mode specified above whenever initiated with this system disk. To correct a mis-typed mode number, return to step 1 above before entering Y (RET) and repeat the procedure. Remove the write protect from the system floppy disk before storing the mode settings in the configuration file. CONFIGURATION WRITE OK ? (Y/N) ? _ CONFIGURATION WRITE OK ? (Y/N ) ? Y(RET) START E7000 S : START E7000 6. After the mode settings have been stored in the configuration file, the E7000 system program automatically terminates. R : RELOAD & START E7000 L : DISPLAY LAN PARAMETER T : START DIAGNOSTIC TEST (S/R/L/T) ? _ 7. Enter S (RET) to re-initiate the system program. (S/R/L/T) ? S (RET) WARM OR COLD START file name: WARM START return : COLD START (file name/return) ? _ 8. Enter (RET). (file name/return) ? (RET) 4-5 4.1.3 Allocating Standard Emulation Memory and Specifying Attributes In order to load the user program to memory, allocate the standard emulation memory in the pods by the following procedure: Operations Console Message :MAP 0 1FFFF;S (RET) Enter MAP 0 1FFFF;S (RET) to allocate the standard emulation memory to addresses H'0 to H'1FFFF. The console displays the message shown on the right, which indicates that the memory allocation has been completed. Enter MAP (RET) and the console displays the attributes of all the memory areas. REMAINS EMULATION MEMORY S=60000/E=000000 :MAP (RET) 000000 - 01FFFF;S 020000 - FFFFFF;U INTERNAL RAM = FFEF10 - FFFF0F INTERNAL I/O = FFFF1C - FFFFFF REMAINS EMULATION MEMORY S=60000/E=000000 4-6 4.1.4 Executing Program Execute the loaded program by the following procedure: Operations Console Message 1. : .SP (RET) Enter .SP (RET) then FFFF0E (RET) as the SP value to set the stack pointer (SP) to H'FFFF0E. The console then asks for the program counter (PC) value. Enter 100 (RET) as the program counter value. The console then asks for the condition code register (CCR) value. In this example, the condition code register need not be set or changed, therefore, enter . (RET) to exit this interactive mode. ER7(SP) =00FFFF1A ? _ ER7(SP) =00FFFF1A ? FFFF0E (RET) PC = FFFFFF ? _ PC = FFFFFF ? 100 (RET) CCR = 80:I****** ? _ CCR = 80:I****** ? .(RET) :_ Note: In interactive mode, entering only (RET) makes no change to the currently displayed item, and the next item is displayed. In the above example, entering only (RET) to the condition code register prompt can complete the register modification procedure. The register value can also be directly input without using the interactive mode. For example, to set the stack pointer value directly, enter .SP FFFF0E (RET). 2. 3. Enter GO (RET) to execute the program from the address pointed by the PC. While the program is executed, the console displays the current program counter value (shown as xxxxxx on the right). :GO (RET) Enter (BREAK) key or (CTRL) + C keys to terminate program execution. The console displays the contents of the program counter, the condition code register, and the general registers ER0 to ER7 at termination. RUN - TIME shows the duration of program execution from the GO command execution to (BREAK) or (CTRL) + C key input. BREAK KEY shows that the execution has been terminated because (BREAK) or (CTRL) + C was entered. (BREAK) ** PC = xxxxxx PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:01S:049705US BREAK KEY : _ 4-7 4.1.5 PC Break Program execution can be stopped at a particular address by setting a breakpoint as follows: Operations Console Message 1. Enter BREAK 10C (RET) to terminate program execution when the instruction at address H'10C in the program is executed. :BREAK 10C (RET) 2. Restart program execution from address H'100. This can be done in two ways: one is to enter the start address directly, and the other is to first set the program counter to H'100, then enter GO, as described in section 4.1.4, Executing Program. :GO 100 (RET) The program execution terminates when the instruction at address H'10C is executed. The console displays the data shown on the right. The BREAK POINT 00010C shows that the program execution was terminated because of a PC breakpoint at H'10C. PC = 00010E 3. ** PC = xxxxxx 4-8 CCR=80:I******* ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000014US BREAK POINT 00010C : _ 4.1.6 Single-Step Execution A single instruction can be executed using the single-step function by the following procedure: Operations Console Message 1. The program counter points to the next address to be executed when the program execution terminates in the example of section 4.1.5, PC Break. Here, entering STEP (RET) executes only one instruction, and the console displays the information as shown on the right. 00010E CMP.B #0A:8,R1L shows the executed address and mnemonic code, and STEP NORMAL END shows that the single-step execution has terminated. :STEP (RET) To repeat single-step execution, enter only (RET). This can be repeated until another command is executed. :(RET) 2. PC = 000110 CCR=A9:I*H*N**C ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E 00010E CMP.B #0A:8,R1L STEP NORMAL END :_ PC = 00010A CCR=A9:I*H*N**C ER0 - ER3 00000002 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E 000110 BNE STEP NORMAL END :_ 4-9 00010A:8 4.1.7 Setting Hardware Break Conditions Various hardware break conditions can be specified by the following procedure: Operations Console Message 1. Enter BREAK - (RET) to cancel the breakpoint set in the example in section 4.1.5, PC Break. :BREAK - (RET) 2. To confirm the cancellation, execute the BREAK command (enter BREAK (RET)). *** 45: NOT FOUND shows that no PC breakpoint is set. :BREAK (RET) 3. To specify that program execution should terminate when data is written to address H'1000, enter BREAK_CONDITION1 A = 1000 W (RET). :BREAK_CONDITION1 A = 1000 W (RET) 4. Enter GO 100 (RET) to start executing the program from address H'100. When the break condition is satisfied, the console displays the information shown on the right. BREAK CONDITION1 shows that the program execution has terminated because the break condition was satisfied. :GO 100 (RET) *** 45: NOT FOUND ** PC = xxxxxx PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000093US BREAK CONDITION1 :_ 4-10 4.1.8 Displaying Trace Information Trace information acquired during program execution can be displayed by the following procedure: Operations Console Message 1. :TRACE (RET) Enter TRACE (RET) to see the trace information. The console will display the instruction mnemonic information. IP ADDR LABEL 000100 MOV:L #00FFFF0E:32,ER7 *-D'00043 000106 MOV.B #00:8,R0L *-D'00042 000108 MOV.B #00:8,R1L *-D'00041 00010A ADD.B #02:8,R0L 00010C ADD.B #01:8,R1L : To display the trace information in buscycle units, enter TRACE;B (RET). BP * AB DB MA R/W 000100 : : :TRACE;B (RET) ST IRQ MOV.L NMI RES RA PROB VCC CLK #00FFFF0E:32,ER7 -D'00123 000100 79 EXT R PRG 111111 1 1 11 11111111 1 08 -D'00122 000101 07 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00121 000102 79 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00120 000103 07 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00119 000104 FF EXT R PRG 111111 1 1 11 11111111 1 06 -D'00118 000105 FE EXT R PRG 111111 1 1 11 11111111 1 06 -D'00117 000106 F8 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00116 000107 00 EXT R PRG 111111 1 1 11 11111111 1 06 * 000106 MOV.B : 3. OPERAND *-D'00044 *-D'00040 2. MNEMONIC To temporarily stop the trace information display, enter (CTRL)+S. To continue the display, enter (CTRL)+Q. (CTRL)+S and (CTRL)+Q are also effective on other information display. #00:8,R0L : : (CTRL)+S (CTRL)+Q 4-11 4.2 Application Examples 4.2.1 Break with Pass Count Condition The pass count condition can be set to a breakpoint by the following procedure: Operations Console Message 1. Enter BREAK 10A 5 (RET) to terminate program execution when address 10A is passed five times. :BREAK 10A 5 (RET) 2. To start execution from address H'100, enter GO 100 (RET). :GO 100 (RET) When execution terminates after address H'10A is passed five times, the console displays the data shown on the right. PC = 00010C 3. ** PC = xxxxxx CCR=80:I******* ER0 - ER3 0000000A 00000004 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000058US BREAK POINT 0010A :_ :BREAK (RET) 4. Entering BREAK (RET) displays (a) the breakpoint address, (b) the specified count, and (c) the pass count as shown on the right. The pass count is cleared when the GO command is entered again. ADDRESS CNT PASS 00010A 0005 0005 (a) (b) (c) 4-12 SYMBOL 4.2.2 Conditional Trace The following procedure can be used to limit the acquisition of trace information during program execution. Operations Console Message 1. To cancel the breakpoint set in the example of section 4.2.1, Break with Pass Count Condition, enter BREAK - (RET). :BREAK - (RET) 2. Enter TRACE_CONDITION A=100:106;R (RET) to get trace information only while the program counter is between addresses H'100 and H'106. :TRACE_CONDITION A= 100:106;R (RET) 3. Enter GO 100 (RET) to start executing the program, then (BREAK) key or (CTRL) + C keys to terminate the execution. :GO 100 (RET) ** PC = xxxxxx PC = 000106 (BREAK) CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:01S:049705US BREAK KEY :_ 4. Enter TRACE (RET) to display the trace information acquired under the specified condition. :TRACE (RET) IP ADDR * D'***** 000100 * D'***** 000106 LABEL : 4-13 MNEMONIC OPERAND MOV.L #00FFFF0E:32,ER7 MOV.B #00:8,R0L 4.2.3 Parallel Mode During program execution in parallel mode, the memory contents can be displayed or modified by the following procedure: Operations Console Message 1. :GO 100 (RET) After executing the GO command, enter (RET) to move to parallel mode. ** PC = xxxxxx (RET) #_ 2. Enter DUMP 1000 100F (RET) to display the memory contents from H'1000 to H'100F. <ADDR> #DUMP 1000 100F (RET) <D A T A> <ASCII CODE> 001000 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3. Enter MEMORY 117 EE (RET) to modify the contents of memory address H'117 into EE. #MEMORY 117 EE (RET) 4. To exit from parallel mode, enter END (RET). #END (RET) ". . . . . . . . . . . . . . . ." ** PC = xxxxxx (BREAK) 5. To terminate program execution, enter (BREAK) key or (CTRL) + C keys. PC = 000116 CCR=80:I******* ER0 - ER3 00000014 0000000A 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:07M:25S:441007US BREAK KEY :_ 6. Enter DISASSEMBLE 100 117 (RET) to confirm that the program has been changed by memory modification in parallel mode. : DISASSEMBLE 100 117 (RET) 4-14 ADDR CODE 000100 7A0700FF LABEL MNEMONIC OPERAND MOV.L #00FFFF0E:32,ER7 #00:8,R0L FF0E 000106 F800 MOV.B 000108 F900 MOV.B #00:8,R1L 00010A 8802 ADD.B #02:8,R0L 00010C 8901 ADD.B #01:8,R1L 00010E A90A CMP.B #0A:8,R1L 000110 46F8 BNE 00010A:8 000112 6A881000 MOV.B R0L,@1000:16 000116 40EE BRA 000106:8 4.2.4 Searching Trace Information The TRACE_SEARCH command can be used to search for a particular part of the acquired trace information. Console Message Operations Enter TRACE_SEARCH A=116 (RET), and the console will only display those parts of the trace information in which the address bus value is H'116. BP AB :TRACE_SEARCH A=116(RET) DB MA R/W ST IRQ NMI RES RA PROB VCC CLK -D'04077 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 -D'03964 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 -D'03851 000116 40 EXT R PRG 111111 1 1 11 11111111 1 06 : : : : : : 4-15 4.2.5 Sequential PC Break A break can be generated when specified addresses are passed in a specified order, using the BREAK_SEQUENCE command as follows: Operations Console Message 1. :BREAK_SEQUENCE 110 10A (RET) Enter BREAK_SEQUENCE 110 10A (RET), which terminates program execution when the instructions at addresses H'110 and H'10A are executed consecutively in that order, as shown in figure 4-1. ADDR CODE LABEL 000100 7A0700FF FF0E 000106 F800 000108 F900 00010A 8802 00010C 8901 00010E A90A 000110 46F8 000112 6A881000 000116 40EE MNEMONIC MOV.L Program execution flow OPERAND #00FFFF0E:32,ER7 MOV.B MOV.B ADD.B ADD.B CMP.B BNE MOV.B BRA #00:8,R0L #00:8,R1L #02:8,R0L #01:8,R1L #0A:8,R1L 00010A:8 R0L,@1000:16 000106:8 Figure 4-1 Program Execution Flow 2. Enter GO 100 (RET) to execute the program. When the specified condition is satisfied, execution terminates, and the console displays the data shown on the right. The BREAK SEQUENCE shows that execution has terminated because the condition specified in the BREAK_SEQUENCE command has been satisfied. :GO 100 (RET) ** PC = xxxxxx PC = 00010C CCR=80:I******* ER0 - ER3 00000004 00000001 00000000 00000000 ER4 - ER7 00000000 00000000 00000000 00FFFF0E RUN - TIME = D'0000H:00M:00S:000028US BREAK SEQUENCE :_ 4-16 3. Enter TRACE (RET) to confirm the executed instructions. :TRACE (RET) MNEMONIC OPERAND *-D'00007 IP ADDR 000100 MOV.L #00FFFF0E:32,ER7 *-D'00006 000106 MOV.B #00:8,R0L *-D'00005 000108 MOV.B #00:8,R1L *-D'00004 00010A ADD.B #02:8,R0L *-D'00003 00010C ADD.B #01:8,R1L *-D'00002 00010E CMP.B #0A:8,R1L *-D'00001 000110 BNE 00010A:8 * D'00000 00010A ADD.B #02:8,R0L :_ 4-17 LABEL Part III Emulator Function Guide Section 1 Emulator Functions 1.1 Overview This system is a hardware and software support tool for the development of systems incorporating H8/300H-series microcomputer, the H8/3048 series and H8/3048F. In addition to a high-speed CPU, the H8/3048 series contains internal ROM, internal RAM, timers, serial communication interface (one channel having an extended function for smart card interface), a refresh controller, DMAC, I/O ports, and A/D and D/A converters on a single chip. The H8/3048F has the same functions as the H8/3048 series except that it has flash memory instead of the internal ROM. Table 1-1 shows the differences between the H8/3048 series and H8/3048F functions. Table 1-1 Differences between the H8/3048 Series and H8/3048F Functions H8/3048 Series Function H8/3048 H8/3047 H8/3044 H8/3048F Maximum address space 16 MB 16 MB 16 MB 16 MB Internal ROM 128 kB 96 kB 32 kB -- Internal flash memory -- -- -- 128 kB Internal RAM 4 kB 4 kB 2 kB 4 kB 16-bit integrated timer unit Contains Contains Contains Contains Programmable timing pattern controller Contains Contains Contains Contains Watchdog timer 1 ch 1 ch 1 ch 1 ch Refresh controller 1 ch 1 ch 1 ch 1 ch Serial communication interface (extended function for smart card interface) 2 ch (1 ch) 2 ch (1 ch) 2 ch (1 ch) 2 ch (1 ch) DMAC 4 ch 4 ch 4 ch 4 ch A/D converters 10 bits x 8 ch 10 bits x 8 ch 10 bits x 8 ch 10 bits x 8 ch D/A converters 8 bits x 2 ch 8 bits x 2 ch 8 bits x 2 ch 8 bits x 2 ch Interrupt controllers External interrupts Internal interrupt sources 7 30 7 30 7 30 7 30 Pins 100 100 100 100 1-1 The emulator operates in just the same way as the MCU on the user system and enables realtime emulation of the user system with functions for efficiently debugging hardware and software. The emulator consists of a station, an emulator pod, and a user system interface cable. The descriptions in this manual apply to all H8/3048-series and H8/3048F MCUs unless otherwise specified. 1.2 Specification The main features of the emulator are its emulation functions, its floppy disk utility functions, and its host system interface functions, as listed in tables 1-2 to 1-4. Table 1-2 Emulation Functions Command Type Command Realtime emulation GO Break condition setting Function Reference Section Performs realtime emulation in the following cases. The operating frequency is 18 MHz at max. * Executes until a hardware or PC break condition is satisfied, or until the (CTRL) + C keys or (BREAK) key is pressed. * Cycle-reset mode: Executes while the RES signal is sent to the MCU at fixed intervals. (Effective for waveform measurement immediately after a reset) * Measures the execution time during a specified range. * Parallel mode: Displays trace data and modifies memory contents during emulation. 7.2.20 EXECUTION_ MODE * Specifies execution mode. 7.2.18 BREAK_ CONDITION 1,2,3,4 Sets hardware break conditions * Normal break: Breaks when the following condition is satisfied (up to four points): -- Address bus and data bus value -- Read/write condition -- External probe value (eight probes) -- External interrupt condition -- NOT condition -- Delay count -- Number of times a condition is satisfied * Specification of the satisfaction sequence up to four points 7.2.6 1-2 Table 1-2 Emulation Functions (cont) Reference Section Command Type Command Function Break condition setting (cont) BREAK Sets PC break conditions. 7.2.5 * Normal break: Sets breakpoints in memory including programs in the ROM area (255 points max). * Sets pass count. BREAK_ SEQUENCE * Sequential PC break up to four points 7.2.7 TRACE * Displays executed instruction mnemonic. * Displays the following data for each bus cycle: -- Instruction mnemonic -- Address and data bus value -- Access area and status -- MCU I/O control signals -- External probe value (eight probes) -- Clock count 7.2.45 TRACE_ CONDITION Sets trace condition. * Traces data only when a condition is satisfied. -- Address bus value (address range and NOT condition can also be specified.) -- Read/write condition -- Access type * Subroutine trace * Stops trace when a trace stop condition is satisfied. -- Address and data bus value -- Read/write condition -- Access type -- External probe value (eight probes) -- System control signals -- NOT condition -- Delay count * Outputs a low pulse from the trigger output pin when a condition is satisfied. -- Address and data bus value -- Read/write condition -- Access type -- External probe value (eight probes) -- System control signals -- NOT condition -- Delay count 7.2.46 TRACE_SEARCH Searches for trace data. 7.2.49 TRACE_MEMORY Specifies memory address to trace. 7.2.47 TRACE_MODE Specifies refresh cycle display. 7.2.48 Trace data acquisition and display 1-3 Table 1-2 Emulation Functions (cont) Reference Section Command Type Command Function Single-step execution STEP * Executes one step at a time, and 7.2.41 displays the following. -- Instruction mnemonic -- Memory contents -- Register contents * Executes displaying the above data for only branch instructions. * Executes displaying the above data for only specified routines. * This operation is performed for a specified number of steps or until a specified address is reached. STEP_ INFORMATION * Specifies information to be displayed during single-step execution. 7.2.42 STEP_OVER * Executes subroutine as a single step. 7.2.43 MEMORY, DUMP Displays or modifies memory contents in 1-, 2-, or 4-byte units. 7.2.27, 7.2.16 MAP Specifies memory attributes in 128-kbyte units. * User memory * Write-protected area (128-kbyte units) * Guarded memory area (128-kbyte units) * Emulation memory -- Standard installation: 512 kbytes (SRAM with no wait state) -- Options: 1 or 4 Mbytes (memory attributes specified in 1-Mbyte units; at 12 MHz or higher frequency, accessible in 3 states) 7.2.26 FILL Writes data in specified pattern. 7.2.19 DATA_SEARCH, DATA_CHANGE Searches for and replaces data in specified pattern. 7.2.13, 7.2.12 CLOCK Selects emulator internal clock. * 13 MHz * 18 MHz Selects user system clock. * 1 to 18 MHz Selects crystal oscillator clock installed on the emulator pod. * 8 to 18 MHz 7.2.9 Memory access Clock selection 1-4 Table 1-2 Emulation Functions (cont) Command Type Command Function Reference Section Register access REGISTER, .<register name> Displays and modifies MCU register contents of the MCU. 7.2.35, 7.2.1 Line assembly ASSEMBLE Assembles instruction mnemonics and modifies memory contents. * Enables use of labels and symbol names. 7.2.4 Disassembly DISASSEMBLE Disassembles memory contents. * Displays labels and symbol names. 7.2.14 Execution time, pass count measurement GO, PERFORMANCE_ ANALYSIS Measures GO command execution time. * Measures total run-time (approx. 305 hours max). * Measures execution time and pass count of the specified range. 7.2.20, 7.2.31 TRACE Counts clocks in each bus cycle. 7.2.45 FILL Reads and writes the specified data to the memory. 7.2.19 CHECK Tests MCU I/O signals. 7.2.8 DISPLAY_ COVERAGE, SET_COVERAGE Provides C0 coverage trace. * Traces addresses executed by the MCU during user program execution. 7.2.15, 7.2.43 LOAD, INTFC_LOAD Loads symbols from host system. 9.4.2, 9.4.7 SYMBOL, SHORT_SYMBOL Defines, displays, and deletes symbols. 7.2.44, 7.2.39 !<symbol name> &<symbol name> Displays symbol contents according to attributes associated with symbol names. * Function names, label names * Variables (simple variables, pointer variables, arrays) and structure names * Line numbers 7.2.2 COMMAND_ CHAIN * * * * Provides automatic input from file. Enables editing with cursor keys. Copies immediately preceding line. Copies operand of previous command. 7.2.10 RADIX Enables value input in binary, octal, decimal, hexadecimal, or ASCII characters. (Default can be specified) 7.2.34 Test functions Symbolic debugging Command input 1-5 Table 1-2 Emulation Functions (cont) Command Type Command Function Reference Section Results display PRINT Outputs to printer or file. 7.2.32 RESULT Displays emulation results. 7.2.27 EXECUTION_ MODE Sets pin status 7.2.18 GO Executes in boot programming mode 7.2.20 MOVE, MOVE_TO_RAM Transfers memory contents. * Memory to memory * ROM (user system memory) to emulation memory 7.2.29, 7.2.30 CONVERT Converts number display. * Displays in binary, octal, decimal, hexadecimal, or ASCII characters. 7.2.11 STATUS Displays emulator operating status. 7.2.40 GO Monitors emulation. * Monitors emulation status every 200 ms and displays abnormalities found during emulation. 7.2.20 RESET Inputs RES signal to MCU. 7.2.36 HELP Displays all commands. 7.2.21 HISTORY Displays the history of the input command. 7.2.22 Flash memory support Others 1-6 Table 1-3 Floppy Disk Utility Functions Reference Section Command Type Command Function Backup B (Monitor command) Backs up or verifies floppy disk. 3.6 in Part I File copy FILE_COPY Copies or verifies file contents. 8.4.1 Directory display FILE_ DIRECTORY Displays file directory information of the floppy disk. 8.4.2 Dump FILE_DUMP * Dumps or modifies floppy disk. * Dumps or modifies file. 8.4.3 File deletion FILE_ERASE Deletes file. 8.4.4 Data transfer to and from user memory FILE_LOAD Loads file contents into memory. 8.4.5 FILE_VERIFY Verifies file contents against memory. 8.4.9 FILE_SAVE Saves memory contents in file. 8.4.7 Format FLOPPY_FORMAT Formats and initializes floppy disk. 8.4.11 File contents display FILE_TYPE Displays file contents. 8.4.8 Rename FILE_RENAME Renames file. 8.4.6 Display free area FLOPPY_CHECK Displays free area on floppy disk. 8.4.10 1-7 Table 1-4 Host System Interface Functions Reference Section Command Type Command Function Interface condition setting HOST Sets the following for RS-232C interface: * Transfer rate (2400 to 38400 BPS) * Data length (7 or 8 bits) * Parity (even, odd, or none) * Number of stop bits (1 or 2 bits) * Busy control method (X-ON/X-OFF control or RTS/CTS control) 9.4.1 Program transfer to and from user system LOAD, INTFC_LOAD Loads contents from host system. 9.4.2, 9.4.7 VERIFY, INTFC_VERIFY Verifies file contents against memory. 9.4.6, 9.4.10 SAVE, INTFC_SAVE Saves memory contents in host system. 9.4.3, 9.4.8 Data transfer to and from floppy disk TRANSFER, INTFC_TRANSFER * Receives data from host system and writes it to file. * Transfers file contents to host system. 9.4.5, 9.4.9 Host system terminal selection TERMINAL Makes the console operate as a terminal of the host system. 9.4.4 1-8 1.3 Realtime Emulation The emulator enables realtime emulation for the MCU with no wait states. Realtime emulation consists of the following three modes: * * * Normal mode: Executes only emulation Cycle reset mode: Forcibly inputs the RES signal to the MCU at a specified period Parallel mode: Enables the user to display or modify memory and display trace information during user program execution The user can select the mode which best suits the user's debugging needs. The following describes each of these modes. 1.3.1 Normal Mode Normal Mode Function: This mode executes only user program emulation. Until a break condition is satisfied, the emulator executes the user program. When a hardware break condition or PC break condition is satisfied, the emulator stops program execution and outputs a low pulse only once from the trigger output probe. When a number of times for the PC break condition or sequential break is specified, the emulator outputs a low pulse from the trigger output probe every time the PC break condition is satisfied. Normal Mode Specification: Specifying no option with the GO command sets normal mode. 1-9 1.3.2 Cycle Reset Mode Cycle Reset Mode Function: The emulator inputs the RES signal to the MCU at a specified period during realtime emulation and repeats the execution from the reset state. The emulator outputs a low-level pulse from the trigger output probe at the same time when the RES signal is input to the MCU. This function is useful for observing waveforms from an initial state such as power-on reset to the specified time. User program Re-execution from reset address Program flow A low pulse is output from the TRIG output probe RES input to the MCU after specified time TRIG signal Figure 1-1 Cycle Reset Mode Cycle Reset Mode Specification: Set "R=n" as a GO command option to specify cycle reset mode. Emulation Stop: In cycle reset mode, hardware break conditions and PC break conditions are ignored. To stop emulation, press the (CTRL) + C keys or the (BREAK) key. Note: When the emulator displays trace information after emulation terminates, disassembly of the instruction just before input of the RES signal may not be correct. If so, the mnemonic display will be .DATA. 1-10 Trigger Signal Output Timing in Cycle Reset Mode: In cycle reset mode, the emulator inputs the RES signal to the MCU when the time specified by a command passes. Figure 1-2 shows the timing for output from the trigger output probe in cycle reset mode. Time specified by a command TRIG (RES) 16 s Figure 1-2 Trigger Signal Output Timing 1-11 1.3.3 Parallel Mode Parallel Mode Function: In parallel mode, the emulator can display or modify memory or display trace information during realtime emulation. Parallel Mode Specification: Parallel mode can be activated during GO command realtime emulation by any of the following methods as shown in figure 1-3. * * * Press the (RET) key Press the space key Satisfy a trace stop condition specified by the TRACE_CONDITION command If any of the above occurs, the emulator will display a prompt (#) and enter parallel mode command input wait state. Emulation, however, continues without interruption. Executing the ABORT command terminates parallel mode. (RET) key input or trace condition satisfaction Parallel mode (a) END (RET) input Normal mode (SPACE) key input A command execution Parallel mode (b) Figure 1-3 Transition to Parallel Mode 1-12 User program Program flow * Pressing the (RET) key * Pressing the space key * Satisfying the trace stop condition A prompt (#) is displayed and the emulator waits for command input in parallel mode Program does not stop Figure 1-4 Parallel Mode Note that debugging differs in parallel mode operation depending on the method used to activate it, as follows. * By pressing the (RET) key or satisfying a trace stop condition -- The emulator stops acquiring trace information as soon as parallel mode is entered. -- The emulator can execute multiple commands entered by the user in parallel mode. -- The END command terminates the parallel mode and returns the emulator to normal mode (displays the current PC). At this time, the emulator restarts detecting trace information acquisition conditions. * By pressing the space key -- The emulator continues trace information acquisition; however, while the emulator executes the TRACE, TRACE_SEARCH, TRACE_CONDITION, or TRACE_MEMORY command, it acquires no trace information. -- In parallel mode, the emulator returns to normal mode after one command execution and displays the current PC. At this time, if trace information acquisition has stopped, the emulator restarts acquisition. Table 7-1 lists the commands usable in parallel mode. 1-13 Notes: 1. Emulation memory can be accessed without interrupting program execution in parallel mode. 2. When memory other than internal ROM, internal RAM, internal flash memory, and emulation memory is accessed with the MEMORY command, DUMP command, DISASSEMBLE command or !<symbol name> in parallel mode, the user program will pause for a while. For example, this pause lasts for about 2.0 ms when the MEMORY command is executed at 18 MHz. The emulator pauses at the following timing. * * * * MEMORY command: At each memory access DUMP command: In 16-byte units DISASSEMBLE command: In 4-byte units !<symbol>: During symbol read 3. During execution of the TRACE, TRACE_SEARCH, TRACE_MEMORY or TRACE_CONDITION command, the emulator stops trace information acquisition. 4. The emulator cannot enter parallel mode when executing emulation in the following modes specified by GO command mode options. * * Cycle reset mode Time interval measurement mode 1, 2 1-14 1.4 Break Function The following four methods are useful to stop emulation. The break function can be used regardless of the MCU's operating mode. * * * * Hardware break: PC break: Forced break: Write protect/guarded break: Caused by the MCU's signal status as specified Caused by a PC (Program Counter) Caused by pressing the (CTRL) + C keys or the (BREAK) key Caused by writing to a write-protected area or accessing guarded area 1.4.1 Hardware Break Break conditions can be specified at any four points with the BREAK_CONDITION1,2,3,4 commands. (1) Break Conditions * * * * * * * * * * Address bus value Data bus value Read/write condition External probe value External interrupt condition (NMI, IRQ0 to IRQ5) NOT condition Number of times the condition is satisfied (H'1 to H'1000) Delay count (H'1 to H'7FFF bus cycles) Sequential break Access type (PRG, DAT, DMA) Note: Because the MCU prefetches instructions, a break may occur before the prefetched instruction is executed when a break condition is satisfied during a prefetch cycle. 1-15 Address Bus Value: A break occurs when the MCU address bus value matches the specified condition. To specify a break address, there are two methods. One is to specify an address range, and the other is to specify a particular address. * Break condition: When the address bus value is 1204 * Specification: A =1204 User program Break condition is satisfied 1202 1203 1204 NOP NOP MOV.B @4000, R0 Break occurs when the MOV instruction is fetched Figure 1-5 Break with Address Bus Value Data Bus Value: A break occurs when the MCU data bus value matches the specified condition. The emulator checks both program fetch and data access for the condition. When specifying the condition, the access size must be selected from word access (WD) or byte access (HD, LD, or D). * Break condition: When the data bus value is 12 * Specification: D =12 User program Break condition is satisfied 1202 1203 1204 NOP NOP MOV.B #12, R0 Break occurs when the #12 is fetched Figure 1-6 Break with Data Bus Value 1-16 Read/Write Condition: A break occurs when the MCU's RD and WR (HWR and LWR) signal levels match the specified conditions. Usually, the read/write condition is specified together with the address or data conditions. * Break condition: When writing to address FF00 User program Break condition is satisfied 1200 1201 1204 * Specification: A=FF00 W NOP MOV.B #01 , R0L MOV.B R0 , @FF00 Break occurs when address FF00 is written to Figure 1-7 Break with Read/Write External Probe Value: * A break occurs when external probe signal levels match the specified values. For example, the user can specify probe 1 and 2's levels to high and the other probes' levels to low to generate a break. * Multibreak function External probe 8 has a falling-edge detection function. By using this function, you can break other emulators of the same type simultaneously. Specify the falling-edge function or level signal input for external probe 8 using the EXECUTION_MODE command. The following explains how to perform a multibreak with external probe 8. 1-17 E7000 HITACHI Emulator pod (II) E7000 Emulator pod (I) HITACHI Figure 1-8 Multibreak Function Procedure 1. Connect external probe 8 of emulator pod (I) to the trigger output probe of emulator pod (II). 2. Set the break condition for emulator pod (II). 3. Set the break condition for external probe 8 of emulator pod (I). At this time, specify external probe 8 to break at low level: PROB=B'0xxxxxxx. 4. Execute the programs for both emulator pods (I) and (II). 5. First, when the break condition is satisfied, the emulator pod (II) program breaks. At this time, the emulator pod (I) program also stops due to pulse output from the trigger output probe. However, the break in emulator pod (I) follows that in emulator pod (II) by several bus cycles. 1-18 External Interrupt Condition (NMI, IRQ0 to IRQ5): This break is caused by an external interrupt condition (NMI, IRQ0 to IRQ5). Emulation stops when the value of the interrupt signal matches the specified value. Figure 1-9 shows an execution example. * * NMI: Can specify low or high level IRQ0 to IRQ5: Can specify low or high level * Break condition: When the IRQ0 is low level (IRQ1 to IRQ5 are high level) MCU * Specification: IRQ = H'3E Break occurs when the IRQ0 is low level and IRQ1 to IRQ5 are high level IRQ0 to IRQ5 IRQ0 to IRQ5 Figure 1-9 Break with External Interrupt Note: External interrupt signals (IRQ0 to IRQ5) can also be used for other input depending on MCU control register settings. However, the emulator monitors status of these signals as break conditions. 1-19 NOT Condition: A break occurs when the break condition of the address bus and data bus value is not satisfied. The user can specify this condition only with the BREAK_CONDITION1 command. Memory area 0000 * Break condition: When accessing outside the address 4000 to 7FFF 4000 * Specification: A=4000 : 7FFF ; NOT 8000 Break occurs when accessing outside the address range from 4000 to 7FFF FFFF Figure 1-10 Break with NOT Condition Number of Times the Break Condition is Satisfied: A break occurs after the above break condition has been satisfied for a specified number of times (4,096 max). When specifying this condition, specify in combination with any of the above conditions. The user can specify this condition only with the BREAK_CONDITION1 command. 1-20 User program When the first break condition is satified No break occurs * Specification: A=2000 Program flow When the second break condition is satisfied * Break condition: When accessing to address 2000 four times COUNT = 4 No break occurs When the third break condition is satisfied No break occurs User program stops when the fourth break condition is satisfied When the fourth break condition is satisfied Figure 1-11 Break with the Number of Times Break Condition is Satisfied Delay Count: A break occurs when the above break condition is satisfied and the emulator executes the bus cycle for a specified number of times (32,767 max). When specifying this condition, specify in combination with any of the above break conditions. The user can specify this function only with the BREAK_CONDITION1 command. User program Break condition is satisfied Program flow * Break condition: 50 bus cycles are executed after address 2000 is accessed * Specification: A=2000 DELAY=50 No break occurs 50 bus cycles Break occurs 50 bus cycles after the satisfaction of the condition Figure 1-12 Break with Delay Count Specification 1-21 Sequential Break Condition: In sequential mode, a break occurs when hardware break conditions 4 to 1 have been satisfied in that order. There are three kinds of modes, depending on the number of the specified condition. * Sequential break mode 1 When break conditions 2 and 1 are satisfied in that order, a break occurs. * Sequential break mode 2 When break conditions 3, 2, and 1 are satisfied in that order, a break occurs. * Sequential break mode 3 When break conditions 4, 3, 2, and 1 are satisfied in that order, a break occurs. Specify the break condition with the BREAK_CONDITION1,2,3,4 commands. The user can specify any of the above conditions. When executing the user program, specify the sequential break option (;S1 to S3) with the mode option of the GO command. When no option is specified, the sequential break function does not operate, and a break will occur as soon as any of the break conditions are satisfied. User program 2000 Program flow Break condition 2 is satisfied * Initiation condition: User program is executed in sequential mode 1 from address 2000 * Specification: GO=2000 ; S1 No break occurs Break condition 1 is satisfied When break condition 1 is satisfied after break condition 2, a break occurs. A break occurs even when break condition 1 is satisfied after break condition 2 has been satisfied more than twice. Figure 1-13 Break with Sequential Specification 1-22 (2) Break Timing Hardware break sampling timing synchronizes with the MCU bus cycle (AS signal). T1 T2 T3 T1 T2 T3 T1 T2 T3 T1 T2 T3 T1 Address Data AS Interrupt signal External probe Figure 1-14 Break Timing Notes: 1. Because the MCU prefetches instructions, a break may occur before the prefetched instruction is executed when a break condition is satisfied during a prefetch cycle. 2. When the AS signal is negated simultaneously with the external probe signal transition, the break condition may be undefined while a value on that external probe is specified as a break condition. 1-23 1.4.2 PC Break The program counter (PC) break stops program execution when the instruction of the specified PC address is executed. Since a PC break is caused by hardware, it can be set in the ROM area. Note that the address corresponding to the beginning of the instruction must be specified; otherwise a break does not occur. The PC break can be performed in the following two ways; * * Normal break Sequential breaks Normal Break: A break occurs after executing the breakpoint instruction specified with the BREAK command. At this time, the following can be specified: * Number of break points: 255 points (max) * Range specification : A break occurs when an instruction in the specified address range is executed. * Number of times the break condition is satisfied: A break occurs after executing the breakpoint instruction a specified number of times. The maximum number to specify is 16,383 (H'3FFF). User program Program flow 1000 Instruction * Break condition: The break condition is satisfied when instructions at addresses H'1000 to H'2000 have been executed. * Specification: BREAK 1000 : 2000 A break occurs after the instruction of the address H'1000 is executed. Figure 1-15 Normal Break (PC Break) Note: When specifying the number of times that the break condition is to be satisfied before generating a normal break, emulator firmware performs processing every time the program passes the break condition address. As a result, the program will not operate in realtime. 1-24 Sequential Break: A sequential break occurs (four points max) when certain conditions are satisfied in a specified order. A reset point can be specified in addition to these four points. If the reset point is reached, all sequential break conditions up to that point become invalid and the emulator rechecks from the first break condition. Figure 1-16 illustrates the usual sequential break and figure 1-17 describes a sequential break when a reset point is specified. * Break condition: The break condition is satisfied when instructions at addresses H'1000, H'2000, H'3000 and H'4000 have been executed in sequence. * Specification: BREAK_SEQUENCE 1000 2000 3000 4000 User program 1000 (break condition 1) 2000 (break condition 2) 3000 (break condition 3) Program flow No break occurs No break occurs No break occurs 4000 (break condition 4) The break condition is satisfied when instructions at addresses H'1000, H'2000, H'3000, and H'4000 have been executed in sequence. Figure 1-16 Sequential Break Note: When specifying the sequential break, emulator firmware performs processing every time the program passes the break condition address. As a result, the program will not operate in realtime. 1-25 * Break condition: A break occurs when the instructions at addresses H'1000, H'2000, H'3000, and H'4000 have been executed in sequence. * Specification: BREAK_SEQUENCE 1000 2000 3000 4000 BREAK_SEQUENCE 500;R User program 1000 (Break condition 1) Program flow No break occurs (wait for break condition 2) 2000 (Break condition 2) No break occurs (wait for break condition 3) 3000 (Break condition 3) No break occurs (wait for break condition 4) 500 (Reset point) No break occurs (wait for break condition 1) 4000 (Break condition 4) No break occurs (wait for break condition 1) 1000 (Break condition 1) No break occurs (wait for break condition 2) 2000 (Break condition 2) No break occurs (wait for break condition 3) 3000 (Break condition 3) No break occurs (wait for break condition 4) 4000 (Break condition 4) Ignores conditions 1, 2, 3, 4 and searches for the condition from break condition 1 A break occurs when the instructions at address H'1000, H'2000, H'3000, and H'4000 have been executed in sequence. Figure 1-17 Sequential Break (with Reset Point Specification) Note: When specifying the sequential break, emulator firmware performs processing every time the program passes the break condition address or reset point. As a result, the program will not operate in realtime. 1-26 1.4.3 Forced Break Pressing the (CTRL) + C keys or the (BREAK) key stops program execution. 1.4.4 Write Protect/Guarded Break The user can specify the MCU memory area as write-protected or guarded areas in 128-kbyte units with the MAP command. The emulator forcibly stops the program when a write access or read/write access is attempted to the specified memory. A normal break occurs, however, after the accessed instruction execution is completed. For details, refer to section 7.2.26, MAP. 1-27 1.5 Realtime Trace Function The emulator can trace bus information during realtime emulation without affecting the user system. The emulator can fetch bus information of the MCU such as address or data, and the contents of eight external probes up to 32,767 bus cycles. Trace information is displayed with the TRACE command. Display of this information enables a check on executed program. Trace information: * * * * * * Address bus: 24 bits Data bus: 16 bits External probes: 8 MCU I/O control signals: 30 Number of bus cycle clocks (o): 7 bits (127 bytes max) Memory contents tracing: 16 bits The emulator displays trace information as the following methods: * * * Fetches only instruction words from the trace information and displays them in mnemonic. Displays the trace information in bus cycle units. Searches for the specified information and displays it. Use the TRACE_SEARCH command. This trace function traces the bus information even in the MCU single chip mode. 1.5.1 Trace Timing Trace information is acquired in trace memory synchronized with rising edges of the address strobe signal (hereinafter referred to as the AS signal). However, because external probe signal input is not synchronized with the AS signal, it may not be possible to log all the changes in the external probe signal. In each bus cycle, the clock number is the number of clock (o) cycles between the end of the previous bus cycle and the end of the current bus cycle (between one rising edge of AS and the next). Figure 1-18 shows an example of the external probe trace signal. 1-28 T1 T2 T3 T1 T2 T3 T1 T2 T3 T1 T2 T1 T3 Address (A) (A) Data AS (1) (2) (3) External probe 0 1 1 X Figure 1-18 External Probe Trace Signal Example Description: * External probe signal -- Trace information sampled at rising edges of AS (figure 1-18 (1)). -- When the external probe signal changes between samplings, it cannot be reflected in the trace data (figure 1-18 (2)). -- When a sampling edge coincides with a change in the external probe signal, the trace contents are undefined.(figure 1-18 (3)). * Clock number -- Three clock cycles are traced in bus cycle (A). 1-29 1.5.2 Trace Condition Setting The user can specify the following four conditions with the TRACE_CONDITION command. * * * * Free trace Subroutine trace Range trace Trace stop Free Trace: In free trace when the user program is executed as a result of the GO, STEP, STEP_OVER command, tracing is carried out continuously for a maximum of the latest 32,767 bus cycles until a break condition is satisfied. When no parameter is given with the TRACE_CONDITION command, the default is free trace. Figure 1-19 illustrates the free trace operation. User program Program flow Trace memory Break condition is satisfied 32,767 bus cycles Figure 1-19 Free Trace Execution 1-30 Subroutine Trace: When a subroutine trace is specified, the emulator acquires operand accesses and instructions between a specified start address and end address. However, when the specified subroutine calls another subroutine, the called subroutine is not traced. Figure 1-20 illustrates the operation of the subroutine trace. Start address BSR JSR Trace information is acquired Figure 1-20 Subroutine Trace Specification Range Trace: When a range trace is specified, the emulator only traces at points where specified conditions are satisfied. The following conditions can be specified. * * * Address value (Within or outside a specified range) Read/write condition Access type Figure 1-21 illustrates the trace acquisition condition. 1-31 User program Program flow Trace memory Trace acquisition condition is satisfied When the user program stops, the trace memory stores trace information from the address at which the trace acquisition condition was satisfied Break condition is satisfied Figure 1-21 Trace Acquisition Condition Specification Trace Stop (Parallel Mode): When a trace stop condition is specified, the emulator acquires trace information until the specified condition is satisfied. At this point, trace acquisition stops and the emulator prompts for command input, although realtime emulation does not stop. This so-called parallel mode enables the user to view trace information without stopping realtime emulation. Refer to section 1.3.3, Parallel Mode, for details. Once the trace stop conditions have been satisfied and the trace information has been displayed, the user can specify the trace stop condition again. The user can specify the following conditions. * * * * * * * Address bus and data bus value Read/write condition Access type (PRG, DAT, DMA) External probe value System control signal (BREQ, BACK) NOT condition Delay count (H'1 to H'7FFF) The trace stop condition is set with the TRACE_CONDITION command. Figure 1-22 illustrates how the system operates when a trace stop condition is specified. 1-32 User program Program flow Trace memory 32,767 bus cycles Trace stop condition is satisfied No break occurs Figure 1-22 Trace Stop Condition Specification 1.5.3 Trace Display The user can display trace information using the TRACE command. There are three display formats, as follows. * Instruction display From the contents of the trace information, only the executed instructions are displayed in mnemonics. * Bus cycle display Trace information is displayed in bus cycle units. When a trace is specified in special address memory, the memory contents are also displayed. The memory address is specified with the TRACE or MEMORY command. * Search and display The emulator searches for specified trace information and displays all the appropriate bus cycles. In this case, use the TRACE_SEARCH command. 1-33 1.6 Single-Step Function In addition to realtime emulation, effective debugging is facilitated by the single-step function. This function displays the following information every time a program instruction is executed. * * * * * * MCU control registers (PC, CCR) MCU general registers (ER0 to ER7) Instruction address Instruction mnemonic Memory contents The cause of termination 1.6.1 Single-Step Execution Single-step execution has three modes: one in which all the instructions are displayed, one in which only branch instructions are displayed, and another in which instructions of a subroutine executed at first are displayed. To execute this function, use the STEP command, or to execute a subroutine in a single step, use the STEP_OVER command. * Displaying all instructions The emulator displays the information described above after every instruction. * Branch instruction display The information is only displayed at execution of branch instructions listed below. Bcc, BRA, BRN, JMP, BSR, JSR, RTS, RTE * Subroutine display The information for the subroutine executed at first is displayed. Start address BSR JSR Trace information is acquired Figure 1-23 Subroutine Display 1-34 This function interrupts the execution state display at the JSR or BSR instruction in the designated subroutine, and resumes the execution state display when the instruction placed immediately after the JSR or BSR instruction is executed. After that, if another JSR or BSR instruction is executed, the execution state display is interrupted. * Subroutine step execution: When executing a JSR or BSR instruction, the emulator treats the called subroutine as a single step. The emulator stops after executing an instruction other than JSR or BSR. This function can be used in the internal ROM, internal RAM, user RAM, or the emulation memory area. 1.6.2 Setting Display Information The user can set the information displayed at each instruction by using the STEP_INFORMATION command. 1.6.3 Termination of Single-Step Function The single-step function stops after executing a specified number of steps from the specified start address (or the current PC address). The user can stop continuous execution by specifying a stop address. However, the specified address must be at the start of an instruction. 1.7 Execution Time Measurement The user can measure the user program execution time. This function has four modes. * * * * Normal mode Time interval measurement mode 1 Time interval measurement mode 2 Subroutine time measurement and number of times measurement Specify the execution time measurement mode with the GO command. 1-35 Normal Mode: In this mode, the emulator measures the total execution time from when the user program is started with the GO command to when it is stopped by a break. Normal mode is selected as a default when no option is specified with the GO command. The maximum time period that can be measured is 305 hours. Program execution starts Time measurement The break condition is satisfied : The break condition is satisfied Figure 1-24 Normal Mode Time Measurement Range Time Interval Measurement Mode 1: The emulator measures the elapsing between the satisfaction of hardware break conditions 2 and 1, up to a maximum of 305 hours. Set the hardware break condition using BREAK_CONDITION1,2 commands. Time interval measurement mode 1 is specified using GO command option I1. Condition 2 is satisfied Condition 2 is satisfied Condition 2 is satisfied a Condition 1 is satisfied Condition 2 is satisfied b Condition 1 is satisfied Measurement time = a Measurement time = b c BREAK key Measurement time = c Figure 1-25 Time Interval Measurement Mode 1 1-36 In this mode, program execution does not stop unless break condition 1 is satisfied after break condition 2 has been satisfied. Even if break condition 2 is satisfied many times before break condition 1, the emulator measures the time from the first occasion on which break condition 2 is satisfied. When this mode is specified, the BREAK_CONDITION3,4 commands and PC break are invalid. Time Interval Measurement Mode 2: In this mode, the time intervals between the satisfaction of break conditions 2 and 1 are added together up to a maximum of 305 hours. Without stopping program execution, this mode is selected by specifying option I2 with the GO command. In time interval measurement mode 1, a break occurs after hardware break condition 2 and then break condition 1 are satisfied. However, in this mode, even if break condition 1 is satisfied, a break does not occur. Since the PC break becomes invalid, the program can only be stopped using the (BREAK) key or (Ctrl) + C keys. Condition 2 is satisfied Condition 2 is satisfied a Condition 1 is satisfied Condition 2 is satisfied Condition 2 is satisfied Condition 1 is satisfied b Condition 2 is satisfied Condition 1 is satisfied c d Break key Break key Measurement time = a + b Measurement time = c + d Figure 1-26 Time Interval Measurement Mode 2 1-37 1.8 Trigger Output During user program execution, the emulator outputs a low-level pulse from the trigger output probe under the following three conditions. When using this pulse as an oscilloscope trigger input signal, it becomes easy to adjust the user system hardware. * * * Cycle reset Trace condition satisfaction (When trigger output is specified) Hardware break condition satisfaction The emulator always outputs a low-level signal from the trigger output probe in the command input wait state. Cycle Reset: The emulator outputs a low-level pulse from the trigger output probe with the same timing as the RES input signal to the MCU. Cycle reset is specified with the GO command. Trace Condition Satisfaction: When the trigger output is specified using the TRACE_CONDITION command, a low-level pulse is output from the trigger output probe at bus cycles corresponding to the specified condition. The trigger signal is output from the end of the corresponding bus cycle until the end of the next bus cycle. If the conditions are satisfied in consecutive bus cycles, the trigger output remains low. Hardware Break Condition Satisfaction: During emulation, a low-level pulse is output from the trigger output probe at the end of the bus cycle during which the hardware break condition is satisfied. The EXECUTION_MODE command can be used here to specify whether or not a break is to occur when the hardware break condition is satisfied. When the hardware break condition is satisfied with break specification, the emulator enters the command input wait state, and begins to output a continuous low-level signal. Specify the hardware break condition with the BREAK_CONDITION1,2,3,4 commands and the emulation mode option of the GO command. Note that when a sequential break is specified with the emulation mode option of the GO command, a low-level pulse is output each time a condition is satisfied, that is, the trigger is not output only when the last condition is satisfied. Command Input Wait State: The emulator always outputs a low-level signal from the trigger output probe. 1-38 Figure 1-27 shows the output timing. T1 T2 T1 T2 T1 T2 T1 T2 Address AS 85 ns TRIG (Trace condition is satisfied) 110 ns 85 ns TRIG (Hardware break condition is satisfied; no break occurs) 110 ns 85 ns TRIG (Hardware break condition is satisfied; break occurs) 370 ns 110 ns Condition: 2-state cycle, 18 MHz Figure 1-27 Pulse Output Timing Note: A low-level pulse output timing and pulse width differ depending on each condition. 1-39 1.9 Memory Access Function Memory Management: The MCU has a maximum address space of 16 Mbytes. The emulator manages this space in 128-kbyte or 1-Mbyte units with the following memory attributes. * * * * User memory (User system memory) Emulation memory (512-kbyte standard memory, 1-Mbyte/4-Mbyte optional memory) Write-protected Access-prohibited (Guard function) For details, refer to section 3.2, Memory Space, and section 7.2.26, MAP. Memory Display, Modification, and Transfer: Memory display, modification and transfer are done, using the following commands. ASSEMBLE DISASSEMBLE MEMORY LOAD FILE_LOAD LAN_LOAD INTFC_LOAD DATA_CHANGE DUMP MOVE SAVE FILE_SAVE LAN_SAVE INTFC_SAVE 1-40 DATA_SEARCH FILL MOVE_TO_RAM 1.10 MCU Control and Status Check The emulator is capable of switching the clock signal supplied to the MCU, checking normal operation, and displaying the execution state. This function is effective for debugging the user system hardware. Clock Switching: The emulation clock can be supplied from the user system clock (hereafter referred to as the user clock), the internal clock (13 MHz, 18 MHz), or the crystal oscillator installed in the emulator pod. To switch the clock, refer to section 7.2.9, CLOCK, and note the following. * When the clock is switched, the emulator inputs a RES signal to the MCU. This initializes the registers. * When the user switches to the user clock and the user clock signal is not supplied, an error message is displayed and the internal clock is selected instead. * When initiating the emulator system program, the emulator selects the MCU clock automatically in the following order. -- When an external clock is supplied from the user system, selects the user system clock -- When a crystal oscillator is installed in the emulator pod, selects the crystal oscillator -- Selects the internal clock (13 MHz) Substitution of Internal ROM, Internal RAM, and Internal Flash Memory: The H8/3048 series has internal ROM and internal RAM, and the H8/3048F has flash memory and internal RAM. In the emulator, the MCU internal ROM/flash memory/internal RAM cannot be accessed forcibly and is substituted by off-chip RAM. Since the substitute RAM for internal ROM/internal RAM can be accessed in MCU bus cycles, it does not affect realtime emulation. Strobe Signal Output Function at Emulation Memory Access: When emulation memory is accessed, the emulator outputs the corresponding address to the user system, but does not output the strobe signals (AS, RD, HWR, LWR). When the user system needs the strobe signals (AS, RD, HWR, LWR) that accesses the memory, strobe output can be enabled with EXECUTION_MODE specification. In this case, user WAIT signal input is also valid. Check of I/O signals: The emulator checks the connection with the user system at the system initiation. By this check, abnormalities such as short of the user system interface signal can be detected. The signals for the check is as follows. The CHECK command can also check the same signals with the ones at the system initiation. RES, STBY, BREQ, WAIT, IRQ0 to IRQ5, NMI 1-41 Emulator Execution Status Display: The emulator can display the execution status information listed in table 1-5. To display the execution status, use the STATUS command. Table 1-5 Execution Status Display Operation Status MCU type MCU operating mode Number of MCU pins Radix type Number of breakpoints specified with the BREAK command BREAK_CONDITION 1 to 4 command specifications TRACE_CONDITION command setting status Host system interface conditions Number of registered symbols Number of registered line number symbols Information displayed with the STEP_INFORMATION command during single-step execution Address range displayed with the STEP command Clock type specified by the CLOCK command File name or printer that outputs the CRT displayed contents PC break specification or coverage acquisition range Remaining emulation memory 1-42 1.11 Emulation Monitoring Function The emulator monitors the emulation status such as memory accesses or user program execution. Two kinds of status are monitored. * * MCU execution status User system power and clock status MCU Execution Status: When executing the program with the GO command, the emulator monitors the execution status every 200 ms. When the status changes, the execution status display is updated. With this function, the user can observe the progress of the program. Table 1-6 shows the execution status to be displayed. The execution status cannot be output to a printer or file assigned with the PRINT command. For details, refer to the description on execution status display, in section 7.2.20, GO. Table 1-6 Execution Status Display Display Meaning **PC=xxxxxx [xxxxxx = xxxx] (a) (b) (c) (a) Program fetch address (b) Memory address (c) Memory contents Current program fetch address is displayed. When specifying TM option with GO command, the memory address and its contents are displayed. **VCC DOWN The user system power is off. The user program stops. ** RESET RES signal is low. The MCU has been reset. ** WAIT A = xxxx xxxx: Address bus value WAIT signal is low. ** HARDWARE STANDBY STBY signal is low. However, the MCU is not put in hardware standby mode because this signal is not input to the MCU. Therefore, even if STBY signal is low, this message is displayed only. ** SOFTWARE STANDBY The MCU is in software standby mode. ** SLEEP The MCU is in sleep mode. ** BREQ BREQ signal is low. ** BACK BACK signal is low. ** TOUT A = xxxx xxxx: Address bus value The address bus value is displayed. The bus cycle stops for 80 s or more. 1-43 User System Power and Clock Status: The emulator monitors the user system power and clock status. If the user system power is off or the clock stops when the MCU clock is set to USER with the CLOCK command, the emulator executes the following operation according to its current status. Table 1-7 User System Power and Clock Status Operating Status Emulator Operation At emulator initiation Waits for the user system to power on. After the user system is turned on, starts initiation with the user clock. User system power off (crystal oscillator installed, user clock installed) User system power off (crystal oscillator not installed, user clock installed) After initiation User system power off (crystal oscillator installed, user clock not installed) Waits for the user system to power on. After the user system is turned on, starts initiation with the crystal oscillator. Command input wait Displays ** VCC DOWN and enters command input wait state. After the user system powers on, displays RESET IN BY E7000 ! (the emulator is reset) and enters command input wait state. The clock type does not change at this time. Program execution and parallel mode Displays ** VCC DOWN and stops GO command execution. After the user system powers on, displays RESET IN BY E7000 ! (the emulator is reset) and enters command input wait state. The clock type does not change at this time Notes: 1. Power-off is detected as follows: * When the emulator is initiated at 13 MHz or higher frequency, power-off is detected at about 4 V * When the emulator is initiated at a frequency lower than 13 MHz, power-off is detected at about 2.5 V. 2. When a user system interface cable is connected, power supply voltage must be provided from the Vcc pin on the user system interface cable to operate the emulator. Therefore, when using the emulator on its own, be sure to disconnect the user system interface cable. 1-44 1.12 Operating Voltage and Frequency The emulator can be operated at a voltage from 2.7 V to 5.5 V as supplied by the user system through a user cable connection. Since the operating voltage is supplied to the emulator directly from the user system, the operating voltage must correspond to the operating frequency, as shown in figure 1-28. Note: The emulator monitors whether the user system interface cable is connected and whether the power is being supplied from the user system. Therefore, when using the emulator on its own (stand-alone mode), be sure to disconnect the user system interface cable from the emulator pod. (V) 5.5 4.5 Operating voltage 3.0 2.7 0 0 1 8 13 18 (MHz) Operating frequency Allowable operating range Figure 1-28 Allowable Operating Range of Emulator 1-45 1.13 Flash Memory Usage The H8/3048F has flash memory. The emulator emulates the flash memory with the substitute RAM in the same way as the internal ROM. This section describes how to use the substitute RAM for the flash memory. 1.13.1 On-Board Programming On-Board programming is classified into two modes: boot mode and user program mode. Execution flow for each mode is shown below. For details on on-board programming modes, refer to the H8/3048F Hardware Manual. Boot Mode: Start 1. Connect to the host 1. Connect the serial communication interface pins to the host while the emulator power is off. 2. Select the boot mode with the EM command 2. Apply 12 V to the Vpp pin and select the boot mode with the EXECUTION_MODE (EM) command. (The MCU assumes that 12 V is applied to the MD2 pin.) 3. Execute the GO command with ONRESET option 3. Execute the GO command with the ONRESET option to start boot-mode operation. 4. Start data transfer 4. Start data transfer. For details on the transfer procedure, refer to section 18.6.1, Boot Mode, in the H8/3048F Hardware Manual. Figure 1-29 Boot-Mode Flowchart 1-46 User Program Mode: 1. Write the application program 1. Before starting user program mode, the application program which will execute steps 3 to 5 below must be stored in the flash memory area (substitute RAM). (This can be done by using boot-mode operation.) 2. Apply 12 V to the Vpp pin or use the EM command to apply 12 V to the Vpp pin from the emulator 2. Apply 12 V to the Vpp pin from the user system, or use the EXECUTION_MODE command to apply 12 V to the Vpp pin from the emulator. 3. Transfer on-board write program to MCU RAM 3. Transfer the on-board write program to MCU RAM with the GO command. 4. Execute on-board write program on MCU RAM 4. Branch to the on-board write program in the MCU RAM to write user's application program to the flash memory area (substitute RAM). 5. Execute application program 5. After the on-board writing completes, branch to the user's application program written to the flash memory area (substitute RAM). Figure 1-30 User Program-Mode Flowchart 1.13.2 Flash Memory Operation The flash memory in the MCU can operate in program mode, program-verify mode, erase mode, erase-verify mode, or prewrite-verify mode. However, some operations differ between the emulator and the actual H8/3048F. For details on the differences, refer to section 2, Differences between the MCU and the Emulator. The emulator accesses the substitute RAM instead of the flash memory. Therefore, settings in the flash memory control register (FLMCR) and erase block registers 1 and 2 (EBR1 and EBR2) are invalid when the emulator is used. The RAM control register (RAMCR) does not exist in the emulator. Program Mode and Program-Verify Mode: Settings in the P and PV bits of the FLMCR are invalid in the emulator. To write data by user program execution, apply 12 V directly to the Vpp pin, or use the EXECUTION_MODE (EM) command to apply 12 V to the Vpp pin from the emulator. Note: If writing to the flash memory area (substitute RAM) is attempted when 12 V is not applied to the Vpp pin, the flash memory contents do not change and no error message is displayed. 1-47 Erase Mode and Erase-Verify Mode: The emulator does not support erase mode. The E bit of the FLMCR is ignored and data in the flash memory area (substitute RAM) is not changed to H'FF. To change the data to H'FF, select the erase-verify mode and perform dummy write of H'FF. At this time, apply 12 V directly to the Vpp pin, or use the EXECUTION_MODE command to apply 12 V from the emulator. Data can be erased by using the FILL command as follows: FILL <start address> <end address> FF Notes: 1. When the user program mode is not selected with the EM command or when 12 V is not applied to the Vpp pin, the memory contents do not change even if the erase mode or erase-verify mode is selected. At this time, no error message is displayed. 2. Before erase-mode execution, prewrite-verify-mode operation must be performed. In the emulator, write H'00 as prewrite: do not write inverted data. 3. Settings in EBR1 and EBR2 are invalid. Prewrite-Verify Mode: The emulator accesses the substitute RAM instead of flash memory. Therefore, write H'00 as prewrite: do not write inverted data. Flash Memory Emulation by MCU RAM: The emulator does not support this function. 1-48 1.14 Symbolic Debugging The emulator has a symbolic debugging function which uses the source program symbols (variables and line numbers). This function is explained below. 1.14.1 Defining Symbols * Definition methods There are three ways to define symbols. -- Load module with debugging information load A linkage editor can be used to create a load module containing information for debugging (SYSROF-type load module). Symbols can be defined by loading such a module with the LOAD command. -- SYMBOL command Symbols can be defined with the SYMBOL command. In this case, the symbol attributes are registered as labels. -- ASSEMBLE command Label names are defined using the ASSEMBLE command. * Symbol attributes Table 1-8 lists the attributes of the symbols which may be defined within the load module (SYSROF type) debugging information. Table 1-8 List of Symbol Attributes Item Attributes Symbol type Function name Structure name Label name Variable name (Simple variable, pointer variable, array) Line number Allocation type External static variable Internal static variable Variable type Character Integer Pointer 1-49 * Symbol Names and Abbreviations Symbols within load module debugging information are nested. Use a slash (/) to separate the different parts of a symbol in this nested structure. The basic symbol formats are shown below. -- General symbol format !<unit name>/<function name>/<variable name> -- Line number symbol &<unit name>/<line number> To simplify the nested structure, abbreviations can be defined for symbol names up to a specific level in a nested structure. 1.14.2 Symbol Reference Using Symbols in Commands: A symbol can be used as an address or data in a command after it has been defined by the SYMBOL command. In this case, the value of the symbol is treated as the input value. Referring to Symbol Contents: If a symbol is input in the following format in command input wait state, the symbol's contents are displayed: :!<symbol name> If the D option is specified, it will be displayed in decimal. :!<symbol name> D (D: Option for symbol value in decimal) 1.14.3 Symbol Deletion The symbol deletion function of the SYMBOL command deletes all symbols at the same time. Specific symbols cannot be deleted. 1-50 1.14.4 Symbol Display Displaying Defined Symbols: The SYMBOL command can be used to display either all the symbols or a specific symbol. This command displays the symbol name, its address, and its attribute. During Disassembly: When there are symbols that correspond to labels and operands of absolute addressing modes (PC relative, absolute address), the symbols are displayed. Symbols corresponding to immediate data and displacement are not displayed. If the symbol name exceeds 50 characters, the nest is displayed without the front parts. When abbreviated forms are defined, the abbreviated symbol names appear in the display. When multiple symbols are defined at the same address, only one of them will appear in the display. 1.15 Assembly Function 1.15.1 Overview User memory Writing to memory ASSEMBLE command Assembly-language source input Figure 1-31 Assembly Function The ASSEMBLE command enables line assembly as shown in figure 1-31. * Line assembly: Assembly-language source code is input from the console and assembled one line at a time. Refer to section 7.2.4, ASSEMBLE, for command initiation instructions. 1-51 1.15.2 Instruction Format The basic instruction format is as follows. [<label name>]<instruction mnemonic>[<operand>,...][;<comment>] (RET) <label name>: A label name is a character string of up to 32 characters. Any character used in symbol names can be used, but lower case characters cannot be used. The label name must start in the first column. <instruction mnemonic>: Any instruction mnemonic described in the H8/300H-Series Programming Manual and any assembler directive listed in table 1-9 can be used. <operand>: Any mnemonic described in the H8/300H-Series Programming Manual can be used (table 1-10). <comment>: A character string after a semicolon (;) is considered to be a comment. [ ]: Items within square brackets ([ ]) can be omitted. However, some <operand> values for specific instructions are required. : Indicates a space. Notes: 1. If no instruction operation size is specified, byte (B) is assumed. 2. Continuation lines cannot be input. 3. The default for radix of constants is set by the RADIX command. Note that, if the specified radix is hexadecimal (specified by H), the characters A to F are considered to be numbers and cannot be used in a label name without other alphabetic characters. 1-52 Table 1-9 Assembler Directives Directive Operand Description .DATA[.s] <value>[,<value>...] * Reserves an area for initialized fixed-length data. The type of units of area reserved for each value is given by s: B (byte), W (word), or L (long). Default size is B. * If any <value> exceeds the capacity of the size code (s), an error occurs. * A line can contain up to 40 bytes. .RES[.s] <value> * Reserves a specified number (<value>) of areas for specified-length (s) data. The type of units of area reserved for each value is given by s: B (byte), W (word), or L (long). Default size is B. * Up to 16 Mbytes of area can be reserved at one time. 1-53 Table 1-10 Operand Description Format Addressing Mode ERn Register direct ERn: General register name (32 bits) (SP can be specified instead of ER7) En: General register name (16 bits) (SP can be specified instead of E7) Rn: General register name (16 bits) (SP can be specified instead of R7) RnH: General register name (high-order 8 bits) RnL: General register name (low-order 8 bits) CCR: Condition code register @ERn Register indirect ERn: General register name @(disp[:Sd],ERn) Register indirect with displacement disp: Displacement value Sd: Displacement size 16: 16 bits (default) 24: 24 bits ERn: General register name #xxxxxxxx[:Si] Immediate data @aaaaaa[:Sa] Absolute address @ERn+ Register indirect with post-incrementation ERn: General register name @-ERn Register indirect with pre-decrementation ERn: General register name @@aa[:Sa] Memory indirect aaaa[:Sa] Program counter relative En Rn RnH RnL CCR Remarks xxxxxxxx: Immediate data value Si: Immediate data size (8: 8 bits, 16: 16 bits, 32: 32 bits) Default size depends on the value or instruction. aaaaaa: Absolute address Sa: Absolute address size (8: 8 bits, 16: 16 bits, 24: 24 bits) Default size depends on the value or instruction. aa: Absolute address Sa: Absolute address size 8: 8 bits (default) aaaa: Address (Only usable in BRA, BRN, Bcc, and BSR instruction) Sa: Absolute address size 8: 8 bits (default in normal mode) 16: 16 bits (default in advanced mode) Notes: 1. Symbols or expressions (addition or subtraction) can be specified as address, immediate, and displacement values. However, only address values can be disassembled and displayed. 2. If immediate data do not match the operation size, an error will occur. 1-54 1.15.3 Definition of Label Names as Symbols The names of labels in the assembly-language code are all registered as symbols, which may be used in each command. In line assembly, a symbol name cannot be defined if this has already been done. Symbol table Source file ASSEMBLE Added Figure 1-32 Label Name Definition The maximum number of labels is 1,024. However, if symbols have been already registered, this figure is smaller. 1.15.4 Label Name Reference A label name can be referred by specifying it in an operand field in an assembly-language source statement. Label names are referenced in the following addressing modes: * * * * PC relative addressing mode: For instructions BRA, BRN, Bcc, and BSR Absolute addressing mode: For instructions other than above Immediate data Displacement Forward reference is possible, but if 128 or more forward-reference labels remain unresolved, an error occurs. Label names can be referred to without ! within one ASSEMBLE command execution, but labels previously defined must be preceded by ! when referred to in another ASSEMBLE command. However, 3-bit immediate data must always be preceded by !. Moreover, for 3-bit immediate data, symbol value must be registered in advance. When a disassembled program is displayed, immediate data and displacement are not displayed in symbol form. 1-55 1.15.5 Disassembly The emulator has a disassembly function to display user program contents in mnemonics. This function is performed with the DISASSEMBLE command and enables to debug without referring a program list. For details, refer to section 7.2.14, DISASSEMBLE. 1-56 Section 2 Differences between the MCU and the Emulator 2.1 Flash Memory (H8/3048F) The emulator includes substitute RAM for flash memory. When an H8/3048F MCU that contains flash memory is used in mode 5, 6, or 7 that supports flash memory, this substitute RAM is accessed if an attempt is made to access flash memory. This leads to the following differences between the H8/3048F MCU and the emulator. For flash memory access program, refer to the programming example described in the MCU hardware manual. 2.1.1 On-Board Programming Modes Two on-board programming modes are available: boot mode and user program mode. Boot Mode: The EXECUTION_MODE (EM) command and an option for the GO command enable boot-mode execution. The MD2 pin of the MCU in the emulator is not connected to the user interface cables, and therefore, 12 V applied from the user system does not affect emulator operation. Because the emulator accesses the substitute RAM instead of flash memory, boot-mode execution time and the erasing program in the boot program area differ from those of actual flash memory. User Program Mode: Write and erase operation is enabled by applying 12 V to the Vpp pin directly from the user system or by applying 12 V from the E7000 using the EXECUTION_MODE (EM) command. However, the following register settings are invalid in the emulator and do not affect operation although the registers can be read and written to. * * * Flash memory control register (FLMCR) Erase block register 1 (EBR1) Erase block register 2 (EBR2) The emulator accesses the substitute RAM, and therefore cannot detect errors in the flash memory. 2.1.2 Flash Memory Operating Modes The flash memory in the H8/3048F has five operating modes: program mode, program-verify mode, erase mode, erase-verify mode, and prewrite-verify mode. In each mode, there are differences between the H8/3048F and the emulator. The emulator does not support the function for emulating flash memory by the RAM in the H8/3048F. Program Mode: In the H8/3048F, about 10 to 20 s is required to write to flash memory. In the emulator, however, data can be written in the same way as writing to RAM, that is, for 10 s or less. Therefore, generate the time required to write to flash memory by using a software timer. 2-1 Program-Verify Mode: The H8/3048F requires a wait time of 2 s to read the flash memory in program-verify mode after setting the program-verify mode. However, the emulator does not require this wait time. Therefore, generate the time required to read flash memory by using a software timer. Erase Mode: The emulator does not support erase mode. In the emulator, therefore, data is not converted into H'FF even if the erase mode is specified; the erase-verify mode is recommended because data is converted into H'FF by a dummy write of H'FF in this mode after erase mode. Erase-Verify Mode: The H8/3048F requires a wait time of 2 s to read the flash memory in eraseverify mode after setting the erase-verify mode. However, the emulator does not require this wait time. Therefore, generate the time required to read flash memory by using a software timer. The emulator does not support the prewrite operation (in which the inverted contents of a memory address are written back to it, making the data H'00). In the emulator, inverted data is written instead. To perform a prewrite, break program execution, fill the area with H'00 using the FILL command, and then re-execute the program, or write H'00 instead of inverted data. In the emulator, EBR1 and EBR2 settings are invalid, and the blocks other than those selected by EBR1 and EBR2 can be erased. Prewrite-Verify Mode: The H8/3048F requires a wait time of 2 s to read the flash memory in prewrite-verify mode after setting the prewrite-verify mode. However, the emulator does not require this wait time. Therefore, generate the time required to read flash memory by using a software timer. The emulator does not support the prewrite operation (in which the inverted contents of a memory address are written back to it, making the data H'00). In the emulator, inverted data is written instead. To perform a prewrite, break program execution, fill the area with H'00 using the FILL command, and then re-execute the program, or write H'00 instead of inverted data. Flash Memory Emulation by MCU RAM: The emulator does not support this function, and does not have the RAM control register (RAMCR). 2-2 2.2 Register Values at Reset The emulator partially initializes the general and control registers when starting the system or when resetting the MCU with the command (when switching the clock with the CLOCK command, or resetting with the RESET command). In particular, note that the ER7 register value is changed as shown in table 2-1. Table 2-1 Differences between the MCU and the Emulator Status Register name Emulator MCU Emulator power-on PC Vector address Vector address CCR 10000000 1******* ER0 to ER6 H'0000 Undefined ER7 Internal I/O start address - 2 Undefined PC Vector address Vector address CCR 10000000 1******* Reset by command Note: * indicates an undefined value. 2.3 User Interface The pull-up resistors and buffers used in the user system interface of the emulator will cause propagation delays and will cause high-impedance signals to become high. Adjust the hardware accordingly. Refer to section 5, User System Interface Circuit, for more details. 2.4 Crystal Oscillator A crystal oscillator can be installed in the emulator pod. Note that the crystal oscillator must be used within the range 8 to 18 MHz. For other ranges, input an external clock to the EXTAL pin. 2.5 Load Capacitance The load capacitance in the emulator and user system interface cables is larger than that of the actual MCU. Insert a buffer in the user system interface for any signal whose capacitance is large in the user system. 2-3 Section 3 MCU Function Support The emulator supports the H8/3048 series and the H8/3048F. The H8/3048 series includes the H8/3048, H8/3047, and H8/3044. The H8/3048F has the same functions as the H8/3048 except that it has flash memory instead of internal ROM. The H8/3048 series and H8/3048F have seven operating modes. These operating modes are supported by the emulator as described below. 3.1 Setting the MCU Operating Mode The MCU type and operating mode can be set as follows using the MODE command. Each MCU operating mode can be set by mode setting pins (MD0 to MD2) as shown in table 3-1. In the emulator, the desired operating mode can be set regardless of the setting of the mode setting pins on user system. The emulator can also read the mode setting pin status of the user system without affecting the emulator MCU operating mode. Table 3-1 H8/3048-Series and H8/3048F MCU Operating Modes Operating Mode MD2 MD1 MD0 H8/3048 Series H8/3048F Mode 0 0 0 0 -- -- Mode 1 0 0 1 Expanded 8-bit bus, 1-Mbyte space Expanded 8-bit bus, 1-Mbyte space Mode 2 0 1 0 Expanded 16-bit bus, 1-Mbyte space Expanded 16-bit bus, 1-Mbyte space Mode 3 0 1 1 Expanded 8-bit bus, 16-Mbyte space Expanded 8-bit bus, 16-Mbyte space Mode 4 1 0 0 Expanded 16-bit bus, 16-Mbyte space Expanded 16-bit bus, 16-Mbyte space Mode 5 1 0 1 Expanded 8-bit bus, 1-Mbyte space with ROM Expanded 8-bit bus, 1-Mbyte space with flash memory Mode 6 1 1 0 Expanded 8-bit bus, 16-Mbyte space with ROM Expanded 8-bit bus, 16-Mbyte space with flash memory Mode 7 1 1 1 Single-chip advanced mode Single-chip advanced mode The MCU type and operating mode previously set is saved to the configuration file on the emulator system disk. When initializing with this disk, the emulator initiates the system with the MCU type and operating mode specified with the MODE command. When the operating mode is set with the MODE command, the emulator system program terminates and must be restarted. 3-1 3.2 Memory Space The MCU has a maximum memory space of 16 Mbytes, within which memory can be set in units of 128 kbytes (in units of 1 Mbyte on an optional emulation memory board). U: User system memory S: Standard emulation memory E: Optional emulation memory A write-protected area and an access-prohibited (guarded memory) area can be allocated to memory in minimum units of 128 kbytes (in units of 1 Mbyte on an optional emulation memory board). W: Write-protected G: Access-prohibited The above attribute settings are valid in external memory area only; they are invalid in the internal ROM, flash memory, internal RAM, and internal I/O area. 3.2.1 Internal ROM Area The emulator includes substitute RAM for the MCU internal ROM. In operating modes including internal ROM, the substitute RAM is accessed if an attempt is made to access the internal ROM, regardless of the MAP command attribute settings. In addition, the internal ROM area access differs between user program execution and the emulator commands. * Access in user program execution: Read only, write disabled (program is terminated if attempted.) * Access with the emulation command: Read/write enabled Therefore, the internal ROM contents can be changed or an object program can be loaded using commands such as MEMORY and LOAD, but they cannot be rewritten from the user program. If this is attempted, the user program is terminated. The internal ROM area is accessed in two states. 3-2 3.2.2 Internal RAM Area The emulator includes substitute RAM for the MCU internal RAM. If the internal RAM is enabled, this substitute RAM is accessed if an attempt is made to access the internal RAM, regardless of the MAP command attribute setting. In addition, the user program is not terminated even if the internal RAM area is written to or accessed by the user program while the attribute setting is write-protected (attribute W) or access prohibited (attribute G). To break the user program when the internal RAM area is written to or accessed, use the BREAK_CONDITION1, 2, 3, 4 commands. The internal RAM area can be accessed in the user program and with the emulator command, and can be accessed in two states. If the internal RAM area is disabled, it is used as an external area. 3.2.3 Internal I/O Area If an attempt is made to access the internal I/O area, the internal I/O area in the MCU installed in the emulator is accessed regardless of the memory attribute set with the MAP command. In addition, the user program is not terminated even if the internal I/O area is written to or accessed by the user program while the attribute setting is write-protected (attribute W) or access prohibited (attribute G). To break the user program when the internal I/O area is written to or accessed, use the BREAK_CONDITION1, 2, 3, 4 commands. The internal I/O area can be read from or written to by the user program or with emulator commands. When writing to the internal I/O area with an emulator command (MEMORY command), the following warning message is displayed and the emulator starts writing without verifying. *** 86: INTERNAL AREA 3.2.4 Unusable Area In the emulator, emulation memory can be allocated to the unusable area in single-chip normal mode and single-chip advanced mode. In this case, this area can be read from or written to by the user program or with emulator commands. If the emulation memory is write-protected, the user program is terminated if this area is written to in the user program. Such areas can be used as work memory for debugging the user program, but they cannot be accessed in the actual MCU. After debugging is completed, change the program so as not to access unusable areas. The default memory attribute of these areas is guarded (access-prohibited) at emulator initiation. 3.2.5 External Memory Area The MCU external memory area can be set with all memory attributes that the emulator supports. Memory corresponding to the allocated attributes can be accessed by the user program or with emulator commands. 3-3 3.2.6 Reserved Areas In the emulator, emulation memory can be allocated to reserved areas, which can be accessed by either user programs or emulator commands. If the emulation memory attribute is set to writeprotected, however, user program execution stops when this area is written to by the user program. Such areas can be used as work memory for debugging the user program, but they cannot be accessed in the actual MCU. After debugging is completed, change the program so as not to access reserved areas. Reserved areas are accessed in the same way as external memory areas, that is, through an 8-bit bus in three states. 3.2.7 Flash Memory Area The emulator includes substitute RAM for the H8/3048F flash memory. In operating modes supporting flash memory, the substitute RAM is accessed if an attempt is made to access the flash memory area, regardless of the MAP command attribute setting. The flash memory area can be accessed during user program execution and by means of emulator commands as follows: * Access by user program when 12 V is not applied to Vpp: Data can be read but cannot be written to. User program execution does not stop. * Access by user program when 12 V is applied to Vpp: Data can be read and written to. * Access by emulator commands: Data can be read and written to. Therefore, with the MEMORY or LOAD command, the contents of the flash memory area can be changed or object programs can be loaded into the flash memory area. However, the contents cannot be changed by a user program when 12 V is not applied to Vpp; if writing of data is attempted by the user program in such a case, no error message will be displayed. The flash memory area is accessed in two states. Note: 12 V is applied to Vpp in two ways: one is applying 12 V directly from the user system to the Vpp pin, and the other is using the EXECUTION_MODE (EM) command to apply 12 V from the E7000. 3-4 3.3 Low-Power Modes (Sleep, Hardware Standby, and Software Standby) For reduced power consumption, the MCU has sleep, hardware standby, and software standby modes. 3.3.1 Hardware Standby Mode Hardware standby mode is switched by the STBY signal input. However, since the STBY signal from the user system is not input to the MCU in the emulator, the emulator does not support this mode. The STBY signal status can be monitored by the user. 3.3.2 Sleep and Software Standby Modes These modes are switched by executing the SLEEP instruction, and they are cleared by break condition matching (including break key input) as well as by normal clear sources, and program breaks. Trace information is not acquired during these modes. Notes: 1. When restarting after a break, the user program will restart at the instruction following the SLEEP instruction. 2. During sleep mode, if the user accesses or modifies the memory in parallel mode, the sleep mode is cleared and the user program execution continues from the instruction following the SLEEP instruction. 3.4 Interrupts During emulation, the user can interrupt the MCU. If an interrupt occurs while the emulator is waiting for command input, the interrupt is not processed. However, if an edge sensitive interrupt occurs while the emulator is waiting for command input, the emulator latches the interrupt and executes the interrupt processing routine when the GO command is entered. 3.5 Control Input Signals (RES, WAIT, BREQ) The MCU control input signals are RES, WAIT, and BREQ. The RES signal is valid only during emulation with the GO command. The WAIT and BREQ signals are valid during emulation with the GO, STEP, or STEP_OVER command. Therefore, while the emulator is waiting for command input, the user cannot input RES, WAIT or BREQ signals to the MCU. BREQ signals can be masked using the EXECUTION_MODE command. 3-5 3.6 Watchdog Timer (WDT) The WDT only operates during emulation (by the GO, the STEP, or the STEP_OVER command), and does not operate when the emulator is waiting for command input. The timer stops at a break and restarts when emulation resumes. 3.7 Integrated Timer Pulse Unit (ITU) and Programmable Timing Pattern Controller (TPC) The ITU and TPC operate during the command input wait state as well as during emulation. Even if the user program has stopped when a break condition is satisfied after the user program has been started with the GO command, the ITU and TPC continue to operate. Therefore, the timer pins are valid even when the user program has stopped. The user can rewrite the timer registers with the MEMORY command. 3.8 Serial Communications Interface The serial communications interface signals are connected to the user system directly from the MCU on the emulator. Therefore, the interface is valid during the emulator command input wait state as well as during emulation. For example, when writing data to the transmit data register (TDR) with the MEMORY command, data is output to the TXD line after the serial communication interface output has been prepared. 3.9 DMAC The DMAC operates during the command input wait state as well as during emulation. When a transfer is requested, the DMAC executes a DMA transfer. 3.10 Wait State Controller The MCU wait state controller has a programmable wait mode and a WAIT pin input mode. The programmable wait mode is valid when the emulation memory or user external memory is accessed, but input to the user WAIT pin is only valid when user external memory is accessed. However, the EXECUTION_MODE command can be used to enable input to the user WAIT pin during emulation memory access cycles. The input to the user WAIT pin is always enabled during refresh cycles. 3.11 I/O Port The MCU I/O port can be used as peripheral module input/output pins or as an address/data bus. It is specified as I/O port pins according to the operating mode or internal register settings. The I/O port pins are also valid in the emulator command input wait state during emulation. The I/O pins can be read from and written to by the MEMORY command. 3-6 3.12 A/D and D/A Converters Analog I/O pins are directly connected to the user system from the MCU installed in the emulator. Therefore, they are valid in the emulator command input wait state as well as during emulation. The A/D and D/A converters also have AVcc, AVss, Vref, and ADTRG pins. Because these converters operate with a special power supply, connect AVcc (power supply pin) and Vref (reference voltage pin) to the A/D and D/A conversion power supply and the reference power supply on the user system. When not using the A/D and D/A converters, connect the AVcc and Vref pins to Vcc. 3.13 Refresh Controller The refresh controller always operates in the emulator. Refresh cycles are executed even in the emulator command input wait state. However, the emulator does not support battery back-up mode. Note that data in the DRAM will be lost if the battery back-up mode is entered. 3.14 Clock Pulse Generator The division ratio (1/1, 1/2, 1/4, or 1/8) of the clock pulse generator can be changed using the frequency divider during operation. Select the appropriate division ratio within the clock cycle time (tcyc) range guaranteed by the AC timing specifications for electrical characteristics. 3-7 Section 4 User System Interface Circuit The emulator is connected to the user system via user system interface cable. Probe signal trace and break is enabled by connecting the eight external probes to the user system. User System Interface Circuits: The circuits that interface the MCU in the emulator to the user system include buffers and resistors, as described below. When connecting the emulator to a user system, adjust the user system hardware compensating for FANIN, FANOUT, and propagation delays. Tables 4-1 and 4-2 show the bus timing specifications when using the emulator. Figures 4-1 to 4-4 show their timing charts, and figures 4-5 shows the user interface circuits. Table 4-1 Bus Timing (Reference Value at 5-V and 18-MHz Operation) Parameter MCU Specification (ns) Emulator Specification (ns) tRDS 15 (min) 39 (typ) tACC1 50 (max) 37 (typ) tACC2 105 (max) 93 (typ) tACC3 20 (max) -5 (typ) tACC4 80 (max) 50 (typ) Table 4-2 Refresh Controller Bus Timing (Reference Value at 5-V and 18-MHz Operation) Parameter MCU Specification (ns) Emulator Specification (ns) tRAH 20 (min) 8 (typ) tRAC 70 (max) 55 (typ) tAA 45 (max) 39 (typ) tCAC 25 (max) 16 (typ) tWDS3 40 (min) 20 (typ) Adjust user system hardware considering the above bus timing conditions. 4-1 T1 T2 T3 tcyc tCH tCL tCR tCF tAD A 23 -A 0 CS7 -CS 0 tASD tACC3 (2 states) tACC4 (3 states) tSD tAH tACC3 (2 states) tACC4 (3 states) tSD tAH AS tAS1 tASD RD (Read) tAS1 tRDH tRDS tACC1 D15 -D0 (Read) HWR,LWR (Write) tASD tAH tSD tAS1 tWSW1 tWDH tWDS1 D15 -D0 (Write) Note: In a 2-state cycle, T3 state is omitted. Figure 4-1 Basic Bus Cycle Timing in Expanded Mode T1 T3 TW T2 t WTH t WTS t WTH t WTS WAIT Figure 4-2 1-Wait Inserted Bus Cycle Timing 4-2 T1 T2 T3 tAD tAD A 23 -A 0 CS7 -CS 0 AS tASD RD (Read) tRAD3 tRAH tAS1 tASD tSD tCAS CS3 (CAS) tAS1 HWR (UW), LWR (LW), (Read) tRAH tASD tAA tSD tCAC HWR (UW), LWR (LW), (Write) tWDH RFSH tRDS D15 -D0 (Read) tWDS3 D15 -D0 (Write) Figure 4-3 DRAM Read/Write Cycle Timing (2WE Mode) 4-3 tRDH T1 T2 T3 A 23 -A 0 tASD tSD AS tRAD3 tCRS CS3 (RAS) tRAD2 tASD tSD RD (CAS) HWR (UW), LWR (LW), RFSH tRAD3 tRAD2 tCSR Figure 4-4 DRAM Refresh Cycle Timing (2WE Mode) 4-4 User system MCU AVCC AVCC 0.022 Vref Vref 0.022 P77/AN7/DA1 P76/AN6/DA0 P75-70/AN5-0 P77/AN7/DA1 P76/AN6/DA0 P75-70/AN5-0 AVSS AVSS UVCC P83/CS1/IRQ3 P82/CS2/IRQ2 P81/CS3/RAS/IRQ1 P80/RFSH/IRQ0 P94/SCKO/IRQ4 P95/SCK1/IRQ5 47 k 47 ABT16373 P83/CS1/IRQ3 P82/CS2/IRQ2 P81/CS3/RAS/IRQ1 P80/RFSH/IRQ0 P94/SCKO/IRQ4 P95/SCK1/IRQ5 UVCC 47 k 47 P84 P93-90 PA7-A0 PB7-B0 P84 P93-90 PA7-A0 PB7-B0 AQW614A RESO ACT04 (Relay) 0.01 Note: RESO 4.7 k 1 k UVCC is either of the following: * User system VCC when the user system is connected via the user system interface cables * 5-V emulator power when the user system interface cable is not connected Figure 4-5 User Interface Circuit 4-5 MCU User system UVCC HG62G027 47 k P53-50/A19-16 P27-20/A15-8 P17-10/A7-0 47 P53-50/A19-16 P27-20/A15-8 P17-10/A7-0 UVCC UVCC 4.7 k HG62G027 47 k 47 P37-30/D15-8 P47-40/D7-0 P37-30/D15-8 P47-40/D7-0 UVCC 47 k 47 P66/LWR/LW/LCAS P65/HWR/UW/UCAS P64/RD/CAS/WE P63/AS P66/LWR/LW/LCAS P65/HWR/UW/UCAS P64/RD/CAS/WE P63/AS UVCC 47 k 47 P62/BACK P61/BREQ P60/WAIT ABT16373 P62/BACK P61/BREQ P60/WAIT UVCC ABT16373 HD151015 EXTAL 47 k 47 EXTAL EPM7128 XTAL Notes: NC 1. UVCC is either of the following: * User system VCC when the user system is connected via the user system interface cables * 5-V emulator power when the user system interface cable is not connected 2. EPM7128 is an EPLD manufactured by Altera Corporation. 3. The emulator and the user system interface cables have load capacitance. If the load capacitance on the user system is larger, connect EXTAL through a buffer. Figure 4-5 User Interface Circuit (cont) 4-6 (VCC) MCU User system UVCC ABT16244 47 k 47 UVCC HD151015 47 k 47 ACT16244 MD1-MD0 MD1-MD0 UVCC HD151015 ACT04 ACT04 1.5 k MD2 MD2 6.8 k AQV251A User VCC UVCC (VCC) HG62G027 0.022 0.022 GND UVCC 47 k 47 ABT16646 External probe EXT8-1 UVCC HD151015 Notes: 47 k 47 Trigger output probe 1. UVCC is either of the following: * User system VCC when the user system is connected via the user system interface cables * 5-V emulator power when the user system interface cable is not connected 2. (VCC) is 5-V emulator power supplied from the E7000 or E7000PC. 3. User VCC is the user system power supply. Figure 4-5 User Interface Circuit (cont) 4-7 MCU User system UVCC 47 k 47 ACT14 ACT14 HD151015 RES RES AC11 AC32 UVCC UVCC ACT16373 47 k 47 STBY STBY ACT16652 HG62S058 UVCC HD151015 NMI Note: HC375 Q ACT14 ACT14 D 47 k 47 NMI UVCC is either of the following: * User system VCC when the user system is connected via the user system interface cables * 5-V emulator power when the user system interface cable is not connected Figure 4-5 User Interface Circuit (cont) 4-8 Section 5 Troubleshooting The emulator internal system test checks the emulator's internal RAM and registers at power-on (emulator monitor initiation) and at system program initiation. Section 5.1 describes the emulator internal system test when using the E7000 emulator (HS7000EST01H), and section 5.2 describes the test when using the E7000PC emulator (HS7000ESTP1H). 5.1 Internal System Test Using the E7000 Internal System Test at Power-On: The E7000 checks its internal RAM and registers at power-on. While tests are in progress, the following messages are displayed: E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. (a) TESTING RAM 0123 (b) ** E7000 SYSTEM LOADING ** *** FD NOT READY (c) START E7000 S : START E7000 R : RELOAD & START E7000 B : BACKUP FD F : FORMAT FD L : SET LAN PARAMETER T : START DIAGNOSTIC TEST (S/R/B/F/L/T) ? (d) (a) E7000 monitor start message (b) Internal RAM and registers are being tested. * A number from 0 to 3 is displayed as each of the four internal RAM blocks has been tested. If an error occurs, the address, write data, and read data are displayed as follows: ** RAM ERROR ADDR=xxxxxxxx W-DATA=xxxxxxxx R-DATA=xxxxxxxx 5-1 * After RAM testing is completed, the registers are tested. If an error occurs, the following message is displayed: *** xxxx REGISTER ERROR W-DATA=xx R-DATA=xx xxxx: Name of E7000 internal register where an error occurs (c) E7000 system program is being loaded. If the E7000 system disk is not inserted, the E7000 monitor enters command input wait state. (d) The E7000 monitor is in command input wait state. Note: Operation continues even if an error occurs in step (b) or (c), but the error should be investigated according to section 5.3, Troubleshooting Procedure, without loading the E7000 system program. Internal System Test at E7000 System Program Initiation: The E7000 system performs internal system tests, mainly on the E7000 registers, at its initiation. ** E7000 SYSTEM LOADING ** H8/xxxx E7000 (HSxxxxEPD70SF) Copyright (C) Hitachi, LTD. 19xx Licensed Material of Hitachi, Ltd. Vn.m CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz MCU NAME = H8/xxxx MODE = x PIN = xxx (MDx-x = x)(h) FAILED AT xxxx REMAINS EMULATION MEMORY S = xxxxxx/E = xxxxxx (j) WARM OR COLD START filename : WARM START return : COLD START (file name / return) ? (a) (b) (c) (d) (e) (f) (g) (i) (k) 5-2 (a) E7000 system program start message. Vn.m indicates the version number. (b) Configuration file is being loaded. If an invalid configuration file is assigned, the following message is displayed: *** 54:INVALID CONFIGURATION FILE If no configuration file is contained in the system disk, the following message is displayed: *** 55:CONFIGURATION FILE NOT FOUND At this time, an unavailable system disk is inserted. Change system disks and re-execute. (c) IP address information file for the host system connected via the LAN interface is being loaded. If an invalid IP address information file is assigned, the following message is displayed. LAN I/O ERROR (E0xx) socket library error n: <error message> xx: Current processing (refer to table 12-6 in section 12, Error Messages) n: Error code (refer to table 12-5 in section 12, Error Messages) <error message>: Refer to table 12-5 in section 12, Error Messages If an error message that is not shown in table 12-5 in section 12, Error Messages, is displayed, the error may have occurred in the host system connected via the FTP interface. Also check the host system. (d) The E7000 control registers are being checked. If an error occurs, one of the following messages is displayed. ** xxx REGISTER ERROR W-DATA = xxxx R-DATA = xxxx ** BREAK MEMORY ERROR ADDR = xxxx W-DATA = xxxx R-DATA = xxxx ** SHARED RAM ERROR ADDR = xxxxxx W-DATA = xxxxxxxx R-DATA = xxxxxxxx (i) (ii) (iii) (i) A write verification error occurred in one of the following E7000 internal registers: RAR, TCR, BQR, TSR, TBM (ii) An error occurred in break memory (iii) An error occurred in the shared RAM (e), (f) The emulator pod is being tested. If an error occurs, one of the following message is displayed. *** *** *** *** INVALID EMULATOR POD! EMULATOR POD NOT READY ! EMULATOR POD ERROR CODE=xx EMULATOR POD SYSTEM FILE NOT FOUND 5-3 (i) (ii) (iii) (iv) (i) The incorrect MCU emulator pod is connected. Please check the MCU type and use the appropriate E7000 system program, or exchange the emulator pod. (ii) The emulator pod is not connected correctly. Connect the emulator pod to the E7000 correctly. (iii) One of the following errors occurred in the emulator pod: xx: error code RE: An error occurred in the emulator pod work RAM RA: An error occurred in the shared RAM RM: An error occurred in the MCU installed in the emulator pod IO: An error occurred in the internal ROM substitute RAM IA: An error occurred in the internal RAM substitute RAM BK: The BREAK key was pressed, suspending operation (iv) System programs for the emulator pod are not loaded because the incorrect E7000 system program is installed. Insert the correct E7000 system disk and restart the E7000. Note: If the (CTRL) + C keys or (BREAK) key is pressed during emulator pod testing, the test is suspended (error code BK). (g) The MCU is reset, the clock is set, and the specified clock type is displayed ((g) is not executed if an error has occurred in step (d), (e), or (f)). (h) The MCU type, the operating mode, and the status of user system mode selection pins are displayed. (i) MCU pins are being checked. For details, refer to section 7.2.8, CHECK ((i) is not executed if an error has occurred in step (d), (e), or (f)). (j) The remaining emulation memory size that can be assigned. (k) The emulator pod system program is initiated. E7000 System Down: If an exception occurs during E7000 monitor or E7000 system program execution, the system shuts down, and the following message is displayed: <exception> PC=xxxxxx *** E7000 SYSTEM DOWN *** If an error occurs, re-execute using another system disk. If an error still occurs, inform a Hitachi sales agency of the error. 5-4 5.2 Internal System Test Using the E7000PC Internal System Test at Power-On: The E7000PC checks its internal RAM and registers at poweron. While tests are in progress, the following messages are displayed: E7000 MONITOR Vn.m Copyright (C) 19xx Hitachi, Ltd. Licensed Material of Hitachi, Ltd. (a) TESTING RAM 0123 (b) START E7000 S : START E7000 R : RELOAD & START E7000 L : DISPLAY LAN PARAMETER T : START DIAGNOSTIC TEST (S/R/L/T) ? (c) (a) E7000PC monitor start message (b) Internal RAM and registers are being tested. * A number from 0 to 3 is displayed as each of the four internal RAM blocks has been tested. If an error occurs, the address, write data, and read data are displayed as follows: ** RAM ERROR ADDR=xxxxxxxx W-DATA=xxxxxxxx R-DATA=xxxxxxxx * After RAM testing is completed, the registers are tested. If an error occurs, the following message is displayed: *** xxxx REGISTER ERROR W-DATA=xx R-DATA=xx xxxx: Name of E7000PC internal register where an error occurs (c) The E7000PC monitor is in command input wait state. Notes: 1. Operation continues if an error occurs in step (b), but the error should be investigated according to section 5.3, Troubleshooting Procedure, without loading the E7000PC system program. 2. After message (c) is displayed, enter S or R to load the E7000PC system program that has been installed according to the procedure described in section 3.4.2, Installation in Part II, E7000PC Guide. If the system program is not correctly loaded, an error message will be displayed. In this case, check the IBM PC settings. 5-5 Internal System Test at E7000PC System Program Initiation: The E7000PC system performs internal system tests, mainly on the E7000PC registers, at its initiation. ** E7000 SYSTEM LOADING ** H8/xxxx E7000 (HSxxxxEPDxxSF) Copyright (C) Hitachi, LTD. 19xx Licensed Material of Hitachi, Ltd. Vn.m CONFIGURATION FILE LOADING LAN IP ADDRESS FILE LOADING HARD WARE REGISTER READ/WRITE CHECK POD SYSTEM LOADING EMULATOR POD TEST ** RESET IN BY E7000 ! CLOCK = xx MHz MCU NAME = H8/xxxx MODE = X PIN = xxx (MDx-x = x) (h) FAILED AT xxxx REMAINS EMULATION MEMORY S=D'xxxxxx/E=xxxxxx WARM OR COLD START filename : WARM START return : COLD START (file name / return) ? (a) (b) (c) (d) (e) (f) (g) (i) (j) (k) (a) E7000PC system program start message. Vn.m indicates the version number. (b) Configuration file is being loaded. If an invalid configuration file is assigned, the following message is displayed: *** 54:INVALID CONFIGURATION FILE If no configuration file is contained in the specified directory, the following message is displayed: *** 55:CONFIGURATION FILE NOT FOUND When this message is displayed, an incorrect system program is installed. Install the correct E7000PC system program and restart the E7000PC. (c) IP address information file for the host system connected via the LAN interface is being loaded. If an invalid IP address information file is assigned, the following message is displayed. 5-6 (d) The E7000PC control registers are being checked. If an error occurs, one of the following messages is displayed. ** xxx REGISTER ERROR W-DATA = xxxx R-DATA = xxxx ** BREAK MEMORY ERROR ADDR = xxxx W-DATA = xxxx R-DATA = xxxx ** SHARED RAM ERROR ADDR = xxxxxx W-DATA = xxxxxxxx R-DATA = xxxxxxxx (i) (ii) (iii) (i) A write verification error occurred in one of the following E7000PC control registers: RAR, TCR, BQR, TSR, TBM (ii) An error occurred in break memory (iii) An error occurred in the shared RAM (e), (f) The emulator pod is being tested. If an error occurs, one of the following message is displayed. *** INVALID EMULATOR POD ! *** EMULATOR POD NOT READY ! *** EMULATOR POD ERROR CODE=xx *** EMULATOR POD SYSTEM FILE NOT FOUND (i) (ii) (iii) (iv) (i) The incorrect MCU emulator pod is connected. Please check the MCU type and use the appropriate E7000PC system program, or exchange the emulator pod. (ii) The emulator pod is not connected correctly. Connect the emulator pod to the E7000PC emulator correctly. (iii) One of the following errors occurred: xx: error code RE: An error occurred in the emulator pod work RAM RA: An error occurred in the shared RAM RM: An error occurred in the MCU installed in the emulator pod IO: An error occurred in the internal ROM substitute RAM IA: An error occurred in the internal RAM substitute RAM BK: The BREAK key was pressed, suspending operation (iv) The system program for the emulator pod is not loaded because the incorrect E7000PC system program is installed. Install the correct E7000PC system program and restart the E7000PC. Note: If the (CTRL) + C keys or (BREAK) key is pressed during emulator pod testing, the test is suspended (error code BK). 5-7 (g) The MCU is reset, the clock is set, and the specified clock type is displayed ((g) is not executed if an error has occurred in step (d), (e), or (f)). (h) The MCU type, the operating mode, and the status of user system mode selection pins are displayed. (i) MCU pins are being checked. For details, refer to section 7.2.8, CHECK ((i) is not executed if an error has occurred in step (d), (e), or (f)). (j) The remaining emulation memory size that can be assigned. (k) The emulator pod system program is initiated. E7000PC System Down: If an exception occurs during E7000PC monitor or E7000PC system program execution, the system shuts down, and the following message is displayed: <exception> PC=xxxxxx *** E7000 SYSTEM DOWN *** If an error occurs, re-install the E7000PC system program and restart the E7000PC. If an error still occurs, inform a Hitachi sales agency of the error. 5.3 Troubleshooting Procedure This section attempts to reduce the time taken by troubleshooting by providing a troubleshooting Problem Analysis Diagram (PAD, see figure 5-1). Note that the troubleshooting is limited to failures that the user can treat. As you work through the diagram: * Follow the instructions that request operator assistance or intervention. * Note that "system defect" means that the emulator station is malfunctioning. Execute the diagnostic program as described in the Diagnostic Program Manual (HS3048TM01ME), and inform a Hitachi sales agency of the test results in detail because a system defect may be caused by a number of reasons. 5-8 Yes Emulator system down? System defect No b Yes c b Emulator monitor message Yes displayed? Power lamp No on with power-on? No Check power supply START a (breaker, fuse, outlet) to emulator Yes Yes Console connected correctly? No c Breaker, fuse fails again Yes Yes d Defect in power supply or emulator power No a Power lamp defect Emulator fan working Internal system test at power-on passed? No No Connect correctly Yes Set power supply Failure occurred? No System defect Switch defect System defect Yes e d System program loaded correctly? Yes No One of the messages in note* displayed? Disk is not system disk: insert correct disk System disk load failed: use another Yes disk No FD I/O ERROR displayed? Yes No Emulator system failed? No Figure 5-1 Troubleshooting PAD 5-9 System disk may be faulty: use another system disk System defect Yes f e Internal system test at emulator system program initiation passed? System defect Yes No Register, break memory, shared RAM error? Emulator pod connected correctly? Yes Emulator pod error? System defect No No f Connect correctly Yes g Yes CHECK command passed? User system Yes connected? f Yes g No Emulator command input correctly? Yes CHECK command passed? No No System defect No Without user system, CHECK command passed? System defect Yes h g Yes Correct data transfer between emulator and host? Yes No h No System defect Correct protocol and baud rate for transfer between emulator and host system? No Host system connected and set up correctly? No User system defect Use correct protocol and baud rate Connect correctly END Note: If one of the following messages is displayed, check that the correct system disk is set: FD NOT SYSTEM FD CONFIGURATION FILE NOT FOUND INVALID CONFIGURATION FILE POD SYSTEM FILE NOT FOUND Figure 5-1 Troubleshooting PAD (cont) 5-10 System defect Section 6 Command Input and Display 6.1 Command Syntax 6.1.1 Command Input Format The emulator command format is as follows: <command><parameter>;<option> (RET) : Space (RET): (RET) key Note that each command can be specified in abbreviated form. 6.1.2 Help Function All emulator commands can be displayed by entering the HELP command. Any command input format can be displayed by specifying the command name as a parameter as part of the HELP command. * To display all emulator commands : HELP (RET) <All commands are displayed in their full names and abbreviations> * To display a command input format : HELP<command name> (RET) <A command input format is displayed> In this example, an abbreviation of the command name can be entered as <command name>. 6-1 6.1.3 Word Definition Constants, symbols, or file names can be entered as command parameters or options. Spaces () or commas (,) can be inserted between words. Words are described below: Constants: Numeric constants, character constants, and expression can be used as constants. * Numeric constants The following shows numeric constant formats. A radix is entered at the head of a numeric constant. S'nnnnnnnn S: Radix of a constant B: Binary O: Octal D: Decimal H: Hexadecimal (At emulator initiation) Default: Value specified with the RADIX command nnnnnnnn: Value based on the radix (4-byte value maximum) Example: To indicate 100 in decimal: D'100 If the radix is omitted, the radix specified with the RADIX command is automatically used. Example: If the radix is omitted while hexadecimal is specified with the RADIX command, entering 10 means H'10. * Character constants Enclosed with single or double quotation marks. If a single or double quotation mark is used as data, add two sequential quotation marks. For example, ' ' ' means the character constant ' (H'27). Example: ' A' means that H'41 has been input. Multiple characters can be included inside the quotation marks within the specified data size as shown below. Example: ' AB' means that H'4142 has been input. 6-2 * Expression An expression can be described using numeric constants, character constants, symbols, and operators. As an operator, + (addition ) or - (subtraction) can be specified. Examples: D'10 + H'20 20 - 4 -1 (H'2A) Symbols: There are two types of symbols; symbols defined with emulator's SYMBOL or ASSEMBLE command and that defined with an assembler or C compiler on a cross system. A basic format for each symbol type is shown below. * Symbols defined with emulator command !<symbol name> <symbol name>: A name defined by the emulator's SYMBOL command or ASSEMBLE command. Note that only the upper case characters can be defined by the ASSEMBLE command. * Symbols defined on a cross system These symbols are divided into two groups; a general symbol indicating a label name, variable name, or function name, and a line number symbol indicating an address of a line number of a C compiler listing file or an assembly listing file. -- General symbol (starts with !) !<unit name>/<symbol name>/.... -- Line number symbol (starts with &) &<unit name>/<line number> Examples: !prog/main !prog/_sub &test/100 For details, refer to section 1.11, Symbolic Debugging Function. 6-3 Notes on Using Symbols: 1. Do not use the following characters as symbols: ;:()/+-,.=?!& 2. A symbol name can contain up to 32 characters. 3. Only the externally defined labels used in the assembler or static symbols used in the C compiler can be defined. 4. Uppercase letters and lowercase letters are distinguished. However, in the ASSEMBLE command, a symbol in lowercase letters cannot be defined. * File name A file name can be specified as a command parameter. The general file name format is as follows: <drive name>:<file name>.<extension> Note that the drive name is specified only in the FILE_COPY command when a file is copied to another floppy disk. For details, refer to section 8.3, Files. 6.2 Special Key Input The emulator supports special key functions to facilitate keyboard operations. In the following description, CTRL + X means pressing the CTRL and X keys simultaneously. 6.2.1 Command Execution and Termination * Command execution (RET) Enters all characters on that line, regardless of the cursor position, and executes the command. * Command termination CTRL + C (BREAK) Aborts command execution. All characters typed so far are lost and the emulator enters command input wait state. 6-4 6.2.2 Display Control * Display stop CTRL + S Temporarily stops display. Resumes display by entering CTRL and Q keys. * Display restart CTRL + Q Restarts display. * Display the previous 16 lines CTRL + P Effective only for the DUMP and TRACE commands. Displays the 16 lines before the first line of the current screen and then stops. Pressing the (RET) key restarts the display. 6.2.3 Command Re-entry * Display last entered line CTRL + L Redisplays the last line entered. Pressing these keys will repeatedly redisplay up to 16 lines and then returns to the last line again. * Display last entered command parameters <command name> . When a period is entered after a command, the previously input parameters of that command are displayed. If two periods are entered after a command, parameters of two commands prior to the entered command are displayed. This key input is useful for executing commands with the same options again. (Example) :D 1000 1010 (RET) : Execution of other command :D.(RET) :D 1000 1010 Displays the parameters specified in the DUMP command and enters command input wait state. 6-5 6.2.4 Cursor Control and Character Editing * Move cursor backwards CTRL + H Moves the cursor one position backwards. * Move cursor to word starting position CTRL + T Moves the cursor to the first position of the word (the first position to the right of the previous space or the character following the space). * Delete one character CTRL + D Deletes a character at the cursor position. * Cancel line CTRL + X Deletes the contents of the entire line. * Advance cursor CTRL + W Moves the cursor one position forwards. * Insert space CTRL + U Inserts a space at the cursor. * Tab CTRL + I Moves the cursor to the next (multiple of 10) + 1 column. 6-6 Section 7 Emulation Commands 7.1 Overview The emulator provides a wide range of functions such as break, trace, performance analysis, and coverage. Table 7-1 lists the emulation commands that enable these functions. Table 7-1 Emulation Commands Command Function Usable/Unusable in Parallel Mode .<register> Modifies and displays register contents Unusable !<symbol> or &<symbol> Displays symbol value Usable ABORT Terminates emulation in parallel mode Usable ASSEMBLE Assembles a program line Unusable BREAK Sets, displays, and cancels PC breakpoints Only display function is available BREAK_CONDITION1, 2,3,4 Sets, displays, and cancels hardware break condition Unusable BREAK_SEQUENCE Sets, displays, and cancels PC breakpoints with pass sequence specification Only display function is available CHECK Tests MCU pin status Unusable CLOCK Sets and displays clock Only display function is available COMMAND_CHAIN Inputs emulator commands from a file (only for E7000) Usable CONVERT Converts data Usable DATA_CHANGE Replaces memory data Unusable DATA_SEARCH Searches for memory data Unusable DISASSEMBLE Disassembles and displays memory contents Usable DISPLAY_COVERAGE Displays coverage trace results Unusable DUMP Displays memory contents Usable END Cancels parallel mode Usable EXECUTION_MODE Specifies and displays execution mode Unusable FILL Writes data to memory Unusable GO Executes realtime emulation Unusable HELP Displays all commands and command format Usable HISTORY Displays all commands to be input Usable ID Displays the emulator program version number Usable LED1,2,3,4 Specifies, displays, and cancels memory content display on LEDs Usable 7-1 Table 7-1 Emulation Commands (cont) Usable/Unusable in Parallel Mode Command Function LED_OUT1,2 Specifies and displays analog output of LED display data Usable MAP Specifies and displays memory attribute Unusable MEMORY Modifies and displays memory contents Usable MODE Specifies and displays the MCU operating mode Unusable MOVE Transfers memory contents Unusable MOVE_TO_RAM Moves ROM contents to emulation memory Unusable PERFORMANCE_ ANALYSIS Specifies, deletes, initializes, and displays performance measurement data Unusable PRINT Sets or cancels output device for command result display (only for E7000) Usable QUIT Terminates emulator system program Unusable RADIX Specifies and displays radix for numeric input Usable REGISTER Displays register contents Unusable RESET Resets MCU Unusable RESULT Displays execution results Unusable SET_COVERAGE Initializes the coverage trace function Unusable SHORT_SYMBOL Defines a short format for a symbol and displays current symbol definition Usable STATUS Displays emulator execution status Usable STEP Performs single-step execution Unusable STEP_INFORMATION Specifies and displays information during single-step execution Unusable STEP_OVER Performs single-step execution except for subroutines Unusable SYMBOL Defines, displays, or deletes symbols Usable TRACE Displays trace buffer contents Usable TRACE_CONDITION Specifies, displays, and cancels trace conditions Usable TRACE_MEMORY Specifies, displays, and cancels trace data address Usable TRACE_MODE Specifies and displays trace acquisition mode Unusable TRACE_SEARCH Searches for and displays trace information Usable 7-2 7.2 Emulation Commands This section provides details of emulation commands in the format shown in figure 7-1. Sect. Command Name No. Abbreviation Command Name Function * Command Name Full command name * Abbreviation Abbreviated command name Command Format Function 1 : Command input format Function 2 : Command input format * * <parameter 1>: Description of parameter 1 <parameter 2>: Description of parameter 2 : * Function Command function * Command Format Command input format for each function * Description Function and usage in detail Description Function 1 Description of function 1 Function 2 Description of function 2 * * * Notes Warnings and suggestions for using the command. If additional information is not required, this item is omitted. * Examples Command usage examples. Differs a little in the E7000PC. Notes Examples Figure 7-1 Emulation Command Description Format Symbols used in the command format have the following meanings: [ ]: (a/b): < >: ......: : (RET): Parameters enclosed by [ ] can be omitted. One of the parameters enclosed by ( ) must be specified. Contents shown in < > are to be specified or displayed. The entry specified just before this symbol can be repeated. Indicates a space. Used only for command format description. Pressing the (RET) key. Although underlining is often used throughout this manual to indicate input, it is not used in the command format sections of these descriptions. 7-3 7.2.1 .<register> .<register> .<register> Modifies and displays register contents Command Format * * Modification (direct mode) : .<register>[<data>] (RET) Modification (interactive mode) : .<register> (RET) <register>: Control register or general-purpose register to be modified or displayed. (Control register) PC, CCR (General-purpose register) ER0, ER1, ER2, ER3, ER4, ER5, ER6, ER7 (SP) E0, E1, E2, E3, E4, E5, E6, E7 R0, R1, R2, R3, R4, R5, R6, R7 R0H, R0L, R1H, R1L,R2H, R2L,R3H, R3L, R4H, R4L, R5H, R5L, R6H, R6L, R7H, R7L <data>: The value to be set in the specified register Description * Modification -- Direct mode Sets the specified value in the specified register. SP can be specified instead of ER7. : .<register> <data> (RET) -- Interactive mode If no data is specified on the command line with the register, register modification is performed in interactive mode. In this case, the system displays the current register value and requests its modification. When a modification value is specified, that value is set in the register, the next register contents are displayed, and its modification is requested. Registers are processed in the following order (and processing can begin at any register): ER0, ER1, ER2, ER3, ER4, ER5, ER6, ER7 (SP), PC, CCR In interactive mode, a general-purpose register can only be processed as a complete entity; extension registers E0-E7 and the high and low parts of a general register cannot be independently modified. 7-4 .<register> Example: To modify registers in interactive mode : .<register> (RET) <register> =xxxxxxxx ? <register> =xxxxxxxx ? * * * * yyyy <data>: .: ^: Only (RET): yyyy (RET) yyyy (RET) * * Inputs the value to be set Terminates the command Displays the previous register Does not modify the register; displays the following one To display all register contents, use the REGISTER command. Note Registers are set as follows at emulator initialization: ER0 to ER6: ER7 (SP): PC: CCR: H'00000000 Internal I/O start address - 2 Reset vector value H'80 If the MCU is reset by the emulator RESET or CLOCK command, registers are set as follows: ER0 to ER6: ER7 (SP): PC: CCR: Value before reset Value before reset Reset vector value H'80 Since the reset values for ER0 to ER7 in the MCU are not fixed, the initial values must be set by a program. 7-5 .<register> Examples 1. To set H'5C60 in the PC, H'FFE00 in the SP, H'FF in R1, H'11 in R2H and H'1 in E0, and then display all registers: :.PC 5C60 (RET) :.SP FFE00 (RET) :.R1 FF (RET) :.R2H 11 (RET) :.E0 1 (RET) :R (RET) PC=005C60 CCR=80:I******* ER0-ER3 00010000 000000FF 00001100 00000000 ER4-ER7 00004000 00005000 00000000 000FFE00 : 2. To modify the contents of control registers in interactive mode: :.PC (RET) PC =001000 ? 2000 (RET) CCR =80:I******* ? 00 (RET) : 7-6 !<symbol> 7.2.2 !<symbol> or &<symbol> !<symbol> or &<symbol> Displays symbol value Command Format * Display : !<symbol>[D] (RET) &<symbol>[D] (RET) !<symbol>: Symbol to be displayed &<symbol>: Line number symbol to be displayed D: Specifies display of data in decimal. (If D is omitted, data is displayed in hexadecimal.) Description * Display Displays data in the format shown in table 7-2, depending on attribute type. Table 7-2 Display Formats of Symbol Contents Attribute Display Format Description Function name, structure name, label name, symbol defined with the SYMBOL command <symbol>: xxxxxxxx Displays the symbol address as a 4-byte value. Simple variable name or pointer <symbol>: xx ...... Displays the variable contents according to its data length. For decimal display, a signed variable is displayed with a sign. Array name <symbol>: xx.. xx.. xx.. Displays entire contents of all elements in the array. Array element name <array name> (n): xx .. Displays the contents of the nth element if (n) is specified after the array name. Data size to be displayed is the element length of the array. Indicates the nth element (n = 1, 2, 3, ..) Line number symbol <line number symbol> : xxxxxxxx Displays the start address of a line number if that line number symbol is specified. 7-7 !<symbol> Examples 1. To disassemble the contents of an address specified by a symbol: :DISASSEMBLE !MAIN_START (RET) ADDR CODE LABEL MNEMONIC OPERAND 000500 1C89 !MAIN_START CMP.B #8,R1L 000502 4706 BEQ !MAIN_001 000504 6AA800FF MOV.B R0L,@FFFF00 FF00 000506 6B02FD80 MOV.W @FF80,R2 : : : : 2. To display the contents of array msym/sym_chr: :!msym/sym_chr (RET) 00 01 00 02 00 03 00 04 00 05 00 06 : 7-8 7.2.3 ABORT Terminates emulation in parallel mode ABORT AB Command Format * Termination : ABORT (RET) Description * Termination -- Terminates emulation execution in parallel mode (prompt #), and cancels parallel mode. -- When emulation is terminated by the ABORT command in parallel mode, BREAK KEY is displayed as the termination cause. Note Similar to when pressing the break key, when executing the ABORT command in a command chain file, the emulator outputs the termination cause followed by the confirmation message STOP COMMAND CHAIN (Y/N). Example To terminate GO command emulation in parallel mode: :GO RESET (RET) ** PC=001022 (RET) (To enter parallel mode) #ABORT (RET) PC=001300 CCR=80:I******* ER0 - ER3 00000000 00001000 00002000 00003000 ER4 - ER7 00044000 00225000 00006000 000FFF7E RUN-TIME=D'00M:01S:457355US BREAK KEY : 7-9 7.2.4 ASSEMBLE ASSEMBLE A Assembles a program line Command Format * Line assembly : ASSEMBLE <address> (RET) <address>: The address where the object program will be written Description * Line assembly -- After displaying the memory contents at the specified address, the emulator enters subcommand input wait state. Line input in subcommand input wait state is assembled to create machine codes and is written to memory. : ASSEMBLE <address> (RET) ADDR CODE LABEL MNEMONIC xxxxxx yyyy <disassemble display> xxxxxx yyyy ? <subcommand> (RET) xxxxxx yyyy ? <subcommand> (RET) (a) (b) (c) (a) Address (b) Memory contents (c) Subcommand (Input a subcommand shown in table 7-3) 7-10 OPERAND ASSEMBLE The subcommands listed in table 7-3 can be used with the ASSEMBLE command: Table 7-3 Subcommands for Line Assembly Subcommand Description <assembly language statement> Assembles the input line (statement) into machine code and writes it to memory. /[<address1>[<address2>]] Disassembles instructions from <address1> to <address2> and displays them. If <address2> is omitted, the first 16 instructions from <address1> are displayed. If only a slash (/) is input, the contents from the ASSEMBLE command start address to the current address -1 are disassembled. (RET) only Increments the address to the next instruction, and enters subcommand input wait state. ^ Decrements an odd address by one and an even address by two, and then enters subcommand input wait state. : Increments an odd address by one and an even address by two, and then enters subcommand input wait state. . Terminates the ASSEMBLE command. Note: The label is entered at the beginning. A space must be entered before an instruction. -- If an undefined label is referenced during line assembly, *** 33:INVALID ASM OPERAND is displayed. -- Even if an odd address is specified, write is performed. In that case, the following warning message is displayed: *** 82:ODD ADDRESS 7-11 ASSEMBLE Example To perform line assembly from address H'1000: :A 1000 ADDR 001000 001000 001004 001006 00100A : (RET) CODE 0000 0000 ? 0000 ? 0000 ? 0000 ? LABEL MNEMONIC OPERAND NOP SUB010 MOV.W ADD.B MOV.W . (RET) 7-12 #1,R3 (RET) R0L,R1L (RET) R0,@FB80 (RET) 7.2.5 BREAK B BREAK Sets, displays, and cancels PC breakpoints Command Format * * * Setting : BREAK<PC breakpoint to be set> [,<PC breakpoint to be set>]... (RET) Display : BREAK (RET) Cancellation : BREAK[]-[<PC breakpoint to be cancelled> [,<PC breakpoint to be cancelled>]...] (RET) <PC breakpoint to be set>: <start address>[:<end address>][<number of times>] <start address>: PC breakpoint start address <end address>: PC breakpoint end address (Specify when the range is specified) <number of times>: How many times the specified PC breakpoint is to be passed (H'1 to H'3FFF) (Default: H'1) <PC breakpoint to be cancelled>: <start address>[:<end address>] <start address>: The start address of the PC breakpoint to be cancelled <end address>: The end address of the PC breakpoint to be cancelled* Notes: 1. To cancel a breakpoint with range specification, specify one address within the specified range. 2. When the specified address is odd, it is rounded down to an even address. Description * Setting -- Sets a PC breakpoint for the specified address. GO command emulation terminates when an instruction within the specified range has been executed. (At termination, the instruction at the PC breakpoint is executed.) Since the PC break is performed by hardware, a PC breakpoint can also be set in the ROM area. A maximum of four breakpoints can be set with one command input, and a maximum of 255 breakpoints can be set in total. -- The user can specify the range or number of times. * Range specification: Break occurs when the instructions in address range H'100 to H'200 are executed BREAK 100:200 7-13 BREAK * Number of times specification: Break occurs when the instruction at address H'300 is executed five times BREAK 300 5 Note: When specifying the number of times, the program stops every time a PC breakpoint is passed and emulation ceases operating in realtime. -- PC breakpoints cannot be set at the addresses which have been specified with the BREAK_SEQUENCE command and in the internal I/O area. -- PC breakpoints are ignored during STEP and STEP_OVER command execution, so the pass count is not updated at this time. -- PC breakpoints are specified in 2-Mbyte address areas. When the MCU has a 64-kbyte or 1-Mbyte address area, PC breakpoints can be specified in all areas. When the address area is 16 Mbytes, PC breakpoints can be specified in the 2-Mbyte memory area starting from the base address determined by the BS option of the EXECUTION_MODE command. Refer to section 7.2.18, EXECUTION_MODE. * Display Display format is as follows: : BREAK (RET) <ADDR> xxxxxx (a) <CNT> yyyy (b) <PASS > zzzz (c) <SYMBOL> mmmm (d) (a) Setting address (b) Specified number of passes (hexadecimal) (c) Value of pass counter (shows how many times the specified address has been passed until GO command termination, in hexadecimal) Note: The pass counter is cleared by the next GO command. (d) Symbol (only displayed if the PC breakpoint start address has a symbol) 7-14 BREAK * Cancellation Cancels PC breakpoints. Breakpoints can be cancelled in the following two ways: -- Cancellation of PC breakpoints at specified addresses. A maximum of four breakpoints can be cancelled with one command. : BREAK-<PC breakpoint>[,<PC breakpoint> ]...(RET) -- Cancellation of all breakpoints. : BREAK- (RET) Notes 1. A PC breakpoint must be set at the start address of the MCU instruction. If not, a break does not occur. 2. In parallel mode, if a memory access command is executed and the emulation stops at a pass point at the same time, the memory access may not take place. In this case, *** 78: EMULATOR POD BUSY is displayed. Re-enter the command. If the termination interval is short, the emulator may not enter parallel mode or commands cannot be executed in parallel mode. 7-15 BREAK Examples 1. To set a PC breakpoint at H'100: :B 100 (RET) : 2. To set a PC breakpoint with the range from H'1000 to H'1FFF: :B 1000:1FFF (RET) : 3. To generate a break when H'6004 has been passed three times: :B 6004 3 (RET) : 4. To display set PC breakpoints: :B (RET) <ADDR> <CNT> 000100 0001 001000:001FFE 0001 : 5. <PASS> <SYMBOL> 0000 0000 !symbol To cancel the PC breakpoints in address range from H'1000 to H'1FFE; this range can be specified only by entering H'1000: :B -- 1000 (RET) : 6. To cancel all PC breakpoints: :B -- (RET) : 7-16 7.2.6 BREAK_CONDITION1,2,3,4 BC1,2,3,4 BREAK_CONDITION1,2,3,4 Specifies, displays, and cancels a hardware break condition Command Format * * * Setting : BREAK_CONDITION (1/2/3/4)<condition>[[ <condition >] [<condition>]...] (RET) Display : BREAK_CONDITION [(1/2/3/4)] (RET) Cancellation : BREAK_CONDITION [(1/2/3/4)] []- (RET) (1/2/3/4): Break command number When omitted, 1, 2, 3, and 4 will all be displayed or cancelled. <condition>: Hardware break condition (refer to tables 7-5 and 7-6 for details) Description * Setting -- Specifies hardware break conditions up to four points. Program execution stops when the specified conditions are satisfied. Combinations of conditions can be specified with the GO command option. In such combinations, normal mode, sequential break mode 1, 2, 3, or time measurement mode 1, 2 can be selected as the break mode. For details on specification and mode operation, refer to section 7.2.20, GO. The relationship between the GO command option and BREAK_CONDITION1,2,3,4 command is summarized in table 7-4. Table 7-4 Relationship between GO Command Option and BREAK_CONDITION1,2,3,4 Command BREAK_ CONDITION1 BREAK_ CONDITION2 BREAK_ CONDITION3 BREAK_ CONDITION4 Normal mode (no option specified) O O O O Sequential break mode 1 (S1) X X Sequential break mode 2 (S2) X Sequential break mode 3 (S3) Time measurement mode 1 (I1) X X Time measurement mode 2 (I2) X X GO Command Option Symbols: O X Must be specified. Specification is valid. Specification is invalid. 7-17 BREAK_CONDITION1,2,3,4 -- Conditions specified by BREAK_CONDITION1,2,3,4 are listed in tables 7-5 and 7-6. Note that the specifiable conditions for BREAK_CONDITION1 and BREAK_CONDITION2,3,4 are different. Table 7-5 Specifiable Conditions (BREAK_CONDITION1) Item and Input Format Description Address condition The condition is satisfied when the address bus value is in the range from <address 1> to <address 2>. A=<address 1>[:<address 2>][;NOT] If <address 2> is omitted, the condition is satisfied when <address 1> is recognized. If NOT is specified, the condition is satisfied when an address other than the specified one is accessed.* Data condition The condition is satisfied when the data bus value matches the specified value. D, LD, and HD are valid when byte access is performed, while WD is valid when word access is performed. If NOT is specified, the condition is satisfied when data other than the specified one is accessed.* D = <1-byte value>[;NOT] WD = <2-byte value>[;NOT] LD = <1-byte value> [;NOT] (Values on data bus from D7 to D0) HD = <1-byte value>[;NOT] (Values on data bus from D15 to D8) Read/Write condition The condition is satisfied in a read cycle (R is specified) or a write cycle (W is specified). R: Read W: Write Access type PRG: Program fetch cycle DAT: Execution cycle DMA: DMA cycle Default: All bus cycles described above Note: The condition is satisfied when the bus-cycle type matches the specified type. Multiple access types cannot be specified; either select one of the access types on the left, or specify none of them. Refer to the address and data condition descriptions on the following pages. 7-18 BREAK_CONDITION1,2,3,4 Table 7-5 Specifiable Conditions (BREAK_CONDITION1) (cont) Item and Input Format Description External probe condition The condition is satisfied when all the emulator's external probe signals match the specified values. Specify <value> as one byte of data. Each bit corresponds to a probe number, as follows: 7 6 5 4 3 2 1 0 Bit position x x x x x x x x Specified value 8 7 6 5 4 3 2 1 Probe number x: 0=Low level 1=High level (Ex.) To generate a break when probes 1 and 6 are high and the others are low, specify: PROB=H'21 External probe 8 is used for a multibreak. Specify EXECUTION_MODE command PB8 option and specify break when probe 8 is low with this condition. For details on multibreak, refer to the description on external probe values in section 5.4.1. PROB=<value> <value>: Values for probes 1 to 8 External interrupt condition NMI [:L] or NMI:H IRQ=<value> Note: * The condition is satisfied when NMI is at the specified level. -- NMI:L or NMI: Condition is satisfied when NMI is low. -- NMI:H: Condition is satisfied when NMI is high. * The condition is satisfied when all IRQn pins are at the specified levels. Specify <value> as one byte of data. Each bit corresponds to a signal as follows.* 7 6 5 4 3 2 1 0 Bit position x x x x x x Specified value 5 4 3 2 1 0 IRQ number x: 0=Low level 1=High level (Ex.) To generate a break when IRQ1 and IRQ5 are high and the remaining IRQ pins are low, specify: IRQ=H'22 * Both NMI and IRQ conditions can be specified simultaneously. Refer to the mask specification descriptions on the following pages. 7-19 BREAK_CONDITION1,2,3,4 Table 7-5 Specifiable Conditions (BREAK_CONDITION1) (cont) Item and Input Format Description Number of times a condition is satisfied COUNT=<value> <value>: H'1 to H'1000 This condition can be specified in combination with any of the above conditions. The complete condition combination is satisfied when the specified condition has been satisfied for the specified number of times. Delay count specification This condition can be specified in combination with any of the above conditions. The complete condition combination is satisfied when the specified number of bus cycles have been executed after the other specified condition is satisfied. When this conditions is specified in combination with the number-of-times conditions, the complete condition combination is satisfied when the specified number of bus cycles have been executed after the specified condition has been satisfied for the specified number of times. DELAY=<value> <value>: H'1 to H'7FFF Table 7-6 Specifiable Conditions (BREAK_CONDITION2,3,4) Item and Input Format Description Address condition The condition is satisfied when the address bus value matches the specified value.* A=<address> Data condition The condition is satisfied when the data bus value matches the specified value. D, LD, and HD are valid when byte access is performed, while WD is valid when word access is performed.* D = <1-byte value> WD = <2-byte value> LD = <1-byte value> (Values on data bus from D7 to D0) HD = <1-byte value> (Values on data bus from D15 to D8) Read/Write condition The condition is satisfied in a read cycle (R is specified) or a write cycle (W is specified). R: Read W: Write Access type PRG: Program fetch cycle DAT: Execution cycle DMA: DMA cycle Default: All bus cycles described above Note: The condition is satisfied when the bus-cycle type matches the specified type. Multiple access types cannot be specified; either select one of the access types on the left, or specify none of them. Refer to the address and data condition descriptions on the following pages. 7-20 BREAK_CONDITION1,2,3,4 Table 7-6 Specifiable Conditions (BREAK_CONDITION2,3,4) (cont) Item and Input Format Description External probe condition The condition is satisfied when all the emulator's external probe signals match the specified values. Specify this condition in the same way as BREAK_CONDITION1 shown in table 7-5. PROB=<value> External interrupt condition NMI [:L] or NMI:H IRQ=<value> Note: The condition is satisfied when NMI or IRQ is at the specified level. Specify this condition in the same way as BREAK_CONDITION1 shown in table 7-5.* Refer to the mask specification descriptions on the following pages. -- The address conditions and data conditions are satisfied when the address bus and data bus values match the specified values. Note the following when specifying break conditions. * Word access to a 16-bit bus area (including internal ROM, internal flash memory, and internal RAM areas) Word data is accessed in one bus cycle. Only even address values are valid for the address condition while only WD (word data) is valid for the data condition. * Word access to an 8-bit bus area (internal I/O and external area) Accessing this area in word units is equal to accessing it in byte units two times. Both even and odd address values are valid for the address condition while only D (byte data) is valid for the data condition. * Byte access All addresses can be accessed byte access. Both even and odd address values are valid for the address condition while only D (byte data) is valid for the data condition. Note: D, HD, or LD can be specified as byte data. Use these three data types depending on the trace conditions to be specified. D: If the specified address is even, data on data bus D15-D8 is specified. If the specified address is odd, data on data bus D7-D0 is specified. If no address is specified or if an address range or mask is specified, data on data bus D15-D8 is automatically specified as shown below. 7-21 BREAK_CONDITION1,2,3,4 Example 1: BC1 A=101 D=10 A condition is satisfied when byte data H'10 is written to or read from address H'101. Example 2: BC1 A=101:1FF D=20 A condition is satisfied when byte data H'20 is written to or read from odd addresses from H'101 to H'1FF. HD: Byte data (data bus D15-D8) access to an even address is always specified. Data access to an odd address is ignored. Example: BC1 A=1000:10FF HD=80 A condition is satisfied if byte data H'80 is written to or read from even addresses from H'1000 to H'10FF. LD: Byte data (data bus D7-D0) access to an odd address is always specified. Data access to an even address is ignored. Example: BC1 A=1000:10FF LD=80 A condition is satisfied if byte data H'80 is written to or read from odd addresses from H'1000 to H'10FF. Note that D, HD, or LD cannot be specified in word access. -- Bit masks can be specified for data, IRQ, or external probe conditions in 1-bit, or 4-bit units. When a bit is masked, the condition is satisfied irrespective of its bit value. To mask a bit, specify it as * at input. The number of bits that can be masked differs depending on the conditions. Examples of masks are shown below and in table 7-7. Example 1: A condition is satisfied when the D0 bit is 0 in a byte data condition. : BREAK_CONDITION 1 D = B'******* 0 (RET) Example 2: A condition is satisfied when IRQ2 is 0 in the IRQ condition. : BREAK_CONDITION 2 IRQ = B'*****0** (RET) 7-22 BREAK_CONDITION1,2,3,4 Table 7-7 Mask Specifications (BREAK_CONDITION1,2,3,4) Radix Mask Unit Example Mask Position Allowed Condition Binary 1 bit B'01*1010* D0 and D5 bits BREAK_CONDITION1 data (WD, D, HD, LD) BREAK_CONDITION1,2,3,4, IRQ, PROB Hexadecimal 4 bits H'F*50 D15 to D12 bits BREAK_CONDITION1,2,3,4 data (WD, D, HD, LD), IRQ, PROB Notes 1. BREAK_CONDITION1 data is in bit units and BREAK_CONDITION2,3,4 data is specified in 4-bit units. 2. BREAK_CONDITION1 address is masked from the low-order bit. However, the optional bit position or the range specification can not be masked. In addition, BREAK_CONDITION2,3,4 address cannot be masked. * When the specification is possible BREAK_CONDITION 1 A=H'10** * When the specification is impossible BREAK_CONDITION 1 A=H'1*00 BREAK_CONDITION 1 A=H'100*:10** -- If a hardware break condition is specified and that condition is satisfied, emulation stops after at least one instruction has been executed. -- The number of IRQ pins is 6 (IRQ0 to IRQ5)in the MCU. However, the IRQ condition can be specified by 8 bits. Because the emulator masks the settings of bits 6 and 7 that correspond to non-existent IRQ pins such as IRQ6 and IRQ7, bits 6 and 7 can be either 0 or 1. For example, if IRQ = 7F is specified, bits 6 and 7 are masked and the conditions specified for bits other than bits 6 and 7 must be satisfied. 7-23 BREAK_CONDITION1,2,3,4 * Display Displays specified conditions. The specified input character string is displayed as is before. All four break conditions are displayed if break command numbers 1 to 4 are omitted. For BREAK_CONDITION1, the number of times the break condition is satisfied and delay count since the previous break condition was satisfied are displayed. If no condition is specified, a blank is displayed. : BC (RET) BC1 (BREAK_CONDITION1 command setting) PASS COUNT = xxxx DELAY COUNT = yyyy BC2 (BREAK_CONDITION2 command setting) BC3 (BREAK_CONDITION3 command setting) BC4 (BREAK_CONDITION4 command setting) xxxx: Number of times the condition is satisfied yyyy: Delay count after the condition is satisfied Note: Pass count stops when the condition is satisfied. Therefore, the pass count whose condition is satisfied is not counted from the conditional satisfaction to the program stop. * Cancellation Cancels specified conditions. When conditions 1, 2, 3, and 4 are omitted, all break conditions are cancelled. -- Cancels all break conditions : BREAK_CONDITION - (RET) -- Cancels BREAK_CONDITION2 : BREAK_CONDITION2 - (RET) 7-24 BREAK_CONDITION1,2,3,4 Examples 1. To generate a break when byte data H'10 is accessed at address H'FF00: :BC1 A=FF00 D=10 : 2. To generate a break when the range from H'F000 to H'FFFF is accessed: :BC1 A=F000:FFFF : 3. (RET) (RET) To generate a break when IRQ0 is low: :BC2 IRQ=B'*******0 : 4. (RET) To display the specified condition: :BC (RET) BC1 A=FF00 D=10 PASS COUNT=0000 DELAY COUNT=0000 BC2 IRQ=B'*******0 BC3 BC4 : 5. To delete the specified condition: :BC1 -- :BC2 -- : (RET) (RET) 7-25 BREAK_SEQUENCE 7.2.7 BREAK_SEQUENCE BS Sets, displays, or cancels PC breakpoints with pass sequence specification Command Format * * * Setting : BREAK_SEQUENCE<pass point><pass point>[<pass point> [<pass point>]] (RET) (Pass point setting) : BREAK_SEQUENCE<reset point>;R (RET) (Reset point setting) Display : BREAK_SEQUENCE (RET) Cancellation : BREAK_SEQUENCE[]- (RET) (Pass point cancellation) : BREAK_SEQUENCE[]-;R (RET) (Reset point cancellation) <pass point>: <address> (two to four points) R: Reset point specification <reset point>: <address> (one point) Note: When the specified address is odd, it is rounded down to an even address. Description * Setting -- Sets pass points to enable the break for which the pass sequence is specified (sequential break). GO command emulation terminates when these pass points have been passed in the specified sequence. -- If the pass points have not been passed in the specified sequence, break checking begins again from the first pass point. -- When the specified reset point is passed, break checking begins again at the first pass point, even if the remaining pass points are then passed in the assigned sequence. -- When pass points or a reset point are specified, the emulator temporarily stops emulation and analyzes the pass sequence at each point. Therefore, realtime emulation is not performed. -- The pass points and reset point can be set in the ROM area; however, they cannot be set at an address that has already been specified with the BREAK command or in the internal I/O area. -- Pass points or a reset point are ignored during STEP and STEP_OVER command execution. Therefore, the pass count is not updated during STEP and STEP_OVER command execution. 7-26 BREAK_SEQUENCE -- The pass point and reset point setting range is a 2-Mbyte address area. When the MCU has a 64-kbyte or 1-Mbyte address area, all areas can be set. However, when the MCU has a 16-Mbyte address area, they are specified in a 2-Mbyte range from the base address specified with the BS option of the EXECUTION_MODE command. For details, refer to section 7.2.18, EXECUTION MODE. * Display Displays specified pass points and reset point as follows: : BREAK_SEQUENCE (RET) PASS POINT NO.1 = xxxxxx PASS POINT NO.2 = xxxxxx PASS POINT NO.3 = xxxxxx PASS POINT NO.4 = xxxxxx RESET POINT = xxxxxx (a) yyyy yyyy yyyy yyyy yyyy (b) zzzzzzzz zzzzzzzz zzzzzzzz zzzzzzzz (c) (a) Address (If nothing is specified, a blank is displayed.) (b) Number of times passed (The number of times the pass point was passed is displayed in hexadecimal. If it exceeds H'FFFF, counting restarts from H'0. The number of times passed is cleared by the next GO command.) (c) Symbol name (Displayed only when specified with symbols.) * Cancellation Cancels specified pass points or reset point. -- Cancellation of pass points : BREAK_SEQUENCE- (RET) -- Cancellation of a reset point : BREAK_SEQUENCE-;R (RET) 7-27 BREAK_SEQUENCE Notes 1. The pass points or reset point must be set at the start address of an MCU instruction. If not, a break does not occur.2. In parallel mode, if a memory access command is executed and the emulation stops at a reset point at the same time, the memory access may not take place. In this case, *** 78: EMULATOR POD BUSY is displayed. Re-enter the command. If the termination interval is short, the emulator may not enter parallel mode or commands cannot be executed in parallel mode. Examples 1. To set pass points at H'4000, H'4100, H'4200, and H'4300 in that order and a reset point at H'2000: :BS 4000 4100 4200 4300 :BS 2000 ;R (RET) : 2. To display the specified pass points and reset point: :BS (RET) PASS POINT PASS POINT PASS POINT PASS POINT RESET POINT : 3. (RET) NO1 NO2 NO3 NO4 = 004000 = 004100 = 004200 = 004300 = 002000 0000 0000 0000 0000 0000 To cancel the reset point: :BS -- ;R (RET) : 4. To cancel the pass points and reset point: :BS -- (RET) :BS -- ;R (RET) : 7-28 CHECK 7.2.8 CHECK CH Tests MCU pins Command Format * Test : CHECK (RET) Description * Test Tests the status of the MCU pins shown in table 7-8. Table 7-8 MCU Pin Test Pin Name Error Status Remarks RES RES signal is fixed low NMI NMI signal is fixed low STBY STBY signal is fixed low WAIT WAIT signal is fixed low Not tested in single-chip mode BREQ BREQ signal is fixed low Not tested in single-chip mode IRQ0 IRQ0 signal is fixed low IRQ1 IRQ1 signal is fixed low IRQ2 IRQ2 signal is fixed low IRQ3 IRQ3 signal is fixed low IRQ4 IRQ4 signal is fixed low IRQ5 IRQ5 signal is fixed low If an error occurs, the following message is displayed: FAILED AT <pin name> Note Some signal lines in table 7-8 are multiplexed with I/O ports, and may have different pin functions according to the MCU control register values. The emulator always tests these pins as control signal lines without checking the control register values. 7-29 CHECK Example When the IRQ0 signal is low: :CH (RET) FAILED AT IRQ0 : 7-30 CLOCK 7.2.9 CLOCK CL Sets or displays clock Command Format * * Setting Display : CLOCK<clock> (RET) : CLOCK (RET) <clock>: One of the following signals: 13: 13-MHz emulator internal clock 18: 18-MHz emulator internal clock U: User system clock X: Crystal oscillator clock on the emulator pod Description * Setting -- Selects emulator clock signals from the user system or from the emulator clock (installed in the emulator). Resets the MCU when a clock is selected, and consequently, internal I/O registers and control registers return to their reset values. -- Displays the specified clock signal. If the user system clock (U) or the crystal oscillator clock (X) is specified, but the clock signal is not input, an error occurs and the 13-MHz emulator clock (13) is set instead. At emulator initiation, the user system, crystal oscillator, and 13-MHz emulator clocks are selected in that order, and the correct clock signal is set. * Display Displays the current clock signal. : CLOCK (RET) CLOCK = <Used clock> <Used clock>: 13MHz: 18MHz: USER: X'TAL: Emulator internal clock (13 MHz) Emulator internal clock (18 MHz) User system clock Crystal oscillator 7-31 CLOCK Notes 1. 2. If U or X is specified and the following clock signal problems occur, the emulator system program may terminate. In this case, the emulator system program must be restarted. * User system clock is not input when it is specified. (Vcc has no problem.) * Crystal oscillator clock is not input when it is specified. When the user system interface cable is connected to the emulator, power must be supplied from the user system. If it is not, this command cannot be executed regardless of the current clock type. In addition, note that the user system interface cable must not be connected or disconnected at emulator initiation. Examples 1. To use the user system clock signal: :CL U (RET) ** RESET IN BY E7000 ! CLOCK = USER : 2. To use the 18-MHz emulator clock signal: :CL 18 (RET) ** RESET IN BY E7000 ! CLOCK = 18 MHz : 3. To display the current clock signal: :CL (RET) CLOCK = 18 MHz : 7-32 7.2.10 COMMAND_CHAIN CC COMMAND_CHAIN Inputs emulator command from a file (specific to the E7000) Command Format * Command input : COMMAND_CHAIN<file name> (RET) Description * Command input -- Sequentially reads commands from a command file, and executes them. When the following command file is specified, MAP, MEMORY, and CLOCK command are sequentially executed. The MEMORY command, though requiring further input within the command, can be read from a file and be executed. However, this command cannot execute the COMMAND_CHAIN command itself. Example: File contents: MAP 0 1FFFF;U MEMORY 100 30 . CLOCK Execution results: : COMMAND_CHAIN <file name> (RET) : MAP 0 1FFFF;U REMAINS EMULATION MEMORY S=60000/E=000000 : MEMORY 100 000100 00 ? 30 000101 00 ? . : CLOCK CLOCK = USER : (Command input wait state) 7-33 COMMAND_CHAIN -- The command file reading does not terminate until the end of the file is detected, or the (BREAK) key or (CTRL) + C keys are pressed. If either combination of keys are pressed, the message below is displayed, and execution is halted. The COMMAND_CHAIN command is then continued or terminated. STOP COMMAND CHAIN (Y/N) ? (a) (RET) (a) Y: Terminate N: Continue -- Create a command file with the editor of the host system connected to the emulator and transmit it to an emulator file using the TRANSFER, INTFC_TRANSFER, or LAN_TRANSFER command. -- This command is specific to the E7000. This command cannot be used in the E7000PC. The E7000PC, however, supports a function to input commands from the IBM PC file automatically. For details, refer to section 3.7.2, Debugging Function, in Part II, E7000PC Guide. Example To execute command file SAMPLE.COM: :CC SAMPLE.COM :FILL 0 FFFF :MEMORY 100 : (RET) The command is input sequentially and then executed. 7-34 CONVERT 7.2.11 CONVERT CV Converts data Command Format * Conversion : CONVERT<data> (RET) : CONVERT<expression> (RET) <data>: Data to be converted <expression>: Addition or subtraction <data>+<data>-<data> ... -<data> Description * Conversion -- Converts data to hexadecimal, decimal, octal, binary, and ASCII format. Input data is handled as 4-byte values, but unnecessary (leading) zeros are not displayed. If there is no corresponding ASCII character, a period (.) is displayed instead. : CONVERT <data> (RET) H'xx... D'xxx... Q'xxx... (a) (b) (c) (a) (b) (c) (d) (e) B'xxx... (d) xx... (e) Hexadecimal display Decimal display Octal display Binary display ASCII display -- If the H', D', Q', or B' radix is not specified for <data> at data input, the radix specified with the RADIX command is assumed. 7-35 CONVERT Examples 1. To convert hexadecimal data (H'7F): :CV H'7F (RET) H'7F D'127 Q'177 B'1111111 .... : 2. To convert the formula: :CV H'31+D'16 (RET) H'41 D'65 Q'101 B'1000001 ...A : 7-36 DATA_CHANGE 7.2.12 DATA_CHANGE DC Replaces memory data Command Format * Replacement : DATA_CHANGE<data 1><data 2><start address> (<end address>/@<number of bytes>)[;[<size>][Y]] (RET) <data 1>: <data 2>: <start address>: <end address>: <number of bytes>: <size>: Old data New data Start address of the memory area to be changed End address of the memory area to be changed The number of bytes in the memory area to be changed Length of data B: 1 byte W: 2 bytes L: 4 bytes Default: 1 byte Y: Specify Y if a confirmation message is not necessary. If Y is specified, data in all assigned areas is replaced without confirmation messages. Description * Replacement -- Replaces <data 1> in the specified memory area (set by the <start address> and <end address> or the <number of bytes>) with <data 2> and verifies the results. -- If option Y is not specified, the following message is displayed when the data specified by <data 1> is found: xxxxxx CHANGE (Y/N) ? y (RET) xxxxxx: Address where <data 1> was found. y: Y: <data 1> is replaced with <data 2>. N: Data is not replaced; search for another occurrence of the specified data continues. To terminate this command before reaching <end address>, press the (CTRL) + C keys. If option Y is specified, data is replaced without confirmation messages. 7-37 DATA_CHANGE -- Memory is not modified in the internal I/O area. If <data 1> is not found at any point in the replacement range, *** 45:NOT FOUND is displayed. Examples 1. To replace 2-byte data H'6475 in the area from H'7000 to H'7FFF with H'5308 (with confirmation message): :DC 6475 5308 7000 7FFF ;W (RET) 007508 CHANGE (Y/N) ? Y (RET) 007530 CHANGE (Y/N) ? N (RET) : 2. To replace 4-byte data 'DATA' in the area from H'FB80 to H'FE00 with 'DATE' (without confirmation message): :DC 'DATA' 'DATE' FB80 FE00 ;L Y (RET) : 7-38 7.2.13 DATA_SEARCH DS DATA_SEARCH Searches for memory data Command Format * Search : DATA_SEARCH<data>[<start address> [(<end address>/@<number of bytes>)]][;[<size>] [N]] (RET) <data>: <start address>: <end address>: <number of bytes>: Data to be searched for Search-start address (Default: H'0) Search-end address (Default: Maximum address in each operating mode) The number of bytes to be searched for (Default: Maximum address in each operating mode) <size>: Length of data to be searched for B: 1 byte W: 2 bytes L: 4 bytes Default: 1 byte N: Data other than the specified data is searched for Description * Search -- Searches for <data> from the start address to the end address (or for the specified number of bytes). All addresses where <data> is found are displayed. -- If data is not found, *** 45:NOT FOUND is displayed. -- If the N option is specified, data other than the specified <data> is searched for. 7-39 DATA_SEARCH Examples 1. To search for 1-byte data H'20 in the address range from H'FB80 to H'FF7F: :DS 20 H'FB80 H'FF7F FBFB FCCD : 2. (RET) To search for data other than 2-byte data H'0 in H'100 addresses starting from H'1000: :DS 0 1000 @100 ; W N (RET) *** 45 : NOT FOUND : 7-40 7.2.14 DISASSEMBLE DA DISASSEMBLE Disassembles and displays memory contents Command Format * Display : DISASSEMBLE<start address> [(<end address>/@<number of instructions>)] (RET) <start address>: Start address of disassembly <end address>: End address of disassembly <number of instructions>: The number of instructions to be disassembled Description * Display -- Disassembles the specified memory contents and displays addresses, machine codes, labels, mnemonics, and operands in the following format. As many lines as necessary are used for the display. ADDR <address> CODE <machine code> LABEL <label> MNEMONIC <mnemonic> OPERAND <operand> -- If <end address> or <number of instructions> is omitted, 16 lines of data are disassembled and displayed. -- If there is no applicable instruction, DATA.W xxxx is displayed. If <start address> is odd, DATA.B xx is displayed. -- After executing this command (except when it is forcibly terminated by the (CTRL) + C keys or (BREAK) key, or by an error), press the (RET) key to disassemble and display the next 16 lines of data. -- Disassemble is not performed in the internal I/O area. 7-41 DISASSEMBLE -- There are two instructions, PUSH/POP and MOV, that store register contents on the stack or recover them from the stack. However, these two instructions are displayed as the PUSH/POP instruction during disassembly as follows: * * * * MOV.W Rn, @-R7 is displayed as PUSH.W Rn. MOV.W @R7+, Rn is displayed as POP.W Rn. MOV.L ERn, @ - ER7 is displayed as PUSH.L ERn. MOV.L @ER7+, ERn is displayed as POP. L ERn. For assembly, of course both instructions can be specified. Examples 1. To disassemble and display six instructions starting from address H'1000: :DA 1000 @6 (RET) ADDR CODE LABEL MNEMONIC OPERAND 001000 7A07000F !MAIN MOV.L #00F0000:32,ER7 0000 001006 79000000 MOV.W #0000:16,R0 00100A 79010000 MOV.W #0000:16,R1 00100E 5E001200 JSR @!INIT 001012 A800 CMP.B #00:8,R0L 001014 586000E8 BNE !MAIN10 : 7-42 DISASSEMBLE 2. To disassemble and display 16 lines starting from address H'3000, and to furthermore disassemble and display the next 16 lines by only entering (RET): :DA 3000 (RET) ADDR CODE LABEL 001000 01006DF6 !SUB 001004 0D76 001006 7900000A 00100A 190T 00100C 01006DF5 001010 01006DF4 001014 79050001 001018 78606BA5 0000FFF6 001020 78606B25 0000FFF6 001028 AD01 00102A 79350001 00102E 58E02100 001032 1956 001034 0000 :(RET) 001036 78606BA5 0000FFF8 00103E 78606BA5 0000FFF8 : : : : MNEMONIC OPERAND PUSH ER6 MOV.W R7,R6 MOV.W #000A:16,R0 SUB.W R0,R7 PUSH ER5 PUSH ER4 MOV.W #0001:16,R5 MOV.W R5,@(00FFF6:24,ER6) MOV.W @(00FFF6:24,ER6),R5 CMP.B #01:8,R5L SUB.W #0001:16,R5 BGT 3132:16 SUB.W R5,R6 NOP MOV.W R5,@(00FFF8:24,ER6) MOV.W @(00FFF6:24,ER6),R5 7-43 DISPLAY_COVERAGE 7.2.15 DISPLAY_COVERAGE DCV Displays coverage trace results Command Format * Display : DISPLAY_COVERAGE[<start address><end address>] [;<option>[N]] (RET) <start address>: Start address of coverage trace display <end address>: End address of coverage trace display <option>: Display format of coverage trace display A: Address display D: Dump display Default: Address display N: Displays unexecuted or unaccessed addresses if option A is specified Description * Display -- Displays coverage trace information of addresses in the range from <start address> to <end address> (accessed during GO command execution) as address values or in display-dump format. The coverage trace acquisition range is a 2-Mbyte address area. When the MCU has a 64-kbyte or a 1-Mbyte address area, all spaces can be acquired. When the MCU has a 16-Mbyte address area, the trace range is within 2 Mbytes from the base address specified with the EXECUTION_MODE command with the BS option. Refer to section 7.2.18, EXECUTION_MODE. The range to be acquired is the same as for the PC break (BREAK, BREAK_SEQUENCE) range. When the address range specification is omitted, all address information to be acquired in the program area is displayed. -- Coverage trace can be executed after emulator system program initiation. Coverage trace settings can be initialized with the SET_COVERAGE command. 7-44 DISPLAY_COVERAGE -- The address display format is as follows: <ADDR> <ADDR> xxxxxx - xxxxxx * * * * * * <ADDR> <ADDR> ........... xxxxxx xxxxxx ............ * * * * * * Displays executed or accessed addresses in one of the following two ways: xxxxxx - xxxxxx: Memory area between these two addresses was executed or accessed. xxxxxx: Only this address was accessed. -- If option [;AN] is specified, coverage trace information is displayed for addresses in the specified memory range which were not executed or accessed during GO command execution. Although the display format is the same as the address display format, note that the displayed addresses have not been executed or accessed in this case. -- If option D is specified, coverage trace information is displayed in the following displaydump format: <start address> is a multiple of 8 and <end address> is a multiple of 8 - 1. <ADDR> xxxxxx (a) < yy yy yy (b) yy D yy A T A > ...................................... (a) Address (b) Address access information in hexadecimal (00 to FF). Each bit represents one memory address, and an accessed address is indicated as 1. Example: 001000 8F 00 ...... The first byte of data 8F indicates that addresses 1000, 1004, 1005, 1006, and 1007 were accessed. Data value Bit pattern Address (8) 1000 1000 (F) 1111 1004 7-45 DISPLAY_COVERAGE -- Coverage trace information is valid until re-initialization is provided with the SET_COVERAGE command. Coverage trace information of addresses accessed by the user program during GO command execution continues to be acquired until a new coverage trace initialization. Note The coverage trace range is 2 Mbytes from the base address specified by the BS option of the EXECUTION_MODE command. Examples 1. To display coverage trace information for the area from H'400 to H'7FFF: :DCV 400 7FFF (RET) <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> 000400--000503 000700--000703 000800-000815 007000--007103 007F00--007F09 007F20--007FFF : 2. To display addresses of areas not executed by GO command execution: :DCV ;A N (RET) <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> <ADDR> 000504--0006FF 000704--0007FF 000816--006FFF 007104--007EFF 007F0A--007F1F 008002--008003 008006--00FFFF : 3. To display executed addresses in display-dump format: :DCV ;D (RET) <ADDR> < D A T A> 000000 FF C0 F0 00 00 00 00 00 - 00 00 00 00 00 00 00 00 000080 FF FE F0 00 00 00 00 00 - FF FF FF 00 00 00 00 00 : : : : 7-46 DUMP 7.2.16 DUMP D Displays memory contents Command Format * Display : DUMP<start address>[(<end address/[@]<number of bytes>)] [;<display unit>] (RET) <start address>: Display start address <end address>: End address for memory dump <number of bytes>: Size of data for memory dump If @ is omitted, this value is taken as end address or size according to the inequalities given below. Default is 256 bytes, as size. End address: <start address> specified value Number of bytes: <start address> > specified value <display unit>: Size in bytes of display unit B: 1 byte W: 2 bytes L: 4 bytes Default: 1 byte Description * Display -- Displays a memory dump of the specified area as follows: <ADDR> xxxxxx (a) < DATA > xx.........................................xx (b) <ASCII CODE> "xxxx................xx" (c) (a) Address (b) Memory contents (c) Memory contents displayed as ASCII codes. If there is no applicable ASCII code, a period (.) is displayed instead. 7-47 DUMP -- If (CTRL) + P keys (hold down (CTRL), then press P) are entered during a memory dump, the emulator displays the 256 bytes of data before the start address of the current dump, and halts command execution. The emulator then waits for key input, but does not display a prompt. If the (RET) key is pressed at this stage, memory dump is started from the next address. If instead, (CTRL)+ P keys are pressed, the 256 bytes of data before the start address of the last dump are displayed. -- If no command is executed after DUMP command execution has been terminated (except for forcible termination by the (BREAK) key or an error), the 256 bytes of data from the next address of the last dump are displayed. Note The user can execute this command in parallel mode. However, when displaying the user system memory or internal I/O area, the program stops every time 16 bytes are displayed. Therefore, emulation does not operate in real time. Software standby or sleep state is cancelled, and the execution starts from an instruction following the SLEEP instruction. Emulation memory, internal ROM, flash memory, and internal RAM areas can be emulated in realtime, but the contents are not displayed in software standby or sleep mode. Examples 1. To display a memory dump from addresses H'0 to H'2F: :D 0 2F (RET) <ADDR> < D A T A > 000000 20 48 20 49 20 54 20 41 000010 00 00 00 00 00 00 00 00 <ASCII CODE> 20 43 20 48 20 49 20 20 " H I T A C H I " 00 00 00 00 00 00 00 00 "................" 000020 20 20 20 20 20 20 20 20 20 20 20 45 37 30 30 30 " E7000" : 2. To display 20 bytes of memory dump from address H'FB80 in 4-byte units: :D FB80 20 ;L (RET) <ADDR> < D A T A > <ASCII CODE> 00FB80 00000000 00000001 00000002 00000003 "................" 00FB90 00000000 00000001 00000002 00000003 "................" : 7-48 DUMP 3. To display by entering (CTRL) + P and (RET): :D 1000 @200 (RET) <ADDR> < D A T A > <ASCII CODE> 001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" Enter (CTRL) + P 000F00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 000F10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 000F20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 000F30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" : : : 000FF0 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 "................" Display of memory dump stops. Enter (RET) to continue display. 001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" : : : 0010F0 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 "................" Entering (RET) displays next 16 lines. :(RET) 001100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" 001130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................" : : : 0011F0 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 "................" : 7-49 7.2.17 END END E Cancels parallel mode Command Format * Cancellation # END (RET) Description * Cancellation -- Cancels parallel mode during GO command execution. -- Entering the END command clears old trace information and starts storing new trace information. Example To cancel parallel mode during GO command execution: :GO (RET) ** PC=003400 (RET) (Parallel mode entered) #M FD80 (RET) 00FD80 00 ? FF(RET) (Command execution in parallel mode) 00FD81 10 ? .(RET) #END (RET) (Parallel mode cancellation) ** PC=003800 7-50 7.2.18 EXECUTION_MODE EM EXECUTION_MODE Specifies and displays execution mode Command Format * Setting : EXECUTION_MODE [STR=<option 1>][BRQ=<option 2>] [TIME=<option 3>][PB8=<option 4>] [BS=<option 5>][LD=<option 6>] [TRG=<option 7>][FLA=<option 8>] [VPP=<option 9>][MON=<option 10>][;C] (RET) * Display : EXECUTION_MODE (RET) <option 1>: Specifies whether AS, RD, and WR are output to user system, and whether WAIT can be input at emulation memory access. E: Outputs AS, RD, and WR, and inputs WAIT when accessing emulation memory D: Does not output AS, RD, and WR and prohibits input of WAIT when accessing emulation memory (default at emulator shipment) <option 2>: Specifies whether the BREQ (bus request) signal input is enabled. E: Enables the BREQ signal input D: Disables the BREQ signal input (default at emulator shipment) <option 3>: Specifies the minimum time to be measured by the GO command or PERFORMANCE_ANALYSIS command. 1: 1 s (default at emulator shipment) 2: 250 ns <option 4>: Specifies whether external probe 8 is used for a synchronous break on multiple emulators (multibreak). N: Uses external probe 8 as a normal probe (default at emulator shipment) M: Uses external probe 8 for multibreak detection <option 5>: Specifies the PC breakpoint setting range for BREAK or BREAK_SEQUENCE command or the coverage trace acquisition range for the SET_COVERAGE command. 0 to F (default at emulator shipment is 0) <option 6>: Specifies whether the MOV or EEPMOV instruction is executed when memory is accessed with a host-related command. M: MOV is used E: EEPMOV is used (default at emulator shipment) 7-51 EXECUTION_MODE <option 7>: Specifies whether a pulse is output from the trigger output probe of the emulator pod without a break occurring when a hardware break condition is satisfied. E: Outputs a pulse from the trigger output probe without a break occurring when a hardware break condition is satisfied D:Breaks when a hardware break condition is satisfied (default at emulator shipment) <option 8>: Specifies whether boot program execution for the flash memory is enabled at GO command execution. E: Enables boot program execution D:Disables boot program execution (default at emulator shipment) <option 9>: Specifies whether the emulator applies 12 V to the VPP pin of the MCU at GO, STEP, or STEP_OVER command execution. E: Applies 12 V from the emulator to the VPP pin of the MCU D:Applies the voltage specified by the user system to the VPP pin of the MCU (default at emulator shipment) <option 10>: Specifies how long the interval is for execution status display. 0: No display 1: Approximately 200 ms (default at emulator shipment) 2: Approximately 2 s C: Writes the setting contents to the configuration file. 7-52 EXECUTION_MODE Description * Specification -- Enables/disables AS (address strobe), RD (read), HWR (higher write), LWR (lower write), and WAIT (wait) input/output at emulation memory access. * To specify that the signals, AS, RD, HWR, and LWR are not output to the user system and the WAIT signal is not input from the user system to the MCU when emulation memory is accessed: : EXECUTION_MODE STR=D (RET) * To specify that the signals, AS, RD, HWR, and LWR are output to the user system and the WAIT signal is input from the user system to the MCU when emulation memory is accessed: : EXECUTION_MODE STR=E (RET) The set signal inputs and outputs affect user program execution and emulation memory access with emulator command execution, such as memory modification/reference. -- Enables/disables the BREQ signal (bus request signal) input during realtime emulation. * To disable the BREQ signal input during realtime emulation: : EXECUTION_MODE BRQ=D (RET) * To enable the BREQ signal input during realtime emulation: : EXECUTION_MODE BRQ=E (RET) -- Specifies the minimum time to be measured by the GO command execution time measurement or by the PERFORMANCE_ANALYSIS command. * To set the minimum time to 1 s: : EXECUTION_MODE TIME=1 (RET) * To set the minimum time to 250 ns: : EXECUTION_MODE TIME=2 (RET) 7-53 EXECUTION_MODE -- Sets whether or not external probe 8 is used for multibreak. Refer to the description on external probes in section 5.4.1, Break Function, for details. * To specify that emulator's external probe 8 is used as a normal probe (the same as probes 1 to 7): : EXECUTION_MODE PB8=N (RET) * To specify that emulator's external probe 8 is used for multibreak detection: : EXECUTION_MODE PB8=M (RET) -- Specifies the PC breakpoint setting range for BREAK and BREAK_SEQUENCE commands, or the coverage trace acquisition range for the SET_COVERAGE command. The following 2-Mbyte ranges can be selected by entering data from H'0 to H'F. Data 0 1 2 3 4 5 6 7 Address Range H'0 to H'1FFFFF H'100000 to H'2FFFFF H'200000 to H'3FFFFF H'300000 to H'4FFFFF H'400000 to H'5FFFFF H'500000 to H'6FFFFF H'600000 to H'7FFFFF H'700000 to H'8FFFFF Data 8 9 A B C D E F Address Range H'800000 to H'9FFFFF H'900000 to H'AFFFFF H'A00000 to H'BFFFFF H'B00000 to H'CFFFFF H'C00000 to H'DFFFFF H'D00000 to H'EFFFFF H'E00000 to H'FFFFFF H'F00000 to H'FFFFFF and H'000000 to H'0FFFFF Example: To set the address range of H'700000 to H'8FFFFF : EXECUTION_MODE BS=7 (RET) -- Specifies whether the EEPMOV or MOV instruction is used for program loading or saving. When the EEPMOV instruction is used, the program is transferred in byte units and so the transfer speed is high. * To use the MOV instruction: : EXECUTION_MODE LD=M (RET) * To use the EEPMOV instruction: : EXECUTION_MODE LD=E (RET) 7-54 EXECUTION_MODE -- Specifies whether a pulse is output without stopping emulation by a hardware break specified with the BREAK_CONDITION1,2,3,4 command. When a hardware break condition is satisfied, a pulse is output to the trigger output probe. For details, refer to section 5.8, Trigger Output. Note that the PC break specified with the BREAK or BREAK_SEQUENCE command is always valid regardless of this setting. If TRG = E is specified, the sequential break specified with the GO command becomes invalid and a pulse is output whenever hardware break conditions are satisfied. * To stop the program by a hardware break: : EXECUTION_MODE TRG=D (RET) * To output a pulse without stopping the program by a hardware break: : EXECUTION_MODE TRG=E (RET) -- Enables/disables the execution of boot program for flash memory during realtime emulation by the GO command. * To enable the boot program execution: : EXECUTION_MODE FLA=E (RET) * To disable the boot program execution: : EXECUTION_MODE FLA=D (RET) -- Specifies whether 12-V power is applied from the E7000 to the Vpp pin of the MCU during GO, STEP, or STEP_OVER command execution. If Vpp = E is specified (12-V power is applied), flash memory modification can be emulated even if 12-V power is not applied to the Vpp of the user system. * To apply 12 V from the E7000 to the Vpp of the MCU: : EXECUTION_MODE VPP=E (RET) * To place the Vpp of the MCU in the same state as the Vpp of the user system: : EXECUTION_MODE VPP=D (RET) 7-55 EXECUTION_MODE -- Specifies the interval length of PC display during GO command execution. * To disable PC display: : EXECUTION_MODE MON=0 (RET) * To enable PC display every 200 ms: : EXECUTION_MODE MON=1 (RET) * To enable PC display every 2 s: : EXECUTION_MODE MON=2 (RET) -- The following message is output when the C option is specified: CONFIGURATION WRITE OK (Y/N) ? When using the E7000 and Y is input, the specifications are written in a configuration file on the system disk. When using the E7000PC and Y is input, specifications are written in the configuration file in the directory where the current system program is stored on the IBM PC. Hereafter, when the E7000 is activated with the system disk, the saved specifications go into effect. * Display When all options are omitted, the current value is displayed and the emulator enters the interactive mode. Enter the required value for each item. Enter (RET) for the item not to be modified. To exit the interactive mode, enter a period (.). In this case, modification before entering a period is valid. : EXECUTION_MODE (RET) STR=D BRQ=D TIME=1uSEC PB8=N BS=0 LD=E TRG=D FLA=U MON=1 STR (E: ENABLE/D: DISABLE) ? E (RET) (Displays current value) (Inputs/outputs AS, RD, LWR, HWR, and WAIT) BRQ (E: ENABLE/D: DISABLE) ? (RET) (No modification) TIME (1: 1uSEC/2: 0.25uSEC) ? 2 (RET) (Display time is 250 ns) PB8 (M: MULTI/N: NORMAL) ? . (RET) (Command is terminated. Modification is valid.) : 7-56 EXECUTION_MODE Examples 1. To set the PC break range 2 Mbytes from address H'200000 and write the setting in the configuration file: :EXECUTION_MODE BS=2 ;C (RET) *** 85: COVERAGE INITIALIZED CONFIGURATION WRITE OK (Y/N) ? Y (RET) : 2. To display the specified values of the current emulation execution mode and modify them in interactive mode (the command execution can be terminated by entering a period (.)): :EM (RET) STR=D BRQ=D TIME=1uSEC PB8=N BS=0 STR (E:ENABLE/D:DISABLE) ? (RET) BRQ (E:ENABLE/D:DISABLE) ? (RET) TIME (1:1uSEC/2:0.25uSEC) ? 2 (RET) PB8 (M:MULTI/N:NORMAL) ? (RET) BS (0 - F) ? .(RET) : 7-57 LD=E TRG=D FLA=D VPP=D MON=1 (Input (RET) for no modification) 7.2.19 FILL FILL F Writes data to memory Command Format * Write : FILL<start address>(<end address>/@<number of bytes>)[<data>] [;[<size>][N]] (RET) <start address>: <end address>: <number of bytes>: <data>: <size>: Write start address Write end address The number of bytes to be written Data to be written. Default is H'00. Length of data to be written B: 1 byte W: 2 bytes L: 4 bytes Default: 1 byte N: No verification Default: Verification performed Description * Write -- Writes data to the specified memory area. Default value is H'0. -- When option N (No verification)is not specified (default is selected), data is also verified after it has been written. This command can therefore be used as a memory test. If an error occurs, the following message is displayed and processing is terminated. FAILED AT xxxxxx WRITE = yy..'y..' READ = zz...'z..' xxxxxx: Error address yy..'y..': Write data (hexadecimal and ASCII characters) zz...'z..': Read data (hexadecimal and ASCII characters) -- If a write to the internal I/O area is attempted, execution terminates just before entering the internal I/O area. -- If W or L is specified as <size>, but the start address is odd, the lowest bit of the start address is rounded down to the preceding even address. The end address is set without changes. 7-58 FILL Example To fill the entire area from addresses H'0 to H'6FFF with 1-byte data H'00: :F 0 6FFF 0 (RET) : 7-59 7.2.20 GO GO G Provides realtime emulation Command Format * Execution : GO[[<start address>][;[<break address>][<mode>][TM]]] (RET) <start address>: Start address of realtime emulation, or the word RESET or ONRESET <break address>: A breakpoint address <mode>: Emulation mode S1: Sequential break mode 1 S2: Sequential break mode 2 S3: Sequential break mode 3 R=<n>: Cycle reset mode, n = 1 to 9 I1, I2: Time interval measurement modes 1, 2 N: Invalidates break conditions temporarily TM: Displays the memory contents in the address specified with the TM (TRACE_MEMORY) command. Description * Execution -- Executes realtime emulation (user program execution) starting with a specified <start address>. The following data can be specified as <start address>. : GO RESET (RET) : After RES signal input to the MCU, PC is set to the value specified with the reset vector and program execution starts. : GO ONRESET (RET) : If the flash memory is enabled, the boot program for the flash memory and user program are executed in this order after RES signal input to the MCU. If the flash memory is disabled, PC is set to the value specified with the reset vector and program execution starts after RES signal input to the MCU. : GO <address> (RET) : Executes the program from the specified address. : GO (RET) : When omitting the address, the program executes from the address where the current PC indicates. 7-60 GO -- By the <mode> specification at the GO command input, the program executes in one of the following modes. * Sequential break mode 1 (S1) Realtime emulation stops only when break conditions set by the BREAK_CONDITION1,2 command are satisfied in the sequence of <condition 2> followed by <condition 1>. * Sequential break mode 2 (S2) Realtime emulation stops only when break conditions set by the BREAK_CONDITION1,2,3 command are satisfied in the sequence of <condition 3>, <condition 2>, and <condition 1>. * Sequential break mode 3 (S3) Realtime emulation stops only when break conditions set by the BREAK_CONDITION1,2,3,4 command are satisfied in the sequence of <condition 4>, <condition 3>, <condition 2>, and <condition 1>. * Cycle reset mode (R=n) A RES signal is input to the MCU at the intervals given in table 7-9. At the same time, a trigger signal for an oscilloscope is output through the TRIG output pin. In this mode, all break conditions and trace conditions are invalidated during emulation. Table 7-9 Cycle Reset Times Value of n Reset Interval 1 32 s 2 96 s 3 512 s 4 1.024 ms 5 5.12 ms 6 10.24 ms 7 51.2 ms 8 102.4 ms 9 512 ms 7-61 GO * Time interval measurement mode 1 (I1) The execution time from the point when <condition 2> is satisfied until <condition 1> is satisfied is measured. Program stops at the BREAK_CONDITION1 satisfaction. * Time interval measurement mode 2 (I2) The execution time from the point when <condition 2> is satisfied until <condition 1> is satisfied is measured. Even if these break conditions are satisfied, the program does not stop and the execution time between <condition2> and <condition1> is measured. When these conditions are satisfied twice or more, the time is added to the previous measured time. Table 7-10 lists restrictions for the above modes. Table 7-10 Restrictions for Realtime Emulation Modes Mode Restrictions Sequential break mode 1 * Conditions must be specified with the BREAK_CONDITION1,2 command. * Conditions specified with the BREAK_CONDITION3,4 command are ignored. Sequential break mode 2 * Conditions must be specified with the BREAK_CONDITION1,2,3 command. * Conditions specified with the BREAK_CONDITION4 command are ignored. Sequential break mode 3 * Conditions must be specified with the BREAK_CONDITION1,2,3,4 command. Cycle reset mode * PC break conditions specified with the BREAK or BREAK_SEQUENCE command are ignored. * All conditions specified with the BREAK_CONDITION1,2,3,4 command are ignored. * All conditions specified with the TRACE_CONDITION command are ignored. * Parallel mode cannot be entered * The TM option cannot be specified. Time interval * Conditions must be specified with the BREAK_CONDITION1,2 command measurement modes 1 and 2 * PC break conditions specified with the BREAK or BREAK_SEQUENCE command are ignored. * All conditions specified with the BREAK_CONDITION3,4 command are ignored. * Parallel mode cannot be entered. * Measurement for PERFORMANCE_ANALYSIS cannot be performed. 7-62 GO * Invalidating break conditions temporarily If option N is specified, PC breakpoints set with the BREAK or BREAK_SEQUENCE command and hardware breakpoints set with the BREAK_CONDITION1,2,3,4 command are invalidated temporarily, and emulation continues. However, the breakpoints are invalidated only within one user program execution by the GO command. If option N is not specified in the next GO command emulation, breakpoints are validated again. -- If <break address> is specified, realtime emulation stops after the instruction at the specified address is executed. This specification is valid for only the current GO command emulation. The range to specify is 2-Mbytes from the base address specified with EXECUTION_MODE command BS option. Refer to section 7.2.18, EXECUTION_MODE, for details. -- During realtime emulation, program fetch addresses are displayed at the interval specified with the MON option of the EXECUTION_MODE command. If the TM option is specified, memory contents of the address specified with the TRACE_MEMORY command are also displayed. Two-byte data is displayed for memory contents. An error occurs if the address is not specified with the TRACE_MEMORY command. : GO ; TM (RET) ** PC = xxxxxx yyyyyy = zzzz xxxxxx: Program fetch address yyyyyy: Address of memory contents to be displayed (valid when the TM option is specified) zzzz: Memory contents (2 bytes) Note: The TRACE_MEMORY display address can be modified in parallel mode, but the contents to be displayed are not updated until access is completed (the contents before modification are displayed). When specifying the access with DMA, the display contents are not updated until access is completed with DMAC. -- During GO command emulation, pressing the SPACE key or (RET) key sets parallel mode. For details, refer to section 1.3.3, Parallel Mode. 7-63 GO -- If emulation is terminated, register contents, execution times, cause of termination, and line number symbols are displayed in the following format: PC=001000 CCR=80:I******* ER0 - ER3 00000000 00000001 00000002 00000003 ER4 - ER7 00000008 00000009 0000000A 0000000B RUN-TIME=D'000H:00M:00S:000000US[:000NS] <cause of termination> LINE NO = <line number symbol> + n (a) (b) (c) (d) (a) The contents of each register at emulation termination. (b) Time of user program execution, in decimal. According to the TIME option of the EXECUTION_MODE command, the maximum measurable time is 305 or 76 hours, where the minimum measurement time is 1 s or 250 ns, respectively. If the period exceeds the maximum, it is displayed as *. (c) Cause of termination, as listed in table 7-11. (d) If a line number symbol is defined, the termination location is displayed in the format of: line number symbol + n. Table 7-11 Causes of GO Command Emulation Termination Display Termination Cause BREAK KEY The (CTRL) + C keys were pressed or the ABORT command was executed for forcible termination BREAK POINT xxxxxx Emulation stopped at a PC breakpoint xxxxxx specified with the BREAK command STOP ADDRESS An instruction at the break address was executed during GO command emulation BREAK SEQUENCE A PC break condition specified with the BREAK_SEQUENCE command was satisfied BREAK CONDITION 1 A break condition specified with the BREAK_CONDITION1 command was satisfied BREAK CONDITION 2 A break condition specified with the BREAK_CONDITION2 command was satisfied BREAK CONDITION 3 A break condition specified with the BREAK_CONDITION3 command was satisfied BREAK CONDITION 4 A break condition specified with the BREAK_CONDITION4 command was satisfied BREAK CONDITION 1,2,3,4 A break combination condition was satisfied when the break conditions specified with the BREAK_CONDITION1,2,3,4 command were satisfied (refer to notes) 7-64 GO Table 7-11 Causes of GO Command Emulation Termination (cont) Display Termination Cause BREAK CONDITION S1 Sequential break conditions specified with the BREAK_CONDITION1,2 command were satisfied BREAK CONDITION S2 Sequential break conditions specified with the BREAK_CONDITION1,2,3 command were satisfied BREAK CONDITION S3 Sequential break conditions specified with the BREAK_CONDITION1,2,3,4 command were satisfied GUARDED AREA ACCESSED A guarded memory area was accessed WRITE PROTECT A write-protected area or internal ROM area (flash memory) was written to ILLEGAL INSTRUCTION A break instruction (H'5740 to H'577F) was executed NO EXECUTION The user program was not executed (this message is displayed only for the RESULT command) RESET IN BY E7000 Terminates the program with the RES signal because an error occurs in the user system DMA GUARDED OR WRITE PROTECT The write-protected area is written to or guarded memory area is accessed by the DMA during the continuous execution after the PC breakpoint. INVALID SP ADDRESS Stack pointer specifies the internal I/O area. -- During user program execution, MCU execution status is displayed. Displayed contents are shown in table 7-12. This status is monitored every 200 ms and if there is a difference from the previous status, the status is displayed. Table 7-12 Execution Status Display Display Meaning **PC=xxxxxx [yyyyyy=zzzz] Displays program fetch addresses during execution at the interval specified with the MON option of the EXECUTION_MODE command. If TM option was specified, each address specified with the TRACE_MEMORY command and its contents are also displayed and updated. ** VCC DOWN VCC (power supply voltage) is not correct and the emulator forcibly terminates the user program. Provide the correct power supply voltage and re-execute. ** RESET RES signal is low. The MCU has been reset. 7-65 GO Table 7-12 Execution Status Display (cont) Display Meaning ** WAIT A = xxxxxx WAIT signal is low; the value on the address bus is displayed. At the refresh cycle, the address is not displayed. *** HARDWARE STANDBY The STBY signal is low but since this signal is not input to the MCU, the MCU does not enter hardware standby state in the emulator. ** SOFTWARE STANDBY The MCU is in software standby state. ** SLEEP The MCU is in sleep state. ** BREQ The BREQ signal is low. ** BACK The BACK signal is low. ** TOUT A = xxxxxx The AS signal has remained high for 80 s or more; the value on address bus is displayed. Notes 1. The emulator cannot operate correctly when the stack pointer (ER7; R7 in the 64-kbyte area) points to the MCU internal I/O area at program execution start or stop. Accordingly, the stack pointer must be within the following address range to perform emulation correctly. H'000004 to ( internal I/O area start address + 1) Outside the range: (a) At emulation start: User program is not executed. (b) At emulation stop: Internal I/O register is written to. To resume emulation, set the internal I/O register and stack pointer. When emulation starts, *** 49: INVALID SP ADDRESS is displayed. When emulation terminates, INVALID SP ADDRESS is displayed as the cause of termination. 2. When the hardware break condition (BREAK CONDITION1,2,3,4 command setting) is satisfied during program execution, the program terminates after execution of at least one of the instructions that have been already fetched. If another hardware break is satisfied before the user program terminates, BREAK CONDITION1,2,3,4 (the number of the satisfied condition) is displayed. For further details, examine the trace information. 7-66 GO 3. At each PC breakpoint set with the BREAK command or the BREAK_SEQUENCE command, the program stops, the pass count and address of the program are analyzed, and then the program continues. When the memory command processing in parallel mode occurs during this termination, memory cannot be accessed. At this time, *** 78: EMULATOR POD BUSY is displayed, and the command should be re-input. However, when the interval of termination is short, the PC is not displayed, the emulator does not enter parallel mode, or parallel mode command may not be executed. 4. If TRG = E is specified as a TRG condition with the EXECUTION_MODE command, a break does not occur even if a break condition specified with the BREAK_CONDITION1,2,3,4 command is satisfied. In this case, a pulse is output from the trigger output probe pin. 5. The ONRESET specification is valid only in operating mode 5, 6, or 7 in which the flash memory is used in the MCU incorporating the flash memory. If ONRESET is specified in an MCU incorporating no flash memory or in an operating mode in which no flash memory is used, the emulator operates in the same way as when RESET is specified. * If FLA = E is specified with the EXECUTION_MODE command, the emulator initiates the installed flash memory boot program, loads the flash memory modification program via the MCU internal SCI, and executes the flash memory modification program. * If FLA = D is specified with the EXECUTION_MODE command, the emulator operates in the same way as when RESET is specified. 6. If VPP = E is specified with the EXECUTION_MODE command, the flash memory modification can be emulated even if the 12-V power is not applied from the user system to the VPP pin. 7-67 GO Examples 1. To reset the MCU and start emulation from the reset vector PC address: :G RESET (RET) ** PC=001130 2. To start emulation from address H'1000 and stop emulation when address H'2020 is executed: :G 1000 ; 2020 (RET) ** PC=002002 3. To start emulation from the current PC address in sequential break mode 2: :G ; S2 (RET) ** PC=004250 4. To invalidate current PC break conditions and hardware break conditions, start emulation, and display the contents of the address specified by the TRACE_MEMORY command: :G ; N TM (RET) ** PC=006642 5. 00FFD0=0080 To start emulation from the current PC address and modify memory contents in parallel mode: :G (RET) ** PC=010204 #M FEF0 (RET) FEF0 FE ? FF (RET) FEF1 FF ? . (RET) #END (RET) ** PC=011456 (RET) 7-68 7.2.21 HELP HE HELP Displays all commands and command format Command Format * Display : HELP (RET) : HELP <command> (RET) (All commands are displayed.) (Command format is displayed.) Description * Display Displays all emulator command names and abbreviations. 7-69 HELP Examples 1. To display all emulator commands: :HELP (RET) .<REGISTER> *!<SYMBOL> *&<LINE NUMBER> *AB : ABORT A : ASSEMBLE **B : BREAK BC,BC1,BC2,BC3,BC4 : BREAK_CONDITION,1,2,3,4 **BS : BREAK_SEQUENCE CH : CHECK **CL : CLOCK *CC : COMMAND_CHAIN *CV : CONVERT DC : DATA_CHANGE DS : DATA_SEARCH *DA : DISASSEMBLE DCV : DISPLAY_COVERAGE *D : DUMP *E : END EM : EXECUTION_MODE F : FILL G : GO *HE : HELP *HT : HISTORY *ID : ID *LED,*LED1,*LED2,*LED3,*LED4 : LED,1,2,3,4 *LT,*LT1,*LT2 : LED_OUT,1,2 MP : MAP *M : MEMORY MD : MODE MV : MOVE MR : MOVE_TO_RAM PA : PERFORMANCE_ANALYSIS *P : PRINT Q : QUIT *RX : RADIX R : REGISTER RS : RESET RT : RESULT SCV : SET_COVERAGE *SS : SHORT_SYMBOL *ST : STATUS S : STEP SI : STEP_INFORMATION SO : STEP_OVER *SY : SYMBOL *T : TRACE *TC : TRACE_CONDITION *TM : TRACE_MEMORY TMO : TRACE_MODE *TS : TRACE_SEARCH *FCO : FILE_COPY *FDI : FILE_DIRECTORY *FDU : FILE_DUMP *FER : FILE_ERASE FL : FILE_LOAD *FRE : FILE_RENAME FS : FILE_SAVE *FTY : FILE_TYPE FV : FILE_VERIFY *FCH : FLOPPY_CHECK *FF : FLOPPY_FORMAT H : HOST L : LOAD SV : SAVE TL : TERMINAL TR : TRANSFER V : VERIFY IL : INTFC_LOAD IS : INTFC_SAVE IT : INTFC_TRANSFER IV : INTFC_VERIFY *LAN : LAN LH : LAN_HOST *LO : LOGOUT *FTP : FTP *#OPEN : OPEN *#LS : LS *#PWD : PWD *#ASC : ASC *#BIN : BIN *#STA : STA *#CD : CD *#BYE : BYE #LSV : LAN_SAVE #LTR : LAN_TRANSFER #LV : LAN_VERIFY 7-70 HELP Note: *: **: No *: #: Usable in parallel mode Available only for display in parallel mode Unusable in parallel mode Available when the FTP server is open. The above example is a display when E7000 is used. The display when using E7000PC is a little different. 2. To display each command format: :HELP G (RET) Displays GO command format. : 7-71 7.2.22 HISTORY HISTORY HT Displays input command history Command Format * Display : HISTORY (RET) (Displays all input commands) : HISTORY <history number> (RET) (Displays the input command of specified history number) <history number>: History number (1 to 16) Description * Display -- Displays the 16 commands most recently input including the HISTORY command in the input order. -- If <history number> is entered, the command corresponding to <history number> is displayed as shown below and the emulator enters input wait state. When the (RET) key is pressed, the displayed command is executed. Example :HISTORY (RET) 1 MAP 2 MAP 0 1FFFF;S 3 F 0 1000 FF 4 B 300 5 BC1 A=104 6 HISTORY :HISTORY 5 (RET) :BC1 A=104 ------------Enters command input wait state Restriction Subcommands cannot be displayed by the HISTORY command. 7-72 7.2.23 ID Displays emulator system program version ID ID Command Format * Display : ID (RET) Description * Display -- Displays the MCU emulator system version and revision numbers. Example To display the MCU emulator system version and revision numbers: :ID (RET) H8/3048 E7000 (HS3048EPD70SF) Vn.m Copyright (C) Hitachi,LTD. 1994 Licensed Material of Hitachi, Ltd. : 7-73 7.2.24 LED1,2,3,4 LED1,2,3,4 LED1,2,3,4 Specifies, displays, or cancels memory contents display on LEDs Command Format * * * * Specification Initialization Display Cancellation : : : : LED(1/2/3/4)<address>[;<size>] (RET) LED[(1/2/3/4)] I (RET) LED[(1/2/3/4)] (RET) LED[(1/2/3/4)][] - (RET) <address>: Memory address whose contents are to be displayed on LEDs <size>: Display data size B: 1 byte W: 2 bytes L: 4 bytes Default: 1 byte I: Specifies initialization of memory contents display on LEDs Description * Specification -- Specifies the memory addresses whose contents are to be displayed on the LEDs on the optional bus monitor board. After an address is specified with this command, the corresponding data is displayed on the LEDs when the address is accessed by the user program. Up to four addresses can be specified by the LED1 to LED4 commands, and up to four bytes of data can be displayed for one address. -- When specifying W (two bytes) or L (four bytes) as the size, specify a multiple of two or four as the address, respectively. When an odd address is specified, 1-byte (B) data is displayed regardless of the size specification. When L is specified and the address is not a multiple of four, the size is automatically set to W and B, when the address is even and odd, respectively. -- The LEDs turn on, and the display is updated, only after the specified address is accessed by the user program. This applies even when the contents of the address are updated in the emulator as in the case of a timer counter, and neither is the displayed data updated when accessed by an emulator command such as MEMORY. 7-74 LED1,2,3,4 * Initialization -- Turns off the specified LED. The previously specified address remains valid until the address is cancelled or a new address is specified, and its contents are still displayed when the address is accessed by the user program again. When 1, 2, 3, and 4 are omitted, all the LEDs are extinguished. * To turn off all the LEDs: : LED I (RET) * To turn off LED 2: : LED2 I (RET) * Display Displays the currently specified addresses. When 1, 2, 3, and 4 are omitted, the addresses specified for all the LEDs are displayed. When no address is specified, a blank will be displayed. -- To display all specified addresses: : LED (RET) LED1 = xxxxxx LED2 = xxxxxx LED3 = xxxxxx LED4 = xxxxxx y y y y zzzz... zzzz... zzzz... zzzz... xxxxxx: Address y: Display size (B: 1 byte, W: 2 bytes, L: 4 bytes) zzzz...: Symbol (only when a symbol is specified) -- To display the address specified for LED3: : LED3 (RET) LED3 = xxxxxx y zzzz... 7-75 LED1,2,3,4 * Cancellation Cancels the specified address. When 1, 2, 3, and 4 are omitted, the addresses specified for all the LEDs are cancelled. -- To cancel all specified addresses: : LED - (RET) -- To cancel the address specified for LED2: : LED2 - (RET) Examples 1. To display the 2-byte data stored at address H'20000 on LED1: :LED1 20000;W (RET) : 2. To temporarily turn off LED2 (initialization): :LED2 I (RET) : 3. To display all the current address specifications: :LED1 (RET) LED1 = 000882 W LED2 = 000FFE B LED3 = LED4 = : 4. To cancel the address specified for LED1: :LED1 - (RET) : 7-76 7.2.25 LED_OUT1,2 LT1,2 LED_OUT1,2 Specifies and displays analog output of LED display data Command Format * * Specification Display : LED_OUT(1/2)<LED number>[;<data position>] (RET) : LED_OUT(1/2) (RET) <LED number>: LED number whose displayed data is to be output from the analog terminals 1: LED1 data is output 2: LED2 data is output <data position>: Position of data to be output from the analog terminals H: High-order 16 bits of displayed data L: Low-order 16 bits of displayed data Default: Low-order 16 bits of displayed data Description * Specification -- Outputs data displayed on LED1 or LED2 on the optional bus monitor board as analog data, from two analog output terminals 1 and 2 located on the monitor board. The output from terminals 1 and 2 is specified by the LED_OUT1 and LED_OUT2 commands, respectively. Either the high-order or low-order 16 bits of data displayed on LED1 or LED2 can be output. LED display High-order 16 bits Low-order 16 bits -- Analog data is output when the address specified by LED1,2 is accessed by the user program. Accordingly, addresses and LED numbers output by LED1,2 must be specified before program execution. Note that analog data output is undefined until the LED address is accessed by the user program. In addition, analog data output is undefined if the LED is not displayed. 7-77 LED_OUT1,2 * Display Displays the LED number whose display data is being output from the analog terminals, and the data position. When 1 and 2 are omitted, the specifications for both LED_OUT1 and LED_OUT2 are displayed. -- To display specifications for both the LED_OUT1 and LED_OUT2: : LED_OUT (RET) LED_OUT1 LEDn m LED_OUT2 LEDn m LEDn: m: LED number whose displayed data is being output Output data position H: High-order 16 bits L: Low-order 16 bits -- To display specifications for LED_OUT2: : LED_OUT2 (RET) LED_OUT2 LEDn m Examples 1. To output the high-order 16 bits of the data displayed by LED2 from analog output terminal 1: :LT1 2 H (RET) : 2. To display the specifications for analog output terminals 1 and 2: :LT (RET) LED_OUT1 LED1 L LED_OUT2 LED2 L : 7-78 7.2.26 MAP Specifies, displays, or cancels memory attribute(s) MAP MP Command Format * * * Specification Display Cancellation : MAP<start address><end address>;<memory attribute> (RET) : MAP[<start address><end address>] (RET) : MAP[]-; (W/G) (RET) <start address>: Start address of memory area whose attribute is to be specified or displayed <end address>: End address of memory area whose attribute is to be specified or displayed <memory attribute>: U: Memory in the user system S: Emulation memory in the emulator pod SW: Emulation memory with write protection in the emulator pod SG: Emulation memory with access inhibition in the emulator pod E: Optional memory board EW: Optional memory board with write protection EG: Optional memory board with access inhibition W: Read-only memory (write-protected) area G: Guarded memory area (access-inhibited) Description * Specification -- Allocates standard emulation memory or optional emulation memory board * Standard emulation memory allocation Allocates standard emulation memory (512 kbytes) in the emulator pod in 128-kbyte units. The emulation memory can be write-protected or access-inhibited by specifying SW or SG, respectively. The start address is rounded down to 0 or a multiple of H'20000, and the end address is rounded up to a multiple of H'20000, minus one. Note, however, that, when the MCU has only 64 kbytes of memory space, the start and end addresses must be H'0 and H'FFFF, respectively. (In this case, however, remaining memory space is reduced by 128 kbytes.) : MAP 0 1FFFF;S (RET) 7-79 MAP * Memory board (option) emulation memory allocation Memory board (option) is allocated in 1-Mbyte units. The emulation memory can be write-protected or access-inhibited by specifying EW or EG, respectively. The start address is rounded down to 0 or a multiple of H'100000, and the end address is rounded up to a multiple of H'100000, minus one. Note, however, that when the operating frequency is 12 MHz or more, memory board emulation memory must not be assigned to a 2-state access area. : MAP 0 FFFFF;E (RET) Both emulation memories can be accessed in real time in parallel mode. To move the memory to the user system, specify option U. After allocation, the size of the unused emulation memory is displayed. REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx S = xxxxx (Standard emulation memory) E = xxxxxx (Optional emulation memory) -- One write-protected area and one access-inhibited area can be allocated in 128-kbyte units independently of the emulation memory allocation. Write protected: Program execution stops when the area is written to by the user program Access inhibited: Program execution stops when the area is accessed (read/written) by the user program With an emulator command, the user can read from and write to the write-protected area. In single chip mode, the UNUSABLE area has already been specified as access-inhibited at start up. * Display -- Displays the memory attributes of the area defined by <start address> and <end address>, in the following format: : MAP <start address> <end address> (RET) xxxxxx-xxxxxx;x INTERNAL ROM = xxxxxx-xxxxxx INTERNAL FLASH = xxxxxx-xxxxxx INTERNAL RAM = xxxxxx-xxxxxx INTERNAL I/O = xxxxxx-xxxxxx GUARDED AREA = xxxxxx-xxxxxx WRITE PROTECT AREA= xxxxxx-xxxxxx REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx 7-80 (a) (b) (c) (d) (e) (f) (g) MAP (a) Address range and memory attributes (b) Internal ROM address range (displayed only when the MCU has an internal ROM) (c) Internal flash memory address range (displayed only when the MCU has an internal flash memory) (d) Internal RAM address range (e) Internal I/O address range (f) Guarded memory area and write-protected area address ranges (displayed only when they are specified) (g) Unused emulation memory size in hexadecimal S=xxxxx (Standard emulation memory) E=xxxxxx (Optional emulation memory) -- When no address is specified, the memory attributes of the whole memory area are displayed in the format shown above. * Cancellation Cancels the write protection and access inhibition specifications. : MAP - ;W (RET) Cancels all write protection specifications. : MAP - ;G (RET) Cancels all access inhibition specifications. Notes 1. If there is not enough emulation memory to satisfy the specification, the attribute is specified only for the memory area available. 2. Emulation memory cannot be allocated to the internal ROM (flash memory), internal RAM, and internal I/O areas. These areas cannot be specified as a write-protected or access-inhibited area. 3. Optional memory (E) should not be allocated to a 2-state access area; if it is, it may not be accessed correctly. Standard memory (S) must be assigned to 2-state access areas. 4. Emulation memory may be temporarily assigned to an unusable area in single-chip mode. However, in the actual MCU, note that an unusable area cannot be accessed. 7-81 MAP Examples 1. To allocate standard emulation memory to the address range from H'0 to H'1FFFF: :MP 0 H'1FFFF;S (RET) REMAINS EMULATION MEMORY : 2. S=60000/E=000000 To make the address range from H'40000 to H'5FFFF write-protected: :MP 40000 5FFFF ;W (RET) : 7-82 7.2.27 MEMORY M MEMORY Displays or modifies memory contents Command Format * Display, modification : MEMORY<modification address>[<data>][;[<option>] [N]] (RET) <modification address>: Address of memory area to be displayed or modified <data>: Data to be written to the address <option>: Length of display or modification unit B: 1 byte W: 2 bytes L: 4 bytes O: Odd address, 1 byte E: Even address, 1 byte Default: 1 byte N: No verification Description * Display, modification -- If the <data> is omitted, the emulator displays memory contents at the specified address and enters input wait state of the modified data. The user can then enter data and modify memory contents; this process can then be repeated for the next address. If option N is not specified, the data to be modified is read and verified. Data in the internal I/O area is never verified. Memory contents are displayed and modified data is input in the following format. 7-83 MEMORY : MEMORY <address> (RET) xxxxxx yyyyyyyy ? [<data>][;<option>] (RET) xxxxxx: Address of data to be modified yyyyyyyy: Memory contents displayed in modification units. <data>: Modification data. Data length is considered to be the same as that of the data displayed on the screen. If only the (RET) key is pressed, data is not modified, and the next address is displayed. <option>: The unit of display or modification can be changed, or the address can be incremented or decremented. When <data> is specified, <option> is processed after the data is modified. When <data> is not specified, a semicolon (;) can be omitted to specify options L, W, O, ^, =, or (period). Table 7-13 lists option functions. Table 7-13 MEMORY Command Options Option Description B 1 byte W 2 bytes L 4 bytes O Odd address, 1 byte E Even address, 1 byte ^ Display of previous address contents = Display of current address contents . Command termination Default Display of next address contents -- When specifying <address> and <data>, memory contents are modified immediately and the emulator waits for the next command input. : MEMORY H'FFF0 H'F8 (RET) : 7-84 MEMORY Note This command can be executed in parallel mode. When the user system memory or internal I/O area contents are displayed, the program stops at every display or when writing is performed. The emulator therefore, does not operate in realtime. Software standby and sleep states are cancelled and program starts to execute from the next instruction of the SLEEP instruction. In the emulation memory, internal ROM (flash memory), and internal RAM, the emulator operates in realtime. Their contents are not displayed in software standby or sleep state. Examples 1. To modify memory contents from address H'1000: :M 1000 (RET) 001000 00 ? FF (RET) 001001 01 ? 10 (RET) 001002 22 ? (RET) 001003 00 ? 30;W (RET) 001004 0000 ? 1234 (RET) 001006 1100 ? ^ (RET) 001004 1234 ? ;L (RET) 001004 12341100 ? 12345678 (RET) 001008 00000000 ? . (RET) : 2. To modify memory contents from address H'8000 in 2-byte units without verification: :M 8000 008000 008002 008004 : 3. ;W N (RET) 0000 ? FF (RET) 0002 ? 1000 (RET) FFF2 ? . (RET) To write the data H'10 to address H'FE00 without displaying the memory contents: :M FE00 10 (RET) : 7-85 7.2.28 MODE MODE MD Specifies or displays MCU operating mode Command Format * * Specification : MODE;C (RET) Display : MODE (RET) Description * Specification -- Interactively specifies MCU operating mode as shown below. : MODE;C (RET) MCU NAME (1:H8/3048, 2:H8/3047, 3:H8/3044, 4:H8/3048F) ? (a) (RET) OPERATION MODE ? (b) (RET) CONFIGURATION WRITE OK (Y/N) ? (c) (RET) (a) MCU type Example: Input 3 to select H8/3044. (b) MCU operating mode setting Example: Input 6 to select operating mode 6. (c) Verification message of specification Input Y to perform specification and N to cancel specification. -- Since the specified MCU type and operating mode are written to the configuration file when the E7000 is used, a writable system disk must be set up before MODE command execution. After the MCU type and operating mode are recorded in the configuration file, the E7000 can be initiated as the specified MCU type and operating mode. When the E7000PC is used, the MCU operating mode is written in the configuration file in the directory where the current system program is stored on the IBM PC. The emulator terminates after the MCU operating mode is set, and must then be restarted. 7-86 MODE * Display Displays the MCU type, operating mode on the emulator, number of MCU pins, and the MCU operating mode selection pin (MD0-MD2) status on the user system in the following format: : MODE (RET) MCU NAME = H8/3048 (a) (a) (b) (c) (d) MODE = x (b) PIN = xxx (c) (MD2-0=n) (d) MCU type Operating mode Number of pins MD0 to MD2 pin status on the user system (Refer to table 7-14.) Table 7-14 Operating Mode Selection Pin Status and Display MD2 MD1 MD0 Display (n) Low Low Low 0 Low Low High 1 Low High Low 2 Low High High 3 High Low Low 4 High Low High 5 High High Low 6 High High High 7 Note The emulator operating mode is specified by the MODE command, regardless of the operating mode selection pin (MD0 to MD2) status on the user system. 7-87 MODE Examples 1. To specify the current MCU type as H8/3047 and the operating mode as mode5: :MD;C (RET) MCU NAME (1:H8/3048,2:H8/3047,3:H8/3044,4:H8/3048F) ? 2 (RET) OPERATION MODE ? 5 (RET) CONFIGURATION WRITE OK (Y/N) ? Y (RET) START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? S (RET) 2. (Emulator is restarted by S) To display the current MCU type, operating mode, and operating mode selection pin (MD0 to MD2) status: :MD (RET) MCU NAME=H8/3047 MODE=5 PIN=100 (MD2-0=7) : 7-88 MOVE 7.2.29 MOVE MV Transfers memory contents Command Format * Move data : MOVE<start address>(<end address>/@<number of bytes>) <destination address> (RET) <start address>: <end address>: <number of bytes>: <destination address>: Start address of source area End address of source area The number of bytes to be transferred Start address of destination Description * Move data -- Transfers the contents of the memory area specified with <start address>, <end address>, and <number of bytes> to <destination address>. Transfer is usually performed from the <start address> in byte units. However, if <destination address> is set within the range from <start address> to <end address> or <number of bytes>, transfer is performed from the <end address> or <start address> + <number of bytes> - 1. -- Verifies the transfer. If a verification error occurs, FAILED AT xxxxxx WRITE = yy 'y' READ = zz 'z' is displayed. xxxxxx: Address of error yy 'y': Write data (hexadecimal and ASCII character) zz 'z': Read data (hexadecimal and ASCII character) If data is to be written to or from an area including the internal I/O area, the following warning message is displayed: *** 86:INTERNAL I/O AREA In this case, data is written to addresses other than the internal I/O area. 7-89 MOVE Example To transfer data in the address range from H'101C to H'10FC to address H'1000: :MV 101C 10FC 1000 (RET) : 7-90 7.2.30 MOVE_TO_RAM MR MOVE_TO_RAM Moves contents of ROM to emulation memory Command Format * Movement : MOVE_TO_RAM<start address><end address> [;<memory attribute>] (RET) <start address>: Start address of the ROM area to be moved <end address>: End address of the ROM area to be moved <memory attribute>: Type of emulation memory to be allocated S: Standard emulation memory installed in emulator pod SW: Standard emulation memory with write protection installed in emulator pod E: Optional memory board EW: Optional memory board with write protection Default: Standard emulation memory installed in emulator pod (S) Description * Movement -- Use this command to temporarily modify ROM contents in the user system and execute the modified program. Transfers ROM contents to the specified emulation memory area. Data is transferred to standard emulation memory and optional emulation memory in 128-kbyte units and 1-Mbyte units, respectively. After data transfer, the unused emulation memory area is displayed as follows: REMAINS EMULATION MEMORY S=xxxxx/E=xxxxxx S=xxxxx (Standard emulation memory) E=xxxxxx (Optional emulation memory) -- If the internal ROM (flash memory) or I/O area is included in the specified transfer area, data transfer is performed in areas other than these areas. Note This function cannot be used in single-chip mode. Example To allocate standard emulation memory to the address range from H'0 to H'1FFFF in the user system ROM area and transfer ROM contents: :MR 0 1FFFF;S (RET) REMAINS EMULATION MEMORY : S=60000/E=000000 7-91 PERFORMANCE_ANALYSIS 7.2.31 PERFORMANCE_ANALYSIS Specifies, deletes, initializes, or displays PA performance measurement data Command Format * Specification * * * Cancellation Initialization Display : PERFORMANCE_ANALYSIS<subroutine name><start address> <end address> (RET) : PERFORMANCE_ANALYSIS[]-[<subroutine name>] (RET) : PERFORMANCE_ANALYSISI (RET) : PERFORMANCE_ANALYSIS[V] (RET) <subroutine name>: Name of the subroutine whose execution performance is to be measured. Any name can be specified other than I or V. <start address>: Subroutine entry address <end address>: Subroutine exit address I: Initializes execution performance measurement information. V: Displays in numeric values performance results such as execution time, number of times executed, and total run-time. If V is omitted, execution time rate is displayed in graph form. Description * Specification -- Measures the execution time of the subroutine defined by the start and end address parameters during user program execution initiated with the GO command. Measurement starts when an address within the range from the start address to the end address is prefetched, and is suspended when an address outside of the range is prefetched. Measurement resumes when an address within the specified range is again prefetched. The number of times these subroutines are executed can also be counted. The subroutine execution count is incremented every time the subroutine exit address is passed. -- While the measurement and execution count are performed in realtime, please note the following: a. This command measures execution time and counts during program prefetch. While executing the preceding subroutine (which has a lower address), the subroutine to be measured is fetched. Even if interrupt processing starts immediately after that and the program is not yet being executed, execution time measurement and counting begin. b. Execution count is doubled when the measured subroutine is in the 8-bit data bus access area. 7-92 PERFORMANCE_ANALYSIS -- Up to four subroutines can be specified. -- The PERFORMANCE_ANALYSIS command cannot be executed during program execution of the STEP or STEP_OVER command. Likewise, it cannot be executed when time measurement mode 1 or 2 is specified with the GO command. * Cancellation -- Cancels execution performance measurement corresponding to the specified subroutine. -- If the subroutine name is omitted, all subroutines for execution performance measurement are cancelled. * Initialization Clears the current execution time and execution count for all subroutines, as well as the total run-time. The total run-time begins to be measured only after the subroutines measured by this command are assigned. * Display Displays execution performance measurement results, in either of the following two formats: -- Execution time ratio displayed in graph form. (Option V is not specified.) :PERFORMANCE_ANALYSIS (RET) NAME S-ADDR E-ADDR RATE 0------------------50------------------100 SUBA 000100 001FF3 D'10.0% **** SUBB 002030 00215F D'20.0% ******** SUBC 003000 003457 D'15.0% ****** (a) (b) (c) (d) (e) ------------------------------------------------------------------------------------------------------------TOTAL RUN-TIME = D'0000H:10M:00S:000020US[:250NS] (f) (a) (b) (c) (d) (e) (f) Subroutine name (the eight characters at the head of the subroutine name) Subroutine start address Subroutine end address Execution time as a percentage Execution time ratio in graph form (in units of 2.5%/asterisk, rounded up) Total run-time displayed as H (hour), M (minute), S (second), US (microsecond), and NS (nanosecond). However, when minimum measurement time is specified as 1 s by the TIME option of the EXECUTION_MODE command, NS display is not available. 7-93 PERFORMANCE_ANALYSIS -- Execution time and number of executions are displayed as numerical values. (Option V is specified.) :PERFORMANCE_ANALYSIS V (RET) NAME SUBA SUBB S-ADDR 000100 002030 E-ADDR 001FF0 00215F RATE D'10.0% D'20.0% RUN-TIME D'0000H:00M:05S:001000US[:250NS] D'0000H:00M:10S:010305US[:500NS] E-COUNT D'00005 D'00010 (a) (b) (c) (d) (e) (f) ------------------------------------------------------------------------------------------------------------TOTAL RUN-TIME = D'0001H:00M:50S:000020US[:250NS] (g) (a) (b) (c) (d) (e) (f) (g) Subroutine name (the eight characters at the head of the subroutine name) Subroutine start address Subroutine end address Execution time as a percentage Execution time Number of executions (If 65,535 is exceeded, ***** is displayed) Total run-time Note If the minimum measurement time is specified by the TIME option of the EXECUTION_MODE command as 1 s, the maximum measurable time is approximately 305 hours. Alternatively, if it is specified as 250 ns, it is approximately 76 hours. Examples 1. To measure the execution time of subroutines SUBD (H'5204 to H'5E00) and SUBE (H'787E to H'7EF0) and to initialize the measurement data: :PA SUBD 5204 5E00 (RET) :PA SUBE 787E 7EF0 (RET) :PA I (RET) : 7-94 PERFORMANCE_ANALYSIS 2. To display execution time ratio in graph form: :PA (RET) N A M E S-ADDR E-ADDR RATE 0------------50---------100 SUBD 0 0 5 2 0 4 005E00 D'10.0% **** SUBE 00787E 007EF0 D'20.0% ******** ------------------------------------------------------------TOTAL RUN-TIME = D'0000H:00M:50S:000020US 3. To display execution time and number of executions in numerical form: :PA V (RET) NAME S-ADDR E-ADDR RATE RUN-TIME E-COUNT SUBA 000100 001FF0 D'10.0% D'0000H:00M:05S:001000US D'04024 SUBB 002030 00215F D'20.0% D'0000H:00M:10S:010305US D'09566 --------------------------------------------------------------------------TOTAL RUN-TIME = D'0001H:00M:50S:000020US 4. To cancel all registered subroutines: :PA - (RET) : 7-95 7.2.32 PRINT PRINT P Assigns or cancels output device for command result display (specific to the E7000) Command Format * Assignment : PRINT (RET) : PRINT<file name> (RET) * Cancellation : PRINT[]- (RET) (Selects printer) (Selects file) <file name>: Name of file where display information is to be stored Description * Assignment -- Assigns either the printer or a file (FD) to output command results, such as command inputs, execution results, and error messages. -- If the file already exists, the following message is displayed: OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites existing file. N: Aborts the command. -- The following data are not output to the printer or file: * * * Program counter during GO command execution HELP messages for each command (HELP <command name>) Addresses being loaded, saved, or verified -- This command is specific to the E7000. To use a printer in the E7000PC, use the logging function to the IBM PC files. For details, refer to section 3.7.2, Debugging Functions, in Part II, E7000PC Guide. * Cancellation Cancels the currently assigned printer or file. 7-96 PRINT Notes 1. Do not eject the floppy disk when a file is assigned. 2. To change the output destination from a printer or file that was previously assigned with this command, first cancel the assignment and then reassign the output to the new destination. Examples 1. To assign a printer: :P (RET) : 2. To assign the existing file SAMPLE.LOG: :P SAMPLE.LOG (RET) OVERWRITE(Y/N) ? Y (RET) : 7-97 7.2.33 QUIT QUIT Q Terminates emulator system program Command Format * Termination : QUIT [<file name>[;S]] (RET) <file name>: Name of the file to contain emulation information (table 7-15) S: Option to save symbol information Description * Termination -- Terminates the emulator system program, puts the emulator monitor in command input wait state, and displays: : QUIT (RET) START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/L/B/F/T) ? _ Cursor 7-98 QUIT -- Stores emulation information (shown in table 7-15) in the specified file and terminates the emulator system program. The emulation information can be restored later if the emulator system program is initiated with warm start. Specify the S option to store symbol information. Note, however, that symbol information may require too big an amount of memory to be saved in a file. : QUIT <file name> (RET) If the specified file already exists, the following message is displayed: OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites existing file. N: Aborts the command, and enters emulator system program command input wait state. Table 7-15 Emulation Information Saved with the QUIT Command Item Description PC breakpoints Information set by the BREAK and BREAK_SEQUENCE commands Hardware break conditions Information set by the BREAK_CONDITION1,2,3,4 command Trace condition Information set by the TRACE_CONDITION, TRACE_MODE, and TRACE_MEMORY commands Memory map Information set by the MAP command Performance analysis information Information set by the PERFORMANCE_ANALYSIS command Coverage information Coverage acquisition status Emulation operating mode Information set by the EXECUTION_MODE command Configuration information Configuration file contents Symbol information Registered symbol information (Only available when the S option is specified) LED display information Information set by LED1,2,3,4 and LED_OUT1,2 commands Note In the E7000, a file to store emulation information as listed in table 7-15 is created on a floppy disk. In the E7000PC, on the other hand, the file is created in the current directory of the IBM PC. To store emulation information in another directory, specify that directory name. 7-99 QUIT Example To save emulation information in file SAMPLE.INF and terminate the emulator system: :QUIT SAMPLE.INF (RET) START E7000 S: START E7000 R: RELOAD & START E7000 B: BACKUP FD F: FORMAT FD L: SET LAN PARAMETER T: START DIAGNOSTIC TEST (S/R/B/F/L/T) ? _ 7-100 7.2.34 RADIX Specifies and displays radix for numeric input RADIX RX Command Format * * Specification : RADIX<radix> (RET) Display : RADIX (RET) <radix>: Radix to be used for input of numeric values H: Hexadecimal (default at emulator system program initiation) D: Decimal Q: Octal B: Binary Description * Specification -- Specifies the radix used by the emulator to interpret numbers entered on the command line. -- The RADIX command sets the radix to be used for numbers entered simply as numbers. Hexadecimal is used at emulator activation. Numbers may be entered in any radix at any time, provided that each value is prefixed with the appropriate character. Table 7-16 Radix and Input Examples Radix Input Example Binary B'1010 Octal Q'2370 Decimal D'6904 Hexadecimal H'AF10 7-101 RADIX * Display Displays the currently set radix as follows: RADIX = Radix character Radix character, displayed as one of the following: B: BINARY Q: OCTAL D: DECIMAL H: HEX DECIMAL Binary Octal Decimal Hexadecimal Note The specified radix applies to the input of numeric values only; it does not affect display. To specify line number symbols, enter in decimal. Examples 1. To set the radix to decimal: :RX D (RET) :B 10 (RET) : 2. (10 is input in decimal) To display the current radix: :RADIX (RET) RADIX = D:DECIMAL : 7-102 REGISTER 7.2.35 REGISTER R Displays register contents Command Format * Display : REGISTER (RET) Description * Display Displays all register contents. Example To display all register contents: :R (RET) PC=001000 ER0 - ER3 ER4 - ER7 : CCR=80:I******* 00000000 00000001 00000002 00000003 00000008 00000009 0000000A 0000F000 7-103 7.2.36 RESET RESET RS Resets MCU Command Format * Reset : RESET (RET) Description * Reset Resets the MCU. The MCU general-purpose and control register contents will be reset to the following values: ER0 to ER6 : The value before reset ER7 (SP) : The value before reset PC : Reset vector value CCR : H'80 The internal I/O register contents will also be reset. Example To reset the MCU: :RS (RET) ** RESET IN BY E7000! : 7-104 RESULT 7.2.37 RESULT RT Displays execution results Command Format * Display : RESULT (RET) Description * Display Displays current register contents, execution time, and the GO, STEP, or STEP_OVER command termination cause. The display format is as follows: :RESULT (RET) -PC=001000 CCR=80:I******* -ER0 - ER3 00000000 00000001 00000002 00000003 -ER4 - ER7 00000008 00000009 0000000A 0000000B RUN-TIME=D'000H:00M:00S:000000US[:000NS] <cause of termination > [LINE NO=<line number symbol>+n] (a) Register contents at program termination (b) Execution time (c) Cause of termination. For a list of these causes, refer to section 7.2.20, GO, and section 7.2.41, STEP. (d) If line number symbols are registered, the stop address is displayed as the nearest <line number symbol> + n. Note Displayed register contents show values at program termination, not the current values. 7-105 (a) (b) (c) (d) RESULT Example To display execution results: :RT (RET) -PC=001000 CCR=80:I******* -ER0-ER3 00000000 00000001 00000002 00000003 -ER4-ER7 00000008 00000009 0000000A 0000000B RUN-TIME=D'000H:00M:00S:000124US BREAK POINT 002FF0 : 7-106 7.2.38 SET_COVERAGE SCV SET_COVERAGE Initializes the coverage trace function Command Format * Initialization : SET_COVERAGE (RET) Description * Initialization -- Initializes the coverage buffer, which acquires address access information during GO command execution. The coverage trace information begins to be acquired from the moment the emulator system is activated. The coverage trace range is within a 2-Mbyte memory space. When the MCU's memory space is 64 kbytes or 1 Mbyte, the coverage trace function for the whole area is acquired. However, if the memory space is 16 Mbytes, the coverage trace range is only a 2-Mbyte memory space, starting from the base address specified with the BS option of the EXECUTION_MODE command. Refer to section 7.2.18, EXECUTION_MODE. Note that the coverage trace range is the same as that in which PC breakpoints (including those specified by BREAK and BREAK_SEQUENCE commands) are specified. -- Coverage trace information is displayed with the DISPLAY_COVERAGE command. Example To initialize the coverage buffer: :SCV (RET) : 7-107 SHORT_SYMBOL 7.2.39 SHORT_SYMBOL SS Defines a short format for a symbol and displays current short formats Command Format * * Definition Display : SHORT_SYMBOL\n = <short-format symbol> (RET) : SHORT_SYMBOL (RET) n: Number from 1 to 5 <short-format symbol>: Abbreviated form of symbol Description * Definition -- Enables input of a short-format symbol, by defining a short format for the upper symbol or all symbols in a nested symbol sequence. Symbols in a nested sequence are delimited by slashes (/), as follows: !<name>/<name>/<name> ... &<name>/<line number> ... Normal symbols Line number symbols Example: : SHORT_SYMBOL \1=MAIN/SUB (RET) : BREAK !\1/ABC (RET) The above specification has the same meaning as the following: : BREAK !MAIN/SUB/ABC (RET) To define a short format for a symbol, the symbol must have already been defined. -- This command cannot delete the short format of a symbol, but the short format will be deleted if the corresponding symbol is deleted by the SYMBOL command. * Display Displays all previously defined short formats for review; blanks are displayed for symbols with no short formats. 7-108 SHORT_SYMBOL Note Short formats cannot be specified for <short-format symbol> in this command. Examples 1. To specify a short format for a nested sequence of symbols and set a PC breakpoint: :SS \2=msym/main/cmd0 (RET) :SS \3=msym/sub/cmd7 (RET) :B !\2,!\3 (RET) : 2. To display all current short formats: :SHORT_SYMBOL (RET) \1 = msym/sub/cmd1 \2 = msym/sub/cmd2 \3 = \4 = \5 = : 7-109 7.2.40 STATUS STATUS ST Displays emulator execution status Command Format * Display : STATUS (RET) Description * Display Displays emulator execution status in the following format: CPU=(a) MODE=(b) PIN=(c) RADIX=(d) HOST=(h) SYM=(i) LINE_SYM=(j) CLOCK=(m) PRINT=(n) BASE=(o) BREAK=(e) B_CND=(f) T_CND=(g) STEP_INFO=REG:(k) /A:(l) EML_MEM=S:(p)/E:(q) (a) CPU=xxxxxxx The CPU types are as follows. Example: H8/3048 (b) MODE=x: MCU operating mode specified with the MODE command (c) PIN=x: Number of MCU pins (d) RADIX=xxx: Default input number type BIN: Binary OCT: Octal DEC: Decimal HEX: Hexadecimal (e) BREAK=D'xxx: Number of breakpoints (decimal) (f) B_CND=xxxx: BREAK_CONDITION1,2,3,4 command setting. If specified, the specified number is displayed; otherwise, a blank is displayed. 7-110 STATUS (g) T_CND=xx: TRACE_CONDITION command setting ST: Subroutine trace mode R: Range trace mode S: Trace stop condition T: Trigger mode NO: No condition is set (h) HOST=x1x2x3x4x5: Host interface protocol. When the E7000PC is used, PC is displayed. x1: Baud rate (BPS: Bits per second) 1: 2400 BPS 2: 4800 BPS 3: 9600 BPS 4: 19200 BPS 5: 38400 BPS x2: Data length for one character 7: 7 bits 8: 8 bits x3: Parity E: Even O: Odd N: None x4: Number of stop bits 1: 1 stop bit 2: 2 stop bits x5: Busy control method X: X-ON/X-OFF control R: RTS/CTS control (i) SYM=D'xxxxx: Number of defined symbols (decimal) (j) LINE_SYM=D'xxxxx: Number of defined line number symbols (decimal) (k) STEP_INFO=REG:x1 x2: Register information provided by the STEP command x1 1: Control register (PC, CCR) information is displayed. Space: No control register (PC, CCR) information is displayed. x2 2: General-purpose register (ER0-ER7) information is displayed. Space: No General-purpose register (ER0-ER7) information is displayed. (l) /A:xxxxxx-xxxxxx: Memory address displayed with the STEP command. (m) CLOCK=xx: Clock signal type 13 MHz: 13-MHz emulator internal clock signal 18 MHz: 18-MHz emulator internal clock signal USER: User system clock signal X'TAL: Crystal oscillator clock signal of the emulator pod 7-111 STATUS (n) PRINT=<file name>: File to which data is displayed on the console being output. If data is being output to a printer, #PR is displayed instead of <file name>. If no file name is specified, nothing is displayed. (o) BASE=x: Indicates the PC break and coverage trace address range specified by the BS option of the EXECUTION_MODE command 0: 1: 2: E: F: x1 = 0 to F 000000 to 1FFFFF 100000 to 2FFFFF 200000 to 3FFFFF : E00000 to FFFFFF F00000 to FFFFFF and 000000 to 0FFFFF (p), (q) EML_MEM=S:xxxxKB/E:yyyyKB: Indicates the remaining size in the standard emulation memory and optional memory boards. xxxx: Remaining size in standard emulation memory yyyy: Remaining size in optional memory boards Example To display the emulator status: :ST (RET) CPU=H8/3048 MODE=3 PIN=100 RADIX=HEX BREAK=D'001 B_CND=1 3 T_COND=NO HOST=38N1X SYM=D'00254 LINE_SYM=D'00786 STEP_INFO=REG:12/A: CLOCK=13MHz PRINT=X1 BASE=0 EML_MEM=S:0384KB/E:0000KB : 7-112 7.2.41 STEP S STEP Performs single-step execution Command Format * Single step : STEP [<number of execution steps>[<start PC>]] [;[<stop PC>][<display option>][I]] (RET) <number of execution steps>: Number of steps to be executed (H'1 to H'FFFFFFFF). Default: If <stop PC> and <display option> are specified, H'FFFFFFFF is assumed. If not, 1 is assumed. <start PC>: Start address of single-step execution. Default is the current PC address. <stop PC>: Address when the single-step execution is terminated. Default is <number of execution steps>. <display option>: Specification of instructions to be displayed J: Displays instruction and register contents only when a branch instruction is executed R: Displays instruction and register contents only within the opening routine Default: Displays instructions and register contents for all executed instructions I: Enables interrupts during single-step execution 7-113 STEP Description * Single step -- Performs single-step execution beginning at <start PC>. The type of emulation performed (described below) depends on the specified parameters and option. In addition, register and memory contents, address and instruction mnemonic information, and termination cause can be displayed in the following format: (a) PC=001000 CCR=80:I******* ER0 - ER3 00000000 00000001 00000002 00000003 ER4 - ER7 00000008 00000009 0000000A 0000000B (b) <address> <instruction mnemonic> (c) MEMORY <memory contents> (d) <cause of termination> (a) (b) (c) (d) Register information Address and mnemonic of the instruction that was executed Memory contents display Cause of termination Information (a) and (c) is displayed according to specifications made with the STEP_INFORMATION command. The termination cause, (d), is displayed only when the STEP command is completed. The causes are listed in table 7-17. 7-114 STEP Table 7-17 Causes of STEP Command Emulation Termination Message Description BREAK KEY The BREAK key or (CTRL) + C keys were pressed. STEP NORMAL END The specified number of steps were executed. STOP ADDRESS The instruction at the address specified as stop PC was executed. BREAK CONDITION 1 A break condition specified with the BREAK_CONDITION1 command was satisfied. BREAK CONDITION 2 A break condition specified with the BREAK_CONDITION2 command was satisfied. BREAK CONDITION 3 A break condition specified with the BREAK_CONDITION3 command was satisfied. BREAK CONDITION 4 A break condition specified with the BREAK_CONDITION4 command was satisfied. BREAK CONDITION 1,2,3,4 Break conditions specified with the BREAK_CONDITION1,2,3,4 command were satisfied. GUARDED AREA ACCESSED A guarded memory area was accessed. WRITE PROTECT A write-protected or internal ROM (flash memory) area was written to. ILLEGAL INSTRUCTION A break instruction (H'5740-H'577F) was executed. RESET IN BY E7000 A problem occurred in the user system. The emulator has input the RES signal for forced termination. DMA GUARDED OR WRITE PTOTECT A write-protected area was written to or a guarded memory area was accessed by DMA. INVALID SP ADDRESS The stack pointer points to the internal I/O area. 7-115 STEP -- If <display option> is omitted, instruction mnemonics and register information are displayed for each step executed. : STEP <number of execution steps> [<start PC>] (RET) -- Instruction mnemonics and register information are also displayed for each step when <stop PC> is specified, and single-step emulation is executed until the instruction at <stop PC> is executed. : STEP [<number of execution steps> [<start PC>]]; <stop PC> (RET) -- If the J option is specified, instruction mnemonics and register information are displayed only for branch instructions, and single-step emulation is executed until the instruction at <stop PC> is executed. : STEP [<number of execution steps> [<start PC>]];[<stop PC>] J (RET) The following instructions are valid when the J option is specified: Bcc, BRA, BRN, JMP, BSR, JSR -- If the R option is specified, instruction mnemonics and register information are displayed only during execution within the opening routine. At that time, single-step execution continues until the instruction at <stop PC> is executed. The jump addresses of branch instructions, such as JSR or BSR, are not displayed. This function is similar to the STEP_OVER command function. If the instruction is in RAM (including internal ROM, flash memory, RAM, and emulation memory), use the STEP_OVER command whose execution time is shorter. : STEP [<number of execution steps> [<start PC>]];[<stop PC>] R (RET) -- No interrupts are accepted during single-step execution, unless the I option has been specified. -- After the STEP command has been executed (so long as it was not forcibly terminated), and if no other command has been entered, single-step execution can be continued by simply pressing the (RET) key. -- <stop PC> must be the first address of an instruction. If not, execution does not stop. 7-116 STEP Notes 1. The emulator does not operate correctly when the stack pointer (ER7; R7 in a 64-kbyte memory area) points to the internal I/O area, during or after STEP command execution. Make sure the stack pointer points to an address within the following range: H'000004 to (start address of internal I/O area + 1) If not, one of the following cases will occur: -- Execution starts The user program will not be executed and the error message, ***49:INVALID SP ADDRESS will be displayed. -- Execution stops The internal I/O registers will have been rewritten. Set the internal registers and SP to the correct values before re-execution. The cause for termination will be displayed as INVALID SP ADDRESS. 2. PC breakpoints (including those specified by the BREAK and BREAK_SEQUENCE commands) are ignored during single-step execution. 3. If VPP = E is specified with the EXECUTION_MODE command (12-V power application from E7000 to VPP), the flash memory modification can be emulated even if the 12-V power is not applied from the user system to the VPP pin. 7-117 STEP Examples 1. To execute a program one step at a time, starting from the address given by the current PC: :S (RET) PC=001002 CCR=80:I******* ER0 - ER3 00000000 00000000 00000002 ER4 - ER7 00000008 00000009 0000000A 001000 MOV.W R0,R1 STEP NORMAL END :(RET) PC=001004 CCR=80:I******* ER0 - ER3 00000000 00000000 00000002 ER4 - ER7 00000001 00000009 0000000A 001002 MOV.W #0001:16,R4 STEP NORMAL END 00000003 0000FF00 00000003 0000FF00 : 2. To perform single-step execution from address H'1060 to H'1070 with information displayed only for branch instructions: :S FFFF 1060 ;1070 J (RET) PC=00106A CCR=84:I****Z** ER0 - ER3 00000000 00000000 00000044 000000FF ER4 - ER7 00000008 00020000 0000000A 0000FF00 001064 JMP @00106A:16 PC=001072 CCR=80:I******* ER0 - ER3 00000000 00000000 00000044 000000FF ER4 - ER7 00000008 00020000 0000000A 0000FF00 001070 NOP STOP ADDRESS : 7-118 7.2.42 STEP_INFORMATION SI STEP_INFORMATION Specifies or displays information during single-step execution Command Format * Specification : STEP_INFORMATION[<register information>][A=<start address> [(<end address>/@<number of bytes>)]] (RET) * Display : STEP_INFORMATION (RET) <register information>: Register to be displayed 1: Displays PC and CCR 2: Displays ER0 to ER7 ALL: All register information is output (default specification at emulator initiation) -: No information displayed Default: ALL <start address>: Start address of memory dump <end address>: End address of memory dump. (Default is 16 bytes of memory beginning at the start address.) <number of bytes>: The number of bytes of memory dump. (Default is 16 bytes.) Description * Specification Displays register information, executed instruction information, memory contents, and cause of termination during STEP and STEP_OVER command execution. This command also selects the range of register information and memory contents which are to be displayed. 7-119 STEP_INFORMATION (a) PC=005C60 CCR=80:I******* (b) ER0 - ER3 00000000 00000001 00000002 00000003 ER4 - ER7 00000008 00000009 0000000A 0000000B (c) 00F0F2 NOP (d) MEMORY 00FF80 00 04 00 FF F0 00 02 00 10 00 02 00 0F 00 00 00 "................" (e) STEP NORMAL END (a) (b) (c) (d) (e) * Control register information (PC and CCR) General-purpose register information (ER0 to ER7) Address and assembler mnemonic of executed instruction Memory contents display Cause of termination Display Displays STEP information according to the specified contents. However, the address and assembler instruction mnemonic of each executed instruction are not displayed. Examples 1. To display only the contents of control registers (PC and CCR) during STEP and STEP_OVER command execution: :SI 1 (RET) : 2. To not display register information during STEP and STEP_OVER command execution: :SI - (RET) : 3. To display memory contents from address H'FB80 to H'FB87 during STEP and STEP_OVER command execution: :SI : A=FB80 FB87 (RET) 7-120 STEP_INFORMATION 4. To display contents according to the specified display information: :SI (RET) PC=005C60 CCR=80:I******* ER0 - ER3 0000000 00000001 00000002 00000003 ER4 - ER7 0000008 00000009 0000000A 0000000B MEMORY 00FB80 00 04 00 FF F0 00 02 00 ".............." : 7-121 STEP_OVER 7.2.43 STEP_OVER SO Performs single-step execution except for subroutines Command Format * Execution : STEP_OVER [<start PC>] [;I] (RET) <start PC>: Address of the start of single-step execution. Default is the current PC address. I: Enables interrupts during single-step execution. Description * Execution -- Performs single-step execution of instructions, except for subroutines called by the BSR, JSR, or TRAPA instructions beginning at <start PC>. If BSR, JSR, or TRAPA is executed, acts as if the subroutine called by the BSR, JSR, or TRAPA is a single instruction. If an instruction other than BSR, JSR, or TRAPA is executed, like the STEP command, register contents and the executed instruction are shown after each instruction is executed. -- If BSR, JSR, or TRAPA is executed, the STEP_OVER command replaces the instruction following the BSR, JSR, or TRAPA with an instruction (H'5770) for the emulator and executes the user program. Accordingly, this command cannot be used for ROM. For ROM, transfer the program to emulation memory using the MOVE_TO_RAM command. Usable areas of STEP_OVER command: Internal ROM (flash memory), internal RAM, area to be allocated with emulation memory, and RAM in user system -- During STEP_OVER command execution, register contents can be displayed in the following format. The range of register information and memory contents are displayed according to the STEP_INFORMATION command specifications. 7-122 STEP_OVER (a) PC=001000 CCR=80:I******* ER0-ER3 00000000 00000001 00000002 00000003 ER4-ER7 00000008 00000009 0000000A 0000000B (b) <address> <instruction mnemonic> (c) MEMORY <memory contents> (d) <cause of termination> (a) (b) (c) (d) Register information Address and mnemonic of the instruction that was executed Memory contents display Cause of termination -- After the STEP_OVER command has been executed (so long as it was not forcibly terminated), and if no other command has been entered, single-step execution can be continued by simply pressing the (RET) key. -- The PC breakpoints (BREAK and BREAK_SEQUENCE specifications) and hardware breaks (BREAK_CONDITION1,2,3,4 specifications) are invalid during STEP_OVER command execution. -- No interrupts are accepted during single-step execution, unless the I option has been specified. Table 7-18 Causes of STEP_OVER Command Emulation Termination Message Description BREAK KEY The BREAK key or (CTRL) + C keys were pressed. ONE STEP END Single-step execution was completed. SUBROUTINE END Subroutine execution was completed. GUARDED AREA ACCESSED A guarded memory area was accessed. WRITE PROTECT A write-protected area or internal ROM (flash memory) area was written to. ILLEGAL INSTRUCTION A break instruction (H'5740-H'577F) was executed. RESET IN BY E7000 A problem occurred in the user system. The emulator had input the RES signal for forced termination. SUBROUTINE END ADDRESS IS NOT RAM Being in the ROM area, the end address cannot be executed. (Refer to descriptions.) SUBROUTINE END ADDRESS IS BREAK INSTRUCTION The instruction following a JSR, BSR, or TRAPA is an illegal instruction (H'5770) INVALID SP ADDRESS The stack pointer is pointing to the internal I/O area. (Refer to notes.) 7-123 STEP_OVER Notes 1. The emulator does not operate correctly when the stack pointer (ER7; R7 in a 64-kbyte memory area) points to the internal I/O area, during or after STEP_OVER command execution. Make sure the stack pointer points to an address within the following range: H'000004 to (start address of internal I/O area + 1) If not, one of the following cases will occur: -- Execution start The user program will not be executed and the error message, ***49:INVALID SP ADDRESS will be displayed. -- Execution stop The internal I/O registers will have been rewritten. Set the internal registers and SP to the correct values before re-execution. The cause for termination will be displayed as INVALID SP ADDRESS. 2. Use this command only when returning to the instruction following a subroutine called by the JSR, BSR, or TRAPA instruction. However, because this command writes over the instruction following the JSR, BSR, or TRAPA instruction, do not use it if the instruction that will be modified is being used as data. 3. If VPP = E is specified with the EXECUTION_MODE command (12-V power application from E7000 to VPP), the flash memory modification can be emulated even if the 12-V power is not applied from the user system to the VPP pin. 7-124 STEP_OVER Example To execute a program one step at a time, starting from the address given by the current PC, and without displaying instructions within the called subroutine: :SO (RET) PC=001002 CCR=80:I******* ER0 - ER3 00000000 00000000 00000002 00000003 ER4 - ER7 00000008 00000009 0000000A 0000FF00 001000 MOV.W R0,R1 ONE STEP END :(RET) PC=001004 CCR=80:I******* ER0 - ER3 00000000 00000000 00000002 00000003 ER4 - ER7 00000001 00000009 0000000A 0000FF00 001002 MOV.W #0001:16,R4 ONE STEP END :(RET) PC=001008 CCR=80:I******* ER0 - ER3 00000000 00000000 00000044 000000FF ER4 - ER7 00000008 00020000 0000000A 0000FF00 001004 JSR @002010:24....(The subroutine is not SUBROUTINE END displayed) :(RET) PC=00100A CCR=80:I******* ER0 - ER3 00000000 00000000 00000044 000000FF ER4 - ER7 00000008 00020000 0000000A 0000FF00 001008 NOP ONE STEP END : 7-125 7.2.44 SYMBOL SYMBOL SY Defines, displays, or deletes symbol Command Format * * * Definition Display Deletion : SYMBOL!<symbol>=<address> (RET) : SYMBOL [!<symbol>] (RET) : SYMBOL[] - (RET) !<symbol>: Symbol to be defined <address>: Address of the symbol to be defined --: Deletes all symbol definitions Description * Definition -- Defines a symbol; the attribute of the defined symbol is label. : SYMBOL !LAB = H'FF00 (RET) -- The number of symbol definitions depends on the length of the symbol. Approximately 50,000 symbols can be defined with eight characters. * Display -- Displays a defined symbol. -- If no symbol is specified, all symbols are displayed. If a nested symbol is specified, all symbols below that symbol are displayed as well. * Display format is as follows: LEV x (a) SYMBOL xx......x (b) ATTRIBUTE xx.........x (c) ADDRESS xxxxxx (d) SIZE xxxx (e) ELEMENT xxxx (f) (a) Level number: Displays nesting level (0 to F) of the symbol. (Symbols with nesting levels upper than F cannot be defined.) (b) Symbol: Displays the symbol's name. A nested symbol is displayed as a symbol for each nesting level. Each symbol starts in the column that corresponds to its attribute, as shown in table 7-19. 7-126 SYMBOL Table 7-19 Symbol Attributes and Related Display Start Columns Attribute Start Column UNIT 0 PROCEDURE 1 STRUCTURE 2 or 3* VARIABLE 2 or 3* ARRAY 2 or 3* LABEL 2 POINTER 2 or 3* Note: If the symbol is a structure element, its name starts in column 3. (c) Attribute: Symbol attribute, as shown in table 7-20. Table 7-20 Symbol Attribute Display Attribute Contents UNIT Unit PROCEDURE Function STRUCTURE Structure VARIABLE Variable ARRAY Array LABEL Label POINTER Pointer (d) Address: Address of a symbol. For a structure element name, the offset value of the element from the start address of the structure is displayed. In this case, a plus sign (+) is placed in front of the address value. 7-127 SYMBOL (e) Size: One of the following sizes, depending on the attribute: Pointer: Pointer size Structure: Total structure size Variable: Variable size Array: Size of one element Others: Blank (f) Number of elements: The number of elements is displayed only when the attribute is an array. A blank is displayed for other attributes. * Deletion Deletes all symbols. However, symbols cannot be deleted if they are used by the following commands: BREAK BREAK_CONDITION1,2,3,4 BREAK_SEQUENCE TRACE_CONDITION LED1,2,3,4 TRACE_MEMORY Note The variable names of a structure must not be the same as the tag names. In the example below, change the variable names or omit the tag names. Example: struct xyz { int a; int b; } xyz ; (Tag name) (Variable) 7-128 SYMBOL Examples 1. To define the symbol SUBOO: :SY !SUBOO=450 : 2. (RET) To display all symbols: :SY (RET) LEV SYMBOL 0 MAIN 0 LOOP 0 SUBA 0 H8300POD : ATTRIBUTE ADDRESS LABEL 001000 LABEL 001100 LABEL 003000 LABEL 000330 7-129 SIZE ELEMENT 7.2.45 TRACE TRACE T Displays trace information Command Format * Display : TRACE[[-]<start pointer>[:[-]<end pointer>]][;[BP][B]] (RET) <start pointer>: Start pointer of trace display. (Default is the PTR option of TRACE_MODE.) <end pointer>: End pointer of trace display. (Default is the PTR option of TRACE_MODE.) -: A trace up until the break condition is satisfied is displayed. (This option is usually necessary, except for displaying trace information during delays when a delay count condition is specified by the TRACE_CONDITION or BREAK_CONDITION1 command.) BP: Bus-cycle pointers specified as pointer values. (Default is the instruction pointer.) B: Trace information is displayed in bus-cycle units. (Default is instruction mnemonic information.) Description * Display -- Displays trace information acquired during user program execution. Either instruction mnemonic or bus-cycle display format can be selected. a. The B option specifies display in bus-cycle units. : TRACE; B (RET) b. If B is omitted, only instruction mnemonic information is displayed. : TRACE (RET) 7-130 TRACE -- The display range can be specified with pointers in bus-cycle units (bus-cycle pointer) or instruction units (instruction pointer). The pointer value is specified as a relative value from the point where a delay condition is satisfied (See note). Trace information acquired before the delay condition is satisfied is displayed with a minus (-). To specify a bus-cycle pointer, the BP option must be selected. The default is the instruction pointer. Note: A delay starts to be counted from where a delay condition specified by the BREAK_CONDITION1 or TRACE_CONDITION command is satisfied. When no delay condition has been specified or termination has been caused by another reason, the current trace information will decide when the delay condition is to be satisfied. Oldest information Pointer Trace information - Display start pointer Condition satisfied Display range Display end pointer + Latest information Figure 7-2 Display Range Specified by Instruction Pointers Pointer default is as follows: a. If <start pointer> is omitted, the start pointer specified by the PTR option of the TRACE_MODE command is used. b. If <end pointer> is omitted, the end pointer specified by the PTR option of the TRACE_MODE command is used. 7-131 TRACE -- To display only mnemonics of the executed instructions, uses the following format: IP * [-]D'xxxxx (a) ADDR 003010 (b) LABEL !xx - xx (c) MNEMONIC xx - xx (d) OPERAND xx - xx (e) (a) Relative instruction location (instruction pointer), based on the instruction where a delay condition is satisfied as a break or trace condition. An instruction pointer begins with an asterisk (*) to differentiate it from a bus-cycle pointer. Although the pointer usually has a negative value (-D'xxxxx), if a delay count condition is specified as a break or trace condition, the delay will be indicated as a positive value (D'xxxxx). (b) Instruction address (c) Label name (d) Instruction mnemonic (e) Instruction operand -- To display trace information in bus-cycle units, uses the following format: BP AB DB [-]D'xxxxx xxxxxx xxxx MA R/W ST xxx x (a) (b) (c) (d) (e) IRQ NMI RES RA PROB VCC CLK TM xxx xxxxxx x x xx xxxxxxxx x xx xxxxxx=xxxx (f) (i) (j) (l) (m) (g) (h) (k) (n) -------------------------------------------------------------------------------------------------------------TOTAL CLOCK NUMBER = xxxxx (o) (a) Bus cycle pointer Number of bus cycles since an instruction where a delay condition is satisfied. In bus cycles which prefetch instructions, the instruction mnemonics and instruction addresses are displayed as described above. Although the pointer usually has a negative value (-D'xxxxx), when a delay count condition is specified, the delay will be indicated as a positive value (D'xxxxx). (b) Address bus value 7-132 TRACE (c) Data bus value If the MCU accesses data in word (2-byte) units, a 2-byte value is displayed. If it accesses data in byte units, a 1-byte value is displayed. (d) Memory area type Table 7-21 MA Display Display Description ROM Internal ROM area access RAM Internal RAM area access IO Internal I/O area access EXT External memory area access (Including UNUSABLE area access) FLA Flash memory access (e) Read/write type Table 7-22 R/W Display Display Description R Data read W Data write (f) MCU status Table 7-23 ST Display Display Description PRG Program fetch cycle REF Refresh cycle DAT Memory or I/O access cycle DMA DMA cycle (g) IRQn signal level IRQ x5 x4 x3 x2 x1 x0 xn: IRQn signal status xn 0: Low level 1: High level Note: The IRQ pins that do not exist in the MCU are displayed as 1s. 7-133 TRACE (h) NMI signal level (0 = low level, 1 = high level) (i) RES signal level (0 = low level, 1 = high level) (j) BREQ and BACK signal levels RA x1 x2 x1: BACK signal status x2: BREQ signal status xn 0: Low level 1: High level (k) External probe signal levels PROB x7 x6 x5 x4 x3 x 2 x1 x0 xn: PROB n signal status xn 0: Low level 1: High level (l) Vcc voltage Table 7-24 Vcc Voltage Display Display Description 0 Vcc voltage is correct 1 Vcc voltage is not correct (If this status is detected, the emulator is forcibly terminated.) (m) The number of clock cycles required from the end of the previous bus cycle to the end of this bus cycle. Up to 128 clocks are counted. If the number is more than 128, it is displayed as **. Refer to section 5.5.1, Trace Timing. (n) Address specified by the TRACE_MEMORY command and its memory contents (o) The total number of clock cycles (value displayed at (m) in the displayed trace range) displayed in hexadecimal. This value can be used to calculate the execution time in the displayed range. However, if ** (more than 128 clock cycles) appears at (m), ***** is displayed as the total value. 7-134 TRACE -- If (CTRL) + P keys are pressed during trace information display, the emulator backs up 32 lines, displays 16 lines of data from that point, then stops display scrolling. At this point, if the (RET) key is pressed, the emulator resumes display scrolling. If (CTRL) + P keys are pressed again, the emulator will again back up 32 lines and display 16 lines of data. If the display is in bus-cycle units, the total number of clock cycles is taken from the display range specified at TRACE command input. Notes 1. During trace information display in bus cycle units, the following message is displayed in the final bus cycle at user program termination as an emulator cycle: *** E7000 *** Note that this cycle is not related to the user program and can be ignored. This message is also displayed when program execution is temporarily terminated because the break satisfaction count specified by the BREAK command, or break conditions specified by the BREAK_SEQUENCE command, has been satisfied. 2. When trace range is specified with the TRACE_CONDITION command, the executed assemble display is not correct. Accordingly, use the trace information display only for reference. 7-135 TRACE Examples 1. To display all trace information with only instruction mnemonics: :T (RET) IP *-D'00007 *-D'00006 *-D'00005 *-D'00004 *-D'00003 *-D'00002 *-D'00001 * D'00000 : 2. ADDR 00000 00004 0008E 00092 00096 0009A 0009E 000A4 LABEL !main MNEMONIC BSR JSR PUSH.L PUSH.L PUSH.L PUSH.L MOV.L PUSH.L OPERAND 000004:8 @00008E:24 ER5 ER4 ER3 ER2 @(0010:16,ER7),ER2 ER2 To display trace information in bus-cycle units, from three instructions before the point where a break condition was satisfied: :T -3;B (RET) BP AB DB MA R/W ST IRQ NMI RES RA PROB VCC CLK * 000050 BLS 00004:8 -D'00005 000050 43F2 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00004 000052 0B56 EXT R PRG 111111 1 1 11 11111111 1 06 * 000044 SUB.B R3L,R3L -D'00003 000044 18BB EXT R PRG 111111 1 1 11 11111111 1 06 * 000046 MOV.B R3L,@ER5 -D'00002 000046 68DB EXT R PRG 111111 1 1 11 11111111 1 06 * 000048 MOV.W R6,R3 -D'00001 000048 0D63 EXT R PRG 111111 1 1 11 11111111 1 06 D'00000 2019AA 00 EXT W DAT 111111 1 1 11 11111111 1 06 * 00004A EXTS.L ER3 D'00001 00004A 17F3 EXT R PRG 111111 1 1 11 11111111 1 06 * 00004C ADD.L ER3,ER5 D'00002 00004C 0AB5 EXT R PRG 111111 1 1 11 11111111 1 06 * 00004E CMP.L ER4,ER5 D'00003 00004E 1FC5 EXT R PRG 111111 1 1 11 11111111 1 06 D'00004 000050 43F2 EXT R PRG 111111 1 1 11 11111111 1 06 D'00005 *** E7000 *** ----------------------------------------------------------------------TOTAL CLOCK NUMBER = 0003C : 7-136 TRACE 3. To specify a display range by bus cycle pointers, and display trace information in bus-cycle units: :T -D'20:-D'16;BP B (RET) BP AB DB MA R/W ST IRQ NMI RES RA PROB VCC CLK * 00004A EXTS.L ER3 -D'00020 00004A 17F3 EXT R PRG 111111 1 1 11 11111111 1 06 * 00004C ADD.L ER3,ER5 -D'00019 00004C 0AB5 EXT R PRG 111111 1 1 11 11111111 1 06 * 00004E CMP.L ER4,ER5 -D'00018 00004E 1FC5 EXT R PRG 111111 1 1 11 11111111 1 06 * 000050 BLS 000044:8 -D'00017 000050 43F2 EXT R PRG 111111 1 1 11 11111111 1 06 -D'00016 000052 0B56 EXT R PRG 111111 1 1 11 11111111 1 06 ----------------------------------------------------------------------TOTAL CLOCK NUMBER = 0001E : 7-137 TRACE_CONDITION 7.2.46 TRACE_CONDITION TC Specifies, displays, and cancels trace condition Command Format * * * : TRACE_CONDITION A=<start address>:<end address>; ST (RET) (Subroutine trace) : TRACE_CONDITION<condition>[[<condition>][<condition>]....];R (RET) (Range trace) : TRACE_CONDITION<condition>[[<condition>][<condition>]....];T (RET) (Trigger trace) : TRACE_CONDITION<condition>[[<condition>][<condition>]....];S (RET) (Stop trace) Display : TRACE_CONDITION (RET) Cancellation : TRACE_CONDITION - (RET) Setting <start address>: <end address>: <condition>: ST: R: T: S: Start address of subroutine trace End address of subroutine trace Range trace, trigger output, and trace stop conditions to be specified Subroutine trace mode condition Range trace mode condition Trigger mode condition Trace stop condition 7-138 TRACE_CONDITION Description * Setting -- Specifies trace acquisition condition (trace mode) for user program emulation (GO command execution). Free trace: Acquires trace information during all bus cycles if no conditions have been set with this command. Subroutine trace: Acquires trace information such as instructions and operands on the range (subroutine) specified by <start address> and <end address>. However, note that if the specified subroutine calls another subroutine, trace information on the called subroutine is not acquired. Range trace: Acquires trace information during bus cycles in which the specified condition is satisfied. Trigger trace: Acquires trace information during all bus cycles and a low-level pulse is output from the trigger pin of the emulator pod when the specified condition is satisfied. Trace stop: Stops trace information acquisition when the specified condition is satisfied, and enters command input wait state in parallel mode. Though realtime emulation continues, trace information acquisition is not possible in parallel mode. If a trace stop condition is satisfied, ** TRACE STOP ** is displayed. -- In subroutine trace, <start address> and <end address> must be specified following A=. In range trace mode, address or read/write condition can be specified as <condition>. In trigger or trace stop mode, the items shown in table 7-25 can be specified as <condition> and they can be combined by ANDing them. Several conditions can be specified in any order. 7-139 TRACE_CONDITION Table 7-25 Specifiable Conditions (TRACE_CONDITION) Item and Input Format Description Address condition * Range trace The condition is satisfied when the address bus value is in the range from <address 1> to <address 2>. A=<address 1>[:<address 2>][;NOT] If <address 2> is omitted, the condition is satisfied when <address 1> is recognized. If NOT is specified, the condition is satisfied when an address other than the specified one is accessed. Specifiable Trace Mode Range trace If an odd address is specified, access of an even address will satisfy the condition. * Trace stop or trigger trace A = <address> The condition is satisfied when the address bus value matches <address>. Data condition The condition is satisfied when the Trace stop or data bus value matches the specified trigger trace value. D, LD, and HD are valid when byte access is performed, while WD is valid when word access is performed. D=<1-byte value> WD=<2-byte value> LD=<1-byte value> (Data on data bus D7 to D0) HD=<1-byte value> (Data on data bus D15 to D8)* Read/write condition Trace stop or trigger trace The condition is satisfied in a read cycle (R is specified) or a write cycle (W is specified). Range trace, trace stop, or trigger trace The condition is satisfied when the bus-cycle type matches the specified type. Multiple bus-cycle types cannot be specified. Make sure to specify one or none bus-cycle types. Trace stop or trigger trace R: Read W: Write Access type PRG: Program fetch cycle DAT: Execution cycle DMA: DMA cycle Default: All bus cycles described above Note: Refer to the description on the following page. 7-140 TRACE_CONDITION Table 7-25 Specifiable Conditions (TRACE_CONDITION) (cont) Specifiable Trace Mode Item and Input Format Description External probe condition The condition is satisfied when all the emulator's external probe signals match the specified values. Specify <value> as one byte of data. Each bit corresponds to a probe number, as follows: PROB=<value> Trace stop or trigger trace <value>: Values for probes 1 to 8 0 Bit position x Specified value 1 Probe number 0=Low level 1=High level Example: To generate a break when probes 1 and 6 are high and the others are low, specify: PROB=H'21 System control signal condition BREQ, BACK The condition is satisfied when the BREQ or BACK signal is low. Trace stop or trigger trace Delay count specification This condition can be specified in combination with any of the above conditions. The complete condition combination is satisfied when the specified number of bus cycles has been executed after the other specified condition is satisfied. Trace stop or trigger trace DELAY=<value> <value>: H'1 to H'7FFF 7 x 8 6 x 7 5 x 6 4 x 5 3 x 4 7-141 2 x 3 1 x 2 x: TRACE_CONDITION -- Address and data conditions are satisfied when address bus values and data bus values match the specified values. Note the following when specifying trace conditions. a. Address condition for range trace mode Address A0 is ignored. Though even addresses are always specified, a condition can also be satisfied at odd addresses. Data condition cannot be specified. Example: H'1000 is specified as an address condition: The condition is satisfied when address H'1000 is accessed in word or byte units or when address H'1001 is accessed in byte units. b. Address and data conditions for trigger trace and trace stop modes * Word access to a 16-bit bus area (including internal ROM, flash memory, and internal RAM area) Word data is accessed in one bus cycle. Only WD (word data) can be specified as a data condition. If an address condition is specified in combination with a data condition (WD), only even address values can satisfy the address condition. Note, however, that if only the address condition is specified, both even and odd address values can satisfy the condition. Example: H'1001 is specified as an address condition (no data condition specified): The condition is satisfied even when H'1000 is accessed in word units. * Word access to an 8-bit bus area (internal I/O and external area) Accessing this area in word units is equal to accessing it in byte units twice. Both even and odd address values are valid for the address condition while only D (byte data) specifications are valid for the data condition. * Byte access All addresses can be accessed by a byte access. Both even and odd addresses can be specified as an address condition. Note, however, that only byte data (D) is valid for data condition. 7-142 TRACE_CONDITION Note: D, HD, or LD can be specified as byte data. Use these three data types depending on the trace conditions to be specified. D: If the specified address is even, data on data bus D15 to D8 is specified. If the specified address is odd, data on data bus D7 to D0 is specified. If no address is specified or if an address range or mask is specified, data on data bus D15 to D8 is automatically specified as shown below. Example 1: TC A=101 D=10;S A condition is satisfied when byte data 10 is written to or read from address 101. Example 2: TC A=100 : 1FF D=20;S A condition is satisfied when byte data 20 is written to or read from an even address within the range from H'100 to H'1FF. HD: Byte data (data bus D15-D8) access on an even address is always specified. Data access on an odd address is ignored. Example: TC A=1000 : 10FF HD=80;S A condition is satisfied if byte data 80 is written to or read from an even address within the range from H'1000 to H'10FF. LD: Byte data (data bus D7-D0) access on an odd address is always specified. Data access on an even address is ignored. Example: TC A=1000 : 10FF LD=80;S A condition is satisfied when byte data H'80 is written to or read from an odd address within the range from H'1000 to H'10FF. Note that D, HD, or LD cannot be specified in word access. -- A bit mask can be specified for data or external probe conditions in trigger trace or trace stop mode. If a bit is masked, its value is always ignored and does not affect the condition satisfaction. To implement the mask, specify each digit to be masked at input as *. Examples of masks are given below. Table 7-26 shows mask specifications. Example 1: A condition is satisfied when the D0 bit is 0 in a byte data condition. : TRACE_CONDITION D = B'*******0 (RET) Example 2: A condition is satisfied when probe 3 is 0 in a probe condition. : TRACE_CONDITION PROB=B'*****0** (RET) 7-143 TRACE_CONDITION Table 7-26 Mask Specifications (TRACE_CONDITION ) Radix Mask Unit Example Mask Position Allowed Condition Binary 1 bit B'01*1010* D0 and D5 bits are masked Data (WD, D, HD, LD), PROB Hexadecimal 4 bits H'F**50 D15 to D8 bits are masked Data (WD, D, HD, LD), PROB -- In parallel mode, this command is executed as follows: Parallel mode is entered by the (RET) key, or the trace stop condition is satisfied: * * * This command setting is invalid during parallel mode. No trace information is acquired. As soon as parallel mode is terminated, this command setting is validated and trace information acquisition starts. In this case, conditions that have been satisfied are all cleared, and the conditions are rechecked from the beginning. Old information is also cleared. At this time, *** 81:TRACE CONDITION RESET is displayed. Parallel mode is entered by the (SPACE) key: * * * This command setting is valid. Trace information is acquired. During the following command execution, this command setting is invalid and no trace information is acquired: A condition is newly set with the TRACE_CONDITION command TRACE command TRACE_SEARCH command As soon as the above command is terminated, this command setting is validated and trace information acquisition starts. In this case, old information is also cleared. At this time, *** 81:TRACE CONDITION RESET is displayed. 7-144 TRACE_CONDITION * Display Displays specified conditions. The specified input character string is displayed as is. If no condition is specified, blanks are displayed. : TRACE_CONDITION (RET) * Cancellation Cancels specified conditions. : TRACE_CONDITION - (RET) Examples 1. To acquire trace information only during the execution cycle of a subroutine in addresses H'4320 to H'4456 (subroutine trace): :TC : 2. To acquire trace information for bus cycles when data is written to addresses in the range from H'2002 to H'2003 (range trace): :TC : 3. A=4320:4456 ;ST (RET) A=2002 W ; R (RET) To stop trace and enter parallel mode if external probe 1 is pulled low (trace stop): :TC PROB=B'*******0 ; S (RET) :GO ** TRACE STOP ** # (command input wait state in parallel mode) 4. To output a trigger signal when byte data H'80 is written to address H'FF00 (trigger): :TC : A=FF00 D=80 W ; T (RET) 7-145 TRACE_MEMORY 7.2.47 TRACE_MEMORY TM Specifies, displays, and cancels memory address to be traced Command Format * * * Setting Display Cancellation : TRACE_MEMORY <address>[DMA][;<size>] (RET) : TRACE_MEMORY (RET) : TRACE_MEMORY []- (RET) <address>: Memory address to be traced into trace buffer DMA: Trace acquisition of DMA-cycle data. Default is an instruction execution cycle. <size>: Traced size B: Byte W: Word (equal to two bytes; valid when <address> has an even value) Default: Word Description * Setting -- Acquires the contents of the specified memory address in bus-cycle units and displays during user program execution. -- Use the TRACE or TRACE_SEARCH command to display or search for the trace information. Specify the TM option of the GO command to display during user program execution. * Display Displays the specified address, access type, and size as shown below. : TRACE_MEMORY (RET) ADDRESS = xxxxxx yyy ; z !ssssss xxxxxx: yyy: z: !ssssss: Specified address Access type DAT: Instruction execution cycle DMA: DMA cycle Traced size Symbol name (displayed only when an address is specified by a symbol) 7-146 TRACE_MEMORY * Cancellation Cancels the specified memory address. Notes 1. Trace acquisition and display are performed in real time. 2. Specifications can be changed in parallel mode; however, note the following: * Data is traced and displayed in an instruction execution cycle or in a DMA cycle. * Data updated within the emulator, such as the internal I/O timer counter, cannot be updated until after the data has been accessed by instruction execution or DMA. * When an address for trace acquisition is changed in parallel mode, the data collected up until then is for the previous address; the data will reflect the new address once this new address is accessed. * In parallel mode, the TRACE_MEMORY command setting cannot be cancelled. Examples 1. To trace the memory contents in address H'FF0E and display the results during user program execution: :TM FF0E (RET) :G ;TM (RET) ** PC = 001204 00FF0E = 8044 2. To display the specified address: :TM (RET) ADDRESS = 00FF0E DAT ;W : 3. !table/stack_top To cancel the specification: :TM - (RET) : 7-147 TRACE_MODE 7.2.48 TRACE_MODE TMO Specifies and displays trace information acquisition mode Command Format * Setting * Display : TRACE_MODE [REF=<option1>] [PTR=[-]<start pointer> [:[-]<end pointer>]][;C] (RET) : TRACE_MODE (RET) <option1>: Enables or disables trace information display for refresh cycles D: Disables trace information display E: Enables trace information display (default at emulator shipment) <start pointer>: Start pointer during trace information display and search (default at emulator shipment is -D'4095) <end pointer>: End pointer during trace information display and search (Default at emulator shipment is D'4095) C: Saves the specified mode in a configuration file Description * Settings -- Enables or disables trace information display for refresh cycles. * To disable trace information display for refresh cycles: : TRACE_MODE REF = D (RET) * To enable trace information display for refresh cycles: : TRACE_MODE REF = E (RET) -- Specifies the default values of start and end bus cycle pointers which are used when the bus cycle pointer values are not specified in the TRACE or TRACE_SEARCH command. Trace information in the emulator is available for a 32k bus cycles. Use this command to specify the range of the default values when all trace information is not required. The specified pointers will function as bus-cycle pointers in the TRACE_SEARCH command, and according to the option as instruction or bus-cycle pointers in the TRACE command. The cycle pointer value ranges from -32768 to 32767. When exceeding this range, start and end pointers are automatically specified as -32768 and 32767, respectively. : TRACE_MODE PTR = -D'2048:D'2048 (RET) 7-148 TRACE_MODE -- Writes the specifications in a configuration file on the system disk, when the C option is specified and the E7000 is used. Hereafter, when the E7000 is activated with the system disk, the saved specifications go into effect. When the E7000PC is used,writes in the configuration file in the directory where the current system program is stored on the IBM PC. The following message is output to confirm with the user whether to rewrite the configuration file: CONFIGURATION WRITE OK (Y/N) ? (a) (RET) (a) Y: Writes in the configuration file. N: Does not write in the configuration file. The existing specifications are valid. * Display Displays the specified trace mode as shown below. : TRACE_MODE (RET) REF = x PTR = -D'yyyyy : D'yyyyy x: E: D: Enables trace information display for refresh cycles Disables trace information display for refresh cycles yyyyy: Default values of start and end bus cycle pointers while trace information is displayed or searched Examples 1. To display trace information, specify the default values of the pointers within the range from -D'10 to D'10, and save the specified contents in a configuration file: :TMO REF = D PTR= -D'10:D'10;C (RET) CONFIGURATION WRITE OK (Y/N)? Y (RET) : 2. To display the specified contents: :TMO (RET) REF = D PTR = -D'00010:D'00010 : 7-149 TRACE_SEARCH 7.2.49 TRACE_SEARCH TS Searches for and displays trace information Command Format * Search and : TRACE_SEARCH[<condition>[<condition> ...]] display [;[-] <start bus cycle pointer>[:[-]<end bus cycle pointer>]] [L] (RET) <condition>: Condition governing trace information to be searched for or displayed. If this is omitted, the number of bus cycles and the number of instructions are displayed. -: Specified when searching for trace information acquired before the trace or break condition has been satisfied. However, this specification can be omitted if delay count condition is specified in TRACE_CONDITION or BREAK_CONDITION1 command. <start bus cycle pointer>: Start pointer of bus cycle to be searched for or displayed. <end bus cycle pointer>: End pointer of bus cycle to be searched for or displayed. If both <start bus cycle pointer> and <end bus cycle pointer> are omitted, bus cycles are searched for or displayed according to the specifications of the TRACE_MODE command. L: Displays the last bus cycle information to be searched for. Description * Search and display -- Searches for information in the trace buffer under the specified conditions, and displays all applicable bus cycle information. If <start bus cycle pointer> and <end bus cycle pointer> are specified, searches for and displays the bus cycle information between <start bus cycle pointer> and <end bus cycle pointer>. Trace information is displayed in the same format as the bus cycle information display by the TRACE command. -- If no conditions are specified, the number of bus cycles and the number of instructions saved in the trace buffer are displayed. : TRACE_SEARCH (RET) INSTRUCTION NUMBER=D'xxxxx BUS-CYCLE NUMBER = D'yyyyy xxxxx: Number of instructions (decimal) yyyyy: Number of bus cycles (decimal) -- Items listed in table 7-27 can be specified for <condition>, and they can be combined by ANDing them. 7-150 TRACE_SEARCH Table 7-27 Specifiable Conditions (TRACE_SEARCH) Item and Input Format Description Address condition Searches for the address bus value in the range from <address 1> to <address 2>. A=<address1>[:<address2>]* If <address 2> is omitted, only <address 1> is searched for. Data condition D=<1-byte value> WD=<2-byte value> LD=<1-byte value> (Data on data bus D7 to D0) HD=<1-byte value> (Data on data bus D15 to D8)* Searches for a bus cycle where the data bus value matches the specified value. D, LD, and HD are valid when byte access is performed, while WD is valid when word access is performed. Memory area condition ROM: Internal ROM area (Flash memory area) RAM: Internal RAM area IO: Internal I/O area EXT: External memory area (Unusable area) Searches for a bus cycle where the specified memory area is accessed. Read/write condition Searches for a read cycle (R is specified) or a write cycle (W is specified). R: Read W: Write Access type PRG: Program fetch cycle DAT: Execution cycle DMA: DMA cycle Default: All bus cycles described above Searches for the specified type of bus cycle. Multiple bus-cycle types cannot be specified. Make sure to specify one or none bus-cycle types. External probe condition Searches for a bus cycle in which all emulator external probe signals match the specified value. Specify <value> as one byte of data. Each bit of <value> corresponds to a probe number, as follows: 7 6 5 4 3 2 1 0 Bit position x x x x x x x x Specified value 8 7 6 5 4 3 2 1 Probe number x: 0=Low level 1=High level Example: To search for a bus cycle in which probes 1 and 6 are high and others are low, specify: PROB=H'21 PROB=<value>* <value>: Values for probes 1 to 8 Note: Refer to the description on the following page. 7-151 TRACE_SEARCH Table 7-27 Specifiable Conditions (TRACE_SEARCH) (cont) Item and Input Format Description External interrupt condition * Searches for a bus cycle in which NMI is at the specified level. -- NMI or NMI:L Searches for a bus cycle in which NMI is low. -- NMI:H Searches for a bus cycle in which NMI is high. * Searches for a bus cycle in which all IRQ signals are at the specified levels. Specify <value> as one byte of data as follows. Each bit corresponds to a signal (IRQ0 to IRQ5). NMI:[L] or NMI:H IRQ=<value>* 5 x 5 4 x 4 3 x 3 2 x 2 1 x 1 x: 0 Bit position x Specified value 0 IRQ number 0=Low level 1=High level Example: To search for a bus cycle in which IRQ1and IRQ5 are high and others are low, specify: IRQ=H'22 RES Searches for a bus cycle in which RES is low. Data condition for the address specified with TRACE_MEMORY command Searches for a bus cycle in which data in the address specified with the TRACE_MEMORY matches the specified value. If the CH option is specified, searches for a bus cycle in which data value changes. TM= {<dataCHvalue>} Note: Refer to the description on the following page. 7-152 TRACE_SEARCH -- If the L option is specified, displays only the last bus cycle information to be searched for. -- When an address or data condition is specified, the emulator searches for a bus cycle where address bus value and data bus values match the specified values, respectively. Note the following when specifying search conditions. * Word access to a 16-bit bus area (including internal ROM, flash memory, and RAM area) Word data is accessed in one bus cycle. Only WD (word data) can be specified as a data condition. In addition, only even address values can satisfy the address condition. * Word access to an 8-bit bus area (internal I/O and external area) Accessing this area in word units is equal to accessing it in byte units twice. Both even and odd address values are valid for the address condition while only D (byte data) specifications are valid for the data condition. * Byte access All addresses can be accessed by a byte access. Both even and odd addresses can be specified as an address condition. Note, however, that only byte data (D, HD, LD) is valid for data condition. Note: D, HD, or LD can be specified as byte data. Use these three data types depending on the search conditions to be specified. D: Byte data on an even or odd address is specified. Word access is ignored. Example 1: TS A=101 D=10 Searches for a bus cycle in which byte data 10 is written to or read from address 101. Example 2: TS A=100 : 1FF D=20 Searches for a bus cycle in which byte data 20 is written to or read from addresses 100 to 1FF. HD: Byte data (data bus D15-D8) access on an even address is always specified. Data access on an odd address is ignored. Example: TS A=1000 : 10FF HD=80 Searches for a bus cycle in which byte data 80 is written to or read from an even address within the range from 1000 to 10FF. 7-153 TRACE_SEARCH LD: Byte data (data bus D7-D0) access on an odd address is always specified. Data access on an even address is ignored. Example: TS A=1000 : 10FF LD=80 Searches for a bus cycle in which byte data 80 is written to or read from an odd address within the range from 1000 to 10FF. Note that D, HD, or LD cannot be specified in word access. -- A bit mask can be specified for data, IRQ, or external probe condition specification in single-bit or 4-bit units. When a bit is masked, its value is always ignored and does not affect the condition satisfaction. To implement the mask, specify each digit to be masked at input as an asterisk (*). Examples of masks are given below. Table 7-28 shows the mask specifications. Example 1: To search for a bus cycle where D0 bit is 0 in byte data condition. : TRACE_SEARCH D = B'*******0 (RET) Example 2: To search for a bus cycle where IRQ2 is 0 in IRQ condition (IRQ pins other than IRQ2 are ignored) : TRACE_SEARCH IRQ = B'*****0** (RET) Table 7-28 Mask Specifications (TRACE_SEARCH) Radix Mask Unit Example Mask Position Allowed Condition Binary 1 bit B'01*1010* D0 and D5 bits are masked Address, data (WD, D, HD, LD), IRQ, PROB Hexadecimal 4 bits H'**50 D15 to D8 bits are masked Address, data (WD, D, HD, LD), IRQ, PROB Note: A mask cannot be specified for an address range condition. -- The display contents are the same as the bus-cycle display of the TRACE command. Refer to section 7.2.43, TRACE, for details. However, instruction mnemonics and the total number of clock cycles are not displayed. 7-154 TRACE_SEARCH -- If no trace information satisfies the specified condition, *** 45: NOT FOUND is displayed. -- If trace information has not been saved in the trace buffer, *** 39: BUFFER EMPTY is displayed. -- The number of IRQ pins is 6 in the MCU. However, the IRQ condition can be specified by 8 bits. Because the emulator masks the settings of bits 6 and 7 that correspond to nonexistent IRQ pins such as IRQ6 and IRQ7, bits 6 and 7 can be either 0 or 1. For example, if IRQ = 7F is specified, bits 6 and 7 are masked and the conditions specified for bits other than bits 6 and 7 must be satisfied. Examples 1. To search for bus cycles when data is written to addresses in the range from H'FF00 to H'FF0F: :TS A=FF00:FF0F W BP AB (RET) DB MA R/W ST IRQ NMI RES RA PROB VCC CLK -D'00065 00FF01 43 EXT W DAT 111111 1 1 11 11111111 1 06 -D'00044 00FF0E 0B EXT W DAT 111111 1 1 11 11111111 1 06 -D'00032 00FF02 80 EXT W DAT 111111 1 1 11 11111111 1 06 -D'00020 00FF0B 00 EXT W DAT 111111 1 1 11 11111111 1 06 : 2. To search for the last bus cycle where IRQ0 is low: :TS IRQ = B'*******0 ;L (RET) BP AB DB -D'00020 003402 00 MA R/W ST EXT R IRQ NMI RES RA PRG 111110 1 : 7-155 1 PROB VCC CLK 11 11111111 1 06 Section 8 Floppy Disk Utility 8.1 Overview The E7000 has a built-in 3.5-inch floppy disk drive which allows the user to save and load user programs and save execution results that are also output to the screen. Floppy disk utility commands are listed in table 8-1. These commands cannot be used in the E7000PC. Table 8-1 Floppy Disk Utility Commands Command Function Usable/Unusable in Parallel Mode FILE_COPY Copies and verifies file contents Usable FILE_DIRECTORY Displays file directory information Usable FILE_DUMP Displays or modifies file contents Usable FILE_ERASE Deletes file Usable FILE_LOAD Loads file contents into memory Unusable FILE_RENAME Renames file Usable FILE_SAVE Saves memory contents to file Unusable FILE_TYPE Displays file contents Usable FILE_VERIFY Verifies file contents against memory Unusable FLOPPY_CHECK Displays floppy disk information Usable FLOPPY_FORMAT Formats a floppy disk Usable 8-1 8.2 Floppy Disk Format Format specifications of floppy disk for the E7000 are given in table 8-2. Prepare an appropriate 2HD floppy disk, and format it with the E7000's FLOPPY_FORMAT command before using it on the E7000. Table 8-2 Floppy Disk Format Item Specification Medium 3.5-inch, 2HD (double sided, high density, double track) Memory capacity 1.2 Mbytes (approx.) Recording format IBM format Number of tracks 80 x 2 = 160 Number of sectors/track 15 sectors/track Sector size 512 bytes/sector 8.3 Files 8.3.1 File Names The general file name format is as follows: <drive name>:<file name>.<extension> File name specifications for the E7000 are given in table 8-3. Table 8-3 File Name Specifications Item Number of Characters Usable Characters Default Enabled/Disabled Default Drive name 1 A, B Enabled A File name 1 to 8 Disabled * -- Extension 1 to 3 A to Z 0 to 9 $&#{}~%-@^` ! _' ( ) Enabled (Space) Note: Default is enabled for some commands. Drive Name: Since the E7000 has only one floppy disk drive, a drive name is usually not required with the file name. Drive A is the default drive. If drive B is specified for a copy procedure, copying to another floppy disk is assumed and a disk exchange message is displayed. When any commands other than the copy command are used, the drive need not be specified. File Name: Identifies the file. Extension: Identifies the file's attributes. Default is a space. 8-2 Wild card characters * and ? can be specified to select several files at a time with the FILE_DIRECTORY and FILE_ERASE commands. The meanings of these wild cards and examples of their use are given in table 8-4. Table 8-4 Wild Card Characters Wild Card Character ? * Examples Meaning Specification Specified Files Regarded as a single character. A?.COM A.COM AX.COM ?.C?M A.COM B.CXM A???.??? A123.COM ABCD.SYS ????????.??? All files A?.* A.COM AB.CX ABC*.S ABCD.S ABCDEF.S *.COM A.COM XYZ.COM *.* All files Regarded as a character string. An asterisk (*) can be added to a file name and an extension. No character can be specified after *. 8.3.2 File Configuration Cluster: A file consists of clusters. A cluster contains 512 bytes and is the same size as a sector. Record: Execution result files output with the PRINT command and text files that can be transferred from the host system are divided into records. The format of a record is shown below. One record can extend over several clusters. Data H'0D H'0A 1 record Figure 8-1 Record Format Note: Only files that consist of records in the above format (with H'0D and H'0A at the end) can be transferred from the host system. 8-3 8.4 Floppy Disk Utility Commands This section provides details of floppy disk utility commands in the format shown in figure 8-2. Sect. Command Name No. Abbreviation Command Name Function * Command Name Full command name * Abbreviation Abbreviated command name Command Format Function 1 : Command input format Function 2 : Command input format * * <parameter 1>: Parameter description 1 <parameter 2>: Parameter description 2 : * Function Command function * Command format Command input format for each function * Description Function and usage in detail Description Function 1 Description of function 1 Function 2 Description of function 2 * * * Notes Warnings and suggestions for using the command. If additional information is not required, this item is omitted. * Examples Command usage examples Notes Examples Figure 8-2 Format of Floppy Disk Utility Command Description Symbols used in the command format have the following meanings: [ ]: Parameters enclosed by [ ] can be omitted. (a/b): One of the parameters enclosed by ( ) and separated by /, that is, either a or b must be specified. < >: Contents shown in < > are to be specified or displayed. ...: The entry specified just before this symbol can be repeated. : Indicates a space. Used only for command format description. (RET): Pressing the (RET) key. Although underlining is used throughout this manual to indicate input, it is not used in the command format parts of these descriptions. 8-4 8.4.1 FILE_COPY Copies or verifies file contents FILE_COPY FCO Command Format * Copy :FILE_COPY<source file><target file> (RET) * Verification :FILE_COPY<source file><target file>;(V/R) (RET) <source file>: <target file>: V: R: Source file name Target file name Verifies files in byte units Verifies files in record units Description * Copy -- Copies source file contents to the specified target file. When B: is specified as the target drive, the source file contents can be copied to another floppy disk. In this case, the disk exchange request message shown below is displayed after the source file's contents have been read from the floppy disk and stored in an internal memory buffer. Enter Y or N after exchanging the floppy disks. SET TARGET FD OK (Y/N) ? (a) (RET) (a) Y: Copies contents of the source file from the internal buffer. N: Aborts copy. When copying to the same floppy disk, the drive name need not be specified. -- The short formats shown in table 8-5 can be used to specify the target file name. Table 8-5 Target File Name Short Formats Short Format Specified File Example <file name>.<extension> <file name>.<extension> FCO F1.COM F2.COM .<extension> <source file name>.<extension> FCO F1.COM .SA B: B:<source file name>.<source file extension> FCO F1.COM B: B:<file name> B:<file name>.<source file extension> FCO F1.COM B:F2 B:.<extension> B:<source file name>.<extension> FCO F1.COM B:.SA 8-5 FILE_COPY -- If the specified target file already exists, the response request message below is displayed. Enter Y or N. OVERWRITE (Y/N) ? (b) (RET) (b) Y: Erases the existing file and creates a new one. N: Aborts copy. * Verification -- Data is verified in byte units if option V is specified. The verification error display format is as follows: <CLUSTER> xxxx (a) (a) (b) (c) (d) <OFFSET> xxx (b) <SOURCE> xx 'x' (c) <TARGET> xx 'x' (d) Cluster number Offset from the beginning of the cluster Source file data in hexadecimal and ASCII characters Target file data in hexadecimal and ASCII characters If the file sizes differ, *** 16:NOT SAME SIZE is displayed. -- Data is verified in record units if option R is specified. The verification error display format is as follows: <RECORD> xxxx (a) (a) (b) (c) (d) <OFFSET> xxx (b) <SOURCE> xx 'x' (c) <TARGET> xx 'x' (d) Record number Offset from the beginning of the record Source file data in hexadecimal and ASCII characters Target file data in hexadecimal and ASCII characters 8-6 FILE_COPY If the record sizes differ, *** 16:NOT SAME SIZE is displayed. -- When drive B is specified, the source file contents can be verified against target file contents on another floppy disk in the same way as for copy function. The verification must be specified in byte units (specify option V). Verification in record units is not possible. -- The short format of a target file name can be specified for the verify function in the same way as for the copy function (table 8-5). Note When the target file is on another floppy disk, the source file contents are first saved in the memory buffer. Therefore, the source file cannot be larger than the memory buffer's capacity. Examples 1. To copy file PROG.S to PROG.X on the same floppy disk: :FCO PROG.S PROG.X (RET) : 2. To copy file ABC.XYZ to another floppy disk by erasing a file of the same name and creating a new one: :FCO ABC.XYZ B: (RET) SET TARGET FD OK (Y/N)? Y (RET) OVERWRITE (Y/N)? Y (RET) : 3. To verify files PROG.S and PROG.BAK in record units (two verification errors occurred): :FCO PROG.S PROG.BAK;R (RET) <RECORD> <OFFSET> <SOURCE> <TARGET> 000031 00B 56 'V' 4C 'L' 000031 00C 30 '0' 31 '1' : 8-7 FILE_DIRECTORY 8.4.2 FILE_DIRECTORY FDI Displays file directory information Command Format * Directory display :FILE_DIRECTORY[<file name>] (RET) <file name>: Specifies a file for directory information display. (Wild cards can be used.) If no file name is specified, all file directory information is displayed. Description * Directory display -- Displays directory information of the specified file. If <file name> is omitted, all file directory information is displayed. The display format is as follows: <NAME> <BYTES> <NAME> <BYTES> <NAME> <BYTES> xxxxxxxx.yyy zzzzz xxxxxxxx.yyy zzzzz xxxxxxxx.yyy zzzzz : : : : : : VOLUME LABEL : vvvvvvvvvv xxxxxxxx: yyy: zzzzz: vvvvvvvvvv: File name File name extension Number of bytes (in hexadecimal) Volume name -- The two wild card characters, ? and *, can be used in <file name>. For details on wild card characters, refer to section 8.3.1, File Names ?: Represents any single character or space. *: Represents a character string. 8-8 FILE_DIRECTORY Examples 1. To display all file directory information in a floppy disk: :FDI (RET) <NAME> <BYTES> <NAME> E7000 .TST F400 PROG .S TEST0001.S 120 VOLUME LABEL : WORKFD : 2. <BYTES> 4400 <NAME> PROG .BAK <BYTES> 4200 To display directory information of the files whose name starts with TST: :FDI TST* (RET) <NAME> <BYTES> <NAME> TST001 .TST 100 TST002 .X TST0001 .S 120 VOLUME LABEL : WORKFD : <BYTES> 200 8-9 <NAME> TSTAAA .Y <BYTES> 4400 FILE_DUMP 8.4.3 FILE_DUMP FDU Displays and modifies file contents Command Format * Display :FILE_DUMP[<file name>] (RET) * Modification :FILE_DUMP[<file name>]; I (RET) <file name>: Specifies a file name. If the file name is omitted, the entire disk in drive A is assumed (floppy disk dump). I: Subcommand input mode Description * Display -- Displays the contents of the specified file in cluster units (file dump). If the file name is omitted or drive A is specified, all data is displayed, beginning from the start sector of the floppy disk (floppy disk dump). File dump: DUMP OF <file name> CLUSTER NO = <cluster number> xxx . . . xxx (a) ............ . . . ............ xx . . . xx xx . . . xx (b) xx . . . xx (a) Offset from that cluster (b) Data in hexadecimal (c) Data in ASCII characters 8-10 xx . . . xx xx . . . xx xxxxxxxxxxxxxxxx . . . xxxxxxxxxxxxxxxx (c) FILE_DUMP Floppy disk dump: DUMP OF A: xxx . . . xxx (a) xx . . . xx SECTOR NO = <sector number> xx . . . xx (b) xx . . . xx ............ . . . ............ xx . . . xx xx . . . xx xxxxxxxxxxxxxxxx . . . xxxxxxxxxxxxxxxx (c) (a) Offset from that sector (b) Data in hexadecimal (c) Data in ASCII characters * Modification When option I is specified, a prompt (>) is displayed and the E7000 enters subcommand input mode. Modify the file contents by inputting the subcommands shown in table 8-6. File contents are modified after reading the cluster or sector to be modified into the internal buffer with the R subcommand. Table 8-6 FILE_DUMP Subcommands Subcommand Format Meaning D<start cluster> [<end cluster>] (RET) Displays specified cluster data (or sector data) R<cluster number> (RET) Loads the specified cluster data (or sector data) into the memory buffer W (RET) Writes memory buffer contents to the cluster (or sector) M <start offset><end offset> (RET) Displays specified memory buffer data M <offset> (RET) Modifies memory buffer data. The specified offset address and its contents are displayed. xxx xx ? (a) (RET) (a) xx : ^: .: (RET) only : Q (RET) Modification value Displays previous offset data Terminates modification mode Displays next offset data Note: Cluster (or sector) data is not changed until the W command is input. Terminates the command 8-11 FILE_DUMP Examples 1. To display the contents of file PROG.S: :FDU PROG.S (RET) DUMP OF PROG.S CLUSTER NO = 0000 000 20 55 53 45 52 20 20 20 20 20 20 20 20 20 20 20 USER 010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ : : : : : : : : : : 2. To modify the contents of bytes 100 and 101 in sector 2 of file TEST.S: :FDU TEST.S;I (RET) >R 2 (RET) >M 100 (RET) 100 FF ? 80 (RET) 101 00 ? 1 (RET) 102 02 ? . (RET) >W (RET) >Q (RET) : Loads sector 2 into memory buffer. Displays the contents of byte 100. Changes the data in byte 100 from H'FF to H'80. Changes the data in byte 101 from H'00 to H'1. Terminates modification. Writes memory buffer contents to the sector. Terminates FILE_DUMP command execution. 8-12 FILE_ERASE 8.4.4 FILE_ERASE FER Deletes file Command Format * Deletion :FILE_ERASE<file name> [;Y] (RET) <file name>: File to be erased. (Wild card characters can be used.) Y: Erases the file without a confirmation message Description * Deletion -- Deletes the specified file. If option Y is omitted, the confirmation message shown below is displayed. Enter Y or N. ERASE A:<file name> [ERASED A:<file name>] OK (Y/N) ? (a) (RET) (b) (a) Y: Deletes the file. N: Aborts command. (b) This message is displayed when the file has been deleted. If wild cards are used, all applicable files are processed as above. -- If option Y is specified, the file is deleted without the confirmation message. In that case, the following message is displayed: ERASED A:<file name> -- The two wild card characters, ? and *, can be used in <file name>. For details on wild cards, refer to section 8.3.1, File Names. ?: Represents any single character or space. *: Represents a character string. 8-13 FILE_ERASE Examples 1. To erase file PROG.S (with a confirmation message): :FER PROG.S (RET) ERASE A:PROG .S ERASED A:PROG .S : 2. OK (Y/N) ? Y(RET) To delete all files with extension LOG (without confirmation messages): :FER *.LOG;Y (RET) ERASED A:DB001 .LOG ERASED A:TST .LOG ERASED A:PROG .LOG : 8-14 8.4.5 FILE_LOAD Loads file contents into memory FILE_LOAD FL Command Format * Load :FILE_LOAD<file name>[<offset>][;<load module type>] (RET) <file name>: File to be loaded <offset>: Value to be added to the address (can only be specified for S-type or HEX-type load modules) <load module type>: Load module type to be loaded S: S-type load module H: HEX-type load module B: Binary-type load module Default: Binary-type load module Description * Load -- Loads load module file contents saved into a floppy disk by the FILE_SAVE command into user memory. :FILE_LOAD <file name>[;<load module type>] (RET) The current load address is displayed as follows. Note that the load address is not output to the file or to the printer assigned by the PRINT command. LOADING ADDRESS xxxxxx xxxxxx: Current load address When loading is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> -- If the load module is either S-type or HEX-type, an address offset (value to be added or subtracted) can be specified. :FILE_LOAD <file name> <offset>;S (RET) 8-15 FILE_LOAD If an offset is specified, a load address is calculated as follows: Load address = <load module address> + <offset> Notes 1. The program cannot be loaded into the internal I/O area. 2. Verification is not performed after a file is loaded. The program must be verified with the FILE_VERIFY command, if necessary. Example To load the program saved in file SAVE.B by the FILE_SAVE command: :FL SAVE.B (RET) LOADING ADDRESS 000000 TOP ADDRESS = 000000 END ADDRESS = 003FFF : 8-16 FILE_RENAME 8.4.6 FILE_RENAME FRE Renames file Command Format * Renaming :FILE_RENAME<old file name><new file name> (RET) <old file name>: Old file name <new file name>: New file name Description * Renaming -- Replaces the old file name with the new file name. Short format can be used to specify the new file name. Table 8-7 lists short formats for specifying file names. Table 8-7 Rename Short Formats Short Format Specified File Example <file name>.<extension> <file name>.<extension> FILE_RENAME F1.COM F2.CXT .<extension> <old file name>.<extension> FILE_RENAME F1.COM .SXT <file name> <file name>.<old file extension> FILE_RENAME F1.COM F2 Examples 1. To rename file PROG.SRC as TEST.S: :FRE PROG.SRC TEST.S (RET) : 2. To rename file PROG.SRC as PROG.SSS: :FRE PROG.SRC .SSS (RET) : 3. To rename file PROG.SRC as TEST.SRC: :FRE PROG.SRC TEST (RET) : 8-17 8.4.7 FILE_SAVE FILE_SAVE FS Saves memory contents to file Command Format * Save :FILE_SAVE<file name><start address>(<end address> /@<number of bytes>)[;<load module type>] (RET) <file name>: <start address>: <end address>: <number of bytes>: <load module type>: File to be saved Start address of the memory area to be saved End address of the memory area to be saved Number of bytes to be saved Load module type to be saved S: S-type load module H: HEX-type load module B: Binary-type load module Default: Binary-type load module Description * Save Transfers the contents of the specified memory area to the specified file, with the specified load module type. If the specified file already exists, the following response request message is displayed: OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites the file. N: Aborts the command without saving the file. The current save address is displayed as follows. Note that the save address is not output to the file or the printer assigned by the PRINT command. SAVING ADDRESS xxxxxx xxxxxx: Current save address When the save is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> To reload the data which has been saved, use the FILE_LOAD command. 8-18 FILE_SAVE Notes 1. Data in the internal I/O area cannot be saved. 2. Verification is not performed after a file has been saved. The program must be verified with the FILE_VERIFY command, if necessary. Examples 1. To save data from addresses H'0 to H'1FFF in the binary-type file SUB.B: :FS SUB.B 0 1FFF (RET) SAVING ADDRESS 000400 TOP ADDRESS = 000000 END ADDRESS = 001FFF : 2. To save H'100 bytes of data from address H'4000 in the S-type file TST.S: :FS TST.S 4000 40FF;S (RET) SAVING ADDRESS 004000 TOP ADDRESS = 004000 END ADDRESS = 0040FF : 8-19 8.4.8 FILE_TYPE FILE_TYPE FTY Displays file contents Command Format * File contents display :FILE_TYPE<file name> (RET) <file name>: Name of the file to be displayed Description * File contents display Displays the contents of the specified file. The file contents must be written in valid ASCII characters. Since the FILE_TYPE command does not check the validity of ASCII characters, the screen will display unreadable text if invalid characters are included in the file. In addition, the file contents cannot be displayed if the records in the file do not have the format specified in section 8.3.2, File Configuration. The contents of execution result files output with the PRINT command can also be displayed with this command. Example To display the execution result file RESULT on the console: :FTY RESULT (RET) :MAP 0 FFFF ;S REMAINS EMULATION MEMORY S=D'30000KB :F 0 FFFF :FL TEST TOP ADDRESS = 000000 END ADDRESS = 001FFF :B 1020 :P - : 8-20 8.4.9 FILE_VERIFY Verifies file contents against memory FILE_VERIFY FV Command Format * Verification :FILE_VERIFY<file name>[<offset>][;<load module type>] (RET) <file name>: Name of file to be verified <offset>: Value to be added to the address (can only be specified for S- or HEXtype load modules) <load module type>: Load module type to be verified S: S-type load module H: HEX-type load module B: Binary-type load module Default: Binary-type load module Description * Verification -- Verifies data in the specified file against that in user memory. The current verification address is displayed as follows: VERIFYING ADDRESS xxxxxx xxxxxx: Current verification address Note that the verification address is not output to the file or to the printer assigned by the PRINT command. When verification is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> 8-21 FILE_VERIFY If a verification error occurs, the following message is displayed: <ADDR> xxxxxx (a) <FILE> xx 'x' (b) <MEM> xx 'x' (c) (a) Address where a verification error occurred (b) File contents at the address where the error occurred (in hexadecimal and ASCII characters) (c) Memory contents at the address where the error occurred (in hexadecimal and ASCII characters) -- If the load module is either S-type or HEX-type, an address offset (value to be added) can be specified. :FILE_VERIFY <file name> <offset>;S (RET) If an offset is specified, a verification address is calculated as follows: Verification address = <load module address> + <offset> Note Data in the internal I/O area cannot be verified. Examples 1. To verify data in file PRG.B against memory contents: :FV PRG.B (RET) VERIFYING ADDRESS 000000 TOP ADDRESS = 000000 END ADDRESS = 001FFF : 2. To verify data against that in the S-type file TST.S (two verification errors occurred): :FV TST.S (RET) VERIFYING ADDRESS 000000 <ADDR> <FILE> <MEM> 002024 30'0' 31'1' 003020 00'.' 01'.' TOP ADDRESS = 002000 END ADDRESS = 003FFF : 8-22 8.4.10 FLOPPY_CHECK FCH FLOPPY_CHECK Displays floppy disk information Command Format * Display :FLOPPY_CHECK (RET) Description * Display Displays the following information on the inserted floppy disk: DRIVE A: xxx xxx xxx TOTAL FREE (a) (b) (c) (d) (e) BYTES/SECTOR SECTORS/TRACK TRACKS/DISK AREA xxxx SECTORS xxxxxx BYTES AREA xxxx SECTORS xxxxxx BYTES Number of bytes per sector (hexadecimal) Number of sectors per track (hexadecimal) Total number of tracks on disk (hexadecimal) Disk capacity in sectors and bytes (hexadecimal) Remaining capacity in sectors and bytes (hexadecimal) Example To display disk information: :FCH (RET) DRIVE A: 200 BYTES/SECTOR 00F SECTORS/TRACK 0A0 TRACKS/DISK TOTAL AREA 0960 SECTORS 12C000 BYTES FREE AREA 06B3 SECTORS 0D6600 BYTES : 8-23 (a) (b) (c) (d) (e) FLOPPY_FORMAT 8.4.11 FLOPPY_FORMAT FF Formats a floppy disk Command Format * Format :FLOPPY_FORMAT (RET) Description * Format Formats and initializes a floppy disk. Only use disks formatted with this command for the E7000. After the floppy disk is inserted and the command is entered, the message below is displayed . Enter appropriate answers as follows: :FLOPPY_FORMAT (RET) VOLUME LABEL <volume name> FORMAT OK (Y/N) ? (a) (RET) *** FORMAT START *** (b) KEY IN VOLUME LABEL (11 CHARACTERS) ?(c) (RET) (a) Specify whether or not the floppy disk is to be formatted. Y: Formats the floppy disk. N: Moves to (c) without formatting the floppy disk. When only initializing the floppy disk, enter N. (b) Format start message. (c) Enter a new volume name (11 characters, max). When N is entered at (a), the floppy disk is initialized only. If the floppy disk is not to be formatted nor initialized, enter the (BREAK) key or the (CTRL) + C keys. Note Do not remove the floppy disk during this command execution. If a floppy disk is removed, an error occurs and the command execution terminates. 8-24 FLOPPY_FORMAT Examples 1. To format and initialize a floppy disk. The volume name is E7000: :FF (RET) VOLUME LABEL FORMAT OK (Y/N) ?Y (RET) *** FORMAT START *** KEY IN VOLUME LABEL (11 CHARACTERS) ?E7000 (RET) : 2. To initialize a floppy disk: :FF (RET) VOLUME LABEL FORMAT OK (Y/N) ?N (RET) KEY IN VOLUME LABEL (11 CHARACTERS) ?WORK (RET) : 8-25 Section 9 Data Transfer from Host System Connected by RS-232C Interface 9.1 Overview When the E7000 is connected to a host system by the RS-232C interface, data can be transferred between the host system and the E7000 or between the host system and user system memory connected to the E7000. This enables the following transmission of files: * * * * Loads host system load module files to user system memory Saves user system memory data to host system files Transfers host system text files to E7000 floppy disk files Transfers E7000 text files to host system Commands listed in table 9-1 can be used to transfer data. These commands cannot be used in the E7000PC. Table 9-1 E7000 Commands for Host System Usable/Unusable in Parallel Mode Command Function HOST Specifies and/or displays host system communication parameters Unusable LOAD Loads program from host system -- Transparent mode and local mode Unusable SAVE Saves program in host system -- Transparent mode and local mode Unusable TERMINAL Transfers to terminal mode -- Transparent mode Unusable TRANSFER Transfers file to and from host system -- Transparent mode and local mode Unusable VERIFY Verifies memory contents against host system file -- Transparent mode and local mode Unusable INTFC_LOAD Loads program from host system -- Remote mode Unusable INTFC_SAVE Saves program in host system -- Remote mode Unusable INTFC_ TRANSFER Transfers file to and from host system -- Remote mode Unusable INTFC_ VERIFY Verifies memory contents against host system file -- Remote mode Unusable 9-1 9.2 Host System Interface Modes and Operating Procedures The E7000 interfaces with the host system in transparent mode, local mode, or remote mode, when RS-232C interface is used. 9.2.1 Transparent Mode This mode is valid for a host system which is connected to the console by an RS-232C interface cable and is removable. A single console is shared between the E7000 and the host system in transparent mode. The configuration and data transfer in this mode are shown in figure 9-1. To enable data transfer, host system commands must be entered in addition to emulator command. E7000 command Host system command Input Console E7000 command Host system command CRT RS-232C HOST E7000 Floppy disk User memory Host system User system : Command flow : Data flow Figure 9-1 Configuration and Data Transfer in Transparent Mode Procedure: (a) Start up the E7000 system program (b) Set up the host system's communication parameters Specify parameters such as baud rate and data length with the HOST command. (c) Activate host terminal mode Enter the TERMINAL command to make the console available to the host system. 9-2 (d) Set up host system Start up the host system and put it in command input mode. (e) Terminate host terminal mode Exit host terminal mode with the code specified by the TERMINAL command. (f) Input data transfer command Add the host system command to the E7000 data transfer command (LOAD, SAVE, VERIFY, and TRANSFER) Example: LOAD : TYPE X.MOT (RET) 9.2.2 Local Mode In local mode, both E7000's console and host system's console are used for data transfer. An EPROM programmer can be connected in local mode. Emulator commands and host system commands are both executed at data transfer. The data receiving command must be executed first. The configuration and data transfer in this mode is shown in figure 9-2. E7000 command Input Input Host command E7000 command Host command CRT RS-232C HOST E7000 Floppy disk User memory Host system User system : Command flow : Data flow Figure 9-2 Configuration and Data Transfer in Local Mode 9-3 Procedure: Host system E7000 Start up host system Start up E7000 system program Set up communication parameters Set up communication parameters <Data transfer from host system to E7000> Execute data receive command Execute data transmission command Specify parameters such as baud rate and data length with the HOST command. Execute the E7000 command (LOAD, VERIFY, or TRANSFER). The E7000 can receive data from the host system. Be sure to execute the receive command first. Execute the host system command to output data to the E7000 connection port. <Data transfer from E7000 to host system> Execute data receive command Execute the host system command to input data from the E7000 connection port. Execute data transmission command 9-4 Execute the E7000 command (SAVE or TRANSFER). 9.2.3 Remote Mode In remote mode, a system that has its own console, such as a personal computer, is connected to the E7000 as the host system. This mode requires H-series interface software that can be separately purchased. In this mode, a host system's console can be used as the E7000's console. The data transfer commands in this mode are different from those in transparent mode and local mode: use the INTFC_LOAD, INTFC_SAVE, INTFC_VERIFY, and INTFC_TRANSFER in remote mode. The configuration and data transfer in this mode are shown in figure 9-3. Command, execution result E7000 command execution result output E7000 command Interface software RS-232C CRT HOST Floppy disk E7000 Host system User memory User system : Command flow : Data flow Figure 9-3 Configuration and Data Transfer in Remote Mode 9-5 Procedure: Start up host system Start up interface software The following H-series interface software start-up message is displayed: H-SERIES INTERFACE (type no.) Ver n.m Copyright (C) Hitachi, Ltd. 1988 Licensed Material of Hitachi, Ltd. Start up the E7000 <Data transfer from host system to E7000> Execute E7000 data receive command The E7000 start-up message is displayed on the host system. E7000 commands can now be entered from the host system. The E7000 data receive command (INTFC_LOAD, INTFC_VERIFY, or INTFC_TRANSFER) can transfer data from the host system to the E7000. Example: INTFC_LOAD:<host system file name> <Data transfer from E7000 to host system> Execute E7000 data transmission command The E7000 data transmission command (INTFC_SAVE or INTFC_TRANSFER) can transfer data from the E7000 to the host system. Example: INTFC_SAVE 0 1FFF:<host system file name> 9-6 9.3 Data Transfer Control 9.3.1 Control Methods The E7000 provides an RS-232C interface for the host system. This interface supports the following two control methods that can be selected by the HOST command: * X-ON/X-OFF control: Stops and restarts data transfer by the X-OFF (H'13) and X-ON (H'11) codes, respectively, sent from the data-receiving system. * RTS/CTS control: Stops data transfer when the data-receiving system outputs a low-level RTS signal, and restarts data transfer when the data-receiving system outputs a high-level RTS signal. 9.3.2 Timeouts The E7000 monitors for timeouts as it receives data from the host system. After command execution, the E7000 waits an unlimited time for the first data byte. However, once it has received the first byte, it will timeout after waiting three seconds for the next data byte, and the command will terminate. 9-7 9.4 Host-System Related Commands This section provides details of host-system related commands in the format shown in figure 9-4. Sect. Command Name No. Abbreviation Command Name Function * Command Name Full command name * Abbreviation Abbreviated command name Command Format Function 1 : Command input format Function 2 : Command input format * * <parameter 1>: Parameter description 1 <parameter 2>: Parameter description 2 : * Function Command function * Command format Command input format for each function * Description Function and usage in detail Description Function 1 Description of function 1 Function 2 Description of function 2 * * * Notes Warnings and suggestions for using the command. If additional information is not required, this item is omitted. * Examples Command usage examples Notes Examples Figure 9-4 Format of Host-System Related Command Description Symbols used in the command format have the following meanings: [ ]: Parameters enclosed by [ ] can be omitted. (a/b): One of the parameters enclosed by ( ) and separated by /, that is, either a or b must be specified. < >: Contents shown in < > are to be specified or displayed. ...: The entry specified just before this symbol can be repeated. : Indicates a space. Used only for command format description. (RET): Pressing the (RET) key. Although underlining is used throughout this manual to indicate input, it is not used in the command format parts of these descriptions. 9-8 9.4.1 HOST Specifies and/or displays host system communication parameters HOST H Command Format * Specification :HOST<baud rate><character length><parity><stop bit> <control method>(RET) * Display and specification: HOST (RET) <baud rate>: Baud rate 1: 2400 bps 2: 4800 bps 3: 9600 bps 4: 19200 bps 5: 38400 bps <character length>: Number of bits for one character 7: 7 bits 8: 8 bits <parity>: Parity E: Even parity O: Odd parity N: No parity <stop bit>: Number of stop bits 1: 1 stop bit 2: 2 stop bits <control method>: Control method X: X-ON/X-OFF control R: RTS/CTS control For details, refer to section 9.3.1, Control Methods. 9-9 HOST Description * Specification Specifies the host system's communication parameters (baud rate, character length, parity, stop bit, and control method). After this command is executed, data is transferred between the E7000 and the host system according to the interface conditions specified by this command. * Display and specification Displays the current parameters and enables their respecification if necessary. Enter only (RET) to continue without changing the current parameter, a caret (^) to display the previous parameter again, and a period (.) to terminate the respecification. :HOST (RET) BAUD RATE = 9600 BPS STOP BIT = 2 CHARACTER LENGTH = 8 CONTROL = X-ON, X-OFF PARITY = NO PARITY (a) BAUD RATE (1:2400/2:4800/3:9600/4:19200/5:38400) ? [n] (RET) CHARACTER LENGTH (7/8) ? [n] (RET) PARITY (E:EVEN/O:ODD/N:NO PARITY) ? [x] (RET) STOP BIT (1/2) ? [n] (RET) CONTROL (X:X-ON, X-OFF/R:RTS, CTS) ? [x] (RET) (b) (c) (d) (e) (f) BAUD RATE = xxxxx BPS CHARACTER LENGTH = x STOP BIT = x CONTROL = xxxxx (g) (a) (b) (c) (d) (e) (f) (g) Current communication parameters Baud rate Character length Parity Stop bit Control method Displays the selected communication parameters. 9-10 PARITY = xxxxxxx HOST Note At system initiation, the host system communication parameters are set according to the switches on the E7000's control board. Refer to section 3.3, System Connection, in Part I, Emulator Guide, for details. Examples 1. To specify all parameters at once: :H 3 8 N 1 X (RET) : 2. To specify parameters in interactive input mode: :H (RET) BAUD RATE = 9600 BPS CHARACTER LENGTH = 8 STOP BIT = 1 CONTROL = X-ON,X-OFF PARITY = NO PARITY BAUD RATE(1:2400/2:4800/3:9600/4:19200/5:38400) ? 4 (RET) CHARACTER LENGTH(7/8) ? 8 (RET) PARITY(E:EVEN/O:ODD/N:NO PARITY) ? E (RET) STOP BIT(1/2) ? 2 (RET) CONTROL (X:X-ON,X-OFF/R:RTS,CTS) ? X (RET) BAUD RATE = 19200 BPS CHARACTER LENGTH = 8 STOP BIT = 2 CONTROL = X-ON,X-OFF : 9-11 PARITY = EVEN LOAD LOAD L 9.4.2 Loads program from host system -- Transparent mode and local mode Command Format * Load :LOAD[<offset>][;[<load module type>][N][WA] [:<command transferred to host system>] (RET) <offset>: Value to be added to the load module address (can only be specified for an S-type or HEX-type load module) <load module type>: Load module type R: SYSROF-type load module S: S-type load module H: HEX-type load module Default: SYSROF-type load module N: Specifies that <line number symbol> is not to be loaded. If omitted, <line number symbol> is loaded. WA: Waits for the LF code. Refer to Description below. <command transferred to host system>: Specifies a command to be transferred to the host system (only in transparent mode). Description * Load -- Loads a user program into user memory from the host system. Loading in different host system interface modes is described below. Transparent Mode: After the command below is transferred to the host system, the user program from the host system is loaded into memory. :LOAD;<load module type>:<command transferred to host system> (RET) <command transferred to host system>: This command is transferred to the host system. The characters following the colon (:) are sent directly to the host system. The command to output source file contents to the terminal is specified. 9-12 LOAD The E7000 transfers <command transferred to host system> and (RET) (CR code: H'0D) to the host system. At the same time, it displays the echo back from the host system on the console. When option WA is not specified, the load module starts to transfer in 50 ms after (RET) is transferred. When option WA is specified, the E7000 waits for the LF code (H'0A) sent from the host system. As soon as the LF code is received, the load module starts to transfer. At first, try to transfer the load module without option WA. If it cannot be transferred, then specify option WA. If transfer does not occur with option WA, set the host system to no echo and transfer the load module without option WA. Local Mode: The E7000 does not issue data output requests to the host system. Therefore, after the LOAD command is entered, set the host system to output data. :LOAD[;<load module type>] (RET) Remote Mode: Use the INTFC_LOAD command. -- The current load address is displayed in the format below. LOADING ADDRESS xxxxxx xxxxxx: Current load address When loading is completed, the start and end addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> -- If the load module is either S-type or HEX-type, an offset (value to be added) can be specified for the load module address. :LOAD <offset>;S[:<command transferred to host system>] (RET) If an offset is specified, a load address is calculated as follows: Load address = <load module address> + <offset> 9-13 LOAD -- Information for symbolic debugging is included in a SYSROF-type load module. When a load module in SYSROF-type format is loaded, unit names of symbols to be defined can be selected as follows: :LOAD;R[:<command transferred to host system>] (RET) ALL SYMBOL LOAD (Y/N)? x (RET) ..................................(a) LOAD UNIT NAME (name/.) <unit name> (RET) ................(b) . . . . . . . . . . . . . . . LOAD UNIT NAME (name/.) . (RET) ....................................(b) (a) Specifies whether all symbols are to be loaded or symbols are to be selected. Y: Loads all symbols. N: Enables the selection of symbols by unit name. If Y is entered, the confirmation request messages (b) are not displayed. If N is entered, the confirmation request messages are displayed. Enter the unit names of symbols to be defined. (b) Symbol unit name to be defined Loading starts when the period (.) is entered. Up to ten unit names can be defined. -- If the N option is specified, <line number symbol> information among debugging information for the SYSROF-type load module is not loaded. 9-14 LOAD Notes 1. The load module cannot be loaded to the internal I/O area. 2. Verification is not performed during load. The program must be verified with the VERIFY command if necessary. 3. The LOAD command reloads existing symbols to enhance throughput without checking for double definitions. When reloading the same load module, temporarily delete existing symbols before performing the LOAD command. Examples 1. To load a SYSROF-type load module (transparent mode). COPYLINE F11.ABS TT: is a host system command. The symbol information for unit un001 will be loaded: :L :COPYLINE F11.ABS TT: (RET) ALL SYMBOL LOAD (Y/N) ? N (RET) LOAD UNIT NAME (name/.) ? un001 (RET) LOAD UNIT NAME (name/.) ? . (RET) LOADING ADDRESS 007000 TOP ADDRESS = 007000 END ADDRESS = 007FFF : 2. To load an S-type load module (local mode): :L;S (RET) After the LOAD command is entered, the host system transfers data to the E7000. LOADING ADDRESS 000000 TOP ADDRESS = 000000 END ADDRESS = 003042 : 9-15 SAVE SAVE SV 9.4.3 Saves program in host system -- Transparent mode and local mode Command Format * Save :SAVE<start address>(<end address>/@<number of bytes>) [;[<load module type>][LF]][:<command transferred to host system>] (RET) <start address>: Start memory address <end address>: End memory address <number of bytes>: Number of bytes to be saved <load module type>: Load module type S: S-type load module H: HEX-type load module Default: S-type load module LF: Adds LF code (H'0A) to the end of each record. <command transferred to host system>: Specifies a command to be transferred to the host system (only in transparent mode). 9-16 SAVE Description * Save -- Saves the specified memory contents in the host system in the specified load module type. An S-type or HEX-type load module can be saved. An SYSROF-type load module cannot be saved. Data receive request to the host system in different host system interface modes is described below. Transparent Mode: After the specified command is transferred to the host system, the memory area contents of the specified load module type are saved in the host system. :SAVE <start address> <end address>[;<load module type>] :<command transferred to host system> (RET) <command transferred to host system>: This command is transferred to the host system. The characters following the colon (:) are sent directly to the host system. The command to save data sent from the terminal in a file is specified. Local Mode: The E7000 does not issue data input requests to the host system. Therefore, before the SAVE command is input, set the host system to be ready to receive data. :SAVE <start address> <end address>[;<load module type>] (RET) Remote Mode: Use the INTFC_SAVE command. -- The current save address is displayed in the format below. SAVING ADDRESS xxxxxx xxxxxx: Current save address When save is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS=<start address> END ADDRESS=<end address> -- When option LF is specified, the E7000 adds an LF code (H'0A) to the end of each record in addition to an CR code (H'0D) in the S- or HEX-type load module. 9-17 SAVE Notes 1. Data in the internal I/O area cannot be saved. 2. Verification is not performed. Verify the program with the VERIFY command if necessary. Examples 1. To save memory contents in the address range from H'7000 to H'7FFF in the host system in Stype load module format (in transparent mode). COPY TT: F11.S is a host system command: :SV 7000 7FFF :COPY TT: F11.S (RET) SAVING ADDRESS 007000 TOP ADDRESS=007000 END ADDRESS=007FFF : 2. To save memory contents in the address range from H'0000 to H'1E00 in the host system in HEX-type load module format (in local mode): :SV 0 1E00 ;H (RET) SAVING ADDRESS 000000 TOP ADDRESS=000000 END ADDRESS=001E00 : Before entering the SAVE command, set the host system to be ready to receive data from the E7000. 9-18 9.4.4 TERMINAL TL TERMINAL Transfers to terminal mode -- Transparent mode Command Format * Transfer :TERMINAL [<end code>] (RET) <end code>: End key code for TERMINAL mode (1-byte data). Default is H'1A ( (CTRL)+ Z). Description * Transfer Transfers characters entered from the keyboard to the host system, and outputs data received from the host system to the console. A console connected to the E7000 can be used as a host system's terminal, as shown in figure 9-5. Terminal mode ends when the specified end code is entered. Default is (CTRL) + Z (H'1A). This command is valid in transparent mode only. Buffering Host sytem Console Buffering E7000 Figure 9-5 TERMINAL Command Processing 9-19 TERMINAL When changing the termination key code, specify hexadecimal data corresponding to the code, as follows: (CTRL) + D: Specify H'4 (CTRL) + X: Specify H'18 Note Terminal mode is controlled by software, although the terminal and the E7000 are connected by hardware. If the baud rate of the console interface is different from that of the host interface, the E7000 will still operate but some data may be lost. When the baud rate is 19200 bps or higher, (CTRL)+ S (display stop) may not be effective. Example To transfer to terminal mode with H'18 ( (CTRL) + X) as terminal end key code: :TL 18 (RET) $DIR . . . . . . $(CTRL) + X : (Executes host system command) . . . . . . (Terminates terminal mode) 9-20 9.4.5 TRANSFER TR TRANSFER Transfers file to and from host system -- Transparent mode and local mode Command Format * Transfer :TRANSFER <file name>[;[(S/R)][WA][C]][:<command transferred to host system>] (RET) <file name>: Name of file on floppy disk in the E7000 S: Transfer from the E7000 to the host system R: Reception from the host system (default) WA: Waits for the LF code after a command is transferred to the host system. Refer to Description below. Valid only when the R option is specified in transparent mode. C: Inserts CR codes before LF codes in files transferred from the host system and removes CR codes from files transferred to the host system. <command transferred to host system>: Specifies a command to be transferred to the host system (only in transparent mode). Description * Transmission -- Only text files can be transferred from the E7000 to the host system. Transfer processing in different host system interface modes is described below. Transparent Mode: After the host system command below is transferred, file contents are sent to the host system. :TRANSFER <file name>;S :<command transferred to host system> (RET) <command transferred to host system>: This command is transferred to the host system. The characters following the colon (:) are sent directly to the host system. The command to output the file contents to a terminal is specified. 9-21 TRANSFER Local Mode: The E7000 does not issue data output request to the host system. Therefore, before this command is entered, set the host system to input data from the E7000. :TRANSFER <file name>;S (RET) Remote Mode: Use the INTFC_TRANSFER command. * Receive -- The transfer of a file from the host system to the E7000. Only text files can be transferred. Data transfer processing in different host system interface modes is described below. Transparent Mode: After the host system command below is entered, transferred data is written to the E7000 file. :TRANSFER <file name>;R :<command transferred to host system> (RET) <command transferred to host system>: This command is transferred to the host system. The characters following the colon (:) are sent directly to the host system. The command to output the file contents to a terminal is specified. The E7000 transfers <command transferred to host system> and (RET) (CR code: H'0D) to the host system. At the same time, it displays the echo back from the host system on the console. When option WA is not specified, the load module starts to transfer in 50 ms after (RET) is received. When option WA is specified, the E7000 waits for the LF code (H'0A) sent from the host system. As soon as the LF code is received, the load module starts to transfer. At first, try to transfer the load module without option WA. If it cannot be transferred, then specify option WA. If transfer does not occur with option WA, set the host system to no echo and transfer the module without option WA. Local Mode: The E7000 does not issue data output requests to the host system. Therefore, after the TRANSFER command is entered, set the host system to output data. :TRANSFER <file name>;R (RET) 9-22 TRANSFER Remote Mode: Use the INTFC_TRANSFER command. If the specified file already exists, the message below is displayed. Enter Y or N. OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites the existing file with the new file. N: Aborts the command. -- The E7000 can receive only text files (ASCII characters) that can be displayed. If the E7000 receives another type of data, an error is generated and the command is aborted. This command is terminated with EOF (H'1A). -- With a UNIX-based host system, each record is terminated with a single LF code and no CR code. To receive such records, specify option C. Examples 1. To output a file from the E7000 to the host system in transparent mode. COPY TT: SAMPLE.S is a host system command: :TR SAMPLE.S;S:COPY TT: SAMPLE.S (RET) : 2. To transfer a file to the host system (in local mode): :TR FILE.TXT;S (RET) : 3. Before entering the TRANSFER command, set the host system to be ready to receive data from the E7000. To receive a file from the host system in transparent mode. TYPE FILE.S is a host system command: :TR FILE.TXT;R:TYPE FILE.S (RET) : 9-23 TRANSFER 4. To receive a file from the host system (in local mode): :TR FILE.TXT;R (RET) : After entering the TRANSFER command, set the host system to output data to the E7000. 9-24 9.4.6 VERIFY V VERIFY Verifies memory contents against host system file -- Transparent mode and local mode Command Format * Verification :VERIFY [<offset>][;[<load module type>][WA]][:<command transferred to host system>] (RET) <offset>: Value to be added to the address (can only be specified for a S-type or HEX-type load module) <load module type>: Load module type R: SYSROF-type load module S: S-type load module H: HEX-type load module Default: SYSROF-type load module WA: Waits for the LF code after a command is transferred to the host system. Refer to Description below. <command transferred to host system>: Specifies a command to be transferred to the host system (only in transparent mode). Description * Verification -- Verifies data transferred from the host system against data in memory. Verification in different host system interface modes is described below. Transparent Mode: After the host system command below is transferred, the user program from the host system is verified against the memory contents. :VERIFY;<load module type>:<command transferred to host system> (RET) <command transferred to host system>: This command is transferred to the host system. The characters following the colon (:) are sent directly to the host system. The command to output the file contents to the terminal must be specified. 9-25 VERIFY The E7000 transfers <command transferred to host system> and (RET) (CR code: H'0D) to the host system. At the same time, it displays echo back from the host system on the console. When option WA is not specified, the emulator starts to receive a load module within 50 ms after (RET) is transferred. When option WA is specified, the E7000 waits for the LF code (H'0A) sent from the host system. As soon as the emulator receives the LF code, the emulator starts to receive the load module. At first, try to transfer the load module without option WA. If it cannot be transferred, then specify option WA. If transfer does not occur with option WA, set the host system to no echo and transfer the load module without option WA. Local Mode: The E7000 does not issue data output requests to the host system. Therefore, after the VERIFY command is entered, set the host system to output data. Remote Mode: Use the INTFC_VERIFY command. -- If a verification error occurs, the address and its contents are displayed as follows: <ADDR> xxxxxx <FILE> yy 'y' <MEM> zz 'z' xxxxxx: Verification error address yy 'y': Load module data (in hexadecimal and ASCII characters) zz 'z': Memory data (in hexadecimal and ASCII characters) -- If the load module is either S-type or HEX-type, an address offset (value to be added or subtracted) of the load module can be specified. :VERIFY <offset>; S [:<command transferred to host system>] (RET) If an offset is specified, a verification address is calculated as follows: Verification address = <load module address> + <offset> Notes 1. Symbolic data cannot be verified. 2. Data in the internal I/O area cannot be verified. 9-26 VERIFY Examples 1. To verify a SYSROF-type load module against the memory contents in transparent mode. COPYLINE F1.ABS TT: is a host system command: :V :COPYLINE F1.ABS TT: (RET) VERIFYING ADDRESS 000000 <ADDR> <FILE> <MEM> 001012 31'1' 00'.' 001022 32'2' 01'.' TOP ADDRESS=000000 END ADDRESS=003FFF : 2. To verify an S-type load module against the memory contents in local mode: :V ;S (RET) VERIFYING ADDRESS 000000 TOP ADDRESS=000000 END ADDRESS=003042 : After entering the VERIFY command, set the host system to output data to the E7000. 9-27 INTFC_LOAD 9.4.7 INTFC_LOAD IL Loads program from host system -- Remote mode Command Format * Load :INTFC_LOAD[<offset>][;[<load module type>][N]]:<file name> (RET) <offset>: Value to be added to the load module address (can only be specified for an S-type or HEX-type load module) <load module type>: Load module type R: S: H: Default: SYSROF-type load module S-type load module HEX-type load module SYSROF-type load module N: Specifies that <line number symbol> is not to be loaded. If omitted, <line number symbol> is loaded. <file name>: Specifies a file name in the host system. Description * Load -- Loads a user program into user memory from the host system connected in remote mode. Use the H series interface software for the host system to open the specified file and transfers its contents to the E7000. :INTFC_LOAD[;<load module type>]:<file name> (RET) When loading is completed, the start and end addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> 9-28 INTFC_LOAD -- If the load module is either S-type or HEX-type, an offset (value to be added) can be specified for the load module address. :INTFC_LOAD <offset>;S :<file name> (RET) If an offset is specified, a load address is calculated as follows: Load address = <load module address> + <offset> -- Information for symbolic debugging is included in a SYSROF-type load module. When a load module in SYSROF-type format is loaded, unit names of symbols to be defined can be selected as follows: :INTFC_LOAD;R :<file name> (RET) ALL SYMBOL LOAD (Y/N)? x (RET) ..................................(a) LOAD UNIT NAME (name/.)? <unit name> (RET) ...............(b) . . . . . . . . . . . . . . . LOAD UNIT NAME (name/.)? . (RET) ..................................(b) (a) Specifies whether all symbols are to be loaded or symbols are to be selected. Y: Loads all symbols. N: Enables the selection of symbols by unit name. If Y is entered, all symbols are loaded and the confirmation request messages (b) are not displayed. If N is entered, the confirmation request messages are displayed. Enter the unit names of symbols to be defined. (b) Specifies symbol unit name to be defined. Loading starts when the period (.) is entered. Up to ten unit names can be defined. -- If the N option is specified, <line number symbol> information among debugging information for the SYSROF-type load module is not loaded. 9-29 INTFC_LOAD Notes 1. The load module cannot be loaded to the internal I/O area. 2. Verification is not performed. The program must be verified with the INTFC_VERIFY command if necessary. 3. The LOAD command reloads existing symbols to enhance throughput without checking for double definitions. When reloading the same load module, delete existing symbols before performing the INTFC_LOAD. Examples 1. To load a SYSROF-type load module F11.ABS. Symbol information for unit un001 is loaded: :IL :F11.ABS (RET) ALL SYMBOL LOAD (Y/N) ? N (RET) LOAD UNIT NAME (name/.) ? un001 (RET) LOAD UNIT NAME (name/.) ? . (RET) TOP ADDRESS = 007000 END ADDRESS = 007FFF : 2. To load an S-type load module ST.MOT: :IL;S :ST.MOT(RET) TOP ADDRESS = 000000 END ADDRESS = 003042 : 9-30 9.4.8 INTFC_SAVE IS INTFC_SAVE Saves program in host system -- Remote mode Command Format * Save :INTFC_SAVE<start address>(<end address>/@<number of bytes>) [;[<load module type>][LF]]:<file name> (RET) <start address>: Start memory address <end address>: End memory address <number of bytes>: Number of bytes to be saved <load module type>: Load module type S: S-type load module H: HEX-type load module Default: S-type load module LF: Adds LF code (H'0A) to the end of each record. <file name>: File name in the host system Description * Save -- Saves the specified memory contents in the specified load module type file in the host system connected in remote mode. Use the H series interface software for the host system. An S-type or HEX-type load module can be saved. A SYSROF-type load module cannot be saved. :INTFC_SAVE <start address> <end address>[;<load module type>] :<file name> (RET) When save is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS=<start address> END ADDRESS=<end address> -- When option LF is specified, the E7000 adds an LF code (H'0A) to the end of each record in addition to a CR code (H'0D) in the S- or HEX-type load module. 9-31 INTFC_SAVE Notes 1. Data in the internal I/O area cannot be saved. 2. Verification is not performed. The program must be verified with the INTFC_VERIFY command if necessary. Example To save memory contents in the address range from H'7000 to H'7FFF in the host system file F11.MOT in S-type load module format: :IS 7000 7FFF :F11.MOT (RET) TOP ADDRESS=007000 END ADDRESS=007FFF : 9-32 9.4.9 INTFC_TRANSFER IT INTFC_TRANSFER Transfers file to and from host system -- Remote mode Command Format * Transfer :INTFC_TRANSFER <file name>[;(S/R)][C]:<host system file name> (RET) <file name>: Name of file on floppy disk in the E7000 S: Transfer from the E7000 to the host system R: Reception from the host system (default) C: Inserts CR codes before LF codes in files transferred from the host system (receive) and removes CR codes from files transferred to the host system (transmission) <host system file name>: File name in the host system Description * Transmission -- Transfers text files from the E7000 to the host system connected in remote mode. Use the H series interface software for the host system. :INTFC_TRANSFER <file name>;S :<host system file name> (RET) * Receive -- Transfers a file from the host system connected in remote mode to the E7000. Only text files can be transferred. :INTFC_TRANSFER <file name>;R :<host system file name> (RET) If the specified file already exists, the message below is displayed. Enter Y or N. OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites the existing file with the new file. N: Aborts the command. 9-33 INTFC_TRANSFER -- The E7000 can receive only text files (ASCII characters) that can be displayed. If the E7000 receives another type of data, an error is generated and the command is aborted. This command is terminated with EOF (H'1A). -- With a UNIX-based host system, each record is terminated with a single LF code and no CR code. To receive such records, specify option C. Examples 1. To transfer file SAMPLE.S from the E7000 to the host system file SAM.S in remote mode: :IT SAMPLE.S ;S :SAM.S (RET) : 2. To transfer the host system file FILE.TXT to the E7000 file F.T: :IT F.T ;R : FILE.TXT (RET) : 9-34 9.4.10 INTFC_VERIFY Verifies memory contents against host system file -- Remote mode INTFC_VERIFY IV Command Format * Verification :INTFC_VERIFY [<offset>][;<load module type>]:<file name> (RET) <offset>: Value to be added to the address (can only be specified for a S-type or HEX-type load module) <load module type>: Load module type R: S: H: Default: SYSROF-type load module S-type load module HEX-type load module SYSROF-type load module <file name>: File name in the host system Description * Verification -- Verifies data transferred from the host system connected in remote mode against data in memory. Use the H series interface software for the host system. :INTFC_VERIFY[;<load module type>]:<file name> (RET) -- If a verification error occurs, verification terminates immediately and the address and its contents are displayed as follows. Note that only one verification error can be detected and its contents are displayed. <ADDR> xxxxxx <FILE> yy 'y' <MEM> zz 'z' xxxxxx: Verification error address yy 'y': Load module data (in hexadecimal and ASCII characters) zz 'z': Memory data (in hexadecimal and ASCII characters) 9-35 INTFC_VERIFY -- If the load module is either S-type or HEX-type, an address offset (value to be added or subtracted) of the load module can be specified. :INTFC_VERIFY<offset>; <load module type> [:<file name>] (RET) If an offset is specified, a verification address is calculated as follows: Verification address = <load module address> + <offset> Notes 1. Symbolic information cannot be verified. 2. Data in the internal I/O area cannot be verified. Example To verify a SYSROF-type load module F1.ABS against the memory contents: :IV :F1.ABS (RET) <ADDR> <FILE> <MEM> 001012 31'1' 00'.' TOP ADDRESS=000000 END ADDRESS=003FFF : 9-36 Section 10 Data Transfer from Host System Connected by LAN Interface 10.1 Overview The optional LAN board supports the FTP client function. This function enables the following data transfer between the E7000 and the host system connected through the LAN interface. * * * Loads the load module file from the host system into the user system memory Saves the user system memory contents into a host system file Transfers files between the E7000 and the host system The E7000 supports the LAN commands listed in table 10-1 to transfer data between the E7000 and the host system. These commands are explained in section 10.3, LAN Commands. These commands cannot be used in the E7000PC. 10-1 Table 10-1 LAN Commands Command Function Usable/Unusable in Parallel Mode ASC Specifies the file type as ASCII Usable BIN Specifies the file type as binary Usable BYE Terminates the FTP interface (Re-connects the FTP interface with the FTP command) Usable CD Modifies the file directory name of the FTP server Usable CLOSE Disconnects the host system from the FTP interface (Re-connects the host system to the FTP interface with the OPEN command) Usable FTP Connects the host system and E7000 via the FTP interface Usable LAN Displays E7000 IP address Usable LAN_HOST Specifies, modifies, and displays the name and IP address of the host system to be connected via the FTP command Unusable LAN_LOAD Loads a load module file from the host system to memory via the FTP interface Unusable LAN_SAVE Saves the specified memory contents in the LAN host system connected via the FTP interface Unusable LAN_TRANSFER Transfers a file between the host system and E7000 Unusable LAN_VERIFY Verifies memory contents against the host system file Unusable LS Displays the host system directory connected via the FTP interface Usable OPEN Connects the host system to the FTP interface Usable PWD Displays the current directory name of the host system to be connected via the FTP interface Usable STA Displays the type of a file to be transferred Usable LOGOUT Disconnects from the Telnet* Usable Note: The optional LAN board supports the Telnet server function in addition to the FTP client function. When the E7000 is connected to the host system through Telnet, the E7000 can be disconnected from the Telnet with the LOGOUT command. For details on the Telnet interface, refer to section 3.4.1, Power-on Procedure for LAN Interface, in Part I, E7000 Guide. Note that the FTP can be connected via Telnet or RS-232C. 10-2 10.2 LAN Data Transfer 10.2.1 Setting the Data Transfer Environment The optional LAN board enables the data transfer between the E7000 and the host system via FTP interface. The transfer environment must be specified before starting data transfer as follows. Note that the optional LAN board supports the FTP client function only. Procedure: 1. Specify the host system environment, including the host system name and IP address, to the network database of the host system. If the operating system of the host system is UNIX, the host system environment is specified in the /etc/hosts file. For details, refer to the appropriate host system's User's Manual. 2. Specify the following E7000 environment: * E7000 IP address Specify the E7000 IP address with the E7000 monitor's L command. Since the E7000 IP address is written to the EEPROM, it need not be written each time the LAN interface is used. The E7000 IP address can be modified as required. * Host system IP address (host system connected via FTP interface) Specify the name and IP address of the host system to be connected to the E7000 via the FTP interface when initiating the E7000 system program. For details, refer to section 10.3.8, LAN_HOST. The specified host name and IP address are written to the system disk. Accordingly, the E7000 is automatically connected to the host system simply by initiating the system disk. The host system name and IP address can be modified as required. 10-3 10.2.2 Data Transfer Data transfer is performed by connecting the E7000 to the host system via the FTP interface after the environmental settings have been completed. In the FTP interface, the optional LAN board supports only the client function. Note that the E7000 and host system must be connected to the FTP interface in that order. Transfer data using the following procedure. Procedure: 1. Initiate the E7000 system program by using the system disk, on which the host system name and IP address have been defined by the LAN_HOST command. 2. Connect the E7000 to the designated host system with the FTP command using the format shown below. Enter the host system name defined by the LAN_HOST command. In addition, enter the user name and password. :FTP <host system name> (RET) Username <user name> (RET) Password <password> (RET) login command success FTP> 3. Transfer data using the LAN_LOAD, LAN_SAVE, LAN_VERIFY, or LAN_TRANSFER command after the FTP interface with the host system is established. For details, refer to the corresponding command descriptions. 10.2.3 Notes on FTP Interface Before turning off the E7000 main power, the FTP interface must be terminated using the BYE command. Otherwise, the host system interface processing may remain uncompleted. In this case, the FTP interface cannot be re-established correctly even if the E7000 is re-initiated. 10-4 10.3 LAN Commands This section provides details of LAN commands in the format shown in figure 10-1: Sect. Command Name No. Abbreviation Command Name Function * Command Name Full command name * Abbreviation Abbreviated command name Command Format Function 1 : Command input format Function 2 : Command input format * * <parameter 1>: Parameter description 1 <parameter 2>: Parameter description 2 : * Function Command function * Command Format Command input format for each function * Description Function and usage in detail Description Function 1 Description of function 1 Function 2 Description of function 2 * * * Notes Warnings and suggestions for using the command. If additional information is not required, this item is omitted. * Examples Command usage examples Notes Examples Figure 10-1 Format of LAN Command Description Symbols used in the command format have the following meanings: [ ]: Parameters enclosed by [ ] can be omitted. (a/b): One of the number of parameters enclosed by ( ) and separated by /, that is, either a or b must be specified. < >: Contents shown in < > are to be specified or displayed. ...: The entry specified just before this symbol can be repeated. : Indicates a space. Used only for command format description. (RET): Pressing the (RET) key Although underlining is used throughout this manual to indicate input, it is not used in the command format sections of these descriptions. 10-5 10.3.1 ASC ASC ASC Specifies the file type as ASCII Command Format * Setting : ASC (RET) Description * Setting Specifies a file type as ASCII in the FTP interface. This specification is required to transfer text files with the LAN_TRANSFER command. Before transferring the command chain file created by the host system, specify the ASCII type with this command. To load a SYSROF-type load module file, binary must be specified with the BIN command. Example To set the file type as ASCII in the FTP interface: FTP> ASC (RET) asc command success FTP> 10-6 10.3.2 BIN BIN BIN Specifies the file type as binary Command Format * Setting : BIN (RET) Description * Setting Specifies the file type as binary in the FTP interface. This specification is required to transfer files with the LAN_LOAD, LAN_VERIFY, LAN_SAVE, or LAN_TRANSFER command. To load or verify a SYSROF-type load module file, binary must be specified with this command. Otherwise, a transfer error will occur. At E7000 initiation, binary is the default setting. Example To set the file type as binary in the FTP interface: FTP> BIN (RET) bin command success FTP> 10-7 10.3.3 BYE BYE BYE Terminates the FTP interface Command Format * Termination : BYE (RET) Description * Termination Terminates the FTP interface and changes the prompt to a colon (:). To re-establish the FTP interface, re-enter the FTP command. Example To terminate the FTP interface: FTP> BYE (RET) bye command success : 10-8 10.3.4 CD CD CD Modifies the file directory of the FTP server Command Format * Modification : CD <directory name> (RET) <directory name>: Name of directory to be modified Description * Modification Changes the current directory of the FTP server to the specified directory. The modified directory must be formatted depending on which host system is connected via the FTP interface. Example To change the current directory of the FTP server to the specified directory: FTP> CD subdir (RET) cd command success FTP> 10-9 10.3.5 CLOSE CLOSE CLOSE Disconnects the host system from the FTP interface Command Format * Disconnection : CLOSE (RET) Description * Disconnection Disconnects the FTP interface from the host system to which it is currently connected. Before changing host systems, disconnect the FTP interface with this command and re-connect with the OPEN command. Example To disconnect the FTP interface and change the host system to be connected: FTP> CLOSE (RET) bye command success FTP> OPEN HOST1 (RET) username ABC (RET) password ****** (RET) login command success FTP> 10-10 10.3.6 FTP Connects host system and E7000 via the FTP interface FTP FTP Command Format * Connection : FTP <host name> (RET) <host name>: Name of the LAN host system to be connected with the FTP server Description * Connection -- Connects the host system and E7000 via the FTP interface to enable data transfer with the LAN_LOAD, LAN_SAVE, LAN_VERIFY, or LAN_TRANSFER command. The host name specified in this command must be defined with the LAN_HOST command. -- If <host name> matches the host name specified with the LAN_HOST command, enter the user name and password in the following format. After the FTP command execution, a prompt changes from a colon (:) to FTP>. In this case, emulation commands and floppy disk utility commands can be executed. : FTP <host name> (RET) Username (a) (RET) Password (b) (RET) login command success FTP> (c) (a) Enter user name (b) Enter password (c) An FTP> prompt is displayed after FTP connection Note A password must be specified before a host system can be connected via the FTP. For a host system that can login by using only the user name, use a login format that requires a password. 10-11 FTP Example To connect the E7000 to host system HOST1 via the FTP interface: :FTP HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP> 10-12 LAN 10.3.7 LAN LAN Displays E7000 IP address Command Format * Display : LAN (RET) Description * Display -- Displays the E7000's internet (IP) address stored in the EEPROM, which is incorporated in the emulator station, in the following format: : LAN (RET) E7000 INTERNET ADDRESS xxx.xxx.xxx.xxx (a) (a): E7000 IP address stored in the EEPROM -- Specify the IP address with the E7000 monitor command L. Example To display the E7000 IP address: :LAN (RET) E7000 INTERNET ADDRESS 128.1.1.10 : 10-13 LAN_HOST 10.3.8 LAN_HOST LH Specifies, modifies, and displays the name and IP address of the host to be connected by the FTP command Command Format * Specification and modification : LAN_HOST;S (RET) * Display : LAN_HOST (RET) Description * Specification and modification -- Specifies and modifies the name and internet (IP) address of the host system to be opened with the FTP command. A maximum of nine names and internet addresses can be specified. -- The specified host name and IP address can be modified in interactive mode as shown below. After displaying the specified host names and internet addresses, the E7000 waits for the selection number input. Note that new data is written to the E7000 system disk; insert the system disk before executing this command. : LAN_HOST; S (RET) NO <HOST NAME> <IP ADDRESS> 01 xxxxxx xx.xx.xx.xx 03 xxxxxx xx.xx.xx.xx 05 xxxxxx xx.xx.xx.xx 07 xxxxxx xx.xx.xx.xx 09 xxxxxx xx.xx.xx.xx PLEASE SELECT NO ? 1 (RET) 01 HOST NAME xxxxxx 01 IP ADDRESS xx.xx.xx.xx PLEASE SELECT NO ? . (RET) NO 02 04 06 08 <HOST NAME> <IP ADDRESS> xxxxxx xx.xx.xx.xx (a) xxxxxx xx.xx.xx.xx xxxxxx xx.xx.xx.xx xxxxxx xx.xx.xx.xx ? xxxxxx (RET) ? xx.xx.xx.xx (RET) 10-14 (b) (c) (d) (e) LAN_HOST (a) Displays host system name and IP address currently defined. If nothing is specified, displays a space. NO indicates selection number. (b) Enters the selection number (1-9) to be set or modified. (c) Displays the host system name for the specified selection number. To specify a new host system name, enter the host system name using six or less characters. To delete the old host system name, enter -(RET). (d) Displays the IP address for the specified selection number. Enter a new IP address in decimal format. Example: 128.1.1.16 (e) Indicates the selection number input wait state. To specify or modify another host system name or IP address, repeat steps (a) to (d). To terminate this command, enter a period (.) and hit the (RET) key. The following confirmation message is displayed: PLEASE SELECT NO ? . (RET) OVERWRITE (Y/N) ? x (RET) x: Enter Y to write new data in the system disk; enter N to terminate the command without storing the new data. If an equal (=) and the (RET) keys are entered in selection number input wait state, the current host system name and IP address settings are displayed. -- Specified host system names and IP addresses are stored in the LANCNF.SYS file of the E7000 system disk. After storing data in the LANCNF.SYS file, the E7000 system program is terminated, along with the Telnet interface. To use the E7000 via the Telnet interface, reinitiate the E7000 and connect the E7000 to the Telnet from the host system. -- Before executing the FTP command, specify the name and IP address of the host system to be connected with the FTP command. If the E7000 is initiated by the system disk where the name and IP address of the host system is defined, the name and IP address of the host system need not be specified. 10-15 LAN_HOST * Display Displays the LAN host system names and IP addresses specified in the LANCNF.SYS file of the E7000 system disk. :LAN_HOST (RET) Examples 1. To add a host system to be connected via the FTP interface: :LH; S (RET) NO <HOST NAME> <IP ADDRESS> 01 HOST1 128.1.1.1 02 03 04 05 06 07 08 09 NO <HOST NAME> <IP ADDRESS> HST2 128.1.1.4 PLEASE SELECT NO ? 3 (RET) ----- (New host system is defined as No.3) 03 HOST NAME ? HOSTX (RET) 03 ADDRESS ? 128.1.1.8 (RET) PLEASE SELECT NO ? . (RET) OVERWRITE (Y/N)? Y (RET) START E7000 S:START E7000 R:RELOAD & START E7000 B:BACKUP FD F:FORMAT FD L:SET LAN PARAMETER T:START DIAGNOSTIC TEST (S/R/B/F/L/T) ? S (RET) --------- (The E7000 is restarted with S) 10-16 LAN_HOST 2. To display all of the defined host system names and IP addresses: :LH NO 01 03 05 07 09 : (RET) <HOST NAME> <IP ADDRESS> HOST1 128.1.1.1 02 HOSTX 128.1.1.8 04 06 08 NO <HOST NAME> <IP ADDRESS> HST2 128.1.1.4 10-17 LAN_LOAD 10.3.9 LAN_LOAD LL Loads a load module file from the host system to memory via the FTP interface Command Format * Load : LAN_LOAD [<offset>][;[<load module type>][N]:<file name> (RET) <offset>: Value to be added to the load module address (can only be specified for an S-type or HEX-type load module) <load module type>: Load module type R: SYSROF-type load module S: S-type load module H: HEX-type load module Default: SYSROF-type load module N: Specifies that <line number symbol> is not to be loaded. If omitted, <line number symbol> information is loaded. <file name>: A LAN host system file name Description * Load -- Loads a load module file from the host system to memory via the FTP interface. Before executing this command, the E7000 must be connected to the host system with the FTP command. -- The current load address is displayed in the format below. LOADING ADDRESS xxxxxx xxxxxx: The current load address display is continuously updated 10-18 LAN_LOAD -- When loading is completed, the start and end addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> -- If the load module is either S-type or HEX-type, an offset (value to be added) can be specified for the load module address. : LAN_LOAD <offset>; S:<file name> (RET) If an offset is specified, the load address is calculated as follows: Load address = <load module address> + <offset> -- Information for symbolic debugging is included in a SYSROF-type load module. Unit name in a SYSROF-type load module can be selected and loaded in SYSROF units. If a SYSROF-type load module is specified, the following message is displayed to prompt the input of symbol units: : LAN_LOAD :<file name> (RET) ALL SYMBOL LOAD (Y/N) ? x (RET) -------------------------------------------- (a) LOAD UNIT NAME (name/.) ? <unit name> (RET) -------------------------------- (b) * * * * * * * * LOAD UNIT NAME (name/.) ? . (RET) --------------------------------------------- (b) (a) Specifies whether all symbols are to be loaded or are to be selected. Y: Loads all symbols. N: Enables the selection of symbols by unit names. If Y is entered, the confirmation request messages (b) are not displayed. If N is entered, the confirmation request messages are displayed. Enter unit names of symbols to be loaded. (b) Specifies a unit name. Loading starts when the period (.) is entered as a response to a confirmation request message. Up to 10 unit names can be specified. -- If option N is specified, <line number symbol> information among the symbol information for the module is not loaded. 10-19 LAN_LOAD Notes 1. A load module file cannot be loaded to the internal I/O area. 2. Verification is not performed at loading. The program must be verified with the LAN_VERIFY command, if necessary. 3. The LAN_LOAD command reloads existing symbols to enhance throughput, without checking for double definitions. When reloading the same load module, delete the symbols before performing the LAN_LOAD. 4. Before loading a SYSROF-type load module, the file contents must be converted into binary code with the BIN command. At E7000 initiation, binary code is selected as the default. However, if ASCII is selected with the ASC command, change the file contents to binary code with the BIN command before loading. Example To load a SYSROF-type load module, enter the following command line. F11.ABS indicates the host system file name. Before entering the LL command, connect the E7000 to the host system with the FTP command: :FTP HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP> LL :F11.ABS (RET) ALL SYMBOL LOAD (Y/N) ? N (RET) LOAD UNIT NAME (name/.) ? un0001 (RET) LOAD UNIT NAME (name/.) ? . (RET) LOADING ADDRESS 007000 TOP ADDRESS = 007000 END ADDRESS = 007FFF FTP> 10-20 10.3.10 LAN_SAVE Saves the specified memory contents in the LAN host system connected via the FTP interface LAN_SAVE LSV Command Format * Save : LAN_SAVE<start address>(<end address>/@<number of bytes>) [;[<load module type>][LF]]:<file name> (RET) <start address>: <end address>: <number of bytes>: <load module type>: Start memory address End memory address The number of bytes to be saved Load module type S: S-type load module H: HEX-type load module Default: S-type load module LF: LF (H'0A) is added to the end of each record. <file name>: A LAN host system file name Description * Save -- Saves the specified memory contents in the host system connected via the FTP interface. Either an S-type or HEX-type load module can be saved. A SYSROF-type load module cannot be saved. Before executing this command, connect the E7000 to the host system with the FTP command. -- The current save address is displayed as follows: SAVING ADDRESS xxxxxx xxxxxx: Current save address display is continuously updated -- When save is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> -- When the LF option is specified, the LF (H'0A) code as well as CR (H'0D) code is added to the end of each S- or HEX-type load-module record. 10-21 LAN_SAVE Notes 1. Data in the internal I/O area cannot be saved. 2. Verification is not performed after saving. Verify the program with the LAN_VERIFY command, if necessary. Example To save the memory contents in the addresses from H'7000 to H'7FFF in the host system as a S-type load module file (file name: F11.S), enter the following command line. Before entering the LSV command, connect the E7000 to the host system with the FTP command: :FTP HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP>LSV 7000 7FFF :F11.S (RET) SAVING ADDRESS 007000 TOP ADDRESS = 007000 END ADDRESS = 007FFF FTP> 10-22 10.3.11 LAN_TRANSFER LTR LAN_TRANSFER Transfers a file between the host system and E7000 Command Format * Transfer : LAN_TRANSFER <file name1>[;[(S/R)]]:<file name2> (RET) <file name1>: S: R: <file name 2>: Name of file on floppy disk in the E7000 Transfer from the E7000 to the host system Receive from the host system (Default at E7000 initiation) An FTP host system file name Description * Transfer Performs file transmission and reception between the E7000 and host system via the FTP interface. Before entering this command, the following steps must be completed. (1) The E7000 must be connected to the host system with the FTP command. (2) The file type must be specified as either binary or ASCII with the BIN or ASC command, respectively. -- Transmission Transfers files from the E7000 to the LAN host system via the FTP interface. : LAN_TRANSFER <file name1> ; S :<file name2> (RET) -- Reception Transfers files from the host system to the E7000 via the FTP interface. Before transferring a command file for the COMMAND_CHAIN command, specify the file type as ASCII with the ASC command. : LAN_TRANSFER <file name1> ; R :<file name2> (RET) 10-23 LAN_TRANSFER If the specified file already exists, the message below is displayed. Enter Y or N. OVERWRITE (Y/N) ? (a) (RET) (a) Y: Overwrites the existing file with the new file N: Aborts the command Examples 1. To transfer file SAMPLE.S from the E7000 to file TEST.S on the host system, enter the following command line. Before executing the LTR command, the E7000 must be connected to the host system with the FTP command: :FTP HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP>LTR SAMPLE.S ;S :TEST.S (RET) FTP> 2. To transfer ASCII file COM.CC from the host system to file E7.CC on the E7000, enter the following command line. Before executing the LTR command, the file type must be specified as ASCII with the ASC command: FTP>ASC (RET) asc command success FTP>LTR E7.CC ;R :COM.CC (RET) FTP> 10-24 10.3.12 LAN_VERIFY Verifies memory contents against the host system file LAN_VERIFY LV Command Format * Verification : LAN_VERIFY [<offset>][;<load module type>]:<file name> (RET) <offset>: Value to be added to the address (can be specified only for an S-type or HEX-type load module) <load module type>: Load module type R: SYSROF-type load module S: S-type load module H: HEX-type load module Default: SYSROF-type load module <file name>: A LAN host system file name Description * Verification -- Verifies file transferred from the host system connected via the FTP interface against data in memory in the following format. Before executing this command, connect the E7000 to the host system with the FTP command. FTP > LAN_VERIFY <load module type>:<file name> (RET) -- If a verification error occurs, the address and its contents are displayed as follows: <ADDR> xxxxxx <FILE> yy 'y' <MEM> zz 'z' xxxxxx: Verification error address yy 'y': Load module data (in hexadecimal and ASCII character) zz 'z': Memory data (in hexadecimal and ASCII character) 10-25 LAN_VERIFY -- If the load module is either S-type or HEX-type, an address offset (to be added or subtracted) of the load module can be specified for the load module address. For subtraction, put a - in front of the value. FTP > LAN_VERIFY <offset> ; S [:<file name>] (RET) If an offset is specified, the load address is calculated as follows: Load address = <load module address> + <offset> Notes 1. Symbolic information cannot be verified. 2. Data in the internal I/O area cannot be verified. 3. Before verifying a SYSROF-type load module, the file contents must be converted into binary code with the BIN command. At E7000 initiation, binary code is selected as default. However, if ASCII is selected with the ASC command, change file contents to binary code with the BIN command before verifying. Example To verify a SYSROF-type load module file F11.ABS with the memory: :FTP HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP>LV :F11.ABS (RET) VERIFYING ADDRESS ****** TOP ADDRESS = ****** END ADDRESS = ****** FTP> 10-26 10.3.13 LS Displays the host system directory connected via the FTP interface LS LS Command Format * Display : LS [ <directory name>] (RET) <directory name>: Name of host system directory (Default: Current directory of the host system) Description * Display Displays the specified directory in the host system connected via the FTP interface. If <directory name> is omitted, the current directory contents is displayed. Note that the directory name must be specified according to the connected host system format. Example To display the contents of current directory of the host system: FTP>LS (RET) abc.s xyz FTP> 10-27 10.3.14 OPEN OPEN OPEN Connects the host system to the FTP interface Command Format * Connection : OPEN <host system name> (RET) <host system name>: Name of host system to be connected via the FTP interface (The host system name must have been defined with the LAN_HOST command) Description * Connection Connects the E7000 to the specified host system via the FTP interface. This command can also be used to change the host system to be connected to the E7000. To change the host system correctly, first disconnect the current host system by using the CLOSE command and then connect the new host system by using this command. FTP>OPEN <host system name> (RET) Username (a) (RET) Password (b) (RET) login command success FTP> (a): Enter user name (b): Enter password Note A password must be specified before a host system can be connected via the FTP. When the host system requires only the user name to login, use a login format that requires a password. 10-28 OPEN Example To disconnect the E7000 from the current host system and connect it to the new host system HOST1: FTP>CLOSE (RET) bye command success FTP>OPEN HOST1 (RET) Username USER1 (RET) Password ******** (RET) login command success FTP> 10-29 10.3.15 PWD PWD PWD Displays the current directory name of the host system connected via the FTP interface Command Format * Display : PWD (RET) Description * Display Displays the current directory name of the host system connected via the FTP interface. Example To display the current directory name of the host system connected via the FTP interface: FTP>PWD (RET) /usr/e7000 FTP> 10-30 10.3.16 STA Displays the type of a file to be transferred STA STA Command Format * Display : STA (RET) Description * Display Displays, in the following format, the file type (binary or ASCII) to be transferred by the LAN_LOAD, LAN_VERIFY, LAN_SAVE, or LAN_TRANSFER command. FTP>STA (RET) type mode is BINARY (Binary) FTP>STA (RET) type mode is ASCII (ASCII) Example To display the type of file to be transferred: FTP>STA (RET) type mode is BINARY FTP> 10-31 10.3.17 LOGOUT LOGOUT LO Disconnects from the Telnet Command Format * Disconnection : LOGOUT (RET) Description * Disconnection Disconnects the E7000 from the Telnet. This command is valid only when the E7000 is connected to the host system via the Telnet interface. Example To disconnect the E7000 from the Telnet interface: :LO (RET) 10-32 Section 11 Data Transfer between E7000PC and IBM PC 11.1 Overview The following data transfers between the E7000PC and a host system (IBM PC) can be performed by the commands listed in table 11-1. * * * Loads a load module file in the host system to the memory on the user system. Saves data in the user system memory as a load module file in the host system. Performs a file transfer between E7000PC and IBM PC. Table 11-1 E7000PC-Related Data Transfer Commands Command Name E7000PC Command Use LOAD Loads program from host system (IBM PC) SAVE Saves program in host system (IBM PC) VERIFY Verifies memory contents against host system file (IBM PC) 11.2 E7000PC and IBM PC System Connection The flow of data transfer between the E7000PC and IBM PC is shown in figure 11-1. Command, execution result E7000PC command E7000PC command execution result output Interface software Parallel interface PC HOST E7000PC Host system User memory User system : Command flow : Data flow Figure 11-1 Flow of Data Transfer 11-1 Procedure: Start up host system Start up interface software The H-series interface software start-up message is displayed: H-SERIES INTERFACE (type no.) Ver n.m Copyright (C) Hitachi, Ltd. 19xx Licensed Material of Hitachi, Ltd. INTERFACE BOARD ADDRESS = yyyy:zzzz, TERMINATE CODE = tt Start up the E7000PC <Data transfer from IBM PC to E7000PC> Execute E7000PC data receive command The E7000PC start-up message is displayed on the host system. Emulator commands can now be entered from the host system. The E7000PC data receive command (LOAD or VERIFY) can transfer data from the host system to the E7000PC. Example: LOAD:<host system file name> <Data transfer from E7000PC to host system> Execute E7000PC data transmission command The E7000PC data transmission command (SAVE) can transfer data from the E7000PC to the host system. Example: SAVE 0 1FFF:<host system file name> 11-2 11.3 E7000PC-Related Data Transfer Commands This section provides details of host-system related commands using the format shown in figure 11-2. Sect. Command Name No. Abbreviation Command Name Function * Command Name Full command name * Abbreviation Abbreviated command name Command Format Function 1 : Command input format Function 2 : Command input format * * <parameter 1>: Parameter description 1 <parameter 2>: Parameter description 2 : * Function Command function * Command Format Command input format for each function * Description Function and usage in detail Description Function 1 Description of function 1 Function 2 Description of function 2 * * * Notes Warnings and suggestions for using the command. If additional information is not required, this item is omitted. * Examples Command usage examples Notes Examples Figure 11-2 Format of E7000PC-Related Data Transfer Command Description Symbols used in the command format have the following meanings: [ ]: Parameters enclosed by [ ] can be omitted. (a/b): One of the parameters enclosed by ( ) and separated by /, that is, either a or b must be specified. < >: Contents shown in < > are to be specified or displayed. ...: The entry specified just before this symbol can be repeated. : Indicates a space. Used only for command format description. (RET): Indicates pressing the (RET) key. Although underlining is used throughout this manual to indicate input, it is not used in the command format parts of these descriptions. 11-3 11.3.1 LOAD LOAD L Loads program from host system (IBM PC) Command Format * Load :LOAD[<offset>][;[<load module type>][N]]:<file name> (RET) <offset>: Value to be added to the address (can be specified only for an S-type or HEX-type load module) <load module type>: Load module type S: S-type load module H: HEX-type load module R: SYSROF-type load module Default: SYSROF-type load module N: Specifies that <line number symbol> is not to be loaded. If omitted, <line number symbol> is loaded. <file name>: Specifies a file name in the host system (IBM PC). Description * Load -- Loads a user program into user memory from the host system. Use the H-series interface software for the host system to open the specified file and transfer its contents to the E7000PC. :LOAD[;<load module type>]:<file name> (RET) When loading is completed, the start and end addresses are displayed as follows: TOP ADDRESS = <start address> END ADDRESS = <end address> 11-4 LOAD -- If the load module is either S-type or HEX-type, an offset (value to be added) can be specified for the load module address. :LOAD <offset>;S:<file name> (RET) If an offset is specified, a load address is calculated as follows: Load address = <load module address> + <offset> -- Information for symbolic debugging is included in a SYSROF-type load module. When a load module in SYSROF-type format is loaded, unit names of symbols to be defined can be selected as follows: :L;R:<file name> (RET) ALL SYMBOL LOAD (Y/N)? x (RET) ........................................(a) LOAD UNIT NAME (name/.)? <unit name> (RET) .....................(b) * * * * * * * * * * * * * * * LOAD UNIT NAME (name/.)? . (RET) ........................................(b) (a) Specifies whether all symbols are to be loaded or symbols are to be selected. Y: Loads all symbols. N: Enables the selection of symbols by unit name. If Y is entered, all symbols are loaded and the confirmation request messages (b) are not displayed. If N is entered, the confirmation request messages are displayed. (b) Symbol unit name to be defined Loading starts when the period (.) is entered. Up to ten unit names can be defined. -- If the N option is specified, <line number symbol> debugging information for the SYSROF-type load module is not loaded. 11-5 LOAD Notes 1. Data cannot be loaded to the internal I/O area. 2. Verification is not performed. The program must be verified with the VERIFY command if necessary. 3. The LOAD command reloads existing symbols to enhance throughput without checking for double definitions. When reloading the same load module, delete existing symbols before performing the LOAD. Examples 1. To load a SYSROF-type load module F11.ABS. Symbol information for unit un001 is loaded: :L :F11.ABS (RET) ALL SYMBOL LOAD (Y/N) ? N (RET) LOAD UNIT NAME (name/.) ? un001 (RET) LOAD UNIT NAME (name/.) ? . (RET) LOADING ADDRESS 007000 TOP ADDRESS = 007000 END ADDRESS = 007A3F : 2. To load an S-type load module ST.MOT: :L ;S :ST.MOT(RET) LOADING ADDRESS 000000 TOP ADDRESS = 000000 END ADDRESS = 003042 : 11-6 11.3.2 SAVE Saves program in host system (IBM PC) SAVE SV Command Format * Save :SAVE<start address>(<end address>/@<number of bytes>) [;[<load module type>][LF]]:<file name> (RET) <start address>: Start memory address <end address>: End memory address <number of bytes>: Number of bytes to be saved <load module type>: Load module type S: S-type load module H: HEX-type load module Default: S-type load module LF: Adds LF code (H'0A) to the end of each record. <file name>: File name in the host system (IBM PC) Description * Save -- Saves the specified memory contents in the specified load module type file in the host system. Use the H-series interface software for the host system. An S-type or HEX-type load module can be saved. A SYSROF-type load module cannot be saved. :SAVE <start address> <end address>[;<load module type>]:<file name> (RET) When save is completed, the start and end memory addresses are displayed as follows: TOP ADDRESS=<start address> END ADDRESS=<end address> -- When option LF is specified, the E7000PC adds an LF code (H'0A) to the end of each record in addition to a CR code (H'0D) in the S- or HEX-type load module. 11-7 SAVE Notes 1. Data in the internal I/O area cannot be saved. 2. Verification is not performed. Verify the program with the VERIFY command if necessary. Example To save memory contents in the address range from H'7000 to H'7FFF in the host system file F11.MOT in S-type load module format: :SV 7000 7FFF :F11.MOT (RET) SAVING ADDRESS 007000 TOP ADDRESS = 007000 END ADDRESS = 007A3F : 11-8 11.3.3 VERIFY Verifies memory contents against host system file (IBM PC) VERIFY V Command Format * Verification :VERIFY [<offset>][;<load module type>]:<file name> (RET) <offset>: Value to be added to the address (can be specified only for an S-type or HEX-type load module) <load module type>: Load module type S: S-type load module H: HEX-type load module R: SYSROF-type load module Default: SYSROF-type load module <file name>: File name in the host system Description * Verification -- Verifies data transferred from the host system against data in memory. Use the H-series interface software for the host system. :VERIFY[;<load module type>]:<file name> (RET) -- If a verification error occurs, verification terminates immediately and the address and its contents are displayed as follows: <ADDR> xxxxxx xxxxxx: yy 'y': zz 'z': <FILE> yy 'y' <MEM> zz 'z' Verification error address Load module data (in hexadecimal and ASCII characters) Memory data (in hexadecimal and ASCII characters) 11-9 VERIFY -- If the load module is either S-type or HEX-type, an address offset (value to be added or subtracted) of the load module can be specified. :VERIFY<offset>;S:<file name in the host system> (RET) If an offset is specified, a verification address is calculated as follows: Verification address = <load module address> + <offset> Notes 1. Symbolic data cannot be verified. 2. Data in the internal I/O area cannot be verified. Example To verify a SYSROF-type load module F1.ABS against the memory contents: :V :F1.ABS (RET) VERIFYING ADDRESS 000000 <ADDR> <FILE> <MEM> 001012 31'1' 00'.' TOP ADDRESS = 000000 END ADDRESS = 003FFF : 11-10 Section 12 Error Messages 12.1 E7000 Error Messages The emulator system program outputs error messages in the format below. Table 12-1 lists error messages, descriptions of the errors, and error solutions. *** nn: <error message> nn: Error No. Table 12-1 Emulator Error Messages Error No. Error Message Description and Solution 1 INTERNAL ERROR (nn) Error occurred in the emulator program or station. Error code nn gives specific details. Contact any Hitachi agency and inform them of the code and statement. 2 HOST I/O ERROR (nn) I/O error occurred between the emulator and host system. Error code nn gives specific details. Refer to table 12-2. 3 FD I/O ERROR (nn) Error occurred during floppy disk read/write. Error code nn gives specific details. Refer to table 12-3. 5 INVALID EMULATOR POD The connected emulator pod is not supported by this emulator program or an error occurred in the connection between the emulator pod and emulator. Check the emulator program and emulator pod type numbers, and check the connection between the emulator station and the emulator pod. 6 USER SYSTEM NOT READY User clock or crystal oscillator clock is not input and therefore cannot be selected. The emulator internal clock is used instead. Check if the clock signal is output correctly. 7 PRINTER NOT READY The printer is not connected or is not turned on. Check the printer power and connection. 8 PAPER EMPTY The printer is out of paper. Reload paper. 9 FD NOT READY The floppy disk cannot be read from or written to. Check that a disk is inserted. 10 FD WRITE PROTECT The floppy disk is write-protected. Remove write protection or use another floppy disk . 11 FD CRC ERROR CRC error occurred during disk read/write. Reformat or change disks. 12 FD UNFORMATTED The floppy disk is not formatted. Format it by using the emulator or exchange it with a formatted disk. 12-1 Table 12-1 Emulator Error Messages (cont) Error No. Error Message Description and Solution 13 FILE NOT FOUND The specified file was not found. Check name. 14 INVALID FILE NAME Invalid file name format. Check format specifications. 15 INVALID FILE The specified file has invalid contents and cannot be read from or written to. Check the contents of the specified file. 16 NOT SAME SIZE Files to be verified are not of the same size. Check the contents of the specified file. 17 NOT SAME FORMAT The specified file cannot be read because its format is different. Specify a correct file. 18 FILE TOO LARGE MAX xxxxx BYTES File to be copied is too large. The maximum size allowed is shown as xxxxx. If the symbols are defined, delete the symbols and re-execute the command, or back up the file with the emulator monitor command. 20 SYNTAX ERROR Command syntax is incorrect. Correct the syntax. 21 INVALID COMMAND The specified command was not found, or this command cannot be specified in parallel mode. Correctly enter the command. 22 INVALID DATA The specified data is invalid. Correctly enter the data. 23 INVALID ADDRESS The specified address or address range is invalid. Correctly enter the address. 24 DATA OVERFLOW The specified data is more than 4 bytes. Correctly specify the data. 25 SYMBOL NOT FOUND The specified symbol was not found. Check whether the specified symbol is defined and specify a correct symbol. 26 INVALID SYMBOL Only a unit name symbol is specified. Specify it with a function and variable names. 27 INVALID CONDITION Invalid conditions are specified. Correctly enter the conditions. 28 DOUBLE DEFINITION Item to be registered has already been defined. Delete existing item and re-register. 29 CC COMMAND IN COMMAND FILE The command file contains a COMMAND_CHAIN command which cannot be used. Delete COMMAND_CHAIN from the file. 12-2 Table 12-1 Emulator Error Messages (cont) Error No. Error Message Description and Solution 30 SYMBOL IN USE The specified symbol cannot be deleted because it has already been used in a BREAK, BREAK_SEQUENCE, BREAK_ CONDITION, LED, TRACE_MEMORY, or TRACE_CONDITION command. Clear the symbol in that command, and delete it again. 31 INSUFFICIENT MEMORY Insufficient memory size for memory allocation with a MAP command. Memory was assigned within the available memory size. 32 INVALID ASM MNEMONIC An instruction mnemonic in an assembly statement is invalid. Correct it. 33 INVALID ASM OPERAND An operand in an assembly statement is invalid. Correct it. 34 ALREADY ASSIGNED The specified printer or file has already been assigned. Cancel the assignment and re-enter the command. 35 CAN NOT USE THIS MODE * GO command GO command cannot be executed because the execution mode settings are invalid. Correctly specify the mode. * MOVE_TO _RAM An attempt was made to execute the MOVE_TO_RAM command in single-chip mode. This command cannot be executed in single-chip mode. 36 TOO MANY SYMBOLS No more symbols can be registered. To load the same program, this error message is displayed because the emulator does not check the symbol double definition. Delete and re-register. 37 TOO MANY POINTS Too many points are specified. Remove any unnecessary settings and re-enter. 39 BUFFER EMPTY * TRACE or TRACE_SEARCH command Trace buffer is empty. Check trace conditions and execution state, and re-execute. Then display trace information. 41 NO OPTION BOARD OR LED_BOX DISCONNECT There is no optional memory board or LED_BOX connected. Connect them and execute the command again. 12-3 Table 12-1 E7000 Error Messages (cont) Error No. Error Message Description and Solution 42 GUARDED I/O WRITE Writing to a special internal I/O register that can only be accessed by the emulator was attempted with the MEMORY command. Check the address. Writing to the register does not affect user program operation. 44 VERIFY ERROR Writing to ROM was attempted or there was a memory error during verification. Check memory. 45 NOT FOUND The specified data or information was not found. Correctly specify data. 47 NOT FTP CONNECTION The command cannot be executed because the FTP is not connected. Connect the FTP with the FTP command. 48 FTP CONNECTION ALREADY The FTP has already been connected. Disconnect the FTP and re-enter the command. 49 INVALID SP ADDRESS The user program cannot be executed because the stack pointer points to the internal I/O area. Set the stack pointer value outside the internal I/O area and reexecute the program. 50 DMA EXECUTING The command is not executed because the DMA is operating. After the DMA completes operation, reexecute the command. 51 DMA GUARDED OR WRITE PROTECT A guarded area or write-protected area was accessed during the DMA cycle. Check the user program including the DMA cycle. 52 INTERNAL I/O AREA An attempt was made to access the internal I/O area. This area cannot be accessed with this command. Check the specified address. 53 LABEL TABLE OVERFLOW The assembler label table overflowed. Reduce the declaration and reference points. 54 INVALID CONFIGURATION FILE The configuration file in the system disk contains invalid data. Initiate the emulator with a correct configuration file. 55 CONFIGURATION FILE NOT Configuration file is not found on the emulator system FOUND disk. Initiate the emulator with a system disk containing the configuration file. 56 CONFIGURATION CHECK ERROR 59 TOO MANY CHARACTERS A warm start cannot be performed because the configuration file to be loaded differs from that has been loaded to the emulator. The warm start must be performed for a file which has been loaded to the emulator. Check the file. Too many characters were specified. Check the number of characters. 12-4 Table 12-1 Emulator Error Messages (cont) Error No. Error Message Description and Solution 61 CAN NOT GET INTO PARALLEL MODE The option which prevents the emulator from entering parallel mode is specified with the GO command. Change the execution mode. 62 LAN BOARD DISCONNECT This command cannot be executed because the LAN board is not installed. Install the optional LAN board and re-enter the command. 63 OUT OF BREAK SET AREA An attempt was made to set a PC breakpoint at an address out of the area specified by the BS option of the EXECUTION_MODE command. Change the area setting by the BS option of the EXECUTION_MODE command. 66 OUT OF COVERAGE PAGE An attempt was made to display coverage information on an address out of the area specified by the BS option of the EXECUTION_MODE command. Change the area setting by the BS option of the EXECUTION_ MODE command. 67 LAN I/O ERROR An attempt was made to access the internal I/O area. This area cannot be accessed with this command. Check the address. 68 INVALID HOST NAME The specified host name is not defined with the LAN_HOST command. Define the host name with the LAN_HOST command. 70 MAPPING BOUND MUST 128KB The size of the memory block specified for memory attribute setting with the MAP or MOVE_TO_RAM command is not a multiple of 128 kbytes. Instead, the memory attributes have been changed in 128-kbyte blocks. For details, refer to the MAP command. 71 MAPPING BOUND MUST 64KB The size of the memory block specified for memory attribute setting with the MAP or MOVE_TO_RAM command is not a multiple of 64 kbytes (in single chip mode). Instead, the memory attributes have been changed in 64-kbyte blocks. For details, refer to the MAP command. 72 MAPPING BOUND MUST 1MB The size of the memory block specified for memory attribute setting with the MAP or MOVE_TO_RAM command is not a multiple of 1Mbytes. Instead, the memory attributes have been changed in 1-Mbyte blocks. For details, refer to the MAP command. 12-5 Table 12-1 Emulator Error Messages (cont) Error No. 77 Error Message ALL BREAK POINTS DELETED Description and Solution All PC breakpoints were cancelled because the BREAK or BREAK_SEQUENCE command settings are modified by the BS option of the EXECUTION_ MODE command. 78 EMULATOR POD BUSY The emulator pod was processing a break processing in parallel mode, so another command could not be executed. Re-enter the command. This error occurs when breakpoints are set with the BREAK (with number of times) or BREAK_SEQUENCE command. 79 RUN_TIME OVERFLOW Execution time measured with the PERFORMANCE_ANALYSIS command overflows. 80 BREAK POINTS OF THIS AREA DELETED Breakpoints set with BREAK or BREAK_SEQUENCE command in the specified area (memory write area) were cancelled because the specified area is changed by the BS option of the EXECUTION_MODE command. 81 TRACE CONDITION RESET Satisfied conditions are all reset when parallel mode is entered. When parallel mode is terminated, the conditions are rechecked from the beginning. 82 ODD ADDRESS An odd address was written to by the assembler. However, processing is initiated from the odd address. 83 INVALID OPERAND SIZE The specified operand size is invalid. Processing is performed with the correct size. 84 INVALID ABSOLUTE ADDRESS An invalid address was specified by the assembler. Processing is performed with the maximum address allowed. 85 COVERAGE INITIALIZED All coverage information was cleared because the BS option specification of the EXECUTION_MODE command was changed. 86 INTERNAL I/O AREA The internal I/O area is included in the processing range. Commands other than MEMORY cannot be performed on the internal I/O area. 87 PERFORMANCE_ANALYSIS The measurement time minimum unit cannot be TABLE BUSY changed during execution time measurement. 88 INTERNAL ROM AREA The contents of memory area other than internal ROM (flash memory) was transferred by the MOVE_TO_RAM command. 12-6 Table 12-2 Host I/O Error Codes Error Code Description and Solution D1 Parity error: The parity bit specified with the HOST command must match the host system specifications. D2 Overrun error: E7000 control method is not recognized by the host system. Refer to the description of control methods in section 9.3.1, Control Methods. D3 Framing error: The baud rate and stop bit specified with the HOST command must match the host system specifications. D4 Load module format error: The load module format of the transferred data is incorrect. Check the data contents. DC Timeout error: Check the connection between the E7000 and host system. Also check the operational status of the host system. B0 The specified file is not found at system program loading or the setting of the environment variable for the IBM PC interface is incorrect. Check that the system program is installed correctly. 12-7 Table 12-3 Floppy Disk I/O Error Codes Error Code Description and Solution 01 A non-existent command was issued to the floppy disk controller (FDC). Reload and re-initiate the E7000 system program. 02 A non-existent disk drive is specified. Reload and re-initiate the E7000 system program. 03 An invalid sector number was accessed. Reload and re-initiate the E7000 system program. 05 The next command was issued during FDC command execution. Reset the E7000 by switching it off and on. 07 File attribute is READ ONLY: Data cannot be written to this file. Remove the write protection or change floppy disks. 0A Floppy disk directory area is full. Use a new disk. 11 No floppy disk: Insert a floppy disk. 12 Floppy disk is write-protected. Remove the write protection. 21 Data transfer between a floppy disk and memory failed. Retry. 32 The sector to be accessed was not found. Retry. 33 Deleted Data Mark was detected. Reformat the floppy disk. 41 Seek error: Retry. 51 The floppy disk remains in the busy state. Reset the E7000 by switching it off and on. 52 A FAULT signal was sent from the FDC. Reset the E7000 by switching it off and on. 53 End of sector was detected. Reset the E7000 by switching it off and on. 54 FDC error: Reset the E7000 by switching it off and on. 55 FDC operation was requested again during FDC operation. Reset the E7000 by switching it off and on. 56 DMAC error: Reset the E7000 by switching it off and on. C1 Record is too long and cannot be accessed. Check data contents. C2 End of File was detected. The specified cluster number is incorrect. Correctly specify the cluster number. C3 End of Volume was detected. The specified sector number is incorrect. Correctly specify the sector number. CD The floppy disk is full. Replace with a new floppy disk. 12-8 Table 12-4 Floppy Disk Error Messages Message Description and Solution *** FD NOT READY No floppy disk: Insert a floppy disk and retry. *** FD NOT SYSTEM FD The inserted floppy disk is not an E7000 system disk. Insert an E7000 system disk and retry. *** FD WRITE PROTECT Data cannot be written because the floppy disk is write-protected. Remove the write protection. *** FD FORMAT TYPE ERROR The inserted floppy disk is not compatible with the E7000 or is not formatted. Insert an E7000 disk or reformat the disk. *** FD CRC ERROR A CRC error occurred during read/write to the floppy disk. Reformat or replace the disk. *** FD I/O ERROR nn An error occurred during read/write to the floppy disk. Error code nn gives details of the error. See table 12-3. The E7000 system program outputs LAN I/O error messages in the format below. Table 12-5 lists the error messages with brief descriptions. LAN I/O ERROR (E0xx) socket library error n : <error message> xx: Process in which error occurred (see table 12-6) n: Error code (see table 12-5) <error message>: See table 12-5 If an error message other than that listed in table 12-5 is displayed, refer to the description for the host system error messages. Table 12-5 LAN I/O Error Messages Error No. Error Message Description 01 not listen The socket cannot be created 02 Insufficient Buffer The internal buffer is insufficient 03 Socket not Support The requested function is not supported 04 Socket is Already The socket has already been connected 05 time out error A timeout error has occurred 06 Ip Address Nothing The IP address destination is undefined 07 Not socket Connection The socket has not been connected 08 connection failure A connection failure has occurred 09 Illegal IP Address An illegal IP address has been specified 12-9 Table 12-5 LAN I/O Error Messages (cont) Error No. Error Message Description 10 be Shutdowning The connection is being terminated 11 Not Socket Entry The socket information has not been defined 12 Socket is already The socket has already been defined 13 HOSTS Name Nothing The host name does not exist 14 Socket not Assign Connected The socket cannot be assigned 15 illegal port No. The port number is invalid 16 initialized error An error has occurred during LAN board initialization 17 Not Terminate The LAN board has not been terminated 18 terminate error A LAN board termination error has occurred 19 Not Initialized The LAN board has not been initialized 20 Illegal Board An error has occurred in the LAN board 21 System Error A LAN board system error has occurred 22 Illegal Request An invalid request has been issued 23 Parameter Error The parameter data is invalid 24 Response Timeout Happend A response timeout error has occurred 25 Check Sum Error A checksum error has occurred 26 ICMP Error An ICMP error has occurred 27 ethernet address error An Ethernet address error has occurred 28 not HOST File The HOSTS information does not exist 30 illegal initialized The HOSTS initialization information is invalid 31 illegal My Data Main station information is invalid 32 illegal Other Party data Remote station information is invalid 33 remote Nothing Remote station has not been defined 34 transmission error A data transfer error has occurred 35 closing error A termination error has occurred FF unknow error An undefined error has occurred 12-10 Table 12-6 Process Code for LAN I/O Error Messages Error No. Process 01 Initialization 02 Telnet data transfer 03 Telnet close 04 Telnet open 10 FTP connection 20 File transmission 30 File reception 40 FTP disconnection 50 Directory modification 60 Directory display 70 Current directory display 80 File transfer binary specification 90 File transfer ASCII specification A0 Termination 12-11 12.2 IBM PC Interface Software Error Messages The IBM PC interface software outputs error messages on the IBM PC. Table 12-7 lists error messages, descriptions of the errors, and error solutions. Table 12-7 Interface Software Error Messages Error Message Description and Solution INTFC ERROR - FILE ALREADY EXISTS OVERWRITE? (Y/N): The specified IBM PC file already exists. Enter Y to transfer any way after deleting the file; enter N to cancel transfer. INTFC ERROR - SYNTAX ERROR An error exists in the IBM PC file name. Refer to the debugger and IBM PC manuals and specify a correct file name. INTFC ERROR - FILE NOT FOUND The specified IBM PC file cannot be found or an error is detected in the file name during load. INTFC ERROR - FILE OPEN ERROR The directory to which the specified IBM PC file is to be saved is full or an erroneous file name is specified. INTFC ERROR - FILE READ ERROR An error has occurred while reading an IBM PC file. INTFC ERROR - FILE WRITE ERROR An error has occurred while writing an IBM PC file. Available memory on the disk is insufficient. INTFC ERROR - FILE CLOSE ERROR An error has occurred while closing an IBM PC file. INTFC ERROR - TIMEOUT ERROR A timeout error has occurred during file transfer or data transfer from the debugger. Check the cable connection and re-transfer. INTFC ERROR - I/O ERROR An I/O error has occurred during file transfer. Check the cable connection and the operating environment, and re-transfer. INTFC ERROR - ABORT BY BREAK The file transfer has been forcibly terminated by pressing the (BREAK), (STOP), or (CTRL) + C keys. INTFC ERROR - INVALID COMMAND An invalid command has been received from the debugger. INTFC ERROR - EMULATOR NOT READY The debugger power has been turned off or a cable connected to the debugger has been disconnected. Check that debugger power is turned on and that cables are connected correctly, and restart. If the same error occurs again, inform a Hitachi sales agency. INTFC ERROR - FILE RENAME ERROR An error has occurred while changing an IBM PC file name. INTFC ERROR - FILE DELETE ERROR An error has occurred while deleting an IBM PC file. 12-12 Table 12-7 Interface Software Error Messages (cont) Error Message Description and Solution INTFC ERROR - STOP COMMAND CHAIN? (Y/N): Automatic command input from the IBM PC file has been completed. Enter Y to terminate command input; enter N to continue command input. INTFC ERROR - ALREADY ASSIGNED The specified command is already being executed. Re-execute the command after command execution has been completed. INTFC ERROR - ENVIRONMENT NOT SPECIFIED The specified environment variable name could not be detected. Specify the environment variable name with the SET command. INTFC ERROR - NO INTERFACE BOARD The interface board is not installed in the IBM PC expansion slot. Check the DIP switch setting on the interface board and that the interface board is inserted in the expansion slot correctly, and retransfer. If the same error occurs again, inform a Hitachi sales agency. 12-13 Appendix A Emulator External Dimensions and Weight Figures A-1 and A-2 show the emulator external dimensions and weight. Weight: Emulator station: 4 kg Emulator pod: 0.7 kg 135 198 Unit: mm 117 HITACHI E7000 167 500 283 53 HITACHI Station-pod interface cables Emulator pod 156 Emulator station Figure A-1 E7000 External Dimensions and Weight Weight: Emulator station: 4 kg Emulator pod: 0.7 kg 135 198 Unit: mm 117 HITACHI E7000 PC 167 500 283 53 HITACHI Station-pod interface cables Emulator pod 156 Emulator station Figure A-2 E7000PC External Dimensions and Weight A-1 Appendix B Memory Map The H8/3048 series and H8/3048F operate in advanced modes. The operating mode can be selected from seven modes (mode 1 to 7) by combining single chip/expanded, internal ROM (flash memory) enabled/disabled, and expanded data bus width. After reset, the settings of the mode pins (MD2 to MD0) determine the operating mode. After program execution starts, the expanded data bus width is determined depending on the attribute of the area in the address space specified by the bus controller. In each operating mode, the address space and pin functions change. B-1 Mode 1 Expanded 8-bit bus, 1-Mbyte mode Area 4 Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 H'DFFFF H'E0000 Area 7 H'0000FF H'007FFF Area 2 Area 0 H'1FFFFF H'200000 Area 1 H'3FFFFF H'400000 H'3FFFFF H'400000 Area 4 External bus area H'5FFFFF 8-bit bus, H'600000 3-state access Area 5 Area 2 External bus area H'5FFFFF 16-bit bus, H'600000 3-state access Area 3 Area 3 Area 7 H'7FFFFF H'800000 16-bit absolute address area (second half) Area 4 Area 4 H'9FFFFF H'A00000 H'9FFFFF H'A00000 Area 5 Area 5 H'BFFFFF H'C00000 H'BFFFFF H'C00000 Area 6 Area 6 H'DFFFFF H'E00000 H'DFFFFF H'E00000 Area 7 H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, H'FFFFFF 3-state access When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-1 H8/3048 Memory Map After Reset B-2 16-bit absolute address area (second half) H'FF8000 8-bit absolute address area 8-bit absolute address area Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF Area 7 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 1. 2. 3. Area 2 Area 6 H'FF8000 Notes: H'007FFF Area 1 Area 3 H'F8000 H'FEF0F H'FEF10 Internal RAM area 16-bit bus, H'FFF00 2-state access H'FFF0F External bus H'FFF10 area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'0000FF Area 0 H'1FFFFF H'200000 Area 1 8-bit absolute address area 16-bit absolute address area (second half) H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access Vector area Area 0 H'7FFFFF H'800000 H'F8000 H'000000 16-bit absolute address area (first half) Area 3 Vector area Expanded 16-bit bus, 16-Mbyte mode 8-bit memory indirect address area H'BFFFF H'C0000 H'5FFFF H'60000 External bus area H'7FFFF 16-bit bus, H'80000 3-state access H'9FFFF H'A0000 H'000000 Mode 4 16-bit absolute address area (first half) H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus area H'7FFFF 8-bit bus, H'80000 3-state access H'9FFFF H'A0000 H'07FFF H'1FFFF H'20000 Area 1 H'3FFFF H'40000 H'000FF Expanded 8-bit bus, 16-Mbyte mode 8-bit memory indirect address area Area 0 H'1FFFF H'20000 Vector area Mode 3 16-bit absolute address area (first half) H'07FFF Expanded 16-bit bus, 1-Mbyte mode H'00000 8-bit memory indirect address area H'000FF Mode 2 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 5 Expanded 8-bit bus, 1-Mbyte mode with ROM H'0000FF Internal ROM area 16-bit bus, 2-state access H'007FFF Single-chip, advanced moe H'00000 Vector area H'000FF Internal ROM area 16-bit bus, 2-state access H'07FFF 16-bit absolute address area (first half) Vector area Mode 7 8-bit memory indirect address area H'07FFF H'000000 16-bit absolute address area (first half) Internal ROM area 16-bit bus, 2-state access Expanded 8-bit bus, 16-Mbyte mode with ROM 8-bit memory indirect address area H'000FF 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 6 H'01FFFF H'020000 Area 0 Area 0 H'1FFFF H'20000 H'1FFFF H'1FFFFF H'200000 Area 1 H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus Area 3 area H'7FFFF 8-bit bus, H'80000 3-state access Area 4 H'9FFFF H'A0000 Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 Area 7 Area 2 H'5FFFFF H'600000 External bus Area 3 area 8-bit bus, 3-state access H'7FFFFF H'800000 Area 4 H'F8000 H'9FFFFF H'A00000 H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access Area 7 8-bit absolute address area Area 6 H'DFFFFF H'E00000 8-bit absolute address area 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF 1. 2. 3. Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'BFFFFF H'C00000 H'FF8000 Notes: H'FEF10 Area 5 16-bit absolute address area (second half) 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'3FFFFF H'400000 16-bit absolute address area (second half) H'F8000 Area 1 When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-1 H8/3048 Memory Map After Reset (cont) B-3 Mode 1 Expanded 8-bit bus, 1-Mbyte mode Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 H'DFFFF H'E0000 Area 7 H'007FFF Area 2 Area 0 H'1FFFFF H'200000 Area 1 Area 3 Area 1 H'3FFFFF H'400000 H'3FFFFF H'400000 Area 4 External bus area H'5FFFFF 8-bit bus, H'600000 3-state access Area 5 Area 2 External bus area H'5FFFFF 16-bit bus, H'600000 3-state access Area 3 Area 3 Area 7 H'7FFFFF H'800000 16-bit absolute address area (second half) Area 4 Area 5 Area 5 H'BFFFFF H'C00000 H'BFFFFF H'C00000 Area 6 Area 6 H'DFFFFF H'E00000 H'DFFFFF H'E00000 Area 7 H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, H'FFFFFF 3-state access When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-2 H8/3047 Memory Map After Reset B-4 16-bit absolute address area (second half) H'FF8000 8-bit absolute address area 8-bit absolute address area Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF Area 7 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 1. 2. 3. Area 4 H'9FFFFF H'A00000 H'9FFFFF H'A00000 H'FF8000 Notes: Area 2 Area 6 H'F8000 H'FEF0F H'FEF10 Internal RAM area 16-bit bus, H'FFF00 2-state access H'FFF0F H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'007FFF Area 0 H'1FFFFF H'200000 Area 1 8-bit absolute address area 16-bit absolute address area (second half) H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'0000FF Area 0 H'7FFFFF H'800000 H'F8000 Vector area 16-bit absolute address area (first half) Area 4 H'0000FF Expanded 16-bit bus, 16-Mbyte mode H'000000 8-bit memory indirect address area H'BFFFF H'C0000 H'5FFFF H'60000 External bus area H'7FFFF 16-bit bus, H'80000 3-state access H'9FFFF H'A0000 Area 3 Vector area Mode 4 16-bit absolute address area (first half) H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus area H'7FFFF 8-bit bus, H'80000 3-state access H'9FFFF H'A0000 H'07FFF H'1FFFF H'20000 Area 1 H'3FFFF H'40000 H'000FF Expanded 8-bit bus, 16-Mbyte mode H'000000 8-bit memory indirect address area Area 0 H'1FFFF H'20000 Vector area Mode 3 16-bit absolute address area (first half) H'07FFF Expanded 16-bit bus, 1-Mbyte mode H'00000 8-bit memory indirect address area H'000FF Mode 2 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 5 Expanded 8-bit bus, 1-Mbyte mode with ROM Reserved H'1FFFF H'20000 H'007FFF H'017FFF H'018000 H'01FFFF H'020000 Reserved Internal ROM area 16-bit bus, 2-state access H'07FFF Area 1 H'3FFFFF H'400000 Area 2 H'5FFFFF H'600000 External bus Area 3 area 8-bit bus, 3-state access H'7FFFFF H'800000 H'F8000 H'FEF10 H'BFFFFF H'C00000 Area 6 H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'DFFFFF H'E00000 Area 7 8-bit absolute address area 8-bit absolute address area Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access Area 5 16-bit absolute address area (second half) Area 4 H'9FFFFF H'A00000 8-bit absolute address area 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF 1. 2. 3. H'000FF H'17FFF H'FF8000 Notes: Vector area H'1FFFFF H'200000 16-bit absolute address area (second half) H'F8000 H'00000 Area 0 Area 2 H'5FFFF H'60000 External bus Area 3 area H'7FFFF 8-bit bus, H'80000 3-state access Area 4 H'9FFFF H'A0000 Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 Area 7 H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access Internal ROM area 16-bit bus, 2-state access Area 0 Area 1 H'3FFFF H'40000 H'0000FF Single-chip, advanced moe 16-bit absolute address area (first half) H'17FFF H'18000 Vector area Mode 7 8-bit memory indirect address area H'07FFF H'000000 16-bit absolute address area (first half) Internal ROM area 16-bit bus, 2-state access Expanded 8-bit bus, 16-Mbyte mode with ROM 8-bit memory indirect address area H'000FF 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 6 When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-2 H8/3047 Memory Map After Reset (cont) B-5 Mode 1 Expanded 8-bit bus, 1-Mbyte mode Area 2 Area 0 H'1FFFFF H'200000 Area 1 Area 3 Area 1 H'3FFFFF H'400000 H'3FFFFF H'400000 Area 4 External bus area H'5FFFFF 8-bit bus, H'600000 3-state access Area 5 Area 2 External bus area H'5FFFFF 16-bit bus, H'600000 3-state access Area 3 H'FEF0F H'FEF10 Internal RAM area 16-bit bus, H'FFF00 2-state access H'FFF0F H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access 16-bit absolute address area (second half) H'F8000 8-bit absolute address area 16-bit absolute address area (second half) H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access Area 3 H'7FFFFF H'800000 Area 4 H'9FFFFF H'A00000 Area 5 Area 5 H'BFFFFF H'C00000 H'BFFFFF H'C00000 Area 6 Area 6 H'DFFFFF H'E00000 H'DFFFFF H'E00000 Area 7 H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, H'FFFFFF 3-state access When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-3 H8/3044 Memory Map After Reset B-6 16-bit absolute address area (second half) H'FF8000 8-bit absolute address area 8-bit absolute address area Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF Area 7 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 1. 2. 3. Area 4 H'9FFFFF H'A00000 H'FF8000 Notes: Area 2 Area 7 H'7FFFFF H'800000 H'F8000 H'007FFF Area 6 H'DFFFF H'E0000 Area 7 H'0000FF 16-bit absolute address area (first half) H'DFFFF H'E0000 Vector area Area 0 H'BFFFF H'C0000 Area 6 Expanded 16-bit bus, 16-Mbyte mode 8-bit memory indirect address area Area 5 H'007FFF 16-bit absolute address area (first half) H'BFFFF H'C0000 Area 4 H'0000FF H'1FFFFF H'200000 Area 1 H'5FFFF H'60000 External bus area H'7FFFF 16-bit bus, H'80000 3-state access H'9FFFF H'A0000 Area 3 Vector area Mode 4 H'000000 Area 0 H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus area H'7FFFF 8-bit bus, H'80000 3-state access H'9FFFF H'A0000 H'07FFF H'1FFFF H'20000 Area 1 H'3FFFF H'40000 H'000FF Expanded 8-bit bus, 16-Mbyte mode H'000000 8-bit memory indirect address area Area 0 H'1FFFF H'20000 Vector area Mode 3 16-bit absolute address area (first half) H'07FFF Expanded 16-bit bus, 1-Mbyte mode H'00000 8-bit memory indirect address area H'000FF Mode 2 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 5 Expanded 8-bit bus, 1-Mbyte mode with ROM H'0000FF Internal ROM area 16-bit bus, 2-state access H'007FFF H'008000 Reserved Vector area H'000FF Internal ROM area 16-bit bus, 2-state access H'07FFF Area 0 Area 0 H'1FFFFF H'200000 Area 1 H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus Area 3 area H'7FFFF 8-bit bus, H'80000 3-state access Area 4 H'9FFFF H'A0000 Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 Area 7 Area 2 H'5FFFFF H'600000 External bus Area 3 area 8-bit bus, 3-state access H'7FFFFF H'800000 H'F8000 H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access Area 5 H'BFFFFF H'C00000 Area 6 H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'DFFFFF H'E00000 Area 7 8-bit absolute address area H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF 16-bit absolute address area (second half) H'FF8000 16-bit absolute address area (second half) Area 4 H'9FFFFF H'A00000 8-bit absolute address area 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access Area 1 H'3FFFFF H'400000 16-bit absolute address area (second half) H'F8000 1. 2. 3. H'00000 H'00FFFF H'010000 H'1FFFF H'20000 Notes: Single-chip, advanced moe 16-bit absolute address area (first half) Reserved H'0FFFF H'10000 Vector area Mode 7 8-bit memory indirect address area H'07FFF H'08000 H'000000 16-bit absolute address area (first half) Internal ROM area 16-bit bus, 2-state access Expanded 8-bit bus, 16-Mbyte mode with ROM 8-bit memory indirect address area H'000FF 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 6 When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-3 H8/3044 Memory Map After Reset (cont) B-7 Mode 1 Expanded 8-bit bus, 1-Mbyte mode Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 H'DFFFF H'E0000 Area 7 H'007FFF Area 2 Area 0 H'1FFFFF H'200000 Area 1 Area 3 Area 1 H'3FFFFF H'400000 H'3FFFFF H'400000 Area 4 External bus area H'5FFFFF 8-bit bus, H'600000 3-state access Area 5 Area 2 External bus area H'5FFFFF 16-bit bus, H'600000 3-state access Area 3 Area 3 Area 7 H'7FFFFF H'800000 16-bit absolute address area (second half) Area 4 Area 5 Area 5 H'BFFFFF H'C00000 H'BFFFFF H'C00000 Area 6 Area 6 H'DFFFFF H'E00000 H'DFFFFF H'E00000 Area 7 H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, H'FFFFFF 3-state access When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-4 H8/3048F Memory Map After Reset B-8 16-bit absolute address area (second half) H'FF8000 8-bit absolute address area 8-bit absolute address area Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF Area 7 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 1. 2. 3. Area 4 H'9FFFFF H'A00000 H'9FFFFF H'A00000 H'FF8000 Notes: Area 2 Area 6 H'F8000 H'FEF0F H'FEF10 Internal RAM area 16-bit bus, H'FFF00 2-state access H'FFF0F H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'007FFF Area 0 H'1FFFFF H'200000 Area 1 8-bit absolute address area 16-bit absolute address area (second half) H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'0000FF Area 0 H'7FFFFF H'800000 H'F8000 Vector area 16-bit absolute address area (first half) Area 4 H'0000FF Expanded 16-bit bus, 16-Mbyte mode H'000000 8-bit memory indirect address area H'BFFFF H'C0000 H'5FFFF H'60000 External bus area H'7FFFF 16-bit bus, H'80000 3-state access H'9FFFF H'A0000 Area 3 Vector area Mode 4 16-bit absolute address area (first half) H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus area H'7FFFF 8-bit bus, H'80000 3-state access H'9FFFF H'A0000 H'07FFF H'1FFFF H'20000 Area 1 H'3FFFF H'40000 H'000FF Expanded 8-bit bus, 16-Mbyte mode H'000000 8-bit memory indirect address area Area 0 H'1FFFF H'20000 Vector area Mode 3 16-bit absolute address area (first half) H'07FFF Expanded 16-bit bus, 1-Mbyte mode H'00000 8-bit memory indirect address area H'000FF Mode 2 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 5 Expanded 8-bit bus, 1-Mbyte mode with ROM H'0000FF Internal flash memory 16-bit bus, 2-state access H'007FFF Single-chip, advanced moe H'00000 Vector area H'000FF Internal flash memory 16-bit bus, 2-state access H'07FFF 16-bit absolute address area (first half) Vector area Mode 7 8-bit memory indirect address area H'07FFF H'000000 16-bit absolute address area (first half) Internal flash memory 16-bit bus, 2-state access Expanded 8-bit bus, 16-Mbyte mode with ROM 8-bit memory indirect address area H'000FF 16-bit absolute address area (first half) Vector area 8-bit memory indirect address area H'00000 Mode 6 H'01FFFF H'020000 Area 0 Area 0 H'1FFFF H'20000 H'1FFFF H'1FFFFF H'200000 Area 1 H'3FFFF H'40000 Area 2 H'5FFFF H'60000 External bus Area 3 area H'7FFFF 8-bit bus, H'80000 3-state access Area 4 H'9FFFF H'A0000 Area 5 H'BFFFF H'C0000 Area 6 H'DFFFF H'E0000 Area 7 Area 2 H'5FFFFF H'600000 External bus Area 3 area 8-bit bus, 3-state access H'7FFFFF H'800000 H'F8000 H'9FFFFF H'A00000 Area 6 H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'DFFFFF H'E00000 Area 7 8-bit absolute address area 16-bit absolute address area (second half) H'FFEF0F H'FFEF10 Internal RAM area H'FFFF00 16-bit bus, H'FFFF0F 2-state access H'FFFF10 External bus area 8-bit bus, H'FFFF1B 3-state access H'FFFF1C Internal I/O area 8-/16-bit bus, 3-state access H'FFFFFF 1. 2. 3. Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'BFFFFF H'C00000 H'FF8000 Notes: H'FEF10 Area 5 16-bit absolute address area (second half) Area 4 8-bit absolute address area 8-bit absolute address area H'FEF0F H'FEF10 Internal RAM area H'FFF00 16-bit bus, H'FFF0F 2-state access H'FFF10 External bus area 8-bit bus, H'FFF1B 3-state access H'FFF1C Internal I/O area 8-/16-bit bus, H'FFFFF 3-state access H'3FFFFF H'400000 16-bit absolute address area (second half) H'F8000 Area 1 When the internal RAM is disabled, the internal RAM area is used as an external address area. Some timer registers in the internal I/O area can be accessed in 3 states through a 16-bit bus. The above bus width and number of external bus area states are those after reset. The values can be changed in one-area units by setting the corresponding registers in the bus controller. Figure B-4 H8/3048F Memory Map After Reset (cont) B-9 Appendix C ASCII Codes Upper 4 bits 0 1 2 3 4 5 6 7 0 NUL DLE SP 0 @ P ' p 1 SOH DC1 ! 1 A Q a q 2 STX DC2 " 2 B R b r 3 ETX DC3 # 3 C S c s 4 EOT DC4 $ 4 D T d t 5 ENQ NAK % 5 E U e u 6 ACK SYN & 6 F V f v 7 BEL ETB ' 7 G W g w 8 BS CAN ( 8 H X h x 9 HT EM ) 9 I Y i y A LF SUB * : J Z j z B VT ESC + ; K [ k { C FF FS , < L \ l | D CR GS - = M ] m } E SO RS . > N ^ n ~ F SI US / ? O _ o DEL Lower 4 bits C-1