ELS Messages for High Speed Serial Interface (HSSI)

HSSI.001

Level:
C-INFO
Short Syntax:
HSSI.001 Modem status change DSR(CA)= dsr , LC = lc , dev device name
Long Syntax:
HSSI.001 Modem status change DSR(CA) = dsr , LC = lc , on device device name
Description:
A modem status change has occurred. The present state is described. testing, as initiated from the remote end.

HSSI.002

Level:
ALWAYS
Short Syntax:
HSSI.002 PUD/DL sts (0x Status ), dev device name
Long Syntax:
HSSI.002 Power-Up Diagnostics and/or download failed with status 0x Status , on device device name
Description:
Selftest of the device includes a stage of fetching the power-up diagnostics and downloading the card. If either failed, the device will not operate correctly, and disables itself.
Cause:
status = 8000 There's already an unacknowledged request to the card.
Cause:
status = 8602 The driver state is inappropriate for downloading.
Cause:
status = 8102 The device wasn't present at restart.
Cause:
status = 8402 The driver didn't recognize the Common MAC-layer request.
Action:
The device should disable itself; call Proteon Customer Service.
Cause:
status = 8902 Command flushed, as part of selftest or initialization.
Action:
The device should recover by itself.
Cause:
status = 8C04 ROM indicates that the download address is out of range.
Cause:
status = 8A04 ROM indicates that the download buffer is too long.
Cause:
status = 8804 ROM indicates that the download checksum is wrong.
Cause:
status = 8404 ROM indicates that the start address is out of range.
Cause:
status = 8504 ROM doesn't recognize the request.
Cause:
status = 8F04 ROM doesn't recognize the request.
Action:
The device should disable itself; call Proteon Customer Service.
Cause:
status = 8502 Download firmware doesn't like its configuration.
Action:
Consider reducing the MTU size. Not good. Get a dump.

HSSI.003

Level:
ALWAYS
Short Syntax:
HSSI.003 Bad cnfg sts = 0x Status , dev device name
Long Syntax:
HSSI.003 Configuration was rejected by the downloaded firmware with status 0x Status , on device device name
Description:
After download, the card is told it's configuration: PDU size, CRC size, receive and transmit queue lengths, receive offset, and transmit delay. The downloaded firmware has rejected it. The device will disable itself.
Action:
Call proteon Customer Service. the router software disagree on what should work. Get a dump.

HSSI.004

Level:
C-INFO
Short Syntax:
HSSI.004 PUD/DL ok, dev device name
Long Syntax:
HSSI.004 Power-Up Diagnostics and firmware DownLoad successful for device device name
Description:
The HSSI smartcard runs power-up diagnostics and then is downloaded with the operational firmware. If this works okay, the card is then configured, and enabled.

HSSI.005

Level:
ALWAYS
Short Syntax:
HSSI.005 Enbl Tx/Rx failed sts 0x Status , dev device name
Long Syntax:
HSSI.005 The command enabling receive and the transmit failed with a status of 0x Status , on device device name
Description:
One of the final steps of initializing the device card is to tell the downloaded firmware to enable the transmitter and receiver. This command did not complete successfully. The device should automatically disable itself. See HSSI_2 for an interpretation of the status codes.
Action:
Restarting the router may clear this condition. If any case, contact Proteon Customer Service. the firmware.

HSSI.006

Level:
ALWAYS
Short Syntax:
HSSI.006 ROM diags err 0x errorcode , dev device name
Long Syntax:
HSSI.006 ROM diagnostics monitor reports a request in error 0x errorcode on device device name
Description:
The device driver has called up to the common MAC layer reporting a mailbox message which the driver can't deal with directly.
Cause:
The driver has received a message from the device card indicating that either the card is in an odd state (e.g. in the ROM diagnostics when it should have been running download software), or that the which it couldn't perform.
Action:
Contact Customer Service. The router should automatically attempt to re-start the card.

HSSI.007

Level:
ALWAYS
Short Syntax:
HSSI.007 Flush timeout, dev device name
Long Syntax:
HSSI.007 Flush (driver device initialization) failed to complete in a reasonable time on device device name
Description:
Flush timeout arises when the driver tries to initialize the software device to the device card (flush the transmit and control queues), and the card doesn't respond fast enough.
Cause:
The downloaded firmware is in an infinite loop, or the card is broken.
Action:
Contact Customer Service. The router will try to automatically recover by resetting the device and attempting to retrieve diagnostics and download the firmware again. If this error recurs frequently, disable the device pending a Customer Service solution.

HSSI.008

Level:
ALWAYS
Short Syntax:
HSSI.008 FW crsh dev device name
Long Syntax:
HSSI.008 Firmware crash on device device name
Description:
The downloaded firmware has encountered an unrecoverable error, and exited to the diagnostics monitor. The device will disable itself.
Cause:
This is most likely a software error.
Action:
Contact Customer Service.

HSSI.009

Level:
ALWAYS
Short Syntax:
HSSI.009 PUD failed (0x Status ) dev device name
Long Syntax:
HSSI.009 Power-Up Diagnostics failed (0x Status ) on device device name
Description:
Power-Up diagnostics tests indicate that the device card is not operational. Software should disable the device.
Action:
Call customer service. This is most likely a hardware failure.

HSSI.010

