No subject

- The usual level of support, adequate for typical debugging
of applications software, is OCDS1 via the wiggler.  This
level of support provides the usual capabilities of halt, go,
breakpoints, triggers, examination of registers, memory, etc.

- If we do not want to add the rather large DB25 connector
and the associated circuitry for a wiggler type connection
on our in-house developed MIB board, then we will need an 
emulator to perform downloads, and connect to debugger 
software via the 16 pin header.  (True, ethernet will be 
available at some point to handle downloads, but that 
capability may not be available initially, and it will 
not support debuggers.)  Inclusion of the wiggler 
would substantially increase the board size.

- It may be desirable to purchase at least one trace execution 
module ($3.5K to $5.5K) and an OCDS2 software debugger (~ $1K).  
These components could be supplied to ATI for their use during 
the rtos port and development of the ethernet driver, and then 
returned to us for our use during the development of applications 
software. 

- We will probably want to include the 60 pin OCDS2 connector
on our in-house developed MIB board.

In general, the emulators and trace execution modules, with
compatible debuggers seem oriented toward lower level debugging,
even bare board sans operating system.  However, the debuggers
do include C & C++ support, and many/most are compatible with 
the TASKING compilers.

I still have several questions outstanding on downloads of 
binaries and OCDS1 support for the Solaris & Linux versions
of the TASKING toolset.  It is unclear at this time if those
versions of the toolset support even binary downloads or
require a 3rd party solution for downloads and debugging.

When pressed, one of the emulator vendors admitted that they
do have drivers for the TASKING debugger, so we could use
the emulator with the TASKING debugger, but trace execution
would not be a possibility with that configuration.