Debugger Flash Programming

Transcription

1 Debugger Flash Programming Revised 07/17/2003

2 Metrowerks, the Metrowerks logo, and CodeWarrior are registered trademarks of Metrowerks Corp. in the US and/or other countries. All other tradenames and trademarks are the property of their respective owners. Copyright Metrowerks Corporation ALL RIGHTS RESERVED. The reproduction and use of this document and related materials are governed by a license agreement media, it may be printed for non-commercial personal use only, in accordance with the license agreement related to the product associated with the documentation. Consult that license agreement before use or reproduction of any portion of this document. If you do not have a copy of the license agreement, contact your Metrowerks representative or call (if outside the US call ). Subject to the foregoing non-commercial personal use, no portion of this documentation may be reproduced or transmitted in any form or by any means, electronic or mechanical, without prior written permission from Metrowerks. Metrowerks reserves the right to make changes to any product described or referred to in this document without further notice. Metrowerks makes no warranty, representation or guarantee regarding the merchantability or fitness of its products for any particular purpose, nor does Metrowerks assume any liability arising out of the application or use of any product described herein and specifically disclaims any and all liability. Metrowerks software is not authorized for and has not been designed, tested, manufactured, or intended for use in developing applications where the failure, malfunction, or any inaccuracy of the application carries a risk of death, serious bodily injury, or damage to tangible property, including, but not limited to, use in factory control systems, medical devices or facilities, nuclear facilities, aircraft navigation or communication, emergency systems, or other applications with a similar degree of potential hazard. USE OF ALL SOFTWARE, DOCUMENTATION AND RELATED MATERIALS ARE SUBJECT TO THE METROWERKS END USER LICENSE AGREEMENT FOR SUCH PRODUCT. How to Contact Metrowerks Corporate Headquarters World Wide Web Metrowerks Corporation 7700 West Parmer Lane Austin, TX U.S.A. Sales Voice: Fax: sales@metrowerks.com Technical Support Voice: support@metrowerks.com

3 Table of Contents 1 FLASH PROGRAMMING Non Volatile Memory Control Utility 5 Introduction The NVMC Graphical User Interface Introduction NVMC Dialog Box Flash Module Handling Configuration: FPP File Loading Loading an Application in Flash Preparing, Loading an Application in Flash Hardware Considerations HC12B HC12D HC12DG AM29F010 on HC08AZ32EVB (CanKit) Flash Programming and Password Security HC08AT60 / AS60-AZ60 Emulation HC08GP HC08GP About FPP Files A Structure of the FPP File 21 B NVMC Commands 23 FLASH Index 29 Debugger Flash Programming 3

4 Table of Contents 4 Debugger Flash Programming

5 1 FLASH PROGRAMMING Non Volatile Memory Control Utility Introduction Writing to Flash modules, eeproms, or other non-volatile memory modules in modern MCUs requires special algorithms from microprocessor designers. Before you write to Flash devices, you must erase them. Many Flash devices need initialization to become accessible; some devices may need write protection removed. This manual explains The Non Volatile Memory Control (NVMC) utility, an extension component that lets you control on-chip Flash devices for all Debugger targets. As it supports many MCUs and Flash modules, the NVMC utility is very flexible. This flexibility comes from a generic Debugger component, which calls a graphical user interface, then loads an MCU-specific module. The module provides the appropriate information (such as structure, access algorithms, and location) for that MCU. The NVMC utility lists all non-volatile memory devices, indicating their structure, state, and location. You can change the state (enabled/disabled, blank, programmed, protected/unprotected) and program data into the modules. Debugger Flash Programming 5

