CAN-Engine
Chapter 4: Software
4-19
Supported #define values included:
TERN_186
186-based A- boards (EE, C-Eye included)
TERN_ST
For the Smart-TFT, this must be explicitly defined.
TERN_ST_MMC
A version of the ST w/ MM-C expansion board.
TERN_RE
All other 186-based boards (RE, RL, RD, RA, RB) when used with an expansion board.
TERN_RD
For the R-Drive, this macros MUST be explicitly defined.
TERN_RL
For the R-Engine-L, this macros MUST be explicitly defined.
TERN_586
586-based boards, 5E or 5P that relies on expansion module (either P51 or MMC) for
I2CHIP Ethernet. These are accessed through I/O mode only (I2CHIP_WINDOW_IO).
TERN_5E
This must be explicitly defined for the 586-Engine boards. It would
indicate custom-mapping for the 5E hardware (typically requiring
added wires for J4).
TERN_5P
This must be explicitly defined for the 586-Engine-P board.
TERN_5E
This must be explicitly defined for the 586-Drive controller.
TERN_P51
Indicates P51 expansion board and 'windowed' access to the memory mapped module;
another macros also needed to indicate the Engine architecture you're working with.
I2CHIP_MMC
Indicates MMC expansion board and also 'windowed' access to module; for the MM-C,
make sure 'i2chip\mmc.c' is also included in your project.
Note: defining TERN_MMC and I2CHIP_MMC have different meaning in the
httpd_fs
sample code (using CompactFlash filesystem).
I2CHIP_MMC
Indicates we should be using MM-C for I2CHIP/Ethernet
capability.
TERN_MMC
Indicates we should also be using MM-C for filesystem
TERN_SC
TERN_RL
For the SensorCore/R-Engine-L controllers, implying a direct mapping at 0x80000 with
'even byte' only shifted addressing.
TERN_CEYE
TERN_EE
For the EE/CEye controller, implying direct mapping at 0x80000 (if no expansion board
used).
The TERN SCA also fits in this category; define TERN_EE when working with the
TERN SCA.