Please help to confirm fail at what device

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

We don’t understand what happen ，please help to fail at what device, the debug message is following:

[0000.383] I> Boot-device: eMMC

[0000.386] I> Boot_device: SDMMC_BOOT instance: 3

[0000.392] I> sdmmc-3 params source = boot args

[0000.395] I> sdmmc bdev is already initialized

[0000.399] I> sdmmc-3 params source = boot args

[0000.408] I> Found 17 partitions in SDMMC_BOOT (instance 3)

[0000.414] I> Found 42 partitions in SDMMC_USER (instance 3)

[0000.415] W> No valid slot number is found in scratch register

[0000.420] W> Return default slot: _a

[0000.423] I> Active Boot chain : 0

[0000.427] I> parsing oem signed section of bpmp-fw header done

[0000.433] I> bpmp-fw binary init read from storage

[0000.438] I> oem authentication of bpmp-fw header done

[0000.444] I> bpmp-fw binary done read from storage

[0000.447] I> bpmp-fw: Authentication init Done

[0000.451] I> parsing oem signed section of cpubl header done

[0000.457] I> cpubl binary init read from storage

[0000.461] I> bpmp-fw: Authentication Finalize Done

[0000.466] I> oem authentication of cpubl header done

[0000.470] I> cpubl binary done read from storage

[0000.475] I> cpubl: Authentication init Done

[0000.480] I> parsing oem signed section of rce header done

[0000.484] I> rce binary init read from storage

[0000.489] I> Relocating BR-BCT

[0000.492] I> cpubl: Authentication Finalize Done

[0000.496] I> oem authentication of rce header done

[0000.501] I> rce binary done read from storage

[0000.505] I> rce: Authentication init Done

[0000.510] I> parsing oem signed section of ape header done

[0000.514] I> ape binary init read from storage

[0000.519] I> rce: Authentication Finalize Done

[0000.523] I> oem authentication of ape header done

[0000.527] I> ape binary done read from storage

[0000.532] I> ape: Authentication init Done

[0000.536] I> parsing oem signed section of tos header done

[0000.541] I> tos binary init read from storage

[0000.545] I> ape: Authentication Finalize Done

[0000.550] I> oem authentication of tos header done

[0000.554] I> tos binary done read from storage

[0000.558] I> tos: Authentication init Done

[0000.563] I> parsing oem signed section of bpmp-fw-dtb header done

[0000.568] I> bpmp-fw-dtb binary init read from storage

[0000.573] I> tos: Authentication Finalize Done

[0000.579] I> oem authentication of bpmp-fw-dtb header done

[0000.586] I> bpmp-fw-dtb binary done read from storage

[0000.588] I> bpmp-fw-dtb: Authentication init Done

[0000.593] I> parsing oem signed section of cpubl-dtb header done

[0000.599] I> cpubl-dtb binary init read from storage

[0000.603] I> bpmp-fw-dtb: Authentication Finalize Done

[0000.641] I> oem authentication of cpubl-dtb header done

[0000.641] I> cpubl-dtb binary done read from storage

[0000.642] I> cpubl-dtb: Authentication init Done

[0000.644] I> parsing oem signed section of eks header done

[0000.645] I> eks binary init read from storage

[0000.645] I> cpubl-dtb: Authentication Finalize Done

[0000.646] I> oem authentication of eks header done

[0000.649] I> eks binary done read from storage

[0000.654] I> eks: Authentication init Done

[0000.658] I> eks: Authentication Finalize Done

[0000.662] I> EKB detected (length: 0x410) @ VA:0x5270a400

▒▒NOTICE: BL31: v1.3(release):de895fd9e

NOTICE: BL31: Built : 12:15:31, Oct 16 2020

ipc-unittest-main: 1519: Welcome to IPC unittest!!!

ipc-unittest-main: 1531: waiting forever

ipc-unittest-srv: 329: Init unittest services!!!

hwkey-agent: 40: hwkey-agent is running!!

hwkey-agent: 182: key_mgnt_processing …

hwkey-agent: 157: Init hweky-agent services!!

platform_bootstrap_epilog: trusty bootstrap complete

▒▒

welcome to lk

calling constructors

initializing heap

creating bootstrap completion thread

top of bootstrap2()

initializing platform

