Skip to content

Commit 1b3e1b2

Browse files
committed
Release 2.3.0, 25.08.
Signed-off-by: Patrick O'Grady <[email protected]>
1 parent 6ad9493 commit 1b3e1b2

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+4285
-3243
lines changed

.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,4 @@
44
**/*.docx filter=lfs diff=lfs merge=lfs -text
55
.gitlab-ci.yml export-ignore
66
RELEASE.sh export-ignore
7+
PUBLISH.sh export-ignore

RELEASE_NOTES.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,28 @@
11
# Release Notes
22

3+
## 2.3-GA, August 2025
4+
5+
### Dependencies
6+
7+
- IGX: [IGX-SW 1.1.2 Production Release](https://developer.nvidia.com/igx-downloads)
8+
- AGX: Use [SDK Manager](https://developer.nvidia.com/sdk-manager) to set up JetPack
9+
6.2.1.
10+
- Thor: Use [SDK Manager](https://developer.nvidia.com/sdk-manager) to set up JetPack
11+
7.0.
12+
- Holoscan Sensor Bridge, 10G; FPGA v2507.
13+
14+
Be sure and follow the installation instructions included with the release, including
15+
PTP configuration and HSB device firmware updates. To generate documentation, in the
16+
host system, run `sh docs/make_docs.sh`, then use your browser to look at
17+
`docs/user_guide/_build/html/index.html`.
18+
19+
### Updates from 2.2-GA
20+
21+
- **Thor support with Leopard Eagle VB1940 cameras.** Documentation and device
22+
programming support is included to support JP7.0 based Thor configurations with the
23+
Leopard Eagle VB1940 camera. See
24+
[Thor JP7 setup instructions here](https://docs.nvidia.com/holoscan/sensor-bridge/latest/thor-jp7-setup.md).
25+
326
## 2.2-GA, August 2025
427

528
### Dependencies

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
2.2.1
1+
2.3.0

docs/user_guide/introduction.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ provided showing video processing and inference based on a Sony IMX274 camera. T
1414
configuration can be connected to an
1515
[IGX](https://www.nvidia.com/en-us/edge-computing/products/igx) or
1616
[Jetson AGX Orin](https://developer.nvidia.com/embedded/learn/jetson-agx-orin-devkit-user-guide/index.html)
17+
or
18+
[Jetson AGX Thor](https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-thor/)
1719
edge compute system. Additionally:
1820

1921
- Holoscan Sensor Bridge supports hosts with or without accelerated RDMA capable NICs.

docs/user_guide/sensor_bridge_firmware_setup.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,15 +50,24 @@ components are programmable and should be updated.
5050
program_lattice_cpnx100 --hololink=192.168.200.2 scripts/manifest.yaml
5151
```
5252

53+
1. For programming the Leopard imaging VB1940 Eagle Camera: make sure you cloned and
54+
built the `holoscan-sensor-bridge repo` (for instructions please see
55+
[Thor Host Setup](thor-jp7-setup.md) page).
56+
57+
```sh
58+
cd holoscan-sensor-bridge/build
59+
sudo ./tools/program_leopard_cpnx100/program_leopard_cpnx100 ~/holoscan-sensor-bridge/scripts/manifest_leopard_cpnx100.yaml
60+
```
61+
5362
1. When run this way, the manifest file directs the firmware tool to download the FPGA
5463
BIT files from
5564
[NVIDIA Artifactory](https://edge.urm.nvidia.com/artifactory/sw-holoscan-thirdparty-generic-local/hsb)
5665
with the version validated for use with this software tree. When run on an IGX
5766
configuration, firmware updates can take up to 5 minutes; when run on AGX, expect a
5867
run time of as much as 30 minutes. **Do not interrupt the process in the middle.**
5968

60-
1. Once flashing is complete, **power cycle** the device and watch that the sensor
61-
bridge powers up with 2 green LEDs on
69+
1. For the Lattice CPNX100-ETH-SENSOR-BRIDGE, once flashing is complete, **power cycle**
70+
the device and watch that the sensor bridge powers up with 2 green LEDs on
6271

6372
1. Ping the sensor bridge device at its IP address (e.g. 192.168.0.2) and verify a valid
6473
ping response

docs/user_guide/sensor_bridge_hardware_setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ It features:
129129
<img src="vb1940-aio.jpg" alt="LI VB1940 Eagle Camera" width="80%"/>
130130
131131
## Connecting VB1940 Eagle Camera to the Host
132-
132+
Make sure your VB1940 is flashed with the latest firmware, see [Holoscan Sensor Bridge FPGA firmware update](sensor_bridge_firmware_setup.md) page for more details.
133133
1. Connect the Ethernet cable from the VB1940 Eagle Camera to an available Ethernet port on your devkit
134134
135135
2. For IGX Devkit, use a QSFP adapter to connect to the QSFP Ethernet port marked with a red arrow on the back panel

docs/user_guide/setup.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ Holoscan sensor bridge is supported on the following configurations:
99
this configuration, the on-board Ethernet controller is used with the Linux kernel
1010
network stack for data I/O; all network I/O is performed by the CPU without network
1111
acceleration.
12+
- Thor systems running [JP7.0.0](https://developer.nvidia.com/embedded/jetpack) with
13+
MGBE SmartNIC device and CoE transport. JP7.0.0 release currently supports only the
14+
[Leopard imaging VB1940 Eagle Camera](sensor_bridge_hardware_setup.md).
1215

1316
After the [Holoscan sensor bridge board is set up](sensor_bridge_hardware_setup.md),
1417
configure a few prerequisites in your host system. While holoscan sensor bridge
@@ -33,7 +36,11 @@ remembered across power cycles and therefore only need to be set up once.
3336

3437
Reboot the computer to activate this setting.
3538

36-
Next, follow the directions on the appropriate tab below to configure your host system.
39+
Next, follow the directions on the appropriate tab below to configure your Orin host
40+
system.
41+
42+
**For Thor host setup, please follow the instructions on the
43+
[Thor Host Setup](thor-jp7-setup.md) page.**
3744

3845
`````{tab-set}
3946
````{tab-item} IGX

docs/user_guide/thor-jp7-setup.md

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
# Thor host setup
2+
3+
After installing JetPack 7.0.0 on the Thor devkit, please follow these steps to set up
4+
your Thor for running Holoscan sensor bridge examples.
5+
6+
- Install Holoscan SDK v3.5.1
7+
8+
```none
9+
echo "deb https://repo.download.nvidia.com/jetson/jetson-4fed1671 r38.1 main" | sudo tee /etc/apt/sources.list.d/nvidia-l4t-apt-source-jpea.list
10+
sudo apt update
11+
sudo apt install holoscan
12+
```
13+
14+
- Install other Holoscan sensor bridge dependencies:
15+
16+
```none
17+
sudo apt install -y git-lfs cmake libfmt-dev libssl-dev libcurlpp-dev libyaml-cpp-dev libibverbs-dev python3-dev
18+
```
19+
20+
- Obtain the Holoscan sensor bridge repository:
21+
22+
```none
23+
git clone https://github.com/nvidia-holoscan/holoscan-sensor-bridge.git
24+
```
25+
26+
- Build Holoscan sensor bridge, inside the `holoscan-sensor-bridge` directory:
27+
28+
```none
29+
mkdir build && cd build
30+
cmake -DCCCL_DIR:PATH="/usr/local/cuda/targets/sbsa-linux/lib/cmake/cccl" -DHOLOLINK_BUILD_SIPL=1 ..
31+
make -j
32+
```
33+
34+
- Enable the network interface and ensure that the camera enumerates. Note that this
35+
documentation assumes a camera IP address of 192.168.0.2.
36+
37+
```none
38+
EN0=mgbe0_0
39+
sudo nmcli con add con-name hololink-$EN0 ifname $EN0 type ethernet ip4 192.168.0.101/24
40+
sudo nmcli connection modify hololink-$EN0 +ipv4.routes 192.168.0.2/32
41+
sudo nmcli connection modify hololink-$EN0 ethtool.ring-rx 4096
42+
sudo nmcli connection up hololink-$EN0
43+
```
44+
45+
- Retrieve your camera's MAC ID with the `hololink-enumerate` command:
46+
47+
```none
48+
./tools/enumerate/hololink-enumerate
49+
```
50+
51+
You should see a response from the camera similar to this one:
52+
53+
```none
54+
mac_id=8C:1F:64:6D:70:03 hsb_ip_version=0x2506 fpga_crc=0xffff ip_address=192.168.0.2 fpga_uuid=f1627640-b4dc-48af-a360-c55b09b3d230 serial_number=ffffffffffffff interface=mgbe0_0 board=Leopard Eagle
55+
```
56+
57+
Make sure to set all of the `ip_address` and `mac_address` fields in the configuration
58+
files (there are multiple instances in each configuration file)
59+
60+
```
61+
../examples/sipl_config/vb1940_single.json
62+
../examples/sipl_config/vb1940_dual.json
63+
```
64+
65+
Give permission for root to access the X display, Note that the DISPLAY environment
66+
variable needs to be set first if being run over SSH.
67+
68+
```none
69+
xhost +
70+
```
71+
72+
Run the `sipl_player` application using either the single or dual camera configurations
73+
contained in the `examples/sipl_config` directory. To run them using HW ISP capture
74+
mode, use the following:
75+
76+
```none
77+
sudo ./examples/sipl_player --json-config ../examples/sipl_config/vb1940_single.json
78+
sudo ./examples/sipl_player --json-config ../examples/sipl_config/vb1940_dual.json
79+
```
80+
81+
To run the examples for RAW capture mode, add the --raw argument. Note that the image
82+
quality will not be very good due to the lack of proper ISP processing (the image may be
83+
extremely dark).
84+
85+
```none
86+
sudo ./examples/sipl_player --json-config ../examples/sipl_config/vb1940_single.json --raw
87+
sudo ./examples/sipl_player --json-config ../examples/sipl_config/vb1940_dual.json --raw
88+
```
89+
90+
JP7.0.0 release currently supports only the
91+
[Leopard imaging VB1940 Eagle Camera](sensor_bridge_hardware_setup.md).

docs/user_guide/troubleshooting.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,30 @@ Use the appropriate value where `roceP5p3s0f0` is shown here. When no data plane
4949
requests are received, be sure and check that the sensor is properly connected to the
5050
sensor bridge board.
5151

52+
## v2.3.0 Thor Intermittent Random I2C errors when running SIPL sample applications
53+
54+
When running SIPL applications, intermittent failures to ping cameras over Ethernet and
55+
random I2C errors can be seen because of driver header incompatibility. This applies
56+
only for SIPL applications and not for Holoscan Sensor Bridge applications. When you
57+
encounter an issue with running the SIPL CoE Camera sample, follow the steps below.
58+
59+
After you install JetPack 7.0 GA, the following steps are required for running the
60+
nvsipl_coe_camera application:
61+
62+
```none
63+
sudo cp /usr/lib/nvsipl_uddf/libnvuddf_eagle_library.so /tmp/libnvuddf_eagle_library.so_orig
64+
cd /usr/src/jetson_sipl_api/sipl/
65+
sudo mkdir build
66+
cd build
67+
sudo cmake ..
68+
sudo make nvsipl_coe_camera
69+
sudo cp ./samples/coe_camera/nvsipl_coe_camera ~/
70+
sudo cp /tmp/libnvuddf_eagle_library.so_orig /usr/lib/nvsipl_uddf/libnvuddf_eagle_library.so
71+
Run the app nvsipl_coe_camera.
72+
```
73+
74+
Please also refer to JetPack 7.0 GA release notes for more details.
75+
5276
## Sensor Bridge LED indications
5377

5478
The Holoscan Sensor Bridge board has two leds that depending on their state have the

examples/CMakeLists.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,8 +105,11 @@ if(HOLOLINK_BUILD_SIPL)
105105
target_link_libraries(sipl_player
106106
PRIVATE
107107
hololink
108+
hololink::operators::image_processor
109+
hololink::operators::packed_format_converter
108110
hololink::operators::sipl_capture
109111
holoscan::core
112+
holoscan::ops::bayer_demosaic
110113
holoscan::ops::holoviz
111114
gxf_multimedia
112115
)

0 commit comments

Comments
 (0)