Bluepill board support for Mbed OS 6

hudakz · May 13, 2020, 3:51pm

Hello,

the Bluepill (STM32F103C8) module is supported as a custom board for Mbed OS 6. You can find the repository at mbed-os-bluepill.

Best regards, Zoltan

jeromecoutant · July 7, 2020, 11:53am

Hi Zoltan

With mbed-os-6.1.0, Bluepill support should be even easier!
You should only keep PeripheralPins.c and PinNames.h,
then, custom_target has only to inherit from “MCU_STM32F103x8”

hudakz · July 8, 2020, 7:26am

Hello Jerome,

Thank you for the notice and making life easier!

Best regards, Zoltan

DesktopMan · July 20, 2020, 4:29pm

Would it be possible for this to be updated for Mbed OS 6.2? I tried keeping only PeripheralPins.c and PinNames.h and changing the target inheritance as Jerome suggested, and I got blinky working but USB does not work for me.

hudakz · July 20, 2020, 5:56pm

Hello,

Thank you for the feedback. mbed-os-bluepill is now updated to Mbed OS 6.2.0.

Best regards, Zoltan

DesktopMan · July 21, 2020, 1:10pm

Thank you for the update. I still seem to have a problem with USB. The following code works fine on the ST L475 board, but not on a Bluepill with your target configuration:

Here’s the Linux kernel output:

[3165.055171] usb 1-1.3: new full-speed USB device number 36 using xhci_hcd
[ 3165.135362] usb 1-1.3: device descriptor read/64, error -32
[ 3165.323206] usb 1-1.3: device descriptor read/64, error -32
[ 3165.511339] usb 1-1.3: new full-speed USB device number 37 using xhci_hcd
[ 3165.591343] usb 1-1.3: device descriptor read/64, error -32
[ 3165.779243] usb 1-1.3: device descriptor read/64, error -32
[ 3165.887440] usb 1-1-port3: attempt power cycle
[ 3166.491330] usb 1-1.3: new full-speed USB device number 38 using xhci_hcd
[ 3166.491515] usb 1-1.3: Device not responding to setup address.
[ 3166.699506] usb 1-1.3: Device not responding to setup address.
[ 3166.907313] usb 1-1.3: device not accepting address 38, error -71
[ 3166.987301] usb 1-1.3: new full-speed USB device number 39 using xhci_hcd
[ 3166.987486] usb 1-1.3: Device not responding to setup address.
[ 3167.195510] usb 1-1.3: Device not responding to setup address.
[ 3167.403314] usb 1-1.3: device not accepting address 39, error -71
[ 3167.403471] usb 1-1-port3: unable to enumerate USB device

hudakz · July 21, 2020, 1:43pm

Hello,

The BLUEPILL custom target is based on (inherits from) the officially supported MCU_STM32F103x8 target which does not implement a USBDEVICE. You can verify that in the mbed-os/targets.json at master · ARMmbed/mbed-os · GitHub file. By the way, neither the official NUCLEO_F103RB target implements a USBDEVICE. On the other hand, for the officially supported DISCO_L475VG_IOT01A target Mbed OS 6 implements a USBDEVICE. That’s why the #include "mbed.h"#include "USBMouse.h"//create mouse objectUSBMouse mous - Pastebin.com code compiles.

Best regards, Zoltan

DesktopMan · July 24, 2020, 4:50pm

The code compiles fine for both the BLUEPILL target and the NUCLEO_F103RB target, it just doesn’t work correctly. Is this something that could be added in the BLUEPILL target? Or must it be added in the base MCU_STM32F103x8 target?

hudakz · January 8, 2021, 10:24pm

Hello,

To make USB work update the TARGET_BLUEPILL directory in your project and add the following mbed_app.json file to the root directory of your project:

{
    "requires": ["bare-metal","drivers-usb", "events"],
    "target_overrides":{
        "*": {
            "target.clock_source": "USE_PLL_HSE_XTAL",
            "target.clock_source_usb": "1",
            "target.device_has_add": ["USBDEVICE"]
        }
    }
}

Best regards, Zoltan

flamedmg · February 15, 2021, 12:37pm

