Can't access shell on UART0 with SDCARD image (Luckfox-rk3576-buildroot_250301.img)

2025-04-20 4:13

Hi,

I'm trying to access the shell via UART0.

I flashed Luckfox-rk3576-buildroot_250301.img to a 32GB SDCARD
Inserted it into the board and powered it on
On the UART0 console, I can see U-Boot logs, but after that, nothing happens — I don’t see any shell login prompt.
What could be the problem?
My goal is simply to access a login shell over UART.

Any help is appreciated.
Thanks!

: 1

: 2

: 3

[Log]

DDR 81dd75088a wesley.yao 24/04/16-11:19:41,fwver: v1.03
In
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
Manufacturer ID:0xff
CH0 RX Vref:24.9%, RX DQS Vref:32.5%, TX Vref:20.8%,20.8%
DQ roc:
p1 n0, p4 n0, p4 n0, p0 n0, p2 n0, p1 n0, p0 n3, p0 n2, p2 n0,
p1 n0, p7 n0, p0 n1, p7 n1, p0 n0, p1 n0, p0 n0, p1 n0, p2 n0,
DQ rds:
h0 l0, h1 l0, h0 l0, h0 l0, h1 l0, h0 l0, h0 l0, h0 l0,
h0 l0, h0 l0, h0 l0, h0 l0, h0 l0, h0 l0, h0 l0, h0 l0,
DQS roc: p0 n0, p0, n0

CH1 RX Vref:24.9%, RX DQS Vref:30.0%, TX Vref:22.8%,22.8%
DQ roc:
p4 n0, p1 n0, p0 n0, p5 n0, p3 n0, p7 n0, p7 n0, p2 n0, p7 n0,
p5 n0, p7 n0, p3 n0, p3 n0, p4 n0, p5 n0, p7 n0, p7 n0, p4 n0,
DQ rds:
h2 l0, h0 l0, h0 l0, h0 l0, h0 l0, h1 l0, h0 l0, h0 l0,
h0 l0, h1 l0, h1 l0, h0 l0, h0 l0, h0 l0, h0 l0, h1 l0,
DQS roc: p2 n0, p1, n0

stride=0x3, ddr_config=0x4
hash bank_mask0-3 0x0 0x880 0x1100 0x2200, rank_mask0 0x400400
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 (Apr 20 2025 - 11:15:40)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
SPL: A/B-slot: _a, successful: 0, tries-remain: 7
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x40040000 ... sha256(29d0db0f11...) + OK
## Checking uboot 0x40200000 ... sha256(b6c58202b0...) + OK
## Checking fdt 0x40341120 ... sha256(673916e062...) + OK
## Checking atf-2 0x400f0000 ... sha256(99ef39a641...) + OK
## Checking atf-3 0x3fe70000 ... sha256(e6de1355c6...) + OK
## Checking optee 0x48400000 ... sha256(988a2a2a76...) + OK
Jumping to U-Boot(0x40200000) via ARM Trusted Firmware(0x40040000)
Total: 592.242/757.776 ms

INFO: Preloader serial: 0
NOTICE: BL31: v2.3():v2.3-802-g286c013b2:derrick.huang, fwver: v1.09
NOTICE: BL31: Built : 18:03:51, Jun 28 2024
INFO: ext 32k is not detected
INFO: cost 772328 us before hptimer restart
INFO: soc warm boot, reset status: 0x0
INFO: ARM GICv2 driver initialized
INFO: bypass memory repair
INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
I/TC:
I/TC: OP-TEE version: 3.13.0-795-gb90c1680e #hisping.lin (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Mon May 13 14:42:41 CST 2024 aarch64, fwver: v1.02
I/TC: OP-TEE memory: TEEOS 0x200000 TA 0xc00000 SHM 0x200000
I/TC: Primary CPU initializing
I/TC: Primary CPU switching to normal world boot
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x40200000
INFO: SPSR = 0x3c9

U-Boot 2017.09-g6160967 #root (Apr 20 2025 - 08:01:41 +0900)

