FreeCalypso > hg > fc-magnetite
view doc/Calypso-version-override @ 685:3fb7384e820d
tpudrv12.h: FCDEV3B goes back to being itself
A while back we had the idea of a FreeCalypso modem family whereby our
current fcdev3b target would some day morph into fcmodem, with multiple
FC modem family products, potentially either triband or quadband, being
firmware-compatible with each other and with our original FCDEV3B. But
in light of the discovery of Tango modules that earlier idea is now being
withdrawn: instead the already existing Tango hw is being adopted into
our FreeCalypso family.
Tango cannot be firmware-compatible with triband OM/FCDEV3B targets
because the original quadband RFFE on Tango modules is wired in TI's
original Leonardo arrangement. Because this Leonardo/Tango way is now
becoming the official FreeCalypso way of driving quadband RFFEs thanks
to the adoption of Tango into our FC family, our earlier idea of
extending FIC's triband RFFE control signals with TSPACT5 no longer makes
much sense - we will probably never produce any new hardware with that
once-proposed arrangement. Therefore, that triband-or-quadband FCFAM
provision is being removed from the code base, and FCDEV3B goes back to
being treated the same way as CONFIG_TARGET_GTAMODEM for RFFE control
purposes.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Thu, 24 Sep 2020 21:03:08 +0000 |
| parents | 9f19cc5e46e8 |
| children |
line wrap: on
line source
TI's TCS211 program supported 3 different Calypso silicon versions on their D-Sample and Leonardo boards: C05B (CHIPSET 8, DSP 33), early C035 (CHIPSET 10, DSP 34) and final C035 (CHIPSET 10, DSP 36). In FreeCalypso we generally work only with the last chipset (final C035), but we also support the two earlier ones to a good extent. C05B has been partially exercised on the Mother's D-Sample board (non-functional Clara RF, no genuine tpudrv10.c source and too many unknowns, but at least some of the DSP-based audio services work), whereas Calypso C035 with DSP 34 has been tested and found to work on a specially modified FCDEV3B board - see the FCDEV3B-751774 article. All 3 Calypso chip versions in question are footprint-compatible, i.e., they can all be populated onto the same PCB. Changing between C05 and C035 requires changing the VLRTC strapping on the Iota companion chip, thus not all boards can support Calypso C05 (the newer ones are C035 only), but one can always populate either early C035 (DSP 34) or final C035 (DSP 36) on the same PCB. TI's own D-Sample and Leonardo development boards have most certainly been made with all 3 Calypso silicon versions: D-Sample appears to support both C05 and C035 on the same PCB; the schematics we have for Leonardo show fixed VLRTC strapping for C035, but there also existed an earlier Leonardo version with Calypso C05B. Our own FCDEV3B also has fixed C035-only VLRTC strapping, our regular boards have final C035 chips on them, but we have put a D751774AGHH chip on one experimental board for DSP 34 testing. In the case of target boards that can have different Calypso chip versions populated on them, we want to be able to target all of them without creating a configuration explosion. The implemented solution is that you can pass a target argument to the ./configure.sh script of the following form: dsample-c05b dsample-dsp34 dsample-dsp36 leonardo-c05b leonardo-dsp34 leonardo-dsp36 fcdev3b-dsp34 Our configure.sh script recognizes the hyphen as indicating this construct; the word before the hyphen must be the conventional target name, and the word after the hyphen needs to be one of c05b, dsp34 or dsp36, corresponding to the three supported Calypso silicon versions.