Now i have to flash my customizing image as well as device tree to the original BSP. Earlier i have used to flash the image of jetson xavier nx with substituting the image and device tree. But here i dont know how to proceed?
For driver we need to replace the .c file in media/i2c/. But for device tree, which is the right place to include the customizing device tree in customizing kernel. (For xavier nx, under jakku platform i used to register)
Could you please give any suggestion to move forward for this flashing?
I have gone through the document which you shared above. Documents saying that how to copy the dtb and image from customized kernel to original bsp. But i am asking, for orin how to add the device tree in customizing kernel?
Please correct my below interpretation.
Compilation process of driver, device tree and modules are same for all the platform right?
But before compilation, In which directory we need to place the new device tree (.dtsi) for orin nx. Can you please tell me how to proceed further?
For your kind information, i am using custom board from avermedia. I have used below command for flashing.
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal`
As per your reply, I have searched the nv-public under the directory of t23x. But there is no directory called nv-public. I am using jetpack 5.1.3. So, I found five directory under t23x which is common,concord,mandalore,p3768,prometheus.
There is no nv-public.
If I do the change in directory means, it should update the original bsp after flashing right?
Please tell me the exact directory for add the dtsi file.|
# In Linux_for_Tegra
./source_sync.sh -k -t jetson_35.3.1
You could modify it in Linux_for_Tegra/sources/hardware/nvidia/platform/t23x/p3768/kernel-dts
You could get more information from Kernel Custionization