comparison TCS211-fw-arch @ 14:f5ddeacbe744

TCS211-fw-arch: change from fc-target.cfg to fc-target.h
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 08 Apr 2019 08:23:41 +0000
parents 5de1f72ce941
children
comparison
equal deleted inserted replaced
13:8a3fd530a647 14:f5ddeacbe744
1469 trees for the magic. 1469 trees for the magic.
1470 1470
1471 The BOARD symbol is always fixed at 41 in all FreeCalypso firmwares, 1471 The BOARD symbol is always fixed at 41 in all FreeCalypso firmwares,
1472 corresponding to TI's D-Sample and Leonardo, and we use our own different 1472 corresponding to TI's D-Sample and Leonardo, and we use our own different
1473 mechanism to distinguish among our supported targets. The solution adopted in 1473 mechanism to distinguish among our supported targets. The solution adopted in
1474 Magnetite and Selenite is as follows: we are supplementing TI's *.cfg files 1474 Magnetite and Selenite is as follows: we are supplementing TI's *.cfg and
1475 with our own fc-target.cfg (included as #include "fc-target.cfg" or as 1475 rv_swe.h files with our own fc-target.h (included as #include "fc-target.h" or
1476 #include "config/fc-target.cfg" matching whatever existing TI code we are 1476 as #include "config/fc-target.h" matching whatever existing TI code we are
1477 gently extending), and this fc-target.cfg header is populated by the build 1477 gently extending), and this fc-target.h header is populated by the build system
1478 system by copying the appropriate targets/*.h header file. These targets/*.h 1478 by copying the appropriate targets/*.h header file. These targets/*.h
1479 header snippets define C preprocessor symbols of our own invention like 1479 header snippets define C preprocessor symbols of our own invention like
1480 CONFIG_TARGET_xxx, and whenever we need to know our target in C code, we 1480 CONFIG_TARGET_xxx, and whenever we need to know our target in C code, we
1481 #include "fc-target.cfg" and use #ifdef logic based on these preprocessor 1481 #include "fc-target.h" and use #ifdef logic based on these preprocessor symbols
1482 symbols of our own addition. 1482 of our own addition.
1483 1483
1484 RVTMUX debug and development interface 1484 RVTMUX debug and development interface
1485 ====================================== 1485 ======================================
1486 1486
1487 The Calypso chip has two UARTs, and TI's TCS211 firmware and its predecessors 1487 The Calypso chip has two UARTs, and TI's TCS211 firmware and its predecessors
1785 notifications such as incoming calls. The host utility for talking AT commands 1785 notifications such as incoming calls. The host utility for talking AT commands
1786 to a FreeCalypso GSM device via RVTMUX is fc-shell, described below. 1786 to a FreeCalypso GSM device via RVTMUX is fc-shell, described below.
1787 1787
1788 Now that we have built a proper FreeCalypso development board with two UARTs, 1788 Now that we have built a proper FreeCalypso development board with two UARTs,
1789 the use of this AT-over-RVTMUX hack is deprecated for general usage: this hack 1789 the use of this AT-over-RVTMUX hack is deprecated for general usage: this hack
1790 does not support any data services (CSD or GPRS), and even for SMS it is 1790 does not support any data services (CSD or GPRS), and even for SMS it was
1791 crippled because maximum-length messages cannot be sent in the more capable PDU 1791 crippled for a long time because maximum-length messages could not be sent in
1792 mode. However, it still comes in handy during certain casual testing sessions, 1792 the more capable PDU mode until our recent extension that works around this
1793 and it is required if one needs to run our FreeCalypso firmware on Mot C1xx or 1793 limitation. However, it still comes in handy during certain casual testing
1794 Pirelli DP-L10 hardware. 1794 sessions, and it is required if one needs to run our FreeCalypso firmware on
1795 Mot C1xx or Pirelli DP-L10 hardware.
1795 1796
1796 FC host tools for talking to firmwares via RVTMUX 1797 FC host tools for talking to firmwares via RVTMUX
1797 ================================================= 1798 =================================================
1798 1799
1799 The fundamental tool for talking to running firmwares via RVTMUX is a program 1800 The fundamental tool for talking to running firmwares via RVTMUX is a program