Upgrading from JP 4.6.3 to JP 5.1.2 - CPU Bootloader is not running on device Error

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

We are having trouble upgrading our AGX Xavier SOMs from JP 4.6.3 to the latest version JP 5.1.2. We are using custom config & pinmux files that can be flash successfully with 4.6.3 via command line (sudo ./flash.sh umc-gpgpu mmcblk0p1).

I have downloaded the AGX Jetpack 5.1.2 and setup the directory (just like in 4.6.3). I have copied over the custom configuration files from the successful 4.6.3 directory into the 5.1.2 directory.

When I try to flash the JP5.1.2. via the same ./flash command, I receive a ‘CPU Bootloader is not running on device error’ after some time like before and then fails to flash:

[1017.3453] tegrarcm_v2 –isapplet
[2033.1633] tegradevflash_v2 –iscpubl
[2033.1633] CPU Bootloader is not running on device.
[3049.9629] tegrarcm_v2 –isapplet
[4064.7695] tegrarcm_v2 –ismb2
…

If I try to just flash directly using the SDK Manager, I receive an ID, Version, SKU error as seen below. How can I use my configuration files from my working 4.6.3 install in the new JetPack 5.1.2? I placed the files in the correct location, same as in 4.6.3, /bootloader, /bootloader/t186ref/BCT/, etc.

image
image1049×575 208 KB

3

Hi,

what do you get from serial console log during flashing?
Also, are you sure changes in device tree/pinmux are the same across 4.6.3 and 5.1.2?

4

DaveYYY,

Attached is the failed flash log.

jp512_flash_log_fail.txt (35.1 KB)

Also, the changes I copied from 4.6.3 to the 5.1.2 were the files:
p2972-0000.conf.common
tegra19x-umc-gpgpu.cfg (pinmux change)
tegra19x-umc-gpgpu-padvoltage.cfg (pinmux change)
tegra194-umc-gpgpu.dtb
umc-gpgpu.conf (my custom configuration file that mentions the above files)

That file looks like:
source “${LDK_DIR}/p2972-0000.conf.common”;
PINMUX_CONFIG=“tegra19x-umc-gpgpu.cfg”;
PMC_CONFIG=“tegra19x-umc-gpgpu-padvoltage.cfg”;

ODMDATA=0x8191000
DTB_FILE=“tegra194-umc-gpgpu.dtb”;
CMDLINE_ADD=“console=ttyTCU0,115200n8 fbcon=map:0 net.ifnames=0 rootfstype=ext4 loglevel=9”;

And I placed those files in the same location on 5.1.2 as they were on 4.6.3. Am I missing any files that I need to copy over?

5

Hi,

we need the UART log from the device side, but not flashing log from the host side.
The serial console on AGX Xavier is available with the micro USB port.

6

Unfortunately, this is not on the Dev kit, but on a production SoM, so there is not a micro USB port.
I am using minicom on the host side (Ubuntu 18.04) to get console access into the AGX Xavier SoM. I’ll see if I can find a way to capture that output during the flash.