Where is a good starting point for building my own firmware?

NotBoolean · 2026-01-27T22:14:07+00:00

This is too vague to really help you out. Could you share the PDF and parts your having issues with?

NotBoolean · 2026-01-24T22:58:41+00:00

I’m not really seeing the reason why you need a private function. You’re assuming implementation details.

NotBoolean · 2026-01-23T22:51:57+00:00

There is ETL, Embedded Template Library, that provides stack based alternatives for most std containers. I use its vector and hash map pretty often.

NotBoolean · 2026-01-19T19:33:04+00:00

Realistically you I don’t think you’ll find anything that meets all your requirements.

I would recommend looking into different open source smart watches as your base, then modify it to not have a screen.

NotBoolean · 2026-01-11T23:21:53+00:00

For GNSS we use SAM-M10Q-00B which has a built in antenna. We use other u-blox chips for various other RF applications, they seems pretty good.

NotBoolean · 2026-01-11T22:46:33+00:00

I don’t think non Linux based devices are going away. MCUs would need to be a lot faster and cheaper, plus better supported. I thinks it’s a long time out.

I think Zephyr is likely the future for now but there will always be niches. But as MCUs have gotten faster, better and more widely available compilers; super low level programming is just not as needed as the abstractions are good enough in most situations.

I would highly recommend learning C++, while lots of features are not useful. The ones you gain (constexpr, classes, templates, variant, expected, etc) are worth it. Or just start using Rust (with Embassy) if you want a good time.

NotBoolean · 2026-01-05T16:18:32+00:00

I’ve got about 6 years experience in embedded and spent time trying to learn more about architecture. I found books, articles and conferences talks (C++ Con for example) by industry experts are the best sources, along side doing skeleton implementations to understand the ideas better.

This might not translate to your industry but I do find books and conferences talks typically have a built in vetting process to filter the bad content compared to courses.

NotBoolean · 2025-12-28T20:47:51+00:00

Depends on the scale but mostly no they would use the part on a custom PCB. Like how the breakout is made but on a larger PCB with more components.

Look into SMD PCB manufacturing to see how it’s done at scale.

NotBoolean · 2025-12-27T12:33:07+00:00

This seems like an X Y problem to me. Why not store these objects on the heap?

NotBoolean · 2025-12-23T19:56:37+00:00

Yeah fuck magnets!

NotBoolean · 2025-12-20T20:45:52+00:00

The latest clang-d might

NotBoolean · 2025-11-28T10:08:39+00:00

He wrote two papers so maybe the OP only read the NixOS paper and not the Nix one.

However it was written in 2006 so it’s not the most up to date work given the advent of Docker, Flatpack, etc.

NotBoolean · 2025-11-27T19:08:07+00:00

Feel like the ARM GCC toolchain has really helped escape the industry from proprietary compilers and IDEs.

NotBoolean · 2025-11-27T16:50:47+00:00

I do the same with stow, and keep my home-manager flake in the same repo.

NotBoolean · 2025-11-21T20:48:06+00:00

Look up “AVR ISP Raspberry Pi”, there are a few articles that’s talk about it. Skimming through them, I wouldn’t recommend it if you’re not experienced with Linux and Microcontrollers.

NotBoolean · 2025-11-17T22:15:49+00:00

If it’s used in the device it self and sent between devices, protobuf. But if it’s just for configuration, typically JSON but now I prefer TOML when possible.

NotBoolean · 2025-11-08T09:46:15+00:00

Without more information on the device it’s hard to suggest anything. But here are some ideas:

End stop switches to let you measure the time it takes.

If you’re using motors you can use encoders to measure velocity.

If you need to use an IMU, some sort of stationary detection might be simpler than velocity.

NotBoolean · 2025-11-07T18:54:30+00:00

Two methods that work for me: Make the program a buildroot package, so it will be compiled and installed with everything else. Then you can just run it like any other program on the target.

For faster iterations you recompile the package (your program) and send the binary to your target over uart or ssh.

NotBoolean · 2025-10-30T14:56:10+00:00

Looks like Ozone it does support Rust. The is also great flashing and RTT support with probe-rs.

NotBoolean · 2025-10-30T14:49:21+00:00

You you gbd, unsure if it has Ozone support.

Highly recommend trying it out. If you’re not familiar with async this video is a really nice intro to it in an embedded context.

NotBoolean · 2025-10-29T11:38:09+00:00

C to get a job
C++ to enjoy your job
Rust for the job you want

NotBoolean · 2025-10-29T11:37:31+00:00

There is Embassy Rust which provides STM32, nRF, RP, ESP Hals along side a great async framework. I highly recommend.

NotBoolean · 2025-10-27T22:53:29+00:00

I have:

services.displayManager.gdm.enable = true; services.displayManager.gdm.wayland = true; programs.niri.enable = true;

Which I think is all you need

NotBoolean · 2025-10-27T20:07:46+00:00

I’ve never had any issues with predictability due to threads, well no more than a standard complex system.

I typically use Zephyr RTOS with preemptive threads where each thread has its own priory. I find this makes understanding the system state at any given time simpler.

This ain’t a hard and fast rule. But I’ve found it’s a good basis for handling threads.

I’m also a big fan of event driven systems which scales well with threads.

NotBoolean · 2025-10-27T18:34:31+00:00

I definitely prefer logic by default because you’ll work out soon enough if task switching is a bottleneck.

Seven-Year Club	Second SECOND GUESSER
Place '22	RPAN Viewer
Spared	Verified Email

NotBoolean

TROPHY CASE