FreeCalypso > hg > freecalypso-docs
diff 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 |
line wrap: on
line diff
--- a/TCS211-fw-arch Thu Mar 28 16:49:38 2019 +0000 +++ b/TCS211-fw-arch Mon Apr 08 08:23:41 2019 +0000 @@ -1471,15 +1471,15 @@ The BOARD symbol is always fixed at 41 in all FreeCalypso firmwares, corresponding to TI's D-Sample and Leonardo, and we use our own different mechanism to distinguish among our supported targets. The solution adopted in -Magnetite and Selenite is as follows: we are supplementing TI's *.cfg files -with our own fc-target.cfg (included as #include "fc-target.cfg" or as -#include "config/fc-target.cfg" matching whatever existing TI code we are -gently extending), and this fc-target.cfg header is populated by the build -system by copying the appropriate targets/*.h header file. These targets/*.h +Magnetite and Selenite is as follows: we are supplementing TI's *.cfg and +rv_swe.h files with our own fc-target.h (included as #include "fc-target.h" or +as #include "config/fc-target.h" matching whatever existing TI code we are +gently extending), and this fc-target.h header is populated by the build system +by copying the appropriate targets/*.h header file. These targets/*.h header snippets define C preprocessor symbols of our own invention like CONFIG_TARGET_xxx, and whenever we need to know our target in C code, we -#include "fc-target.cfg" and use #ifdef logic based on these preprocessor -symbols of our own addition. +#include "fc-target.h" and use #ifdef logic based on these preprocessor symbols +of our own addition. RVTMUX debug and development interface ====================================== @@ -1787,11 +1787,12 @@ Now that we have built a proper FreeCalypso development board with two UARTs, the use of this AT-over-RVTMUX hack is deprecated for general usage: this hack -does not support any data services (CSD or GPRS), and even for SMS it is -crippled because maximum-length messages cannot be sent in the more capable PDU -mode. However, it still comes in handy during certain casual testing sessions, -and it is required if one needs to run our FreeCalypso firmware on Mot C1xx or -Pirelli DP-L10 hardware. +does not support any data services (CSD or GPRS), and even for SMS it was +crippled for a long time because maximum-length messages could not be sent in +the more capable PDU mode until our recent extension that works around this +limitation. However, it still comes in handy during certain casual testing +sessions, and it is required if one needs to run our FreeCalypso firmware on +Mot C1xx or Pirelli DP-L10 hardware. FC host tools for talking to firmwares via RVTMUX =================================================