[beagleboard] Re: Flir Lepton 3 and I2C

2018-04-16 Thread Davide Aguiari
You need to config-pin your I2C and SPI pins first, then set you i2c-X device in bbb_I2C.c so you can read data. No need to edit uEnv.txt Il giorno domenica 15 aprile 2018 04:31:52 UTC+2, jesse...@capecodmakers.org ha scritto: > > Did you find the config-pin statements in the uEnv.txt to be

[beagleboard] Re: Flir Lepton 3 and I2C

2018-04-14 Thread jesse . craig
Did you find the config-pin statements in the uEnv.txt to be necessary, or just changing the I2C bus in the bbb_I2C.c file? On Monday, December 18, 2017 at 2:46:35 AM UTC-5, Davide Aguiari wrote: > > I solved this problem by editing > Lepton3_BBB/grabber_lib/Lepton_SDK/src/bbb_I2C.c > (or

[beagleboard] Re: Flir Lepton 3 and I2C

2017-12-17 Thread Davide Aguiari
I solved this problem by editing Lepton3_BBB/grabber_lib/Lepton_SDK/src/bbb_I2C.c (or rasp_I2C.c) where it uses open("/dev/i2c-2 ) instead of libmpsse. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

[beagleboard] Re: Flir Lepton 3 and I2C

2017-12-16 Thread Davide Aguiari
Actually seems that the mCciPort (first parameter in LEP_OpenPort) doesn't stand for the I2C bus but for a user-defined id number for the camera. So actually the problem moves to "How do tell the SDK to read from I2C-2 instead of I2C-1"? The SDK uses libmpsse, I think. In order to test the