| Both sides previous revisionPrevious revision | |
| en:pfw:spi_gd32vf_mecrisp-quintus [2024-07-06 16:57] – some typos mb | en:pfw:spi_gd32vf_mecrisp-quintus [2024-07-22 11:01] (current) – [Files] uho |
|---|
| ==== Files ==== | ==== Files ==== |
| |
| ^Filename ^Comment ^ | ^Filename ^Comment ^ |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:readme.md|read.me]] |This file | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/readme.md|read.me]] |This file | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi-soft.fs|spi-soft.fs]] |You're totally free to choose the pins you use. It will consume MCU time. | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi-soft.fs|spi-soft.fs]] |You're totally free to choose the pins you use. It will consume MCU time. | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi0-hard.txt|spi0-hard.txt]] |Will use the built-in module of the GD32VF103. Here is shown how to remap the pins used by SPI0. That makes it possible to have the display of the Longan Nano running in parallel. | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi0-hard.txt|spi0-hard.txt]] |Will use the built-in module of the GD32VF103. Here is shown how to remap the pins used by SPI0. That makes it possible to have the display of the Longan Nano running in parallel. | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi0-normalize.fs|spi0-normalize.fs]] |Translates the words **{SPI0 SPI0} SPI0-IN SPI0-OUT SPI0-I/O** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi0-normalize.fs|spi0-normalize.fs]] |Translates the words **{SPI0 SPI0} SPI0-IN SPI0-OUT SPI0-I/O** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi1-hard.fs|spi1-hard.fs]] |Will use the built-in module of the GD32VF103. Can act as a template for all spiX interfaces. It releases the MCU. It is shown how to switch to a software CS line. For that, follow the steps shown in spi1-set-software-cs.fs.| | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi1-hard.fs|spi1-hard.fs]] |Will use the built-in module of the GD32VF103. Can act as a template for all spiX interfaces. It releases the MCU. It is shown how to switch to a software CS line. For that, follow the steps shown in spi1-set-software-cs.fs.| |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi1-normalize.fs|spi1-normalize.fs]] |Translates the words **{SPI1 SPI1} SPI1-IN SPI1-OUT SPI1-I/O** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi1-normalize.fs|spi1-normalize.fs]] |Translates the words **{SPI1 SPI1} SPI1-IN SPI1-OUT SPI1-I/O** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi1-set-software-cs.fs|spi1-set-software-cs.fs]]|This shows how to use the built-in module and control the **CS** line by yourself - not by the module. | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi1-set-software-cs.fs|spi1-set-software-cs.fs]]|This shows how to use the built-in module and control the **CS** line by yourself - not by the module. | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi2-hard.fs|spi2-hard.fs]] |Will use the built-in module of the GD32VF103. It is here to show how to release the JTAG pins so that they could be used by interface SPI2. | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi2-hard.fs|spi2-hard.fs]] |Will use the built-in module of the GD32VF103. It is here to show how to release the JTAG pins so that they could be used by interface SPI2. | |
| |[[pfw:communication-protocols:spi:gd32vf:mecrisp-quintus:spi2-normalize.fs|spi2-normalize.fs]] |Translates the words **{SPI2 SPI2} SPI-IN2 SPI-OUT2 SPI-I/O2** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | | |[[https://github.com/project-forth-works/project-forth-works/blob/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus/spi2-normalize.fs|spi2-normalize.fs]] |Translates the words **{SPI2 SPI2} SPI-IN2 SPI-OUT2 SPI-I/O2** to **{SPI SPI} SPI-IN SPI-OUT SPI-I/O** | |
| |
| | |
| | View the complete [[https://github.com/project-forth-works/project-forth-works/tree/main/Communication-Protocols/SPI/GD32VF/mecrisp-quintus|repository on Github]]. |
| ==== Directories ==== | ==== Directories ==== |
| |
