-
Notifications
You must be signed in to change notification settings - Fork 34
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
Expand your library in order for it to could be used with esp8266 #26
Comments
One of the idea about our library is to write a second working modality that will use digitalwrite() instead of registry manipulation. Expecially on 32bit world, that normally have a big cpu freq, the speed problem will non be a problem, we can contunue to use the lib like now on 8 bit and with the new modality on 32bit cpu. |
Thanks for your answer, let me know if i can Help you in something |
My idea was to use the low-level functions of the OneWire library for other processors. However, I did some tests with the 48MHz SAMD21 processor (Arduino Zero, M0, and many MKR boards) and the digitalWrite() and digitalRead() seems fast enough for those. Using the normal Arduino functions as a fallback might be good enough for most faster boards. It could be something like this:
The ::setClock() needs a better formula, I did some tests with this:
|
Your idea looks nice @Koepel, now i am busy but maybe in one or two weeks i could Help you. If i do this, I will make you a pull request. Thanks for sharing |
In this issue #10 you said that the esp8266 Wire library is already a software library. This is true, but it isn't able to create multiple i2c buses. You referenced another library, which works fine but it is not compatible with Wire original library, so if you use a device library which receives a pointer to a Wire object, you must modify the library (something i already did). Because of this, I think that if you improve your library in order for it to be used with esp8266, it will be the BEST SoftwareWire library. I hope you will think about it. I will be waiting for your answer
The text was updated successfully, but these errors were encountered: