1 Jan
2013
1 Jan
'13
6:34 p.m.
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