M68PCbug11/V3.40-2 January 1994 M68PCbug11 V3.40 Information Copyright (c) MOTOROLA Ltd., 1994; All Rights Reserved Motorola reserves the right to make changes without further notice to any products herein to improve reliability, function, or design. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under its patent rights nor the rights of others. Motorola products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other application in which the failure of the Motorola product could create a situation where personal injury or death may occur. Should Buyer purchase or use Motorola products for any such unintended or unauthorized application, Buyer shall indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent regarding the design or manufacture of the part. Motorola and the Motorola logo are registered trademarks of Motorola Inc. Motorola Inc. is an Equal Opportunity/Affirmative Action Employer. TABLE OF CONTENTS 1. Summary 5 2. Major Improvements 5 2.1. PCbug11 Environment 5 2.2. Environment File 5 2.3. Initialisation File 9 2.4. Command Logging 9 2.5. File Structure Changes 9 2.6. Initialisation of Communications 10 2.7. MCU Driven Macros 10 2.8. Communications Error Messages 10 2.9. CONTROL TIMEOUT Default 11 2.10. EEPROM Programming 11 2.11. EPROM Programming 11 2.12. Status Window 11 2.13. CONTROL PROTECT 11 3. Commands 12 3.1. Command Descriptions 15 3.1.1. BAUD [rate] 15 3.1.2. BL 15 3.1.3. BR [addr [macroname]] 15 3.1.4. CONTROL 15 3.1.5. CONTROL BASE 15 3.1.6. CONTROL COLOR|COLOUR 15 3.1.7. CONTROL LOG OPEN|CLOSE|ON|OFF 16 3.1.8. CONTROL PROTECT 16 3.1.9. CONTROL RTS ON|OFF 16 3.1.10. DEFM macrname|TRACE|AUTOSTART| 16 3.1.11. DIR 16 3.1.12. EDITM 16 3.1.13. EEPROM 16 3.1.14. EEPROM DELAY 16 3.1.15. EEPROM ERASE ENABLE|DISABLE 16 3.1.16. ENV 17 3.1.17. EPROM 17 3.1.18. EPROM DELAY 17 3.1.19. HELP 17 3.1.20. HELP MCU [topic] 17 3.1.21. PROTECT 17 3.1.22. RM 17 3.1.23. RS 17 3.1.24. TERM 17 LIST OF TABLES Table 1 PCbug11 COMMANDS 12 Table 2 PCbug11 COMMANDS (continued) 13 Table 3 PCbug11 COMMANDS (continued) 14 LIST OF FIGURES Figure 1 Contents of Environment file 6 Figure 2 Example Environment file 8 MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 3 of 17 Copyright (c) MOTOROLA Ltd., 1994; All Rights Reserved MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 4 of 17 1. Summary PCbug11 V3.40 contains a number of major feature improvements and corrections to commands. Key upgrades include the ability to define PCbug11 default parameters at start-up, an improved programming algorithm for EPROM devices, an option to log all commands and the ability for the MCU to drive specific macros. PCbug11 V3.40 is upward compatible with PCbug11 V3.24a and its talkers although a new talker library exists for this version. 2. Major Improvements The sections below deal with major enhancements. Section 3 describes the changes to the full command set. 2.1. PCbug11 Environment Within PCbug11 there are certain parameters that determine the way the program looks and behaves. Examples include the colours of the windows, communications frequencies and the control options. The user could only change some of these through PCbug11 commands or command line options. In this version of the software, it is possible to store and recall these parameters along with some others. This allows a much greater degree of customisation than has been possible until now. These parameters are known as the 'environment'. The files that contain these parameters are called 'environment files'. A defined format exists for this file and the following section describes this structure. To allow the user to make full use of this new feature easily, new commands are available; the description below also contains details of these. To further extend the usefulness of the environment, PCbug11 can optionally update the parameters each time the user closes the program. This means that the environment file records the status of PCbug11 on termination of the program, allowing the user to continue from a given point in his debugging when restarting. There may, however, also be instances when the user would require a known environment at start up. If this was the case then it is possible to define the behaviour of the environment such that no update takes place. In addition, the definition of the environment file allows groups of parameters within the environment to have their own termination status. That is PCbug11 only records the status of some of the parameters. The user specifies the PCbug11 environment file on the command line at start-up. Even with the environment feature it is still possible to include command line options. In this case the options on the command line override related parameters within the environment file. See the following section for further information. 2.2. Environment File Those parameters that are part of PCbug11's environment are: Start-up parameters (talker, baud rates, name displayed) MAP parameters CONTROL options EEPROM and EPROM ranges Defined Breakpoints Screen colour attributes Command Stack Macros (libraries to be opened at start-up) Figure 1 shows the specific parameters involved. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 5 of 17 TALKER parameters name (displayed on Status screen) boot (talker option, e.g. A, E, K, KW, etc.) start (Baud rate for talker downloads) run (Baud rate for communications) MAP parameters Per map file description, and EPROG (address of EPROG register) PPROG (address of PPROG register) prog_jmp address of BSR to write to memory read_jmp address of BSR to read memory CONTROL parameters COM port ERRMSG on/off LAST error TIMEOUT value BASE BIN/DEC/HEX EEPROM parameters All ranges ERASE before write DELAY for programming EPROM parameters All ranges DELAY for programming BOOTROM where EPROM range overlaps internal boot ROM BR parameters All ranges breakpoint macros STACK parameters All previous commands on command stack (up to 16) WINDOW parameters Foreground and background colours of main window, register window, status window and command history window. MACRO parameters names of macro library files to be loaded at start-up Figure 1 Contents of Environment file MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 6 of 17 PCbug11 uses the default extension '.P11' for environment files. The user can override this default by stating another extension. To load an environment file the syntax is: PCBUG11 ENV1 where ENV1 is an environment file name. Figure 2 shows an example of what ENV1.P11 might contain. As noted above, PCbug11 loads the environment parameters at the start of the program's execution. Options on the command line override any related parameters and normal PCbug11 commands can also override once the program is running. This means that although the environment file defines the talker in use, the user can be override this default (by adding a boot talker switch on the command line). For example ENV1.P11 defines the talker in use as TALKK.BOO, however the following command line: PCBUG11 ENV1 -E forces the download of boot talker TALKE.BOO. To override the map parameters in the environment file, specify an alternative map file on the command line. Similarly, the user can override the default baud rates. Note that the baud= switch on the command line scales the download baud rate and the communications baud rate. For example ENV1.P11 specifies a download baud rate of 1200 baud and a communications baud rate of 19200. The command PCBUG11 ENV1 BAUD=600 would cause the download baud rate to be 600 and the communications baud rate to be 9600. The user may override the communications port parameter in a similar way. By using the new ENV command the user can select which options to update when the quitting the program. PCbug11 stores the environment in the format shown in figure 2. The user must take care when storing breakpoints for the following reason. PCbug11 saves the address value and the opcode at the address of the breakpoint. The opcode stored is the one that existed when the user defined the breakpoint. If the user changes the opcode at the address of the breakpoint then he must clear the breakpoint at that address before doing so; otherwise whenever the running program reached a breakpoint, PCbug11 would write the wrong opcode into the address. Note that any AUTOSTART macro defined on the command line runs after the installation of any of the above environment parameters. If an environment specified macro library contains an AUTOSTART macro then this also runs after the initialisation of the environment. If both the environment file and the command line contain macro library options that have AUTOSTART macros within them, then the AUTOSTART macro defined by the command line will execute. Note that if the command line does not specify an environment then the default loaded is identical to that in PCbug11 V3.24a. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 7 of 17 ENV1.P11 Environment @ 11:14:33 16/10/1992 ~ENVIRONMENT~ ENV SAVE ^ ~TALKER~ name 68HC11N4 boot k start 1200 run 19200 ^ ~MAP~ talker_start $0100 talker_idle $0118 user_start $0100 xirq_ujmp $0153 relocate_buf $00F0 xirq_srv $0153 swi_srv $0153 swi_idle $0118 null_srv $0153 xirq_jmp $00C5 swi_jmp $00C5 cme_jmp $00C5 EPROG $003B PPROG $002B prog_jmp $0147 read_jmp $0130 ^ ~CONTROL~ CONTROL NOSAVE COM 1 ERRMSG LAST TIMEOUT $1C69 BASE HEX ^ ~EEPROM~ EEPROM SAVE $B600 $B7FF ERASE DELAY $000D ^ ~EPROM~ EPROM SAVE BOOTROM $A000 $FFFF DELAY $006 ^ ~BR~ BR NOSAVE $0100 $FF RUN ^ ~COMMAND STACK~ STACK SAVE control colour RD md 0 ^ ~WINDOWS~ WINDOWS SAVE MAIN $7E REGHEAD $4F REGVALUE $4E HISTORY $0F STATUS $5F ^ ~MACROS~ 711n4.mcr ^ Figure 2 Example Environment file MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 8 of 17 2.3. Initialisation File The number of HC11 devices and bootstrap options is increasing at such a large rate that the process of updating the source code to be able to accommodate them all in the command line compiler is becoming too intensive. As a result the number of devices "known" to PCbug11 will remain fixed as present and future devices will be accommodated using an initialisation file. The command line compiler reads this file, that the user can modify and update, when the program runs. The file is in a text format and contains the following information: 1) Text string displayed by the command line compiler 2) The talk index which indicates which talker to download 3) An optional environment file to be loaded. PCbug11 predefines nine devices. PCBUG11.P11 is the name defined for the initialisation file. Each line must contain the following information, in the following format, for each new device: NAME=name INDEX=talker ENV=envfile The delimiter used is a space. For example: NAME=68HC11P2 INDEX=K ENV=P2.P11 In this case the Command Line Compiler would display the text "MC68HC11P2", and choose the talker file TALKK and the environment file P2.P11. For the Command line compiler to recognise the option, the items in bold and the '=' sign must be present. The ENV parameter is optional and independent. 2.4. Command Logging PCbug11 V3.40 contains a new feature that allows the user to log all of his commands entered and the response to them in a text file called PCBUG11.LOG. The file contains the commands entered preceded by a Ψ symbol and the results of the commands (as shown on the main window). There are four new commands to allow the user to control the log file. Initiate logging by the command: CONTROL LOG OPEN This opens a file called PCBUG11.LOG (if possible) and enables the storing of all subsequent commands and responses in it. Suspend logging temporarily, if required, by use of the command: CONTROL LOG OFF This stops logging of commands and responses until the command: CONTROL LOG ON re-enables logging. To close the log file two alternatives are possible; either quit PCbug11 normally (QUIT) or close the file without quitting using the command: CONTROL LOG CLOSE Note that opening the log file while it already exists simply overwrites the previous file. 2.5. File Structure Changes PCbug11 no longer requires the assembler mnemonic files CODES.P11 and OFFSETS.P11 and will not check for their existence. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 9 of 17 2.6. Initialisation of Communications If PCbug11 detects a communications error immediately upon running, or after a RESTART, then it aborts the subsequent communications with the MCU. This means that PCbug11 displays fewer communications failure messages after start-up. It also means that the user should restart his software if he wishes to use the communications functions of PCbug11. This is especially true if using a ROMed talker (where it is possible to restore communications) as certain system parameters remain uninitialised. 2.7. MCU Driven Macros A new extension allows the MCU to drive macros within PCbug11. These macros use a coded name that corresponds to the value of the byte received on the communications port. The name of the macro must be of the form: where byte is a hexadecimal byte value. For example, if the MCU sends a byte with the hex value $23 to the PC then PCbug11 can optionally execute the macro <23>. PCbug11 warns the user that an MCU driven macro is pending by the message: MCU MACRO event pending to accept The user has the option of stopping PCbug11 from executing the macro by responding to the message with any key except . Pressing causes PCbug11 to abort the current command (saving any macro edit) and execute the macro specified. PCbug11 reserves certain byte values. Allowable ranges are: <00> to <3F> User definable <40> to <7F> Reserved by PCbug11 <80> to Reserved for future use A possible use for this function is to allow the user to check the communications between the PC and the MCU. An MCU emerging from the reset state will automatically transmit a break character that the PC reads as a $00. A macro defined as <00> could automatically indicate a received transmission by printing a simple message on the main window. In this case a macro could be DEFM <00> BEGIN MSG COMMUNICATIONS OK!! END The user must exit the terminal emulator by pressing the Esc key. 2.8. Communications Error Messages If PCbug11 detects a communications failure then it displays a new last error message: General Communications Failure The MCU block is shown as ? the state is shown as UNKNOWN PCbug11 also examines the PC communications hardware much more closely. If PCbug11 is unable to access the communications port hardware directly it will default to BIOS access. If BIOS access fails then the PCbug11 will abort and display the message COMMUNICATIONS HARDWARE FAILURE If the user attempts to change the COM port in use with the CONTROL command then PCbug11 will attempt to verify the presence of the new port. If the port does not exist then PCbug11 displays the same error and ignores the command. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 10 of 17 2.9. CONTROL TIMEOUT Default PCbug11 will now make an estimate as to the timeout value required by the PC in use. The minimum timeout set will be 1000 and the maximum will be 15000. It is possible that the value chosen may be too low or too high for the PC in use. In this case the user can alter the value chosen by the program. This value is part of the environment and PCbug11 loads (saves) it as part of the environment (.P11) file. 2.10. EEPROM Programming PCbug11 now displays the number of bytes programmed using the EEPROM algorithm on a per byte basis rather than the previous $100 byte basis. The algorithm that PCbug11 uses to program on-chip EEPROM has been altered slightly. The change increases the size of the program by 1 byte. This will not alter the operation of any currently available HC11s on PCbug11. 2.11. EPROM Programming The EPROM programming section now has its own independent timing delay. PCbug11 formerly shared this value with the EEPROM programming command. In addition, the new EPROM programming algorithm significantly improves the time taken to program large EPROM blocks. This requires a slight change to the talkers used for programming. PCbug11 will detect whether the talker in use is suitable for the new EPROM programming algorithm. PCbug11 V3.40 comes with a full suite of new talkers. The new EPROM delay option now displays the actual programming time for each byte in MCU cycles. The granularity of the EPROM delay is seven cycles. Note that 1 cycle corresponds to 500ns programming time for an HC11 running at 8MHz crystal, therefore each seven cycle increment or decrement causes and increase or decrease in programming time of 3.5Κs. Another enhancement of the EPROM programming algorithm is that PCbug11 can now ignore boot ROM contents when programming and verifying EPROM ranges. That is, if a boot ROM lies on top of an EPROM range then PCbug11 reads and writes the EPROM rather than the boot ROM. The environment file contains a parameter BOOTROM that defines that the enhancement is in use. If BOOTROM is not specified then PCbug11 takes no account of boot ROM location. Note it is not good practice to define BOOTROM when the EPROM does not overlap boot ROM; this causes an extension in the time taken to program EPROM. 2.12. Status Window This window now includes the current number base status. Also the status window displays the 'RTS level' status above the 'STATE:' bar. 2.13. CONTROL PROTECT PCbug11 V3.40 removes this command and all auto protect features. The user can still use the RTS line to protect memory blocks but must manually reset the RTS line when using PCbug11 to modify memory (A macro with CONTROL RTS ON/OFF can achieve this). MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 11 of 17 3. Commands Table 1 shows a full list of commands available within PCbug11. Changed and new commands are indicated as follows * - NEW command; @ - Changed command. The following sections describe only those commands that have changed from that described in the PCbug11 manual M68PCbug11/D. New commands include a description and a usage guide. Table 1 PCBUG11 COMMANDS ŠΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΐΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥͺ †COMMAND † DESCRIPTION † ΓΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ‘ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΌ †ASM addr [mne|dir] † Call symbolic macro line assembler, † † † with option to auto-insert mnemonic † † † or directive. † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †BAUD [rate] † Display or set serial baud rate † †BF addr1 [addr2] byte|word † Block fill memory with byte or word † †BL † Display Breakpoints † †BR [addr[macroname]] † Display or set breakpoint [with † † † optional command execution] † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †CALL addr † Execute the subroutine at addr † †CLRM † Clear all command macros † †CLS † Clear main window † †CONTROL † Display or set CONTROL parameters † †CONTROL BASE BIN|HEX|DEC † Change default number base † †CONTROL BIOS † Access serial COM port through BIOS † † † calls † †CONTROL COLOR † Set PCbug11 display colors † †CONTROL COLOUR † Set PCbug11 display colours † †CONTROL COM1 † Use COM1 port † †CONTROL COM2 † Use COM2 port † †CONTROL EPROG address † Change the EPROM register address † †CONTROL ERRMSG option † Enable or disable display of error † † † messages † †CONTROL HARDWARE † Access serial COM port directly through † † † hardware † †CONTROL LAST † Toggle the last error † † † message window on or off † †CONTROL LOG CLOSE † Close the open command log file † †CONTROL LOG OFF † Suspend logging to command log file † †CONTROL LOG ON † Enable logging to the † † † command log file † †CONTROL LOG OPEN † Open the command log file † †CONTROL PPROG address † Change the EEPROM register address † †CONTROL PROTECT † Use the RTS to provide † † † memory protection † †CONTROL RTS † Control the RTS line directly † †CONTROL RTS ON|OFF † Set RTS line high or low † †CONTROL TIMEOUT [value] † Display or set the value of † † † serial COM timeout during input † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †DASM addr1 [addr2] † Disassemble from addr1 [to addr2] † †DB startaddr [endaddr] † Display MCU memory † †DEBUG † Reserved word † †DEFINE symbol value|address † Define a symbol † »ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΊ MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 12 of 17 Table 2 PCBUG11 COMMANDS (continued) ŠΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΐΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥͺ †COMMAND † DESCRIPTION † ΓΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ‘ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΌ †DEFM macrname|TRACE|AUTOSTART† Define a command, trace or † † † autostart macro † †DELM macrname|TRACE|AUTOSTART† Delete a command, trace or † † † autostart macro † †DIR [mask] † Display disk directory † †DOS [command] † Shell to DOS or execute DOS command † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †EDITM macroname † Edit a macro † †EEPROM [startaddr[endaddr]] † Display, clear, or set EEPROM address † † † range(s) † †EEPROM DELAY [option] † Display or set EEPROM erase or write † † † programming time † †EEPROM ERASE † Display EEPROM erase-before-write state † †EEPROM ERASE BULK [addr] † Bulk erase EEPROM array at $B600 or † † † [addr] † †EEPROM ERASE DISABLE † Disable erase-before-write function † †EEPROM ERASE ENABLE † Enable erase-before-write function † †ENV † Define environment save options † †EPROM [startaddr[endaddr]] † Display, clear, or set EPROM address † † † range(s) † †EPROM DELAY [option] † Display or set EPROM erase or write † † † programming time † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †FIND byte|word addr1 addr2 † Find all occurrences of byte or word † † † between addr1 and addr2 † †FIND mnemonic addr1 addr2 † Find all occurrences of mnemonic † † † between addr1 and addr2 † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †G [addr] † Start user code execution † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †HELP [command] † Display help Information † †HELP MCU [topic] † Display help on specific MCU topic † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †KLE † Kill last error message † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †LOADM [filename [macroname]] † Load macro definition from default or † † † user file † †LOADS filename [loadaddr] † Load S-record into MCU memory † †LS symbol † Display symbols † †LSTM [mname|TRACE|AUTOSTART] † Display macro names or definitions † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †MD startaddr [endaddr] † Display MCU memory † †MM addr † Modify memory from addr † †MOVE addr1 addr2 addr3 † Move MCU memory between addr1 and addr2 † † † to addr3 † †MS addr byte|word [byte|word]† Set MCU memory bytes(s) or word(s) † †MSG [string] † Display message in main window † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †NOBR [address] † Remove or specified breakpoints † »ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΊ MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 13 of 17 Table 3 PCBUG11 COMMANDS (continued) ŠΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΐΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥͺ †COMMAND † DESCRIPTION † ΓΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ‘ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΌ †PAUSE [ms] † Wait for any key press or delay time † †PRINT † Display PCbug11 version number † †PROTECT[startaddr[endaddr]] † Display, clear, or set write-protected † † † address range(s) † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †QUIT [Y] † Terminate PCbug11 session [without † † † confirming] † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †RD [T] † Display or trace MCU registers † †RESET [addr] † MCU hardware reset with existing or new † † † reset vector † †RESTART [option] † Restart PCbug11 with same or new option † †RM † Modify MCU registers in window † †RS register value † Set value of MCU register † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †S † Stop user code execution † †SAVEM [filename] † Save macro definitions in default or † † † user file † †SHELL [command] † Shell to DOS or execute DOS command † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †T [addr] † Display or trace MCU registers † †TERM [X1 Y1 X2 Y2] † Simple windowed terminal emulator † †TYPE filename † Display disk file in main window † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †UNDEF symbol † Undefine a symbol † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †VER † Display PCbug11 version number † †VERF filename [memaddr] † Verify S-record disk file against † † † memory † †VERF ERASE addr1 [addr2] † Verify that memory contains $FF † †VERF SET addr1 addr2 value † Verify that memory contains the value † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †WAIT [ms] † Wait for any key press or delay time † «ŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸΧŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸŸ †CTRL B † Send break on COM channel † †CTRL P † Toggle MCU memory write protect/RTS † † † line † †CTRL R † Try to re-synchronise talker † »ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥ ΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΥΊ MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 14 of 17 3.1. Command Descriptions The following sections describe the changes which have been made to the standard PCbug11 commands and new additions. 3.1.1. BAUD [rate] If option is specified then main window now displays EEPROM delay time since this is affected by baud rate changes. The EPROM delay is no longer affected by baud rate changes 3.1.2. BL Command now displays the currently defined breakpoints in a pop-up window. Clear the window by pressing or . When run from a macro the command does not cause a pop-up window to occur 3.1.3. BR [addr [macroname]] Without options command now displays the currently defined baud rates in a pop-up window. Clear the window by pressing or . With options the new values and any previously defined are displayed in a pop-up window. Clear the window by pressing or . When run from a macro the command does not cause a pop-up window to occur 3.1.4. CONTROL This command now displays a pop-up window which allows the user to modify most control options. Status of the following items are added to the command: Baud rate; command log file status; Display format of the following commands are changed: Hardware access; error messages; PPROG/EPROG The user can alter the values of each CONTROL option by using the up/down arrows or in some options (baud rate, I/O timeout, PPROG, EPROG) by entering a alphanumeric value. Symbols are not acceptable in this window. Move between field by using the page up/down or TAB/back TAB keys. Once complete, to change the control values press , to retain the original values use . 3.1.5. CONTROL BASE This command included a bug which did not allow the user to change from hex mode directly into decimal mode, this is corrected in this release. 3.1.6. CONTROL COLOR|COLOUR Allows the user to alter the default window foreground and background colours. Once the command has been entered a text message will be displayed on the main window indicating to the user how to change the colours. To change a text colour the up and down arrows are used. To change a background colour the left/right arrows are used. To move from one window to another the page up and page down keys are used. To complete the change press . To exit without making any changes press . If the environment save option is active the new colours will be stored at program termination and loaded next time the program is run. Usage : CONTROL COLOUR Change current screen colours CONTROL COLOR Change current screen colors Related commands : none MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 15 of 17 3.1.7. CONTROL LOG OPEN|CLOSE|ON|OFF This command enables the command logging feature. Usage : CONTROL LOG OPEN Open the command log file PCBUG11.LOG CONTROL LOG CLOSE Close the command log file PCBUG11.LOG CONTROL LOG OFF Suspend the command log file PCBUG11.LOG CONTROL LOG ON Re-enable the command log file PCBUG11.LOG Related commands : none 3.1.8. CONTROL PROTECT This command has been removed. 3.1.9. CONTROL RTS ON|OFF This command is provided to allow the user to force the RTS line high or low explicitly. Without parameters the command forces the PC to control the status of the RTS line directly. With parameters the RTS line is forced high (ON) or low (OFF). Usage : CONTROL RTS ON Force RTS line high CONTROL RTS OFF Force RTS line low Related commands: ^P 3.1.10. DEFM macrname|TRACE|AUTOSTART| This command now accepts a new format for macro names to allow them to be driven directly by the MCU. The format allows byte values received at the communications port to activate macros directly. The format is 3.1.11. DIR This command now displays the contents of the disk directory in a pop-up window with additional information on the path being displayed and the number of the item being viewed. 3.1.12. EDITM The display format of this command has been changed such that the pop-up window now displays the line number being edited. This command does not now accept the name of a macro which is also a valid PCbug11 command. 3.1.13. EEPROM This command now displays the result of setting the EEPROM range on the main window. The range checking on the command is much smarter. 3.1.14. EEPROM DELAY This command now displays the result of setting the EEPROM DELAY on the main window. 3.1.15. EEPROM ERASE ENABLE|DISABLE This command now displays the result of enabling or disabling the EEPROM ERASE on the main window. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 16 of 17 3.1.16. ENV This command is used to select the settings for saving of the PCbug11 environment. The user can alter the values of each ENV option by using the up/down arrows or in the filename option by entering a alphanumeric name. Move between field by using the page up/down or TAB/back tab keys. Once complete, to change the env values press , to retain the original values use . Usage : ENV Alter the current default environment save parameters Related commands : none 3.1.17. EPROM This command now displays the result of setting the EPROM range on the main window. The range checking on the command is much smarter. The erase-before-write message is discarded. 3.1.18. EPROM DELAY This command now displays the result of setting the EPROM DELAY on the main window. The operation o the EPROM DELAY has changed for this version; it is now displayed in the number of HC11 MCU cycles used for the delay. To calculate the actual delay simply multiply the number of cycles with the time taken for 1 E-clock cycle. For example at an operating frequency of 8MHz, the E clock will be 2MHz or 500ns per cycle. Therefore a delay of 4000 cycles will produce a programming delay of approximately 2ms. The delay count can be set in increments of 7. 3.1.19. HELP Display format amended to include information on the topic being viewed and the line number of the topic being viewed. 3.1.20. HELP MCU [topic] This new command allows the user to view MCU specific information. Without parameters it displays a menu screen detailing topics available. With the topic specified it displays information on that item. Usage : HELP MCU Display general help information on current MCU HELP MCU CONFIG Display help information on CONFIG register Related commands : none 3.1.21. PROTECT This command now displays the result of setting the PROTECT range on the main window. The range checking on the command is much smarter. 3.1.22. RM This command now allows the use of TAB and Back TAB to move between fields. 3.1.23. RS This command included a bug which did not allow the user to select certain registers (ACCA, ACCB) while in hex mode, this is corrected in this release. 3.1.24. TERM The display of information for this command is changed. The terminal defaults are now the co-ordinates of the main window. This is the maximum extent of the terminal window. The register display window is blanked and reads 'Terminal window active' when the terminal is active. MCU Development Systems EKB Copyright (c) Motorola Ltd 1994 PCbug11 V3.40 Information -2 17 of 17 =========================================================================== PCbug11 V3.41 Information ------------------------- This document notes the changes made to PCbug11 for revision 3.41. The changes are noted with respect to V3.40. A8 Start Up Option ------------------ There existed a possibility that PCbug11 could read a valid ID from the A0/1/8 device an incorrectly set up its internal options. For example the A8 device could read as a 711D3 and PCbug11 would thence prevent EEPROM or breakpoint operations. This has been corrected. Copyright (c) Motorola Ltd 1994; all rights reserved. ____________________________________________________________________________ PCbug11 V3.42 Information ------------------------- This document notes the changes made to PCbug11 for revision 3.42. The changes are noted with respect to V3.41. PCBUG11 Start Up Option ------------------ PCbug11 failed to recognise the PCBUG11 PCBUG11 command line as identical to the PCBUG11 command line. This has been corrected. The command line is intended for use in Windows systems as a method of starting PCbug11 with the command line compiler. Copyright (c) Motorola Ltd 1994; all rights reserved. ============================================================================= PCbug11 V3.20 Information This document notes information for PCbug11 revision 3.20. Command Line Ateration ---------------------- PCbug11's DOS command line has been significantly changed for this version as compared to earlier issues. Full details are contained in the text, however, the key features are: . Explicit declaration of macro names, baud rate and com port . Simplification of boot type talker selection . Simplification of directory structure by creation of new .XOO files . Feature to allow parameters to be passed to the AUTOSTART macro . New single file for help Placing of .MAP files --------------------- The PCbug11 documentation indicates that any .MAP files should be placed in the user's working directory. In V3.20 PCbug11 will not find the user's .MAP file unless it is in the same directory as PCBUG11 itself. PCbug11 V3.21 Information This document notes the changes made to PCbug11 for revision 3.21. The changes are noted with respect to V3.20. See also PCbug11 V3.20 Information. S-Records of more than 8KB -------------------------- A problem existed in earlier versions when loading or verifying S-records of more than 8Kbytes. This occurred when an S-record exceeded the PC internal 8Kbyte boundary. This could cause the PC to crash or cause strange graphic effects. This has now been remedied. Programming 711 parts --------------------- 68HC711 parts may be programmed more quickly using PCbug11 if an alternative crystal is used. If a crystal of 4.9152MHz is used then the HC11 is capable of communicating at 38400 Baud. This in turn reduces the programming time required by internal EPROM to one quarter of the normal time. The method requires a talker which initialises the SCI properly, the option baud=4800 to start PCbug11, and the digit 7 as a prefix to the bootloader type. A talker called TALK7E.BOO is supplied to program the 711E9 part. To use this talker the command line should be: PCBUG11 -7E baud=4800 On detecting the presence of the 7 and the baud=4800 options together, PCbug11 will use a default baud rate of 38400. If either of these options are missing then PCbug11 will default to its standard baud rate. PCbug11 V3.22 Information This document notes the changes made to PCbug11 for revision 3.22. The changes are noted with respect to V3.21. See also PCbug11 V3.21 Information. EEPROM and EPROM bugs --------------------- A possibility existed that the EPROM and EEPROM functions would not work with certain options. This concerns mainly options - A/D/K. Option D would allow all the normally disallowed commands and would not program properly. K would not program EEPROM or EPROM properly and A would not program EEPROM correctly. This bug has been fixed on the current version. PCbug11 V3.23 Information This document notes the changes made to PCbug11 for revision 3.23. The changes are noted with respect to V3.22. See also PCbug11 V3.22 Information. CONTROL command options ----------------------- Two options have been added to allow the location of the PPROG (EEPROM) and EPROG (EPROM) programming registers to be moved by the user. This may be necessary in the future as the HC11 family develops. The address of these registers may be the same - i.e. one register performing both tasks. The current values are displayed using the CONTROL command on its own. The values may be changed using the format CONTROL PPROG addr (addr is the address to be used) CONTROL EPROG addr (addr is the address to be used) Note that PCbug11 assumes that the relevant bits in each register maintains the same position as in the 711E9. User Map files -------------- This must now be placed in the userΉs working directory as described in the manual Command Line Compiler --------------------- The crystal value used parameter entered to the command line compiler is now given in KHz. This will allow the use of an extended range of values. EPROM Command ------------- An EPROM memory range error now reads 'Invalid EPROM address range'. EPROM/EEPROM Programming Error ------------------------------ The error displayed is now 'Programming t/out' or 'Programming cmd' depending on the failure. Loading and Verifying S-records ------------------------------- An upgrade here allows users to load and verify S-record files which contain backward discontinuous S-records. The code was already able to handle forward jumps in the S-record but not backward jumps. This is now allowed. Automatic Recognition --------------------- PCbug11 now has the capability of recognising which HC11 is in use from the contents of the boot ROM. The boot ROM contains information in two bytes which help to describe the part in use. PCbug11 reads these and displays the version in use by the MCU : label. Note that some MCUs may not be recognised correctly by this feature. PCbug11 V3.24(a) Information This document notes the changes made to PCbug11 for revision 3.24 and V3.24a. The changes are noted with respect to V3.23. See also PCbug11 V3.23 Information. Memory Operation Buffer ----------------------- The memory buffer for reads and writes has been increased to 12Kbytes. This allows an increased size of block to be handled by PCbug11 before it carries out the operation. This should increase the operating speed of the code for this kind of operation. The change will transparent to users who move read or write blocks of less than 8Kbytes. Default Number Base ------------------- PCbug11 now allows the default number base used to be altered. Up till now this has always been decimal. To use hex numbers the prefix character $ had to be used. Now the default base can be changed between hex, decimal and binary. The default can be overridden at any point by placing the appropriate prefix in front of the number. The prefixes are $ -hex, & - decimal, % - binary. The default base is handled by the CONTROL command. A new option BASE has been added. To change the default base the command CONTROL BASE HEX|DEC|BIN should be used. To display the default base use the CONTROL command on its own. V3.24a - CONTROL TIMEOUT Upgrade -------------------------------- For users of very fast PCs the default timeout has been changed from 1000 to 2000. The value may be changed back to 1000 or another value by the command CONTROL TIMEOUT value See User's Manual page 3-11. In addition the value is not now re-initialised by the RESTART command. Therefore any change made by the user will remain until the program is terminated.