# Maker support for STM32 Bluepill 64kb?
**URL:** https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641
**Category:** Maker
**Created:** [October 17, 2019, 5:30pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641 "2019-10-17T17:30:58Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@gbraad](https://forum.makecode.com/u/gbraad)
#### Post date: [October 17, 2019, 5:30pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/1 "2019-10-17T17:30:58Z")
In recent time I have only been able to get hold of medium density STM32F103 boards (bluepills). Which means they come with either 64kb (C8) or 128kb (CB). But, all of them have been 64kb … and according to [https://github.com/microsoft/pxt-maker/tree/master/libs/bluepill#support-for-blue-pill-boards](https://github.com/microsoft/pxt-maker/tree/master/libs/bluepill#support-for-blue-pill-boards) ONLY 128kb is supported. However, I have no use for these boards for jacda, math and the asserts. How would I go about adding this as a target?
I found that the base was modified in [https://github.com/microsoft/pxt-common-packages/pull/706/files](https://github.com/microsoft/pxt-common-packages/pull/706/files) to become leaner and providing the STM32F1 support, but can this be made modular as not all targets would require jacdac or advanced maths
---
### Author:  [@mmoskal](https://forum.makecode.com/u/mmoskal)
#### Post date: [October 18, 2019, 4:57pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/2 "2019-10-18T16:57:31Z")
Depends what you want to do, but most of these boards have 128k and the ones marked as 64k are just untested beyond 64k. So if you are doing something that isn’t critical then it may just work.
---
### Author:  [@gbraad](https://forum.makecode.com/u/gbraad)
#### Post date: [October 18, 2019, 5:04pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/3 "2019-10-18T17:04:29Z")
UF2 firmware was flashed, but after uploading the .hex of a simple blink using the LED (PC13) nothing seems to happen.
```auto
forever(function () {
pins.LED.digitalWrite(false)
pause(1000)
pins.LED.digitalWrite(true)
pause(1000)
})
```
The boards led blink/fades to show the bootloader passed, and then stays dark.
---
### Author:  [@gbraad](https://forum.makecode.com/u/gbraad)
#### Post date: [October 22, 2019, 9:13am UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/4 "2019-10-22T09:13:51Z")
> [@mmoskal](#):
>
> it may just work.
How to make sure of this?
---
### Author:  [@mmoskal](https://forum.makecode.com/u/mmoskal)
#### Post date: [October 22, 2019, 2:23pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/5 "2019-10-22T14:23:47Z")
Does it work on your 128k boards?
---
### Author:  [@gbraad](https://forum.makecode.com/u/gbraad)
#### Post date: [October 22, 2019, 2:36pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/6 "2019-10-22T14:36:32Z")
Well, that is the whole point. Flashing the firmware and uploading the program is not the issue… but when I use the code as described above it should blink the LED on PC13, right? I does not… is that conclusive? not sure how to get more information, like debugging… I have an ST-Link V2 if necessary (no CMSIS-DAP at the moment).
---
### Author:  [@mmoskal](https://forum.makecode.com/u/mmoskal)
#### Post date: [October 24, 2019, 5:05pm UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/7 "2019-10-24T17:05:04Z")
Well I didn’t test 128k version recently, so it could be broken completely. Maker is not very stable, especially for less used boards.
There are some docs on hardware debugging here [https://github.com/microsoft/pxt/blob/master/docs/develop/hw-debugging.md](https://github.com/microsoft/pxt/blob/master/docs/develop/hw-debugging.md)
---
### Author:  [@gbraad](https://forum.makecode.com/u/gbraad)
#### Post date: [October 25, 2019, 10:26am UTC](https://forum.makecode.com/t/maker-support-for-stm32-bluepill-64kb/641/8 "2019-10-25T10:26:00Z")
> [@mmoskal](#):
>
> the ones marked as 64k are just untested beyond 64k.
I have checked, and in ST-Link utility all boards I have are identified as:
```auto
18:21:18 : Device ID:0x410
18:21:18 : Device flash Size : 64KBytes
18:21:18 : Device family :STM32F10xx Medium-density
```
they were sourced from about 5 different places over time