Upgrading Arduino IDE to V2 fails

[Phonog]

Hi, I have used the arduino IDE1 with the STM32 boards package v1.8 for years, with success.
Now I want to move to IDE V2, and I have installed the board package V2.11.
Compilation and upload have worked. However, the board, once programmed, does not work.
Details:
I use Olimexino STM32 boards, which are equivalent to the late Maple boards.
In IDE1 I used to select the following options:

In IDE 2 I chose the following options:

Apparently both selections are identical.
I did the test with the Blink example sketch. In IDE 1, it works normally.
In IDE 2, nothing happens once the board is rebooted. I checked the digital pins using a multimeter, and basically the output pin selected in the source code was floating, i.e., uninitialized. What is more serious, is that the USB serial device that the board presents at power on was missing.
I could recover by forcing the board to "permanent upload mode" using the buttons, and reprogramming it using IDE 1. So no harm was done to the board, but the sketch did not run for some reason.
Is this a known problem? Or did noone use the packages since V2 with Olimexino/Maple boards to encounter it?

[fpistm]

I used maple board regularly and it works.
I do not have this board (blue button) so never tested.
This board have been added to 1.9.0 which is very old. Since this release, several update were done. It is possible the init simply failed because of a wrong option in the clock config which is now catch by the HAL.
You best bet is to try to debug if you have a STLink.
Enable the "Optimize for debugging" in the Sketch menu.

[Phonog]

AS I said, I installed the deprecated package V1.8.0 into the IDE V2 and it worked normally.
I then updated the package to the last version of the deprecated set, which is 1.90.
I then noticed that the board type I used, "Blue Button", was no more present in the package. Instead was a "Blue Pill" which does not use the same chip. See the screen capture:

I tried to select the board Generic F103RB, but it failed. It could compile and upload, but the board did not start.
When you say that it was introduced with version 1.9, are you talking about the Blue Pill or the Blue Button? The blue pill is as follows:

I have no pic for a blue button, but this is the setting that works for me and that has be removed in version 1.9.
The blue button option exists in version 2.11, but it does not work.

[fpistm]

Blue button name was removed in 1.9.0 as it is purely a generic board and where only the LED was defined. It was not removed only cleanup. See e27a24d
Since 2.x variants are better managed and automatically generated for generic to avoid any issue.

You used a variant which is for another board with a dedicated config.

So try to use the variant Generic F103RBTx with the correct LED pin definition. This OLIMEX is not supported by default.

#define OLIMEX_LED PA1
// #define OLIMEX_LED PA5

// the setup function runs once when you press reset or power the board
void setup() {
  // initialize digital pin LED_BUILTIN as an output.
  pinMode(OLIMEX_LED, OUTPUT);
}

// the loop function runs over and over again forever
void loop() {
  digitalWrite(OLIMEX_LED, HIGH);  // turn the LED on (HIGH is the voltage level)
  delay(1000);                      // wait for a second
  digitalWrite(OLIMEX_LED, LOW);   // turn the LED off by making the voltage LOW
  delay(1000);                      // wait for a second
}

[Phonog]

Using package V1.9, or 2.11?

[fpistm]

2.11.0...

[Phonog]

I just did the test with package 2.11. With the correct declaration of the LED pin, the sketch works : the LED flashes!
Thanks for your help.
I still have a problem. In the version 1.8, there was a problem with the USB enumeration, and at that time (several years ago), someone proposed a workaround : in the Setup(), insert the following lines:

pinMode(DISC, OUTPUT); // DISC
digitalWrite(DISC, HIGH) ; // Séquence d'invite à l'énumération USB
digitalWrite(DISC, LOW) ;

The DISC signal when active pulls the D+ line of the USB bus high, which invites the host to restart the enumation. See the schematic below.

This worked well with the package V1.8, and I never had a problem with it. Once initialised, the boards manifest a serial port to the host.
However, in package 2.11, this mechanism does not work fully. After reboot of the board, my PC show a fugitive notification saying that a peripheral was not recognized, and the peripheral manager shows a faulty device (the device descriptor was not recognized):

What can I do with this?

[fpistm]

You have to define this:

Arduino_Core_STM32/variants/STM32F1xx/F103C8T_F103CB(T-U)/variant_MAPLEMINI_F103CB.h

Line 141 in 22e40f4

#define USBD_ATTACH_PIN PB9