6 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface The NVMC Graphical User Interface Introduction The NVMC utility is integrated into the Debugger, as an extension of certain targetinterface components. If the NVMC utility is available, your target-component menu includes a Flash... selection. Example with the SDI target Modules and Module States In following sections, the expression available modules means all the FLASH or EEPROM on-chip modules that the NVMC dialog box lists. The module definitions track with the CPU derivative technical summary and special technical considerations. If a module consists of several independent blocks, the NVMC dialog box lists all of these blocks. NOTE Please see Hardware Considerations for more information about the Flash modules of your CPU derivative. Other important expressions are: Enabled An enabled module is a module currently active on the chip; it is possible to read (as a ROM) or program an enabled module. Disabled A disabled module is not active on the chip, so program and reading are not possible. The usual control for enabling or disabling a module is setting/ clearing a flag in a special register. Note that a few modules always must be active; you may not disable such modules. Blank A blank module is empty of code: you can program its full address range. (Each blank byte contains the value 0xFF or 0x00, depending on harware.) 6 Debugger Flash Programming

7 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface Programmed A programmed module is partially programmed (not all bytes contain 0xFF or 0x00). You must keep track of the areas still available for programming, if any. Protected A protected module is partially protected from erasure or programming. The usual control for protecting a module is setting/clearing a flag in a special register. Note that a few modules always must be unprotected; you may not protect such modules. Unprotected An unprotected module can be erased and programmed. To select a module or other list item, left-click the module. To unselect a module, press the Ctrl key and left-click. For multiple selections or unselections, use the Shift key. NVMC Dialog Box The NVMC dialog box lists all the Flash or EEPROM modules of a CPU derivative. A derivative such as the HC12B32 has just one on-chip Flash module; other derivatives have multiple modules. NOTE The dialog box does not have a Select or Unselect button, as you merely click on a module in the list to select it. But selecting and unselecting are not automatic from the command line. Before you use the command line to perform any operation on a module, you must use the SELECT command to select the module.(also see the FLASH SELECT and FLASH UNSELECT commands in Appendix B.) Debugger Flash Programming 7

8 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface For each block, the dialog box has a line of these fields: Name the module name. Start the module start address. End the module end address. State the modules states, such as disabled, enabled, blank, programmed, protected, unprotected. Possible state combinations are: Bad Device (the interface could not detect a correct device) Disabled (one or all modules are disabled) [Enabled] / <Blank Programmed> / [Unprotected Protected] The NVMC dialog box displays only meaningful states. For example, it displays Enabled only if it is possible to disable a module. It displays Unprotected only if it is possible to protect a module. The Configuration group identifies the current.fpp parameter file. This group also includes the Auto select according to MCU-Id checkbox; the Configuration: FPP loading section explains this option. The second checkbox of the Configuration group is Save and restore workspace content. If this checkbox is clear, Flash programming applications overwrite any data in RAM. To save the current RAM data, check this box. (Saving RAM data slows 8 Debugger Flash Programming

9 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface down the NVMC; checking this checkbox is equivalent to entering the SAVECONTEXT and LOADCONTEXT commands.) Flash Module Handling Flash parameter files (which have the extension.fpp) contain MCU-specific parameters, as well as programs to handle internal flash modules. (The FPP Files section includes additional information about.fpp files.) The.FPP files also include code-applet descriptions of flash operations; later text of this manual includes these descriptions. You also may use the Command Line component to handle flash operations. The NVMC Commands section explains the corresponding commands. The NVMC dialog box has buttons for commands you can apply to each block. These buttons are dynamic: active if the operation is possible for at least one selected item, disabled if the operation is not possible. Select All The Select All... button selects all modules in the list box. Enable/Disable The Enable button enables all selected modules currently disabled. The Disable button disables all selected modules currently enabled. (The possibility of enabling or disabling a flash module depends on the MCU features and context.) Protect/Unprotect The Protect button protects all selected modules currently unprotected. The Unprotect button unprotects all selected modules currently protected. (The possibility of protecting or unprotecting a flash module depends on the MCU features and context.) NOTE For some MCUs, protection is possible only for the Boot section and boot routines, not for the entire module. Please see Hardware Considerations for protection information about your CPU derivative. Erase The Erase button removes any programming from all selected Flash modules. (That is, it assigns the value 0xFF or 0x00 to each byte.) Erasure changes the module status to Blank. If all the selected modules already are blank, the Erase button is disabled. Load The Load.. button arms all selected modules, executes a LOAD command, then disarms the modules. If you click the Load.. button without selecting any flash modules, the NVMC utility selects and loads all the modules. Debugger Flash Programming 9

