Application Note

Using the ZDS Command

Processor for eZ80 and
eZ80Acclaim!™ Flash
Loading
AN016701-0903

ZiLOG Worldwide Headquarters • 532 Race Street • San Jose, CA 95126

Telephone: 408.558.8500 • Fax: 408.558.8300 • www.ZiLOG.com
 Application Note
Using the ZDS Flash Loader with eZ80 and eZ80Acclaim!TM Devices

This publication is subject to replacement by a later edition. To determine whether a later edition
exists, or to request copies of publications, contact:

ZiLOG Worldwide Headquarters

532 Race Street
San Jose, CA 95126
Telephone: 408.558.8500
Fax: 408.558.8300
www.zilog.com

ZiLOG is a registered trademark of ZiLOG Inc. in the United States and in other countries. All other
products and/or service names mentioned herein may be trademarks of the companies with which
they are associated.

Information Integrity
The information contained within this document has been verified according to the general
principles of electrical and mechanical engineering. Any applicable source code illustrated in the
document was either written by an authorized ZiLOG employee or licensed consultant. Permission
to use these codes in any form, besides the intended application, must be approved through a
license agreement between both parties. ZiLOG will not be responsible for any code(s) used
beyond the intended application. Contact the local ZiLOG Sales Office to obtain necessary license
agreements.

Document Disclaimer
©2003 by ZiLOG, Inc. All rights reserved. Information in this publication concerning the devices,
applications, or technology described is intended to suggest possible uses and may be
superseded. ZiLOG, INC. DOES NOT ASSUME LIABILITY FOR OR PROVIDE A
REPRESENTATION OF ACCURACY OF THE INFORMATION, DEVICES, OR TECHNOLOGY
DESCRIBED IN THIS DOCUMENT. ZiLOG ALSO DOES NOT ASSUME LIABILITY FOR
INTELLECTUAL PROPERTY INFRINGEMENT RELATED IN ANY MANNER TO USE OF
INFORMATION, DEVICES, OR TECHNOLOGY DESCRIBED HEREIN OR OTHERWISE. Except
with the express written approval ZiLOG, use of information, devices, or technology as critical
components of life support systems is not authorized. No licenses or other rights are conveyed,
implicitly or otherwise, by this document under any intellectual property rights.

AN016701-0903
 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
General Overview of the ZDS Command Processor . . . . . . . . . . . . . . . . . . 1
Configuring ZDS Virtual Flash Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Using the ZDS Command Processor Flash Loader . . . . . . . . . . . . . . . . . . . . 3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Example of Flashing Using a Command Processor Batch File . . . . . . . . . . 6
Example of Flashing using a DOS Batch File . . . . . . . . . . . . . . . . . . . . . . . 7
Creating a Desktop Shortcut for FlashBurnxx.bat . . . . . . . . . . . . . . . . . . . . 8
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Appendix A: FlashDevice.xml File Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

AN016701-0903
 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Abstract
The Zilog Development System (ZDS) Flash Loader function can be executed
from either the Flash Loader Graphical User Interface (GUI) Dialog Box or the
ZDS Command Processor. The Command Processor option enables the ZDS
Development tool to flash a hex file to memory using the Command Processor
scripting capability provided with ZDS. The Command Processor Flash Loader
provides a simplified interface that reduces the number of steps required for pro-
gramming multiple Flash memory targets. The ZDS Flash Loader function was
introduced with Version 4.5.0 of the ZDS II Integrated Development Environment
(IDE).

Discussion
General Overview of the ZDS Command Processor
The ZDS Command Processor gives users command-script access to almost all
IDE functions. The Command Processor Flash Loader is an extension of this
capability. Refer to the On-Line Help for the latest syntax and for additional exam-
ples that are supported by the ZDS "FLASH" command: ("Help->Help Topics->
Index ->flash-> Flash Loader, running from the Command Processor").

Configuring ZDS Virtual Flash Devices

The eZ80 and eZ80Acclaim!™ development and evaluation platforms contain an
external Micron Flash memory component. The ZDS Flash Loader provides the
ability to define that component as a set of virtual Flash devices. The GUI refers to
these as external Flash devices; they are in reality segments of external Flash
memory defined as virtual Flash devices. The configuration for these virtual Flash
devices is defined in an XML file named flashdevice.xml, located in:
<INSTALL DIRECTORY>\Zilog\ZDS _<Processor>_<version>\config
The flashdevice.xml file defines the configuration for the eZ80 and
eZ80Acclaim!™ external Micron Flash component using the syntax shown in
Table 1.
Caution: The eZ80Acclaim!™ processors feature internal Flash memory as well
as external Flash memory. Internal Flash device configuration is
defined in an XML file named CPUflashdevice.xml. Do not attempt
to modify this file.

AN016701-0903 Abstract
 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Table 1. flashdevice.xml File Syntax

Syntax Description
<flash> Begin Virtual Flash Device Container
<Flash_Device> Begin Virtual Flash Device
<Device_Name>Device 1</Device_Name> Virtual Flash Device Name
<writeSequence>50 40</writeSequence> Micron Control Characteristic
<writeVerifyValue>80</writeVerifyValue> Micron Control Characteristic
<writeVerifyMask>f8</writeVerifyMask> Micron Control Characteristic
<eraseSequencePage>50 20 d0</eraseSequencePage> Micron Control Characteristic
<eraseVerifyValue>80</eraseVerifyValue> Micron Control Characteristic
<eraseVerifyMask>f8</eraseVerifyMask> Micron Control Characteristic
<identifyDevice>90</identifyDevice> Micron Control Characteristic
<readArray>ff</readArray> Micron Control Characteristic
<Device_ID>99</Device_ID> Micron Control Characteristic
<Manuf_ID>89</Manuf_ID> Micron Control Characteristic
<flashBlock> Begin Virtual Flash Device Memory Block
<name>type1</name> Block Name
<baseAddress>40000</baseAddress> Lower Bound
<endAddress>43fff</endAddress> Upper Bound
</flashBlock> End Virtual Flash Device Memory Block
</Flash_Device> End Virtual Flash Device
</flash> End Virtual Flash Device Container

Note: The current Flash loader supports only Micron Flash and cannot be
configured to support Flash devices from other manufacturers.
Users can create, delete and alter virtual Flash devices by modifying the name
and memory address range elements in the XML file, and by adding or removing
Flash block elements. However, the Micron-specific Control Characteristic ele-
ments must be preserved and be present for each defined Flash virtual device.
The complete XML example file for the MT28F008B3 Micron component is
included as Appendix A.

AN016701-0903 Configuring ZDS Virtual Flash Devices

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

The User can select these XML-defined virtual Flash devices in the Flash Loader
GUI Dialog Box or in the SELECTION# parameter field of the Command Processor
FLASH command. The SELECTION# parameter is explained in the following sec-
tion. Each virtual Flash device is numbered sequentially starting with 1 (one) for
the first occurrence of a <Flash_Device> element. See Figure 1.

The Flash Loader Command Script would reference SELECTION# one (:1).

Figure 1. ZDS II Relationship between GUI, XML, and Selection

Using the ZDS Command Processor Flash Loader

To run the Flash Loader from the ZDS Command Processor, use the Command
Dialog Box shown in Figure 2. The ZDS Command Processor accepts either flash
loader commands typed directly into the dialog box, or the name of a file contain-
ing the flash loader commands (script file). Execute the command script by click-

AN016701-0903 Using the ZDS Command Processor Flash Loader

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

ing the Go icon (the green triangle to the left of the command entry field shown in
Figure 2).

Figure 2. ZDS II Command Processor

Command Processor keywords allow easy scripting of the Flash loading process.
Each of the keyword parameters are persistent, allowing users to repeat the flash
and verification process for multiple targets.
To set up ZDS to run the flash loader:
1. Create a new project or open an existing project. Project files supply the
Flash Loader with all information needed to communicate with the target.
2. In the General tab of the Project Settings dialog, set the CPU field to the
eZ80 or eZ80Acclaim!™ microcontroller installed on the target.
3. Set the Chip Select parameters to the correct configuration. The Flash
Loader requires both RAM for execution and the correct external Flash
memory chip select parameters and memory limits. If there is internal RAM,
the Flash Loader uses that memory for execution. The parameters are
entered in the Initializations Dialog Box (Project-> Settings-> Debugger->
Initialization Params…).
4. In the Configure ZPAK II Dialog, specify the ZPAK II Ethernet address. The
Flash Loader uses the ZPAK II to communicate with the target.
Once ZDS is properly configured, you are ready to use the Command Processor.
In the Command Processor toolbar, enter the following command sequence to
use the Flash Loader (see on-line help and Table 2 for option definitions):
FLASH [memory configuration][:<Selection#>] action
<"path\file"> [OFFSET="hexvalue"] [NEBF]|[EBF] [REPEAT]
Notes: [ ] indicates optional commands.
<> indicates a variable.
The Flash Loader GUI Dialog Box and the Command Processor interface
use the same parameters. If you do not specify an option in the Command
Processor interface, the Flash Loader uses the current setting in the Flash
Loader GUI Dialog Box. When you change a setting in the Command
Processor interface, the Flash Loader GUI Dialog Box settings change.

AN016701-0903 Using the ZDS Command Processor Flash Loader

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Table 2. FLASH Command Options

Options Definition
[memory configuration] Defines the Flash memory destination segment. The following options are
available:
<INTMEM | EXTMEM | BOTHMEM>
INTMEM - Internal Flash memory
EXTMEM - External Flash memory (requires selection number)
BOTHMEM - Both internal and external Flash memory (requires selection
number)
<:selection#> Defines the selected memory for external memory (EXTMEM) or internal and
external memory (BOTHMEM) option. Numbering is based on the Flash Loader
dialog box selection options for these memory types. The selection in defined in
the flashdevice.xml file. The first selection is indicated by 1. The format is a
colon followed by an integer number from 1 to the number of devices in the
memory list displayed in the Flash Loader GUI dialog box.
For example: EXTMEM :1
action Defines the command to be used by the Flash Loader. This option is required.
The options are:
[ERASE | BURN | BURNVERIFY | VERIFY | SETUP]
ERASE - Erase selected memory segment
BURN - Flash selected file without verifying
BURNVERIFY - Flash and verify selected file
VERIFY - Verify selected file
SETUP - List current values of all Flash Loader Command Options
"path\file" The file to be used. The file must include the absolute path and must be enclosed
by double quotation marks:
"C:\Program File\test.hex"
Note: If you are referencing files across a network, use the File Explorer
Tools --> Map a Network Drive option to map the remote file system as a network
drive letter and use the network drive letter in your command files instead of the
full network path.
OFFSET="hexvalue" Defines the offset to be set for the specified memory segment. If the internal or
external memory option is selected, the specified file is shifted by the offset
amount. If the both memory option is selected, the offset is applied to both the
internal and external memory segments. The value is read as a hex value and
must be enclosed by double quotation marks.
For example: OFFSET = "0x10000"

AN016701-0903 Using the ZDS Command Processor Flash Loader

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Table 2. FLASH Command Options

Options Definition
NEBF | EBF Defines if the Flash memory is erased before flashing. The options are:
<NEBF | EBF>
NEBF - No erase before flashing
EBF - Erase before flashing
REPEAT (Optional) Sets the Flash Loader to flash recursively. The Flash Loader executes
the command, disconnects from the target, and then prompts to repeat the
operation. The user is given the option to continue or stop.

Example
The following are valid examples for a target with an eZ80F91 and external Flash
memory:
FLASH INTMEM BURN "c:\testing\test.hex" OFFSET="0x1000" EBF
REPEAT
The file test.hex is loaded into internal Flash memory with a value of 0x1000
added to all addresses. The Flash memory is erased before flashing. After the
flashing is completed, the user is prompted to program an additional unit.
FLASH VERIFY
The file test.hex is verified against internal Flash memory with a offset value of
0x1000.
FLASH EXTMEM:1 VERIFY
The file test.hex (from the first example) is verified against the external Flash
selection number one.
FLASH SETUP
The current Flash Loader parameters settings are displayed in the command Out-
put window.

Example of Flashing Using a Command Processor Batch File

The Command Processor interface within the ZDS IDE uses the "BATCH" com-
mand ("Help->Help Topics-> Index ->batch->batch command") to execute a
sequence of ZDS IDE commands. The BATCH command requires a plain text file
as the argument. The text file contains the commands that ZDS executes in a
sequential batch mode. The following ZDS batch file example shows how to
erase, burn and verify FLASH Memory and then repeat for one or more additional
targets:

AN016701-0903 Example
 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

; <Begin File Flashcmd.txt >

;******************************************************************
;Change directory to location of Hex file
cd "<INSTALL DIRECTORY>\zilog\<product><version>\myproject\src"

;Open Project file

open project "<INSTALL DIRECTORY>\Zilog\<product><version>\myproject\src\boardprog.pro"

;Execute flash command

flash intmem burnverify ".\boardprog.hex" EBF REPEAT

;Wait 2 seconds
wait 2000

;exit ZDS
exit
;*******************************************************************
; <End File Flashcmd.txt >

The batch file example above assumes the following:

• A valid project has been created that has the correct memory map for target
Flash and ram.
• The project has already been built and does not need to be rebuilt before
flashing.
• The project has been built in the release Flash configuration (.hex).
• The first target is connected and has power applied.
• The project has the correct Ethernet address selected for the ZPAK.
• The project is using INTERNAL FLASH only and the default SELECTION is
used.
To run the batch file, enter the following command in the ZDS Command Proces-
sor box:
batch "c:\flashcmd.txt"

Example of Flashing using a DOS Batch File

Use a Windows DOS batch (.bat) file to execute a command batch file that flashes
a target. The DOS batch file contains commands that start ZDS and pass a speci-
fied Command Processor batch file. The "@" symbol following the ZDS2IDE.exe
command causes ZDS to process the specified command file after starting ZDS. It
is equivalent to starting ZDS and then entering the command batch "c:\Flash-
cmd.txt" in the command processor window.

Note: In Windows 98, use start /wait to call the ZDS executable.

AN016701-0903 Example of Flashing using a DOS Batch File

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

FlashBurn98.bat Windows 98SE Example

REM Begin Flashburn example
REM The following two lines should be entered as a single line.
start /wait "<INSTALL
DIRECTORY>\Zilog\<product><version>\bin\Zds2Ide.exe" @c:\Flashcmd.txt
REM End Flashburn example

FlashBurnNT.bat WinNT, Win2K, WinXP Example

REM Begin Flashburn example
REM The following two lines should be entered as a single line.
"<INSTALL DIRECTORY>\Zilog\<product><version>\bin\Zds2Ide.exe"
@c:\Flashcmd.txt
REM End Flashburn example

FlashBurn.bat Win98SE, WinNT, Win2K, WinXP Combined Example

REM Begin Flashburn example
set ostype=win98
if %OS%!==Windows_NT! set ostype=NT
if %ostype%==NT goto nt1
:win98

REM The following two lines should be entered as a single line.

start /wait "<INSTALL
DIRECTORY>\Zilog\<product><version>\bin\Zds2Ide.exe" @c:\Flashcmd.txt

goto exit01

:nt1

REM The following two lines should be entered as a single line.

"<INSTALL DIRECTORY>\Zilog\ <product><version>\bin\Zds2Ide.exe"
@c:\Flashcmd.txt

:exit01
REM End Flashburn example

Creating a Desktop Shortcut for FlashBurnxx.bat

You can create a shortcut on the computer desktop that points to a DOS batch file
in the ZDS directory to minimize the number of the steps required to flash a target.
To create the shortcut, right-click the batch file name and select "Create Shortcut".
A shortcut is created in the same folder as the DOS batch file. Drag or copy the
shortcut to the desktop.

AN016701-0903 Creating a Desktop Shortcut for FlashBurnxx.bat

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

Summary
The ZDS Command Processor Flash Loader provides a tool for developers, tech-
nicians, and manufacturing to flash eZ80 and eZ80Acclaim!™ Flash microproces-
sors. Users can automate the flashing process using a combination of DOS Batch
files and ZDS command files.

References
ZiLOG Developer Studio II -- eZ80Acclaim!™ User Manual, UM0144
ZiLOG Developer Studio II -- eZ80 User Manual, UM0123

AN016701-0903 Summary
 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

10

Appendix A: FlashDevice.xml File Listing

<flash>
<Flash_Device>
<Device_Name>1. (40000h-13FFFFh) All--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type1</name>
<baseAddress>40000</baseAddress>
<endAddress>43fff</endAddress>
</flashBlock>
<flashBlock>
<name>type2</name>
<baseAddress>44000</baseAddress>
<endAddress>45fff</endAddress>
</flashBlock>
<flashBlock>
<name>type3</name>
<baseAddress>46000</baseAddress>
<endAddress>47fff</endAddress>
</flashBlock>
<flashBlock>
<name>type4</name>
<baseAddress>48000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

11

<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>100000</baseAddress>
<endAddress>11ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>120000</baseAddress>
<endAddress>13ffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>2. (40000h-047FFFh) Boot and Param Blocks--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type1</name>
<baseAddress>40000</baseAddress>
<endAddress>43fff</endAddress>
</flashBlock>
<flashBlock>
<name>type2</name>
<baseAddress>44000</baseAddress>
<endAddress>45fff</endAddress>
</flashBlock>
<flashBlock>
<name>type3</name>
<baseAddress>46000</baseAddress>
<endAddress>47fff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>3. (48000h-13FFFFh) Main Blocks--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

12

<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type4</name>
<baseAddress>48000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>100000</baseAddress>
<endAddress>11ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>120000</baseAddress>
<endAddress>13fffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>4. (46000h-13FFFFh) w/IVECT TBL--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

13

<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<jmpTable>true</jmpTable>
<interruptJumpTable1>48000</interruptJumpTable1>
<interruptJumpTable2>C00000</interruptJumpTable2>
<flashBlock>
<name>type3</name>
<baseAddress>46000</baseAddress>
<endAddress>47fff</endAddress>
</flashBlock>
<flashBlock>
<name>type4</name>
<baseAddress>48000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>100000</baseAddress>
<endAddress>11ffff</endAddress>
</flashBlock>
<flashBlock>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

14

<name>type11</name>
<baseAddress>120000</baseAddress>
<endAddress>13fffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>5. (48000h-13FFFFh) w/IVECT TBL--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<jmpTable>true</jmpTable>
<interruptJumpTable1>48000</interruptJumpTable1>
<interruptJumpTable2>C00000</interruptJumpTable2>
<flashBlock>
<name>type4</name>
<baseAddress>48000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

15

<baseAddress>100000</baseAddress>
<endAddress>11ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>120000</baseAddress>
<endAddress>13fffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>6. (0000h-FFFFFh) All--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type1</name>
<baseAddress>0000</baseAddress>
<endAddress>3fff</endAddress>
</flashBlock>
<flashBlock>
<name>type2</name>
<baseAddress>4000</baseAddress>
<endAddress>5fff</endAddress>
</flashBlock>
<flashBlock>
<name>type3</name>
<baseAddress>6000</baseAddress>
<endAddress>7fff</endAddress>
</flashBlock>
<flashBlock>
<name>type4</name>
<baseAddress>8000</baseAddress>
<endAddress>1ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>20000</baseAddress>
<endAddress>3ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>40000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

16

<name>type7</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>7. (0000h-07FFFh) Boot&Param Blocks--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type1</name>
<baseAddress>0000</baseAddress>
<endAddress>3fff</endAddress>
</flashBlock>
<flashBlock>
<name>type2</name>
<baseAddress>4000</baseAddress>
<endAddress>5fff</endAddress>
</flashBlock>
<flashBlock>
<name>type3</name>
<baseAddress>6000</baseAddress>
<endAddress>7fff</endAddress>
</flashBlock>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

17

</Flash_Device>
<Flash_Device>
<Device_Name>8. (8000h-FFFFFh) Main Blocks--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<flashBlock>
<name>type4</name>
<baseAddress>8000</baseAddress>
<endAddress>1ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>20000</baseAddress>
<endAddress>3ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>40000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

18

</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>9. (6000h-FFFFFh) w/IVECT TBL--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<jmpTable>true</jmpTable>
<interruptJumpTable1>8000</interruptJumpTable1>
<interruptJumpTable2>C00000</interruptJumpTable2>
<flashBlock>
<name>type3</name>
<baseAddress>6000</baseAddress>
<endAddress>7fff</endAddress>
</flashBlock>
<flashBlock>
<name>type4</name>
<baseAddress>8000</baseAddress>
<endAddress>1ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>20000</baseAddress>
<endAddress>3ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>40000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type9</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

19

<flashBlock>
<name>type10</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
</Flash_Device>
<Flash_Device>
<Device_Name>10. (8000h-FFFFFh) w/IVECT TBL--MT28F008B3</Device_Name>
<writeSequence>50 40</writeSequence>
<writeVerifyValue>80</writeVerifyValue>
<writeVerifyMask>f8</writeVerifyMask>
<eraseSequencePage>50 20 d0</eraseSequencePage>
<eraseVerifyValue>80</eraseVerifyValue>
<eraseVerifyMask>f8</eraseVerifyMask>
<identifyDevice>90</identifyDevice>
<readArray>ff</readArray>
<Device_ID>99</Device_ID>
<Manuf_ID>89</Manuf_ID>
<jmpTable>true</jmpTable>
<interruptJumpTable1>8000</interruptJumpTable1>
<interruptJumpTable2>C00000</interruptJumpTable2>
<flashBlock>
<name>type4</name>
<baseAddress>8000</baseAddress>
<endAddress>1ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type5</name>
<baseAddress>20000</baseAddress>
<endAddress>3ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type6</name>
<baseAddress>40000</baseAddress>
<endAddress>5ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type7</name>
<baseAddress>60000</baseAddress>
<endAddress>7ffff</endAddress>
</flashBlock>
<flashBlock>
<name>type8</name>
<baseAddress>80000</baseAddress>
<endAddress>9ffff</endAddress>
</flashBlock>
<flashBlock>

AN016701-0903 Appendix A: FlashDevice.xml File Listing

 Application Note
Using the ZDS Command Processor for eZ80 and eZ80Acclaim!TM Flash Loading

20

<name>type9</name>
<baseAddress>a0000</baseAddress>
<endAddress>bffff</endAddress>
</flashBlock>
<flashBlock>
<name>type10</name>
<baseAddress>c0000</baseAddress>
<endAddress>dffff</endAddress>
</flashBlock>
<flashBlock>
<name>type11</name>
<baseAddress>e0000</baseAddress>
<endAddress>fffff</endAddress>
</flashBlock>
</Flash_Device>
</flash>

AN016701-0903 Appendix A: FlashDevice.xml File Listing