Jump to content

struthio

Members
  • Posts

    2
  • Joined

  • Last visited

  1. Hi, I have 4 FriendlyElec NanoPi Neo 3 boards. Till now they were working fine, but after today 'apt upgrade' none of them boot anymore. I got one connected in debug mode and got this log: => DDR version 1.16 20190528 ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=16 CS=1 Die Bus-Width=16 Size=2048MB ddrconfig:14 OUT Boot1 Release Time: May 13 2019 17:34:36, version: 2.50 ChipType = 0x11, 248 mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=30436MB FwPartOffset=2000 , 0 StorageInit ok = 33580 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x337a9f0 signature is wrong recovery gpt... GPT 0x337a9f0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 hdr 000000000337a3b0 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, Load OK, addr=0x200000, size=0xab950 RunBL31 0x40000 INFO: Preloader serial: 2 NOTICE: BL31: v1.3(debug):403e0b816 NOTICE: BL31: Built : 14:13:08, Aug 11 2020 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (May 06 2021 - 17:55:54 +0000) Model: FriendlyElec NanoPi R2S DRAM: 2 GiB PMIC: RK8050 (on=0x40, off=0x00) MMC: mmc@ff500000: 1 Loading Environment from MMC... MMC Device 0 not found *** Warning - No MMC card found, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: FriendlyElec NanoPi R2S Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 8 ms (388.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 261 bytes read in 4 ms (63.5 KiB/s) 14236833 bytes read in 623 ms (21.8 MiB/s) 30083584 bytes read in 1307 ms (22 MiB/s) Failed to load '/boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 1314 bytes read in 9 ms (142.6 KiB/s) Applying kernel provided DT overlay rockchip-spi-jedec-nor.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 1266 bytes read in 9 ms (136.7 KiB/s) Applying kernel provided DT overlay rockchip-spi-spidev.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT Failed to load '/boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb' Moving Image from 0x2080000 to 0x2200000, end=3f50000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14236769 Bytes = 13.6 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 SCRIPT FAILED: continuing... MMC Device 0 not found no mmc device at slot 0 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. starting USB... No working controllers found ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-b6-20-d4-48-8b-b5 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 (...) SD card is good and I can read it in PC in normal SD-to-USB reader. Is there a way to boot from this state ? Is NEO3 still supported ?
  2. hi, I am running newest armbian for NEO3. I've noticed that when I issue poweroff command armbian shuts down correctly, but the CPU (with heatsink) remains hot. I left my board for 2 days in poweroff state and it remained 'warm' all the time. Is there something that can be done to put CPU to sleep before shutting down system (or some low power state) ?
×
×
  • Create New...