TinyGo VS MicroPython

Reading through the documentation, you will understand why this plugin is called "tiny," i.e., the SDK uses the TinyGo compiler instead of the official Go compiler. You can read more about why this is the case on the SDK\'s overview page, but the TLDR version is that the Go compiler can only produce Wasm binaries that run in the browser.

Not only you can fit Go into a kernel, there is at least two products that do so.

TamaGo, used to write the firmware used in USB armory.

https://www.withsecure.com/en/solutions/innovative-security-...

TinyGo, which even has official Arduino and ARM support, and is sponsored by Google

https://tinygo.org/

Ah but that isn't proper Go! Well neither is the C code that is allowed to be used in typical kernel code, almost nothing from ISO C standard library is available, and usually plenty of compiler specific language extensions are used instead.

Reminds me of https://tinygo.org/ - a project that brings Golang to embedded devices, browser (wasm) contexts. Do you converge or diverge from that project?

You should also consider TinyGo. It can compile Go for the Pico, and is starting to get good device support.

tools/mpy_ld.py: https://github.com/micropython/micropython/blob/master/tools...

tools/mpy-tool.py lists opcodes: https://github.com/micropython/micropython/blob/master/tools...

Can the same be done with .pyc files; what are the advantages of MicroPython native modules?

Why does it need wasm2c?

For more: https://micropython.org/

For context

> MicroPython is a lean and efficient implementation of the Python 3 programming language that includes a small subset of the Python standard library and is optimised to run on microcontrollers and in constrained environments.

https://micropython.org/

Just putting my hand up to say that MicroPython is awesome (and runs on the RP2040). https://micropython.org

Gah, I just ordered one on impulse [1]. I've wanted to build out a WiFi PDA for quite some time now and I like this hardware.

I'm quite liking the idea of running tulip MicroPython [2] on it, or going back to pure MicroPython [3] and writing some drivers. Apparently something like ampy can be used to upload/download Python files [4].

Threads could be quite exciting for running multiple programs at once [5], although I have no idea what it means for two programs to fight over GPIO! It does seem as though MicroPython can only utilise a single core [6].

[1] https://www.lilygo.cc/products/t-deck?variant=43087936487605

[2] https://github.com/bwhitman/tulipcc/tree/main/tulip/tdeck

[3] https://docs.micropython.org/en/latest/esp32/tutorial/intro....

[4] https://www.digikey.co.uk/en/maker/projects/micropython-basi...

[5] https://docs.micropython.org/en/latest/library/_thread.html

[6] https://github.com/micropython/micropython/issues/8197

If you really want to engage in the travesty that is shoehorning a high level scripting language into an environment that has 512 bytes of RAM and less clock cycles than an electric toothbrush, there is micropython.