Nano mdodule failed to start

Autonomous Machines Jetson & Embedded Systems Jetson Nano
,
#1

Hi all，
my new design（V0.2） add a line from CR2030 to PMIC_BBAT，like this：
image

then，my load board failed to start。 Can’t determine if it’s a core board or a load board problem。but during my debugging，3~4core board start successed，and zhe core board successed once,can success every time(try 100+)。

jectpack 4.6 REV3
sdkm 1.7.2.9007

We have the following questions:
1、Can’t determine if it’s a core board or a load board problem；
if core board，Can’t determine if it’s a core board or a load board problem；
if module board,zhe core board successed once,can success every time。

Nano boot failed
#3

add,boot failed pin rst is 3.3V,log like this:

Starting kernel …

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.201-tegra (buildbrain@mobile-u64-5294-d8000) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Fri Feb 19 08:40:32 PST 2021
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32,
[ 0.000000] OF: fdt: - 80000000 , 7ee00000
[ 0.000000] OF: fdt: - 100000000 , 7f200000
[ 0.000000] Found tegra_fbmem: 00140000@92cb4000
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options ‘’)
[ 0.000000] bootconsole [uart8250] enabled
[ 0.527965] genirq: Setting trigger mode 8 for irq 57 failed (irq_chip_set_type_parent+0x0/0x48)
[ 1.095032] tegradc tegradc.1: tegra_dc_parse_panel_ops: could not find panel for /host1x/sor
[ 1.103723] tegradc tegradc.1: err:-19 parsing panel_ops
[ 1.121078] nct1008_nct72 0-004c: write reg err -121
[ 1.126177] nct1008_nct72 0-004c: sensor init failed 0xffffff87
[ 1.132169] nct1008_nct72 0-004c:
[ 1.132169] exit nct1008_probe, err=-121
[ 1.403127] mmc0: error -110 whilst initialising MMC card
[ 1.409707] sdhci-tegra sdhci-tegra.3: Failed to set parent pll 32770
[ 1.525788] mmc0: error -110 whilst initialising MMC card
[ 1.532291] sdhci-tegra sdhci-tegra.3: Failed to set parent pll 32770
[ 1.656505] mmc0: error -110 whilst initialising MMC card
[ 1.663009] sdhci-tegra sdhci-tegra.3: Failed to set parent pll 32770
[ 1.821232] mmc0: error -110 whilst initialising MMC card

#4

You can probe the output voltage level of CR2030 during power on and compare to that of a capacitor to find out if any difference.

#5

success:
image
error:
image
ch1:module power ch2:power_en ch3:reset ch4 PMIC_BBAT
the error module rst levle is 3.3V?

#6

log:
success.log (19.2 KB)
error.log (17.9 KB)

#7

It is OK without CR2030, right? You should focus on the RTC battery/capacitor and find out why it will cause boot failure. What is the device of the backup battery attached to? What if you cut off the line to that device?

#8

not OK without cr2032,now, after I changed the power-on sequence of the Carrier Board Supplies,the module success。

#9

So it is a power sequence issue? Have you compare to the power on sequence as listed in design guide? The key point is to let module power on first and all carrier power supplies should be ON later than module.

#10

According the design guide , The normal Boot Sequence should be :

5V(VDD_IN) ->Power_EN->Module Power_On->Sys_Reset(Pull Hight)->Board Supplies

3497d56980ef4a0156d4811bf423139

so , it means we need to check te module power_on first , right?

#11

SYS_RESET going high means module power on is OK. The carrier supplies should be enabled by SYS_RESET. That can guarantee carrier supplies are turn on later than module.

#12

yes,wo do as you say boot failed;after change board supplies same as power_en successed。

#13

add,
image
ch1:power_en;ch2:reset;ch3:carrier board; the reset levle is 3.3V

#15

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