-
non generic esp32 devices like the m5stack core2 have a specific wiring to peripheral chips and the pin assignments of theses chips are also specific to this design. i don't see how to implement the drivers in a generic way. Also these devices sometimes use 2 different hardware spi, i2c and i2s busses. but since we mostly need a specific driver for each device and it makes no sense to select different GPIOs as in generic devices we could also hardcode the driver with a specific device template, only leaving not used pins open for selecting GPIO functions. these devices always need a self compile and they should be ready for use directly after compiling with all pins already assigned. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
I have a device with only some of the components used in m5stack and some of the components used in another device but on different gpio's but I cannot use the available drivers correctly if they/re hardcoded and/or implemented all in one. While true that almost every device will probably need a self compile with specific options this is what tasmota was at the beginning with modules but as the gamut of available devices grows larger you run into the same problem of trying to add every device into the code and maintain it at the same time |
Beta Was this translation helpful? Give feedback.
-
ok in a first step we would need 2 busses each and more than 1 SPI chip select. this will solve the problem partly but i don't see how to template very specific wiring as with the AXP power chips. |
Beta Was this translation helpful? Give feedback.
-
Regarding SPI chip select I noticed too we need specific CS for any SPI bus user. So every SPI display driver will need one in addition to MFRC522. I will initiated this one of these days. |
Beta Was this translation helpful? Give feedback.
-
and also one for the SD card. |
Beta Was this translation helpful? Give feedback.
I have a device with only some of the components used in m5stack and some of the components used in another device but on different gpio's but I cannot use the available drivers correctly if they/re hardcoded and/or implemented all in one.
While true that almost every device will probably need a self compile with specific options this is what tasmota was at the beginning with modules but as the gamut of available devices grows larger you run into the same problem of trying to add every device into the code and maintain it at the same time