summaryrefslogtreecommitdiffstats
path: root/keyboards/custommk/bonsai_c4_template/readme.md
diff options
context:
space:
mode:
authorDavid Hoelscher <infinityis@users.noreply.github.com>2022-11-13 17:59:01 -0600
committerGitHub <noreply@github.com>2022-11-13 23:59:01 +0000
commita42ab90220ce01c2aebdebb09aa458f383d26892 (patch)
tree4920acd95eef0a390a3a7f1a182b92803bbe91df /keyboards/custommk/bonsai_c4_template/readme.md
parent7901ba431a4a6248aeb4b16c570e96ce44e56a42 (diff)
Add Bonsai C4 as a platform board file (#18901)
* Set up Bonsai C4 as a platform board file * corrections and improvements based on testing and feedback * Added VBUS sensing as default capability for improved split support using Bonsai C4 * Update clock divisor for SPI flash Co-authored-by: Nick Brassel <nick@tzarc.org> Co-authored-by: Nick Brassel <nick@tzarc.org>
Diffstat (limited to 'keyboards/custommk/bonsai_c4_template/readme.md')
-rw-r--r--keyboards/custommk/bonsai_c4_template/readme.md10
1 files changed, 0 insertions, 10 deletions
diff --git a/keyboards/custommk/bonsai_c4_template/readme.md b/keyboards/custommk/bonsai_c4_template/readme.md
deleted file mode 100644
index 0c0fd8ed0c..0000000000
--- a/keyboards/custommk/bonsai_c4_template/readme.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# Bonsai C4 template code
-
-Currently, the converter for Pro Micro to Bonsai C4 only does pin mapping. This is sufficient for simple keyboards and also a good start for
-incorporating into more advanced keyboards with other features (like RGB, OLED, backlighting, split communiciations, etc.). However, to make
-use of the more advanced features--including using the FRAM and flash memory chip included on Bonsai C4--various peripheral hardware must
-be configured. Pro Micro does not requrie such configuration because such functionality is more limited and hard-wired to specific pins.
-
-The code here provides examples that can be used to operate SPI, I2C, PWM, and Serial comms. In addition to using the converter, you will
-need to take code (as-needed) and add it to existing config.h files, or add in new halconf.h and mcuconf.h files. If you are changing which
-pins are used for certain functions, you should verify the new pins support that functionality, and check all assingments to ensure the correct settings are used (including as-applicable driver, channel, PAL (Pin ALternate function) mode, DMA stream, and/or DMA channel).