Hacker News new | past | comments | ask | show | jobs | submit login

Our company decided that they want to make an electronic device. They've found an electronics engineer who devised a schematics and wrote some kind of PoC firmware. I wrote "driver" for it (really just wrapper around serial port) for our software to consume it.

That guy was busy with other tasks, so iterating on firmware was too slow. So I decided to dive in. I mean I knew C a bit.

So I had to learn STM32 arm, I had to learn low level C, I had to learn assembly, I had to get some understanding of those electronics things to get some sense of it, I had to read tons of manuals and datasheets.

Long story short, I rewrote this PoC firmware into something I could bear. It's so nice to control all software from the start to the end.

Now our company wants to rework this device into "smart", add display with touchscreen and stuff. So I'm digging into embedded Linux programming, LoL.

I'm generally consider myself full stack developer, so I can write frontend, backend, kubernetes, setup servers, deal with cloud stuff. However digging that deep feels like testing my limits.




"Now our company wants to rework this device into "smart", add display with touchscreen and stuff."

please don't do that. Add some kind of interface, eg bluetooth, and an open-source app, or open-source/documented protocol, to control it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: