Odroid N2+ doesn't boot server image v6.12

[rosenrot00]

Using a 256G emmc and the server image v6.12 my Odroid N2+ doesn't boot. Here is the log.

 

The Homeassistant image works.

 

Would be nice to understand why it doesn't boot.

 

<00><00><00>G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:0;READ:0;0.
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:0000c067
L3:14000020
B2:00402000
B1:e0f83180

TE: 196470

BL2 Built : 06:17:13, Jun 28 2019. g12b gf0505d7-dirty - qi.duan@droid13

Board ID = 5
Set A53 clk to 24M
Set A73 clk to 24M
Set clk81 to 24M
A53 clk: 1200 MHz
A73 clk: 1200 MHz
CLK81: 166.6M
smccc: 000347a9
eMMC boot @ 0
sw8 s
DDR driver_vesion: LPDDR4_PHY_V_0_1_14 build time: Jun 28 2019 06:17:09
board id: 5
Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from eMMC, src: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from eMMC, src: 0x00038200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
00000000
emmc switch 1 ok
00000000
emmc switch 2 ok
fastboot data verify
verify result: 255
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
ddr clk to 1320MHz
Load ddrfw from eMMC, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0
00000000
emmc switch 0 ok
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from eMMC, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

R0_RxClkDly_Margin==94 ps 8
R0_TxDqDly_Margi==106 ps 9


R1_RxClkDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0

 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 
2D training succeed
auto size— 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00600024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass
 pre test  bdlr_100_average==425 bdlr_100_min==425 bdlr_100_max==425 bdlr_100_cur==425
 aft test  bdlr_100_average==425 bdlr_100_min==425 bdlr_100_max==425 bdlr_100_cur==425
non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 425
result report
boot times 0Enable ddr reg access
00000000
emmc switch 3 ok
Authentication key not yet programmed
get rpmb counter error 0x00000007
00000000
emmc switch 0 ok
Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from eMMC, src: 0x0006c200, des: 0x0175c000, size: 0x0009aa00, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0
E30HDR
MVN_1=0x00000000
MVN_2=0x00000000
[Image: g12b_v1.1.3375-8f9c8a7 2019-01-24 10:44:46 guotai.shen@droid11-sz]
OPS=0x40
ring efuse init
chipver efuse init
29 0c 40 00 01 03 0d 00 00 07 39 31 4e 31 53 50 
[0.019859 Inits done]
secure task start!
high task start!
low task start!
run into bl31
NOTICE:  BL31: v1.3(release):ab8811b
NOTICE:  BL31: Built : 15:03:31, Feb 12 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast

<debug_uart>
serial_meson serial@3000: pincu

U-Boot 2022.10-armbian-2022.10-S4deb-Pa713-H24ab-V6e0a-Bb703-R448a (Jan 24 2025 - 02:39:57 +0000) odroid-n2/n2-plus

Model: Hardkernel ODROID-N2
SoC:   Amlogic Meson G12B (S922X) Revision 29:c (40:2)
DRAM:  3.8 GiB
Core:  388 devices, 27 uclasses, devicetree: separate
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere… OK
In:    serial
Out:   serial
Err:   serial
Board variant: n2-plus
Net:   dwmac_meson8b ethernet@ff3f0000: Can’t get reset: -2
eth0: ethernet@ff3f0000
Hit any key to stop autoboot:  2 <08><08><08> 1 <08><08><08> 0 
starting USB…
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices… Failed to get keyboard state from device 1915:1047
3 USB Device(s) found
       scanning usb for storage devices… 0 Storage Device(s) found

Device 0: unknown device
Card did not respond to voltage select! : -110
unable to select a mode : -5
MMC Device 2 not found
no mmc device at slot 2
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.179 (29 ms)
*** Warning: no boot file name; using ‘C0A801B3.img’
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.179
Filename ‘C0A801B3.img’.
Load address: 0x1000000
Loading: *<08>T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-00-1e-06-42-56-3a
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.179
Filename ‘pxelinux.cfg/01-00-1e-06-42-56-3a’.
Load address: 0x1080000
Loading: *<08>T T T T T T T 

 

[usual user]

6 hours ago, rosenrot00 said:

