I am currently using Yocto (v3.0.4) to build an image for RK3328-based custom board, and I have generated a GPT image (gpt.img) that is 6.2 GB in size. However, when I try to flash this image using RK Burning Tool (v1.72.9), the tool does not recognize it while other Android and Linux (.img) images get recognized.
I am using this YOCTO setup (ZEUS) for Rock PI E and building radxa-desktop-image.
Any idea what might be the problem over here?? Any help or suggestion is appreciated.
What version of ROCK-PI-E do you have?
Are you trying to flush the generated gpt.img into the EMMC of the PI-E?
Have you ever flashed an image to emmc before?
Yes, we have flashed emmc using upgrade_tool utility. But seems not reliable as it requires flashing two times
You can try using this version of the burn-in tool:
RKDevTool_Release_v2.86.zip (2.5 MB)
Use this loader file:
rk3328_loader_ddr333_v1.16.250.bin.zip (177.9 KB)
(Both files need to be unzipped)
I tried using the RKDevTool v2.86 along with the rk3328_loader_ddr333_v1.16.250.bin loader file, but unfortunately, I encountered the same issue: “Download image failed”, please find below screenshot.
Why does the picture show version 2.96?
You can burn the image to SD card first, then when the system is up, use the dd command to empty the emmc:
dd if=/dev/zero of=/dev/mmcblk0 bs=4M count=100
you can flash this image to SD card:
https://github.com/radxa-build/rock-pi-e/releases/download/b22/rock-pi-e_debian_bookworm_cli_b22.img.xz
Thanks for you early response.
I want to flash the image directly to the eMMC without using an SD card.
I apologise for the earlier mistake regarding tools version. Now I have used RKDevTool v2.86. I am able to flash the image successfully but requires to flash the image twice using tool.
On first attempt of flashing only the U-Boot loads, and doesn’t starts the kernel, below logs are attached for you reference.
first_attempt.zip (1.7 KB)
However, when I flash the same image again, the board boots correctly.
second_attempt.zip (12.3 KB)
Could you please provide any insights on why I need to flash the image twice to work properly?
