Xtium2-CLHS PX8 User's Manual
Xtium2-CLHS PX8 Reference
•
51
•
GetGenericParam0: returns the source of the error:
•
1: CRC Error
•
2: 64/66B Error
•
3: Packet Buffer Overflow
•
4: Packet Resend
•
5: 64B/66B Corrected Error
•
GetGenericParam1: returns a bitfield indicating which lane(s) generated the error
•
Bit 0 = Lane 1, Bit 1= Lane 2, …
•
GetCustomSize: returns 7 * UINT32
•
GetCustomData: returns the number of errors per lane. There are 7 entries, each entry
being a UINT32.
Transfer Events
Transfer events are the ones related to the transfer module. Transfer events provide feedback on
image transfer from onboard memory frame buffers to PC memory frame buffers.
•
Start of Frame
Start of Frame event generated when the first image pixel is transferred from on-board
memory into PC memory.
The Sapera event value is CORXFER_VAL_EVENT_TYPE_START_OF_FRAME.
•
End of Frame
End of Frame event generated when the last image pixel is transferred from on-board
memory into PC memory.
The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_FRAME.
•
End of Line
The End of Line event is generated after a video line is transferred to a PC buffer.
The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_LINE.
•
End of N Lines
The End of N Lines event is generated after a set number of video lines are transferred to a
PC buffer. The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_NLINES.
•
End of Transfer
End of Transfer event generated at the completion of the last image transfer from on-board
memory into PC memory. Issue a stop command to the transfer module to complete a
transfer (if transfers are already in progress). If a frame transfer of a fixed number of
images is requested, the transfer module will stop transfer automatically. The Sapera event
value is CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER.
Trigger Signal Validity
The ACU ignores external trigger signal noise with its programmable debounce control. Program
the debounce parameter for the minimum pulse duration considered as a valid external trigger
pulse. For more information see Note 1: General Inputs / External Trigger Inputs Specifications.
Supported Transfer Cycling Methods
The Xtium2-CLHS PX8 supports the following transfer modes, which are either synchronous or
asynchronous.
Images are accumulated in on-board memory in a FIFO type manner. On-board memory can get
filled up if the rate at which the images are acquired is greater than the rate at which the DMA
engine can write them to host buffer memory. On-board memory can also get filled-up if there are
no more empty buffers available to transfer the on-board images.
When no memory is available for a new image to be stored in on-board memory, the image is
discarded and a CORACQ_VAL_EVENT_TYPE_FRAME_LOST or trash buffer callback is generated. If
a CORACQ_VAL_EVENT_TYPE_FRAME_LOST occurs when host buffers are available, it can indicate
a problem with the PX8 bus bandwidth.
