Partition bpmp-fw-dtb not found Error

Hi.

According to this site, I was trying to develop Jetson TX2 on SSD.
I put an incorrect value in /boot/extlinux/extlinux.conf, and after rebooting I can not start TX2.
Currently, it was not possible to enter factory reset mode, even with carrier boards that could enter factory reset with another TX2.
The NVIDIA logo is no longer displayed on the screen, so I read the UART communication.

The log is shown below.

[0[0000.242] I> Welcome to MB2(TBoot-BPMP)(version: 01.00.160913-t186-M-00.00-mobile-c4328dc3)
[0000.250] I> Default Heap @ [0xd486400 - 0xd488400]
[0000.255] I> DMA Heap @ [0x85200000 - 0x86200000]
[0000.260] I> bit @ 0xd480000
[0000.263] I> BR-BCT relocated to 0xd7020000
[0000.267] I> Boot-device: eMMC
[0000.271] I> sdmmc bdev is already initialized
[0000.275] I> pmic: reset reason (nverc)	: 0x0
[0000.280] I> Reading GPT from 512 for device 00000003
[0000.285] I> Reading GPT from 8388096 for device 00000003
[0000.293] I> Found 13 partitions in 00000003 device
[0000.297] I> Reading GPT from 512 for device 00010003
[0000.304] I> Found 29 partitions in 00010003 device
[0000.309] W> No valid slot number is found in scratch register
[0000.315] W> Return default slot: _a
[0000.318] I> A/B: bin_type (16) slot 0
[0000.322] I> Loading partition bpmp-fw at 0xd7800000
[0000.327] I> Reading two headers - addr:0xd7800000 blocks:1
[0000.332] I> Addr: 0xd7800000, start-block: 58761217, num_blocks: 1
[0000.347] I> Binary(16) of size 529040 is loaded @ 0xd7800000
[0000.353] W> No valid slot number is found in scratch register
[0000.359] W> Return default slot: _a
[0000.362] I> A/B: bin_type (17) slot 0
[0000.366] I> Loading partition bpmp-fw-dtb at 0xd79f0000
[0000.371] W> Partition bpmp-fw-dtb not found
[0000.375] E> Failed to load binary(17)
[0000.379] C> ERROR: Highest Layer Module = 0x1d, Lowest Layer Module = 0xd,
Aux Info = 0x0, Reason = 0xd

This log continues to flow continuously.
According to the log, TBoot-BPMP is not working properly, so it is unlikely to be able to enter factory reset mode.

Can I repair this TX2?

Thank you

hello boostrobot309,

you got failed in the very early boot stage, please also refer to Jetson TX2 Boot Flow.

several questions as below.

  1. may I know which JetPack release you’re working with
  2. may I know what’s the incorrect configuration of your /boot/extlinux/extlinux.conf
  3. don’t you had hardware key (recovery+rest) to put device enter forced-recovery mode
  1. I use Jetpack 3.2.1
  2. I have no data nor log, but I think set like this
TIMEOUT 30
DEFAULT eMMC

LABEL eMMC
    MENU LABEL primary kernel SSD
    LINUX /boot/Image
    INITRD /boot/initrd
    APPEND ${cbootargs} root=<wrong directory> rw rootwait

3)not works even with carrier boards that could enter factory reset with another TX2.

also,When I tried to enter recovery mode, I accidentally got a screen that was not in any document or website.

Some characters were displayed in white letters on the black screen, and there was the word “System reset.” The screen can not be operated using the buttons on the keyboard or carrier board on that screen, and the screen disappears after a while It has ended.
I continued to short the pin that was close to the recovery button with the jumper pin to enter this screen, and soon the power of TX2 will be turned off.

Is this an emergency program prepared by NVIDIA, or was I dreaming because I was tired?

Lastly, will the SoC only reset terminal on the board solve the problem?

Thank you.

hello boostrobot309,

could you please take a picture or video of the booting failure.
please have another way to enter forced-recovery mode: disconnect the power-supply, press the recovery button and power-on the board.
thanks

Hi

I have a very similar problem. Using JetPack 3.2.1 after flashing it gets stuck in a loop:-

[0000.354] I> Loading partition bpmp-fw-dtb at 0xd79f0000
[0000.359] W> Partition bpmp-fw-dtb not found
[0000.363] E> Failed to load binary(17)
[0000.367] C> ERROR: Highest Layer Module = 0x1d, Lowest Layer Module = 0xd,
Aux Info = 0x0, Reason = 0xd

I think this problem is due to deleting the file “Linux_for_Tegra/bootloader/t186ref/tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb” before running:-

sudo ./flash.sh -d mydevicetree.dtb -r jetson-tx2 mmcblk0p1

However I don’t want to test if it is repeatable!

Is there any way to get out of this though the serial console maybe?

Thanks

hello jamie.whitham,

that’s expected by deleting bpmp-fw-dtb file and doing whole flashing.
to clarify, below commands specify mydevicetree.dtb location and also skipping building system image to perform whole flashing process.

$ sudo ./flash.sh -d mydevicetree.dtb -r jetson-tx2 mmcblk0p1

may I have more details about why deleting that file before running the flash command.
thanks

Hi JerryChang

Thanks for your reply.

I was deleting it as I thought it was only used by

sudo ./flash.sh -r -k bpmp-fw-dtb jetson-tx2 mmcblk0p1

And I wanted to replace that with a new dtb for enabling UART7, and wanted to check our build process was working and the file was really copied over.

Anyway I now see that it is needed by the initial call to flash.sh.

So have stopped deleting it!

But how do I recover the TX2 module?

Thanks

Jamie

hello jamie.whitham,

But how do I recover the TX2 module?

you could simply execute the flash script to perform whole flashing process for the target.

sudo ./flash jetson-tx2 mmcblk0p1

Ah but it never gets as far as recover mode I get this output from flash.sh:-

###############################################################################

L4T BSP Information:

R28 (release), REVISION: 2.1, GCID: 11272647, BOARD: t186ref, EABI: aarch64,

DATE: Thu May 17 07:29:06 UTC 2018

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
micro-B USB port and is in recovery mode.

With this output continually repeating from the serial console:-

[0000.354] I> Loading partition bpmp-fw-dtb at 0xd79f0000
[0000.359] W> Partition bpmp-fw-dtb not found
[0000.363] E> Failed to load binary(17)
[0000.367] C> ERROR: Highest Layer Module = 0x1d, Lowest Layer Module = 0xd, Aux Info = 0x0, Reason = 0xd

hello jamie.whitham,

may I know what’s the addition device you had connected.
please refer to Jetson TX1 and TX2 Developer Kits User Guide for the steps to enter forced-recovery mode.
thanks

Hi Jerry

The TX2 is on a custom carrier board with FPGAs and various video encoder and decoder ICs, we are using the UART for external RS422 comms. We have the FORCE RECOVERY button which works for other TX2 modules but not for this one any more.

Thanks

Jamie


Hi Jamiem

That seems to be a HW issue on that TX2 module, please go for RMA: https://developer.nvidia.com/embedded/faq#rma-process

Thanks