Debugging (C-SPY)
4. C-SPY can download data into RAM, information, and Flash main memories. A warning message
is output if an attempt is made to download data outside of the device memory spaces.
5. C-SPY can debug applications that utilize interrupts and low power modes (see FAQ Debugging
#26 ).
6. C-SPY cannot access the device registers and memory while the device is running. C-SPY will
display "-" to indicate that a register/memory field is invalid. The user must stop the device to access
device registers and memory. Any displayed register/memory fields are then updated.
7. When C-SPY is started, the Flash memory is erased and the opened file is programmed in
accordance with the download options as set in Project → Options → FET Debugger → Download
Control. This initial erase and program operations can be disabled selecting Project → Options → FET
Debugger → Download Control → Suppress Download. Programming of the Flash can be initiated
manually with Emulator → Init New Device.
8. The parallel port designators (LPTx) have the following physical addresses: LPT1: 378h, LPT2:
278h, LPT3: 3BCh. The configuration of the parallel port (ECP, Compatible, Bidirectional, Normal) is
not significant; ECP seems to work well (see FAQ Debugging #1 for additional hints on solving
communication problems between C-SPY and the device).
9. C-SPY may assert RST/NMI to reset the device when C-SPY is started and when the device is
programmed. The device is also reset by the C-SPY RESET button, and when the device is manually
reprogrammed (Emulator → Init New Device), and when the JTAG is resynchronized (Emulator →
Resynchronize JTAG). When RST/NMI is not asserted (low), C-SPY sets the logic driving RST/NMI to
high-impedance, and RST/NMI is pulled high via a resistor on the PCB.
RST/NMI may get asserted and negated after power is applied when C-SPY is started. RST/NMI may
then get asserted and negated a second time after device initialization is complete.
Within C-SPY, Emulator → "Power on" Reset cycles the power to the target to generate a power-on
reset.
10. C-SPY can debug a device whose program reconfigures the function of the RST/NMI pin to
NMI.
11. The level of the XOUT/TCLK pin is undefined when C-SPY resets the device. The logic driving
XOUT/TCLK is set to high-impedance at all other times.
12. When making current measurements of the device, ensure that the JTAG control signals are
released (Emulator → Release JTAG on Go), otherwise the device will be powered by the signals on
the JTAG pins and the measurements will be erroneous (see FAQ Debugging #14 and Hardware #13 ).
13. Most C-SPY settings (breakpoints, etc.) are preserved between sessions.
14. When C-SPY has control of the device, the CPU is ON (i.e., it is not in low-power mode) regardless
of the settings of the low-power mode bits in the status register. Any low-power mode conditions will be
restored prior to Step or Go. Consequently, do not measure the power consumed by the device while
C-SPY has control of the device. Instead, run your application using Go with JTAG released (see FAQ
Debugging #12 and Hardware #13 ).
15. The View → Memory → Memory Fill dialog of C-SPY requires hexadecimal values for Starting
Address, Length, and Value to be preceded with "0x". Otherwise the values are interpreted as
decimal.
16. The Memory debug view of C-SPY (View → Memory) can be used to view the RAM, the information
memory, and the Flash main memory. The Memory utility of C-SPY can be used to modify the RAM;
the information memory and Flash main memory cannot be modified using the Memory utility.
The information memory and flash main memory can only be programmed when a project is opened
and the data is downloaded to the device, or when Emulator → Init New Device is selected.
17. C-SPY does not permit the individual segments of the information memory and the flash main
memory to be manipulated separately; consider the information memory to be one contiguous
memory, and the flash main memory to be a second contiguous memory.
18. The Memory window correctly displays the contents of memory where it is present. However, the
Memory window incorrectly displays the contents of memory where there is none present.
Memory should be used only in the address ranges specified by the device data sheet.
34 Frequently Asked Questions SLAU138F – June 2004 – Revised March 2007
Submit Documentation Feedback
To Next Page
Loading...
Need help?
General
