Boot failed after flashed bios

Orion Series O6
21

Okay, after buying a 1.8V SPI Flash programmer, banging my head for some time, I think the situation is this:

  1. The Version 9.0.0 BIOS on Radxa’s Download Page ( https://docs.radxa.com/en/orion/o6/download#bios ) DOES NOT work with 64GB Boards.
  2. The other Version 0.3.0-1 listed at the top also DOES NOT work with 64GB Boards.
  3. The only version that I managed to get working was the link tucked away below under compatibility list: https://github.com/radxa-pkg/edk2-cix/releases/download/0.3.1-1/edk2-cix_0.3.1-1_all.deb

IF YOU HAVE A 64GB BOARD, I WOULD STRONGLY ADVISE AGAINST ATTEMPTING A BIOS UPDATE AT THIS POINT IN TIME. IT COULD LEAVE YOUR BOARD IN AN UNBOOTABLE STATE AND REQUIRE YOU TO PHYSICALLY FLASH THE BIOS CHIP IN ORDER TO RECOVER.

If you do end up in this state, the instructions to follow for flashing are here: Guide: Flash Bios with CH341A (macos/linux)

@RadxaYuntian It would be nice to have prominent warnings on the BIOS download page indicating that the Version 9.0.0 BIOS is not compatible with all 64GB board variants.

1 Like
22

This was mentioned here: https://docs.radxa.com/en/orion/o6/download#bios-compatibility-instructions

23

I think my board may’ve bricked. This wasn’t triggered by a firmware update, but might be related to something I did in BIOS. Last action I took was:

  1. Set from ACPI to Device Tree
  2. Told boot manager to boot from USB (was about to install Radxa Image to try Vulkan drivers)
  3. Prompted to restart to save changes, etc.

After that, no screen output… power monitor shows ~2W (20V/0.1A)… no keyboard light, etc.

This is my EC UART output:

Channel0: (3, 13)2.539V T:303.244(29.7 C) Rt:80.034.
Channel1: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
Channel3: (2, fb)2.461V T:306.035(32.5 C) Rt:70.431.
Channel4: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
Channel5: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
rPVT_TEMP w fail!
rCsuPM fail!
GPDRD:ab, PLT_RST:0.
dut warm reboot.
GPDRD:ab, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.
GPDRD:ab, PLT_RST:0.
dut warm reboot.
GPDRD:ab, PLT_RST:0.
dut warm reboot.
GPDRD:ab, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.
GPDRD:eb, PLT_RST:0.
dut warm reboot.

Powered off, it’s a little bit less noisy:

dut warm reboot.
GPDRB:b6 SOC_SLP5:1.
s3 n_off.
s5 n_off.
GPDRH:a5 SOC_SLP3:1.
GPDRH:a5, SYS_S0_PG:0.
GPDRH:a5, SYS_S3_PG:0.
GPDRD:ba, PLT_RST:0.
Blink led state from 0 to 2.
Power state from S0 to SD.
OS suspend from S0 to SD.
Power key release.
Channel0: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
Channel1: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel3: (2, f8)2.452V T:306.375(32.9 C) Rt:69.354.
Channel4: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel5: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
rPVT_TEMP w fail!
rCsuPM fail!
Channel0: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
Channel1: (3, 10)2.529V T:303.600(30.1 C) Rt:78.728.
Channel3: (2, f7)2.448V T:306.488(33.0 C) Rt:69.000.
Channel4: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel5: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
rPVT_TEMP w fail!
rCsuPM fail!
Channel0: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel1: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel3: (2, f8)2.452V T:306.375(32.9 C) Rt:69.354.
Channel4: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel5: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
rPVT_TEMP w fail!
rCsuPM fail!
rSCM3218_word fail(4)
rSCM3218 raw:(0x06)
wCsuPM addr:0x0010 fail!
wPM reg[16]:29.9(29.981).
wCsuPM addr:0x0011 fail!
wPM reg[17]:29.9(29.981).
wCsuPM addr:0x0012 fail!
wPM reg[18]:0.0(0.000).
wCsuPM addr:0x0013 fail!
wPM reg[19]:32.8(32.875).
wCsuPM addr:0x0014 fail!
wPM reg[20]:29.9(29.981).
wCsuPM addr:0x0015 fail!
wPM reg[21]:29.8(29.863).
Channel0: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel1: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel3: (2, f9)2.455V T:306.262(32.8 C) Rt:69.710.
Channel4: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel5: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
rPVT_TEMP w fail!
rCsuPM fail!
Current fan rpm is 0.
Channel0: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
Channel1: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel3: (2, fb)2.461V T:306.035(32.5 C) Rt:70.431.
Channel4: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel5: (3, 12)2.535V T:303.363(29.9 C) Rt:79.595.
rPVT_TEMP w fail!
rCsuPM fail!
Channel0: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel1: (3, 11)2.532V T:303.481(30.0 C) Rt:79.160.
Channel3: (2, fb)2.461V T:306.035(32.5 C) Rt:70.431.
Channel4: (3, 10)2.529V T:303.600(30.1 C) Rt:78.728.
Channel5: (3, 10)2.529V T:303.600(30.1 C) Rt:78.728.
rPVT_TEMP w fail!
rCsuPM fail!
GPDRA:73 INT_PD2:0.
Trigger interrupt SlaveAddr:d0.

Is my board RIP?

24

Had a bit more of a tinker earlier. Here’s the output from UART5:

ERROR: Fail to load memory con[BROM]# CiX Bootrom Sky1 Alpha1.0
drv_ddr_init ver 10002 start ...
ERROR: Fail to load memory con�[BROM]# CiX Bootrom Sky1 Alpha1.0
drv_ddr_init ver 10002 start ...
ERROR: Fail to load memory con[BROM]# CiX Bootrom Sky1 Alpha1.0
drv_ddr_init ver 10002 start ...
ERROR: Fail to load memory con[BROM]# CiX Bootrom Sky1 Alpha1.0
drv_ddr_init ver 10002 start ...
ERROR: Fail to load memory con[BROM]# CiX Bootrom Sky1 Alpha1.0
drv_ddr_init ver 10002 start ...
ERROR: Fail to load memory con[BROM]# CiX Bootrom Sky1 Alpha1.0

I can only get output from EC_UART and UART5. Does the above indicate the memory controller is broken?

25

Hi jimhamiru,

From what you describe (BootROM output on UART5, DDR init failing), it really looks more like a soft-brick to me.
What makes you think it could be a hard-brick this time?

Have you already, after unplugging power source and the RTC battery,
tried a full erase of the SPI flash, then reflashing a firmware you know works on your board?

:crossed_fingers:

1 Like
26

Thanks! Will try that out.

>What makes you think it could be a hard-brick this time?

I hadn’t thought about it before, but where and how do BIOS configuration (not the firmware itself) get saved on the O6? Does this get saved somewhere to the SPI Flash and is non-volatile (doesn’t require a battery to retain the config?)

I didn’t expect it would be an issue with the flash given I didn’t do an update. But maybe it was the config steps I took above that caused it to corrupt.

After testing, I’ll feedback on result in case it helps others. Firmware I was on would’ve been V0.3.1-1 (64GB model).

27

Thank you, that actually worked! I’m guessing BIOS settings themselves are actually stored in the SPI Flash chip??

I went with the latest BIOS release (V1.0.0-5) which seems okay with my 64GB unit (previously, I had trouble finding one that worked with my 64GB model).

I am having some trouble booting the official Radxa image into Gnome (black-screen), but that’s a different issue and I’m going to try the Debian Image instead (main intent of all this was to test the Mali Drivers on Llama.cpp benchmarks - but I needed to revert to an older kernel).

1 Like