Freeze during booting

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello,

After kernel compilation, I changed the boot/Image.
It stops during booting with the following message.
What should I do?

============== message ============================================
MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1
SF: Detected MX25U3235F with page size 256 Bytes, erase size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
1445 bytes read in 149 ms (8.8 KiB/s)
L4T boot options
1:      primary kernel
2:      Custom 40-pin Header Config
3:      FE-PI Audio Z V2
Enter choice: 3:        FE-PI Audio Z V2
Retrieving file: /boot/initrd
5488163 bytes read in 357 ms (14.7 MiB/s)
Retrieving file: /boot/Image
** File not found /boot/Image **
Skipping FE-PI Audio Z V2 for failure retrieving kernel
1:      primary kernel
Retrieving file: /boot/initrd
5488163 bytes read in 356 ms (14.7 MiB/s)
Retrieving file: /boot/Image
** File not found /boot/Image **
Skipping primary for failure retrieving kernel
2:      Custom 40-pin Header Config
Retrieving file: /boot/initrd
5488163 bytes read in 358 ms (14.6 MiB/s)
Retrieving file: /boot/Image
** File not found /boot/Image **
Skipping JetsonIO for failure retrieving kernel
SCRIPT FAILED: continuing...
Card did not respond to voltage select!
starting USB...
USB0:   tegrausb: Invalid dr_mode 2 for host mode
probe failed, error -1
USB error: all controllers failed lowlevel init
BOOTP broadcast 1
DHCP client bound to address 192.168.0.204 (23 ms)
*** Warning: no boot file name; using 'C0A800CC.img'
Using eth_rtl8169 device
TFTP from server 0.0.0.0; our IP address is 192.168.0.204; sending through gateway 192.168.0.1
Filename 'C0A800CC.img'.
Load address: 0x83280000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
pci_hose_bus_to_phys: invalid physical address
missing environment variable: pxeuuid
Retrieving file: /boot/extlinux/pxelinux.cfg/01-00-04-4b-eb-f2-e9
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A800CC
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A800C
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A800
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A80
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A8
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0A
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C0
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/C
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/default-arm-tegra210
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/default-arm
*** ERROR: `serverip' not set
Retrieving file: /boot/extlinux/pxelinux.cfg/default
*** ERROR: `serverip' not set
Config file not found
starting USB...
USB0:   tegrausb: Invalid dr_mode 2 for host mode
probe failed, error -1
USB error: all controllers failed lowlevel init
BOOTP broadcast 1
DHCP client bound to address 192.168.0.204 (26 ms)
Using eth_rtl8169 device
TFTP from server 0.0.0.0; our IP address is 192.168.0.204; sending through gateway 192.168.0.1
Filename 'boot.scr.uimg'.
Load address: 0x80200000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
pci_hose_bus_to_phys: invalid physical address
BOOTP broadcast 1
DHCP client bound to address 192.168.0.204 (26 ms)
Using eth_rtl8169 device
TFTP from server 0.0.0.0; our IP address is 192.168.0.204; sending through gateway 192.168.0.1
Filename 'boot.scr.uimg'.
Load address: 0x83280000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
pci_hose_bus_to_phys: invalid physical address

========================================================================
Thank you.

2

I don’t know if it is failing to find this within the initrd or if the Image file is being looked for on the ext4 filesystem, but what is the content of the extlinux.conf file? If you are adding multiple kernels, then each should have its own name variation rather than having each overwrite the other, and then the extlinux.conf should name that slightly different Image name.

Sometimes I have created alternate entries with the same Image file, but different kernel command line or device tree entries, so it isn’t necessarily an error to have a single Image in /boot, but it makes me suspicious unless I know why they all use the same file name /boot/Image.

3

changed in which way?
deleted?
substituted?
both?
neither of the two?
if substituted - with what? in which way?
what are the steps to reproduce the error?

1 Like
4

Hello,

  1. substituted

  2. copy

Thank you.