Odroid C4 - boot problem October 2023

Post Reply
flavio
Posts: 11
Joined: Fri Jun 03, 2022 2:40 pm
languages_spoken: english
ODROIDs: C2, C4, U3
Has thanked: 0
Been thanked: 0
Contact:

Odroid C4 - boot problem October 2023

Post by flavio »

Hi!
I received a few days ago a large batch of Odroids C4 from an european distributor.
These boards seem to have a problem similar to this one: viewtopic.php?f=207&t=44634&p=350786&hi ... HA#p350786
Not exactly the same but still something that has to do with boot process: I tried many boards from this batch and, apparently, all have the same problem: sometimes they are unable to complete the booting process.
I use your ubuntu image on 16bg eMMCs. These boards are from production EL2308.
This is what is happening: I take a new C4 from this batch, I put the eMMC module correctly programmed and it works just fine a few times... I power it off and it doesn't boot anymore, either it won't boot or the process will stop at one point. Then I power off, on again and it works... maybe it works 10 times but then, again, it doesn't boot anymore, it's just random. It can act like this 10 times, 2 times, 100 times.
So, at this point, I decided to try boards from other batches I have here... for example batch EL2301 but we tried other too. Same configuration, same power supply (9v 3A), same eMMC... they ALWAYS work as it should 100% no matter what.
Do you have evidence of this problem? Is there something I should look? A faulty regulator? Some hardware revision or component revision?
If you need to, I made a video showing ax example of this.

Thanks!

User avatar
odroid
Site Admin
Posts: 42177
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3609 times
Been thanked: 2004 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by odroid »

We have already shipped over 5,000 LOT EL2308 units, and there have been no reports of random boot instability yet. I will inquire with the hardware team about any changes.

I have a couple of questions to investigate this issue.
How many C4 boards of EL2308 LOT do you have?
Can you please upload the boot log that appears when booting fails with the USB-UART adapter?
Which devices do you connect to USB ports and GPIO ports?

flavio
Posts: 11
Joined: Fri Jun 03, 2022 2:40 pm
languages_spoken: english
ODROIDs: C2, C4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Odroid C4 - boot problem October 2023

Post by flavio »

odroid wrote:
Wed Oct 04, 2023 6:10 pm
We have already shipped over 5,000 LOT EL2308 units, and there have been no reports of random boot instability yet. I will inquire with the hardware team about any changes.

I have a couple of questions to investigate this issue.
How many C4 boards of EL2308 LOT do you have?

200 pieces

Can you please upload the boot log that appears when booting fails with the USB-UART adapter?

ok, I will do this ASAP

Which devices do you connect to USB ports and GPIO ports?

They are acting like that without anything connected too
Thanks

flavio
Posts: 11
Joined: Fri Jun 03, 2022 2:40 pm
languages_spoken: english
ODROIDs: C2, C4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Odroid C4 - boot problem October 2023

Post by flavio »

Here's the log:

Code: Select all

