Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
The error message ‘Configuration file wrong or corrupted’ when executing the fw_setenv command suggests there might be an issue with the U-Boot environment on your Verdin iMX8MP module. Here are some steps to help you troubleshoot and resolve this issue:
Check U-Boot Environment:
Boot into U-Boot and use the printenv command to list all environment variables. This can help identify if the environment is corrupted or if there are any unexpected entries.
Verify Command Syntax:
Ensure that the command syntax is correct. The command should be:
fw_setenv tdxargs "clk-imx8mp.mcore_booted=1"
Double-check for any typographical errors or incorrect quotation marks.
Environment Corruption:
If the environment is corrupted, you may need to reset it to default values. This can be done by using the env default -a command in U-Boot, followed by saveenv to save the changes.
Backup and Restore:
If you have a backup of the U-Boot environment, consider restoring it to see if the issue persists.
By following these steps, you should be able to identify and resolve the issue with the U-Boot environment configuration. If the problem persists, further investigation into the specific environment setup on your module may be necessary.
Best regards,
Toradex AI Assistant.
Please, also check if these links can help you solve your problem:
Using the ${tdxargs} is just a way of making sure that you are not losing what you previously had in the tdxargs (if any). Just in case
The problem here is that this command doesn’t open the /sys/module/firmware_class/parameters/path as a super user. Here only the echo is the executed as super user.
To overcome this, you need to do something like this:
echo -n new_path | sudo tee /sys/module/firmware_class/parameters/path
As the command tee is the one that will open and write to the file, and it is executed as super user, this should solve your issue.
That worked. I found another option, which is to call sudo su first.
This command still doesn’t work:
torizon@verdin-imx8mp-15139674:~$ echo start | sudo tee /sys/class/remoteproc/remoteproc0/state
start
tee: /sys/class/remoteproc/remoteproc0/state: No such file or directory