A64-H shutting down after starting kernel

[yht-km-mk]

My board shuts down after starting the kernel, I've put the serial terminal output below. Could anyone suggest whats wrong and how I could get the board working again. I have quite a few python scripts on the board that I need to get, so as a second question is there any way of retrieving those scripts without the kernel starting? Thanks in advance.

U-Boot SPL 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:31 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):
NOTICE:  BL31: Built : 23:33:29, Nov 27 2018
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x40b1870, model: Olimex A64-Olinuxino
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Detected AXP803 on RSB.
INFO:    PMIC: AXP803: Enabling DRIVEVBUS
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:31 +0000) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: Olimex A64-Olinuxino
DRAM:  1 GiB
Failed to probe SPI flash device
MMC:   mmc@1c0f000: 0
Loading Environment from EXT4... *** Warning - bad CRC, using default environment

Warning: HDMI PHY init timeout!
Warning: HDMI PHY init timeout!
Warning: HDMI PHY init timeout!
Warning: HDMI PHY init timeout!
In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   phy interface7
eth0: ethernet@1c30000, eth1: usb_ether
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2274 bytes read in 3 ms (740.2 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
Checking for /uEnv.txt...
Checking for /boot/uEnv.txt...
460 bytes read in 4 ms (112.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Loading FIT image...
37248711 bytes read in 1599 ms (22.2 MiB/s)
## Loading kernel from FIT Image at 58000000 ...
   Using 'config-9065' configuration
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel 5.10.105-olimex
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x580000d4
     Data Size:    20187144 Bytes = 19.3 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x40080000
     Entry Point:  0x40080000
     Hash algo:    crc32
     Hash value:   24d8219f
     Hash algo:    sha1
     Hash value:   fe5763f27c7116a383bfceef0c1a76f8cd09bc32
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading ramdisk from FIT Image at 58000000 ...
   Using 'config-9065' configuration
   Trying 'ramdisk-1' ramdisk subimage
     Description:  Ramdisk for kernel 5.10.105-olimex
     Type:         RAMDisk Image
     Compression:  Unknown Compression
     Data Start:   0x59340a14
     Data Size:    16855264 Bytes = 16.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x4fe00000
     Entry Point:  0x4fe00000
     Hash algo:    crc32
     Hash value:   0391a162
     Hash algo:    sha1
     Hash value:   97dbfd754b3bb25aef8b936eaae7148ba089fbcb
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Loading ramdisk from 0x59340a14 to 0x4fe00000
WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file!
## Loading fdt from FIT Image at 58000000 ...
   Using 'config-9065' configuration
   Trying 'fdt-4' fdt subimage
     Description:  unavailable
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x5a371398
     Data Size:    39730 Bytes = 38.8 KiB
     Architecture: AArch64
     Load Address: 0x4fa00000
     Hash algo:    crc32
     Hash value:   08c99f3a
     Hash algo:    sha1
     Hash value:   d2aa851749eaa1341f8989693055b85d2a17fd72
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Loading fdt from 0x5a371398 to 0x4fa00000
## Loading fdt from FIT Image at 58000000 ...
   Trying 'overlay-1' fdt subimage
     Description:  unavailable
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x5a3850ec
     Data Size:    330 Bytes = 330 Bytes
     Architecture: AArch64
     Load Address: 0x4fa10000
     Hash algo:    crc32
     Hash value:   4feb8819
     Hash algo:    sha1
     Hash value:   5a2294834f1bb2916cdbcde98423a535ef16022f
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Loading fdt from 0x5a3850ec to 0x4fa10000
## Loading fdt from FIT Image at 58000000 ...
   Trying 'overlay-2' fdt subimage
     Description:  unavailable
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x5a38531c
     Data Size:    330 Bytes = 330 Bytes
     Architecture: AArch64
     Load Address: 0x4fa20000
     Hash algo:    crc32
     Hash value:   764ecf6a
     Hash algo:    sha1
     Hash value:   89d6927b768cd47216c588c44ece170b7f8b5713
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Loading fdt from 0x5a38531c to 0x4fa20000
## Loading fdt from FIT Image at 58000000 ...
   Trying 'overlay-3' fdt subimage
     Description:  unavailable
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x5a38554c
     Data Size:    460 Bytes = 460 Bytes
     Architecture: AArch64
     Load Address: 0x4fa30000
     Hash algo:    crc32
     Hash value:   68dc2714
     Hash algo:    sha1
     Hash value:   22aaffcbf62558480912ddc0b9edcfeb2b8ce7b3
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Loading fdt from 0x5a38554c to 0x4fa30000
   Booting using the fdt blob at 0x4fa00000
   Loading Kernel Image
   Loading Ramdisk to 48fec000, end 49fff0e0 ... OK
   Loading Device Tree to 0000000048fdf000, end 0000000048febb15 ... OK
Applying overlay: '/usr/lib/olinuxino-overlays/sun50i-a64/sun50i-a64-i2c0.dtbo'...
330 bytes read in 7 ms (45.9 KiB/s)

Starting kernel ...

[JohnS]

Did it ever work? If so, what changed?

Where are the files you want? If SD card, you can read it elsewhere. If flash, can you boot a known-working SD card?

John

[LubOlimex]

Which board is that exactly? Does it have eMMC? Where do you boot from?

Sudden stops like that are either lack of sufficient powering or file system got corrupted or some hardware/software mismatch. Try with another source of power first.

As JohnS wrote, if you boot from SD card you can read and explore the SD card on any Linux machine to back up your stuff.

It is harder to do data recovery if you boot from eMMC.

[FalloutST]

JohnS some time you'll start help, I pray ^_^


Global Moderator answers right in the message.
Loading Environment from EXT4... *** Warning - bad CRC, using default environment
U-boot loaded from SD
Boot script loaded from MMC


I guess something broken at loading binaries.
.itb .scr

yht-km-mk
if you files on MMC so. best way is to boot from SD card standard image. Mount MMC and get it.
Any way problem is on MMC side with kernel.itb or boot.scr or any other binary in you boot directory.
By the way thank you now I found drivers I need to fix
07