ardnew / ESP32-3248S035

Board support package for Sunton ESP32-3248S035
MIT License
18 stars 5 forks source link

Missing Readme #1

Open MkMunich opened 1 year ago

MkMunich commented 1 year ago

Hi, this seems to be a very small starting point for developing a sunton ESP32-3248S035c device for platformio (I hope) - I love it. Only missing, how to get it integrated in platformio? Is there a platformio.ini file? What do I need to do to compile your sources? Next would be to ask, where&how to add own GUI elements? Is there a 'Hello world' available? It would be great, if you could publish a Readme in git. Many thanks in advance MK_Munich

ardnew commented 1 year ago

Hi, this project has been under active development the last few weeks and has changed quite a bit since inception. It seems mostly stable at this point — I'm not experiencing any bugs so far. I will gladly add a README.md with usage details and close this thread once completed.

Note that it is currently only being used with Arduino. I haven't tested it with PlatformIO, though it should integrate very easily because it has minimal 3rd-party dependencies. I will first work on getting a draft README written per existing implementation. Then I can try to integrate with PIO and will update README accordingly.

ardnew commented 1 year ago

@MkMunich Still haven't made time to write up a proper README, but I wanted to address your principal question regarding PlatformIO integration:

I've added a pair of example projects here: https://github.com/ardnew/ESP32-3248S035/tree/main/examples. One for Arduino, and one for PlatformIO. Both of these examples are identical in behavior, the only difference is toolchain configuration.

There is a platformio.ini file included (with comments), and the example's source file main.cpp (with comments) shows how to create a basic GUI and access the other hardware peripherals on the board.

Please test the PlatformIO example and let me know what works and what doesn't. I quite liked this PlatformIO approach, and may begin using it more frequently.

Will follow up once more when I get the README written.