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

Firmware versioning mismatch is too hard to diagnose #123

Open
martincalsyn opened this issue Jan 4, 2021 · 4 comments
Open

Firmware versioning mismatch is too hard to diagnose #123

martincalsyn opened this issue Jan 4, 2021 · 4 comments
Milestone
Backlog

Comments

@martincalsyn
Copy link

Using the ATWinC driver (and likely others that are dependent on firmware), if the firmware is out of sync, you just get an "Invalid Operation" exception. There's no indication as to whether this is really an invalid operation (program error; driver in a bad state; etc) or a firmware mismatch.

The init functionality for every driver should check to make sure that the driver and native firmware are in sync, and if not, should report that. This could solved by just adding a message to the InvalidOperationException that identifies firmware mismatches.
@Palomino34
Copy link
Contributor

We open for user to use a compatible firmware, but not recommended.

User can check firmware version before continue.

@Palomino34 Palomino34 added this to the Backlog milestone Feb 19, 2021
@Palomino34 Palomino34 reopened this Feb 19, 2021
@Palomino34
Copy link
Contributor

Move to backlog

@Palomino34
Copy link
Contributor

Done from RC1.

@Palomino34
Copy link
Contributor

Reopen. My mistake. This is Wifi, not TinyCLR.

@Palomino34 Palomino34 reopened this May 28, 2021
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
Backlog
Development

No branches or pull requests
2 participants
@martincalsyn @Palomino34