FreeCalypso > hg > fc-magnetite
view doc/Calypso-version-override @ 673:62a5285e014a
Lorekeeping: allow tpudrv-leonardo.lib on Leonardo/Tango
Back in 2015 the Mother's idea was to produce a FreeCalypso development
board that would be a clone of TI Leonardo, including the original
quadband RFFE; one major additional stipulation was that this board
needed to be able to run original unmodified TCS211-20070608 firmware
with all blobs intact, with only minimal binary patches to main.lib
and tpudrv.lib. The necessary patched libs were produced at that time
in the tcs211-patches repository.
That plan was changed and we produced FCDEV3B instead, with Openmoko's
triband RFFE instead of Leonardo quadband, but when FC Magnetite started
in 2016, a TPUDRV_blob= provision was still made, allowing the possibility
of patching OM's tpudrv.lib for a restored Leonardo RFFE.
Now in 2020 we have FC Tango which is essentially a verbatim clone of
Leonardo core, including the original quadband RFFE. We have also
deblobbed our firmware so much that we have absolutely no real need
for a blob version of tpudrv.lib - but I thought it would be neat to put
the ancient TPUDRV_blob= mechanism (classic config) to its originally
intended use, just for the heck of it.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Fri, 29 May 2020 03:55:36 +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.