Skip to content
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.

ATECC108 Chip stopped working after personalizing chip #16

Open
mutexlocker opened this issue Aug 26, 2016 · 1 comment
Open

ATECC108 Chip stopped working after personalizing chip #16

mutexlocker opened this issue Aug 26, 2016 · 1 comment

Comments

@mutexlocker
Copy link

Hello,
I have successfully compiled EClet on my raspberry pi .
I have soldered ATECC108 to my own PCB and i don’t use any development board, after connecting i2c pins and 3.3v and GND to chip i was able to find the chip at address 60 using i2cdetect -y 1,then i ran sudo ./eclet state and got "Factory" as response. But after that all commands got stuck in terminal and nothing happens sudo ./eclet personalize and sudo ./eclet random returns nothing and also i2cdetect -y 1 command is not finding the chip anymore.I think its burned i have more chips i can test but i just want to know your opinion why the chip is not recognized anymore after running state command.
I can see in your PCB you have used 1uf cap between GND and Vcc do you think it has something to do with that ?

@jbdatko
Copy link
Member

jbdatko commented Aug 30, 2016

I've used it w/o the bypass cap before. It's good practice, but unless you have some really dirty power, you should be fine.

Try running it with the --verbose or -v flag--it should give you more details about what's going on at the i2c level.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants