Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rock 4C+ doesn't boot at all with every image #6

Open
killianeletellier opened this issue May 1, 2023 · 17 comments
Open

Rock 4C+ doesn't boot at all with every image #6

killianeletellier opened this issue May 1, 2023 · 17 comments

Comments

@killianeletellier
Copy link

My Rock 4C+ doesn't boot with every image I tried.

I use the alimentation shipped with the SBC, I tried with several SD cards, I also tried to flash with BalenaEtcher on Linux and with Rufus on Windows, but the Rock doesn't want to boot : there's only a green solid light, no blue one, and no signal is sent through the HDMI ports.
@RadxaYuntian
Copy link
Member

Did you also post on our forum, and which image have you tried?

@killianeletellier
Copy link
Author

Yes, I've also asked this question on your forum.

I tried every official image recommanded on the Rock 4C+ download page, I also tried every image of the latest release of this repo (20230312-1521) and those of the latest pre-release (20230501-0118).

So... I don't know what else I could do to make the Rock working :-/

@AMuellerAtAHS
Copy link

For me the official Debian release works fine on rock 4 c plus. I also used BalenaEtcher to create a SD card.

@killianeletellier
Copy link
Author

Thanks ! I'll try it :)

@killianeletellier
Copy link
Author

killianeletellier commented May 8, 2023 •
edited
Loading

It still doesn't work...
I only get a solid green light and no signal in the both HDMI ports...

@killianeletellier
Copy link
Author

killianeletellier commented May 8, 2023 •
edited
Loading

I wonder if the problem couldn't come from a malfunction of the microSD slot.

How could I check if it functions normally ?

I'm sorry, I know that this repo isn't the ideal place for this kind of questions, but I don't get any answer on the Radxa's forum.

@AMuellerAtAHS
Copy link

You could try to follow the instructions on serial console maybe you can get any output.

@infinite-dark
Copy link

I have exactly the same problem. None of the 20230312-1521 images work.
Armbian, bullseye, focal, jammy. Tried them all on the eMMC module and none of them worked.

The only image that currently works for me is the old focal server 4.4.

@RadxaYuntian
Copy link
Member

RadxaYuntian commented May 23, 2023 •
edited
Loading

@infinite-dark , do you happen to have a serial cable available? If so some boot log will be appreciated.

I'll also test it on eMMC just to make sure.

Edit: here is how b55 image running on my ROCK 4C+ v1.41 on eMMC.

@yoyojacky
Copy link

what is the meaning of b55 image ? build for 55 times?
is there an explainnations about the code name of b55?

@yoyojacky
Copy link

I've encounted the same problem with : https://github.com/radxa-build/rock-4c-plus/releases/download/20230312-1521/Armbian_23.05.0-trunk_Rockpi-4cplus_bullseye_current_5.15.101_kde-plasma_desktop.img.xz .
Unzipped it with 7zip and flash it to TF card with etcher tool, but once booting up, there is nothing display on screen...

@RadxaYuntian
Copy link
Member

It's the build number embedded in the file: https://github.com/radxa-build/rock-4c-plus/releases/tag/20230312-1521

Please do not use the automatically generated Armbian image. They were there for some historical reasons. The latest release no longer builds them.

@infinite-dark
Copy link

@infinite-dark , do you happen to have a serial cable available? If so some boot log will be appreciated.

I'll also test it on eMMC just to make sure.

Sorry for the late reply. I tested on eMMC. My board version is 1.2. Here's the log I got.

U-Boot 2017.09-00026-g2431fa34678 (Feb 14 2022 - 21:41:40 +0800)

Model: Radxa ROCK Pi 4B
PreSerial: 2
DRAM:  3.9 GiB
Relocation Offset is: f5bdd000
Sysmem: init
I2c speed: 400000Hz
rk8xx_read: read reg 0x17 failed, ret=-121
rk8xx_read: read reg 0x17 failed, ret=-121
"Synchronous Abort" handler, esr 0x96000010
* Relocate offset = 00000000f5bdd000
* ELR(PC)    =   000000000025964c
* LR         =   0000000000259634
* SP         =   00000000e9dc6ed0

* ESR_EL2    =   0000000096000010
        EC[31:26] == 100101, Exception from a Data abort, from current exception level
        IL[25] == 1, 32-bit instruction trapped

* DAIF       =   00000000000003c0
        D[9] == 1, DBG masked
        A[8] == 1, ABORT masked
        I[7] == 1, IRQ masked
        F[6] == 1, FIQ masked

* SPSR_EL2   =   0000000080000349
        D[9] == 1, DBG masked
        A[8] == 1, ABORT masked
        I[7] == 0, IRQ not masked
        F[6] == 1, FIQ masked
        M[4] == 0, Exception taken from AArch64
        M[3:0] == 1001, EL2h

* SCTLR_EL2  =   0000000030c51835
        I[12] == 1, Icaches enabled
        C[2] == 1, Dcache enabled
        M[0] == 1, MMU enabled

* HCR_EL2    =   000000000800003a
* VBAR_EL2   =   00000000f5ddd800
* TTBR0_EL2  =   00000000f7ff0000

x0 : 0000000000000000 x1 : 00000000f5e87b3b
x2 : 00000000f5ea86d8 x3 : 00000000e9de3cc0
x4 : 00000000ffffff87 x5 : 00000000e9dfac10
x6 : 0000000000000021 x7 : 00000000f5ea8698
x8 : 00000000e9dfae00 x9 : 0000000000000008
x10: 00000000ffffffe0 x11: 0000000000000006
x12: 000000000001869f x13: 00000000f5eab760
x14: 00000000f5eab6e8 x15: 00000000fffffffe
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000e9dd4d80 x19: 00000000e9dfac70
x20: 0000000000000009 x21: 00000000e9dfad58
x22: 00000000e9de3c80 x23: 00000000f5e98e82
x24: 00000000e9df1500 x25: 000000000036ee80
x26: 00000000f5ea0695 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000e9dc70b0

