Custom camera driver for TX2 NX

Please update to r32.7.2 for native support IMX477 by jetson-io

Thanks

I wish that were the case but it doesn’t appear to be so for the TX2 NX. I downloaded a clean version of r32.7.2, removed my nvme ssd just to ensure there were no lingering files, then flashed the emmc. I ran jetson-io and just as with version 32.6.1, there are only two default options:

  • “Configure Jetson 40pin Header”
  • “Configure Jetson M.2 Key E Slot”.

I figured maybe the drivers were missing so I followed Seeed’s documentation and flashed with their .dtb and .cfg files with no difference. Still only two options. I ran a diff on the source for 32.6.1 vs 32.7.2 and nothing stands out that would suggest the imx477 is supported in this version.

@tzjay
It’s my mistake, current TX2 NX still not support IMX477 yet.
Will check it if the plan for it.

Thanks

Okay, thanks for confirming @ShaneCCC. In general, I don’t see much support for the TX2 NX yet it is the only Jetson module in stock (under $2000). Hopefully there are already efforts underway to improve the support and documentation (Nvidia and partners).

1 Like

Can someone clarify what is the recommended approach to understand the code flow of ov5693 image sensor driver like I am unable to interpret like where the process/program starts and ends in driver code after loading as a module.

Hello @naradhamdharanija24,

A rough idea of how a driver works is the following:

  1. The board boots and loads the device tree.
  2. The camera driver is loaded once the device tree module with the matching compatible is loaded.
  3. The driver runs the probe function which checks if an adequate HW is connected. This is done by powering on the device, and trying to interact with it through i2c.
  4. If the probe goes well then a video device is registered.
  5. If a user tries to interact with the video device, to capture for example. The driver powers on the camera, writes the required configuration and starts capturing.

That is a very very rough and simplified version of how a driver works. We hope that helps. However, if you have further questions or require further assisntance, please do not hecitate to reach out.

regards,
Andrew
support@proventusnova.com