Jetson Xavier AGX PXE boot fail with JetPack 5.0.2

I did try UEFI PXE boot for JetPack 5.0.2.

Output is similar than with 5.0.1 in following ticket:

Is PXE boot supported in with JetPack 5.0.2 (or in my case more interesting Linux4Tegra release:35.1.0)? What documentation I would follow to succesfully setup PXE (or any network) boot environment?

Based on JetsonAgxXavierSeries r35.1 documentation I would assume some sort of network boot would be available.

Not sure about version, but I see that PXE boot is done with this board according following discussion: Flashing only UEFI bootloader to Jetson AGX Xavier

Hi cartographer,

Are you using the devkit or custom board for AGX Xavier?

Please use latest Jetpack5.1.1(R35.3.1) to verify.

You could refer to the following instruction to boot from NFS.
Flashing Support — Flashing for NFS as Root

Hi @KevinFFF ,

I am using developer kit.

Problem with JetPack 5.1.1 is exactly same:

>>Start PXE over IPv4.
  Station IP address is

  Server IP address is
  NBP filename is BOOTAA64.efi
  NBP filesize is 73728 Bytes
 Downloading NBP file...

  NBP file downloaded successfully.

L4TLauncher: Attempting Direct Boot
ProcessExtLinuxConfig: Unable to find partition info
L4TLauncher: Unable to process extlinux config: Not Found
L4TLauncher: Attempting Kernel Boot
ReadAndroidStyleKernelPartition: Unable to located partition
Failed to boot kernel:0 partition

NFS mount flashing approach you mentioned does not fullfill my need. It starts kernel from EMMC and expects to use NFS as rootfs. As I mentioned before, need is similar than in linked ticket, so quotation from that ticket:

I want to setup a PXE boot environment in our system in which the Jetson only contains the UEFI bootloader and nothing else on its eMMC. In my current setup, the Jetson uses the integrated PXE boot functionality in the UEFI bootloader to PXE boot a GRUB image from the TFTP server and use said GRUB image to boot a kernel image, initial ramdisk, and device tree blob from the TFTP server while also mounting its root filesystem over NFS from the server.

Am I using correct NBP file (BOOTAA64.efi) or should I create it somehow? On tftp server side I don’t see another file requests which would lead forward in boot procedure over network.

ping @abotelho1994

Based on which documentation you did you solve linux kernel network boot problem? I could not find any instructions related to GRUB kernel image usage in that purpose on that Jetson Xavier AGX board. I am wondering what is suitable NBP binary on PXE server in order to continue kernel image loading from tftp (and latter using NFS for filesystem).

May I know what’s the purpose of you for this requirement?

Sorry, we still have internal bug tracking about PXE boot feature in Jetpack 5.1.1.

May I know what’s the purpose of you for this requirement?

Helping automatic testing. Kernel changes which do not require bootloader changes would be possible test with PXE boot and without doing flashing. If only bootloader is flashed to EMMC, that would be just simplier, not necessary. Then we can faster be sure when boot over network has happened and when not. And also I suppose network boot would decrease need for dedicated hosts for software upgrade(or is it possible e.g. connect >1 nvidia USB device and handle parallel upgrades via command line flashing tools?). Solution might be combination about USB flashing with NFS rootfs as you mentioned earlier.

Sorry, we still have internal bug tracking about PXE boot feature in Jetpack 5.1.1.

That’s sad to here, hopefully it will be working in future. Is kernel booting over network possible in any way with Jetpack 5.0.2/LinuxTegra 35.1?

Thanks for your reason to do this.

Currently, there’s only NFS boot available for you to be used for booting from network, the rest of contents should be stored in internal eMMC or QSPI.

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