The peripheral circuits of Core1106 are not fixed, so no default mirroring is provided. Modifications can be made based on the configuration of Luckfox Pico Pi.
The upload tool still uses SocToolkit.

Ok, I’m encountering an issue while uploading the image. Every time I try to upload it, it always fails at this point.

"Error:Write LBA failed,can't read flash id from device!"
Download env...Fail
I tried with different boards and different USB cables. The connection is direct, without a hub.

Thank you in advance for your support.

Best regards,

Have any of the other RV1106 models been successfully upgraded through burning?
A damaged driver could also be the cause of this issue. You can try reinstalling the driver.

Hi,

Just to update you: I managed to flash everything correctly. Most likely, the issue was the driver, which I uninstalled and reinstalled.

I am using the files that make up the Pico Pi W image as a starting point. Of course, I am modifying the DTSI files to make them compatible with my carrier board.

Do you have any suggestions regarding this approach?

Best regards

I still need your help.

I created a corrupted image, and now U-Boot will not start. This is the log.
"
\ | /
- RT - Thread Operating System
/ | \ 3.1.3 build Jun 22 2022
2006 - 2019 Copyright by rt-thread team

Hello, RV1106 MCU

[STREAM]: the device to be found:isp_0, object_id:0
[STREAM]: find the device:isp_0
[isp_0]:Err: buf head[1e03000] heap->end_addr 23fffff
[isp_0]:Err: buf head[1e74000] heap->end_addr 23fffff
[isp_0]:Err: buf head[1ee5000] heap->end_addr 23fffff
[isp_0]:Err: buf head[1f56000] heap->end_addr 23fffff
[isp_0]:Err: buf head[1fc7000] heap->end_addr 23fffff
fastae: 2.1.6
[FASTAE]: lux sensor is enable
[FASTAE]: probe rk_adc0
[FASTAE]: read_lux_adc over tick:46, 419-417
env_lux: 87
[AELIB]:times=0,luma=0x0,cur_exp=0x0,time=0x20c,gain=0x2603e,time_reg=0x21b,gain_reg=0x30
sc230ai on enter tick:57
U-Boot SPL board init
U-Boot SPL 2017.09 (Mar 26 2026 -i2c write continue success
sc230ai on exit tick:71
11:40:52)
Trying to boot from MMC1
MMC error: The cmd index is 7, ret is -110
mmc_init: -22, time 18
MMC error: The cmd index is 7, ret is -110
Best phase range 0-270 (25 len)
Successfully tuned phase to 135, used 4ms
ENVF: Primary 0x00000000 - 0x00008000
ENVF: Primary 0x00000000 - 0x00008000
## Verified-boot: 0

## Checking mcu1 0xff6fe000 ... sha256(7c6c18c711...) + OK

fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
FIT image with Li[isp_0]:Err: take dqbuf sem failed!
[STREAM]: dqueue buf fail,stop streaming!
[STREAM]: stop_stream start, tick 173
stop_ae on enter tick:175
[FASTAE]: exp thread exit
[FASTAE]: stats tick:181 seq:0 type:0x0, ae:0x0 0x0 0x0 awb:0x0 0x0 0x0
[FASTAE]: calcwbgain: 0x100 0x100 0x100 0x100
[FASTAE]: stat thread exit
[isp_0]:Warning: there is still buf enqueued in driver!
[STREAM]: stop_stream end, complete:2 tick 199
nux kernel, FDT blob and resource
fit_find_ci2c write continue success
onfig_node: Missing FDT description in DTB
No matching DT out of these options:
FIT image with Linux kernel, FDT blob and resource
fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
FIT image with Linux kernel, FDT blob and resource
Trying ramdisk fit image at 0x190640 sector
DDR 306b9977f5 wesley.yao 23/12/21-09:28:37,fwver: v1.15
S5P1
4x
f967
F
DDRConf2
DDR3, BW=16 Col=10 Bk=8 CS0 Row=14 CS=1 Size=256MB
924MHz
DDR bin out
"

I searched a bit on the forum, and it seems that the suggested solution is to short GND and eMMC CLK.

I tried shorting pin 46 and pin 47 on the module, but without success. Are these the correct pins to short, or should I short different ones instead?

Thank you in advance for your help.