I wanted to try FUZIX on my pico2 so I had to build it myself. I don’t really know anything in particular about FUZIX, but I knew that I didn’t want to have to remember how this stuff worked in the future, so I’ve automated building and publishing of FUZIX images for both the pico and pico2 over in my fork of FUZIX:
You can download the images from its release page:
These builds are based on the patch that was made available over in the PicoCalc repo https://github.com/clockworkpi/PicoCalc/blob/master/Code/FUZIX/fuzix.patch
(I’m not allowed to post more than 2 links at once)
Thank you! I’ve been curious about this but hadn’t gotten around to trying it yet.
Is wifi supported on the Pico2? The FUZIX website didn’t really mention it, though they did say wifi was supported for some other platforms. Figured I’d find out when I got aroudn to trying it, and now you’ve made that easy to do.
Yeah, that’s ok. I will note that I just pushed an update that doubles the amount of usermem that is available to run programs on the pico2, so you may want to grab that build.
Please note that, until the most recent build from a few minutes ago, the filesystem image I was publishing in the releases section was a generic image. I switched that to one that is slightly more pico-friendly and that includes a utility that will reboot in flashing mode, which is more convenient than trying to press the bootsel button: picoctl flash.
So I recommend fetching the latest release zip before you flash the image, just to save an extra couple of steps later.
If you are using macOS, things should not be that different (even though I don’t know the details as I am not really a Mac user even though I borrow a Mac occasionally for testing things). If you are a Windows user, sorry, but your best option is to create a Linux live USB and boot off that, and then follow the directions for Linux.
If you are using xBSD or macOS, there should be equivalent Unix tools available. If you are using Windows, your options are to either use a Linux live USB or use WSL2, since it is not reasonable to expect developers who develop for a Unix-like OS (Linux, xBSD, or macOS) to go out of their way to write tools specifically support those Windows users who are unwilling to use WSL2 or a Linux live USB.
(This is because the Windows API’s are substantially different from the Unix-type API’s shared by Linux, xBSD, and macOS such that in many cases supporting Windows outside of WSL2 may be a significant rewrite.)
I sense sarcasm in your response. The fact of the matter is that there are just certain sorts of things that are easier to do under Unix-like OSes than Windows.