Skip to content
This repository has been archived by the owner on Sep 27, 2024. It is now read-only.

[BPMApp] Not checking if acquisition is stalled due to too fast data rates #30

Open
lerwys opened this issue Mar 10, 2018 · 0 comments
Open
Assignees
Labels

Comments

@lerwys
Copy link
Contributor

lerwys commented Mar 10, 2018

Problem: By changing the ADC clock frequency one can be in a condition where the maximum DDR3 memory bandwidth is exceeded. At least a flag indicating this has happened with the current acquisition must be created.

Solution: There is already a flag in the lnls-bpm/bpm-gw gateware and lnls-bpm/halcs software that can be used for this., called FC_FULL status field in the acquisition status register.

This is related to issue #28.

@lerwys lerwys added the bug label Mar 10, 2018
@lerwys lerwys self-assigned this Mar 10, 2018
@lerwys lerwys changed the title [BPMApp] No checking if acquisition is stalled due to too dast data rates [BPMApp] Not checking if acquisition is stalled due to too dast data rates Mar 10, 2018
@lerwys lerwys changed the title [BPMApp] Not checking if acquisition is stalled due to too dast data rates [BPMApp] Not checking if acquisition is stalled due to too fast data rates Mar 10, 2018
lerwys added a commit to lnls-dig/halcs that referenced this issue Apr 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant