search

ghi-electronics / TinyCLR-Drivers

Drivers for sensors/devices to be used with TinyCLR OS
Apache License 2.0
6 stars 9 forks source link

Firmware versioning mismatch is too hard to diagnose #123

Open martincalsyn opened 3 years ago

martincalsyn commented 3 years ago

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 commented 3 years ago

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

User can check firmware version before continue.

Palomino34 commented 3 years ago

Move to backlog

Palomino34 commented 3 years ago

Done from RC1.

Palomino34 commented 3 years ago

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