SM1: BL:511f6b:81ca2f; FEAT:A0F83180:20282000; POC: F; RCY:0; EMMC: 0; READ:0;0.0; CHK:0;
b12_stage_init 0x01
b12 stage init 0x81
hw id: 0x0000 - pwm id 0x01
b12_stage_init 0xcl
b12_stage_init 0x02
LO:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180
TE: 137016
BL2 Built: 22:54:32, Apr 28 2020. g12a ga659aac-dirty
Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1 pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
Sw8 s
-
changqing.gao@droidll
DDR driver_vesion: LPDDR4 PHY_V_0_1_15 build time: Apr 28 2020 22:54:28
board id: 1
Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from eMMC, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from eMMC, src: 0x0002c200, 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
dmc version 0001
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!
RO_RXC1kDly_Margin=-94 ps 8
RO_TXDqDly_Margi==106 ps 9
R1_RxC1kDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0
dwc_ddrphy_apb_wr ((0<<20) | (2<<16) | (0<<12) | (0xb0) : 0001
soc_vref_reg_value 0x 00000050 00000051 00000050 0000004e 00000050 0000004e 0000004 0000004 0000004e 00000050 0000004e 00000050 0000004d 0000004e 0000004 0000004e 00000050 00000051 0000004 00000050 00000050 0000004 00000050 0000004
00000050 0000004e 00000052 00000051 00000051 00000051 0000004d 0000004e dram_vref_reg_value Ox 00000023
2D training succeed
aml_ddr_fw_vesion: LPDDR4 PHY_V_0_1_15 build time: Jun 18 2019 20:29:43
auto size-- 65535DDR cs0 size: 2048MB
DDR csl size: 2048MB
DMC DDR CTRL: 00700024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
X
cs1 AddrBus test pass
non-sec scramble use zero key
ddr scramble enabled
100bdlr_step_size ps== 416
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: 0x0003c200, des: 0x0172c000, size: 0x0009c000, part: 0
0.0;M3 CHK: 0; cm4_sp_mode 0
MVN_1=0x00000000
MVN 2=0x00000000
[Image: g12a_v1.1.3386-3b31431 2019-05-21 10:41:54 luan.yuan@droid15-sz]
OPS=0x10
ring efuse init
2b Oc 10 00 01 11 33 00 00 02 31 32 38 53 4e 50
[0.017354 Inits done]
secure task start!
high task start!
low task start!
run into b131
NOTICE
NOTICE: BL31: v1.3 (release) : 4fc40b1
NOTICE: BL31: Built: 15:57:33, May 22 2019
NOTICE: BL31: G12A normal boot!
NOTICE: BL31: BL33 decompress pass
ERROR:
Error initializing runtime service opteed fast
U-Boot 2015.01-dirty (Dec 13 2021 18:32:49)
DRAM: 3.5 GiB
Relocation Offset is: d6eee000
spi_post_bind (spifc): req_seq = 0
MMC: aml_priv->desc_buf = 0x00000000d3ede7c0
aml_priv->desc_buf = 0x00000000d3ee0b00
SDIO Port C: 0, SDIO Port B: 1
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
aml_sd_retry_refix [983]: delay = 0x0, gadjust =0x162000
[mmc startup] mmc refix success
[mmc_init] mmc init success
In: serial
Out: serial
Err: serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 12
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk level = 7
vpu: vpu_power_on
vpu: set vpu clk
vpu: set clk: 666667000Hz, readback: 666666667Hz (0x100)
vpu: set_vpu clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: gl2a/b osdl matrix rgb2yuv
vpp: g12a/b osd2 matrix rgb2yuv..
vpp: gl2a/b osd3 matrix rgb2yuv.
cvbs: cpuid: 0x2b
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
reading boot-logo.bmp.gz
** Unable to read file boot-logo.bmp.gz **
reading boot-logo.bmp
** Unable to read file boot-logo.bmp **
movi: not registered partition name, logo
movi - Read/write command from/to SD/MMC for ODROID board
Usage:
movi <read/write> <partition | sector> <offset> <address> [<length>]
<read write>
<offset>
the command to access the storage
the offset from the start of given partiton in lba
<address> the memory address to load/store from/to the storage device
[<length>] the size of the block to read/write in bytes
all parameters must be hexa-decimal only
[OSD] check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD] set initrd_high: 0x3d800000
[OSD] fb addr for logo: 0x3d800000
[OSD] check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD] fb addr for logo: 0x3d800000
[OSD] VPP_OFIFO_SIZE:0xfff01fff
ICANY
[CANVAS] canvas init
[CANVAS] addr=0x3d800000 width=5760, height=2160
cvbs: outputmode [1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLvl: 0xdb3a04f7
config HPLL done
j=6 vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset [1319]
rx version is 1.4 or below
Net: dwmac.ff3f0000
div=10
[OSD] check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD] fb addr for logo: 0x3d800000
[OSD] check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD] fb addr for logo: 0x3d800000
[OSD] VPP_OFIFO_SIZE:0xfff01000
card out
** Bad device mmc 1 **
card out
** Bad device mmc 1 **
reading logo.bmp.gz
** Unable to read file logo.bmp.gz **
reading logo.bmp
** Unable to read file logo.bmp **
cvbs: outputmode [1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC
config HPLL
16
5940000 frac_rate = 1
HPLL: 0x3b3a0417
HPLL: 0x1b3a04f7
HPLLvl: 0xdb3a04f7
config HPLL done
j
vid_clk_div 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset [1319]
rx version is 1.4 or below div=10
Hit Enter or space or Ctrl+C key to stop autoboot :
card out
** Bad device mmc 1 **
## Executing script at 01000000
Wrong image format for "source" command
reading boot.ini
2326 bytes read in 2 ms (1.1 MiB/s)
## Executing script at 01000000
reading config.ini
3322 bytes read in 3 ms (1.1 MiB/s)
ini: Imported display_autodetect as false
ini: Imported hdmimode as 1080p60hz
ini: Imported monitor_onoff as false
ini: Imported overscan as 100
ini: Imported sdrmode as auto
Imported voutmode as hdmi
Imported disablehpd as true
Imported cec as false
Imported disable_vu7 as true
ini: Imported maxcpus as 4
ini: Imported overlay_resize as 16384
ini: Imported overlay_profile as hifishield
ini: Imported overlays as spi0 i2c0 i2cl uart0
0
ini: Imported overlays as hifishield i2c0 i2cl uarto spio
reading Image.gz
9401429 bytes read in 260 ms (34.5 MiB/s)
reading amlogic/meson64_odroidc4.dtb
71207 bytes read in 7 ms (9.7 MiB/s)
reading uInitrd
12034942 bytes read in 334 ms (34.4 MiB/s)
reading amlogic/overlays/odroidc4/hifishield.dtbo
1355 bytes read in 6 ms (219.7 KiB/s)
card out
** Bad device mmc 1 **
## Executing script at 01000000
Wrong image format for "source" command
reading boot.ini
2326 bytes read in 2 ms (1.1 MiB/s)
## Executing script at 01000000
reading config.ini
3322 bytes read in 3 ms (1.1 MiB/s)
ini: Imported display_autodetect as false
ini: Imported hdmimode as 1080p60hz
ini: Imported monitor_onoff as false
ini: Imported overscan as 100
ini: Imported sdrmode as auto
Imported voutmode as hdmi
Imported disablehpd as true
Imported cec as false
Imported disable_vu7 as true
ini: Imported maxcpus as 4
ini: Imported overlay_resize as 16384
ini: Imported overlay_profile as hifishield
ini: Imported overlays as spi0 i2c0 i2cl uart0
ini: Imported overlays as hifishield i2c0 i2cl uarto spio
reading Image.gz
9401429 bytes read in 260 ms (34.5 MiB/s)
reading amlogic/meson64_odroidc4.dtb
71207 bytes read in 7 ms (9.7 MiB/s)
reading uInitrd
12034942 bytes read in 334 ms (34.4 MiB/s)
reading amlogic/overlays/odroidc4/hifishield.dtbo
1355 bytes read in 6 ms (219.7 KiB/s)
reading amlogic/overlays/odroidc4/i2c0.dtbo
223 byte
bytes read in 5 ms (43 KiB/s)
reading amlogic/overlays/odroidc4/i2c1.dtbo
223 bytes read in Oms (43 KiB/s)
reading amlogic/overlays/odroidc4/uarto.dtbo
225 bytes read in 6 ms (36.1 KiB/s)
reading amlogic/overlays/odroidc4/spi0.dtbo
516 bytes read in ms (100.6 KiB/s)
Uncompressed size: 25246208 0x1813A00
## Loading init Ramdisk from Legacy Image at 03700000...
Image Name:
Image Type:
Data Size:
ulnitrd
AArch64 Linux RAMDisk Image (uncompressed)
12034878 Bytes = 11.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
active_slot is <NULL>
Unknown command 'store'
No dtbo patitions found
try 'help'
load dtb from 0x1000000.
## Flattened Device Tree blob at 10000000
Booting using the fdt blob at 0x10000000
No valid dtbo image found
reserving fdt memory region: addr=10000000 size=28000
Loading Ramdisk to 3cc85000, end 3d7ff33e ... OK
Loading Device Tree to 000000001ffd5000, end 000000001fffffff ... OK
Starting kernel ...
uboot time: 3331509 us
pwr_key=ffffffff

User avatar
odroid
Site Admin
Posts: 42177
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3609 times
Been thanked: 2004 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by odroid »

Thank you for the log.
The system seemed to stop just before starting Linux kernel but I don't know why.

Hardware team also mentioned there was no component change in EL2308 against EL2301.

Can you tell me which Ubuntu OS image you have used?
https://wiki.odroid.com/odroid-c4/os_images/ubuntu
We will try reproducing the issue with the same OS image.

flavio
Posts: 11
Joined: Fri Jun 03, 2022 2:40 pm
languages_spoken: english
ODROIDs: C2, C4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Odroid C4 - boot problem October 2023

Post by flavio »

Ubuntu Minimal 20.04.3 LTS

User avatar
neal
Posts: 369
Joined: Fri Apr 14, 2017 10:02 am
languages_spoken: Korean, English
Has thanked: 31 times
Been thanked: 47 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by neal »

Hi @flavio,

I checked your log and there is something I wonder about.

Code: Select all

.
.
Error initializing runtime service opteed fast
U-Boot 2015.01-dirty (Dec 13 2021 18:32:49)
DRAM: 3.5 GiB
.
.
Is the U-boot code customized to you?

flavio
Posts: 11
Joined: Fri Jun 03, 2022 2:40 pm
languages_spoken: english
ODROIDs: C2, C4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Odroid C4 - boot problem October 2023

Post by flavio »

Thanks for replying...

<<<Is the U-boot code customized to you?

does it really matter? As I wrote in my first message, if I use a board from another batch (for example 2301) with exactly the same eMMC, it ALWAYS work.
We use this image since years.

Thanks!

User avatar
neal
Posts: 369
Joined: Fri Apr 14, 2017 10:02 am
languages_spoken: Korean, English
Has thanked: 31 times
Been thanked: 47 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by neal »

Yes, I understand what you mean, but could please try Ubuntu Minimal 20.04.3 LTS pure image or a different version pure image Is also okay, and then let me know?
We are also trying to reproduce this issue. but until now that has not happened yet.

PeteSpectur
Posts: 1
Joined: Tue Jan 30, 2024 3:38 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 0
Contact:

Re: Odroid C4 - boot problem October 2023

Post by PeteSpectur »

Hi Neal and Flavio. Did you guys end up getting to the bottom of this? We are also seeing issues with our first batch of EL2308 boards. We run Android and power the C4 through the GPIO pins. No changes on our side and the same system runs fine on older batches like EL2210. Thanks! Pete.

User avatar
neal
Posts: 369
Joined: Fri Apr 14, 2017 10:02 am
languages_spoken: Korean, English
Has thanked: 31 times
Been thanked: 47 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by neal »

PeteSpectur wrote:
Tue Jan 30, 2024 3:57 pm
Hi Neal and Flavio. Did you guys end up getting to the bottom of this? We are also seeing issues with our first batch of EL2308 boards. We run Android and power the C4 through the GPIO pins. No changes on our side and the same system runs fine on older batches like EL2210. Thanks! Pete.
The Lot EL2308 has been replaced DC-DC converter. Please check C4 PCB revision history https://wiki.odroid.com/odroid-c4/hardw ... on_history
That seems to affect the timing of the first boot stage in u-boot. We have checked the official images are booting without issue. but, any changes in u-boot code customized for their own seem to have booting issues like above @Flavio.

User avatar
neal
Posts: 369
Joined: Fri Apr 14, 2017 10:02 am
languages_spoken: Korean, English
Has thanked: 31 times
Been thanked: 47 times
Contact:

Re: Odroid C4 - boot problem October 2023

Post by neal »

Updated C4 PCB revision history here https://wiki.odroid.com/odroid-c4/hardw ... on_history
The FC6800 component shortage is not anymore so far. Lot number EL2401 and later products have been expecting the above issue not be exist.

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 1 guest