Chapter
1:
R-Engine-D
1-6
Introduction
There is no ROM socket on the RE. The user’s application program must reside in SRAM for debugging in
STEP1, reside in battery-backed SRAM for the standalone field test in STEP2, and finally be programmed
into Flash for a complete product. For production, the user must produce an ACTF-downloadable HEX file
for the application, based on the DV-P Kit. The “STEP2” jumper (J2 pins 38-40) must be installed for
every production-version board.
Step 1 settings
In order to talk to
RD
with Paradigm C++, the
RD
must meet these requirements:
1) RE40_115.HEX must be pre-loaded into Flash starting address 0xfa000.
2) The SRAM installed must be large enough to hold your program.
For a 64 KW SRAM, the physical address is 0x00000-0x01ffff
For a 256 KW SRAM, the physical address is 0x00000-0x07ffff
3) The on-board EE must have a Jump Address for the RE40_115.HEX with starting address of 0xfa000.
4) The STEP2 jumper must be installed on J2 pins 38-40.
For further information on programming the R-Engine-D, refer to the Software chapter.
1.6
Minimum Requirements for RD System Development
1.6.1
Minimum Hardware Requirements
•
PC or PC-compatible computer with serial COMx port that supports 115,200 baud
•
R-Engine-D controller
•
PC-V25 serial cable (RS-232; DB9 connector for PC COM port and IDE 2x5 connector for controller)
•
center negative wall transformer (+9V, 500 mA)
1.6.2
Minimum Software Requirements
•
TERN EV-P Kit installation CD and a PC running: Windows 95/98/NT/2000/XP
With the EV-P Kit, you can program and debug the R-Engine-D in Step One and Step Two, but you cannot
run Step Three. In order to generate an application Flash file and complete a project, you will need the
Development Kit (DV-P Kit).