4 ms·

I own a home router (TP-Link Archer C7) and I have been running OpenWRT for many years on it, having full control over it via SSH. A few years back, I had an id

I own a home router (TP-Link Archer C7) and I have been running OpenWRT for many years on it, having full control over it via SSH. A few years back, I had an idea for an daemon process/service to improve a certain thing in its functionality. I was delighted to find out that the MIPS chip that powers the thing was supported by Rust, and I coded a "script", cross-compiled it to a binary and SCP't that to the router. It ran beautifully. After that (and running Rust on a few other embedded systems, including an ARM Cortex-R chip) I became convinced that Rust is the next C for the embedded.

johnisgood 2y ago
> I became convinced that Rust is the next C for the embedded. Ada works, too, though, or Forth. :P
- johnisgood 2y ago
  See more at https://learn.adacore.com/courses/Ada_For_The_Embedded_C_Developer/index.html https://learn.adacore.com/courses/Ada_For_The_Embedded_C_Dev....
ricudis 2y ago
The OpenWRT SDK is quite polished and convenient to use, so I usually use that for custom OpenWRT binaries. But a few days ago I needed to run something custom on my old QNAP NAS (Marvell ARMv5TE based), and I decided to try cross-rs[1] for the first time. It turned the usual multi-hour expedition of locating and configuring SDKs, toolchains, etc into 3 commands and 5 minutes of downloads and compilation. The resulting executable ran successfully at the first try. I was amazed. [1] https://github.com/cross-rs/cross https://github.com/cross-rs/cross
- overfeed 2y ago
  I default to Go for code I want to run on old MIPS and ARMv5/v6 appliances because despite the "huge" binary sizes, cross-compiling is done by setting 2 environmental variables.
  - Graziano_M 2y ago
    Easily making static executables is a huge boon too.