bpmp: platform_init

tag is 57f8a77779f848bf2ecf21dabee5645f

tag_show initialized

dt initialized

mail initialized

chipid initialized

fuse initialized

sku initialized

speedo initialized

ec_get_ec_list: found 45 ecs

ec initialized

ec_mrq initialized

vmon_populate_monitors: found 3 monitors

vmon initialized

adc initialized

fmon_populate_monitors: found 73 monitors

fmon initialized

fmon_mrq initialized

reset initialized

nvhs initialized

392 clocks registered

WARNING: pll_c4 has no dyn ramp

clk_mrq_init: mrq handler registered

clk initialized

nvlink initialized

io_dpd initialized

io_dpd initialized

thermal initialized

i2c5 controller initialized

initialized i2c mrq handling

i2c initialized

regulator initialized

avfs_clk_platform initialized

soctherm initialized

aotag initialized

powergate initialized

dvs initialized

pm initialized

pg_late initialized

strap initialized

tag initialized

3

hello Tony_Li,

I did not see obvious errors, were those complete console logs?
please revise your comments to attach the logs by the <code> code block </code>.
thanks

4

From others post, the next steps should be

emc initialized
clk_dt initialized
avfs_ccplex_platform initialized
tj_max: dt node not found
tj_init initialized
uphy_mrq_init: mrq handler registered
uphy_dt initialized
uphy initialized

We don’t see the “emc initialized” on our board, what will cause this phenomenon ?

5

hello jb035.cheng,

may I also have complete console logs for reference,
did you perform a whole flashing process with SDKmanager then reproduce the issue?
thanks

6

We can’t flash at our board ,so we use Developer_Kit fish module , then move the module to our board ,get the message

7

hello Tony_Li,

that’s expect results, you may have some platform-specific data updates.
please refer to developer guide, you should also check Jetson Xavier NX and Jetson AGX Xavier Series MB1 Platform Configuration for more details of board customization.
thanks

8

We have no idea about this ,Please help confirm what part can be affect the boot,thanks

9

hello Tony_Li,

I would guess it’s caused by board configuration,
please download pinmiux spreadsheets to complete your board customization. after that, you may flash the correct *.cfg file to update the image.
thanks

10

I know ,but I try most of the control pin ,it is still not work normal ,so I need NV help to clear what is the “emc initialized” work function ?

11

had you complete your board customization to use correct *.cfg file for flashing?

12

Can you help to provide about the config detail,thanks

13

you should also check Jetson Xavier NX and Jetson AGX Xavier Series MB1 Platform Configuration for more details of board customization.

14

At Jetson AGX Developer Kit with 16 GB memory, but the module with 32GB memory, how about this different ,how about setting at this

15

hello Tony_Li,

please refer to developer guide and check Jetson Xavier NX and Jetson AGX Xavier Series MB1 Platform Configuration chapter.
there’re different MB1 configuration files for different Jetson AGX Xavier modules.
you should look into memory rail configuration, i.e. pmic.memio for comparison.
thanks

16

May I to know how to assign MB1 use the <device>-tegra194-mb1-bct-pmic-p2888-0004-<revision>.cfg configuration files for AGX Xavier module with 32 GB of memory?

Linux_for_Tegra/bootloader/t186ref/BCT/<device>-tegra194-mb1-bct-pmic-<partnumber>-<revision>.cfg
<partnumber> is the full part number of the device:
•p2888-0004 for the Jetson AGX Xavier module with 32 GB of memory
17

hello SammyChenTw,

it’s MB1 Platform Configuration process to generate a *.cfg file from the customize pinmux spreadsheets.
you should also check flashing messages, please looking for mb1-bct for the file name that flash to your target.
thanks

18

I am hardware engineer, I don’t have any way to solve this issue, but I think the Can we remove the most of the software files and only remain the boot file to try ,what about the file is for boot only?

19

hello Tony_Li,

please check the Boot Flow Jetson AGX Xavier series. it’s MB1 for the very early stage to initial the board configuration.

20

We don’t have idea at the issue .your agent and Taiwan FAE come here yesterday, but it is still not way to solve this issue , do you have any tool can help to check boot fail at what

21

the attached file is our download error message , please help to confirm about this issue
log_uart.txt (7.2 KB)