User manual
Table Of Contents
- COVER
- TABLE OF CONTENTS
- CHAPTER 1 GENERAL INFORMATION
- CHAPTER 2 DEBUG MONITOR DESCRIPTION
- CHAPTER 3 DEBUG MONITOR COMMANDS
- CHAPTER 4 ASSEMBLER/DISASSEMBLER
- CHAPTER 5 SYSTEM CALLS
- CHAPTER 6 DIAGNOSTIC FIRMWARE GUIDE
- APPENDIX A S-RECORD INFORMATION
- APPENDIX B SELF-TEST ERROR MESSAGES
- APPENDIX C USER CUSTOMIZATION
- LIST OF FIGURES
- LIST OF TABLES
- Table 2-1. Debugger Address Parameter Format
- Table 2-2. CPU32Bug Exception Vectors
- Table 3-1. Debug Monitor Commands
- Table 4-1. CPU32Bug Assembler Addressing Modes
- Table 5-1. CPU32Bug System Call Routines
- Table 6-1. MCU CPU Diagnostic Tests
- Table 6-2. Memory Diagnostic Tests
- Table B-1. Self-Test Error Messages
- Table C-1. CPU32Bug Customization Area
- Table C-2. MCU SCI Communication Formats
- Table C-3. Rev. A Chip Selection Summary
- Table C-4. Rev. B Chip Selection Summary
- Table C-5. BCC Rev. C Chip Selection Summary
- Table C-6. PFB Rev. C Compatibility
- CHAPTER 1 GENERAL INFORMATION
- CHAPTER 2 DEBUG MONITOR DESCRIPTION
- CHAPTER 3 DEBUG MONITOR COMMANDS
- 3.1 INTRODUCTION
- 3.2 BLOCK OF MEMORY COMPARE
- 3.3 BLOCK OF MEMORY FILL
- 3.4 BLOCK OF MEMORY MOVE
- 3.5 BREAKPOINT INSERT/DELETE
- 3.6 BLOCK OF MEMORY SEARCH
- 3.7 BLOCK OF MEMORY VERIFY
- 3.8 DATA CONVERSION
- 3.9 DUMP S-RECORDS
- 3.10 GO DIRECT (IGNORE BREAKPOINTS)
- 3.11 GO TO NEXT INSTRUCTION
- 3.12 GO EXECUTE USER PROGRAM
- 3.13 GO TO TEMPORARY BREAKPOINT
- 3.14 HELP
- 3.15 LOAD S-RECORDS FROM HOST
- 3.16 MACRO DEFINE/DISPLAY/DELETE
- 3.17 MACRO EDIT
- 3.18 MACRO EXPANSION LISTING ENABLE/DISABLE
- 3.19 MEMORY DISPLAY
- 3.20 MEMORY MODIFY
- 3.21 MEMORY SET
- 3.22 OFFSET REGISTERS DISPLAY/MODIFY
- 3.23 PRINTER ATTACH/DETACH
- 3.24 PORT FORMAT
- 3.25 REGISTER DISPLAY
- 3.26 COLD/WARM RESET
- 3.27 REGISTER MODIFY
- 3.28 REGISTER SET
- 3.29 SWITCH DIRECTORIES
- 3.30 TRACE
- 3.31 TRACE ON CHANGE OF CONTROL FLOW
- 3.32 TRANSPARENT MODE
- 3.33 TRACE TO TEMPORARY BREAKPOINT
- 3.34 VERIFY S-RECORDS AGAINST MEMORY
- CHAPTER 4 ASSEMBLER/DISASSEMBLER
- CHAPTER 5 SYSTEM CALLS
- 5.1 INTRODUCTION
- 5.2 SYSTEM CALL ROUTINES
- 5.2.1 Calculate BCD Equivalent Specified Binary Number
- 5.2.2 Parse Value, Assign to Variable
- 5.2.3 Check for Break
- 5.2.4 Timer Delay Function
- 5.2.5 Unsigned 32 x 32 Bit Divide
- 5.2.6 Erase Line
- 5.2.7 Input Character Routine
- 5.2.8 Input Line Routine
- 5.2.9 Input Serial Port Status
- 5.2.10 Unsigned 32 x 32 Bit Multiply
- 5.2.11 Output Character Routine
- 5.2.12 Output String Using Pointers
- 5.2.13 Print Carriage Return and Line Feed
- 5.2.14 Read Line to Fixed-Length Buffer
- 5.2.15 Read String Into Variable-Length Buffer
- 5.2.16 Return to CPU32Bug
- 5.2.17 Send Break
- 5.2.18 Compare Two Strings
- 5.2.19 Timer Initialization
- 5.2.20 Read Timer
- 5.2.21 Start Timer at T=0
- 5.2.22 Output String with Data
- 5.2.23 Output String Using Character Count
- CHAPTER 6 DIAGNOSTIC FIRMWARE GUIDE
- 6.1 INTRODUCTION
- 6.2 DIAGNOSTIC MONITOR
- 6.2.1 Monitor Start-Up
- 6.2.2 Command Entry and Directories
- 6.2.3 Help (HE)
- 6.2.4 Self Test (ST)
- 6.2.5 Switch Directories (SD)
- 6.2.6 Loop-On-Error Mode (LE)
- 6.2.7 Stop-On-Error Mode (SE)
- 6.2.8 Loop-Continue Mode (LC)
- 6.2.9 Non-Verbose Mode (NV)
- 6.2.10 Display Error Counters (DE)
- 6.2.11 Clear (Zero) Error Counters (ZE)
- 6.2.12 Display Pass Count (DP)
- 6.2.13 Zero Pass Count (ZP)
- 6.3 UTILITIES
- 6.4 CPU TESTS FOR THE MCU
- 6.5 MEMORY TESTS (MT)
- 6.6 BUS ERROR TEST
- APPENDIX A S-RECORD INFORMATION
- APPENDIX B SELF-TEST ERROR MESSAGES
- APPENDIX C USER CUSTOMIZATION
DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-34
MA Macro Define/Display MA
NOMA
Macro Delete NOMA
3.16 MACRO DEFINE/DISPLAY/DELETE
MA [<name>]
NOMA [<name>]
The <name> can be any combination of 1-8 alphanumeric characters.
The MA command allows the user to define a complex command consisting of any number of
CPU32Bug primitive commands with optional parameter specifications. By simply entering the
new <name> plus any arguments on the command line, the stored CPU32Bug commands are
executed. This allows the user to design new commands to simplify the debug process. The
NOMA command is used to delete either a single macro or all macros.
Entering MA without specifying a macro name causes CPU32Bug to list all currently defined
macros and their definitions.
When MA is executed with the name of a currently defined macro, that macro definition is
displayed.
Line numbers are shown when displaying macro definitions to facilitate editing via the macro
edit (MAE) command. If MA is executed with a valid name that does not currently have a
definition, then the CPU32Bug enters the macro definition mode. In response to each macro
definition prompt "M=", enter a CPU32Bug command and a carriage return. Commands entered
are not checked for syntax until the macro is executed. To exit the macro definition mode, enter
only a carriage return (null line) in response to the prompt. If the macro contains errors, it can
either be deleted and redefined or it can be edited with the MAE command. A macro containing
no primitive CPU32Bug commands (i.e., no definition) is not accepted.
Macro definitions are stored in a string pool of fixed size. If the string pool becomes full while in
the definition mode, the offending string is discarded, a message STRING POOL FULL, LAST
LINE DISCARDED is printed and the user is returned to the CPU32Bug command prompt. This
also happens if the string entered would cause the string pool to overflow. The string pool has a
capacity of 511 characters. The only way to add or expand macros when the string pool is full is
to either edit or delete macros.
CPU32Bug commands contained in macros may reference arguments supplied at invocation
time. Arguments are denoted in macro definitions by embedding a back slash (\) followed by a
numerial. As many as ten arguments are permitted. A definition containing a back slash followed
by a zero would cause the first argument to that macro to be inserted in place of the "\0"
characters.
DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-31
LO Load S-Records From Host LO
3.15 LOAD S-RECORDS FROM HOST
LO [<port><del>][<addr>][;<X/-C/T>][=<text>]
Use the LO command to download a Motorola S-records format data file from a host computer
to the BCC. The LO command accepts serial data from the host and loads it into on-board
memory.
The optional port number allows the user to specify the download port. If this number is omitted,
the default is port 0.
The BCC default hardware configuration consists of one I/O port; P4 on the BCC or P9 on the
PFB. This limits the user to one host computer running a terminal emulation program. To send S-
records, the user must escape out of the terminal emulation program because the host computer
can not perform terminal emulation and send S-records at the same time. When the host is not in
terminal emulation mode, all status messages from CPU32Bug would be lost. Thus the user must
press <CR> twice after re-entering the terminal emulation program to signal CPU32Bug that
status messages can now be sent.
The optional <addr> field allows the user to enter an offset address. This offset address is added
to the address contained in the address field of each record which causes the records to be stored
in memory at a different location. The contents of the automatic offset register are not added to
the S-record addresses (see OF command). If the address is in the range $0 to $1F and the port
number is omitted, enter a comma before the address to distinguish it from a port number. Only
absolute addresses (i.e., "1000") should be entered, as other addressing modes cause
unpredictable results. An address is allowed here rather than an offset (expression) to permit
support for function codes (see paragraph 2.5).
The optional text field, entered after the equal sign (=), is sent to the host before CPU32Bug
begins looking for S-records at the host port. This allows the user to send a download command
to the host device. This text should NOT be delimited by quote marks. The text string begins
immediately following the equal sign and terminates with the carriage return. If the host is
operating full duplex, the string is echoed back to the host port by the host and appears on the
user’s terminal screen.
In order to accommodate host systems that echo all received characters, the above-mentioned text
string is transmitted to and received from the host one character at a time. After the entire
command is sent to the host, LO looks for a line feed (LF) character from the host, signifying the
end of the echoed command. No data records are processed until this LF is received. If the host
system does not echo characters, LO continues looking for an LF character before data records
are processed. In situations where the host system does not echo characters, it is required that the
first record transferred by the host system be a header record. The header record is not used, but
the LF after the header record serves to break LO out of the loop so data records are processed.
Fr
eescale S
emiconduct
or
, I
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
nc...