Repository navigation
feat(camera): add the FLIR Boson+ driver and JAJ overlays - #163
Merged
Merged
Conversation
A MIPI Boson+ reaches a carrier's CSI port through the ARK Boson Adapter: 640x512 at 60 Hz on two D-PHY lanes with a continuous 246 MHz clock, and FLIR's command protocol on I2C at 0x6a. Add nv_boson, a tegracam driver that sets the Boson up over that I2C, and one jetson-io overlay per JAJ CSI port. The driver offers two 640x512 modes at 60 fps: post-colorize UYVY and pre-AGC 14-bit, which the VI takes as RAW14 Bayer since it has no 14-bit mono format. Mode 1 needs the sensor_mode control, as both are the same size. At stream start it switches the Boson to MIPI, sets the mode's DVO type, output format and MIPI mux, and turns off telemetry and the MIPI embedded-data tag: the tag is on from the factory and its embedded line makes the VI discard every frame (EMBED_INFRINGE). Nothing is saved to the Boson's flash. Starting MIPI keeps the Boson busy for about 300 ms. It holds SCL until the Tegra controller times the read out, and that read still takes the reply's 0x8e. The I2C layer treats NAKs and timeouts as busy, accepts a bare 0xa1 as a reply start, as FLIR's own I2C transport does, and checks MIPI ACTIVE by reading the state back. The adapter routes the port's MCLK net to Boson EXT_SYNC through R12, so each overlay makes that pad a pulled-down input, as the Hadron overlays do. CAM1 is bench-tested on a JAJ; CAM0 is not. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🔵 Needs a closer look
Hardware-aware human review is needed because CAM0 is untested, the full JAJ build was not run, and normal PR CI does not compile the new overlays.
No open issues 🎉
What changed in this PR
Adds FLIR Boson+ thermal-camera support through the ARK Boson Adapter, integrating a new driver and JAJ camera overlays into the existing kernel build.
Changes:
- Adds an I2C-controlled
nv_bosondriver for 640×512 at 60 fps in colourised UYVY and pre-AGC RAW14 modes. - Adds per-port JAJ overlays with shared camera graph, mode definitions and sync-pin configuration. CAM1 is bench-tested; CAM0 remains untested.
- Documents capture commands, mode selection and adapter wiring limitations.
| File | Description |
|---|---|
README.md |
Links to the Boson documentation. |
products/JAJ/overlay/tegra234-p3767-camera-p3768-boson-cam1.dts |
Configures Boson wiring for JAJ CAM1. |
products/JAJ/overlay/tegra234-p3767-camera-p3768-boson-cam0.dts |
Configures Boson wiring for JAJ CAM0. |
products/JAJ/overlay/tegra234-camera-boson.dtsi |
Defines shared capture graph, mode properties and sync pinmux. |
products/JAJ/overlay/tegra234-camera-boson-sensor.dtsi |
Defines the sensor node and both capture modes. |
products/JAJ/overlay/dtbo.list |
Registers both Boson overlays for the JAJ build. |
kernel_overlay/nvidia-oot/drivers/media/i2c/nv_boson.c |
Implements identification, command transport, mode setup and streaming. |
docs/cameras.md |
Adds Boson to the supported-camera list. |
docs/boson.md |
Documents setup, capture, validation status and hardware caveats. |
build.sh |
Registers nv_boson alongside existing sensor modules. |
Review effort: Balanced
The driver hard-coded a continuous MIPI clock. It now sets the Boson's clock lane from the mode's discontinuous_clk, and each port's overlay picks it: CAM1 stays continuous, as it was bench-tested, and CAM0 is gated, like the IMX219, IMX477 and Hadron overlays on that port. CAM0 does not stream yet. The Boson probes on the CAM0 mux channel and takes its configuration, but the VI receives almost no valid packets. With a continuous clock no frame start is recognised. With a gated clock on both ends the Boson's frame numbers decode for a few percent of frames, so lane mapping and polarity are right, and every frame still ends in a forced frame end. Two cables behaved the same, the port settings match the overlays that work there, and the board routes CSI1 straight to J28. docs/boson.md records this. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On JAJ CAM0 (CSI1) the Boson probed and took its configuration, but no frame completed: the VI caught the Boson's frame start in only a few percent of frames. NVCSI's own THS-settle, which it computes from the mode's 246 MHz MIPI clock, is too short there for the Boson's bursts. An experimental build that overrode the parsed mode properties at load time swept both settings without a reboot each. Only lane polarities with bit 2 set and bit 3 clear decoded frame starts, which confirms "6". With cil_settletime from 72 to 230, both modes streamed cleanly with either clock mode; at 0 (automatic), 68 or less, and 255 they did not. Make cil_settletime a per-port overlay setting. CAM0 uses 150, the middle of the window, and goes back to a continuous clock like CAM1; CAM1 keeps NVCSI's own value, which it was tested with. With the repo driver and the new CAM0 overlay, both modes run at 60.00 fps with no VI errors over alternating runs and an 1800-frame run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The hardware notes said R13 would route EXT_SYNC to the IMU's FSYNC "instead". R12 and R13 both hang off the same node, so with R13 fitted the Boson, the port's MCLK pad and the IMU's FSYNC share one net. Rev 1.0 leaves R13 unfitted; the bench unit now has it. A Frame sync section, as hadron.md has, records what the bench measured with the adapter on JAJ CAM1: the Boson as sync master over its UART puts 60.0-60.2 pulses per second on PP.01 (none with sync off), and the ICM-45686 tags 59.6-59.8 samples per second through R13. With the ribbon in the port whose overlay is not applied, that port's MCLK pad stays a driven output and holds the net. The Rev 1.0 UART note now gives the fix: swap the two nets at J1 and leave R7 and R8 where they are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 17, 2026
The four PAB overlays put the Boson on the port's TCA9546 channel, as the PAB Hadron overlays do, and make the port's MCLK pad the sync input. CAM0 and CAM1 set THS-settle 150, the value JAJ CAM0 (CSI1) needed; CAM2 and CAM3 keep NVCSI's own. Bench-tested on a PAB with an Orin Nano 8GB on all four ports: UYVY and RAW14 at 60 fps with no gaps, the IMU, and the Boson's sync pulses at the MCLK pad and at the IMU's FSYNC, with the Boson made sync master over the camera I2C. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
|
Claude review on behalf of @dakejahl Merge after fixes. The driver and overlays look sound and are bench-tested on every port they ship for. Only the camera table and the PR title still describe the JAJ-only version of this PR. Must fix
Optional
|
…son+ with MIPI The adapter leaves the Boson's USB unconnected on purpose, to save space, so MIPI is its only video path. An original Boson (part number 20640 or 20320, 3.x software) has no MIPI output; the one tried on the bench did not answer on the camera I2C at 0x6a. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
nv_boson, a V4L2 driver for MIPI-model FLIR Boson+ thermal cameras, and one jetson-io overlay per JAJ and PAB CSI port for the ARK Boson Adapter. Both modes (colourised UYVY and pre-AGC RAW14) stream 640x512 at 60 fps on JAJ CAM1 and CAM0 and on all four PAB ports. CAM0 needs a longer NVCSI THS-settle than NVCSI computes; see JAJ CAM0. This is also the bring-up record for the Boson Adapter Rev 1.0, which has two wiring problems listed below.Problem
The ARK Boson Adapter (Rev 1.0) puts a Boson+ on a carrier's 22-pin CSI connector, but nothing on the Jetson could configure the Boson or receive its MIPI video. A factory Boson+ powers up with CMOS output and MIPI off, so its CSI lanes stay idle until something switches it over.
Solution
Driver.
nv_bosonis a tegracam driver underkernel_overlay/, registered inbuild.shnext tonv_imx708andnv_ov64b40.0x6a, framed as8E A1, a big-endian u16 length, then sequence, function id, status and arguments, with no CRC. Function ids and enums come from FLIR's Boson SDK (FunctionCodes.h,EnumTypes.h). Videology's MIT-licensedflir_boson_kernel_moduleshowed the framing and the MIPI start sequence. The probe reads the serial number, part number and software version, and fails if the Boson does not answer.sensor_modecontrol.UYVYRG14FLR_BAD_OUT_TYPE.EMBED_INFRINGE(err_databit 14). The driver turns off telemetry and the tag at stream start.DVO_SETMIPISTATEACTIVE takes about 300 ms. During it, the Boson holds SCL until the Tegra controller times the read out, and that read still takes the reply's0x8e. The I2C layer treats a NAK or timeout as busy, accepts a bare0xa1as the start of a reply (as FLIR's own I2C transport does), and confirms ACTIVE by reading the MIPI state back. All configuration commands answer within 10 ms while MIPI is off.discontinuous_clk, so an overlay can pick continuous or gated. Both JAJ overlays use continuous; gated also streams on CAM0.Overlays.
tegra234-camera-boson.dtsiholds the VI/NVCSI graph,tegra-camera-platform, the mode macro and the sync pad.tegra234-camera-boson-sensor.dtsiholds the sensor node, and each per-port.dtswires the I2C mux and sets the port's lane polarity, clock mode and THS-settle.cil_settletime = "150"cil_settletime = "150"cil_settletime = "150"The PAB overlays put the Boson on the port's TCA9546 channel, laid out like the PAB Hadron overlays. PAB's connectors are 15-pin, so the adapter goes through a 22-to-15-pin FFC adapter.
The adapter routes the port's
CAMn_MCLKnet to Boson pin 72EXT_SYNCthrough R12. As in the Hadron overlays, each overlay makes that pad a pulled-down input in theexp-header-pinmuxstate, so it does not fight the Boson.Docs.
docs/boson.mdcovers the overlays, modes, capture commands, wiring, settle time, frame sync and hardware notes.docs/cameras.mdand the README index link to it.Bench
JAJ, Orin Nano 4GB, R36.5 image from
b697c62, Boson+ 640 22640A095-6IAAX (SN 427619, software 4.1.27660), on CAM1 and then on CAM0. The module was built on the target against the image's headers, and the overlay withcpp+dtc. The same recipe reproduces the installed Hadron CAM1.dtbobyte for byte. I did not run a full./build.sh.v4l2-ctl, 300 frames per run) with no NVCSI/VI errors. Five runs alternating UYVY, RAW14, UYVY, RAW14 and UYVY each start cleanly, so mode switches and start/stop both work.5d715f0, after a reboot onto the CAM0 overlay, four alternating 300-frame runs and an 1800-frame UYVY run all ran at 60.00 fps with nothing in dmesg, from a Boson power-cycled back to its factory settings.v4l2srcinto softwarex264enc(the Orin Nano has no hardware encoder) over RTP to the host on the USB network ran for 8,400 frames at 60 fps with none dropped. Encoding uses about 80% of one core.PAB
PAB, Orin Nano 8GB, image from a local
./build.sh PABofe7d1f0f, same Boson+ (SN 427619). The PAB overlays were built on the host withcpp+ the staged tree'sdtc, which reproduces the image's Hadron CAM3.dtbobyte for byte, and copied to/boot. J3's I2C went to a PAB I2C connector (IMU oni2c-1). The PAB has no spare UART for J3, so the sync checks made the Boson sync master with the same FLIR command over the camera I2C (I2C_SLAVE_FORCEon0x6a, nothing streaming).boson 9-006aboson 10-006aboson 11-006aboson 12-006aPP.000 / 59.89 HzPP.010 / 60.01 HzPQ.050 / 60.18 HzPQ.060 / 60.08 HzNo run had a gap or an error frame, and a frame of each mode on each port shows a clean scene. CAM0 and CAM1 were not tried with NVCSI's own settle.
Original Boson (not supported)
An original Boson 640 does not work with this driver or adapter, because it has no MIPI output. The bench tried one on PAB CAM0 after the Boson+ runs: part number 20640AS32-6PARX, software 3.0.25868, SN 227597, sensor 500-0773.
0x6a, on any mux channel, even after a power cycle. The probe fails withno Boson answering at 0x6a (-121), and the Pi driver on the Just A Pi logs the same.DVO_GETOUTPUTINTERFACEreturns0x161(R_CAM_DSPCH_BAD_CMD_ID), andDVO_GETMIPISTATE,DVO_GETMIPISTARTSTATEandDVO_GETMIPICLOCKLANEMODEreturn0x1B0(R_CAM_FEATURE_NOT_ENABLED).The adapter leaves the Boson's USB unconnected on purpose, to save space, so MIPI is its only video path. It therefore needs a Boson+ with the MIPI option, whose part numbers start with
22640and run 4.x software. An original Boson's part number starts with20640and its software is 3.x. The same adapter, port and overlay streamed the Boson+ just before, and the adapter's UART path worked with the original Boson.JAJ CAM0
On JAJ CAM0 the Boson probed on mux channel 0 (
boson 10-006a) and took its whole configuration, but no frame completed. The VI caught the Boson's frame start in only a few percent of frames (corr_err ... frame <n>, err_data 131072, a forced frame end), and with a continuous clock it decoded none. A second cable behaved the same, and the JAJ routes CSI1 straight to J28.NVCSI reads
lane_polarityandcil_settletimefrom the driver's parsed mode properties at every stream start, so an experimental build (not in this PR) that overrode them on load swept both without a reboot each, at 60 frames per point:lane_polarity0–15"6"is rightcil_settletime0 (NVCSI's own), 1–68cil_settletime72–230cil_settletime255At 150, both clock modes then ran 1200 UYVY, 600 RAW14, 600 UYVY and 600 RAW14 frames at 60.00 fps with no errors. NVCSI's own THS-settle, computed from the mode's 246 MHz MIPI clock, is too short on CSI1 for the Boson's bursts, though it works on CSI2. The CAM0 overlay sets
cil_settletime = "150", the middle of the window. CAM1 keeps NVCSI's own value, which it was tested with; 150 has not been tried on CAM1.Adapter Rev 1.0 findings
0x6aon the CAM1 mux channel0x68, WHO_AM_I0xe9, about 1.00 g at restuart_apb_sin(the Boson's input) and pin 43 asuart_apb_sout(its output). The adapter labels 33UART_TX_BOSONand 43UART_RX_BOSON, so a 1:1 J3 cable joins the host TX to the Boson's TX. The fix for the next revision is to swap the two nets at J1 and leave R7 and R8 on their nets: R7 (604 Ω to 1V8, on U4 A2) then pulls upuart_apb_sin, where FLIR asks for a pull-up, and R8 (604 Ω to 3V3, on U4 B1) pulls up the Boson's TX on the 3.3 V side, which the LSF needs to translate a high up. The Rev 1.0 workaround, crossing J3 pins 2 and 3, leaves the Boson's TX with no 3.3 V pull-up of its own; it works on the JAJ only because the JAJ pulls up its RX line.uart3_*_pcc5/6), which the TCU console (ttyTCU0) owns at a fixed 115200. On UART0 or UART1, J3's I2C lands on CTS (SCL) and RTS (SDA). The IMU answered there over bit-banged I2C after setting both pads to drive and read:0x2430090and0x2430098=0x440, runtime only. The video does not need J3 at all, since the driver controls the Boson over the CSI port's I2C.Not in this PR
i2c-gpiooverlay for the IMU on UART1 RTS/CTS./dev/ttyTHS2. It is the debug console (ttyTCU0), andttyTHS2is UARTE. That needs a separate docs fix.🤖 Generated with Claude Code