Hi @joe, @veye_xumm, I have now tested the VEYE-MIPI-IMX462 on the Seeed reComputer J4011B with Jetpack V6.1, and found the same result as at V6.2, i.e., the Veye I2C address 0x3b is not detected. And this is even though Jetpack V6.1 works on the J401 carrier board (with the USB hub firmware patch applied).

Seeed Tech Support are monitoring the situation, and it may be the J401 B based reComputers are now a priority for Seeed. There is a chance that some further information could also inform their response to the lack of video device generation on the J401 at Jetpack V6.2.

I can test the J4011B with Jetpack V6.1 using the modified camera @veye_xumm sent me with the I2C address 0x22. This was when we were diagnosing the original detection problem on the J401. As long as the CSI pins have not been remapped, the issue could be another version of the USB hub firmware fault (e.g., maybe the J401B mini-PCIe expansion board is doing something with I2C). If the 0x22 address is detected on the J4011B it should prove to Seeed that the issue it not the Veye driver. But I would appreciate help with the Device Tree overlay.

I have changed the references to 0x3b in the DTS and DTSI include source to 0x22, but am getting errors like:

i2c i2c-9: of_i2c: modalias failure on /bus@0/cam_i2cmux/i2c@1/rbpcv3_veyecam_c@3b
i2c i2c-9: Failed to create I2C device for /bus@0/cam_i2cmux/i2c@1/rbpcv3_veyecam_c@3b

I am not very familiar with DTS files, and clearly I have missed something, can you help with this please?

Thanks
John

Hi @joe, @veye_xumm I have just encountered this issue, i.e., with a VEYE-MIPI-IMX462 camera on the Seeed J401 carrier board, flashed with Jetpack V6.2, except in this case with an Orin NX 8GB module.

It previously did work on exactly the same board (i.e., the /dev/video0 device was created) at Jetpack V6.1. Does that help explain anything?

Any ideas? (I need Jetpack V6.2 for PPP support, which was omitted from Jetpack V6.1).

Thanks
John

PS I found the Seeed reComputer J4011B with Jetpack 6.2 does not detect the Veye I2C address even though it is supplied with the "fixed" USB hub firmware (version 08B3). Very similar to the J401, but with an internal USB connection that is used for a mini-PCIe adapter "extension board" (perhaps this has upset the firmware fix).

@howard, @vincentng, @veye_xumm is making some progress with Seeed after trying to get a response from them many times over (thanks!). We need the highly sensitive NIR IMX462 for our application and have tuned our code for the Veye ISP. @Howard what is the A206? Perhaps it could help us.

@veye_xumm It is good news that you are finally getting a response from Seeed Studio, but do you think the fault could be corrected by software or might it require a hardware redesign of the Seeed Carrier Board?

@veye_xumm Understood, and thanks for the Plink reference, which looks good. However, this has a larger format and would not fit in our unit.

@vincentng We are close to giving up on the Seeed Orin Nano carrier board, and will try to return the units we bought.

I have the same question for Orin Nano Carrier boards, do you have any advice on boards that do work with the Veye IMX462? (And that have the same dimensions, we don't have room in our device for something bigger).

@vincentng Thanks for raising this on the Seeed Forum. I have been emailing Seeed Tech suppport techsupport@seeed.io, and they were to get a Product Manager to assist, but nothing has happened.

@veye_xumm Same problem for us! I very much appreciate your efforts to help solve this.