SP:
e9dc6ed0:  00000000 00000000 00000000 00000000 
e9dc6ee0:  00000000 00000000 f5e9a1bc 00000000 
e9dc6ef0:  00000000 00000000 00000000 00000000 
e9dc6f00:  f5e9a203 00000000 f5e9a229 00000000 
e9dc6f10:  f5e9a276 00000000 f5e9a2c3 00000000 
e9dc6f20:  f5e9a303 00000000 f5e9a343 00000000 
e9dc6f30:  f5e9a380 00000000 00000000 00000000 
e9dc6f40:  00000000 00000000 f5e9a3bd 00000000 
e9dc6f50:  e9dc70b0 00000000 f5ddda0c 00000000 
e9dc6f60:  e9dfac70 00000000 00000002 00000000 
e9dc6f70:  f7ff0000 00000000 0800003a 00000000 
e9dc6f80:  30c51835 00000000 e9dc6ed0 00000000 
e9dc6f90:  80000349 00000000 f5ddd800 00000000 
e9dc6fa0:  000003c0 00000000 96000010 00000000 
e9dc6fb0:  f5e3664c 00000000 00000000 00000000 
e9dc6fc0:  f5e87b3b 00000000 f5ea86d8 00000000 


Call trace:
  PC:   [< 0025964c >]
  LR:   [< 00259634 >]

Stack:
        [< 0025964c >]
        [< 00230a08 >]
        [< 00231acc >]
        [< 00231b1c >]
        [< 0025953c >]
        [< 002030d8 >]
        [< 00277f7c >]
        [< 00215ef8 >]
        [< 00201b8c >]

NOTE: Please use ./scripts/stacktrace.sh to parse trace info
Resetting CPU ...

DDR Version 1.20 20190314
In
soft reset
SRX
channel 0
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 1
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 1
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 1
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 315
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14800MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67564
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part:  0, name:          loader1, start:0x40, size:0x1f40
GPT part:  1, name:          loader2, start:0x4000, size:0x2000
GPT part:  2, name:            trust, start:0x6000, size:0x2000
GPT part:  3, name:             boot, start:0x8000, size:0x100000
GPT part:  4, name:           rootfs, start:0x108000, size:0x2b1aa9
no find partition:uboot.
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xf1b44
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):0e7a845
NOTICE:  BL31: Built : 16:13:46, Apr 17 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1181): pd status 3e
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 latest-2022.10-1-4debc57a-00007-gb923c1b6 (Mar 06 2023 - 15:54:16 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Radxa ROCK 4C+
DRAM:  3.9 GiB
PMIC:  RK8090 (on=0x40, off=0x00)
Core:  283 devices, 27 uclasses, devicetree: separate
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... mmc fail to send stop cmd
*** ERROR: Can't read GPT Entries ***
find_valid_gpt: *** ERROR: Invalid GPT ***
*** ERROR: Can't read GPT header ***
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
*** ERROR: Can't read GPT Entries ***
.
.
.
.
.
*** Warning - !read failed, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Radxa ROCK 4C+
Net:   eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: ehci_generic usb@fe380000: Failed to get clocks (ret=-19)
Port not available.
Bus usb@fe3c0000: ehci_generic usb@fe3c0000: Failed to get clocks (ret=-19)
Port not available.
Bus usb@fe800000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fe900000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe800000 for devices... 1 USB Device(s) found
scanning bus usb@fe900000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
mmc fail to send stop cmd
*** ERROR: Can't read GPT Entries ***
find_valid_gpt: *** ERROR: Invalid GPT ***
.
.
.
.
.
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
rockchip_pcie pcie@f8000000: PCIe link training gen1 timeout!

Device 0: unknown device

Device 0: unknown device
rockchip_pcie pcie@f8000000: failed to find ep-gpios property
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-16-89-38-e8-2e-16
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/00000000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/0000000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/000000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/00000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/0000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/00
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/0
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/default-arm-rk3399-evb_rk3399
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/default-arm-rk3399
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/default-arm
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Retrieving file: pxelinux.cfg/default
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
Config file not found

I replaced most "*** ERROR: Can't read GPT Entries ***" with the single dot lines because it repeated a few tens of times.
This is the output from ubuntu jammy, b55.

@RadxaYuntian
Copy link
Member

Do you have SPI bootloader flashed? I see the initial part of the log is from U-Boot 2017.09, which is no longer used in our latest images.

If you do have SPI bootloader installed, please clear it first.

@infinite-dark
Copy link

Do you have SPI bootloader flashed? I see the initial part of the log is from U-Boot 2017.09, which is no longer used in our latest images.

If you do have SPI bootloader installed, please clear it first.

No, I do not. I've never done anything like that to the board.
I even cleared it now - the way the wiki describes - and there is no change.

@RadxaYuntian
Copy link
Member

Please try booting without microSD or eMMC, and see if you still getting logs from U-Boot 2017. If so you didn't clear the SPI flash successfully.

@infinite-dark
Copy link

infinite-dark commented Jul 12, 2023 •
edited
Loading

I confirm that there is no output without microSD/eMMC.
By the way - I found out that the only system that boots up without problems in my case is DietPi.
edit: Armbian 22.05.2 also seems to boot but without any video output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@yoyojacky @killianeletellier @AMuellerAtAHS @RadxaYuntian @infinite-dark