Line 12: |
Line 12: |
| *Jetpack4.5,L4T r32.5 | | *Jetpack4.5,L4T r32.5 |
| *Jetpack4.5.1,L4T r32.5.1 | | *Jetpack4.5.1,L4T r32.5.1 |
| + | *Jetpack4.6,L4T r32.6.1 |
| | | |
| We provide two ways to do so: '''Prebuilt Binaries''' or '''Source Code. Yes, It's Open Source!''' | | We provide two ways to do so: '''Prebuilt Binaries''' or '''Source Code. Yes, It's Open Source!''' |
Line 149: |
Line 150: |
| | | |
| <code>FDT /boot/<DTB file name></code> | | <code>FDT /boot/<DTB file name></code> |
| + | |
| + | Note: <DTB file name> should be replaced with the corresponding dtb name of the mainboard, ensure that the file specified in the FDT line actually exists correctly. |
| | | |
| Effective after restart. | | Effective after restart. |
Line 276: |
Line 279: |
| <code>ls /sys/bus/i2c/drivers/</code> | | <code>ls /sys/bus/i2c/drivers/</code> |
| | | |
− | There should have veye327 csx307 cssc132 directory. | + | There should have veye327 veyecam csx307 cssc132 directory. |
| =====For DTB===== | | =====For DTB===== |
| DTB varies from platform and from camera module. | | DTB varies from platform and from camera module. |
Line 317: |
Line 320: |
| Run the following command to confirm whether the camera is probed. | | Run the following command to confirm whether the camera is probed. |
| | | |
− | *For VEYE-MIPI-327 | + | *For VEYE-MIPI-327(using VEYE-MIPI-327 dtb) |
| | | |
| <code>dmesg | grep veye327</code> | | <code>dmesg | grep veye327</code> |
Line 326: |
Line 329: |
| | | |
| <code>subdev veye327 X-003b bound</code> | | <code>subdev veye327 X-003b bound</code> |
| + | |
| + | *VEYE-MIPI-X(using VEYE-MIPI-CAM2M dtb) |
| + | |
| + | <code>dmesg | grep veye</code> |
| + | |
| + | The output message appears as shown below: |
| + | |
| + | <code>camera id is veyecam</code> |
| + | |
| + | <code>sensor is IMX327/IMX462/IMX385</code> |
| + | |
| + | <code>subdev veyecam X-003b bound</code> |
| | | |
| *For CS-MIPI-IMX307 | | *For CS-MIPI-IMX307 |
Line 414: |
Line 429: |
| For AGX-Xavier and TX2, ADP-N1 has 6 MIPI CSI-2 interface [A-F],the corresponding i2c address is[30-35]. | | For AGX-Xavier and TX2, ADP-N1 has 6 MIPI CSI-2 interface [A-F],the corresponding i2c address is[30-35]. |
| | | |
− | For Xavier NX, the corresponding i2c address is 9 and10. | + | For Xavier NX, TX2 NX,the corresponding i2c address is 9 and10. |
| | | |
− | For Nano A02, the corresponding i2c address is 6. | + | For Nano A02,Nano 2GB, the corresponding i2c address is 6. |
| | | |
| For Nano B01, the corresponding i2c address is 7 and 8. | | For Nano B01, the corresponding i2c address is 7 and 8. |
Line 422: |
Line 437: |
| It is also the same as the X part of dmesg message: | | It is also the same as the X part of dmesg message: |
| | | |
− | <code>subdev veye327 X-003b bound</code> | + | <code>subdev veyeX X-003b bound</code> |
| | | |
| <code>subdev csimx307 X-003b bound</code> | | <code>subdev csimx307 X-003b bound</code> |