Table of Contents
Advertisement
B E N E F I T S
O F
F O R
S O F T W A R E
DevKit16 provides the same feature as high end emulator – application thinks,
that works with single chip and runs program in ROM or FLASH, but in fact the
program is running in Main board RAM in final address space under software
debugger control or as standalone.
This is possible using CPU simulated ports P0-P3 for application instead of
„native" ones. The MCU then can work in External Bus Mode and use all Main
board resources.
Non-single chip applications can benefit from large Main board RAM, FLASH
and use Prototype connector with prepared chip select, MCU bus signals.
The Main board logic also provides hardware breakpoints (in default version of
FPGA only one – please check DevKit16 WEB for FPGA upgrades) which
works for CPU External Bus Interface and provides break on read or write or
both accesses.
The argument, that this hardware breakpoint cannot include MCU RAM based
variables means minor limitation, because critical variables could be linked by
tools to appear in Main board RAM. Other limitation is that breakpoint uses
external interrupt line of CPU, which should run on top priority.
The software debugger kernel is started after reset (from Main board FLASH in
UMB) then RAM is swapped with FLASH, which means RAM appears on
UMB and FLASH with kernel in LMB. Then the application code can be
downloaded into Main board RAM (in UMB). The application is debugged at
addresses where it will burned.
Running the application in RAM immediately after reset (USW switch ON)
In Softune or Processor Expert
immediately after reset (so it behaves as it was burned in the FLASH). The
application runs from external RAM (in UMB) without debugging. To do this,
you should remove all breakpoints first. Then, start debug in your debugger
front-end to download application code into DevKit16. Set the USW switch to
„ON" and then press RESET button on the Main board.
Softune - Abort
When USW switch is OFF – using reset button will start monitor debugger in
LMB. The UKEY button is connected to the interrupt line 0 and can be used to
abort Softune monitor debugger session.
To be able to debug using debug kernel or Softune monitor, it must be burned in
FLASH using DevKit16 FLASH Programming tool. See chapter Flash it! for
more information about burning code into flash.
D E V K I T 1 6
D E B U G G I N G
(TM)
debug session, you can run your application
23
23
23
23
Advertisement
Table of Contents
