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-16
DU Dump S-Records DU
3.9 DUMP S-RECORDS
DU [<port><del>]<range><del>[<text><del>][<addr>][<offset>] [;B|W|L]
The DU command outputs data from memory in the form of Motorola S-records to a port
specified by the user. If <port> is not specified then the S-records are sent to the I/O port (port 0).
For S-record information see Appendix A.
The option field is only allowed when <range> is specified using a count. In this case the B, W,
or L defines the size of data to which the count is referring. For example, a count of four with an
option of L would mean to move four longwords (or 16 bytes) to the new location. An error
results if an option field is specified without a count in the range.
Use the optional <text> field for incorporating text into the S0 header record of the block of
records that is to be dumped.
To use the optional <addr> field, enter an entry address for code contained in the block of
records. This address is incorporated into the address field of the block’s termination record. If no
entry address is entered then the address field of the termination record will contain the
beginning <range> address. The termination record is an S7, S8, or S9 record and depends upon
the entered address.
An optional offset may also be specified by the user in the <offset> field. The offset value is
added to the addresses of the memory locations being dumped. This generates the address which
is written to the address field of the S-records, creating an S-record file which is loaded back into
memory at a different location than that from which it was dumped. The default offset is zero.
NOTE
If an offset is specified but no entry address is specified then two
commas (indicating a missing field) must precede the offset to
keep it from being interpreted as an entry address.
EXAMPLES Dump memory from $8000 to $802F to port 1.
CPU32Bug>DU 1 8000 802F<CR>
Effective address: 00008000
Effective address: 0000802F
CPU32Bug>
DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-17
DU Dump S-Records DU
Dump 10 bytes of memory beginning at $3000 to terminal screen (port 0).
CPU32Bug>DU 3000:&10;B<CR>
Effective address: 00003000
Effective count : &10
S0003000FC
S10D3000000000040008000C00109A
S9030000FC
CPU32Bug>
Dump memory from $4000 to $402F to host (port 1). Specify a file name of ’’TEST’’ in the S0
header record and specify an entry point of $400A.
CPU32Bug>DU 1 4000 402F ’TEST’ 400A<CR>
Effective address: 00004000
Effective address: 0000402F
CPU32Bug>
The following example illustrates the procedure for uploading S-records to a host computer, in
this case an IBM-PC or compatible running MS-DOS with the ProComm terminal emulation
utility. Assume memory from $4000 to $4007 is initialized as follows:
CPU32Bug>MD 4000:4;DI<CR>
00004000 7001 MOVEQ.L #$1,D0
00004002 D089 ADD.L A1,D0
00004004 4A00 TST.B D0
00004006 4E75 RTS
CPU32Bug>
Enter the following command to dump S-records from memory locations $4000-$4007 with a
start address of $4000, a title of ’TEST.MX’, and an offset of $65000000. Before entering the
<CR> to send the DU command to CPU32Bug, enter the ProComm command <ALT-F1> keys
to open a log file. Enter the filename as TEST.MX. Then enter the carriage return, <CR> to
complete the DU command entry. The DU command output is sent to the screen and ProComm
copies it into the file TEST.MX.
CPU32Bug>DU 4000 4007 ’TEST.MX’ 4000 65000000<ALT-F1><CR>
Effective address: 00004000
Effective address: 00004007
S00A0000544553542E4D58E2
S30D650040007001D089A004E7576
S7056500400055
CPU32Bug>
Fr
eescale S
emiconduct
or
, I
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
nc...