10 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface NOTE The dialog box does not have a Select or Unselect button, as you merely click on a module in the list to select it. But selecting and unselecting are not automatic from the command line. Before you use the command line to perform any operation on a module, you must use the SELECT command to select the module.(also see the FLASH SELECT and FLASH UNSELECT commands in Appendix B.) Configuration: FPP File Loading When the dialog box is open, the NVMC utility loads the.fpp configuration file according to this algorithm: 1. The utility reads the NV_PARAMETER_FILE entry from the target-specific section of the project.ini file. [Motorola ESL] is such a target-specific section. Example: [Motorola ESL] NV_PARAMETER_FILE=C:\MYINSTALL\PROG\FPP\mcu03C4.fpp 2. If the utility retrieves a valid.fpp file name, it loads the file. 3. If the utility cannot find a valid.fpp file name, it displays an appropriate error message. 4. If the utility does not find an entry, or if it finds an empty entry, the utility automatically checks the Auto select according to MCU Id: checkbox. Then the utility loads the parameter file from the \FPP subdirectory of the METROWERKS installation, according to the mcuid. 5. If the utility finds a file that has the wrong format, it displays an appropriate error message. 6. The utility always displays the MCU Id, if the Id is available from the target. Another way to load an.fpp parameter file is clicking the Browse... button. This brings up a standard Open dialog box, which you can use to select the file. When you do so, the Open dialog box disappears, and the NVMC utility loads the file, automatically clearing the Auto select according to MCU Id: checkbox. In case of any error during loading, the utility displays an appropriate message. 10 Debugger Flash Programming

11 FLASH PROGRAMMING Non Volatile Memory Control Utility The NVMC Graphical User Interface If you check the Auto select according to MCU Id: checkbox, the NVMC utility searches for and loads the corresponding.fpp parameter file. Click the OK button to close the NVMC dialog box. If the Auto select according to MCU Id: checkbox is clear, the NVMC utility saves the name of the selected configuration file under the NV_PARAMETER_FILE entry of the project.ini file. If you check this checkbox, the utility dies not save the.fpp in the project file. Click the Cancel button to close the dialog box without saving changes. Loading an Application in Flash The Load... button and the Load... selection of the target-specific menu function identically. Using either of these controls brings up the Load Executable File dialog box, which lets you select the file to be loaded. The Load Executable File dialog box lists the executable files that relate to blocks selected in the NVMC dialog box. Debugger Flash Programming 11

12 FLASH PROGRAMMING Non Volatile Memory Control Utility Preparing, Loading an Application in Flash If a problem occurs during application loading into flash, the NVMC utility displays an error message, such as: if programming voltage is not available. Another possible error message is: This means that you tried to load a program into an unselected section. (The NVMC utility s selecting/unselecting feature reduces the risk of overwriting, erasing, or unprotecting valuable data.) Preparing, Loading an Application in Flash Use either: The NVMC dialog box, which the NVMC Dialog section explains. Flash commands within a command file. Appendix B explains these commands. If necessary, link your application with the appropriate memory model. The example below shows a.prm file for an HC12DG128 application. The default ROM is in pages 2 and 4; the application uses the banked memory model. Make sure that your code location is within a Flash address range. LINK my_appli.abs NAMES my_appli.o ansib.lib start12b.o END SECTIONS MY_RAM = READ_WRITE 0x2010 TO 0x23FF; MY_ROM = READ_ONLY 0xC000 TO 0xFEFF; PAGE_2 = READ_ONLY 0x28000 TO 0x2BFFF; PAGE_4 = READ_ONLY 0x48000 TO 0x4BFFF; PLACEMENT _PRESTART, STARTUP, 12 Debugger Flash Programming

