You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason I can only switch really fast between 8 frequencies. If I add 9 frequencies and more, the switching time becomes very long and I can't accurately predict the time to get samples.
The first 8 fastlock profiles are preloaded onto the AD9361. Subsequent profiles are stored in Nios memory. After the first 8 profiles are iterated through, the Nios core hot-loads the ones in Nios memory to the AD9361 which takes just under millisecond per profile.
@rthomp10
Can you tell me how loading from Nios works? As I understand, I can't set bladerf_schedule_retune for different quick_tune and different timestamp but with the same profile index, right? It seems like the new bladerf_schedule_retune overwrites the quick tuning profile in AD9361.
Also, according to my tests, switching takes from 5 to 6 milliseconds (my delay is calculated as await_time = (sample_rate // 1000) * 6
For some reason, even if I call bladerf_schedule_retune much earlier, I still have to wait for these 6 milliseconds, although I expected that the switching time would be lower, since it seems that the data from quick_tune is written to the AD9361 immediately after calling bladerf_schedule_retune.
I implemented the sweep mode and noticed that with a delay of less than 6 milliseconds, I can get samples from the old frequency range.
For some reason I can only switch really fast between 8 frequencies. If I add 9 frequencies and more, the switching time becomes very long and I can't accurately predict the time to get samples.
Here are the logs for 9 frequency switches:
And here is a really fast switching but with 8 frequency switches
The text was updated successfully, but these errors were encountered: