|
|
|
|
Displays uart information as follows:
|
|
| Uart: Datalink (Open), Rx 13/255, Tx 7/255
Uart: Parity Errors=0, Dirty Bits=0, Framing Error=0
Uart: Firmware Overruns=0, Transmit Overruns=0, Receive Overruns=0
Uart: Monitor (Open), Rx 1/255, Tx 255/255
Uart: Dirty Bits=0, Firmware Overruns=0, Hardware Overruns=0 |
|
| The uart state will be one of the following:
|
|
|
|
|
| The uart subsystem buffers all received characters in the receive buffer. The count and size of the receive buffer determines the maximum usage of the receive buffer. The maximum usage of the receive buffer will typically be only a few characters. If the maximum usage of the receive buffer approaches 100%, then the firmware isn't processing received characters efficiently.
|
|
| The uart subsystem buffers all transmitted characters in the transmit buffer. The count and size of the transmit buffer determines the maximum usage of the transmit buffer. The maximum usage of the transmit buffer will typically be 100%. This indicates that the firmware can generate transmit characters faster than the hardware can transmit characters.
|
|
| The dirty bits indicates the number of received bits for which the bit samples had to be deciphered using a voting algorithm. For example, if the bit samples are 1111 or 0000, the received bit is clean. However if the bits samples are 1101 or 0100, the received bit is dirty.
|
|
| The firmware overruns indicates the number of received characters that had to be discarded to prevent receive buffer overflows. The hardware successfully received the characters, but the firmware isn't processing received characters efficiently.
|
|
| On the datalink port only, the parity errors indicates the number of received characters for which there was a parity error. Occasional parity errors can be ignored; but frequent parity errors indicate a problem with the communication link.
|
|
| On the datalink port only, the framing errors indicates the number of received characters for which there was a framing error. Occasional framing errors can be ignored; but frequent framing errors indicate a problem with the communication link. Note that a break condition will be detected as a framing error by the datalink port.
|
|
| On the datalink port only, the transmit overruns indicates the number of transmit characters that had to be discarded since the transmit buffer was full. This indicates a firmware development error since the firmware should not attempt to transmit a character when the transmit buffer was full.
|
|
| On the datalink port only, the receive overruns indicates the number of receive characters that had to be discarded since the receive buffer was full. This indicates the firmware isn't processing received characters efficiently.
|
|
| On the monitor port only, the hardware overruns indicates the number of times the firmware re-initialized the receive buffers. Most likely the hardware successfully received the characters, but the firmware isn't processing received characters efficiently. Note that a hardware overrun can occur if characters are received during initialization.
|
Thermal 1.0 / 1.7x equivalents:
|
|
|
- The monitor command urt info does not have an equivalent.
|
|
| Thermal 2 equivalents:
|
|
|
- The monitor command urt info is comparable to urt info.
|