Echelon Neuron C - Manual (Page 241)

Neuron C Programmer’s Guide 229
BFT5000 - Firmware incorporated into a Neuron 5000 Processor or
an FT 5000 Smart Transceiver.
SYS3150 - For all devices using a Neuron 3150 Chip or FT 3150
Smart Transceiver.
SYS3150A - For all devices using a PL 3150 Smart Transceiver.
SYS3150C - For all devices using an FT 3150 Smart Transceiver.
SYS3150D - For all devices using a PL 3150 Smart Transceiver.
System image A system image is a set of files that contain the Neuron
firmware needed to operate a Neuron Chip or Smart
Transceiver and implement the LonTalk protocol. The
software in the image is a pre-linked executable. It must
not contain any external references.
NodeBuilder Use of Custom System Images
For Series 3100 devices, you can use the NodeBuilder Neuron C compiler,
assembler, and librarian to construct a custom system image as described in
Constructing a Custom System Image on page 231. You can then use this custom
system image within a NodeBuilder device template to construct application
programs using the NodeBuilder project manager.
Important: Custom system images are not supported for Series 5000 devices.
The NodeBuilder project manager does not detect when a custom system image
needs to be rebuilt due to changes in the source files that make up the custom
system image. When you construct custom system images, you should use
standard software engineering techniques to manage your software baseline and
insure that current versions of your software are being used. Use of a third-party
make program can help in managing software dependencies.
The NodeBuilder project manager can use a custom system image in much the
same way as it handles the standard system images. The NodeBuilder project
manager does full dependency checking on the use of custom system images.
When you modify a custom system image, the NodeBuilder project manager
automatically detects this condition and re-links the program for the device when
you invoke the build function.
See the NodeBuilder FX User's Guide and the NodeBuilder Online Help for
details about choosing the firmware image to be used for a device target, and for
details about using custom firmware images.
Following are guidelines for using custom system images with the NodeBuilder
tool:
1 Re-program any custom device PROMs using a custom system image
when you generate a new version of the custom system image. If you do
not re-program the PROMs, inconsistencies between the PROM version of
the system image and the NodeBuilder version can cause the device’s
program to fail in odd ways—often with a watchdog timer timeout or
other diagnostic failure.
2 You must keep the set of files that comprise a system image together.
For example, keep all the system image files together when you copy
them to the appropriate Ver nnn directory. When updating system image
files, ensure that all files in the set are updated together. Failure to do so
can result in errors similar to those mentioned above. The set of files