1. a2-3dev_02.zip Driver
2. readme.txt File Contents

readme.txt Driver File Contents (a2-3dev_02.zip)

Congratulations for ordering the Paradigm C++ Integrated Development Environment

It is very useful for Paradigm C++ integrated debugger users to know 
about how the debugger and PDREMOTE interact with your application program. 
For users who are interested, we'll give a primer here. The application 
program being debugged is not "linked" to the PDREMOTE/ROM monitor program 
(the optional kernel interface is an exception to this). The application 
being debugged is linked to the Paradigm startup code and library support 
files as similarly to if it were going into EPROM, but it is located in the 
RAM area of your target system and usually has no INITCODE directives. Most 
of the Paradigm C++ example programs have a LOCATE configuration file that 
checks to see if the PDREMOTE/ROM is defined. This happens when building a 
project with PDREMOTE/ROM as the remote connection. 

When PDREMOTE/ROM is defined no reset vector or INITCODE is added to the 
application since the kernel will be running and handles all of the target 
boards peripherals. When No TARGET/ROM is selected, then the IDE will use 
the alternate path in the LOCATE configuration file add a reset vector, chip 
selects etc. The Paradigm C++ example files in \examples are a tremendous 
resource that will greatly speed your transition to effectively using Paradigm C++.

The PDREM[x].HEX included on this disk is a ready configured PDREMOTE/ROM monitor 
for the A2D-3. The PDREM4.HEX is installed on the A2D-3 as ready to go 
application. These PDREMOTE build is configured to autodetect the Baudrate of
the Debugger (range 9600..115200). Please configure the serial connection of the PDREMOTE/ROM inside the IDE with the same parameter range. (Context Menu *.AXE 
Node or TargetExport) Please check the connection to the PDREMOTE/ROM monitor 
with the RTTEST utility. Optional you can use the PDREMOTE/ROM in a slower 
communication mode if there are some communication problems occurs. 
The PDREM2.HEX additionally can be used to debug application through the 
serial port COM2.You should disable all code in your application that change any parameter of the COM2 during debug session. 
Please note that there are some problems using this RTTEST utility inside a 
window DOS box with higher speeds. Please refer the A2-3PRG12.PDF for the 
download commands. To use a different baudrate of the unit you should repower 
the A2(D)-3 and change the serial communication parameters inside the IDE 
depending your requirments.

Thanks and best regards.

Falcom Technical Support Staff