13 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations ROM_VAR, STRINGS, NON_BANKED, COPY INTO MY_ROM; DEFAULT_RAM INTO MY_RAM; MyPage, DEFAULT_ROM INTO PAGE_2, PAGE_4; END STACKSIZE 0x50 VECTOR ADDRESS 0xFFFE _Startup /*set reset vector IN FLASH on _Startup */ Follow the loading command example in Appendix B, or follow these instructions: 1. From the Debugger menu bar, open the target-specific menu (such as SDI). Select Flash... the NVMC dialog box appears. 2. If you are sure about the absolute location of your application, you do not need to select a module. But if you program in a protected area (boot block), make sure that the matching module is unprotected. 3. Click the Load... button the NVMC utility selects all modules and opens the Load Executable File dialog box. 4. Select the.abs file to be loaded into Flash. Loading begins; a progress bar appears. When loading is finished, the NVMC dialog box displays the new state of the modules. 5. This completes loading. You can close the NVMC dialog box and run your application. For some some hardware, however, you first must do a target reset, by clicking the reset button of the Debugger. Hardware Considerations This section consists of hardware-specific information about current.fpp files. A release note will explain any new.fpp file features. NOTE The Flash Programming release note, in the on-line documentation of your toolkit installation, contains the latest information about.fpp files. Debugger Flash Programming 13

14 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations HC12B32 fpp file name: mcu03c1.fpp number of Flash modules: 1 -applet code currently not relocatable, loaded at 0x800, using 0x400 bytes. module name: FLASH_B32 / module number: 0-32 KBytes flash located in 0x8000-0xFFFF or 0x0000-0x7FFF (both handled, according to MAPROM bit in MISC register). -boot sector unprotectable/protectable (2 KBytes in range 0xF800-0xFFFF or 0x7800-0x7FFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). -flash enable/disable via ROMON bit in MISC register. HC12D60 fpp file name: mcu03c3.fpp number of Flash modules: 2 -applet code currently not relocatable, loaded at 0x400, using 0x400 bytes. module name: FEE28 / module number: 0-28 KBytes flash located in 0x1000-0x7FFF or 0x9000-0xFFFF (both handled, according to MAPROM bit in MISC register). -boot sector unprotectable/protectable (8 KBytes in range 0x6000-0x7FFF or 0xE000-0xFFFF) (via BOOTP bit in FEE28MCR register and LOCK bit in FEE28LCK register). -flash enable/disable via ROMON28 bit in MISC register. module name: FEE32 / module number: 1-32 KBytes flash located in 0x8000-0xFFFF or 0x0000-0x7FFF (both handled, according to MAPROM bit in MISC register). -boot sector unprotectable/protectable (8 KBytes in range 0xE000-0xFFFF or 0x6000-0x7FFF) (via BOOTP bit in FEE32MCR register and LOCK bit in FEE32LCK register). -flash enable/disable via ROMON32 bit in MISC register. 14 Debugger Flash Programming

15 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations HC12DG128 fpp file name: mcu03c4.fpp number of Flash modules: 10 -applet code currently not relocatable, loaded at 0x2000, using 0x400 bytes. -all flash modules enable/disable at same time via ROMON bit in MISC register. module name: FLASH_4000 / module number: 0-16 KBytes unpaged Flash located in 0x4000-0x8000 also matches 11FEE even page (6), that is, FLASH_PAGE6. module name: FLASH_PAGE0 / module number: 1-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 00FEE Flash even page (0). module name: FLASH_C000 / module number: 2-16 KBytes unpaged Flash located in 0xC000-0xFFFF also matches 11FEE odd page (7),that is, FLASH_PAGE7. -boot sector unprotectable/protectable (8 KBytes in range 0xE000-0xFFFF or paged range 0xA000-0xBFFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). module name: FLASH_PAGE1 / module number: 3-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 00FEE Flash odd page (1). -boot sector unprotectable/protectable (8 KBytes in range 0xA000-0xBFFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). module name: FLASH_PAGE2 / module number: 4-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 01FEE Flash even page (2). module name: FLASH_PAGE3 / module number: 5-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 01FEE Flash odd page (3). -boot sector unprotectable/protectable (8 KBytes in range 0xA000-0xBFFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). module name: FLASH_PAGE4 / module number: 6 Debugger Flash Programming 15

