Boot folder is empty, where are the system files?

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hey guys,

I’m about to try flashing a modified a dtb file. Just to play it super-safe, I thought that I might try pulling the existing dtb file off of the Orin first and comparing it to a compiled dtb file with no modifications. They should be bit-for-bit identical.

But, our Orin has a “/boot” folder which is completely empty. And there’s no “vmlinuz” file or anything like that in the root either. So I’m sort of puzzled at where this is actually stored. In addition to the main partition, “vblkdev0p1”, there’s the data partion, “sda”. It’s not there either. And it’s not on the other two recognized partitions on the system, “vblkdev1” and “vblkdev3”.

1 Like
3

Dear @jcatlin,
May I know which dtb file you want to modify?

4

In my case, I’m modifying camera frame sync properties. So that means modifying files in “tegra234-p3710-0010.dtsi” which will in turn effect the “tegra234-p3710-0010-a*.dtb” files.

But beyond this specific case of these dtb files I’m modifying, I actually really am curious where all of the system files are stored on this setup.

Thank you!

5

By the way, I’m aware that the files can also be stored directly on partitions, outside of the normal filesystem. The problem is, I just can’t find any partitions that appear to be storing that. I’ve attatched the output of running “parted -l”. There aren’t any partitions named “kernel-dtb” or anything like that.
parted.txt (2.4 KB)

6

Dear @jcatlin,
DRIVE OS is different because of hypervisor. The kernel is loaded by partition loader from kernel partition instead of vmlinuz in /boot of rootfs as part of hypervisor (bootrom → mb1 → mb2 → pl → kernel) and it’s the same as kernel device tree kernel-dtb. The kernel partition is not accessible by default.

In the boot log, we can see messages like below

=========== boot ===========
   I> MB2 finished
   pl:[I]: storage is virtualized
...
  pl:[I]: Loaded PT
   pl:[I]: dev_id 0xe instance 0x9 part_name :pt part_id 0x1 start_addr 0x0 size 0x40000 end_addr 0x3ffff
   pl:[I]: dev_id 0xe instance 0x9 part_name :kernel-dtb part_id 0x2 start_addr 0x40000 size 0x60000 end_addr 0x9ffff
   pl:[I]: dev_id 0xe instance 0x9 part_name :kernel part_id 0x3 start_addr 0xa0000 size 0x1b00000 end_addr 0x1b9ffff
   pl:[I]: dev_id 0xe instance 0x9 part_name :ramdisk part_id 0x4 start_addr 0x1ba0000 size 0x700000 end_addr 0x229ffff
...
   pl:[I]: Booted chain A
   pl:[I]: Loading Ramdisk Image
...
  pl:[I]: Loading DTB image
...
  pl:[I]: Kernel Cmdline: aurixfw=AFW root=/dev/vblkdev0 loglevel=3 ip=off pci=pcie_bus_perf usr_fs=/dev/vblkdev1:/mnt/persistent/metadata usr_fs2=/dev/vblkdev2:/mnt/persistent/data rw_overlay=/dev/vblkdev3:/rw_o   verlay gpt rootwait rw gpt tegra_keep_boot_clocks disable_android_paranoid_network sdhci_tegra.en_boot_part_access=1 nospectre_bhb console=ttyS2,115200n8 pci=ecrc=on verity=0 board_name=p3710-10-s05 pct=linux p   ower_profile=MAXP_A_990_D_04 tegraid=23.4.1.0.0 tegra_bootloader_debug.bl_debug_data=65536@0x7fe97f0000 tegra_bootloader_debug.bl_prof_dataptr=65536@0x7fe21c0000 tegra_bootloader_debug.bl_prof_ro_ptr=196608@0x7   fe21b0000 ^M
   pl:[I]: Loading Kernel Image
...
   pl:[I]: jumping to kernel at 0x80200000 (virtual 0x80a00000)
   [    0.227417] INITRAMFS STARTS
...
   [    1.563100] Trying switch_root to /new_root
   [    1.563156] INITRAMFS END
...
   Ubuntu 20.04.6 LTS tegra-ubuntu ttyS2
8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.