Hello,
we have bought an IMX390C camera sensor.
It is from SeeedStudio bought via DigiKey because out of stock directly from Seeed.
Model: SG2-IMX390C-MIPI-H120H
Interface: MIPI CSI 4-Lane
It is explicitely declared as compatible with Jetson Orin Nano development board and Jetson Orin Nano.
Citation: “It is compatible with the NVIDIA Jetson Orin Nano.”
The same is noted at the page of “sensing”, what seems to be the original manfacturer.
and at the camera page from Nvidia.
I have found, that an IMX390 driver is hard compiled into the Nvidia Linux kernel r35.4.1 but this contains information, that it is designed for GMSL interface converter.
I am not shure, if this driver is useable for MIPI/CSI without GMSL anyhow.
The camera type can not be selcted via the “jetson-io.py” tool.
It seems, that there is not the right *.dtbo file available for tegra234, Jetson version 3767 and board 3768.
Hello,
i am currently doing this but currently no success. really nothing - no useful answer anyhow from seeed and digikey.
i am afraid, that this attempt will fail.
IMX390 (with SerDes chip) by default only support with AGX Xavier and AGX Orin platforms.
there’s NO IMX390 device tree for Orin NX or Orin Nano.
so…
they should at least sharing you IMX390 device tree (or, even DTBO) for Orin Nano series.
i am facing the issue while testing the camera(imx219) for my jetson nanon board and getting the erorrs as mentioned below. many people are facing the same issue but there is no clarified answer for that till now, please help me to solve that @JerryChang
its reporting No cameras available errors, please narrow down by checking your device registration process.
besides, please file a new forum discussion thread for tracking.
Hello,
the difference is, that this camera does not have an SerDes chip (for GMSL or whatever).
The camera is directly connected to the CSI interface.
The Nvidia driver seems to need SerDes chip and i do not know, if the driver can handle IMX390 without SerDes chip anyhow?
Do you know this? Otherwise an dtbo file will not solve the issue.
Query state: Currently no answer anymore from suppliers/distributors (DigiKey, Seeed, Sensing). Lets wait some time …
it’s device tree to define port-binding for device registration.
it’s SerDes chip to serializer/deserializer the MIPI signaling.
according to above, it should works if you’re using the exactly same camera module by updating device tree blob.
anyways,
this issue will require our camera partner to do the support, let me add @Luke.Li and @Peter.Xu here to help you.
Hi Matthias,
In response to your problem, I have already replied to you via email. If there are any further issues, please feel free to let me know. Thank you.
Hi felix.krabbes.lzc,
You can download the driver package for this camera from the following GitHub address. Please refer to the documentation in the driver package to set up the camera. SENSING-Technology/nvidia-jetson-camera-drivers (github.com)
Thanks.
