Consequences of using gcc-arm-none-eabi-7-2017-q4-major-win32 with nRF5_SDK_17.1.0

[TilakL]

Hi,

I would like to help/influence the course of our on-going project with nRF52832 such that the recommended/default Toolchains are used. In this regard I have the following question:

I understand that the nRF5_SDK_17.1.0 recommends using GNU Arm Embedded Toolchain/9 2020-q2-update version 9.3.1. I would like to understand the consequences of using an older version such as gcc-arm-none-eabi-7-2017-q4-major-win32. Also, do you foresee any problems/vulnerabilities with using micro-ecc due to this Toolchain mismatch?

Thanks,
Tilak

[Simonr]

Hi Tilak

We recommend the specific toolchain that an nRF5 SDK version has been production tested with, so we know for sure that it will work with that toolchain version. Using other toolchains have not been tested, so we can't provide any guarantees, but they will most likely work, and it is up to the individual customer whether they want to use another toolchain than what has been used for testing/verification. I don't have any comments on what specific problems you might see when using another toolchain.

Best regards,

Simon