-
Notifications
You must be signed in to change notification settings - Fork 13
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
Is ATECC608A-TNGTLSU compliant ? #5
Comments
Judging by the datasheet: It looks like it has an ECC private key in slot 0 and you can optionally put ECC private keys in slots 2, 3 and 4 as well... So in principle it should work, but you should get some and test it before committing to a big order. Also note this part of the datasheet - the default 7 bit i2c address is 0x35 which is different to the non programmed one (which uses 0x60 - or 0xC0 for a write operation with the R/W bit set to 0):
Also, note that you may need to modify gateway-mfr-rs to work with this chip as it may give errors when trying to configure/lock the chip and other standard routines it uses on the bare chip. |
I use 0x35 ATECC608B, how to change script to 0x35? |
@Hccd2022 You would use gateway-mfr-rs and pass in the correct device: https://github.com/helium/gateway-mfr-rs#addressing
The address 96 corresponds to 0x60 |
Is ATECC608A-TNGTLSU compliant ?
The text was updated successfully, but these errors were encountered: