Skip to first unread message
Charles
Oct 4, 2016, 9:16:29 AM10/4/16
to BeagleBoard
Hi, I'm having some issue trying to talk to a chip over I2C.
The chip in question is the ATAES132 (https://cdn.sparkfun.com/datasheets/Dev/Beagle/Atmel-8760-CryptoAuth-ATAES132-Datasheet.pdf) on the cryptocape. Up to yesterday I could send command and read response packets from the Command memory register, but today the chip doesn't appear anymore on the I2C bus.
It was showing at the address 0x50. Trying to read from this slave address now gives me random bytes. Anyone has an idea on how to fix this ? Did I brick the chip ?
The chip in question is the ATAES132 (https://cdn.sparkfun.com/datasheets/Dev/Beagle/Atmel-8760-CryptoAuth-ATAES132-Datasheet.pdf) on the cryptocape. Up to yesterday I could send command and read response packets from the Command memory register, but today the chip doesn't appear anymore on the I2C bus.
root@beaglebone:~# i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: 60 -- -- -- 64 -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- It was showing at the address 0x50. Trying to read from this slave address now gives me random bytes. Anyone has an idea on how to fix this ? Did I brick the chip ?
Reply all
Reply to author
Forward
0 new messages