This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Build failures with projects with e2studio Standalone Installer and FSP v2.0.0.

Title: Build failures with projects with e2studio Standalone Installer and FSP v2.0.0.

 

Issue:

When using the e2studio standalone installation <https://www.renesas.com/us/en/products/software-tools/tools/ide/e2studio.html>  and FSP 2.0.0 https://github.com/renesas/fsp/releases/download/v2.0.0/FSP_Packs_v2.0.0.exe and installing to the same location as a previous FSP (v1.x) installation, the pack files Arm.MbedCrypto.3.1.0+renesas.1.pack and Arm.MbedTLS.3.0.0+renesas.0.pack installed by FSP v2.0.0 are not extracted to the support area since they have the same name (but different contents) than the previous FSP version (v1.x) installed. This results in build errors when a project requiring these pack files is built.

Note: The issue does not occur when operating the platform installer from Github with default installation settings.

 

Workaround:

Create a new e2studio installation for 2.0.0/2.1.0, separate from e2studio installations used with FSP v1.x.