>> So now I just need to try to dig up enough hardware documentation to >> write my own code for it, probably including writing an ARM >> assembler. > The RP2040 is extensively documented.
Yes, I've found some of it. Unfortunately much of the useful stuff data is buried in PDFs, so it costs time and effort to convert the PDFs into something useful. (I've never understood the apparent attitude that surface glitz is so important it's worth impairing content accessibility and usability for.) > Almost all development on the RP2040 is bare-metal development (thatâ??s wha$ Given its size, that's what I'd expect. 264K of RAM doesn't hold much. > The Pico SDK makes building RP2040 binaries super easy, and itâ??s BSD-licen$ Easy? I disagree. Nothing involving cmake is easy. Not for me. Also, based on what little I've found so far, it requires gcc so recent it's not usable for my purposes. And python, just in case two showstoppers weren't enough. >> (I think I have a DNARD somewhere, but I suspect I will find writing >> my own assembler easier than bludgeoning the NetBSD/arm toolchain >> into generating what the Pico wants.) > Or just install this package? > cross-arm-none-eabi-gcc-8.3.0nb5 GCC for bare metal ARM EABI 8.3.0? Much too recent for me. (Besides, pkgsrc isn't interested in supporting me.) /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B