Hello, mbed newbie here. Just installed mbed studio and imported your project. Can’t build or set target.
Here is an output:
c:\Users\DmG\Mbed Programs\bluepill>mbed compile -t GCC_ARM -m bluepill
[mbed] Working path “c:\Users\DmG\Mbed Programs\bluepill” (program)
Traceback (most recent call last):
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\targets_init_.py”, line 151, in target
resolution_order = get_resolution_order(json_data, name, )
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\targets_init_.py”, line 139, in get_resolution_order
order = get_resolution_order(json_data, par, order, level + 1)
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\targets_init_.py”, line 137, in get_resolution_order
parents = json_data[target_name].get(“inherits”, )
KeyError: ‘MCU_STM32F103x8’

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\make.py”, line 421, in
main()
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\make.py”, line 311, in main
mcu = extract_mcus(parser, options)[0]
File “c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\options.py”, line 145, in extract_mcus
update_target_data()
), exc)
File “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\future\utils_init_.py”, line 398, in raise_from
exec(execstr, myglobals, mylocals)
File “”, line 1, in
tools.utils.NotSupportedException: target BLUEPILL has an incomplete target definition
[mbed] ERROR: “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe” returned error.
Code: 1
Path: “c:\Users\DmG\Mbed Programs\bluepill”
Command: “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe -u c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\make.py -t GCC_ARM -m bluepill --source . –
build .\BUILD\BLUEPILL\GCC_ARM”
), exc)
File “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\future\utils_init_.py”, line 398, in raise_from
exec(execstr, myglobals, mylocals)
File “”, line 1, in
tools.utils.NotSupportedException: target BLUEPILL has an incomplete target definition
[mbed] ERROR: “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe” returned error.
Code: 1
Path: “c:\Users\DmG\Mbed Programs\bluepill”
Command: "c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe -u c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\make.py -t GCC_ARM -m bluepill --source . –
), exc)
File “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\future\utils_init_.py”, line 398, in raise_from
exec(execstr, myglobals, mylocals)
), exc)
), exc)
File “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\future\utils_init_.py”, line 398, in raise_from
exec(execstr, myglobals, mylocals)
File “”, line 1, in
tools.utils.NotSupportedException: target BLUEPILL has an incomplete target definition
[mbed] ERROR: “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe” returned error.
Code: 1
Path: “c:\Users\DmG\Mbed Programs\bluepill”
Command: “c:\Users\DmG\AppData\Local\Mbed Studio\mbed-studio-tools\python\python.exe -u c:\Users\DmG\Mbed Programs\bluepill\mbed-os\tools\make.py -t GCC_ARM -m bluepill --source . –
build .\BUILD\BLUEPILL\GCC_ARM”
Tip: You could retry the last command with “-v” flag for verbose output

hudakz · February 15, 2021, 10:35pm

Hello Dmitry,

Open the Target drop-list.
Type BLUEPILL (upper case!) into the Search targets edit box and select BLUEPILL from the drop-list.
Click on the button with a hammer icon on it (Build program).

Although the bluepill board is a good choice for Mbed OS 2, because of it’s relatively small SRAM (20 kBytes) and flash size (64/128 kBytes) it isn’t very suitable for Mbed OS 6 (especially when RTOS is used).

To learn Mbed OS 6 the blackpill (128 kBytes SRAM, 512 kBytes flash memory) is a much better choice (still at a quite low price).

Best regards, Zoltan

nonchip · March 11, 2021, 11:57am

having the same issue as dmitry here even though i did all that: just installed mbed studio, imported the mbed6 bluepill example blinky project, selected BLUEPILL as the target, compiling fails with:

KeyError: 'MCU_STM32F103x8'
tools.utils.NotSupportedException: target BLUEPILL has an incomplete target definition

(those are the actual errors thrown in between a bunch of python stacktrace that’s most likely irrelevant)

almost sounds to me like MCU_STM32F103x8 doesn’t exist in whatever list it’s trying to find compatible MCUs?

jeromecoutant · July 7, 2021, 3:11pm

Hi all
Note I just added BLUEPILL support in this new repo:

hudakz · July 8, 2021, 7:24am

Hello Jerome,

Thank you for the STM32 custom targets support! It makes life easier for users and I hope it will motivate the other Mbed partners to provide such support too.

With best regards, Zoltan

JojoS · September 21, 2021, 9:23pm

great starting point also for using custom_targets with CLI2 and cmake.

alma_mohmoud · March 4, 2022, 10:44am

anyone help to install it

hudakz · March 4, 2022, 11:13am

Hello alma_mohmoud,

Visit GitHub - ARMmbed/stm32customtargets: Enable the support of your custom boards in mbed-os 6 and have a look at the Usage and BLUEPILL sections.

Topic		Replies	Views
USBSerial on bluepill / STM32F103RB Mbed OS stmicroelectronics	5	820	January 8, 2021
MBED support for a STM32 custom board? Custom and community boards stmicroelectronics	8	896	October 4, 2021
Custom Tragets mbed 6.0.0 Bugs mbed_os	1	346	June 24, 2020
STM32F411CE Black Pill USB Mbed OS	7	3148	December 29, 2023
Bluepill programming with online compiled bin Custom and community boards bluepill	1	789	May 21, 2020

Bluepill board support for Mbed OS 6

Related topics