aboutsummaryrefslogtreecommitdiffstats
path: root/README.org
diff options
context:
space:
mode:
authorBrian Cully <bjc@kublai.com>2022-08-08 12:19:08 -0400
committerBrian Cully <bjc@kublai.com>2022-08-08 12:19:08 -0400
commitcabe5b42cfe408c7bbde8b4bd40ce0282eb7e58c (patch)
tree9247007dc67478babeab603150bbe9daeeaa6bf6 /README.org
parent340eb6eb0d3fb47f5d968c323c92943662457fda (diff)
downloadluchie-cabe5b42cfe408c7bbde8b4bd40ce0282eb7e58c.tar.gz
luchie-cabe5b42cfe408c7bbde8b4bd40ce0282eb7e58c.zip
get serial printing on usart1 (tx: pa2, rx: pa3)
Diffstat (limited to 'README.org')
-rw-r--r--README.org3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.org b/README.org
index 1fd9975..9ad9910 100644
--- a/README.org
+++ b/README.org
@@ -1,4 +1,4 @@
-looks like the start board is a gd32vf103cbt from the tiny print silk-screened on the chip. [[https://www.tme.com/us/en-us/details/gd32vf103c-start/development-kits-others/gigadevice/][TME]] says it's a gd32vf103d6t6
+looks like the start board is a gd32vf103cbt from the tiny print silk-screened on the chip. [[https://www.tme.com/us/en-us/details/gd32vf103c-start/development-kits-others/gigadevice/][TME]] says it's a gd32vf103d6t6 — but [[https://www.gigadevice.com/products/microcontrollers/gd32-development-tools/gd32-mcu-starter-kits/][gigadevice]] says gd32vf103cbt6
which means it has 128k flash and 32k sram and 37(!) gpio pins
@@ -17,3 +17,4 @@ usb is 2.0 full-speed (12Mbps)
* USART
On [[https://github.com/tyustli/rt-thread/tree/master/bsp/gd32vf103v-eval][github]] it says that ~uart0~ tx/rx is gpio 9/10 — but that's for the eval board.
See the [[https://github.com/riscv-mcu/GD32VF103_Firmware_Library/tree/master/Examples/USART/Printf][risc-v repository]] for a printf example.
+The [[https://docs.zephyrproject.org/latest/boards/riscv/gd32vf103c_starter/doc/index.html][zephyr documentation]] for it indicates the usb is on ~usart0~ with tx/rx pins ~pa9~ / ~pa10~