-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timestamp issue #228
Comments
Passing NULL as metadata gives the same result as passing metadata with: |
Given the following conditions:
I make a call to LMS_StopStream, then I make some changes to the data source, then I call LMS_StartStream. What I observe is that data is only transmitted when I perform the LMS_StopStream & LMS_StartStream twice. Issue #219 was the first workaround I found that made data transmit after every call to LMS_StartStream instead of every other. |
Could you provide a more detailed explanation of your problem? What board are you using (LimeSDR-Mini or LimeSDR-USB)? Are you using Tx only or both Tx and Rx?
|
I updated LimeSuite to gitrev: 18d2fa (this is LimeSuite 18.10), and I got the same results as I did with the older version of LimeSuite. I should also say that I tested with a LimeSDR-Mini. |
So the issue only appears on Raspberry Pi 3 and it works fine on PC with Intel i5 CPU? |
|
I updated, so I'm posted the updated software: |
Do you have any idea how this issue will be resolved for the limenet-micro? |
Issue #219 was closed because SYNCH_DIS (bit 9) in DIQ interface control (0x0008) should always be 0 (Enable packets synchronization using timestamps).
Because the FPGA must always use the time stamp, LMS_RecvStream and LMS_SendStream should return an error if meta is ever NULL because metadata.timestamp = 0 is not a valid condition. As found in src/API/lms7_api.cpp.
The text was updated successfully, but these errors were encountered: