-
Notifications
You must be signed in to change notification settings - Fork 33
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
Why is supported chip size floored at 64Kbits? #6
Comments
I guess you're talking about EEPROMs, but the comment below is true for all types. The list of supported chips represents chips tested by myself or others. It is very possible that other chips will work as there is a good deal of standardisation, but the only way to be sure is to check the datasheet of the chip you intend to use. If you are successful in using another chip, please report it and I will update the docs. |
Yes sorry, I forgot to mention it was about EEPROMS. I've successfully tested the library with a CAT24C256LI-G chip. I currently do not have smaller chips to test with, although I might in the future. I was mainly curious if there was a technical limitation, as the library currently raises an exception if the provided chip size doesn't match one of the existing constants. Maybe instead of raising an exception, it could simply display a warning? |
Yes, I guess I was being overly restrictive. There is more standardisation between chips than I realised when I started out. I'll make this change in due course. Thanks for testing and reporting back. |
I have made this change for I2C and SPI EEPROMs, also updated the README to report your success with CAT24C256LI-G. Please report success with other devices by an issue or a README.md PR. |
Hi, is there a reason why the list of available chip sizes is floored at 64Kbits? Wouldn't it work with smaller sizes?
The text was updated successfully, but these errors were encountered: