Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Portable Device Debug Framework Using Java

IP.com Disclosure Number: IPCOM000123881D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 1 page(s) / 66K

Publishing Venue

IBM

Related People

Slane, AA: AUTHOR

Abstract

A portable device debugger framework written in Java was developed to ease developers support and education workload and ease device user's ramp-up time for using the device. The framework consists of a graphical user interface (GUI) that is platform independent and driven by user-defined macro files. The macro files define how a macro window should look like, what fields to display, and how to get the data for the fields. There is a mechanism to build new macro windows, so users can build windows that they think are useful in their environment. A base set of macros are provided to debug basic problems.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Portable Device Debug Framework Using Java

   A portable device debugger framework written in Java was
developed to ease developers support and education workload and ease
device user's ramp-up time for using the device.  The framework
consists of a graphical user interface (GUI) that is platform
independent and driven by user-defined macro files.  The macro files
define how a macro window should look like, what fields to display,
and how to get the data for the fields.  There is a mechanism to
build new macro windows, so users can build windows that they think
are useful in their environment.  A base set of macros are provided
to debug basic problems.

   Another part of the GUI/debugger is the inclusion of built
in routines that can be executed from menus.  For example, one
routine exists to create a register dump file, and other routines
exist to dump memory and memory regions.  These files can later be
reloaded into the debugger in place of an actual device.  This
allows dump files to be sent to the device development team, and
then loaded into the debugger on the developer's desk.  Another
example routine is the ability to determine the memory map being
used and check it for common user configuration errors.  These error
checking routines are very useful when users are writing new
drivers.  Because the framework is written in Java, users can write
new routines and have them dynamically loaded into the environment.

   The GUI sits on top of a Device object.  This object
provides the basic interface to get registers and memory from the
device.  This interface allows the GUI to operate with no knowledge
of the underlying device driver.  There are a number of different
De...