Posts made by Haxerus

@Alex-Kushleyev I made the following changes.

1. Modified the DTS files as stated prior.
2. Flashed the devcfg.mbn file from SDK 1.0.0
3. I did not need to configure the level shifter actually. The port worked in SPI mode even without running voxl-gpio -w 67 1. Running the command doesn't seem to change anything.

I used Channel 1 on /dev/i2c-0 for the second lepton. I simply wrote TCA9543A_CHANNEL_1_ENABLE to TCA9543A_CONTROL_REGISTER in voxl-lepton-server. I pretty much followed what was described here.

@Alex-Kushleyev sure thing. As per your suggestion, I modified voxl-lepton-server by moving all the Lepton camera-specific logic into a C++ class and added locks to any I2C operations to prevent race conditions. I then just created 2 instances of the LeptonCamera class I made which parse and publish the camera feeds to their own pipes which I can view in voxl-portal.

I didn't need to disable any I2C interface for the second Lepton. I'm not too sure what you were referring to by that.

In regards to the horizontal line artifacts, those don't seems to consistently appear and I don't know what causes it. I'll investigate it further.

My next steps are to get the Leptons working with voxl-open-vins-server. One question I had was that our VOXL 2 Mini appears to be running a service called voxl-lepton-tracker however I cannot find the source code for this anywhere on the voxl public GitLab. Was it removed or hidden?

@Alex-Kushleyev Hi, I'm working with @cbay on this project and I just wanted to report that I was able to modify voxl-lepton-server with your suggestions and achieved dual lepton camera streaming into voxl-portal.

Ok, I was actually able to get J10 to work as an SPI port by following this thread. I was also able to get video feed from the lepton on slot #2 on the M0188 with this approach. I still don't know if using the devcfg.mbn file from SDK ver 1.0.0 is really the "proper" thing to do, it feels like it could lead to issues down the road. An official answer regarding J10 in SPI mode would be greatly appreciated.

@Alex-Kushleyev @modaltb If you have any insights that would be appreciated. Thanks.

Hello,

I am trying to get the M0188 board working with the VOXL 2 Mini to control 2 Leptons but I've hit a roadblock getting the J10 port to switch from UART to SPI. I've rebuilt the kernel with the following modifications to the DTS files on meta-voxl2-bsp.

m0104-kona.dtsi:

• added spi14 = &qupv3_se14_spi

m0104-modalai-qupv3.dtsi:

• changed status of &qupv3_se14_2uart to "disabled"
• changed status of &qupv3_se14_spi to "ok"
• added the following to &qupv3_se14_spi

spidev@0 {
    compatible = "spidev";
    reg = <0>;
    spi-max-frequency = <50000000>;
};

I am not sure these are the only modifications required as I am not familiar with Linux kernel development, I just followed the documentation and commit history in meta-voxl2-bsp.

After building and loading the kernel I run voxl-gpio -w 67 1 as mentioned here. When I run ls /dev/ I am able to see /dev/spidev14.0. I tried testing it with this tool and a loopback cable that connects MISO to MOSI but it just hangs. That tool works fine with spidev0.0.

I modified voxl-lepton-server to use the 2nd I2C channel for Lepton #2. I then tried to change /etc/modalai/voxl-lepton-server.conf to use SPI bus id 14 but it caused voxl-lepton-server to hang, seemingly not getting any data from the SPI port.

Any guidance on how to properly use J10 as an SPI port and how to get voxl-lepton-server to read from it would be greatly appreciated.