Messages

I would like to try the image on R4S, @spikerguy Can you link to the telegram chat? I couldn't find it.

https://personalbsd.org/?p=313 < there you go.

I tried booting the R2S image but that didn't work.

Hi all,

Thanks for the progress on getting this to work on ARM devices @nekoprog and @yrzr. Hopefully the PR will get merged soon :)

For now I resumed my effort to get a working NanoPi R2s image going, but I am stuck at U-Boot problems. I hope someone here is able to help me forward again :)

I have this as my config now:
https://github.com/wilmardo/tools/blob/nanopi-r2s/device/NPIR2S.conf

It contains all kinds of stabs in the dark like the .dtb from Debian and the loadaddr 32K moved over from the address in u-boot.

I currently have a working U-boot but it can't seem to find the kernel (or an UFS partition for that matter). I can mount the UFS partition fine on my PC so the SD card seems to be fine.

This is my current bootlog:

Code Select Expand


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=3781MB
FwPartOffset=2000 , 0
StorageInit ok = 34120
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 part:  0, name:                 , start:0x800, size:0x762000
recovery gpt success!
no find partition:uboot.
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 - 18:04:51 +0000)

Model: FriendlyElec NanoPi R2S
DRAM:  1022 MiB
PMIC:  RK8050 (on=0x40, off=0x01)
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 EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@ff500000.blk...
** Unrecognized filesystem type **
Found 3 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
393216 bytes read in 68 ms (5.5 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Booting /efi\boot\bootaa64.efi

>> FreeBSD EFI boot block
   Loader path: /boot/loader.efi

   Initializing modules: ZFS UFS
   Load Path: /efi\boot\bootaa64.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x19000)
   Probing 3 block devices...... done
    ZFS found no pools
    UFS found no partitions
Failed to load '/boot/loader.efi'
panic: No bootable partitions found!
## Application failed, r = 1
EFI LOAD 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 anyone point me into a new direction or something to try? I am really stuck at the moment, I tried everything I could think off.

Again, massive thanks for the porting of tools to ARM!

BTW: something seems to be preventing download of https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz

I was getting the same error but with infinite retries it completed 35 minutes or so:

Code Select Expand


wget --tries=0 https://people.freebsd.org/\~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz


I received my Nanopi R2S today and will try to compile the kernel hopefully soon. My attempts are stored in this repo:
https://github.com/wilmardo/tools/tree/nanopi-r2s

Are there working device configs and kernel configs around for the NanoPi R2s? I am trying to set them up myself but starting from something that is known to work is much nicer.