dearsky/pico-hsm
1
0
Fork 0
Code Issues 17 Pull Requests 4 Actions Packages Projects Releases 26 Wiki Activity

RP2350 HSM Serial #97

New Issue
Closed
opened 2025-05-26 15:05:43 +08:00 by IsayIsee · 1 comment
IsayIsee commented 2025-05-26 15:05:43 +08:00 (Migrated from https://github.com/polhenarejos/pico-hsm)
Copy Link

#56 mentioned that the RP2350 has a unique SN (serial number), and the chipid field can also be viewed via picotool info -d. If it were possible to generate unique HSM serial numbers (instead of the uniform ESPICOHSMTR) based on such chips with unique identifiers, it would provide significant value for multi-device differentiation scenarios . Would it be feasible to implement this feature request?

#56 mentioned that the RP2350 has a unique SN (serial number), and the chipid field can also be viewed via picotool info -d. If it were possible to generate unique HSM serial numbers (instead of the uniform ESPICOHSMTR) based on such chips with unique identifiers, it would provide significant value for multi-device differentiation scenarios . Would it be feasible to implement this feature request?
👍 1
polhenarejos commented 2025-12-17 21:14:00 +08:00 (Migrated from https://github.com/polhenarejos/pico-hsm)
Copy Link

I implemented with in a different way. Following the CVC specifications, only 5 digits AZ09 are allowed. With few of thousands of devices, the collisions start appearing with notably probability. The CVC serial is an administrative number that might be reshared if the numering is exhausted. To solve this, I made a database with a relationship of CVC Serial <-> Pico serial. The result is a unique CVC serial for that device (note the collisions still happen).

I implemented with in a different way. Following the CVC specifications, only 5 digits AZ09 are allowed. With few of thousands of devices, the collisions start appearing with notably probability. The CVC serial is an administrative number that might be reshared if the numering is exhausted. To solve this, I made a database with a relationship of CVC Serial <-> Pico serial. The result is a unique CVC serial for that device (note the collisions still happen).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 enhancement
New feature or request
 good first issue
Good for newcomers
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 invalid
This doesn't seem right
 question
Further information is requested
 question
Further information is requested
 wontfix
This will not be worked on
 wontfix
This will not be worked on
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-hsm#97
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?