Flashing r32.7.3 to emmc doesn't boot, r32.7.2 does

(We haven’t been able to move to r35 yet - we’ll get there, but for now we need to stay on r32)

I’m having an issue booting a Xavier NX after flashing to emmc since upgrading from r32.7.2 to r32.7.3; when I’m in the Linux4Tegra directory and run:

sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

…I get something that boots to “entering main console loop”, and gives a prompt, but doesn’t boot into Linux as expected. (see full boot log below) When I reflash with the same command from above on an r32.7.2 distribution, things work as expected and the Xavier NX boots as expected (even from a disk image that has r32.7.3 on it).

Is there anything I can do to fix this, or do I need to only flash from r32.7.2 ?

Here’s the full boot log from r32.7.3:
bad-3273-boot.log (9.7 KB)

Hi riz94107,

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

entering main console loop

This message seems expected in the boot log.

How do you upgrade from R32.7.2 to R32.7.3?

Have you tried to flash r32.7.3 directly?

What do you mean? I don’t see that when I boot a Xavier flashed with 32.7.2.

What I mean is, the Xavier is running 32.7.2 and I flash it with 32.7.3. Doing that (whether flashing 32.7.2 or 3) involves - unpacking the L4T release package, unpacking the sample rootfs into Linux4Tegra/rootfs, running apply_binaries.sh, and then sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1 - the only difference is whether I use the 32.7.2 or 32.7.3 L4T release package…

I think I am flashing it directly? Or what do you mean by that?

Upon closer inspection, we had a build step which involved replacing cboot due to an issue in 32.7.2 - and we were still installing that cboot in 32.7.3, which caused the problem with boot.

Building a new cboot for 32.7.3 (or using the stock cboot) makes my boot problem go away. Sorry for the noise.

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