You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not all board offer the same user experience one might expect from a CircuitPython board.
So I was wondering if a proper way to indicate those potential problem or surprise could be defined. This idea came while playing with this board: #1114
Here are some "glitch":
JST SH vs JST PH: some early board do not that the QT connector, but the big one
Some board have a JST PH connector, but do not use Adafruit pinout
5V vs 3V: some board you have to select voltage or are 5V and you want to know
Some board with build in display
Some board do not have full native USB and don't have mass storage (C3 and ESP32 board)
Some board do not have double click reset (nor boot button) to get in UF2 upgrade mode, but require special software, or connecting two pin, or ...
Some board have Feather format, but do not respect the usual M4 pin numbering
When this is an Adafruit board, the caveats can be in the learn guide, but for non-Adafruit board the download page could help identify those small or bit annoyance (and make the benefit of a coherent ecosystem more obvious).
Those are little detail that make me prefer one board rather than another.
If I have already the board, having a reminder when I download a new firmware would help too.
What do you think?
The text was updated successfully, but these errors were encountered:
This would imply/dictate a 'standard' config - so that you could identify the differences.
Both Hardware and possibly software - on the software there already is a list of modules
for each board -
Not all board offer the same user experience one might expect from a CircuitPython board.
So I was wondering if a proper way to indicate those potential problem or surprise could be defined. This idea came while playing with this board: #1114
Here are some "glitch":
When this is an Adafruit board, the caveats can be in the learn guide, but for non-Adafruit board the download page could help identify those small or bit annoyance (and make the benefit of a coherent ecosystem more obvious).
Those are little detail that make me prefer one board rather than another.
If I have already the board, having a reminder when I download a new firmware would help too.
What do you think?
The text was updated successfully, but these errors were encountered: