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 280 commits into
Draft
Conversation
dragonmux
added
the
Foreign Host Board
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
1d39692 to
fb6cb65
Compare
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
fb6cb65 to
b84edbf
Compare
Contributor
Author
|
This now supports 96 MHz APM32F103CB. |
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
ed79933 to
f6dab76
Compare
ALTracer
force-pushed
the
feature/bluepillplus-platform
branch
from
f6dab76 to
97627db
Compare
… writing firmware
…v8-M main profile
…adability in the USB configuration setup code
…per use of atomics, resulting in smaller and more correct code
…roper use of atomics, resulting in smaller and more correct code
…change notifications so it's a little more responsive without being overwhelming for traffic
…correctly and the pins are driven suitably hard
…the on-board Flash
…ng the dual target serial interfaces up to the second host serial interface
…oesn't get upset by them
…K blocks as found on the Lattice Versa boards
…nk v2 firmware to make things fit again
…and stubs for manipulating it
…ulation to implement Flash functions
…ut of programming mode
…lock_flash_erase`
…ommand This was found by looking at the JTAG traffic the lattice diamond programmer generated when programming the ispCLOCK device, and the name was extracted from a JED for the ispCLOCK being converted to an svf file, as the name for this command was included in a comment in the resulting file.
…_done` These now properly handle the setup and exit for programming ispCLOCK devices
…e attached ispCLOCK device. After much mucking about and trying to figure out what the lattice programmer was doing and how much of it is required, the method for properly programming the ispCLOCK devices was figured out, which does include wiggling TCK, for some reason....
This is used so we can verify the contents of the the ispCLOCK device and ensure that the correct configuration for it was written
* Extract the memory write into a dedicated helper function * Wrap it into TRY-CATCH macros * Drop the extraneous 10ms delay introduced back in PR2072
* 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
d075c2b to
1c31cc6
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.
9 participants
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