PlatformIO VS TinyGo

For the ESP32 in read mode, we've successfully developed a project using PlatformIO that accepts the key during build time and stores it in memory.

Check out Zephyr OS and Platform IO. Zephyr is part of the Linux foundation and has similarities to Linux with how it performs hardware abstraction (device tree). Platform IO integrates with other frameworks including mbed and Arduino.

PlatformIO together with avr-stub can be used to do source level debugging but there are some caveats.

Look into https://platformio.org/, it can abstract over a few RTOSes, and can show you which OSes work with which chips/boards.

If the HW looks like it works, you could also try alternate programming software. (e.g. TinyGo or PlatformIO)

You might have better luck with PlatformIO than the Arduino IDE; it's better at automatically choosing the serial port, though I can't say I've used it under Windows.

My other suggestion takes more work but will make your life oh so much better. Professionally I have used and highly recommend. https://platformio.org/ which is free!

Will you be doing embedded Linux? Embedded RTOS? Bare metal? Microcontrollers? SoC (say, FPGA with a hard processor core)?

You can do a lot with QEMU. https://bootlin.com/ has a lot of great, free training material.

https://bootlin.com/doc/training/embedded-linux-qemu/embedde...

is one of my favorites.

Learning to cross-compile, do embedded debugging, the process of booting an embedded system (which varies depending on the answers to the above questions), learning how to read a technical reference for the processor you’re using as well as for peripherals you’re likely to interact with - SPI, i2c, UART, maybe PCIe, are all handy skills. Learn a bit about JTAG, hardware, reading schematics, etc. Even being able solder is helpful.

There may be books (I had a great embedded Linux book when I started) but there are lots of online materials too. Check out https://platformio.org/

There are fun embedded boards and projects for microcontrollers too - micropython on an rpi pico, tinygo, eLua, etc.

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).