Nano Boot failure

Hello, teams.

We have occasional boot failure on out Jetson Nano platform, which looks similar to the topic below:

The `dying’ console is the following, and it looks similar to the above mentioned topic. (Stops just after ther thernal* messages)

The original topic is already `closed’ after some questions about DVFS features.

Does anyone has a similar issue? or Any further information?
Did DVFS tweaks worked?

Thanks in advance

------------------ from here ----------------
[ 3.207563] [drm] Initialized
[ 3.236875] brd: module loaded
[ 3.244722] tegradc tegradc.0: fb registered
[ 3.250060] loop: module loaded
[ 3.250816] tegradc tegradc.1: disp1 connected to head1->/host1x/sor
[ 3.250890] tegradc tegradc.1: No lt-data, using default setting
[ 3.250914] tegradc tegradc.1: No hpd-gpio in DT
[ 3.250945] tegradc tegradc.1: DT parsed successfully
[ 3.250997] tegradc tegradc.1: Display dc.ffffff800d500000 registered with id=1
[ 3.252341] tegradc tegradc.1: dpd enable lookup fail:-19
[ 3.757970] Host read timeout at address 545c00c4
[ 3.759101] tegradc tegradc.1: probed
[ 3.796771] tegradc tegradc.1: fb registered
[ 3.796908] tegra_profiler: version: 1.134, samples/io: 47/26
[ 3.797048] tegra_profiler: auth: init
[ 3.798329] THERMAL EST: found 2 subdevs
[ 3.798335] THERMAL EST num_resources: 0
[ 3.798340] [THERMAL EST subdev 0]
[ 3.798348] [THERMAL EST subdev 1]
[ 3.798827] thermal thermal_zone5: Registering thermal zone thermal_zone5 for type thermal-fan-est
[ 3.798829] THERMAL EST: thz register success.
[ 3.799002] THERMAL EST: end of probe, return err: 0
[ 3.800218] hisi_sas: driver version v1.6
[ 3.806709] libphy: Fixed MDIO Bus: probed

No idea about this. There was really no topic indicating a fix as most users just don’t reply.
I would say no need to keep thinking of your issue is related to DVFS. Just clarify the situation first.

Is this a NV devkit or your custom board which reproduce this issue?

Wayne, Thanks for your information, the issue is on our custom board.
We don’t yet have enough information on it, since the rare occurrence.
Any suggestion/information wil be appreciated.

Thank you again.

please enable serial console log from uart. Monitoring your board until this issue happened.

The log you showed in first comment didn’t give any hint. Looks like just normal boot log.

Some common way to debug is remove all peripherals from your board and add them back one by one and see which device is the cause here.

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