Hero Intelligent Posted January 15 Share Posted January 15 I first made a self-built image for nanopi-r2s and everything is fine. But another self-built image of Nanopi-R2S seems refuse to boot after enabling these configurations: `DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT`, then `DEBUG_INFO_BTF` and `MODULE_ALLOW_BTF_MISMATCH` But the LED on RJ45 blinks, and I can ping the IP that I get from my router DHCP, but SSH connection refused. So I guess it may have booted, but refuse SSH connection. I have no TTL serial connections yet, I'll check it and post the logs here some time later. Can anybody help? How can I enable ssh with? Is it possible to enable it at build stage? Thanks. 0 Quote Link to comment Share on other sites More sharing options...
Hero Intelligent Posted February 21 Author Share Posted February 21 This is the output of my board: DDR version 1.16 20190528 ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 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=15216MB FwPartOffset=2000 , 0 StorageInit ok = 24008 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=0xb3690 RunBL31 0x40000 01INFO: 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 2022.07-armbian (Jan 13 2024 - 14:06:57 +0000) Model: FriendlyElec NanoPi R2S DRAM: 1022 MiB PMIC: RK8050 (on=0x40, off=0x01) Core: 231 devices, 23 uclasses, devicetree: separate MMC: mmc@ff500000: 1 Loading Environment from MMC... *** Warning - bad CRC, 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 3548 bytes read in 8 ms (432.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 176 bytes read in 7 ms (24.4 KiB/s) 196677074 bytes read in 8585 ms (21.8 MiB/s) 35713536 bytes read in 1561 ms (21.8 MiB/s) 64562 bytes read in 16 ms (3.8 MiB/s) 2698 bytes read in 13 ms (202.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=44b0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 196677010 Bytes = 187.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... 1b7 1b[r 1b[999;999H 1b[6n 1b8No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image MMC Device 0 not found no mmc device at slot 0 starting USB... Bus usb@ff5c0000: ehci_generic usb@ff5c0000: Failed to get clocks (ret=-19) Port not available. Bus usb@ff5d0000: USB OHCI 1.0 Bus usb@ff580000: USB DWC2 scanning bus usb@ff5d0000 for devices... 1 USB Device(s) found scanning bus usb@ff580000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-22-19-a0-37-f6-ff ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/00000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/0000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/000000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/00000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/0000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/00 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/0 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/default-arm-rk3328-evb_rk3328 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/default-arm-rk3328 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/default-arm ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Retrieving file: pxelinux.cfg/default ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 Config file not found ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 => 0 Quote Link to comment Share on other sites More sharing options...
usual user Posted February 21 Share Posted February 21 12 minutes ago, Hero Intelligent said: Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... broken build 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.