WeAct STM32F411CEU6 black pill

Discussion and questions about boards that can run MicroPython but don't have a dedicated forum.
Target audience: Everyone interested in running MicroPython on other hardware.
jppang
Posts: 1
Joined: Tue Feb 04, 2020 8:18 am

Re: WeAct STM32F411CEU6 black pill

Post by jppang » Tue Feb 04, 2020 8:32 am

gersch07 wrote:
Mon Feb 03, 2020 10:59 pm
Dear all,

I’ve followed the steps above to compile MicroPython (including support for a Winbond W25Q128 Flash Chip) and successfully flashed it using the ST-Link Utility. However, the ST Virtual COM port has so far only appeared twice after plugging in the USB cable... most of the time the device remains undetected, showing „Error 43“ in the Windows device manager. I‘m not sure if this is related, but in the „STM32duino“ forum people have reported that running the MCU at 100 MHz causes the USB clock to be slightly off...
Has anyone of you had similar trouble? I’ve also opened an issue on GitHub.

Thanks for your help!
I had tried 100MHz clock but failed too, USB communication was unstable.
96MHz clock is a good option for micropython.
Hope this can help.

User avatar
mcauser
Posts: 437
Joined: Mon Jun 15, 2015 8:03 am

Re: WeAct STM32F411CEU6 black pill

Post by mcauser » Mon Feb 10, 2020 4:10 am

In the board definition mpconfigboard.h, HSE is set to 25MHz and the CPU freq set to 96MHz (192/2) and USB 48MHz (192/4):

Code: Select all

#define MICROPY_HW_CLK_PLLM (25)
#define MICROPY_HW_CLK_PLLN (192)
#define MICROPY_HW_CLK_PLLP (RCC_PLLP_DIV2)
#define MICROPY_HW_CLK_PLLQ (4)
I noticed on the Arduino_Core_STM32 fix they increased the flash latency from 2 to 3. I'll try adding that:

Code: Select all

#define MICROPY_HW_FLASH_LATENCY    FLASH_LATENCY_3

Post Reply