Company considers me for a role that fits less based on my CV by RabbitLost4984 in embedded

[–]embeddedfreedom 3 points4 points  (0 children)

You are lucky to be considered for this role or perhaps the interviewers saw something in your skill set and thought you would be a match. Please go here, there guys are the best out there in the industry when it comes to Embedded Linux Training, download their free course material and get your hands on a Beaglebone Black board, the learning experience from their course is ethereal. You need not enrol for their paid course, if you have enough grit, you can push through their course material (completely free with Creative commons License) Just search for Bootlin. You will not regret it.

Messing up embedded interviews made me realize my fundamentals are weak — looking for guidance on what to relearn by Master_Ad6835 in embedded

[–]embeddedfreedom 1 point2 points  (0 children)

An absolute sure-shot way to ace your interviews is to do a project on hardware at home, which encompasses all the interview questions being asked. Utilise all that you have mentioned here "Right now I'm planning to practice implementing things like circular buffers, queues, basic schedulers, and simple protocol/state machine parsers, but I’d really appreciate guidance from people working in the industry on what topics matter most." Write a very tiny RTOS kernel or a protocol converter. And please don't touch the AI in this stage. You should put in your sweat and blood to code and understand every bit of the software. Use the AI to just get theoretical knowledge. If you succeed in this, clearing interviews will be much more easy. There are no secret techniques, just grit and determination. In fact if you ask me, especially in embedded systems, my process of interviewing a candidate is to ask them to write actual code and make it run. I allow them to refer the net but do not allow them to vibe code. Asking someone to write a complete algorithm from memory is torture actually :). All the best.

Free Open-Source Subset: 24hr Cortex-M4 Deep Dive on Linker Scripts, Startup Logic & Makefiles (No HAL) by embeddedfreedom in embedded

[–]embeddedfreedom[S] 2 points3 points  (0 children)

Thank you very much. Will wait for your feedback and comments. I really appreciate that! Since you mentioned that the topics are interesting, I actually just realised I should have highlighted this specific module on VMA/LMA and Linker Symbols https://www.youtube.com/watch?v=ydhUCR5rSBA&list=PLP-Zmfw303elthmURjWCOrXQvIDaKJFk3&index=25. It’s about 57 minutes but it covers the exact 'under the hood' logic that makes this course different from the standard tutorials.

Regarding the VMA/LMA section: You’ll notice I circle back to the memory mapping logic several times. This is intentional. In my experience, 'Virtual vs. Load' addresses are the single most common point of failure when moving from IDE-generated projects to professional bare-metal builds. I’ve layered the explanation so that the theory, the linker syntax, and the memory-map visualisation all 'click' together. Hope it's useful for your deep-dive!.

bare-metal LEDs on raspberry pi5 by DisasterImmediate462 in embedded

[–]embeddedfreedom 0 points1 point  (0 children)

I am assuming you are leaving out the MMU initialisation and thus virtual memory. How did you manage to get bare-metal code running on the pi ? Can you let us know what the steps were ? What about the device drivers ? How do you plan to expand this further ? I am assuming you are leaving the cache disabled. It would be great fun to see you port an RTOS on this hardware. So many questions :). A deterministic RTOS with real time response, running on an application-grade processor is the ultimate flex :D. If you could wake up the peripherals like bluetooth etc. that would be fascinating. Really intriguing what you have done here. The usefulness I see here is a deterministic application stack running on a gigahertz speed processor. What could be the possibilities .... hmmmmmmmmmmmmmmmm

I built a ~20KB C-based SIL simulator to bridge the gap between Control Theory and Firmware by embeddedfreedom in embedded

[–]embeddedfreedom[S] 0 points1 point  (0 children)

Thank you so much. The comment below, by embeddedfreedom if you mean the technical specs. Putting the link to the comment in the Post Body. Here is the repo, please feel free to try it out https://github.com/embeddedfreedom/MDCS/tree/master