Skip to content

"Keygen for v2.1s" doesn't work #105

Closed Answered by jopl
jopl asked this question in Q&A
Feb 2, 2024 · 5 comments · 1 reply
Discussion options

You must be logged in to vote

Finally I found the reason ... the EEPROM has to be 24C08 (tested) or 24C16 (not tested). Otherwise the firmware is not able to communicate with the EEPROM chip. Despite the fact I am not using the original firmware (custom FW is more stable and can regulate temperature more accurately - thanks to David), I was trying to uncover the issue. From EEPROM 24C32 (which I had populated on the board) , there is change in communication protocol.
regards, Josef.

Replies: 5 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@deividAlfa
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by jopl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants