Andy Posted March 29, 2018 Posted March 29, 2018 An hour a go I powered down my Neo Core 2 and now I can't get it to boot properly. When I hook it to the serial Monitor this is the output. It tries to load the "-fixup.scr" file in the /boot/dtb/allwinner/overlay folder but of course this is not available. With the extfls command I searched the folder and those two files would be available: sun50i-h5-fixup.scr sun50i-a64-fixup.scr The "sun50i-h5-fixup.scr" would be the right one for my processor however why does it choose "-fixup.scr" instead? Here is the boot sequence output: Reveal hidden contents U-Boot SPL 2017.11-armbian (Mar 20 2018 - 14:52:25) DRAM: 1024 MiB Trying to boot from MMC2 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):ae78724 NOTICE: BL3-1: Built : 14:52:20, Mar 20 2018 NOTICE: DT: sun50i-h5-nanopi-neo-plus2 NOTICE: SCPI: dummy stub handler, implementation level: 000000 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.11-armbian (Mar 20 2018 - 14:52:25 +0100) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO Plus 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3100 bytes read in 180 ms (16.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 0 bytes read in 82 ms (0 Bytes/s) MMC: no card present mmc_init: -123, time 2 ** Bad device mmc 0 ** 30723 bytes read in 372 ms (80.1 KiB/s) ** File not found /boot/dtb/allwinner/overlay/-fixup.scr ** 4925983 bytes read in 505 ms (9.3 MiB/s) 13080584 bytes read in 824 ms (15.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4925919 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49b4d000, end 49fff9df ... OK reserving fdt memory region: addr=4fa00000 size=6d000 Loading Device Tree to 0000000049add000, end 0000000049b4cfff ... OK Starting kernel ... Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Igor Posted March 30, 2018 Posted March 30, 2018 On 3/29/2018 at 9:22 PM, Andy said: ** File not found /boot/dtb/allwinner/overlay/-fixup.scr ** Expand You can ignore that ... What happens after this part: Starting kernel ... Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Andy Posted March 30, 2018 Author Posted March 30, 2018 thx. it keeps printing out the same line: Begin: Running /scripts/local-block ... done. and after 10 or so seconds it does reboot and start over again
zador.blood.stained Posted March 30, 2018 Posted March 30, 2018 On 3/29/2018 at 9:22 PM, Andy said: 0 bytes read in 82 ms (0 Bytes/s) Expand /boot/armbianEnv.txt is either empty or corrupted so u-boot can't load the necessary environment variables from it
Andy Posted March 30, 2018 Author Posted March 30, 2018 Phu now it's working again. So this is what I did: I made a bootable SD Card to boot the system form the SD. Then I used chkdsk on the internal 8GB eMMC. Then I powered off the device, removed the SD-Card and now it works again.... strange... But thx for the help hope this won't happen again...
Recommended Posts