I got a response on the Tinygo slack channel: https://gophers.slack.com/archives/CDJD3SUP6/p1692660961082699?thread_ts=1692660743.478199&cid=CDJD3SUP6

from mbx-iot.

Workaround

I remove the "bad" code on the Tinygo dev branch:

• Uninstalled the tinygo vscode extension
• Uninstalled tinygo via brew
• clone the tinygo-org/tinygo repo, checkout dev
• then go install
• I am not sure if this was needed but I created

ln -s /Users/tgilkerson/go/bin/tinygo /usr/local/bin/tinygo

• then reinstalled the tinygo vscode extension

from mbx-iot.

Workaround Take II

• Install TinyGo the official way with brew
• Get everything working in vscode
  • Install the TinyGo plugin
  • Make sure the TinyGo target is set and machine is recognized in the IDE
• Modify the file as described below

# Make sure you have `pico` selected as the TinyGo target
# and the vscode is working then run the following
code  $(jq -r  '.["go.toolsEnvVars"].GOROOT' .vscode/settings.json)/src/machine/machine_rp2040_spi.go 

# Comment out the two occurrences of the following and save
	for spi.isBusy() {
		gosched()
	}

from mbx-iot.