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

DIAGNOSTIC FIRMWARE GUIDE
M68CPU32BUG/D REV 1 6-4
6.2.13 Zero Pass Count (ZP)
Executing this command resets the pass counter DP to zero. This is frequently desirable before
entering a command that executes the loop-continue mode. Entering this command on the same
line as LC results in the pass counter being reset every pass.
6.3 UTILITIES
The monitor is supplemented by several utilities that are separate and distinct from the monitor
itself and the diagnostics.
6.3.1 Write Loop
WL.<SIZE> [<ADDR> [<DEL><DATA>]]
The WL command executes a streamlined write of specified size to a specified memory location.
This command is intended as a debugging aid once specific fault areas are identified. The write
loop is very short in execution so measuring devices such as oscilloscopes may be utilized in
tracking failures. Pressing the BREAK key does not terminate this command, but pressing the
ABORT switch or RESET switch does.
Command size must be specified as B for byte, W for word, or L for longword.
The command requires two parameters: target address and data to be written. The address and
data are both hexadecimal values and must not be preceded by a $. To write $00 out to address
$10000, enter WL.B 10000 00. The system prompts the user if either or both parameters are
omitted.
EXAMPLES
CPU32Bug>SD<CR> Switch to diagnostic directory
CPU32Diag>WR.W<CR> Prompts for address and data to which to
write word value.
CPU32Diag>WR.B 40FC E6<CR> Writes $E6 to $40FC
CPU32Diag>WR.W 800C 43F6<CR> Writes $43F6 to $800C
CPU32Diag>WR.L 54F0 F8432191<CR> Writes $F8432191 to $54F0
DIAGNOSTIC FIRMWARE GUIDE
M68CPU32BUG/D REV 1 6-1
CHAPTER 6
DIAGNOSTIC FIRMWARE GUIDE
6.1 INTRODUCTION
This diagnostic guide contains operation information for the CPU32Bug Diagnostic Firmware
Package, hereafter referred to as CPU32Diag. Paragraph 6.3 describes utilities available to the
user. Paragraphs 6.4 through 6.6 are guides to using each test.
6.2 DIAGNOSTIC MONITOR
The tests described herein are called via a common diagnostic monitor, hereafter called monitor.
This monitor is command-line driven and provides input/output facilities, command parsing,
error reporting, interrupt handling, and a multi-level directory.
6.2.1 Monitor Start-Up
At the CPU32Bug> prompt, enter SD to switch to the diagnostics directory. The Switch
Directories (SD) command is described elsewhere in this chapter. The prompt should now read
CPU32Diag>.
6.2.2 Command Entry and Directories
Enter commands at the CPU32Diag> prompt. The command name is entered before pressing the
carriage return <CR>. Multiple commands may be entered. If a command expects parameters
and another command is to follow it, separate the two with an exclamation point (!). For
instance, to execute the MT B command after the MT A command, the command line would read
MT A ! MT B. Spaces are not required but are shown here for legibility. Several commands may
be combined on one line.
Commands are listed in the diagnostic directory. Some commands have sub-commands which
are listed in the directory for that particular command (see example below).
CPU A
COMMAND
SUB-COMMAND
Fr
eescale S
emiconduct
or
, I
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
nc...