Best posts made by anichang

https://github.com/mfp20/esp32-template-plus

It's a project template with added features. I started to make it easy for me to start new projects by just cloning that repo and editing the main.c file but ... ended up dumping in as many features I could. The end result is a kind of pseudo operating system for M5Stack (and ESP32 in general, as far as the support for other boards is included in the upstream repos: arduino-esp32 and loboris' micropython).

I started from Loboris' Micropython repo and included the Arduino libs for compatibility with the huge Arduino codebase; but It doesn't interact with Arduino IDE. My goal is to just being able to throw in arduino code and have it run without modifications.
It defaults on TomSuch's menu system and the apps I've found in this forum.

In this way we don't have to choose between arduino and micropython: we can have both running on the same device, disable one. or the other one, directly from the Kconfig menu. Or disable both and start from the scratch: it's just a matter of delete main/main.c and write a new app_main() function.

Currently is clunky and partly not functional but in the next hours/days I'll complete the planned features, as well as add some kind of hooks/callbacks for setup/loop functions: the idea is to have an 'arduino' folder where to place vanilla .ino files and have them run instead of the default menu/upython setup.

Cheers

The project went under deep rewriting. Basically is brand new. As I wrote on the README:

The current code is a rewriting of my previous esp-template-plus (ie: rebased on top of esp-idf-template instead of MicroPython for ESP32 with psRAM support), in order to make explicit and trackable all the changes from Espressif/Micropython/Etc repos to the actual esp-template-plus project.

Currently builds the default image with all the libs from the components folder (micropython included, see tools/micropython/ports/esp32/build/libapp.a) but doesn't run any task yet.

Initially I reworked/cleaned Loboris' Micropython awesome project that lead the way for Micropython on ESP32, but then I discovered that his repo had no history back to the original projects. Moreover Loboris looks particularly focused on the Microphyton port, finalizing that codebase for one task only (Micropython), making the whole project unsuitable for generic templating. I've spent a couple days fiddling with his messy stuff then I gave up and started from the scratch, importing his component.mk files and his existing component patches.

The result is a codebase 99% trackable to the single original project's repos, future proof, and an overall clean project codebase (ex: no extra scripts to manage the project: everything is a 'make' command). This means that you don't depend on me (or Loboris) to update single components or whatever else; we are just packagers saving you a few weeks of work to understand the internals.

Stay tuned ...