Updated Guide – Why #CircuitPython wants unique identifiers for every board
Unique identifiers are important. That’s why Jeff Epler took the time to not only explain the reasons why we’re a stickler about them in CircuitPython, but also where and how to get the right identifier (Product ID or Creation ID) for your product that will run CircuitPython! Check the info out in the new Frequently Asked Questions page of the guide “How to Add a New Board to CircuitPython“.
With a few legacy exceptions, each different hardware product that runs CircuitPython needs a different unique identifier. Furthermore, if a piece of hardware has different operating modes (such as UF2 bootloader, Arduino, CircuitPython), each mode should have a different unique ID.
Here are just a few of the things that need unique identifiers to work properly:
Applying correct firmware updates
Device detection in Arduino
Using correct operating system drivers
Allowing device access on ChromeOS
Managing device permissions with udev on Linux
[Photo credit: USB Connectors by GeroZ at de.wikipedia, CC-BY-SA 3.0]
Have an amazing project to share? The Electronics Show and Tell is every Wednesday at 7:30pm ET! To join, head over to YouTube and check out the show’s live chat and our Discord!
Python for Microcontrollers – Adafruit Daily — Python on Microcontrollers Newsletter: A New Arduino MicroPython Package Manager, How-Tos and Much More! #CircuitPython #Python #micropython @ThePSF @Raspberry_Pi
EYE on NPI – Adafruit Daily — EYE on NPI Maxim’s Himalaya uSLIC Step-Down Power Module #EyeOnNPI @maximintegrated @digikey
