This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi!
I've done a day of bugfixing today, mostly regarding the timing and
sequencing of the TPU window during receive (and transmit).
The biggest new feature is the #define TPU_DEBUG which will transfer the
content of the TPU RAM to the host PC every time tpu_enable(1) is called.
There's a TPU debugger (tpu_debug.c) as part of osmocon which receives,
decodes and prints the TPU instructions. This way you can clearly see
the exact sequence (and timing) of the commands that are executed by
the TPU.
What turned out to be the major problem that I was hunting most of the
day: Whe first did the downlink calibration (BLDCAL), then waited for
a specific time, and then enabled the downlink path (BDLENA).
This worked fine so far. I then added code to disable the TRF6151 after
the downlink path is closed (twl3025_downlink(0)). Suddenly not a single
burst was received anymore.
Now the sequence of events seems correct, at least in the little testing
I did.
Regards,
Harald
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)