Closed ARC-MX closed 4 months ago
I downloaded the image of nanopi R6s from the official websitehttps://www.armbian.com/nanopi-r6s/, but it failed to start no matter burning to sd card or emmc. I know a lot of people have this problem, like this page https://forum.armbian.com/topic/27904-armbian-images-for-r6s-r6c/?do=findComment&comment=164029 This is the log printed by the serial port:
DDR V1.12 52218f4949 cym 23/07/06-19:46:50 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0x1 CH0 RX Vref:27.5%, TX Vref:20.8%,19.8% CH1 RX Vref:26.3%, TX Vref:19.8%,20.8% CH2 RX Vref:27.5%, TX Vref:19.8%,19.8% CH3 RX Vref:27.1%, TX Vref:21.8%,21.8% change to F1: 528MHz change to F2: 1068MHz change to F3: 1560MHz change to F0: 2112MHz out U-Boot SPL board init U-Boot SPL 2017.09-g82417168bf-230508 #root (Sep 08 2023 - 20:53:43) unknown raw ID 0 0 0 unrecognized JEDEC id bytes: 00, 00, 00 Trying to boot from MMC2 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK ## Checking uboot 0x00200000 ... sha256(278bbce123...) + OK ## Checking fdt 0x0031f058 ... sha256(a4fd4b8eff...) + OK ## Checking atf-2 0xff100000 ... sha256(4b2065349b...) + OK ## Checking atf-3 0x000f0000 ... sha256(aa71013e72...) + OK Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 323.167/474.348 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45 NOTICE: BL31: Built : 10:11:21, Dec 27 2023 INFO: spec: 0x13 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 ERROR: dfs get fsp_params[0] error, 0xfead0003 != 0xfead0004 ERROR: dfs get fsp_params[1] error, 0xa2c != 0xfead0004 ERROR: dfs get fsp_params[2] error, 0xa34 != 0xfead0004 ERROR: dfs get fsp_params[3] error, 0xadc != 0xfead0004 ERROR: loader&trust unmatch!!! Please update loader if need enable dmc ERROR: current trust bl31 need match with loader ddr bin V1.13 or newer ERROR: current loader need match with trust bl31 V1.38-V1.40 INFO: BL31: Initialising Exception Handling Framework 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 2017.09-armbian (Jun 25 2024 - 01:32:49 +0000) Model: NanoPi R6S MPIDR: 0x81000000 PreSerial: 2, raw, 0xfeb50000 DRAM: 8 GiB Sysmem: init Relocation Offset: eda3e000 Relocation fdt: eb9f9d20 - eb9fecc8 CR: M/C/I Using default environment optee check api revision fail: -1.0 optee api revision is too low ### ERROR ### Please RESET the board ###
You can only download and install directly
main (main development branch)
Debian 12 Bookworm
No response
Jira ticket: AR-2405
This issue tracker does not accept bugs not related to the build framework (building Armbian to say). Issues running Armbian are collected in forums. https://armbian.com/bugs
What happened?
I downloaded the image of nanopi R6s from the official websitehttps://www.armbian.com/nanopi-r6s/, but it failed to start no matter burning to sd card or emmc. I know a lot of people have this problem, like this page https://forum.armbian.com/topic/27904-armbian-images-for-r6s-r6c/?do=findComment&comment=164029 This is the log printed by the serial port:
How to reproduce?
You can only download and install directly
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Debian 12 Bookworm
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct