FreeCalypso > hg > freecalypso-docs

comparison Tango-pinmux @ 71:bf7a0c2b2b50

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Tango-pinmux: add programming instructions
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 17 Jul 2021 17:19:00 +0000
parents 3365d51773c5
children
comparison
equal deleted inserted replaced
70:3365d51773c5 71:bf7a0c2b2b50
118 118
119 Any GPIO that is configured as an input can be read with AT+IOR, and any GPIO 119 Any GPIO that is configured as an input can be read with AT+IOR, and any GPIO
120 that is configured as a generic (not built-in function) output can be set with 120 that is configured as a generic (not built-in function) output can be set with
121 AT+IOW. 121 AT+IOW.
122 122
123 Programming /etc/tango-pinmux
124 =============================
125
126 To program the pinmux config file on a Tango module running any of our official
127 FreeCalypso firmware versions, you will need to use FC host tools. Connect to
128 the RVTMUX debug trace and control interface (second UART) via rvinterf and
129 execute the following command in fc-fsio:
130
131 fwrite /etc/tango-pinmux hex "xx xx xx xx"
132
133 Replace xx placeholders inside the double quotes with the 4 hex bytes to be
134 programmed; the double quotes are required.
135
123 Other GPIO pins 136 Other GPIO pins
124 =============== 137 ===============
125 138
126 Calypso pins GPIO0, TSPDI/GPIO4, BCLKX/GPIO6, MCUEN1/GPIO8 and MCUEN2/GPIO13 139 Calypso pins GPIO0, TSPDI/GPIO4, BCLKX/GPIO6, MCUEN1/GPIO8 and MCUEN2/GPIO13
127 are not brought out externally on Tango modules, thus they don't need to be 140 are not brought out externally on Tango modules, thus they don't need to be