Hello,
Is there a recommended Camera for working w/ the FLIR Lepton v2 breakout?
Seth
P.S. I have found some from the digikey.com site but I am not sure exactly which one would better work or better suit the needs of my experiments. Please reply when you have time.
Hi @silver2row, this one: (80x60)
https://www.digikey.com/en/products/detail/flir-lepton/500-0659-01/5215153
FLIR stopped making the non-shutter models.
I’ve not tried this model: (80x60)
https://www.digikey.com/en/products/detail/flir-lepton/500-0763-01/6250105
These require a new driver… (160x120)
https://www.digikey.com/en/products/detail/flir-lepton/500-0726-01/6163867
https://www.digikey.com/en/products/detail/flir-lepton/500-0771-01/7606616
Edit: Instead of the Flir Lepton v2, take a look at this adapter first:
https://www.digikey.com/en/products/detail/groupgets-llc/PURETHERMAL-2/9866290
The linux UVC driver can be found here: https://github.com/groupgets/purethermal1-uvc-capture
Regards,
Hello,
I already ordered the FLIR Lepton v2 version. Do those instructions still hold relevant to the FLIR Lepton v2?
…
I am asking b/c ordering another item, the PURE Thermal from GroupGets, is not in my near future. If that is the only way around the instructions, I will think about it.
Seth
P.S. I know this is not your issue. I see your edit and I was just commenting. I may try the old way, circa '18, to get this up and running but I may follow the edit in your last post too. I will update you soon.
My instructions for the BeagleBone family with the 80x60 based sensors work fine with the Lepton v2.
Regards,
Sir,
Even though the part is obsolete, will I still be able to purchase it and use it?
Seth
Correct, as long as we list stock you’ll be able to still purchase it.
Regards,
Hello Sir/@RobertCNelson ,
Seth here. Okay, I finally ordered one of the two left of this specific model that has been tested.
…
I will keep you updated on this thread if I come across any issues. Thank you for making this available.
Seth
Hello @RobertCNelson ,
Are those FLIR Lepton instructions on the eewiki for the BBB/BBG supposed to get the camera working on the LCD?
Seth
P.S. I think I may have misunderstood.
LCD/HDMI, it’s just a qt5 application…
Regards,
Hello Sir,
Are there any LEDs on the FLIR Lepton v2 board to show that it is powered?
Seth
Hello @RobertCNelson ,
Is there a trick or some procedure you know about that will get the video from the FLIR Lepton on the LCD or a server?
Seth
P.S. The reason I am asking is b/c historically I have used USB webcams for video access instead of SPI devices. This is the error in question:
bbb: cannot connect to X serverHello Sir,
I found some good docs. on the FLIR module in question. I apologize for misunderstanding the instructions on the eewiki.
Seth
P.S. I figured you were handing out free work for some reason. Anyway, if you are using this item, v2 and FLIR Camera, let me know. Any of your ideas that prove valuable would be much appreciated. Anyway, it is late and I am off to read more on the datasheet and interface description document.
Nope. there are no LED’s on board.
The v2 board adapter works with the qt5 application shown in the eewiki directions.
If you’d like to use normal /dev/video etc, you need to switch to the PureTermal adapter previously mentioned…
Regards,
Hello,
Okay…as per usual, I must have made an error some where. Off to reread the docs. Thank you for updating me.
Seth
Hello Sir,
Sorry for earlier. I was trying to vent. Not your issue. Okay. So, the qt app works but not on my LCD for now. This is of no concern to you. I understand.
Seth
P.S. I will just find the mfg. and see if they have any info. on the actual whereabouts of the chips onboard the Cape.
The qt app is just a xorg/windowed application. Are you running X? Does the window pop-up? You’ll either get a picture, or a red box… The red box, means a communication failure on the spi bus…
Regards,
Hello Sir,
@RobertCNelson …I get only a pop up on my vncserver when running ./bbb w/ the red square and the FFC button. I do not get a pop up on the LCD Screen.
My LCD is working but I am not sure exactly what to connect so far. I have all my LCD pins, ADC, i2c, CS, MISO, and CLK pins attached along w/ the power pins/GND pins to power the Cape.
I have my board, the BBGW, as my master and two slaves, i.e. the v2 Lepton w/ camera and the LCD screen. Does this sound correct?
Seth
P.S. Just for clarification, I am receiving no picture or red box on the LCD for now. Oh and sir, this is the Cape I currently am using: Seeed Studio BeagleBone® Green LCD Cape with Resistive Touch - Seeed Wiki .
I found the Overlay. I will adjust it accordingly.
Wait! BBGW, why did you label this thread as BBB?
There’s a bug on the BBGW design for SPI0, all SPI transactions are corrupt on that interface…
Use Derek Molloy’s spitest:
./exploringBB/chp08/spi/spidev_test/spidev_test -D /dev/spidev0.0
Please report:
sudo /opt/scripts/tools/version.sh
Regards,
Hello,
Error: src/arm/BB-BONE-LCD5-01-00A1.dts:51.3-4 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [Makefile:173: src/arm/BB-BONE-LCD5-01-00A1.dtbo] Error 1
make: *** [Makefile:119: all_arm] Error 2
This above info is the error in the update to the dts file and then w/ the command ./install.sh.
…
debian@beaglebone:~/bb.org-overlays$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[fe926a6a4cf5805041878d7df82b58c00b4f902e]
eeprom:[A335BNLTGW1ABBGW16060875]
model:[TI_AM335x_BeagleBone_Green_Wireless]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-00002-g07d5700e21 (Mar 06 2020 - 11:24:55 -0600)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-bonegreen-wireless-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BBGW-WL1835-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-BONE-LCD5-01-00A1]
UBOOT: Loaded Overlay:[BB-SPIDEV0-00A0]
kernel:[4.19.94-ti-r57]
nodejs:[v10.23.1]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr1=/lib/firmware/BB-SPIDEV0-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20201221.0-0~buster+20201221]
pkg:[bb-customizations]:[1.20201105.0-0~buster+20201110]
pkg:[bb-usb-gadgets]:[1.20200504.0-0~buster+20200504]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BB-BONE-LCD5-01, coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[ 92.795901] remoteproc remoteproc0: wkup_m3 is available
[ 92.835797] remoteproc remoteproc0: powering up wkup_m3
[ 92.835832] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[ 92.836119] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[ 1.233889] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[ 1.630725] pinctrl-single 44e10800.pinmux: pin PIN30 already requested by gpio-leds-cape-lcd; cannot claim for leds
[ 1.641444] pinctrl-single 44e10800.pinmux: pin-30 (leds) status -22
[ 1.647868] pinctrl-single 44e10800.pinmux: could not request pin 30 (PIN30) from group pinmux_wl18xx_pins on device pinctrl-single
[ 1.838952] pinctrl-single 44e10800.pinmux: pin PIN12 already requested by 47810000.mmc; cannot claim for gpio_keys
[ 1.849711] pinctrl-single 44e10800.pinmux: pin-12 (gpio_keys) status -22
[ 1.856658] pinctrl-single 44e10800.pinmux: could not request pin 12 (PIN12) from group pinmux_bb_lcd_keymap_pins on device pinctrl-single
dmesg | grep gpio-of-helper
[ 1.246479] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
Okay…you are right. I am using the BBGW and I was not thinking of the differences.
Seth
P.S. If necessary, I can change boards if there are no options for this specific board for now.