view doc/Freerunner-Howto @ 598:717ed17d82c6

aci3 vocoder control revamped, AT@VSEL now works as it should The vocoder control code (hl_audio_drv.c) that came with the TCS3 version of ACI was totally broken in the Calypso config (VOCODER_FUNC_INTERFACE) and worked in the standard analog voice environment only by luck. This code has now been rewritten to work correctly with our Calypso platform and TCS211 L1, and our new AT@VSEL mechanism (automatic enabling and disabling of MCSI voice path as the modem enters and exits the voice call state) now also works as designed.
author Mychaela Falconia <falcon@freecalypso.org>
date Wed, 27 Mar 2019 23:44:35 +0000
parents c9a65db8be4a
children
line wrap: on
line source

The latest official firmware for Openmoko Neo1973 and Neo FreeRunner Calypso
modems is moko13 as of this writing; moko13 is FreeCalypso Magnetite Hg
changeset 286:840113655bbf built for the gtamodem target in the l1reconst
configuration.  There have been many changes in FC Magnetite since then, but
few of them affect the l1reconst config on the gtamodem target in any
noticeable way.  The few noticeable post-moko13 changes which we do have in our
current l1reconst code are not deemed important enough to justify making
another formal release for a no-longer-made hardware platform that no longer
has any real user community either.

However, we also have the new TCS2/TCS3 hybrid config in which the old version
of the G23M protocol stack from Openmoko (binary libs only, no source) has been
replaced with a newer version from TI's TCS3/LoCosto program, and this new
version is full source.  This hybrid firmware has now reached the state where
it is ready to be exercised by adventurous beta users in real-life usage.

The new hybrid fw for the gtamodem target can be built as follows:

./configure.sh gtamodem hybrid
cd build-gtamodem-hybrid; make

Then after enduring the very slow build, you can flash it with fc-loadtool:

loadtool> flash erase 0 0x250000
loadtool> flash program-bin 0 fwimage.bin

If you are brave enough to do the above, please let us know how this new modem
firmware fares when driven by QtMoko or SHR on the AP - it would definitely be
an adventure!  We would be most interested in working with developers or
maintainers of specific AP software components that are directly responsible
for talking AT commands to the modem, if there are any such developers or
maintainers still around.