Unable to boot Jetson Nano Devkit r32.5.0 branch tegra-demo-distro

[pgiangrossi]

I tried to deploy the demo-image-base using commit 60e217fb92bb99cb26403a2737b87662ac93c50a (HEAD -> dunfell-l4t-r32.5.0, origin/dunfell-l4t-r32.5.0).

I built using:

cd tegra-demo-distro
. ./setup-env --machine jetson-nano-devkit
MACHINE=jetson-nano-devkit bitbake demo-image-base

I then flashed the SD card on my Linux host via:

cd tmp/deploy/images/jetson-nano-devkit
tar -xvf demo-image-base-jetson-nano-devkit.tegraflash.tar.gz
./dosdcard.sh
sudo dd if=demo-image-base.sdcard of=/dev/sdd bs=10M status=progress

I ran into the following problem:

• mount failure at startup (/dev/mmcblk0p not found, my sdcard had /dev/mmcblk0p1). I fixed this by adding distro_bootpart ?= "1" to conf/machine/jetson-nano-devkit.conf)

With this fix, I was able to build, deploy and bring up the Jetson Nano devkit.

I wonder if I am doing something wrong, or using this repo in the wrong way?

[ichergui]

Hey @pgiangrossi

I think you missed some steps in the build image process.

You don't need the cmd $ sudo dd if=demo-image-base.sdcard of=/dev/sdd bs=10M status=progress to flash the SDcard because the script dosdcard.sh already done this for you.

• Here the instructions:

$ git clone https://github.com/OE4T/tegra-demo-distro.git
$ cd tegra-demo-distro
$ git checkout origin/dunfell-l4t-r32.5.0 -b dunfell-l4t-r32.5.0
$ git submodule update --init --recursive 
$ unset NVIDIA_DEVNET_MIRROR                                    
$ export NVIDIA_DEVNET_MIRROR="/PATH/TO/JETPACK_4.5/nvidia/sdkm_downloads"
$ . ./setup-env --machine jetson-nano-devkit --distro tegrademo build_jetson_nano
$ bitbake demo-image-base

• Go to the deploy directory and flash the device:

$ cd tmp/deploy/images/jetson-nano-devkit
$ tar -xvf demo-image-base-jetson-nano-devkit.tegraflash.tar.gz

In case of updating the SPI flash you need to use the script doflash.sh instead or You can do it in different way.

• Here is the steps
  1- Flash the SDcard via the script dosdcard.sh
  2- Boot the device and stop the boot process to have the u-boot prompt
  3- Execute the following commands:

# env default -a
# saveenv
# reset

[pgiangrossi]

I am using the Micro USB as power supply. When I apply the patch (distro_bootpart ?= 1) as described above, with the steps that you list, I get a login screen on the console and I can login to root. Without the patch, fails as indicated above.

I will try without the patch and the barrel jack as power source, and come back to you with results.

[ichergui]

From your serial UART the mounting of the rootfs is not happening.
Here is my traces from the serial uart as a reference:

[    5.089240] mmc0: hw tuning done ...
[    5.089272] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
[    5.089673] mmcblk0: mmc0:aaaa SE32G 29.7 GiB 
[    5.093023]  mmcblk0: p1
[    5.102751] usb 2-1: usb_suspend_both: status 0
[    5.102896] usb usb2: usb_suspend_both: status 0
[    5.726708] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.726712] usb 1-2: Product: 4-Port USB 2.1 Hub
[    5.726716] usb 1-2: Manufacturer: Generic
[    5.738589] hub 1-2:1.0: USB hub found
[    5.742617] hub 1-2:1.0: 4 ports detected
[    5.754394] Freeing unused kernel memory: 10624K
[    5.770040] EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities
[    5.780215] EXT4-fs (mmcblk0p1): couldn't mount as ext2 due to feature incompatibilities
[    5.797362] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)

You should not apply any patch and it should be working fine.
As I mentioned above please use the script doflash.sh to flash your device.
I will flash my device because I'm using the master branch then share with you the traces from the Serial UART.
Do you remember which branch was flashed your device ?
For example:

• If your device was using the dunfell-l4t-r32.4.3 before the dunfell-l4t-r32.5.0. In this case you need to flash the device via doflash.sh
  Please let me know if it is not clear for you.

[ichergui]

Hello @pgiangrossi

I flashed my device with the same branch that you are using. All good here.

The attached file contains the complete logs from the serial UART.

jetson_nano_devkit_serial_uart.log

[pgiangrossi]

Hi @ichergui

Using doflash.sh worked perfectly!

I do not know what was on the board before I started flashing it, but it was probably the NVIDIA distro that you can download directly from their webiste (ie, it wasn't built locally using yocto).

My understanding is that the doflash.sh script updates the SPI flash as well as the SD card. Is that correct? So I guess the SPI flash needed updating. What is stored there vs. the SD card?

Thanks so much for your help!

/Paul

[ichergui]

Hey @pgiangrossi
Glad to hear that.
All boot partitions are stored in the SPI flash that's why we need to update them.
Yeah, I confirm that the script doflash.sh updates the APP (rootfs) partition as well.