--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/Calypso-version-override	Mon Oct 07 03:59:14 2019 +0000
@@ -0,0 +1,39 @@
+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 would like to support the two
+earlier ones as well, if possible.  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 the early C035 version with DSP 34 has not been
+tested at all yet.
+
+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 should be able to build
+some experimental boards with an early C035 variant (751774) 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.

--- a/doc/D-Sample	Mon Oct 07 02:09:53 2019 +0000
+++ b/doc/D-Sample	Mon Oct 07 03:59:14 2019 +0000
@@ -114,10 +114,9 @@
 
 Because we only have one D-Sample board and we have no idea whether or not there
 are any other DS boards out there in the world (ours may well be the world's
-last remaining unit), our current build system is set up to target only one
-D-Sample version, the one we've got: CHIPSET=8, DSP=33 for Calypso C05 rev B
-silicon.  If anyone else in the world has another D-Sample board and it has a
-different Calypso chip version on it, if you would like to run our FC Magnetite
-firmware on it, you will need to edit the targets/dsample.conf source file
-(it's a Bourne shell script fragment sourced by configure.sh) and set the
-CHIPSET and DSP settings correctly for your Calypso chip version.
+last remaining unit), our dsample build target in FC Magnetite is set up for
+Calypso chip version c05b by default, which is the version we got.  If anyone
+else in the world has another D-Sample board and it has a different Calypso
+chip version on it, if you would like to run our FC Magnetite firmware on it,
+you will need to follow the instructions in the Calypso-version-override
+article.