R2C Plus - Eflasher not working with Debian Bullseye image

: phil535

: Posts: 2; Joined: Sat Mar 04, 2023 5:51 pm

Sat Mar 04, 2023 7:40 pm

by phil535 » Sat Mar 04, 2023 7:40 pm

Cannot flash debian bullseye to R2C PLUS EMMC according to the instructions in the wiki.

What I did:
1. Flash the following image to the sdcard using etcher:

Code: Select all

rk3328-eflasher-debian-bullseye-core-5.15-arm64-20230210.img.gz

2. Insert the SD-card into into NanoPi R2C Plus.
3. Power on the NanoPi R2C Plus
4. Wait until Installation is done according to the wiki (SYS Slow flashing, LAN On, WAN On)
5. Power off the NanoPi R2C Plus
6. Eject the SD-card from the NanoPi R2C Plus
7. Power on the NanoPi R2C Plus
8. System is stuck, SYS LED is on, both network interfaces wont link up when connecting to ethernet

Debug output of EMMC boot after the procedure above:

Code: Select all

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:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
SdmmcInit=0 NOT PRESENT
StorageInit ok = 11468
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 part:  0, name:            uboot, start:0x4000, size:0x2000
GPT part:  1, name:            trust, start:0x6000, size:0x2000
GPT part:  2, name:             misc, start:0x8000, size:0x2000
GPT part:  3, name:             dtbo, start:0xa000, size:0x2000
GPT part:  4, name:         resource, start:0xc000, size:0x8000
GPT part:  5, name:           kernel, start:0x14000, size:0x14000
GPT part:  6, name:             boot, start:0x28000, size:0x18000
GPT part:  7, name:           rootfs, start:0x40000, size:0x260000
GPT part:  8, name:         userdata, start:0x2a0000, size:0xbeffdf
find part:uboot OK. first_lba:0x4000.
find part:trust OK. first_lba:0x6000.
LoadTrust Addr:0x6000
No find bl30.bin
Load uboot, ReadLba = 4000
Load OK, addr=0x200000, size=0xeabf8
RunBL31 0x40000
NOTICE:  BL31: v1.3(release):734d842
NOTICE:  BL31: Built : 15:29:53, Dec 26 2019
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
INFO:    BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-235-g3b0152ca #231 Fri Mar 13 02:01:39 UTC 2020 aarch64)


INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.4


INF [0x0] TEE-CORE:init_teecore:83: teecore inits done

INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-g43267f9286-200623 #root (Jul 07 2021 - 16:49:31 +0800)

Board: FriendlyELEC RK3328 board
PreSerial: 2
DRAM:  992 MiB
Sysmem: init
Relocation Offset: 3dbd8000, fdt: 3bdcd838
Using default environment

mmc@ff500000: 1, mmc@ff520000: 0
Bootdev(atags): mmc 0
MMC0: High Speed, 52Mhz
PartType: EFI
boot mode: None
Found DTB in resource part
Failed to load DTB
Failed to get kernel dtb, ret=-19
rockchip_set_serialno: could not find efuse device
CLK: (sync kernel. arm: enter 600000 KHz, init 600000 KHz, kernel 0N/A)
  apll 400000 KHz
  dpll 664000 KHz
  cpll 1200000 KHz
  gpll 491009 KHz
  npll 600000 KHz
  armclk 600000 KHz
  aclk_bus 150000 KHz
  hclk_bus 75000 KHz
  pclk_bus 75000 KHz
  aclk_peri 150000 KHz
  hclk_peri 75000 KHz
  pclk_peri 75000 KHz

Net:   No ethernet found.
Hit key to stop autoboot('CTRL+C'):  1  0 

## Booting Rockchip Format Image
Failed to load DTB
Failed to read fdt, ret=-19
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
starting USB...
Bus usb@ff5c0000: Port not available.
Bus usb@ff580000: 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
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rockchip
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
nanopi-r2#

This exact same procedure works with the friendlywrt image but not with the debian image.

I also tried to manually trigger the eflasher on the Eflasher OS with default autoStart and .gz file but without success.

Is there anything in the instructions I did wrong or missed out?

Best Regards

Re: R2C Plus - Eflasher not working with Debian Bullseye image

: phil535

: Posts: 2; Joined: Sat Mar 04, 2023 5:51 pm

Tue Apr 18, 2023 8:41 pm

by phil535 » Tue Apr 18, 2023 8:41 pm

Finally got something to work on EMMC on the R2C Plus.

Here is how i got FriendlyWrt22 docker image working on the EMMC:

Flash the rk3328-eflasher-multiple-os-20230404-22g.img.gz image to your SD card.

Modify the autoStart variable in the [General] section in the eflasher.conf file on the SD card to friendywrt22-docker so it looks like as follows:

Code: Select all

[General]
; Automate OS installation at system startup,
; Use the "autoStart" field to specify the image path or RAW image file,
; The RAW image file can be a gzip compressed file,
; The RAW image file extension must be ".raw" or ".gz",
; Available values: friendlywrt22,friendlywrt22-docker,friendlycore-lite-focal-arm64,debian-bullseye-core-arm64
autoStart=friendlywrt22-docker

Savely eject the SD card from your computer and insert it in the R2C Plus.
Power on the R2C Plus
Wait until installation is complete (SYS slow flashing, WAN and LAN On)
Eject the SD Card from R2C Plus while powered on
Wait until initial setup has finished by watching the LEDs again
FriendlyWrt should now be available on the LAN port at 192.168.2.1 via SSH and HTTPS
user: root
password: password
To also allow access on WAN port, set the input chain in the firewall section of the WAN interface to accept.

Sadly this still does not work with the debian image.