Model: Rockchip RK3576 Evaluation board
MPIDR: 0x0
PreSerial: 0, raw, 0x2ad40000
DRAM: 4 GiB
Sysmem: init
Relocation Offset: bda1c000
Relocation fdt: fb9f9e10 - fb9fecf0
CR: M/C/I
Using default environment

optee api revision: 2.0
no mmc device at slot 1
mmc@2a310000: 1 (SD), mmc@2a330000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 52Mhz
PartType: EFI
TEEC: Waring: Could not find security partition
DM: v2
boot mode: None
RESC: 'boot', blk@0x0001bae1
resource: sha256+
FIT: no signed, no conf required
DTB: rk-kernel.dtb
HASH(ce): OK
dw_dp_bind zyb enter
I2c1 speed: 100000Hz
PMIC: RK8060 (on=0x40, off=0x00)
vdd_cpu_big_s0 init 850000 uV
vdd_npu_s0 750000 uV
vdd_cpu_lit_s0 init 850000 uV
vdd_gpu_s0 init 750000 uV
vdd_logic_s0 init 750000 uV
vdd_ddr_s0 850000 uV
I2c5 speed: 100000Hz
drivers/video/waveshare_backlight.c: backlight_i2c_write: waveshare i2c write failed: -110
drivers/video/waveshare_backlight.c: backlight_i2c_write: waveshare i2c write failed: -110
Could not find baseparameter partition
Model: Luckfox Omni3576
Rockchip UBOOT DRM driver version: v1.0.1
Assign plane mask automatically
VOP have 3 active VP
vp0 have layer nr:1[2 ], primary plane: 2
vp1 have layer nr:1[3 ], primary plane: 3
vp2 have layer nr:1[8 ], primary plane: 8
Using display timing dts
dsi@27d80000: detailed mode clock 70000 kHz, flags[a]
H: 0800 0840 0860 0880
V: 1280 1300 1304 1324
bus_format: 100e
VOP update mode to: 800x1280p60, type: MIPI0 for VP1
VP1 set crtc_clock to 69883KHz
Unsupported bt709f at 10bit csc depth, use bt601f instead
VOP VP1 enable Esmart1[654x270->654x270@73x505] fmt[0] addr[0xfdf00000]
final DSI-Link bandwidth: 465886 Kbps x 4

2025-04-21 11:09

Your startup log shows that you haven't even entered the kernel. First, re-plug the core board to rule out the problem of poor contact. Second, try burning and testing with several different TF cards to rule out the compatibility issues of the TF cards.

2025-04-21 22:51

I baked the same image file on Samsung 128evo, sandisk ultra 32GB, but the symptoms were the same.

2025-04-23 10:40

I have also tested with a SanDisk Ultra 256GB card and it was able to boot successfully. So, you should check if the image was not burned successfully. First, format the card and then try burning the image again. Or you can try our Debian 12 image and see if it can boot up normally.

2025-04-23 11:29

I connected the same SD card to a different Omni3576 board, and it booted successfully. What could be the possible cause in this case? Based on the boot logs, it seems to hang while initializing the display output. Could this be related to a display or hardware issue? For example, could it be a problem with the DSI interface, or might it be related to other display outputs like HDMI, BT1120, MIPI, or LVDS?

2025-04-23 12:50

If you have multiple sets of development boards, you can swap the installation of the core boards. Even if the HDMI resolution is incompatible, the system can still enter the kernel and print relevant information. If you suspect that the DSI is causing the problem, unplug all the peripherals and see if the board can boot up normally. If it can boot up after unplugging the peripherals (the act light blinking indicates successful boot), but fails to boot when the DSI screen is connected, there might be a short - circuit in the DSI. Please provide more information, such as what peripherals are connected?

2025-05-03 6:26

Before finalizing my custom board, I soldered the Techpoint BT2855 and proceeded with testing. In the device tree, after disabling all non-essential nodes except critical components such as the CPU, I confirmed that the board operates correctly. It seems I may have damaged the board… Thank you for your response. Also, may I ask questions regarding BT2855-related solutions?