VIM4/3/3L/1S/Edge2 Yocto SDK first release

Hello Folks,

Here we release the first version of Yocto SDK for VIM4/3/3L/1S/ with 5.15 kernel and Edge2 with 6.1 kernel, you can follow the documentation to download the SDK and build Yocto images.

Testing images are also available:

You need to Install the Yocto image into eMMC via USB Flash Tool, please check:

Any feedback are welcome~

NOTE: For VIM series Yocto image doesn’t have the desktop, you will see a black screen on HDMI display, so you need to ssh (ssh root@xx.xx.xx.xx) to it or use the serial debug console to access the terminal, execute weston-terminal on serial debug console to check the weston terminal.

Cheers.

4 Likes

Sounds great! However, the prebuilt image seems not working on my VIM3L device:

$ burn-tool -v aml -b VIM3 -i yocto.img 
Try to burn Amlogic image...
Burning image 'yocto.img' for 'VIM3/VIM3L' to eMMC...
Unpacking image [OK]
Initializing ddr ........[OK]
Running u-boot [KO]

Could you please check it again?

After resetting VIM3L device and retried, the flash seems working:

$ burn-tool -v aml -b VIM3 -i yocto.img 
Try to burn Amlogic image...
Burning image 'yocto.img' for 'VIM3/VIM3L' to eMMC...
Unpacking image [OK]
Initializing ddr ........[OK]
Running u-boot ........[OK]
Create partitions [OK]
Writing device tree [OK]
Writing bootloader [OK]
Wiping  data partition [OK]
Wiping  cache partition [OK]
Writing boot partition [OK]
Writing logo partition [OK]
Writing recovery partition [OK]
Writing system partition [OK]
Writing vendor partition [OK]
Do you want to reset the board? y/n [n]? y
Resetting board [OK]
Time elapsed: 3 minute(s).
Done!
Sat Jan  4 06:15:48 PM CST 2025

You can add weston compositor and launch a weston terminal to your meta-layer. That is all we use, no need for a desktop. You can also add a Khadas branded background. It will also have an icon on the upper left for a shell terminal. So when it starts it will look good and you can still run stuff like firefox from weston. The .ini will have settings for the default terminal that has non-blank screen.

Yes, weston is supported, and you can launch weston terminal with weston-terminal.

2 Likes

In the documentation VIM3/3L. I noticed that we should setup the compile configuration before compilation. I set up bitbake build environment by

source poky/oe-init-build-env

Then I modfied the machine mesong12b-kvim3-k5.15 in local.conf and added layers in bblayers.conf. It seems that I have some errors.

meta-meson/recipes-kernel/realtek/rtk8852be_1.0.bb: EXTERNALSRC must be an absolute path | ETA: --:–:–
meta-meson/recipes-core/aml-hdcp/aml-hdcp_git.bb: EXTERNALSRC must be an absolute path
meta-meson/recipes-drm/aml-mediadrm/aml-youtubesign-bin_git.bb: EXTERNALSRC must be an absolute path
ERROR: ExpansionError during parsing /home/viziosense/VizioSense/projects/vims-yocto-sdk/sources/meta-meson/recipes-kernel/realtek/rtk8852be_1.0.bb

May I miss some steps in set up. Can we have local.conf and bblayers.conf of the example image?

In addition, I think I should do git pull in .repo/repo/ before .repo/repo/repo sync -c command, otherwise I will have an error.

Hi @numbqq, the Yocto image (vim3) can be built successfully. I should set up a python 2 environment and use the script from meta-meson to initialize instead of poky.

source meta-meson/oe-init-build-env-meson

However, I have errors when add some gstreamer packages

ERROR: recovery-image-1.0-r0 do_image_cpio: The initramfs size 173835(K) exceeds INITRAMFS_MAXSIZE: 131072(K)
ERROR: recovery-image-1.0-r0 do_image_cpio: You can set INITRAMFS_MAXSIZE a larger value. Usually, it should
ERROR: recovery-image-1.0-r0 do_image_cpio: be less than 1/2 of ram size, or you may fail to boot it.

If I set up a larger INITRAMFS_MAXSIZE in local.conf. The image can be built but I have a uboot partition error when flash. Any idea on this?

Additionally, is the hardware decoder v4l2h264dec supported in this yocto, as it uses the same 5.15 kernel?

Could you provide the serial console logs?

Yes, but yocot will use amlv4l2h264dec by default.

gst-inspect-1.0 | grep aml to get all plugins from Amlogic.

@numbqq Here are the screenshots showing the errors.
USB Burn Tool:


Console:

Hello @JJ1997

@Naruto-China will help you later.


As shown in the image above, locate the partition_normal_linux.dtsi file and change the size of the recovery partition to 0x3C00000. This should resolve your issue.