[riot-notifications] [RIOT-OS/RIOT] Wrong I2C address for ATECC (cryptoauthlib) (#14001)

Philipp-Alexander Blum notifications at github.com
Sat May 2 13:04:12 CEST 2020


> The ATECC508A datasheet (Sec. 2.2 EEPROM Configuration Zone, Table 2-5 Byte 16 ) clearly states the default I2C address `0xC0` which can be "modified from default by writing a new value into the configuration zone". The ATECC608A is designed to be fully compatible with the ATECC508A with a couple of additions. Regarding I2C, that is "Programmable I 2 C address after data (secret) zone lock". Some ideas:
> 
>     * Connect to an other platform. Maybe there is something wrong in the i2c driver on that platform.
> 
>     * Try an I2C scanner to find the correct I2C address (there is a shell command in RIOT that I just found).
> 
>     * There is a "cryptoauth" shell command as well, which reads and dumps the configuration zone (depends on working communication obviously).
> 
>     * Which device are you actually using? CryptoAuth Xplained Pro shield might need some jumpering.
> 
> 
> @Einhornhool other ideas?

I also thought about the platform. The nRF52 uses this dynamic pin configurations as I remember. So, it is possible to have some kind of bug in there. 
What is the shell command to find the I2C address?
I just use the ATECC608A with the I2C on the nRF52. I just soldered it and connected it on a breakout board. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/14001#issuecomment-622935957
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200502/9e235b1f/attachment.htm>


More information about the notifications mailing list