bluepill | simple process monitoring tool | Monitoring library

This is how I solved the problem:

Actually the LED toggles inside the while loop ,but only in debug mode

Yes, because that's the only time the generated machine code includes those delay loops. In release mode, the LED still toggless, except you need an oscilloscope or a logic analyzer to look at the output pin's state to see that it's toggling - you won't see it with just your eyes :)

In release mode, the delay loops are removed, because you can't implement delays that way. Ideally you should use a timer, but as a quick hack this would work:

First: don't use the STDPeriph, it's deprecated. Use the HAL.

Second: it's asking you to define in the library itself what platform it is compiling for so it can include the correct dependencies. (Such as peripheral placements in memory)

The solution is to read the STM chip's model number (something like STM32F103C8T6) then look inside the stm32f10x.h file and select your MCU, which probably involves uncommenting a define line. If you can't figure out what types of options there are, try reading the datasheet for the MCU you have as it specifies everything about it.

For the EVAL board you can select any of them as they only alias (define) simple names such as LED1. You just can't use them then.

BUT AGAIN DON'T USE STDPeriph use the HAL! Just use CubeMX to generate a project with libraries for you. It probably also better supports the BluePill than some old STDPeriph eval board header.

Found a strange fix.

Had to change the path to the Java binary to point to the provided version inside Arduino installation folder.

This is done through Environment Variables in Windows Control panel. You may also need to uninstall any other Java versions if you have any.

One reason could be there is not ADC pin of number 10 for the currently selected board (check the board on tool -> boards), there might be fewer number of ADC pins, e.g. try A0.

Or maybe you have selected wrong board. Bluepill isn't included in the Arduino IDE, by default. So you have to add it to your IDE first. There is a nice instruction here on how to do this and a sample code. https://maker.pro/arduino/tutorial/how-to-program-the-stm32-blue-pill-with-arduino-ide

Remember that this newly installed library could have small differences in syntax compared with standard Arduino code, Like this example that is taken from the mentioned site:

The STM32F103C8 runs at a maximum clock speed of 72 MHz. So 36 MHz is the maximum frequency that can be generated on a GPIO as a separate clock cycle is needed to set and clear the pin. This frequency can only be achieved with a timer.

If you try the same with code, you will need at least three instructions: two stores and one branch. These instructions require about 6 clock cycles to execute and will therefore result in a maximum frequency of about 12 Mhz.

In order to achieve this in software, your code should look something like this:

First, be aware that TMR clocks may be different from your system clock. So, be sure that you adjusted APB2 clock correctly.

Assuming that your APB2 clock is also 72 MHz, for 1 second period, you need to divide it by 72000000 (72e6) somehow. You need use ARR & PSC registers such that (ARR + 1) * (PSC + 1) = 72e6. Keep in mind that these registers are 16-bit, so they can't be greater than 65535.

One possible combination is:

Using await Navigation.PushAsync(new MainPage()); won't take you back to the MainPage you are using, this line of code will push to a new MainPage.

To select different tab programmatically under tabbar, you can use:

The ribbon cable is attached to the STDC14 connector and the pinout is described in chapter 9.1.3.

The relevant pins are:

• Pin 4: T_SWDIO aka SWDIO aka SWIO
• Pin 6: T_SWCLK aka SWCLK
• Pins 5 and 7: GND (choose either one)

The STLINK V3 cannot supply power to the Blue Pill (see note at the end of chapter 1). So the easiest solution is to supply power by connecting it to a USB port.

I'm not entirely sure how the ribbon cable is connected. Most likely, the red wire corresponds to pin 1 and the other pins follow in order. On the connector itself (looking at it the same way as on the picture), pin 1 would be bottom right (right side because of red wire, bottom side because it is closer to the notch). Better check it out with the continuity tester of a multi-meterr.

On the Blue Pill, the relevant pins are on the short side: