yes now , i could see but which pins should i select now , how can i know?
Confirm if generate the /boot/jetson-io-hdr40-user-custom.dtbo file but jetson-io. If yes than configurate 40pins to check if able to generate dtb file at /boot and confirm the extlinux.conf
there is no file named ‘jetson-io-hdr40-user-custom.dtbo’ in boot folder
below is my extlinux.conf file
TIMEOUT 30
DEFAULT JetsonIO
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra194-p3668-0001-p3509-0000.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 video=efifb:off nospectre_bhb
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# FDT /boot/dtb/kernel_tegra194-p3668-0001-p3509-0000.dtb
# INITRD /boot/initrd
# APPEND ${cbootargs}
LABEL JetsonIO
MENU LABEL Custom Header Config: <CSI Camera IMX477 Dual>
LINUX /boot/Image
FDT /boot/kernel_tegra194-p3668-0001-p3509-0000-user-custom.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 video=efifb:off nospectre_bhb
What’s the storage? NVME? EMMC?
@ShaneCCC ,I use this command to flash so it seems emmc
sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
HI @ShaneCCC , any further thoughts why user-custom dtb file is not generating in boot folder?
Am i missing any step like including files or something?
The default system image should do it without problem.
Could you verify on devkit.
hi @ShaneCCC ,
i have tried in devkit with the steps you suggested now i could see kernel_tegra194-p3668-0001-p3509-0000-hdr40-user-custom.dtbo in /boot but i could not see the user-ucstom.dtbo when i use CSI connector option.
- Now,which pins should i select below are the default pins?
- What is the next step?
hi @ShaneCCC , any thoughts on this ?
Could you verify on latest JP5 release on devkit.
Thanks
ok, i will try but you told to check with 40 header pins configuration right , i have done and i could generate hdr40.custom .dtbo file ,
- why you asked me to do this , any use if so what can i do next?
- Changing version may or may not result in our way?
If configuration 40 PINs able generate the dtb without problem should no problem for the CSI connector too.
okay so what might be reasons , can you help in debugging ? because changing version may also throw the same results
@ShaneCCC , is there any other way to work on overlay?
hi @ShaneCCC , I have flashed 5.1.4 jetpack
Package: nvidia-jetpack
Version: 5.1.4-b17
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.4-b17), nvidia-jetpack-dev (= 5.1.4-b17)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.4-b17_arm64.deb
Size: 29298
SHA256: 5439dabb8d7a097c215602f7cd11773e4745c5e7d5841d9a0a2551a58b82883e
SHA1: b0c2faa6a9d14e056e394625a11a1a8ed8780327
MD5sum: 05fc4b73de35fd33a535fb887c1947ee
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
now when i use the below command the window opens but closes immediately
sudo /opt/nvidia/jetson-io/jetson-io.py
Do you verify on devkit?
yes,this is on devkit, any thoughts on why the window closes immediately @ShaneCCC ?
Hi @spavan,
Have you tried applying the overlay directly from the command line? You can try something like this:
1. List the available hardware modules
Use the following command to list the hardware modules compatible with your Jetson device:
sudo /opt/nvidia/jetson-io/config-by-hardware.py -l
Example Output:
nvidia@tegra-ubuntu:~$ sudo /opt/nvidia/jetson-io/config-by-hardware.py -l
[sudo] password for nvidia:
Header 1 [default]: Jetson 40pin Header
Available hardware modules:
1. Adafruit SPH0645LM4H
2. Adafruit UDA1334A
3. FE-PI Audio V1 and Z V2
4. ReSpeaker 4 Mic Array
5. ReSpeaker 4 Mic Linear Array
Header 2: Jetson 24pin CSI Connector
Available hardware modules:
1. Camera IMX219 Dual
2. Camera IMX477 Dual
3. Camera IMX477 Dual 4 Lane
4. Camera IMX477-A and IMX219-C
Header 3: Jetson M.2 Key E Slot
No hardware configurations found!
2. Select and apply the overlay
To apply an overlay, use the following command (replacing 2 and the module name with the appropriate header number and hardware module name):
sudo /opt/nvidia/jetson-io/config-by-hardware.py -n 2="Camera IMX477 Dual"
Example Output:
nvidia@tegra-ubuntu:~$ sudo /opt/nvidia/jetson-io/config-by-hardware.py -n 2="Camera IMX477 Dual"
Modified /boot/extlinux/extlinux.conf to add following DTBO entries:
/boot/tegra234-p3767-camera-imx477-dual.dtbo
Reboot system to reconfigure.
Note:
Make sure to verify that the extlinux.conf file contains the custom DTBO generated to ensure it is being used correctly.
Additional suggestion:
It is a good idea to perform this test with a freshly flashed system to avoid possible conflicts with previous configurations or tests performed.
Hope this helps! Let me know if you need further assistance.
Regards,
Oscar Mendez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com
thank you @oscar.mendez1 , i will try and let you know
1 Like