It seems that tinygo doesn't not support MIPS based embedded devices out of the box, although LLVM does support the following:

    mips       - MIPS (32-bit big endian)
    mips64     - MIPS (64-bit big endian)
    mips64el   - MIPS (64-bit little endian)
    mipsel     - MIPS (32-bit little endian)

My intent is to execute the tinygo compiled binary within a mipsel linux box, no

Is your enhancement proposal related to a problem? Please describe.
Refer to: zephyrproject-rtos/zephyr#28932

Describe the solution you'd like
Refer to: zephyrproject-rtos/zephyr#28932 (comment)

Describe alternatives you've considered
NA

Additional context
NA

With Tock running on this board with virtual_uart sitting on top of USB, the Nano 33 BLE is a reasonably promising board to be a standard, well supported Tock board. Additionally, if the board turns out to not be great, the infrastructure which would make the Nano 33 BLE work well would apply to any other board that has the nRF52840 + USB combination.

• Make the bootloader and tockloader ex

I was surprised at this:

>>> n = neopixel.NeoPixel(board.GP0, 1, auto_write=False)
>>> n.deinit()
>>> n.show()
>>> 

Expected behavior: n.show() raises an exception since the related object has been deinitialized
Actual behavior: n.show() does not raise an exception

I only tested on Pico, so this may be a port-specific problem. However, I didn't label it as such init

In PROTECTED mode, the MPU is used to map regions of memory to supervisor- and/or user-accessible memory. Currently, that algorithm is very simple: The entire address range is made accessible in supervisor mode; a single MPU region is used to enable user-mode access in each user memory region.

Each MPU region must bit both of a power-of-two size and with an alignment in memory equal to the si