About STM32CubeMX and IAR Embedded Workbench for ARM versions

TTaka.19 · ‎2021-12-24

I am developing using STM32CubeMX and IAR Embedded Workbench for ARM (EWARM).

I was using version 8.50.9 of EWARM.

I have upgraded to the latest EWARM v9.20.2.

Then the firmware that was working with EWARM v8.50.9 stopped working.

I also tried EWARM v9.20.1 and v9.10.2 but it didn't work.

Is it necessary to use EWARM v8.xx.x for the source code output by STM32CubeMX?

TDK · ‎2021-12-24

"worked" and "stopped working" is an insufficient description of what's happening. What didn't work? Do you see error messages? Does it build? What results were you expecting and what happened instead?

If you feel a post has answered your question, please click "Accept as Solution".

TTaka.19 · ‎2021-12-26

In the latest STM32CubeMX (6.4.0), EWARM Toolchain can only be selected up to V8.32.

So I think the output source code will not work with EWARM v9.xx.x.

Has anyone ever created firmware with STM32CubeMX (6.4.0) and EWARM v9.xx.x?

Remy ISSALYS · ‎2022-03-24

Hello,

IAR Embedded Workbench is backwards compatible with previous IAR Embedded Workbench versions. So, if your code was working with v8.50.9, there is no problem to use higher version of IAR like v9.20.1. What's happening when your firmware "stopped working" ?

Best Regards

TSosi.1 · ‎2022-03-24

We upgraded from 8.40.3 to 9.20.3. The product software didn't compile initially, but that was an easy name mangling fix. After that change, the software runs fine.

TTaka.19 · ‎2022-03-24

Thank you for your answer.

After that, I investigated this issue and found that the source code I was overriding the IAR library was incorrect. I fixed the source code and the problem was solved.

Thank you very much.