Skip to content

Fix timegate_csts to process 96-bit timestamps per protocol spec

Aaron Olivarez requested to merge 3080-timegate_csts-enters-an-error-state-upon-recieving-a-proper-csts-timestamp into develop

What this MR does / why we need it:

Per the CSTS (complex short time sample) protocol timestamps are now 96-bit vs 64-bit in CSWM (complex short time sampled). When feeding the component a 96-bit timestamp the timegate component would enter an error state and lock-up from passing data through at the appropriate time.

This MR updates the timegate_csts component to process the wider timestamps.

Steps to complete before submitting MR:

  • I have read Contribution guidelines

  • I have ensured I have a changelog written in the imperative form that is meaningful and accurately summarizes the work done

  • I have added the release notes label if applicable (more information below)

  • I have ensured the workflow labels are up to date and will continue to do so up until this work is merged into develop

  • I have added a category, type, and target release label along with all other labels as need be

  • My branch is up to date with develop. If it is not, then I have ensured my work does not conflict with other work

  • I agree my bugfix MR does not include new features/enhancements

  • I represent that bugfixes have been locally tested against the most recent major.minor release in which the bug exists

  • (REVIEWER ONLY) I have thoroughly gone through the above steps to ensure that they have been followed

Release Notes

N/A

Changelog

  • bug(tools): fix timegate_csts to accept CSTS timestamps

Which issue(s) this MR closes

Closes #3080 (closed)

Edited by Connor Lathrop

Merge request reports