HSB FPGA IP - Camera over Ethernet

In the “HOLOLINK_def.svh” header file, there is a ifdef called “DISABLE_COE”.

What exactly does this ifdef do?

Is there a way to configure or tell the HSB to use CoE exclusively and not ROCE?

Does data have to be packed a certain way on the SIF_RX interface for CoE?

DIS_COE is a build-time option that disables the CoE transmit path to save HW resources. When it is defined, Hololink will send the sensor data using RoCE formatting only. There is not a “CoE-only” setting. In normal circumstances, both RoCE and CoE are enabled in hardware, and can be configured during runtime by software.

For the SIF_RX interface, CoE does expect the payload to be in the right camera-data format. The interface should provide video pixel payload only. This is defined here in the user guide: Dataplane - NVIDIA Docs .

Whatever payload is received on the SIF_RX interface is what will be delivered into GPU memory; Hololink packetizes and transports it, but does not otherwise reinterpret the image data.

How do I setup the HSB for CoE instead of RoCE?

When your application uses FusaCoeCaptureOp (example here), its initialization configures the HSB device to use COE messaging.

One more question…

In the HSB Documentation for the Dataplane Camera Streaming IMX2741080p example, I don’t understand where the 3,840 number of lines come from?

1080p is 1920x1080 pixels and I was expecting 1,080 number of lines instead of the 3,840?

Hi Joe,

You’re right, that’s a typo, the line should go up to 1079 for 1080p resolution

I’ll update the user guide for the next release

Thanks