Thanks for your response.
Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.
Hello Uday,
The error setenv: command not found usually happens when the setenv command is run in the Linux shell rather than in the U-Boot bootloader environment.
Here are the correct ways to update the fdtfile variable:
- Using fw_setenv from Linux
If you are already in Linux, use the fw_setenv command:
fw_setenv fdtfile myname-custom-board.dtb
This updates the U-Boot environment variable from within Linux.
Make sure the /etc/fw_env.config file is correctly set up for your hardware. More info here:
- Using setenv in U-Boot
If you want to use setenv, you need to interrupt the boot process and access the U-Boot console:
- Power cycle your board and connect a serial console.
- When prompted, press any key to stop boot at the U-Boot prompt.
- At the prompt (usually something like =>), use:
setenv fdtfile myname-custom-board.dtb
saveenv
Reference:
You can now reboot (reset) the system, and U-Boot should use your custom fdtfile.
- Verifying the Change
From Linux:
fw_printenv fdtfile
Or from U-Boot:
printenv fdtfile
Summary:
- Use fw_setenv from Linux.
- Use setenv from the U-Boot prompt, not from Linux.
Let me know if you need guidance on configuring /etc/fw_env.config or have any follow-up questions.
Best regards,
Toradex AI Assistant.
Reference URLs: