Specifications

PL 3120/PL 3150/PL 3170 Power Line Smart Transceiver Data Book 35
Upon detecting a checksum error, the reset process will force the appropriate state and log an error in the error log. For
the PL 3150 Smart Transceiver, a checksum must fail twice during reset processing in order for it to be deemed bad.
Reboot and Integrity Options Word
A PL 3150 Smart Transceiver has a number of options for actions taken following a checksum error or other memory
related fatal errors. The 16-bit word that controls these options resides in the system image and is defined as part of the
device’s export options in the NodeBuilder or Mini EVK tools.
The recovery process relies on the fact that the initial on-chip EEPROM image for the application, configuration, and
communication parameter data reside in the off-chip system image. During initial power up, the system image data is
copied (booted) to on-chip EEPROM. The recovery process recopies or reboots the suspect areas as dictated by the error
and the recovery options. Any changes made to the on-chip EEPROM (e.g., a network application load or network
tool initiated reconfiguration) after the initial boot are lost in the recovery process. The recovery action is defined
by setting a combination of bits as defined by the following bit masks (Table 2.12).
Table 2.12 Recovery Action Bit Masks
Recovery Word Description
0x0001 Reboot application if application fatal error.
0x0002 Always reboot application on reset (see note).
0x0004 Reboot configuration if configuration checksum fails.
0x0008 Reboot configuration on an application fatal error.
0x0010 Always reboot configuration on reset.
0x0020 Reboot communication parameters if configuration checksum fails.
0x0040 Reboot communication parameters if type or rate mismatch.
0x0080 Always reboot communication parameters on reset.
0x0100 Reboot EEPROM variables when rebooting application.
0x0200 Applicationless state is considered to be an application fatal error. If
option 0x0001 or 0x0008 is set, applicationless state will result in a
reboot. Application fatal errors are defined below (see note).
0x0400 Checksum all code, including system image.
Note: Applications exported with these options cannot be loaded over the network.
In the above options, “configuration” does not include the communication parameters because their recovery is
governed separately. Also, fatal application errors refer to application image checksum errors, memory allocation
failures, and memory map failures. Refer to Loading an Application Image in the NodeBuilder User’s Guide (Release 3
Revision 2 or later) for more information.
The configuration will be rebooted independently of the application only if all the configuration table sizes match
between EEPROM and ROM. This avoids a situation where a new application with different table sizes is loaded over
the network, and a reboot of the configuration corrupts the program.
When an EEPROM recovery occurs due to a checksum failure or other error, the event will be logged in the error table
of the Smart Transceiver. A test command will show EEPROM recovery occurred as the last error logged.