
79
11.2 Diagnostics
When an error dialog is displayed, diagnostic information is added to the Output Window.
In the following example, I added the line 7FF0..7FFF to the 'External RAM' box in Settings>Memory.
Now this area of memory is unimplemented on my system, so trying to use the Fill Memory command
will fail:
F 7FF0 7FF0 12
produces:
Echo error writing RAM
Addr 7FF0 Sent 12 Rcvd BE
State:Stopped
Reboot MCU? = No
The constants in the information above are:
Addr Address of byte at which the echo occurred. In the case of a Comms error writing the
CPU inherent registers, an address as such is meaningless, and will always be zero.
Sent Byte sent from the PC to the monitor firmware (MON08)
Rcvd Byte as echoed by the monitor firmware (MON08)
State: The information in the left-hand panel of the status line.
The line 'Resett MCU? = Yes|No' will only appear when the remote reset option is in use.
11.3 Error Report
Use this dialog (open in Help menu) to prepare a plain text report if you need to send information by
email with a request for support. Fill in the edit boxes as you feel necessary, then press 'Make Text
File...' This will make a plain text file called something like ErrRpt_20060706_1820.txt, or whatever
is the current date and time. Then send it to me at john.beatty@virgin.net
11.4 Command Line Errors
These are the error messages generated by Xplor8 when it cannot carry out a command. They appear
in the Command History box, following a command in error and beginning with the symbol '<--'.
From the right-click context menu in the Command History Window you can call up the relevant help
topic on one of these errors. For a printable list of all the command line errors, see Appendix E of the
Manual.
Kommentare zu diesen Handbüchern