Jump to content
  • 0

odroid-xu4 sid edge 6.0.9 boot error


suchende

Question

U-Boot 2017.05-armbian (Nov 30 2022 - 10:45:39 +0000) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
12548 bytes read in 44 ms (278.3 KiB/s)
## Executing script at 43e00000
111 bytes read in 33 ms (2.9 KiB/s)
6724096 bytes read in 550 ms (11.7 MiB/s)
11217705 bytes read in 881 ms (12.1 MiB/s)
0 bytes read in 45 ms (0 Bytes/s)
Found mainline kernel configuration
** File not found /boot/dtb/exynos5422-odroidhc1.dtb **
** Unrecognized filesystem type **
** File not found dtb/exynos5422-odroidhc1.dtb **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Kernel image @ 0x40008000 [ 0x000000 - 0x669a00 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11217641 Bytes = 10.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
** File not found /boot.scr **
## Executing script at 43e00000
** Invalid partition 2 **
## Executing script at 43e00000
** Invalid partition 2 **
## Executing script at 43e00000
** Invalid partition 2 **
## Executing script at 43e00000
mmc_init: -110, time 120
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... cannot reset port 1!?
1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found

USB device 0: unknown device
Waiting for Ethernet connection... done.
BOOTP broadcast 1

the boot fails after switching the kernel through armbian-config. Further investigation needed.

 

//Edit 1: the dtb file is missing.

ls -la /boot
insgesamt 32336
drwxr-xr-x  2 root root     4096  8. Dez 19:03 .
drwxr-xr-x 21 root root     4096 12. Jan 2022  ..
-rw-r-----  1 root root      111  8. Dez 18:47 armbianEnv.txt
-rw-r-----  1 root root        0 29. Dez 2021  armbianEnv.txt.out
-rw-r--r--  1 root root     1536  7. Aug 2019  armbian_first_run.txt.template
-rw-r--r--  1 root root    38518  7. Aug 2019  boot.bmp
-rw-r--r--  1 root root     4882  7. Aug 2019  boot-desktop.png
-rw-rw-r--  1 root root    12548  7. Aug 2019  boot.ini
-rw-r-----  1 root root        0 29. Dez 2021  boot.ini.out
-rw-r--r--  1 root root   190980 30. Nov 12:07 config-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       21  6. Dez 18:42 dtb -> dtb-5.4.225-odroidxu4
lrwxrwxrwx  1 root root       22 15. Apr 2020  dtb.old -> dtb-4.14.176-odroidxu4
-rw-r--r--  1 root root 11217641  8. Dez 19:03 initrd.img-6.0.9-odroidxu4
-rw-r--r--  1 root root        0  8. Dez 19:03 .next
-rw-r--r--  1 root root  3672734 30. Nov 12:07 System.map-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       23  8. Dez 19:03 uInitrd -> uInitrd-6.0.9-odroidxu4
-rw-r--r--  1 root root 11217705  8. Dez 19:03 uInitrd-6.0.9-odroidxu4
-rwxr-xr-x  1 root root  6724096 30. Nov 12:07 vmlinuz-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       23  8. Dez 19:03 zImage -> vmlinuz-6.0.9-odroidxu4

It seems that the armbian-config does not install the dtb and because of its enforced reboot, it kills the boot process.

Edited by suchende
Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines