Operator CxpPortStatus

Operator Library: Hardware Platform

The operator monitors the status of a CXP channel. It displays the current channel configuration and provides access to error counters via read parameters.

The operator is using one resource of type CxpStatusPort which is in range 0 to 3. This resource corresponds to the CXP channel. The CxpStatusPort resources correspond to the CameraPort resources which are used by operator CxpCamera.

Available for Hardware Platform
imaFlex CXP-12 Quad

I/O Properties

Property Value
Operator Type None (since there are neither Inputs nor Outputs)

Supported Link Format

None

Parameters

PoCXPState
Type Dynamic read parameter
Default BOOTING
Range {BOOTING, POCXPOK, MAX_CURR, LOW_VOLT, OVER_VOLT, ADC_Chip_Error}

The first 5 states are defined by the CXP standard for the PoCXP state machine. The last state ADC_Chip_Error represents an error when the communication between the FPGA and ADC chip is broken, which measures the voltage and current of the channel.

PoCXPCurrent
Type Dynamic read parameter
Default 0
Range [0:1000]

Current flowing through the CXP cable in mA.

PoCXPVoltage
Type Dynamic read parameter
Default 0
Range [0 : 30]

Voltage sourced through the CXP cable in V.

PoCXPControllerEnabled
Type Dynamic read parameter
Default YES
Range {NO,YES}

State of the power over CXP engine. YES means the power controller will source the camera which requires power over CXP cable when connected, NO means the camera is not powered via the CXP cable. Note that this parameter is not showing whether the camera is sourced or not, instead it is showing that the capability of powering the camera via the CXP cable is enabled or not.

MappedToFgPort
Type Dynamic read parameter
Default 0
Range [0:3]

Frame grabber port to which the corresponding CXP channel is connected.

MappedToFwPort
Type Dynamic read parameter
Default 0
Range [0:3]

The firmware CXP channel which is currently monitored by the module. Note that there is not necessarily a one-by-one mapping between firmware port (resource CameraPort) and frame grabber port (physical connector). Instead it can be any permutation. The software discovery process reorders the channels and ports to achieve correct virtual interconnect.

Decoder8b10bError
Type Dynamic read parameter
Default 0
Range [0 : 2^48-1]

Number of measured symbols received by the channel transceiver, which are not in 8b10b encoding or/and have wrong disparity.

ByteAlignment8b10bLocked
Type Dynamic read parameter
Default NO
Range {NO, YES}

This parameter shows whether the channel transceiver found the byte boundaries or not, so decoding the of 8b10b input stream can be performed.

CurrentPortBitRate
Type Dynamic read parameter
Default 0
Range [0 : 12.5]

This parameter shows the bit rate of the channel in Gb/s which is currently configured in the transceiver by the runtime discovery software.

StreamPacketSize
Type Dynamic read parameter
Default 8192
Range [4 : 65532]

This parameter shows the supported maximum stream packet size, which will be written also to the CXP camera during the CXP discovery step. The value is set by the firmware and complies with the CXP standard. This means the value must be divisible by 4 bytes because all packets are 32 bit aligned.

CxpStandard
Type Dynamic read parameter
Default CXP_1_1_1
Range {CXP_1_0, CXP_1_1_1, CXP_2_0, unknown}

This parameter shows the version of the CXP standard which is currently in use.

RxTriggerOverRequestCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts the received trigger packets for which no acknowledgment could be sent, because the acknowledgment of the previous trigger was still ongoing. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

TxTriggerOverRequestCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts the trigger requests which were skipped, because the transmitter was still busy by sending the previous trigger packet. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxTriggerAckLostCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts the situations in which a trigger packet was sent, but no acknowledgment packet was received for it yet and the timeout (480ns for 1-6Gb/s, 240ns for 10-12.5Gb/s) is reached. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxGpioOverRequestCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which a GPIO packet was received but no acknowledgment could be sent, because the transmitter still was busy sending the acknowledgment of the previously received GPIO packet. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

TxGpioOverRequestCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts GPIO requests which were skipped, because the transmitter was still busy by sending the previous GPIO packet. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxGpioAckLostCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which a GPIO packet was sent but no acknowledgment packet was received for it yet and the timeout (480ns for 1-6Gb/s, 240ns for 10-12.5Gb/s) is reached. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxStreamIncompleteCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which a received stream packet is not correctly formatted, e.g. it misses the end of packet indicator etc. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxControlAckLostCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which a control packet was sent but no acknowledgment packet was received for it yet and the timeout of 200 ms is reached. See CXP 2.0 standard, chapter 9.6.1.1. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxControlTagErrorCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which an acknowledgment for a control packet was received with a tag which is not matching the expected tag sent in the correspondent request control packet. See CXP 2.0 standard, chapter 9.6.1.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxControlAckIncompleteCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which an acknowledgment for a control packet was received which was not correctly formatted, e.g. it misses the end of packet indicator etc. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxEventOverRequestCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which another event packet is received but the corresponding acknowledgment can't be sent because the transmitter is still sending a previous event acknowledgment. See CXP standard 2.0, chapter 9.8.1.1. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxEventIncompleteCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which the received event packet is incomplete, e.g. it misses the end of the packet indicator. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxHeartBeatIncompleteCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which the received heart beat packet is incomplete, e.g. it misses the end of the packet indicator. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxUnknownDataReceivedCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which the unknown packet data is received, which is not part of the CXP standard. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxErrorCorrectedCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts errors received in packet headers and trailers which could be corrected. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxTriggerPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received trigger packets.

RxTriggerAckPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received trigger acknowledge packets.

RxGpioPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received GPIO packets.

RxGpioAckPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received GPIO acknowledge packets.

RxStreamPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received stream packets.

RxControlAckPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received stream acknowledge packets.

RxLinkTestPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received link test packets.

RxEventPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received event packets.

RxHeartBeatPacketCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether errors were corrected in received heart beat packets.

RxUncorrectableErrorCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts errors received in packet headers and trailers which could not be corrected. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxTriggerPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received trigger packets which could not be corrected.

RxTriggerAckPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received trigger acknowledgement packets which could not be corrected.

RxGpioPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received GPIO packets which could not be corrected.

RxGpioAckPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received GPIO acknowledgement packets which could not be corrected.

RxStreamPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received stream packets which could not be corrected.

RxControlAckPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received control acknowledgement packets which could not be corrected.

RxLinkTestPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received link test packets which could not be corrected.

RxEventPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received event packets which could not be corrected.

RxHeartBeatPacketNotCorrected
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were errors in received heart beat packets which could not be corrected.

RxPacketCrcErrorCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts CRC errors in received packets. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxStreamPacketCrcError
Type Dynamic read parameter
Default NO
Range {NO,YES}

Notify whether there were CRC errors in received stream packets.

RxControlAckPacketCrcError
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were CRC errors in received control acknowledgement packets.

RxEventPacketCrcError
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter notifies whether there were CRC errors in received event packets.

RxUnsupportedPacketCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts received unsupported packets, i.e. those which are not allowed by CXP standard. For example event/heart beat packets in CXP 1.x or GPIO packets in CXP 2.0 and CXP 1.1.x. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxUnsupportedGpioPacketReceived
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicates whether a GPIO packet was received while using a CXP standard higher than 1.0.

RxUnsupportedEventPacketReceived
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicates whether an event packet was received while using a CXP standard less than 2.0.

RxUnsupportedHeartBeatPacketReceived
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicates whether a heart beat packet was received while using a CXP standard less than 2.0.

RxUnsupportedGpioAckPacketReceived
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicates whether a GPIO acknowledgment was received while using a CXP standard higher than 1.0.

RxUnsupportedGpioPacketRequestReceived
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicates whether a GPIO request from VisualApplets was received while using a CXP standard higher than 1.0.

RxLengthErrorCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts situations in which the length of the packet does not match the length defined in the packet header. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxStreamPacketLengthError
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicated whether there is a length error in the stream packets.

RxEventPacketLengthError
Type Dynamic read parameter
Default NO
Range {NO,YES}

This parameter indicated whether there is a length error in event packets.

RxEventTagErrorCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

This parameter counts tag errors in received event packets, which happens when the event packet tag got a gap. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

RxStreamPacketCount
Type Dynamic read parameter
Default 0
Range [0 : 2^31-1]

This parameter counts the amount of received stream packets. Bits [29:0] count the number of packets. Bit [30] is set when a counter overflow occurs.

RxHeartBeatMaxPeriodViolationCount
Type Dynamic read parameter
Default 0
Range [0 : 8191]

The heart beat period is defined in CXP 2.0 standard as 100ms maximum, i.e. within that time at least 1 heart beat packet needs to be send by the camera. This parameter counts the situations in which this condition is not met. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.