> Raspberry Pi Zero will remain in production until at least January 2026
Considering the roughly 2ish year release cycle of FreeBSD, it seems likely that 32bit RPIs will be eol'd before FreeBSD 16 is released.
Which SoC are you referring to here?
My simulator is not an qemu/renode like CPU emulator, which would be too slow, just some mesh routing algorithms, with like 200 nodes simulated on a single machine. https://blog.nubix.de/2022/04/testing-baremetal-firmware-at-...
(Support for macOS was removed a few years ago due to a lack of maintenance and no active developers with access to a macOS machine)
It also comes with a mesh simulator: https://github.com/RIOT-OS/RIOT/tree/master/dist/tools/zep_d...
But that's pretty much retro-computing these days, I don't see why anyone would use those on new projects when Cortex-M0+ parts are much cheaper and more power efficient.
And gcc-avr still rules over gcc-arm. qemu on avr easy, on arm horrible.
The 64-bit FreeBSD kernel is perfectly capable of running 32-bit applications, and will be so for the foreseeable future. The only reason I can see to support a 32-bit kernel is to allow for installation on hardware that is approaching decades of obsolescence, so again I ask, what is the point?
Even if there still are plenty of obsolete 32-bit CPUs running Linux or *BSD, since many years I have never seen a case where using them is the right technical choice.
When a UNIX-like OS is desired, it is a mistake to use anything less than a very cheap 64-bit CPU, like one with ARM Cortex-A55 cores.
For the many embedded applications where a 32-bit CPU is appropriate, either one of the many open-source RTOSes should be used or a bare-metal program, which is the best choice in many cases. For such embedded applications, a UNIX-like OS is much too bloated and it does not allow deterministic control of the hardware.
For modern home routers or security appliances you want them to be able to easily execute firewalls with complex sets of rules at multi-gigabit per second throughput, so that the router throughput should not be limited by the CPU instead of the Ethernet or WiFi interfaces.
For this, you really need something like Cortex-A55. The routers with obsolete CPUs limit the performance without any worthwhile price reduction.
On the other hand, for many embedded projects where a 32-bit CPU is the right choice, the developers choose Linux just because they are familiar with it and they are too lazy to read the manuals of some free real-time operating system, even if in fact the latter might require less development work and maintenance work for their software project.
There are some socs with A35 cores though, that is probably lowest end that is actually available.
> For open-source operating systems there will always remain the older stable 32-bit releases like FreeBSD 16 in this case.
I have a couple WD NATs which chug along on 32-bit PowerPC, a patched kernel and the last version of Debian before they dropped support for 32-bit PowerPC. Don't really plan to replace them before they break...do need to work out a backup "story" (as the kids would say) but they just hold old TV shows so if they let out the magic smoke then nothing important is lost.
Would be nice if I could keep them up to date on the latest and greatest but nobody cares about the 32-bits anymore...
Sadly not all on the mainline, but having worked in the embedded world, Linux is a massive part of that space.