-
Notifications
You must be signed in to change notification settings - Fork 841
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.
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
Get an unique device ID #6
Comments
All RP2040s are identical, and there's no persistent state of any kind on-device, so there's no UID for RP2040s. Flash chips tend to have a unique identifier (usually the 4Bh command), so that would get you a per-board ID on Pico. There's some careful footwork involved in sending serial commands to the flash chip, owing to the fact you are also executing code from it, so we can look at adding a general interface to the |
unique id is the basic but necessary feature for all MCU ... |
Yes, it's also a standard feature on the flash chips we boot from, which have a 1:1 association with the MCU. Small OTP stores take up a lot of space on 40nm (it's the programming hardware, not the storage) so why make people pay for a duplicate feature on their silicon? We do need to add an example though, since as you say it needs to be something that's trivial to get at in user software. I'll get on that. |
Is the serial number the device presents to the USB host when running the bootloader also coming from the flash?
|
I have a same SerialNumber in my dmesg :( |
This is the firmware revision number. It will be the same on all chips. |
merged into develop |
Hello,
is there a way to obtain a unique identifier for each device? Something like MAC address on other device Who has a network card ?
The text was updated successfully, but these errors were encountered: