Posts made by rob77

JUST fixed it sudo -s

want to say thank you for your help and patience with me, a person who has very little experience using linux. the camera is perfect for my project and i will be using it to learn more.

@veye_xumm thanks that fixd the file into unix and i was able to open it. i then enter the day/night command

rob@rob-desktop:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ ./veye_mipi_i2c.sh -w -f daynightmode -p1 0xFE -b7
should be root!

it says should be root? so i redo it as root superuser, but got file/directory error. i tryed other types of commands but getting same error.

rob@rob-desktop:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ sudo -i ./veye_mipi_i2c.sh -w -f daynightmode -p1 0xFE
[sudo] password for rob: 
-bash: ./veye_mipi_i2c.sh: No such file or directory

@veye_xumm

rob@rob-desktop:~$ cd /home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/
rob@rob-desktop:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ ./veye_mipi_i2c.sh
./veye_mipi_i2c.sh: line 1: $'\r': command not found
./veye_mipi_i2c.sh: line 3: $'\r': command not found
./veye_mipi_i2c.sh: line 7: $'\r': command not found
./veye_mipi_i2c.sh: line 8: $'\r': command not found
./veye_mipi_i2c.sh: line 9: $'\r': command not found
./veye_mipi_i2c.sh: line 10: $'\r': command not found
./veye_mipi_i2c.sh: line 11: syntax error near unexpected token `$'\r''
'/veye_mipi_i2c.sh: line 11: `print_usage()

rob@rob-desktop:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ ./veye_mipi_i2c.sh -w -f daynightmode -p1 0xFE -b7
./veye_mipi_i2c.sh: line 1: $'\r': command not found
./veye_mipi_i2c.sh: line 3: $'\r': command not found
./veye_mipi_i2c.sh: line 7: $'\r': command not found
./veye_mipi_i2c.sh: line 8: $'\r': command not found
./veye_mipi_i2c.sh: line 9: $'\r': command not found
./veye_mipi_i2c.sh: line 10: $'\r': command not found
./veye_mipi_i2c.sh: line 11: syntax error near unexpected token `$'\r''
'/veye_mipi_i2c.sh: line 11: `print_usage()

@veye_xumm
i have the files and tryed this.

rob@rob-desktop:~$ ./veye_mipi_i2c.sh
bash: ./veye_mipi_i2c.sh: No such file or directory
rob@rob-desktop:~$ '/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh' 
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 1: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 3: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 7: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 8: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 9: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 10: $'\r': command not found
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 11: syntax error near unexpected token `$'\r''
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: line 11: `print_u'age()
rob@rob-desktop:~$ 

i thought maybe it needed a dynamic loader so i did a check.

rob@rob-desktop:~$ ldd '/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh' 
	not a dynamic executable
rob@rob-desktop:~$ file '/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh' 
/home/rob/nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh: ISO-8859 text, with CRLF line terminators

@veye_xumm ok.
running the files just ends with error no such file or directory. ive tryed running them in terminal and vim with no luck. there is clearly something im missing or not understanding, unlike the raspberry pi you have to enable ./enable_i2c_vc.sh but on jetson nano it is already enabled meaning first steps are not required, so i continue with commands that should work but for some reason are not. is there another directory the files are ment to go in? or is there another way to control day/night mode?

@veye_xumm i understood i needed to use those files from the wiki but what do i do with them? do they go in /boot/veyecam directory?

@veye_xumm thank you for that i tryed ./veye_mipi_i2c.sh -w -f daynightmode -p1 0xFE -b 7 and 8 to get the ir mode but it still dosent seem to work. i end up getting
bash: ./veye_mipi_i2c.sh: no such file or directory
their is probably a step im missing due to still being new to the nano.

@veye_xumm ah i see, i was mistaken thinking it used another I2C conection, cool i unpluged the Aux IIC and did a check, i have a nano B01 and checked the i2cdetect bus 7 and 8 and yep it found it connected, strangely bus 6 is also active even tho nothing is being used on it i think. that solves that.

my next problem is useing the day/night comand, im just not sure how to use it as veye_mipi_i2c.sh dosent do anything.
my goal is while the camera is on that i can switch between IR filter on and off easly.

i see my confusion now from the wiki that they are bus numbers

however i can not seem to find the i2c bus for the camera, everything should be connected correctly but command i2cdetect -y -r 1 is not finding anything even tho it is connect to bus 1
and i am now also confused on how to use the cmd sudo ./veye5_mipi_i2c.sh -w -f daynightmode -p1 [0,2]
please tell me how to do this sorry for being noob.

Hello, im seeking some clarification on using the I2C on VEYE-MIPI-IMX385 on the jetson nano. my main goal is to find the easiest way to use the day/night mode IR CUT and from what the wiki shows its very simple to use the i2c, but im confused about the pin layout. on IMX385 wiki J7 are the Auxiliary IIC and so i connect to the jetson pin 3 SDC and pin 5 SCL, but also on the wiki http://wiki.veye.cc/index.php/I2c_bus_number_and_video_node
it shows
1.2.3 Nano B01
i2c num 7 or 8
1.2.4 Nano A02, Nano 2GB
i2c bus number is 6.

they are not I2C pins on the jestson nano, can i just check if this is correct.

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.

@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.

@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: t210ref

I 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.

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?

@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.

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

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.

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 directory

here 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

@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 denied

i 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.