Would be nice to understand why it doesn't boot.

The log is telling that the firmware can't operate the eMMC:

 

6 hours ago, rosenrot00 said:

Device 0: unknown device
Card did not respond to voltage select! : -110

Furthermore, the alternatively attempted BOOTP and PXE boot are also unsuccessful because it seems that a server is found, but the necessary bootflow is not configured correctly.
As you are running a quite dated U-Boot, maybe using a cureent release has better support for the eMMC.

[rosenrot00]

Isn’t uboot coming with the armbian image on the emmc?

 

Could you tell me where I find the most recent uboot? The last is from 2022?

Edited 3 hours ago by rosenrot00

[usual user]

26 minutes ago, rosenrot00 said:

Isn’t uboot coming with the armbian image on the emmc?

Certainly, but I don't know if anyone has taken the effort to integrate a current version so far.

 

27 minutes ago, rosenrot00 said:

Could you tell me where I find the most recent uboot?

The mainline U-Boot project always provides the source codes for the latest versions.
You can build it by yourself with the Armbian build framework, or use my build for a quick test.

[eselarm]

7 hours ago, rosenrot00 said:

Using a 256G emmc and the server image v6.12 my Odroid N2+ doesn't boot. Here is the log.

 

The Homeassistant image works.

Do they use the same U-Boot or different version?

It could be the server image is just composed in a faulty way, some detailed failure somewhere. I would build something for the specific SBC myself or copy the boot area from the HA image into your image/emmc. Or maybe wipe it an use an SD-card with only a U-Boot blob that you want or build yourself maybe from latest U-Boot denx.de. I have done that for QEMU variat, also did some non-standard changes and that works.

In a working Armbian, I have checked/installed 3 variants (vendor, current, edge) and EDK3-UEFI for my ROCK5B and then also switching kernels. No eMMC, but only SPI-flash using flashcp and dd for SD-card. But that is Rockchip, Amlogic I do not know, do not have.

[rosenrot00]

33 minutes ago, usual user said:

The mainline U-Boot project always provides the source codes for the latest versions.
You can build it by yourself with the Armbian build framework, or use my build for a quick test.

How would that work? I just downloaded your u-boot-meson.bin file. Where would I have to place it?

[rosenrot00]

19 minutes ago, eselarm said:

Or maybe wipe it an use an SD-card with only a U-Boot blob that you want or build yourself maybe from latest U-Boot denx.de. I have done that for QEMU variat, also did some non-standard changes and that works.

I'm not an expert about it - could you tell me how I would do that?

 

I currently see only the armbi_root partition on my emmc.

[usual user]

21 minutes ago, rosenrot00 said:

Where would I have to place it?

Use:

dd bs=512 seek=1 conv=notrunc,fsync if=odroid-n2/u-boot-meson.bin of=/dev/${entire-device-to-be-used}

as outlined in the referenced post to replace the existing firmware on the eMMC.

Firmare is residing outside of partition layout structures so you can only write it by absolute access.

[rosenrot00]

30 minutes ago, usual user said:

Use:

dd bs=512 seek=1 conv=notrunc,fsync if=odroid-n2/u-boot-meson.bin of=/dev/${entire-device-to-be-used}

as outlined in the referenced post to replace the existing firmware on the eMMC.

Firmare is residing outside of partition layout structures so you can only write it by absolute access.

 

Thank you that worked.

 

Awesome, what a pitty that the plain armbian image doesn't work. Maybe this is something for a developer but not sure how to reach them.

[usual user]

50 minutes ago, rosenrot00 said:

Thank you that worked.

I don't know your plans for how things are supposed to proceed. But if you plan to continue using my firmware build, I would suggest transferring it to the SPI flash, provided you are not wanted to use any other firmware in there.
- This relieves you from having to pay attention to restoring my firmware build when changing an image.
- You have two firmware versions available to you, between which you can switch with the SPI-MMC boot switch.
- Even without the eMMC module, you can boot an OS from another connected storage device.
- The U-Boot console is also available with an HDMI monitor and a USB keyboard and can be used for analysis in the event of startup problems. Of course, it is also used to select various boot options if autoboot is interrupted.