MicroPython VS TinyGo

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.

There is some work to implement a common CAN interface in micropython but it's some way off yet: https://github.com/micropython/micropython/pull/13149

https://github.com/raspberrypi/pico-sdk/ links to a PDF about connecting to the interwebs with a pi pico.

micropython/micropython//ports/rp2/boards/RPI_PICO_W: https://github.com/micropython/micropython/tree/master/ports...

raspberrypi/pico-sdk /lib: btstack, cyw43-driver, lwip, mbedtls, tinyusb https://github.com/raspberrypi/pico-sdk/tree/master/lib

raspberrypi/pico-examples//pico_w/wifi/access_point/picow_access_point.c:

https://github.com/raspberrypi/pico-examples/blob/master/pic...

There's an iperf opkg pkg, or is it just netperf (which works with fluent)?

raspberrypi/pico-examples//pico_w/wifi/iperf/picow_iperf.c:

Needed for hobby project, maintained by very small team. Haven't decided on specific microcontroller. Needed for general bit-banging, speed and code size are not priorities.

So far have considered MicroPython [0] [1] and Lua [2] [3], but open for suggestions for others.

What are experiences?

[0] https://micropython.org/

Python is also a general-purpose programming language. It's typically used on desktop / laptop computers. But Micropython is a variant that can be used to program embedded devices.

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.

Thankfully some folks completly ignored whatever the rest of the world thinks system programming is all about and created:

- TinyGo (https://tinygo.org/), which is acknowledged by people in the industry[0][1]

- TamaGo unikernel on USB Armory secure key (https://www.withsecure.com/de/solutions/innovative-security-...)

And then there is the question if writing compilers, assemblers, linkers is systems programming or not.

[0]-https://www.cnx-software.com/2019/08/28/tinygo-go-compiler-f...

[1]-https://twitter.com/ArmSoftwareDev/status/131680481331796787...

Have you seen TinyGo? In the case of embedded system I would probably still chose C over Rust if the system didn't support dynamic memory allocation, and most embedded systems do not.

>I really hate how for microcontrollers the only two choices are either C++ or Micropython

There's TinyGo as well. https://tinygo.org/

Gist link fixed, thanks. Compared to TinyGo, Go with GOOS=wasip1 will probably generate larger artifacts (at least, for now). This is because it bundles the entire Go runtime. The benefit is that it fully supports goroutine scheduling and non-blocking I/O. TinyGo (I believe) still uses a custom asyncify pass and does not support non-blocking I/O nor basic WASI networking (e.g. https://github.com/tinygo-org/tinygo/pull/2748 never landed, but GOOS=wasip1 supports it).