Custom carrier board periodicity fails to boot

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

We have developed a custom carrier board for the Jetson Nano. We have found that some times first thing in the morning, the nano hangs up at the boot logo.
When u-boot starts I get random characters from the UART. Below is a part of the UART output.

SoC: tegra210
Model: NVIDIA Jetson Nano Developer Kit
Board: NVIDIA P3450-0000
DRAM:  4 GiB
MMC:   sdhci@700b0000: 1, sdhci@700b0600: 0
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() fai                         led, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Tegra210 (P3450-0000) #[0000.230] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82                         258de)  @@     @@▒ @  @@     @ @ @@@@  @  @ @@ @ @  `    @@▒@@  @ @   @@@  @ @

This is what I normally get

SoC: tegra210
Model: NVIDIA Jetson Nano Developer Kit
Board: NVIDIA P3450-0000
DRAM:  4 GiB
MMC:   sdhci@700b0000: 1, sdhci@700b0600: 0
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() fai                         led, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
879 bytes read in 25 ms (34.2 KiB/s)
1:      primary kernel

Any clues as to what is going on here. Or any ideas on a good place to start looking.
It really feels carrier board related. like I have a floating pin or something that should not be.

3

Is this jetson nano issue? It seems you filed on TK1 forum.

4

It is a nano issue. My stuff up

5

You can try to add some debug print to the uboot and see where gets stuck.
Also, if this is related to board design, please check our design guide in the download center.

6

Found the issue. We had not added a pull-up resistor to the debug UART Rx line. so under certain circumstances random data would be received by the nano causing issues at the u-boot menu.

8

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