1-4 NodeBuilder Debugger Errors (DBG)
DBG# Description
28
Communication with device timed out before a response
was received
This will intermittent if it occurs. Usually no harm would be
done. Breakpoints might not work as expected. Might need to
re-start the debugger.
29 Bad format found when reading [debug] NXE [DBG#29]
This would normally never happen. The file might be corrupt;
possibly it was hand-edited.
30
Operation on a dbgSymbol requires a dbgValue type
[DBG#30]
Used during development.
31
dbgValue operation requested on symbol that is out of
context, e.g. a local variable in a routine that is not in
the current calling sequence [DBG#31]
Should restart the debugger. Did the stacks crash?
32 Cannot read/write timers while running [DBG#32]
The application and the debugger do not agree on what state
the debugger is in. Should restart the debugger.
33 Cannot write this dbgValue [DBG#33]
Possibly the value is in read-only memory.
34 No remote procedure calls while running [DBG#34]
35
Not enough memory in debug kernel to pass RPC
parameters [DBG#35]
Remote procedure call is not supported.
36 Not enough Neuron stack space left for RPC [DBG#36]
Remote procedure call is not supported.
37 Cannot add to list, limit reached [DBG#37]
Resource allocation problem. Probably a program error.
38
Can only watch network variables and variable symbol
types [DBG#38]
39 Cannot debug a read/write protected device [DBG#39]
NodeBuilder debugger modifies program memory when it sets
breakpoints.
40
dbgSymUser and dbgRawMemory cannot refer to a
memory area that is not in the Neuron memory map
[DBG#40]
41
dbgSymUser and dbgRawMemory define read/write
blocks within memory. These blocks must completely
reside within one memory area. Areas include: ROM,
onchip EEPROM, offchip EEPROM, onchip RAM, offchip
RAM and memory mapped I/O. Different memory areas
have different read/write capabilities, etc. [DBG#41]
