The importconfig was the missing piece, and now it worked. Thanks a lot for your help.
uEnv.txt is not created by image-script as it is initially empty (using my u-boot builtin environment). uEnv.txt allows to override this but it has to be created.
Ah, ok, so, I can create one and override settings, thanks.
How do we list the u-boot builtin environment from Linux? Would you be able to give an example of what to put in uEnv.txt in order to insert some customer linux boot link parameters? For example, i wish to experiment with the “clk_ignore_unused” kernel parameter.
in uboot itself you can use printenv, in linux there is a tool named fw_printenv, but i have tried it yet. else you can cat /boot/uEnv.txt if there is any (your own content), else builtin environment is created by the uEnv_*.txt in my uboot-repo
for r3 and the bootargs you can extend bootopts
which is added to bootargs by buildargs
so try to add this to your /boot/uEnv.txt
bootopts=$bootopts clk_ignore_unused=1