hello you, windwos kernel driver supported?

Trying to compile the blinky program for nRF5, but getting an error on macOS 12.3.

export GOTEXT=0x00001000
export GOMEM=0x20000008:262136
export GOSTRIPFN=1
export GOOUT=hex

emgo build -o blinky ./main.go
# runtime
../../../embeddedgo/goroot/src/runtime/stack.go:1132:2: undefined: gostartcall

I tried a few different patch version in the patch repo, but got the same error each time.

Current nil checking code bases on the fact that loading from or store to pageZero causes a segmentation fault. This usually doesn't work in case of embedded system.

Possible solutions for ARMv7-M:

1. Use MPU if available to make the beginning of memory unreadable. This doesn't change the current nil check implementation but the MPU is optional peripheral. I don't know how this solution interfere with exception vector fetch which is performed on instruction bus. In the last resort, we can accept that nil checks work only in unprivileged mode.

2. Use test and branch or conditional UNDEF. This requires couple of additional instructions and unset faultOnNilArg0 for all load instructions. In case of UNDEF we need to implement UsageFault handler to handle Undefined Instruction exception.

We alseo need to handle nil checking for stores. In most cases the beginning of memory is read-only but in case of STM32F7 and maybe other Cortex-M7 based MCUs the ITCM-RAM can be mapped at address 0.

Consider to perform a target specific initialization outside the runtime package in target specific packages as proposed by n64 port:

It may give us more flexibility when it comes to early hardware initialization. For example, with this approach we can probably avoid the plugin code in imxmbr.

Questions

1. Does this //go:linkname approach affects the order of package initialization if we use Go (nosplit) instead of assembly?
2. Can we reduce the number of external functions to only _rt0_GOARCH_noos and in some way force the init function in some external package to be the first one (with dependencies) executed by runtime?
3. If the init approach described above doesn't work, can we reduce the number of external functions to only two. For example the second one in the form of: func noos_defaults() map[string]any?
4. Maybe only one _rt0_GOARCH_noos function is enough to fulfill our needs?

I personally prefer 4. You can probably use DATA unhandledException set to very dumb handler that stops execution here and update it in the _rt0_GOARCH_noos to more intelligent one.

What is the difference between this and tinygo (https://github.com/tinygo-org/tinygo) ?