r/embeddedlinux • u/Stalllio • Sep 13 '26
seeking help and/or advice Firmware intern advice
Hello people,
I’m at firmware engineering intern and I’m looking at learning embedded Linux. The engineers in my team do Linux driver development, embedded Linux, c++ and lots more things.
What’s the best way of learning embedded Linux? My mentor gave me a raspberry pi and and an stm Nucleo board to practice using.
What’s the best thing to learn career wise and what would be the best way to learn. I’m trying to also secure a return offer so I’m gaining as much knowledge as I can.
Also any advice on what else to learn that would be a plus when looking for jobs in embedded.
Thank you!
1
u/Plussy78 Sep 13 '26
I'm kinda in same situation, i would like to connect with you. To learn embedded Linux? Can we connect?
1
1
u/Ok-Suspect-2388 Sep 14 '26
I am also an intern in organization which focuses on IOT devices. I want to get the employment in the same organisation so I want to learn linux and embedded system more I have some experience of stm32 nucleo board and the blue pill if any experience person can guide me it will be very helpful
1
1
u/Longjumping-Pack8494 Sep 15 '26
Embedded linux huh, soft hands i see. In 1942 when the Germans were surrounding Stalingrad, i was writing assembly in my basement with no food.
Being a bit kore serious, better start with low level, like writing your own OS in assembly, then writing a PC emulator on that, then loading your custom OS on the emulated PC.
Gotta go back to my 74-hour shift of writing custom drivers for my homemade tomahawk missile, thank me later.
1
2
u/DaemonInformatica Sep 14 '26
Ultimately? By doing. This may sound crude, but it's effective.
- Start by figuring out what the rest of your team uses. (Buildroot? Yocto? Something else?)
- Setup an environment so you can build at least a base-image that runs. Peek at how your co-workers do it, but don't copy blindly. Try to understand what goes where and why.
- Build and run the base image. Once that is up and running: From there, start messing with it. change things. (This can be so simple as adding / changing a welcome message, purely to see if you can and if the result actually ends up in the end-result).
I remember well the time where I inherited a project from a colleague of mine. An embedded Linux project on some network module. It was built with Buildroot, and I had a bit of a steep learning curve: I knew microcontrollers and I knew Linux. but it took a couple of tries to get it to do what I wanted. ^_^
Including messing up Royally, when I boned the support for USB storage, which was used to update the image on the units. Learned a Lot about bootloaders and TFTP that day..
2
Sep 13 '26
[removed] — view removed comment
1
u/Stalllio Sep 13 '26
Thank you, I’ve worked on a little telemetry so far and gradually adding to it. I’m using Ubuntu Linux. AI helps me quite abit without giving me any code, I use it to learn and it helps learn much faster.
1
u/MrTamboMan Sep 13 '26
Try asking for very brief solution but with links to specific sections of documentation about tools/concepts that could help you instead of ready solution (not just code). Reading docs+source code will give you more knowledge in a long term.
1
u/Stalllio Sep 13 '26
We use confluence and all the engineers document everything. There’s TLD builds etc
1
u/Kaffe-Mumriken Sep 13 '26
Learn their system configuration - are they using Yocto Buildroot or some bare metal thing? Figure out what hardware interfaces their Linux build is using (like custom gpios, rs422, ether).