16 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations - 16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 10FEE Flash even page (4). module name: FLASH_PAGE5 / module number: 7-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 10FEE Flash odd page (7). -boot sector unprotectable/protectable (8 KBytes in range 0xA000-0xBFFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). module name: FLASH_PAGE6 / module number: 8-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 11FEE Flash even page (6). Also equivalent to FLASH_4000 module. module name: FLASH_PAGE7 / module number: 9-16 KBytes paged Flash accessed in bank window 0x8000-0xBFFF, equivalent to (cf Technical Summary) 11FEE Flash odd page (7). Also equivalent to FLASH_C000 module. -boot sector unprotectable/protectable (8 KBytes in range 0xA000-0xBFFF) (via BOOTP bit in FEEMCR register and LOCK bit in FEELCK register). AM29F010 on HC08AZ32EVB (CanKit) fpp file name: cankit08.fpp number of Flash modules: 1 -applet code currently not relocatable, loaded at 0x100, using 0x200 bytes. -not possible to enable/disable/unprotect/protect but can be done by jumper. Please read below. module name: AM29F010 / module number: 0-32 KBytes external optional Flash module chip on CanKit board M68HC08AZ32EVB, located in 0x8000-0xFFFF. To be added on U3 board socket. Note: The jumper JP3 position 1-2 hard-selects the Flash module; jumper JP3 position 2-3 hard-selects the 32 KBytes on-board RAM. Flash Programming and Password Security Some HC08 MCUs, such as the AT/AS/AZ60 and GP20, have security built into the Mon08. This prevents unauthorized access to on-chip FLASH EEPROM. FLASH 16 Debugger Flash Programming

17 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations access to Mon08 of any of these devices requires a password immediately after a Power-On reset. You must specify the password in the HC08 Mon08 Target Interface setup dialog box. If the password is wrong, reading or scrolling the Flash memory always returns the value AD. NOTE All settings below relate to HC08 Mon08 Target Interface setup dialog (the Communication and Debug Option Setup dialog). Changing password: Check the password checkbox, then enter the Mon08 password. Example: Enter: This value always matches when the flash is empty for AZ/AS/AT and GP20 devices. (The value of all unprogrammed, blank, and factory-default bytes is 0x00). NOTE All unprogrammed bytes of the GP32 derivative have the value 0xFF, so the blank/factory password is FF FF FF FF FF FF FF FF. NOTE Some MCU derivatives require a password for any access, even if the values are not checked. In such a case, you must set the password option, but the value of all bytes can be 0x00. NOTE You must make the password connection immediately after MCU Power-on reset (power off + power on). Do not make a password connection after a software or external Reset pin toggle: in such a case, only the on-chip Mon08 monitor checks the password. Each time the debugger communicates with the on-chip Mon08 monitor, it backs up the memory vector password, in log file PWLOG.TXT, in your current project directory. The Password address text box (usually at address range $FFF6-$FFFD) specifies this password. The debugger also backs up the password each time you erase or program the flash. If you do not want log file PWLOG.TXT, insert the line 'NOPWLOGFILE=1' in the [MON08] section of the PROJECT.INI file (in your current project directory). The deliberate awkwardness of this disabling method is Debugger Flash Programming 17

