view doc/Freerunner-Howto @ 672:3e4f212e5d49

targets/*.conf cleanup: remove unnecessary TPUDRV_blob= lines MAIN_blob= and/or TPUDRV_blob= may be *optionally* defined in targets/*.conf files; if either variable is defined, it means that using the specified version of the blob library is allowed on this target, albeit likely suboptimal; if the variable is not defined, then using a blob is not an option and compilation from source is required for this component. MAIN_blob= and TPUDRV_blob= are now defaulted to empty in configure.sh, thus there is no need to explicitly specify that using a blob is not a valid option.
author Mychaela Falconia <falcon@freecalypso.org>
date Fri, 29 May 2020 03:11:16 +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.