README.TXT Driver File Contents (a2-3dev_02.zip)

Customizing PDREMOTE/ROM
========================
With the Paradigm C++ PDREMOTE/ROM Wizard, there is not to much you have to do
to get a nearly working PDREMOTE/ROM debug kernel ready foryour target system.

In order help you identify the files that you may need to modify, the wizard
created a SourcePool containing the files you will need to consider changing
to adjust to your unique target hardware.


DCOMMS.C
========
This is the target dependent serial interface code and has some defines that
might need to be changed.  If you are using a processor with an internal serial
port, then you will have options to select the port (if there is more than one),
the baud rate, and the crystal osciallator frequency (which is usually needed
to calculate a baud rate divisor).

If you have an external serial port, then usually we will need to know the
starting port address and the bus width to be able to use the port.

The default behavior of the remote kernel will be setup in this source.
Please look for the variable BAUD to define the communication baudrate
setting and COMMINT for interrupt controlled mode.

TARGET.H
========
This files does not need to modified until you are ready to create an interrupt-
driven version of PDREMOTE/ROM.  Change the code so that the macro COMMINT is
defined to the serial interrupt and test the results.

A polled-mode PDREMOTE/ROM is the default and often better suited for debugging
interrutp handlers since messing up the interrupts will not affect the oper-
ation of PDREMOTE/ROM.

An interrupt-driven version of PDREMOTE/ROM will allow you to break into your
application from the debugger so choose the debug kernel most suited to the
debugging task.


TARGET.C
========
This is another optional file that you can customize once PDREMOTE/ROM is up
and running on your target hardware.  The key functions you may considering
customizing at some point are:

   USERreset() setup
   =================
   This function should be customized to disable any active interrupts that an
   application might have enabled so that the interrupt vector table can be
   re-initialized.  While we have already done this for some builds, it is not
   possible to do this for all targets so check this out and make sure it is
   compatible with your target system.

   USERpdrementer()/USERpdremexit()
   ================================
   Edit these functions to disable and restore interrupts while in the
   PDREMOTE/ROM kernel.

   USERdisable()/USERenable()
   ==========================
   Edit these functions to prevent the stepping into an interrupt hanlder.
   Various Intel and AMD processors have different priorities for simultaneous
   interrupts and if you find yourself stepping into an interrupt handler, this
   is the code you will want to use to prevent this.


HELPERS.C
=========
Normally you won't need to include this file in your PDREMOTE/ROM build but
there is one case you will definitely want to use this file.  If you have a
16-bit EPROM emulator and your EPROMs do not support byte writes, you will want
to enable word write support in PDREMOTE/ROM.  This is done by adding the define
'__PDREM_WORDWRITE' as a node override for this file.

If you have not done so, please review the PDREMOTE/ROM manual found in the
DOCS directory and the PDREMOTE/ROM help topics.

Thanks and best regards.

Paradigm Technical Support Staff
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 1.00