cancel
Showing results for 
Search instead for 
Did you mean: 

STM Nucleo-WBA52CG compile using IAR 7.40.1

MLiska
Associate II

Hello, i need to compile example project using IAR ver. 7.40.1, (common components ver. 7.2.0), and I'm dealing with this error ".ewp was created by a newer version of the product and cannot be opened." Is there any Guide how to migrate project to older IAR version? Or set IAR compiler in CubeIDE? Thank you!

1 ACCEPTED SOLUTION

Accepted Solutions
Ozone
Lead II

I would suggest to create a new project with the proper target in V7.40.1, and simply import all the example source files into this project. Including the startup (assembler) file(s).
You could try the same with the *.icf file (the linker config).
I did this about a dozen times, to port Eclipse-based, IAR or other STM32 projects to the Segger ES toolchain I use.

Unless your version does not support the MCU of this board.
In this case, I would recommend to update IAR WB to th latest version.

Sticking to specific compiler/toolchain version makes sense were certifications for the final product is involved, i.e. devices with safety or security related certificates.  A toolchain change would require an expensive re-certification.

View solution in original post

4 REPLIES 4

IAR should be able to tell you about migrating between different versions of their product...

Ozone
Lead II

I would suggest to create a new project with the proper target in V7.40.1, and simply import all the example source files into this project. Including the startup (assembler) file(s).
You could try the same with the *.icf file (the linker config).
I did this about a dozen times, to port Eclipse-based, IAR or other STM32 projects to the Segger ES toolchain I use.

Unless your version does not support the MCU of this board.
In this case, I would recommend to update IAR WB to th latest version.

Sticking to specific compiler/toolchain version makes sense were certifications for the final product is involved, i.e. devices with safety or security related certificates.  A toolchain change would require an expensive re-certification.

Yes, safety and security problems could be expensive, and also now i see that M33 core is not supported in 7.4 version so we will see. Thank you.

I know what you mean ...
My company maintains a bunch of toolchains, for both compatibility/maintainance reasons and safety certificate requirements - with ridiculously high costs per licence, especially the latter one's.
And toolchain suppliers usually stop to backport BSPs for new MCUs to older variants quite early. It is what it is ...