Neuron field compiler output – Echelon Neuron Field Compiler User Manual
Page 22

16
Using the Neuron Field Compiler
//
// Start the process
//
Process p = Process.Start(nca) {
//
// Read text from the process with StreamReader
//
StreamReader sr = p.StandardOutput {
string compilerOutput = sr.ReadToEnd();
// parse the compiler output here
// or display it:
Console.Write(compilerOutput);
}
}
}
}
Neuron Field Compiler Output
When you build your application, the Neuron Field Compiler creates application
image files and device interface files. The downloadable application image files
are used by network management tools to download the compiled application
image to a device. Other application image files are used for in-circuit or ex-
circuit programming of Neuron Chips or Smart Transceivers and non-volatile
memory devices. The device interface file describes the external interface for
your device. It is used by network tools such as the LonMaker
®
Integration tool
to determine how to bind and configure your device.
The location of the output files and folders is relative to the location of the
Neuron C source file. The Neuron Field Compiler creates a folder with the name
of the target (see the description of the --target switch in Command Usage on
page 12) in the folder that contains the Neuron C source file. This created folder
contains the log file (.log extension), the device interface files (.xif and .xfb
extensions), the linker map file (.map extension), and the application image files
(various extensions depending on the target hardware, including .apb, .ndl, .nei,
.nfi, .nme, .nmf, .nxe).
Important: The folder that contains the Neuron C source file must be writeable.
That is, the Neuron Field Compiler process must have permission to create,
modify, and delete files and folders in the location of the Neuron C source file.
The Neuron Field Compiler creates a number of hidden intermediate files that
are generally not needed after the build is complete, but can be useful for
program development and debugging. These files include the NodeBuilder
project file (.NbPrj), device template files (.NbDt), and other intermediate files.
These intermediate files are created within an IM subfolder that is deleted after
compilation successfully completes. You can use the --keep switch to ensure that
the IM subfolder and its contents are not deleted. To view these files within
Windows Explorer, you must show hidden files: open Folder Options in the
Windows Control Panel, select the View tab, and select the Show hidden files,
folders, and drives radio button.
Recommendation: Keep the files created in the IM subfolder when you need to
submit project files to Echelon Support for analysis. Your application can
support the keeping of these files by providing an optional method for specifying
the --keep switch when calling the Neuron Field Compiler.