This repository was archived by the owner on Mar 7, 2026. It is now read-only.
New platform: WeActStudio.BluePill-Plus-GD32#2071
Draft
ALTracer wants to merge 332 commits into
Draft
Conversation
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
March 6, 2025 04:41
1d39692 to
fb6cb65
Compare
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
March 23, 2025 13:17
fb6cb65 to
b84edbf
Compare
Contributor
Author
|
This now supports 96 MHz APM32F103CB. |
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
July 13, 2025 14:53
ed79933 to
f6dab76
Compare
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
July 23, 2025 19:23
f6dab76 to
97627db
Compare
…e off the binary and fixing it being grumpy if the length parameter was 0
…p formatting functions
…ion builder function
…dd_by_id() not being an actual error
…usage being able to loose the input pointers if the entry allocation fails
… command (JTAG run cycles command)
… with `jtagtap_cycle()`
…ferent probe platforms and their variants in CI
… we aren't having to build libftdi and other components and getting spurious errors out the flow
…ur dependencies can be cleaned up a biti
… from Linux using UCRT64 tooling
… so that CI can function correctly
TI added multiple layouts for the registers depending on a part. Implementing and maintaining it all is too much effort (and code) with dubious value.
…of the GDB packet structure
…g missing to properly bound the requests to the probe
… to properly bound the requests to the probe in the JTAG TMS sequence impl
…aders to reflect the updates being made
…andle 64-bit addresses
…he remote protocol command functions that would result in garabge or non-sensical error messages being displayed when `platform_buffer_read()` failed with a negative error value
… SWD comms for ADIv5, `dp->ensure_idle` could be left stale pointing at the JTAG function and crash the probe
…C-V support itself is enabled in the firmware
…ilable via the normal GDB memory interfaces anyway
…nk v1 firmware to make things fit again
* Uses PB2 LED, USB FS device with external 1.5k pullup * BMD bootloader also uses PA0 button and boot magic flags
* WeActStudio.BluePill-Plus boards have a DNF SOIC-8 footprint for 25-series SPI NOR flash, wired to PA4/5/6/7. * Add the pin mappings regardless of the platform flavour.
* Rely on DBGMCU_IDCODE and SCB_CPUID
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
July 13, 2026 17:24
5e3cdaf to
581a69c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Detailed description
bluepillplus. In-tree platforms default to 72 MHz and do not leverage full potential of Gigadevices. Unmapping own SWJ-DP is not always acceptable, andstlinkpinout is just weird.I do not expect this to be merged, because in-tree
-Dprobe=bluepillalready does provide some functionality. I do not implement vanilla PC13 bluepills, it's impossible for me to discern these from bluepillplus. This platform has feature parity withblackpill-f4, except I'm dissatisfied with its USBOTG-FS DWC2 bugs.Choice of USART for Aux and SWO was influenced by existing 2x128 aux_serial DMA ping-pong buffers, which are insufficient for 1024 byte Zmodem packet operation I need in DUT firmware. So SWO is faster for burst operation. When that's refactored, I'll swap them back such that 6Mbaud VCP is possible.
TODO: I'd like to use
platform_identto indicate autodetection results, and to leverage meson options to pick linkerscripts which influence flash size for drivers and RAM size for heap/buffers/SWO.Your checklist for this pull request
Closing issues