No new progress in the last few days. Do you have any idea what the issue might be @Alex-Kushleyev ?

Ok looks like it was partially a TrustZone issue. I'm now using the .mbn from sdk 1.0.0 and I can at least read from spidev14.0. But still no dice to actually get the camera to read actual data.

This is the correct pinout from the M0104 J10 to the M0188 J4, yes?

What I'm getting now:
voxl2-mini:/$ dd if=/dev/spidev14.0 bs=164 count=1 | hexdump -C
1+0 records in
1+0 records out
164 bytes copied, 0.0010337 s, 159 kB/s
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000a4

Any ideas @Vinny or @Alex-Kushleyev ? This is unfortunately a pretty big blocker for us.

/dev/spidev14.0 exists but isn't working. Regardless of whether we have the lepton plugged or unplugged from J5 on the m0188, voxl-lepton-server(and even dd) just hangs when we try to read from spi 14.0. And this is after we set 67 high (voxl-gpio -w 67 1). See below for dd outputs from spidev0.0 compared to spidev14.0.

Lepton unplugged

voxl2-mini:/$ dd if=/dev/spidev0.0 bs=164 count=1 | hexdump -C
1+0 records in
1+0 records out
164 bytes copied, 0.00235198 s, 69.7 kB/s
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000a4

Lepton plugged into m0188 J10

voxl2-mini:/$ dd if=/dev/spidev0.0 bs=164 count=1 | hexdump -C
1+0 records in
1+0 records out
164 bytes copied, 0.00223693 s, 73.3 kB/s
00000000 07 ff ff ff 80 00 00 00 00 00 00 00 00 00 00 00 |................|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 e6 |................|
00000020 a7 42 38 4c 4e 04 00 01 00 00 00 00 00 00 00 00 |.B8LN...........|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000a4

Lepton unplugged

voxl2-mini:/$ dd if=/dev/spidev14.0 bs=164 count=1 | hexdump -C
(Just hangs)

Lepton plugged into m0188 J5

voxl2-mini:/$ dd if=/dev/spidev14.0 bs=164 count=1 | hexdump -C
(Just hangs)

So far we've updated https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/dts/m0104/m0104-modalai-qupv3.dtsi and added an alias back to https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/dts/m0104/m0104-kona.dtsi as described below and rebuilt the kernel. We see spidev14.0 but only get "Waiting for first frame" message when trying to run voxl-lepton-server from SPI device 14.

Any ideas? So far we're completely stuck.

Changes to https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/dts/m0104/m0104-modalai-qupv3.dts:

/* M0104 - J10 - GPIO 40-44 */
&qupv3_se14_spi {
        status = "ok";
        spidev@0 {
                compatible = "spidev";
                reg = <0>;
                spi-max-frequency = <50000000>;
        };
};

/* M0104 - J10 JST connector */
&qupv3_se14_2uart {
        status = "disabled";
};

Changes to https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/dts/m0104/m0104-kona.dtsi:

spi14 = &qupv3_se14_spi;

Thanks @Vinny

@Vinny said in FLIR LEPTON 3.5 Thermal camera with VOXL 2:

M0187

Hi @Vinny - I'm guessing the M0187 is your FLIR breakout board? Do you sell these?

@Alex-Kushleyev

That fixed it! Top pin on the M0188 from the view I shared is actually #8, not #1. Thanks for the help!

@Jetson-Nano did you ever figure out a solution to this? I'm getting similar imagery. Is this an FFC issue? Running the same breakout board on a raspberry pi produces completely normal imagery.

And the topmost pin is pin #1 in the view below, correct?

Thanks @Alex-Kushleyev. I hooked up the voxl2 mini to the lepton breakout via the m0188 board and the voxl2 fails to boot (the first green light just stays solid). The voxl2 boots just fine with the m0188 attached if I try without the lepton breakout attached. Does that point to a power issue re:the 2.8v vs 3v mismatch? Or something else?