SOLVED VEYE-MIPI-IMX385 on jetson nano
-
@veye_xumm thank you, i have unpacked the image been able to open the boot but when i try to copy the image to the kernel i get :permission denied.
recharge@R-desktop:~$ cd /home/recharge/nvidia_jetson_veye_bsp/kernel_image/ recharge@R-desktop:~/nvidia_jetson_veye_bsp/kernel_image$ tar -xzvf Image_l4t_r32.7.1_veyecam.tar.gz Image recharge@R-desktop:~/nvidia_jetson_veye_bsp/kernel_image$ sudo cp ./Image /boot/Image [sudo] password for recharge: recharge@R-desktop:~/nvidia_jetson_veye_bsp/kernel_image$ sudo cp </home/recharge/nvidia_jetson_veye_bsp/kernel_image/Image> /Image /boot/Image -f bash: /Image: Permission denied recharge@R-desktop:~/nvidia_jetson_veye_bsp/kernel_image$ sudo cp <'/home/recharge/nvidia_jetson_veye_bsp/kernel_image/Image_l4t_r32.7.1_veyecam.tar.gz'> /Image /boot/Image -f bash: /Image: Permission deniedi then unpacked both L4t-r32.6.1 and L4t-r32.7.1 and tryed to path to image directory but still :permission denied . not working.
-
This post is deleted! -
i am now getting bash error when trying to cp the files, is my command wrong? when check boot no files are there.
here i used root to try and move/copy image to boot
root@R-desktop:/home/recharge# sudo cp </home/recharge/nvidia_jetson_veye_bsp/kernel_image/Image> /boot/veyecam -f bash: /boot/veyecam: Is a directoryhere i tryed to move/copy dtb file to boot but got same response
root@R-desktop:/home/recharge# sudo cp /home/recharge/nvidia_jetson_veye_bsp/dtbs/Nano/JetPack_4.6.1_Linux_JETSON_NANO_TARGETS/dts dtb>/</home/recharge/nvidia_jetson_veye_bsp/dtbs/Nano/JetPack_4.6.1_Linux_JETSON_NANO_TARGETS/dts dtb/VEYE-MIPI-CAM2M/tegra210-p3448-0000-p3449-0000-b00.dtb> /boot/veyecam/ -f bash: /: Is a directory -
@rob77 Sorry, I'm back from a very short break.
The <> is not required in the command, please remove it.
This indicates variables in my formulation. -
hello @veye_xumm thanks for your help i feel so stupid over a mistake like that. the commands now work and i was able to
cp the files where i needed. i checked the extlinux.conf and could see it was linking up to old arducam dtb, so i updated it and now i get this. its unfortunately not responding and just flashes on the screen.
-
Hi @veye_xumm with a fresh sd card i had, i re-did everything in order from the wiki. i am now getting this error. is this due to the extlinux.conf ?
[0_1663700592838_extlinux.conf](Uploading 100%) [0_1663700657221_extlinux.conf](Uploading 100%) extlinux.txt -
@rob77 I have a feeling you are correct about Image and dtb.
Now all you have to do is make sure the hardware connections are correct. -
@veye_xumm i checked the connections and it seems they are fine now as it is showing ''sensor is IMX385'', but its still not working, i rebuilt the sd card and started from scratch i followed the wiki and checked the conections, all ok. but i am getting this result when rebooting after editing the extlinux.conf. it puts the nano in a constant reboot phase.
-
@rob77 said in VEYE-MIPI-IMX385 on jetson nano:
i checked the connections and it seems they are fine now as it is showing ''sensor is IMX385'', but its still not working, i rebuilt the sd card and started from scratch i followed the wiki and checked the conections, all ok. but i am getting this result when rebooting after editing the extlinux.conf. it puts the nano in a constant reboot phase.
I think there is something wrong with your rootfs.
Maybe you have a problem with your tf card? Is there another tf card you can try? -
hi @veye_xumm ive tryed another better fresh sd card, did exactly the same as before and still not working. is the IMX385 designed for nano? ive been looking over the forum and have not seen anyone else useing it with a nano. sorry im starting to get a bit frustrated with how complicated it is to use this. what can i do now?
-
@rob77 Yes, everyone is using it normally.
I now suspect you use the wrong version. -
@veye_xumm ok i will go over what version i am using and the steps i am doing, hopefully it will clarify any mistakes.
and you can correct me if i am wrong.
I first check the connections to the camera are fine.cat /etc/nv_tegra_release
L4T REVISION: 7.1, BOARD: t210refI download the bsp to the nano, i then unpack it.
I find and unpack kernel_veyecam_config_r32.7.1 so i have the Image file.
I then cp the file to /boot/Image -f which copy's and replaces the original Image.
Then sudo depmod to register it.
Then create sudo mkdir /boot/veyecam/
I then find the dtb file i need in JetPack_4.6_Linux_JETSON_NANO_TARGETS/dts dtb
file VEYE-MIPI-CAM2M and sudo cp the tegra210-p3448-0000-p3449-0000-b00.dtb file to The veyecam folder.
I then go in boot and open extlinux to edit the extlinux.conf adding FDT /boot/veyecam/tegra210-p3448-0000-p3449-0000-b00.dtb
I then reboot. -
@rob77
I think you should use JetPack_4.6.1_Linux_JETSON_NANO_TARGETS dts,instead of 4.6 version.
I'm not sure that's the root cause, but that's all I can think of right now. -
@veye_xumm ok i tryed JetPack_4.6.1_Linux_JETSON_NANO_TARGETS dts dtb and it did not work, i ended up with the same bash error.
please look into this for me when you have time i would apreachate it alot as i really want to use this camera from my project. i will try other methods on my end and update this if i find a result. from what i have researched adding a FDT entry in extlinux.conf could cause boot failure. -
@rob77
I see no problem with your operation.
The dtb defines the peripherals of the core and base boards and needs to be consistent with the actual core and base boards.
Is it possible that your jetson nano is not the standard Nvidia b01 version of the dev kit? -
hi @veye_xumm i have now got it working and its really good camera. i had to change the /mmcblk0p1/sda1/' /boot/extlinux/extlinux.conf i believe that mabye my jetson nano thinks its on a custom base board, so changeing the mmcblk0p1 to mmcblk1p1 worked.
thank you for all your help.
-
