Description
Describe the problem
The IDE attempts to configure a board platform, even though there is an error
To reproduce
-
Open IDE 2.0.0rc9.1
-
From the board manager, select version 3.2 of the Mbed library for the Portenta and install
-
The following message is displayed in the terminal
Tool arduino:[email protected] already installed Tool arduino:arm-none-eabi-gcc@7-2017q4 already installed Tool arduino:[email protected] already installed Tool arduino:[email protected] already installed Downloading packages Installing arduino:[email protected] arduino:[email protected] installed Installing platform arduino:[email protected] arduino:[email protected] installed Installing platform arduino:[email protected] Configuring platform. Failed to install platform: arduino:mbed_portenta. Error: 13 INTERNAL: Cannot install platform: installing platform arduino:[email protected]: moving extracted archive to destination dir: rename C:\Users\user\AppData\Local\Arduino15\tmp\package-4051948726\mbed C:\Users\user\AppData\Local\Arduino15\packages\arduino\hardware\mbed_portenta\3.2.0: Access is denied.
-
The UI continues displaying the message
Processing Arduino Mbed OS Portenta Boards: 3.2.0: Configuring platform
for over an hour -
After trying again to install, I am told version 3.2.0 is installed, but the Portenta boards do not show up in the list of supported boards.
-
Close and open the IDE. You will notice that the
INSTALLED
tag is no longer shown when you try to install the Portenta board library again.
Expected behavior
If the library install fails, I would expect to receive a message in the UI stating that it has failed.
Arduino IDE version
IDE 2.0.0-rc9
Operating system
Windows
Operating system version
Windows 10
Additional context
I see no way to remove the Processing Arduino Mbed OS Portenta Boards: 3.2.0: Configuring platform
message, without restarting the program.
I also tried to install support for the Nicla boards, which was done successfully.
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details