Errors
V1 firmware reports errors through a hexadecimal error mask. Each bit corresponds to one product-supported error code. The list of possible errors depends on the product firmware.
Read the current error mask
Use err:
>> err
0
A reply of 0 means that no error is currently reported.
A non-zero value means that one or more error bits are set.
List supported errors
Use errlist to print the error names supported by the current firmware:
>> errlist
...
The order of the names corresponds to the error-bit order used by the firmware.
Clear errors
Use errclr with no argument to clear all currently set errors:
>> errclr
ffffffff
The command returns the mask that was requested for clearing. Use a hexadecimal argument to clear only selected bits:
>> errclr 4
4
Only clear an error after correcting the cause of the error. If the fault condition is still present, the error may be raised again.
Error mask
errmsk reads or writes the persistent error mask:
>> errmsk
ffffffff
>> errmsk ffffffff
ffffffff
Writing errmsk requires normal access. The value is saved by the UART configuration path.
Do not mask protection-related errors unless the consequences are fully understood for the connected system.
Command errors
Invalid command usage sets an error. Common causes are:
- unknown command;
- invalid number format;
- wrong number of arguments;
- write attempted without sufficient access mode;
- invalid EEPROM page or sequencer page;
- raw binary payload with the wrong length;
- buffer overflow or command received before the previous prompt was ready.
Last-error binary status
When supported by the product, logerr returns the binary status snapshot captured when an error was raised.
This is an advanced diagnostic feature. See Binary Status.
Sequencer errors
The sequencer sets command errors when it cannot load or execute a stored program. Common causes include an invalid line, invalid register, invalid page target, too many cached normal commands, zero-delay normal command, or a jump target outside the loaded program.
