Table of Contents
Advertisement
4.3.4 Resetting the EZ-KIT Lite Board
The EZ-KIT Lite board can be reset with the push button switch on the board or with the Debug -
> Reset command in the debugger menu bar. Both resets, clear and reset the chips memory and
debug information so there will be a need to reload any programs that were running. The Debug -
> Restart command resets the processor, however, the processor retains all debug information
and memory contents.
•
The following sequence must be used when starting the debugger:
1.
Start the debugger from the windows Start menu. Start -> Programs ->
VisualDSP -> Debugger
2.
The debugger starts and the Target message Hit Reset Button appears
3.
Press the Reset button on the board.
4.
Wait approximately three seconds for the LED's (except power and FLAG9) to turn
off.
5.
Click OK. The message Communications Success appears.
•
Do not use the reset button while the debugger is open unless the debugger requests you to
press it.
•
While the user may load several programs into the debugger during a single debug session
without resetting the EZ-KIT Lite board, it is recommended to reset the board prior to loading
a new program.
4.4 Benchmarking Utilities
An evaluation platform needs to report an accurate cycle count in order for you to develop efficient DSP
programs. Because the monitor program running on the EZ-KIT Lite board is intrusive, the debugger's
cycle counter (located in the status bar) does not work. To get an accurate cycle count, the EZ-KIT Lite
comes with a set of benchmarking utilities. These utilities come in both C and assembly code types. Use
the following procedures to enable accurate cycle counting of any DSP program.
In C, embed the count_start and count_end functions in your code. The count_start is a function
that returns an initial starting value of the current cycle counter. The user then uses this value as an
argument to the count_end function. The count_end function returns the total number of elapsed cycles
between count_start and count_end. These functions are a completely self contained, so the user
does not need to save or restore any processor registers. The following is an example of how to write these
functions into your existing code.
www.BDTIC.com/ADI
36
Advertisement
Table of Contents