18 FLASH PROGRAMMING Non Volatile Memory Control Utility Hardware Considerations consistent with good security; no dialog box within the debugger lets you disable this security. The setup dialog box includes the Warn when... checkbox. Check this box to be warned if a password mismatch occurs at connection, after programming, or after erasing. The setup dialog box also includes the Autorefresh... checkbox. Check this box to automatically update the password text boxes when you modify a password. NOTE If a lost password prevents your access to Flash, use the Flash Programming dialog to erase the Flash modules. After this erasure, the Flash Programming dialog box returns the status Bad Device, because the Flash modules read AD, so blank verification fails. To reset the Monitor on-chip security, do a power reset (power off + power on) of your HC08 derivative. Then set up the Monitor HC08 with password (FF FF FF FF FF FF FF FF for a GP32), and reconnect to the hardware. HC08AT60 / AS60-AZ60 Emulation fpp file name: mcu0e36.fpp number of Flash modules: 5 -applet code currently not relocatable, loaded at 0x50, using 0x200 bytes. module name: EEPROM_2 / module number: Bytes EEPROM located in 0x600-0x7FF. module name: EEPROM_1 / module number: Bytes EEPROM located in 0x800-0x9FF. module name: FLASH_2 / module number: 2 - flash located in 0x450-0x5FF, 0xE00-0x7FFF, 0xFF81. module name: FLASH_1 / module number: 3 - flash located in 0x8000-0xFDFF, 0xFF80. module name: VECTORS / module number: 4 - flash vectors located in 0xFFCC-0xFFFF. 18 Debugger Flash Programming

19 FLASH PROGRAMMING Non Volatile Memory Control Utility About FPP Files HC08GP20 fpp file name: mcu0c26.fpp number of Flash modules: 2 -applet code currently not relocatable, loaded at 0x50. module name: FLASH / module number: 0 -about 20 KBytes flash located in 0xB000-0xFDFF. module name: VECTORS / module number:1 -vectors in 0xFFDC-0xFFFF. HC08GP32 fpp file name: mcu0c55.fpp number of Flash modules: 2 -applet code currently not relocatable, loaded at 0x50. module name: FLASH / module number: 0 -about 32 KBytes flash located in 0x8000-0xFDFF. module name: VECTORS / module number:1 -vectors in 0xFFDC-0xFFFF. About FPP Files MCU-specific flash parameter files (with extension.fpp) control the Flash operations, which Appendix B explains. The.FPP files contain MCU-dependent parameters and applets to handle internal flash modules. These.FPP files are simple text files; any text editor can edit them. MCU designers or METROWERKS personnel write the.fpp files; installation of your NVMC utility includes installation of the.fpp files. Applets are small programs, loaded into the on-chip RAM. Applets run at well-defined speeds, relative to the MCU clock. They can collect data about the state of memory modules, they can control the memory modules (including erasing and programming). Three applets exist for each flash module: Debugger Flash Programming 19

20 FLASH PROGRAMMING Non Volatile Memory Control Utility About FPP Files INFO which collects information about the module CONTROL which controls (includes erasing) the module PROGRAM which programs the module. The system passes parameter values to these applets at fixed memory addresses (relative to the workspace). 20 Debugger Flash Programming

21 A Structure of the FPP File The figure below shows part of an.fpp file, identifying the parameters that can be edited. applet file name, containing the mcuid mcuid matching the file name workspace size workspace start address module names programming buffer offset applet code You should never modify the applet file name, mcuid, applet code, programming buffer offset or last parameter of the WORKSPACE definition line (for example 3 ). However, you can modify the names of the modules. You can change the order in which the NVMC dialog box lists the modules applets. (Modules start from the MODULE keyword and end before next MODULE keyword.) Debugger Flash Programming 21

