You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the esp-open-rtos project has a lot of component libraries that could be used in several SDKs as well as esp32.
Would it be a good idea to create a standard I2C / SPI / PWM / GPIO / I2S / ... interface ?
a component that would be called by each library. A large part of extras folder will be portable. (I think especially to sensors libraries).
Would the idea of creating a separate repository for these modules be a good idea too?
I see that already libraries are thought to be portable on esp32. Myself, I carry some libraries from here.
The text was updated successfully, but these errors were encountered:
My 2 cents : Nice idea, the way I approached it was by creating in C++ some abstract base classes that on each platform differ in implementation. https://github.com/vortex314/Vertx-ESP8266/blob/master/Hardware.h
On an hardware level I standardized on UEXT connectors , so the sensors/ drivers are interchangeable between ESP8266 and ESP32 ( theoretically ) Still work in evolution.
On an ESP32 I have 3 x UEXT connectors and on an ESP8266 1x UEXT.
The UEXT 1-> 3 is reflected by the Connector class which can provide Uart,SPI,.. classes as a factory.
the esp-open-rtos project has a lot of component libraries that could be used in several SDKs as well as esp32.
Would it be a good idea to create a standard I2C / SPI / PWM / GPIO / I2S / ... interface ?
a component that would be called by each library. A large part of extras folder will be portable. (I think especially to sensors libraries).
Would the idea of creating a separate repository for these modules be a good idea too?
I see that already libraries are thought to be portable on esp32. Myself, I carry some libraries from here.
The text was updated successfully, but these errors were encountered: