Pads for electromagnetic shielding on top and bottom (shields not placed by default on stock PT2).JTAG port broken out to SMT pads for debug via ST-Link/V2 (requires additional cable and adapter, not included).

I2C and UART Expansion over standard 100 mil (0.1') holes.

Works with GetThermal - our custom open source thermal video display software for macOS and Linux with radiometric support.

Open source reference firmware: GroupGets PureThermal Github.

STM32F412 ARM microprocessor - execute on-board image processing without need for an external system.

9 Hz color video over usb using the USB UVC class.

USB UVC works on Linux, macOS, Windows, and Android.

Use one standard and included USB type A to micro B cable cable for all major functions.Compatible with all production FLIR Leptons, including radiometric 2.5 and 3.5 cores.Power Input, Video Output, and Firmware Updates All Over USB (micro B type connector).Get Thermal video over USB right out of the box using common apps like VLC Media Player on Mac, Linux, PC, or even Android (see video below).The FLIR Lepton is required for operation of PureThermal 2 (PT2) but is not included by default with purchase. For developers, its reference firmware, viewer software, and hardware schematic are all open source. Just like its PureThermal 1 predecessor, it ships pre-configured to operate as a plug-and-play UVC 1.0 USB thermal webcam that will work with standard webcam and video apps on all major platforms.

The new PureThermal 2 Smart I/O Module with Thermal by FLIR® is a hackable thermal USB webcam for the FLIR Lepton® thermal imaging camera core. No clue- Sounds like you just changing values without understanding what they supposed to be doing.This product is out of stock at GroupGets. This software you talk about and the arbitrary values. (They recommend 25Mhz) Did you provide that? I suspect they did not include a crystal in the LEPTON to keep the size down and embedded devices usually have access to some kind of constant clock any way. Now we know Raspbian is not very great at generating consistent clock rates consistently so you may be experiencing problems with this - The same way may other FLIR'ers are experiencing. I assume you got it hooked up to SPI correctly but one of the problems seems to be the Input Clock rate. So looking around really I noticed the protocol used on the Lepton is VoSPI (Video over SPI) Frankly never heard of that before but its plausible because the frame size is 80 x 60, which is not a crazy amount of data with some kind of AGC applied format which is selectable (Did you select the correct one?)

Flir lepton raspberry pi 4