Echelon IzoT NodeBuilder - Manual (Page 215)

process will move on to the next target, rather than aborting the build.
Load after Build
Loads the application into a device immediately after the application
image is built. The devices must be commissioned with the IzoT
Commissioning tool and the LonMaker drawing containing the device
must be open and attached to the network. The Load After Build
button (
) on the NodeBuilder toolbar reflects changes to this option
and vice versa. This check box is selected by default.
Load NodeBuilder
Devices only Limits loads to the targets listed in the Devices folder in the Project
pane. This check box is selected by default.
Build Type
Determines whether All Targets (the default), Development Targets,
or Release Targets will be built when you build a project or device
template. You can also view and change the build type from the
NodeBuilder toolbar.
Verbose Make
messages
Displays more descriptive messages in the Results pane when you build
a device template. This check box is selected by default.
Debug make
Messages
Displays debugging messages in the Results pane when you build a
device template. This output may be used by Echelon Support to help
you diagnose problems. This check box is selected by default.
Generate Build
Script Files
Generates build script files when you build a device template. This
check box is cleared by default. Build scripts are described in Appendix
A, Using the NodeBuilder Command Line Project Make Facility.
3. Click OK.
Downloading an Application Image
You can download an application image that you have built with the IzoT NodeBuilder tool to a
L
ON W ORKS device. The device may be a development platform such as the FT 6000 EVB or an
LTM-10A Platform, a custom device that you have manufactured, or a third-party device. Typically,
you will do your initial debugging on a development platform before building a custom device, but you
can create and load a custom device at any time.
Development platforms such as the FT 6000 EVB and the LTM-10A Platform include Neuron
firmware that is preloaded into the device. The Neuron firmware allows these devices to be
downloaded over a L
ON W ORKS network so that you do not have to use any special device
programming tools. If you are using a development platform, you will automatically load the platform
when you add a NodeBuilder target as described in Adding and Managing Target Devices later in this
chapter.
If you are using a custom device that does not have an on-chip Neuron firmware image (similar to a
3150 Neuron Chip or 3150 Smart Transceiver), you must program the Neuron firmware image into the
external memory (EEPROM, flash, PROM, ROM, and so on) before you can use the device as a target.
Once you have completed development, you will load your application image into the device as part of
your manufacturing process. The files containing the application image are described in Building an
Application Image earlier in this chapter.
The following table summarizes the processor/memory combinations that you can use, and the files
that you will use to program each.
IzoT NodeBuilder FX User's Guide 201