> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/holoscan/sensor-bridge/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/holoscan/sensor-bridge/_mcp/server.

## Building the Holoscan Sensor Bridge container

Holoscan sensor bridge host software includes instructions for building a demo
container. This container is used to run all holoscan tests and examples.

1. If you have not done so already, fetch the sensor bridge source code from
   [https://github.com/nvidia-holoscan/holoscan-sensor-bridge](https://github.com/nvidia-holoscan/holoscan-sensor-bridge)

   ```none
   $ git clone https://github.com/nvidia-holoscan/holoscan-sensor-bridge
   ```

2. Build the sensor bridge demonstration container. Use **dGPU** for IGX Orin with a
   discrete GPU and OS configured as dGPU, and for x86\_64 Linux hosts with an NVIDIA
   discrete GPU (see the **x86 Linux** tab in
   [host setup](/holoscan/sensor-bridge/getting-started/host-setup#HostSetupTarget)).
   For remaining platforms listed
   [here](/holoscan/sensor-bridge/getting-started/host-setup#HostSetupTarget), use
   **iGPU** below.

#### iGPU

```none
  $ cd holoscan-sensor-bridge
  $ sh docker/build.sh --igpu
```

#### dGPU

```none
  $ cd holoscan-sensor-bridge
  $ sh docker/build.sh --dgpu
```

Note: If RoCE with GPUDirect RDMA fails at runtime (black image, or errors from
`roce_receiver.cpp` such as mismatched PSN metadata), rebuild to force the use of pinned
host memory instead by adding `--disable-roce-gpu-vram` to the command above. Details
are in the
[x86 Linux](/holoscan/sensor-bridge/getting-started/host-setup#HostSetupTarget) host
setup tab.

## Run tests in the demo container

To run the sensor bridge demonstration container, from a terminal in the GUI,

```none
xhost +
sh docker/demo.sh
```

This brings you to a shell prompt inside the Holoscan sensor bridge demo container.
(Note that iGPU configurations, when starting the demo container, will display the
message "Failed to detect NVIDIA driver version": this can be ignored.) Now you're ready
to run sensor bridge applications.

## Holoscan sensor bridge software loopback tests

Sensor bridge host software includes a test fixture that runs in loopback mode, where no
sensor bridge equipment is necessary. This test works by generating UDP messages and
sending them over the Linux loopback interface.

In the shell in the demo container:

```none
pytest
```

Note that the test fixture intentionally introduces errors into the software stack. As
long as pytest indicates that all test have passed, any error messages published by
individual tests can be ignored. If pytest itself reports failures, see the
[troubleshooting page](/holoscan/sensor-bridge/support/troubleshooting).

For systems with a sensor bridge device and IMX274, the test fixture can execute
additional tests that prove that the device and network connections are working as
expected.

First, ensure that the
[sensor bridge firmware is up to date](/holoscan/sensor-bridge/firmware/firmware-setup).

For IGX configurations,
[connect both SFP+ connections on the sensor bridge device to the QSFP connectors](/holoscan/sensor-bridge/getting-started/hardware-setup#connecting-holoscan-sensor-bridge-to-the-host),
then

```none
sh ./test-igx-cpnx100-imx274.sh
```

For AGX Orin, only one camera is supported, so only
[SFP+ 0](/holoscan/sensor-bridge/getting-started/hardware-setup#connecting-holoscan-sensor-bridge-to-the-host)
is to be connected. Run the device test on AGX this way:

```none
sh ./test-agx-cpnx100-imx274.sh
```

If things are not working as expected, check the
[troubleshooting page](/holoscan/sensor-bridge/support/troubleshooting).