Hello, it is recommended that you use the USB to serial port tool to obtain the boot log for analysis, the LED is flashing with the kernel activity, and stopping the flashing indicates that the kernel may fail to boot

Crocodile wrote: ↑2025-03-27 1:33 Hello, it is recommended that you use the USB to serial port tool to obtain the boot log for analysis, the LED is flashing with the kernel activity, and stopping the flashing indicates that the kernel may fail to boot

thanks for your replay,the uart ouput is below:
```bash
FIT: no signed, no conf required
DTB: rk-kernel.dtb
HASH(c): OK
Model: Luckfox Pico Mini
## retrieving sd_update.txt ...
MMC: no card present
mmc_init: -123, time 2
CLK: (uboot. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
apll 816000 KHz
dpll 528000 KHz
gpll 1188000 KHz
cpll 1000000 KHz
aclk_peri_root 400000 KHz
hclK_peri_root 200000 KHz
pclk_peri_root 100000 KHz
aclk_bus_root 300000 KHz
pclk_top_root 100000 KHz
pclk_pmu_root 100000 KHz
hclk_pmu_root 200000 KHz
Net: eth0: ethernet@ffa80000
Hit key to stop autoboot('CTRL+C'): 0
## Booting FIT Image at 0x2927f40 with size 0x002d1800
Fdt Ramdisk skip relocation
No misc partition
## Loading kernel from FIT Image at 02927f40 ...
Using 'conf' configuration
## Verified-boot: 0
Trying 'kernel' kernel subimage
Description: unavailable
Type: Kernel Image
Compression: uncompressed
Data Start: 0x02931540
Data Size: 2916712 Bytes = 2.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: sha256
Hash value: 24b339fee0ac6d0a5108836d3c906a34a459a2f1fa30521aae4103c49c3148a6
Verifying Hash Integrity ... sha256+ OK
## Loading kernel from FIT Image at 02927f40 ... 15:07:08 [1645/1913]
Using 'conf' configuration
## Verified-boot: 0
Trying 'kernel' kernel subimage
Description: unavailable
Type: Kernel Image
Compression: uncompressed
Data Start: 0x02931540
Data Size: 2916712 Bytes = 2.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: sha256
Hash value: 24b339fee0ac6d0a5108836d3c906a34a459a2f1fa30521aae4103c49c3148a6
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 02927f40 ...
Using 'conf' configuration
Trying 'fdt' fdt subimage
Description: unavailable
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x02928740
Data Size: 36058 Bytes = 35.2 KiB
Architecture: ARM
Load Address: 0x00c00000
Hash algo: sha256
Hash value: ec878326be328d02cf921dd47e26715622d000bcf412e78c8a936ec0f5bb3285
Verifying Hash Integrity ... sha256+ OK
Loading fdt from 0x02927f40 to 0x00c00000
Booting using the fdt blob at 0x00c00000
Loading Kernel Image from 0x02931540 to 0x00008000 ... OK
kernel loaded at 0x00008000, end = 0x002d0168
Using Device Tree in place at 00c00000, end 00c0bcd9
Adding bank: 0x00000000 - 0x04000000 (size: 0x04000000)
Total: 634.247/846.763 ms

Starting kernel ...
```
and i have report this issue on github https://github.com/LuckfoxTECH/luckfox-pico/issues/256

Hello,Please choose either the forum or GitHub Issues to report your problem. Submitting feedback through multiple channels may lead to duplicate responses and increase our workload. Thank you for your understanding.

Your kernel doesn't seem to boot successfully, it may be that the image is not burned correctly, I tried your configuration, if you dynamically load the .ko driver provided by rockchip at startup, it will report an error, you can first move /oem/usr/insmod_ko.sh to other directories to let the loading of .ko not run automatically, so that the kernel can load normally