Tungsteno74

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. Thanks @guidol, i solved this issue. Apparently for some unknown reason the sdcard bood image was corrupted. I reflashed it with the latest armbian and the boot log now is as expected. Cheers
  2. I noticed that with Nanopi NEO v1.2 the fixup.src is not loaded at startup, but after some googling i noticed that other boards with h3 chip succesfully load the correct fixup. My boot log: U-Boot SPL 2018.11-armbian (Feb 08 2019 - 11:04:44 +0100) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2018.11-armbian (Feb 08 2019 - 11:04:44 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: phy interface0 Error: ethernet@1c30000 address not set. eth-1: ethernet@1c30000 230454 bytes read in 35 ms (6.3 MiB/s) Unknown command 'bmp' - try 'help' starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 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 mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3798 bytes read in 20 ms (184.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 278 bytes read in 16 ms (16.6 KiB/s) 8002310 bytes read in 637 ms (12 MiB/s) 7489584 bytes read in 602 ms (11.9 MiB/s) Found mainline kernel configuration 29427 bytes read in 90 ms (318.4 KiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8002246 Bytes = 7.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 EHCI failed to shut down host controller. EHCI failed to shut down host controller. Loading Ramdisk to 4985e000, end 49fffac6 ... OK reserving fdt memory region: addr=43000000 size=6d000 Loading Device Tree to 497ee000, end 4985dfff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. it's a normal behaviour? and... This can be the cause of a random boot/reboot stuck (after some status led startup blinks)? Thanks in advance for your help and work on this awesome project.