[New Variant] request list

@kbumsik

Hereafter the list of all new variants requested and their linked issue.
Feel free to file an new issue then it will be added to this list.

Note

This is a community projects.
Any contribution is welcome, so feel free submit a PR. 😉

Important

To add a STM32 based board follows this wiki

Board support requested:

Discovery

Nucleo

Generic / Custom

3D printer:

BIGTREETECH BTT SKR PRO V1.2 ([New Variant] STM32F407ZGT6 - BIGTREETECH BTT SKR PRO V1.2 #1284)

LoRa:

Heltec LoRa Node L151 ([New Variant][on way] Heltec LoRa Node L151 #983) initial support at https://github.com/fthiebolt/LoRa-boards-stm32duino
RAK811 Wis DUO (STM32L(RAK811 chip) RAK811 Wis DUO #1395)
RAK3172: (RAK3172 "WLE5CCU6" STM32LoRaWAN#7)
- RAK3172-Evaluation-Board
  - RAK3172-SiP
STM32F103C8T6 with DX- LR30 or DX-LR20 ([New Variant] STM32F103C8T6 with DX-LR30 or DX-LR20 #2777)

Done

What about the new STM32MP1 MPU series which has both a Cortex-A7 as well as an onboard Cortex-M4 microcontroller unit?

https://blog.st.com/stm32mp1-mpu-stm32mp157a-ev1-stm32mp157c-dk2/

https://www.cnx-software.com/2019/02/21/stmicro-stm32mp1-cortex-a7-m4-mpu/

Seeed Studio ODYSSEY-STM32MP157C SBC based on Seeed Studio SoM-STM32MP157C SoM

https://www.cnx-software.com/2020/01/21/odyssey-stm32mp157c-sbc-feature-stmicro-stm32mp157c-cortex-a7-m4-soc/

Emtrion emSBC-Argon

https://www.cnx-software.com/2019/07/18/emtrion-emsbc-argon-stm32mp1-dual-cortex-a7-m4-processor/

i2Som PanGu board from I2Som:

https://www.cnx-software.com/2019/06/25/pangu-board-stm32mp1-sbc/

MYIR MYD-YA157C development board based on their MYiR MYC-YA157C STM32MP1 CPU Module

https://www.cnx-software.com/2020/01/07/myir-launches-som-development-board-based-on-stm32mp1-microprocessor/

Avenger96 96Boards CE Extended Board Features an STMicro STM32MP1 SoM

https://www.cnx-software.com/2019/02/23/avenger96-96boards-stmicro-stm32mp1-som/

Shiratech Stinger96 board (96Boards board design)

https://www.cnx-software.com/2020/05/15/stinger96-nb-iot-emtc-and-avenger96-96boards-stm32mp1-sbcs-giveaway/

Direct Insight / Ka-Ro STM32MP1 QSMP 1570 / 157C SoM module and development kit with reference board:

https://www.cnx-software.com/2020/06/26/linux-powered-stmicro-stm32mp1-solder-down-qfn-style-som-measures-27x27mm/

Could we also request support for STM32MP1 (STM32 MP1) that comes onboard STM32MP157A-DK1 development board?

https://www.st.com/en/evaluation-tools/stm32mp157a-dk1.html

STM32MP157A-DK1 development board also come with the STM32MP157C-DK2 Discovery Kit

https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html

STM32MP157A-DK1 and STM32MP157C-DK2 Discovery kits are $99 with LCD or $69 without
https://www.st.com/en/evaluation-tools/stm32mp157a-dk1.html
https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html

STM32MP157A-EV1 Evaluation kit for PCB engineers does have a steeper price at $399
https://www.st.com/en/evaluation-tools/stm32mp157a-ev1.html

Several other boards with STM32MP1 have been announced but none released yet AFIK.

Picked up STM32G0316-DISCO the other day. It'd be nice to port over. It's close to an ATTiny85 alternative.

It would be great if we could have more generic chip options. I'm particularly interested in the 48 and 64 pin versions of the STM32F401 and STM32F411, but these will be used on custom hardware and not board like the Nucleo. The F401 and F411 are also very reasonably priced on LCSC.com.

I've been a pro AVR user for years now, but have very experience with STM32. Let's say I start working on a pin definition file for all 48-pin F401C's. Can we use the same pin definition files for all variants (F401CB/CC/CD/CD)? And are there guidelines on how the Arduino pinout should look like? Perhaps similar/identical to other supported STM32's?

@MCUdude

@MCUdude
As far as I understand about this project, it can support all generic chips, since it pulled from the official STM32 Cube libraries.
The problem is that it is just impossible to define generic pinouts for all possible chips because Arduino platform requires flattened pinout definitions (like PA14 => Arduino Digial 1 pin). You should modify the source code to define your own board.
The good news is that you don't need to do much works since Arduino_Core_STM32 already supports STM32F401 Series, so you only need to define a new variant. You can see the wiki to figure out how to define your own variant and see here to learn how to work with the source code.

Can we use the same pin definition files for all variants (F401CB/CC/CD/CD)?

You should look at the datasheet to see if they have the same pinouts, but as far as I know they have different memories and the same package/pinouts.

@fpistm

The problem is that it is just impossible to define generic pinouts for all possible chips because Arduino platform requires flattened pinout definitions (like PA14 => Arduino Digital 1 pin)

Luckily, (unlike on 8-bit AVRs) I can still use the generic pin names (PA14) instead of the Arduino Pin number. This makes the actual Arduino pinout not so relevant to me, since I will always have full control over the generic pin names.

The good news is that you don't need to do much works since Arduino_Core_STM32 already supports STM32F401 Series, so you only need to define a new variant. You can see the wiki to figure out how to define your own variant and see here to learn how to work with the source code.

Thanks! I'll read through the Wiki and see what I can do. I prefer working in the PlatformIO IDE, so I hope a new variant for 48 pin 401/411's will be added if I do it right, since I'll rely on an official release. In PlatformIO it's also easy to change the microcontroller variant as long as I have a working variants file for the particular target. @fpistm any thought on adding more generic targets to this core?

You should look at the datasheet to see if they have the same pinouts, but as far as I know they have different memories and the same package/pinouts.

I haven't really read through the datasheet, but according to ST's tables the only difference is flash and RAM.

Luckily, (unlike on 8-bit AVRs) I can still use the generic pin names (PA14) instead of the Arduino Pin number. This makes the actual Arduino pinout not so relevant to me, since I will always have full control over the generic pin names.

I mean, this project is an Arduino Core port that implements Arduino API. Even if you physically have access to the generic pin names, Arduino API forces you to use Arduino-style pin numbers. So if you want more flexibility of choice of pins you might have to define your own Arduino pins to work with.

I prefer working in the PlatformIO IDE

I don't know how PlatformIO IDE works with third-party Arduino cores, but working with the source does not require a specific IDE, since you replace the official release with the git repo.

I mean, this project is Arduino Core that uses Arduino API. Even if you physically have access to the generic pin names, Arduino API forces you to use Arduino pin numbers. So if you want more flexibility of choice of pins you might have to define your own Arduino pins to work with.

Yes, I'm forced to use Arduino Pin numbers. But the PA[x], PB[x]..Pn[x] macros are defined in a way that they match their Arduino Pin number. On the Nucleo 401 board I have I don't care about digital pin 13. I use the PA5 macro instead (which is defined as 13).

I have lots of experience when it comes to "wrapping" the Arduino API around AVRs. I currently host six different repos here on GitHub, and some have become quite popular.

I don't know how PlatformIO IDE works with third-party Arduino cores, but working with the source does not require a specific IDE, since you replace the official release with the git repo.

I've been involved with platformIO since three on my Arduino cores (MightyCore, MiniCore and MegaCore) are available through PlatformIO. What they do is that they will make a copy of the latest release and include it in one of their repos. It is possible to add custom core files, but it's so much easier when it is already available as an option in their project wizard.

@MCUdude

@MCUdude
You can add an GenF4 menu, this is not a problem.
About Arduino pinout this is not an issue. We only try to do a correct pins mapping when there is an Arduino connector else this is not important. As you said it is easier to use PYn naming.
Only the Analog pins have to be contiguous.
You can refers to other GenYx series added as an example.

@fpistm

@fpistm thanks! I'll put some time and effort into this. Does any of you guys know if there exist a good ready-made F401/f411 48-pin development board? If not I'd probably have to roll my own.

It would also be great if it was possible to use the standard stlink programmer for the generic "boards", preferably the cheap $3 knockoff's. They do work great in PlatformIO, but not in Arduino IDE. I do have a black magic probe and currently waiting for a Jlink in the mail, but it's always nice to be able to use cheap and highly available tools. Is there any particular reason why support for stlink v2 was dropped?

STlinkv2 is supported, you have to install the STM32CubeProgrammer.

@thernstig

@thernstig You're right, I've made a clean up and update the description. Hope it is more clear now

@fpistm

Hello @fpistm
Sorry for the link, the problem description is there
platformio/platform-ststm32#160 (comment)

@brightproject

@brightproject
Use cubeMx to generate the clock config as described in the wiki.

I generated it without changing anything in the graphic designer, the function turned out like this:

void SystemClock_Config(void)
{
RCC_OscInitTypeDef RCC_OscInitStruct = {0};
RCC_ClkInitTypeDef RCC_ClkInitStruct = {0};

/** Initializes the RCC Oscillators according to the specified parameters

in the RCC_OscInitTypeDef structure.
*/
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI;
RCC_OscInitStruct.HSIState = RCC_HSI_ON;
RCC_OscInitStruct.HSICalibrationValue = RCC_HSICALIBRATION_DEFAULT;
RCC_OscInitStruct.PLL.PLLState = RCC_PLL_NONE;
RCC_OscInitStruct.PLL2.PLL2State = RCC_PLL_NONE;
if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)
{
Error_Handler();
}

/** Initializes the CPU, AHB and APB buses clocks
*/
RCC_ClkInitStruct.ClockType = RCC_CLOCKTYPE_HCLK|RCC_CLOCKTYPE_SYSCLK
|RCC_CLOCKTYPE_PCLK1|RCC_CLOCKTYPE_PCLK2;
RCC_ClkInitStruct.SYSCLKSource = RCC_SYSCLKSOURCE_HSI;
RCC_ClkInitStruct.AHBCLKDivider = RCC_SYSCLK_DIV1;
RCC_ClkInitStruct.APB1CLKDivider = RCC_HCLK_DIV1;
RCC_ClkInitStruct.APB2CLKDivider = RCC_HCLK_DIV1;

if (HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_0) != HAL_OK)
{
Error_Handler();
}

/** Configure the Systick interrupt time
*/
__HAL_RCC_PLLI2S_ENABLE();
}

It seemed to me that SystemClock_Config is similar to f103, the clock frequency for all is 72 MHz.

@brightproject

@brightproject
please in this kind of request open a discussion instead of pollute an issue opened only to reference board request.

Hi, I'd like to request support for the NUCLEO-C092RC (and/or any MCU from the STM32C092 series)

Thanks

@txf-

Hi @txf-

Hi, I'd like to request support for the NUCLEO-C092RC (and/or any MCU from the STM32C092 series)

Thanks

PR ongoing for this mcu, #2735

Please, add support for STM32H523 series; partucularly, for WeAct STM32H523CET6 demo board: https://github.com/WeActStudio/WeActStudio.STM32H523CoreBoard/

Thank you!

Made Custom driver and project using PlatformIO in VScode here for the Aliexpress modules.

https://github.com/NeutralSystem/STM32_DX-LR20_LORA

Made Custom driver and project using PlatformIO in VScode here for the Aliexpress modules.

https://github.com/NeutralSystem/STM32_DX-LR20_LORA

Better place would be here: https://github.com/orgs/stm32duino/discussions/categories/show-and-tell

Made Custom driver and project using PlatformIO in VScode here for the Aliexpress modules.
https://github.com/NeutralSystem/STM32_DX-LR20_LORA

Better place would be here: https://github.com/orgs/stm32duino/discussions/categories/show-and-tell

Thanks, posted it there now.

I want to request support for the WeAct Studio STM32U585CIU6. Thank you all for your great efforts.

Navigation Menu

Repository navigation

[New Variant] request list #722

Board support requested:

Discovery

Nucleo

Generic / Custom

3D printer:

LoRa:

81 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[New Variant] request list #722

Description

Board support requested:

Discovery

Nucleo

Generic / Custom

3D printer:

LoRa:

Activity

Hedda commented on Oct 28, 2019

justind000 commented on Oct 29, 2019

MCUdude commented on Nov 18, 2019

kbumsik commented on Nov 18, 2019

MCUdude commented on Nov 18, 2019

kbumsik commented on Nov 18, 2019

MCUdude commented on Nov 18, 2019

fpistm commented on Nov 18, 2019

MCUdude commented on Nov 18, 2019

fpistm commented on Nov 18, 2019

81 remaining items

fpistm commented on Oct 22, 2024

brightproject commented on Dec 20, 2024

fpistm commented on Dec 20, 2024

brightproject commented on Dec 20, 2024

fpistm commented on Dec 20, 2024

txf- commented on Apr 1, 2025

fpistm commented on May 22, 2025

ShaggyDog18 commented on Aug 2, 2025

NeutralSystem commented on Mar 21, 2026

fpistm commented on Mar 23, 2026

NeutralSystem commented on Mar 24, 2026

mhmayyan commented on Jun 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions