How to edit linux kernel boot parameters on the Xavier A/B target

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Hi,

I just have access to pre-built linux images to flash Xavier A/B targets on my Drive-AGX platform. I use “flash_bsp_images.sh” to flash linux images onto the target. Is there a way to edit the kernel boot parameters either by just editing some file on the target without flashing, or by editing some file on the host and re-flash with the pre built images?

Any comments will be helpful.

Thanks
Anup

2

Dear anup.pemmaiah,
We will check internally on this issue and get back to you.

3

Thank you SivaRamaKrishna. Really appreciate that.

4

Dear anup.pemmaiah,

Could you please help to check the following links?

https://docs.nvidia.com/drive/drive_os_5.1.6.1L/nvvib_docs/index.html#page/DRIVE_OS_Linux_SDK_Development_Guide/Appendix/install_manual.html#

https://docs.nvidia.com/drive/drive_os_5.1.6.1L/nvvib_docs/index.html#page/DRIVE_OS_Linux_SDK_Development_Guide/Appendix/sys_programming_kernel_toolchain.html

Please let me know if you need more information. Thanks.

5

Hi SteveNV,

The first link is to build the image using Yocto from source. In my case I only have access to Drive AGX Xavier images given to me by a vendor. Do not have access to the source.

The second link is to build the kernel from source. Again, I do not have access to the source. Just access to pre-built images. I know to do it when I build images from source.

Was curious, if there is a way to edit the boot parameters either through a boot loader or by editing a some boot file on the target Xaviers. I assume the answer is NO, but wanted to double check.

Thanks
Anup

6

Hi anup.pemmaiah,

Please take a look at os_args attribute mentioned in “Mass Storage Partitions” section and “Passing Additional Kernel Parameters” section of the development guide.

You can modify your boot parameters in the files, and then flash kernel-dtb (or flash with SDK Manager).

  • ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-foundation/virtualization/pct/e3550b03-t194a/linux/linux_storage_emmc.cfg
  • ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-foundation/virtualization/pct/e3550b03-t194b/linux/linux_storage_emmc.cfg
7

Hi VickNV,

In the past when I flashed the target using bootburn on the images I compiled, I used to set the os_args and pass the configuration file as part of bootburn. I assume for the scenario that you mentioned we need to also use bootburn.

In the current situation, I am using flash_bsp_images.sh to flash the target. I do not see an option to pass the configuration file through flash_bsp_images.sh. I may have to dig into the script.

8

FYI. installing with SDK Manager global_storage_qspi.cfg is the top-level CFG file making references to other CFGs.