22 Structure of the FPP File Applets reside in MCU RAM or SRAM. Therefore, the default workspace start address (0x2000, in the figure) is the default RAM start address of the MCU. If your MCU lets you move the RAM block to a dfferent memory-map location, you can set the new workspace starting address in the.fpp file. NOTE Refer to the Hardware Considerations section for more information about applet code relocation in your CPU derivative. The workspace size (0x400, in the figure) can be all or part of the MCU RAM. The workspace-size value must not be less than the programming buffer offset value (0x100, in the figure). When you program a Flash module, the system first loads the application into a RAM buffer, after the applet code, Then the applet copies the application to the destination in Flash. For the fastest programming, the programming buffer size should be as big as possible. For this configuration, increase your workspace size to all RAM available on the MCU. (In the figure example, the buffer size is: workspace size 0x400 - offset 0x100 = 0x300.) To increase the speed of saving and loading RAM content, disable the commands FLASH LOADCONTEXT and FLASH SAVECONTEXT. 22 Debugger Flash Programming

23 B NVMC Commands FLASH Short Description displays flash modules, loads.fpp file, or performs flash operations. Syntax FLASH [(SELECT UNSELECT ERASE ENABLE DISABLE PROTECT UNPROTECT) [<blockno>]] ARM DISARM SAVECONTEXT LOADCONTEXT] [INIT <filename> <mcuid>] Debugger Flash Programming 23

24 NVMC Commands Description The FLASH command displays names, locations, and states of all available modules, provided that a parameter (.fpp) file is already loaded. If no parameter file is loaded, this command loads either the.fpp file for the current mcuid or the last-used.fpp file. FLASH INIT <filename> AUTOID loads the parameter file according to filename (you can specify the path). If this command includes AUTOID, the MCU ID determines the parameter file (autocheck is checked in the NVMC dialog box). FLASH ENABLE enables the specified modules. If no modules are specified, enables all available blocks. This command ignores modules that cannot be enabled. FLASH DISABLE disables the specified modules. If no modules are specified, all disables all available blocks. This command ignores modules that cannot be disabled. FLASH ERASE erases the specified modules. If no modules are specified, erases all available blocks. FLASH UNPROTECT unprotects the specified modules. If no modules are specified, unprotects all available blocks. This command ignores modules that cannot be unprotected. FLASH PROTECT protects the specified modules. If no modules are specified, protects all available blocks. This command ignores modules that cannot be protected. FLASH SELECT selects the specified modules for flash programming. If no modules are specified, selects all available blocks for flash programming. FLASH UNSELECT unselects the specified modules. If no modules are specified, unselects all available blocks. (The unselected state protects against accidental flash programming.) FLASH ARM prepares the NMVC utility for loading; as does a normal LOAD command. The system executes the VPPON.CMD file. This command is required before loading flash. FLASH DISARM ends a load process. The system executes the VPPOFF.CMD file. FLASH SAVECONTEX backs up current SRAM content into a buffer. FLASH LOADCONTEX restores current buffer content into the MCU SRAM. [<blockno>] blockno is a list of flash block/module numbers, according to this syntax: 24 Debugger Flash Programming

25 NVMC Commands blockno = {number["-"number][","]} Examples: FLASH ERASE 2,7 This erases memory blocks 2 and 7. FLASH ERASE 2,4-6 8 This erases memory blocks 2, 4, 5, 6, and 8. FLASH ERASE This erases all available memory blocks. While flash modules are armed, execution of user code is not possible. If you enter a command such as run, step, or so forth, a message box prompts you to disarm the modules or cancel the command. If you click the OK button, the system disarms all flash modules, then executes your command. If you click the CANCEL button, the system cancels the command and leaves the flash modules armed. Example of flash programming from the Command Line component in>flash FLASH parameters loaded for M68HC912DG128 from J:\HC12_EA\PROG\FPP\mcu03C4.fpp MCU clock speed: Module Name Address Range Status FLASH_ FFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_C000 C000 - FFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected HALTED The FLASH command loads the applet that corresponds to the CPU derivative (mcuid) and displays the state of all modules. If you want to program an application into module number 7 (FLASH_PAGE5), you must unprotect the module. Debugger Flash Programming 25

