F2FS Support on Connect Core iMX6UL (ccimx6ulstarter)

I added f2fs-tools into my conf.local file in my project directory. I also modified the ‘image_types.bbclass’ with the following patch: https://patchwork.openembedded.org/patch/147392/

Yet, after building my image, whilst I can now utilize mkfs.f2fs and format my SD card with F2FS, I can’t seem to mount it at all and my image does not recognized the f2fs formatted SD card. I can see it in /dev/ as “/dev/mmcblk1p1” but it won’t mount. Trying to mount it I get the following:

root@ccimx6ulstarter:~# mount -t f2fs /dev/mmcblk1p1 /run/media/mmcblk1p1/
mount: mounting /dev/mmcblk1p1 on /run/media/mmcblk1p1/ failed: No such device

What am I missing. Does DEY 2.4 not support F2FS? Not sure why it wouldn’t be natively supported, as f2fs is pretty prominent and useful for SSDs/eMMC/SD cards especially.

FS2S support is most likely not enabled in kernel.
https://wiki.gentoo.org/wiki/F2FS

>Not sure why it wouldn’t be natively supported, as f2fs is pretty prominent and useful for SSDs/eMMC/SD cards especially

This is embedded system with limited resources so only minimal necessary set is enabled by default

1 Like

I understand its an embedded system, but EXT4 is natively supported and its one of the much less efficient filesystems for flash.

How would I go about enabling support/enabling it in the kernel using the Yocto build system besides what I attempted in the above?

To make sure it works follow this portion of the guide:
https://www.digi.com/resources/documentation/digidocs/90002286/#task/yocto/t_make_devshell_changes.htm

source dey-setup-environment
bitbake -c devshell virtual/kernel
bitbake -c menuconfig virtual/kernel
bitbake -C compile virtual/kernel

For permanent project changes you can use one of the ways here:
https://www.digi.com/resources/documentation/digidocs/90002286/#task/yocto/t_build_custom_kernel_recipe.htm

Thanks, I will try this over the next day or so and see if I get the results I’m looking for. Appreciate the fast feedback!

I forgot to check back in – but this did indeed work. The various file systems were not enabled in the kernel. Thanks for the help!