Add high-density STM32F103RC support

[HorrorTroll]

Description

Add high-density STM32F103RC support for "STM32 Mini V2 Development Kit" board, in case you want to using for experiment thing if you couldn't find any "Bluepill STM32F103C8" and it cheap.

The EEPROM emulation support is not included, as it have built-in SPI Flash 2M-Bit W25Q16JVSIQ already. So by default this board will be using wear_leveling driver on SPI Flash.

Tested onekey keymaps:

• default
• adc (needs changes in halconf.h and mcuconf.h to enable ADC)
• backlight
• console
• digitizer (not tested yet)
• eep_rst (with EEPROM_DRIVER=transient this just restarts the firmware)
• hardware_id
• oled (needs changes in halconf.h and mcuconf.h to enable I2C)
• quine (not tested yet)
• reboot (works appropriately with stm32duino — the bootloader does not appear during the reboot)
• reset (works appropriately with stm32duino — the bootloader starts with the 8s timeout disabled)
• rgb (not tested yet)
• rgb_matrix (needs -e RGB_MATRIX_DRIVER=WS2812 -e CONSOLE_ENABLE=no)

This is my first time open these kind pr, so I would like to have a proper reviewer code. Thanks!

Types of Changes

• [x] Core
• [ ] Bugfix
• [ ] New feature
• [x] Enhancement/optimization
• [x] Keyboard (addition or update)
• [ ] Keymap/layout/userspace (addition or update)
• [ ] Documentation

Checklist

• [x] My code follows the code style of this project: C, Python
• [x] I have read the PR Checklist document and have made the appropriate changes.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[HorrorTroll]

Thanks, lemme split that up right away

[HorrorTroll]

Done, just split the pr to #18066. Feel free to review again, thanks!

[github-actions[bot]]

Thank you for your contribution! This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready. For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[HorrorTroll]

I'm just done it, if u have free time. Can u take a look?

[github-actions[bot]]

Thank you for your contribution! This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready. For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[github-actions[bot]]

Thank you for your contribution! This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. // [stale-action-closed]

[HorrorTroll]

Ehh, sorry but this PR still active and waiting for reviewing

[HorrorTroll]

Done, if anyone have times. Can i have a re-review on this PR?

[HorrorTroll]

Done, thanks

[HorrorTroll]

I'm sorry, the PR seem to be long active anyway. Can i have a re-review this one? Thanks