Deomid Ryabkov

ok, so you need to drive two pins - clock and then bitbang data, correct? i see how it might be useful, but making it generic is a bit problematic....

looks liek we could support it. but it's a big job, most likely to happen if someone with money is interested and can sponsor.

interesting. it looks like they reuse peripherals from ESP32, which is good. i assume we can ignore the "world controller" at least initially, until we figure out what's up with...

defintiely should do it, unfortunately it's a pretty big change and i don't have the time right now...

there isn't really a guide for adding a new platform, yet. i'll try to put something together. but the basic steps are: make sure we can flash the thing (changes...

yes, i think c3 is a big enough change to warrant a new platform

code is the documentation :) it's been a while since i touched it and it looks like code has been buried during some repo restructuring, but it can be found...

there's also a script i used to build the stubs when working on them: https://github.com/mongoose-os/mos/blob/master/cli/flash/esp32/genstubs.sh this is dead code right now and needs to be revived. i think C source...

i dug up the sources and checked them into the repo - https://github.com/mongoose-os/mos/commit/7ec8632c6ff9dbc4181063bff814a20702bcd717 you can now develop C stub code, then rebuild and test it with a single command.

assuming you refer to [this](https://github.com/mongoose-os/mos/blob/db91e49ecc1ec8426428591665867351d528dc2f/cli/flash/esp/stub/stub_flasher.c#L572). stub_main clears the bss segment and sets a stack pointer to where the stack will be. in xtensa abi, `a1` register is the stack pointer,...