26 NVMC Commands in>flash unprotect 7 MCU clock speed: Module Name Address Range Status FLASH_ FFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_C000 C000 - FFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Unprotected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected in>flash The updated display shows that FLASH_PAGE5 is unprotected. Select FLASH_PAGE5 for programming. in>flash select 7 Arm for programming. in>flash arm Arm FLASH for loading. Now you can load your application. in>load a:\my_page5.sx RUNNING Stop loading and disarm. in>flash disarm FLASH disarmed. Halted Use the FLASH command to display the final state of the modules. MCU clock speed: Module Name Address Range Status FLASH_ FFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_C000 C000 - FFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected 26 Debugger Flash Programming

27 NVMC Commands FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Programmed/Unprotected - Selected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected HALTED The FLASH_PAGE5 module is programmed. You must protect and unselect the module. in>flash protect 7 MCU clock speed: Module Name Address Range Status FLASH_ FFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_C000 C000 - FFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Programmed/Protected - Selected FLASH_PAGE BFFF Enabled/Blank - Unselected FLASH_PAGE BFFF Enabled/Blank/Protected - Unselected in>flash unselect 7 This completes the example. Debugger Flash Programming 27

28 NVMC Commands 28 Debugger Flash Programming

29 Index Symbols.FPP file 19.FPP file loading 10 A AM29F Applet 21 Applet edition 21 Applet format 21 Application loading 11 ARM 23 Auto select according to MCU Id 11 B blank 8, 9 blockno 23 Blocks 6 Buffer 21 C CanKit 16 cankit08.fpp 16 Commands 23 CONTROL applet 20 D Dialog 7 disabled 8 Disabling 9 DISARM 23 E EEPROM_1 18 EEPROM_2 18 ENABLE 23 enabled 8 Enabling 9 End 8 ERASE 23 Erasing 9 F FEE28 14 FEE32 14 filename 23 FLASH 19, 23 Commands 23 Disabling 9 Enabling 9 Loading 11 Module 7 Module selecting 9 Operations 9 Protecting 9 Select 7, 10 Unprotecting 9 Unselect 7, 10 Flash Lost Password 18 Password Erasing 18 Flash Programming 18 FLASH SELECT 7, 10 FLASH UNSELECT 7, 10 FLASH_1 18 FLASH_2 18 FLASH_ FLASH_B32 14 FLASH_C FLASH_PAGE0 15 FLASH_PAGE1 15 FLASH_PAGE2 15 FLASH_PAGE3 15 FLASH_PAGE4 15 FLASH_PAGE5 16 FLASH_PAGE6 16 FLASH_PAGE7 16 FPP Browse 10 FPP directory 10 G GUI Graphical User Interface 6 H Hardware 13 Debugger Flash Programming 29

30 HC08AS60 18 HC08AT60 18 HC08AZ32EVB CanKit 16 HC08AZ60 18 HC08GP20 19 HC08GP32 19 HC12B32 14 HC12D60 14 HC12DG How to Load 12 I INFO applet 20 INIT 23 L LOADCONTEXT 22, 23 Loading error 12 Loading problems 12 M mcu03c1.fpp 14 mcu03c3.fpp 14 mcu03c4.fpp 15 mcu0c26.fpp 19 mcu0c55.fpp 19 mcu0e36.fpp 18 mcuid 10, 23 MODULE 21 Modules 7 N Name 8 NOPWLOGFILE 17 NV_PARAMETER_FILE 10 NVMC commands 23 P Password 17 Address 17 Changing 17 Default (cleared flash) 17 Mismatch 18 Warning 18 Power-on reset Debugger Flash Programming

31 PROGRAM applet 20 Program loading 11 programmed 8 Programming buffer 21 project.ini 10, 11 PROTECT 23 protected 8 Protecting 9 S SAVECONTEXT 22, 23 Security 16 SELECT 23 Selecting 7, 9, 10 Start 8 State 8 States 8 U UNPROTECT 23 unprotected 8 Unprotecting 9 UNSELECT 23 Unselecting 7, 10 V VECTORS 18 W WORKSPACE 21 Workspace 20, 22 Debugger Flash Programming 31

32 32 Debugger Flash Programming