Hi Daniel,
Thank you for your quick response. I believed I had to run the SOF firmware using remoteproc, and a week ago I understood it had to be run via the SOF driver. No more issues for me regarding this topic. Do you give the possibilities to use, for instance, uart4, in order to have some kind of printf feature as it is the case using "DSP Framework"?
Wishing you an excellent week-end.
Regards, David Sayada.
On Wed, Apr 5, 2023 at 5:45 PM Daniel Baluta daniel.baluta@nxp.com wrote:
Hi David,
Can you provide us more information about your use case?
At NXP we have different scenarios for using DSP:
- via remoteproc, for that you will need a special firmware (not SOF)
- via SOF driver, for that you will need the SOF firmware
Let us know what is your scenario and what are you trying to do so that we can provide further help.
For starting with SOF there is this quick start guide here:
https://thesofproject.github.io/latest/getting_started/nxp/sof_imx_user_guid...
thanks, Daniel.
*From:* David Sayada dsayada.upwork@gmail.com *Sent:* Sunday, April 2, 2023 11:32 AM *To:* sound-open-firmware@alsa-project.org < sound-open-firmware@alsa-project.org> *Cc:* Kodel Oleg oleg.kodel@elbitsystems.com *Subject:* Bad magic error when loading SOF firmware
Hello SOF team,
We are trying to evaluate the SOF project on our 8MPLUSSLPD4-EVK based product, and we are getting some issues when trying to run one of the "yocto compiled" SOF Firmware.
Below is the procedure we are trying to perform:
*echo /lib/firmware/imx/sof/sof-imx8m.ri > /sys/class/remoteproc/remoteproc0/firmware* *echo start > /sys/class/remoteproc/remoteproc0/state*
We are getting, at the end, a "Image is corrupted (bad magic)" -22 return code.
We have also created a VM (based on SOF 2.4.1) where we can compile (and sign, with default keys) the different toolchains and firmwares. Will that help in having a firmware run correctly?
Maybe, we are doing incorrect things, if this is the case, please advise.
Best regards, David Sayada.