Echelon Neuron - Manual (Page 68)

60 Neuron C Compiler Errors (NCC)
NCC# Description
126 Bad I/O modifier for this I/O object type [NCC#126]
Several of the I/O object declarations permit or require modifiers, like mux,
ded, sync, and so on. These are permitted or required on a per I/O object-
type basis. At most one of each type of modifier is permitted in a single
declaration.
127 Duplicate I/O object modifier not allowed [NCC#127]
Several of the I/O object declarations permit or require modifiers, like mux,
ded, sync, and so on. These are permitted or required on a per I/O object-
type basis. At most one of each type of modifier is permitted in a single
declaration.
128 I/O object type cannot have an initial-pin-level [NCC#128]
Most output object types permit specification of an initial pin-level value to
be assumed by the pin on power up or chip reset, until the application
program takes over. However, the I/O object for which this message is
being output does not permit an initial pin level.
129
130
131
Initial-pin level must be in range 0...255 [NCC#129]
Initial-pin level must be in range 0...15 [NCC#130]
Initial-pin level must be 0 or 1 [NCC#131]
Most output object types permit specification of an initial pin-level value to
be assumed by the pin on power up or chip reset, until the application
program takes over. All single-pin initial levels must be either 0 or 1. The
nibble I/O object type, which uses four consecutive pins, can have initial
values from 0 to 15, with the values being mapped as a binary number onto
the four pins. Likewise, the byte I/O object type can have initial values
from 0 to 255.
132 Unacceptable function return type [NCC#132]
A function in Neuron C cannot return an object that is a struct or union
type, nor can it return an array type. However, a function
can return
pointers to such objects.
133 Explicit addressing requires inclusion of <msg_addr.h> [NCC#133]
An attempt to use the msg_out.dest_addr field or the msg_in.addr field has
been detected, but cannot be compiled because the include file
<msg_addr.h> was not included by the programmer. Note that the include
directive must appear prior to the first such field reference. The include
file is not needed for references to other fields of the msg_out or msg_in
objects.