Possible fix for problem -- "l1ctl.c:114 FBSB RESP: result=255"

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/.

Sylvain Munaut 246tnt at gmail.com
Tue Jan 1 17:34:43 UTC 2013


> Can Holger or Harald who have written ccch_scan please confirm if this is
> the correct way to fix the problem or if there is better solution? Can you
> please also insert the update in the ccch_scan code in the burst_ind branch
> so that others can benefit?

It's not a correct fix, that's just a work around that basically says
"Try to sync endlessly until it works" ...

Finding out _why_ the sync failed in the first place is the correct
fix, which also would most likely fix the border case where you get
bits errors (that case is triggered when the firmware thinks it has
successfully synced but in fact didn't).

Cheers,

    Sylvain




More information about the baseband-devel mailing list