{"id":35649,"date":"2021-02-16T10:30:19","date_gmt":"2021-02-16T15:30:19","guid":{"rendered":"http:\/\/pappp.net\/?guid=addd2be64d0556d47ca9d9036bcec3ee"},"modified":"2021-02-16T10:30:19","modified_gmt":"2021-02-16T15:30:19","slug":"fuzix-unix-on-a-raspberry-pi-pico-raspberrypipico-unix-hjalfi","status":"publish","type":"post","link":"https:\/\/pappp.net\/?p=35649","title":{"rendered":"Fuzix: Unix on a Raspberry Pi Pico #RaspberryPiPico #Unix @hjalfi"},"content":{"rendered":"

Source: adafruit industries blog<\/a><\/p>\n

Article note: Fuckin' cool. An only slightly feeble V7 clone on the Pico. \r\n\r\nAlso, I find their notes about the Pico's C SDK very promising - I've been thinking about where I'd like to move UK's intro embedded lab long term and the quality and simplicity of documentation makes the Pico suddenly kind of appealing. \r\nWe're on Keil in legacy mode which is foul + TI TivaC Cortex M4 right now because there is a good, cheap book for it, major contenders ST CubeIDE + STM32 or TI CCS + TivaC, but maybe I should be looking at the Pico.<\/div>

\"\"<\/p>

David Given blogs<\/a> about porting Fuzix<\/a>, a small V7 Unix clone, to the new Raspberry Pi Pico microcontroller:<\/p>

Working with the Pico was an experience: the documentation is excellent, as is the C SDK. The SDK provides a set of libraries which are thin wrappers around the underlying hardware, making most features utter simplicity to use. Unlike the ESP8266’s libraries, the Pico SDK is unopinionated and doesn’t require you to use any of its features: if you want to talk directly to the hardware, you can (and in fact there’s library support for doing just this).<\/p>\n

There are some high-level features like a heap, stdio emulation, multicore primitives, etc which I’m not using, but if you don’t use them you don’t pay for them. For my embedded-systems brain it’s the ideal ratio of functionality to complexity.<\/p><\/blockquote>

The Fuzix port provides:<\/p>