06-01-2020 07:45 AM
Whenever I save a petalinux kernel configuration, exit, build, etc. and re-configure it, it seems to start from the default config, not the last one applied and saved. Is this what petalinux is intended to do?
It makes me doubt about what config it used for build
06-02-2020 06:06 AM
It should save them - when you do kernel config via PetaLinux it generates individual config fragments that all get applied to build an exhaustive .config file. If you are worried about what the end .config looks like, you can check the kernel-artifacts within your build path (you might need to do this after a PetaLinux kernel build as I'm not sure when it applies the config to the file in this directory you'll have to try yourself). Sometimes the fragment list looks kind of silly, as it generates one each time you save a new config, so you could have fragments that enable a feature, disable it and then enable it, and in the end it will be enabled but it is because it makes a fragment every time you run and save the config.
# You can see the generated fragments somewhere in your project like: project-spec/meta-user/recipes-kernel/linux/linux-xlnx
# and the .config path is usually something like build/tmp/work-shared/zcu102-zynqmp/kernel-build-artifacts/.config