Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Message Validity #2

Open
jamesmunns opened this issue Feb 4, 2020 · 0 comments
Open

Message Validity #2

jamesmunns opened this issue Feb 4, 2020 · 0 comments

Comments

@jamesmunns
Copy link
Owner

jamesmunns commented Feb 4, 2020 •
edited
Loading

We should do some kind of validity checking on messages as they are sent or when they arrive. At least once, I have seen u32::max reported as the work duration, though this may be a vintage-cli issue.

This could be done either by:

  • Implementing the CRC peripheral in hardware
  • Adding a software CRC mechanism
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jamesmunns