according to the BSP42.0 User Manual, added pfe-slave support to conf/local.conf
NXP_FIRMWARE_LOCAL_DIR = "/path/to/s32g2/bsp/yocto/firmware"
DISTRO_FEATURES:append = " pfe"
DISTRO_FEATURES:append = " pfe-slave"
then
$ bitbake fsl-image-auto
report error:
ERROR: Nothing RPROVIDES 'pfe-slave' (but /path/to/s32g2/bsp/yocto/fsl-auto-yocto-bsp-42.0/sources/meta-alb/meta-alb-bsp/recipes-extended/libfci-cli/libfci-cli_1.0.0.bb RDEPENDS on or otherwise requires it)
pfe-slave was skipped: incompatible with machine s32g274ardb2 (not in COMPATIBLE_MACHINE)
NOTE: Runtime target 'pfe-slave' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pfe-slave']
NOTE: Runtime target 'libfci-cli' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libfci-cli', 'pfe-slave']
ERROR: Required build target 'fsl-image-auto' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-auto', 'libfci-cli', 'pfe-slave']
I checked the bb file, actually it only support s32g399ardb3:
$ cat sources/meta-alb/meta-alb-bsp/recipes-kernel/pfe/pfe-slave_1.0.0.bb
COMPATIBLE_MACHINE = "(s32g399ardb3)"
I modified the bb file, add s32g399ardb2 support:
COMPATIBLE_MACHINE = "(s32g274ardb2|s32g399ardb3)"
run the new BSP image, but still can not get the network interface, just like pfe*sl.
Hello, @liujialu_2024
Sorry for your waiting.
I have tested on my end, and reproduced your issue met.
But it is not a bug of Yocto, currently, the pfe-slave on S32G2 has some problems in BSP, so that it is not enabled on the Yocto build.
We have tracked this issue, and it may be fixed in the next release or later.
Sorry for your inconvenience.
BR
Chenyin
Hello, @liujialu_2024
Thanks for your post.
I will tested on my end, once it is produced, I will look into it for the root casue.
BR
Chenyin