Level:
CI-ERROR
Short Syntax:
HSSI.010 No bfr avl int rst dev device name
Long Syntax:
HSSI.010 No buffer available for hard reset of device device name
Description:
A packet buffer was not available when the software was trying to reset the device hardware. Some severe error has been detected which can only be handled by resetting the card, and downloading the code again. A buffer is required to initiate this process. Software will keep trying to obtain one periodically.

HSSI.011

Level:
UE-ERROR
Short Syntax:
HSSI.011 No bfr avl Request dev device name
Long Syntax:
HSSI.011 No buffer available for Request on device device name
Description:
A packet buffer was not available when the software was trying to send the indicated request to the driver. This isn't too serious, but may result in occasionally anomalous behavior.
Cause:
LINE UP LED: the state of this LED may not accurately reflect the link state.
Cause:
DSS NOTIFY: Modem signals changes may not be accurately reported to the link layer protocol.
Cause:
SET DSS: the modem control signals may not be set as required by the link layer.

HSSI.012

Level:
UE-ERROR
Short Syntax:
HSSI.012 No heap mem for MAC dev device name
Long Syntax:
HSSI.012 There isn't enough heap memory to allocate the MAC-layer structure required for device device name
Description:
The common physical layer (MAC) requires some heap memory to maintain its state, and couldn't obtain it. The device should disable itself.
Action:
Minimize the size of routing tables, and other (potentially) large data structures controlled by configuration paramaters. If the error persists, contact Customer Service.

HSSI.013

Level:
ALWAYS
Short Syntax:
HSSI.013 Card bad/not prsnt dev device name
Long Syntax:
HSSI.013 The card is of the wrong type, or inoperative for device device name
Description:
Upon restart of the router, or a crash of the card firmware, the router waits a little bit, and then tries to access the card. Either the card didn't respond, or it responded with an incorrect module ID. The router software automatically disables the device.
Action:
Make sure the card is correctly seated in its slot, and RESTART the router. if this message persists, call Proteon Customer Service.

HSSI.014

Level:
ALWAYS
Short Syntax:
HSSI.014 Card download/config ( state ) timeout dev device name
Long Syntax:
HSSI.014 Download or configuration ( state ) of the card took too long for device device name
Description:
After determining that the card exists, the first thing the driver does is try to download it and configure it. If this takes too long, the device is disabled. Call Proteon Customer Service.
Cause:
Damaged card or defective ROM.
Action:
replace the card.
Cause:
Download firmware has been trashed (the downloaded formware is the entity to which the configuration is passed).
Action:
Reload the router.

HSSI.015

Level:
ALWAYS
Short Syntax:
HSSI.015 Flush incomplete: TxQ not empty, dev device name
Long Syntax:
HSSI.015 The firmware has acknowledged a flush request but has not released the Transmit buffers queued to it on device device name
Description:
When the driver tries to initialize the software device to the device card (flush the transmit and control queues), and while the firmware acknowledges the request, it doesn't release the transmit buffers.
Cause:
The firmware and the driver are out of synchronization.
Action:
Contact Customer Service. The router will try to automatically recover by resetting the device and attempting to retrieve diagnostics and download the firmware again. If this error recurs frequently, disable the device pending a Customer Service solution. can't get the firmware state). This probably has to be recreated in the lab where a debugger, ICE and/or logic analyzer is available: get a detailed configuration, put a breakpoint at hsml_aev() and get a dump, and try to get a traffic profile.

HSSI.016

Level:
ALWAYS
Short Syntax:
HSSI.016 Null cmd (0x command ) cmp, dev device name
Long Syntax:
HSSI.016 The firmware has responded to a command (0x command ) for which the driver has no current record, on device device name
Description:
Commands are sent one-at-a-time from the driver to the firmware and separately acknowledged by the firmware. In this case, the firmware has indicated a command status to the driver when the driver doesn't have a record of an unprocessed command.
Cause:
This indicates a mis-synchronization between the firmware and the driver, and probably a bug.
Action:
Contact Customer Service. The router ignore the event.If this error recurs frequently, disable the device pending a Customer Service solution. can't get the firmware state). This probably has to be recreated in the lab where a debugger, ICE and/or logic analyzer is available: get a detailed configuration, put a breakpoint at hsml_aev() and get a dump, and try to get a traffic profile.

HSSI.017

Level:
UE_ERROR
Short Syntax:
HSSI.017 Bad cmd sts (0x status ) dev device name
Long Syntax:
HSSI.017 The firmware has responded to a command with an unrecognized status (0x status ), on device device name
Description:
The firmware has responded to a command from the driver with an unrecognized status.
Cause:
This may indicate a mis-synchronization between the firmware and the driver, or a load image build error (the wrong version of firmware was downloaded to the card). It probably indicates a bug.
Action:
Contact Customer Service. The router will attempt to recover automatically (restarting the device) or choose to disable the device. If this error recurs frequently, disable the device pending a Customer Service solution. can't get the firmware state). This probably has to be recreated in the lab where a debugger, ICE and/or logic analyzer is available: get a detailed configuration, put a breakpoint at hsml_aev() and get a dump, and try to get a traffic profile.

HSSI.018

Level:
U-TRACE
Short Syntax:
HSSI.018 st slftst dev device name
Long Syntax:
HSSI.018 start selftest device device name
Description:
Self-test is being started on the HSSI device.
Panic
hssinohp
Short Syntax:
HSSI: MAC struct no heap
Description:
The router lacks sufficient heap memory to allocate the common handler layer data structure.
Action:
Minimize the size of routing tables, and other (potentially) large data structures controlled by configuration paaramaters. If the error persists contact Customer Service.