[OoB_5_5] Compile errors on IAR when using F411RE or any unsecure platform

[AriParkkila]

IAR Systems\Embedded Workbench 8.0 used.

mbed compile, see log

IAR IDE build, see log

[0xc0170]

We support 7.8 IAR version at the moment.

[AriParkkila]

Thanks. Where can I find officially supported mbed toolchains on the mbed website?

[SeppoTakalo]

Uhm...
https://docs.mbed.com/docs/mbed-os-handbook/en/latest/dev_tools/options/

Specifies IAR 7.7, but for mbed OS 5.5 this is going to change.
I hope that OOB testers are informed.

[ashok-rao]

The OoB spreadsheet's Introduction tab says to use IAR 7.8 ..

[AriParkkila]

I probably should have read OoB instructions more carefully :)

[SeppoTakalo]

Looks like the target is NUCLEO_F411RE and that does not have hardware random number generator.
Looks like it triggers some kind of weird build where part of mbed TLS is enabled and part of it is not.
CoAP service should be able to build without security, and it has been used that way. This needs more investigation why it only appears on this platform.

[AriParkkila]

I get the same error with IAR 7.8 log.

[AriParkkila]

As expected IAR IDE build gives the same error as mbed compile due to the same compiler. However IDE keeps compiling after the error so it reveals some additional warnings, see
log from IAR EW IDE 7.80.1.

[SeppoTakalo]

Can you also provide the mbed_app.json used for the build.

[AriParkkila]

Please see mbed_app.json.

[SeppoTakalo]

I can see now that these are compiler warnings in GCC and ARM, and failures in IAR.

So, I'm assuming that now this application fails to compile without security enabled on board in IAR.

[SeppoTakalo]

Verified that this example does not compile with NUCLEO_F401RE with IAR.

This is now reported in the known issues list.

[ciarmcom]

ARM Internal Ref: ONME-3194