That's awesome!! Thanks for sharing that with me, I had no idea.

Thank you! 😊 happy to hear that

Yeah it is definitely challenging, especially the first time! A Bootloader in the embedded world is known as a rite of passage 🤣

You should already have everything you need. There's probably no book or course that will chew it down for you, just get a board and use it and get things done, and just use datasheets and standard online documentation (App Notes, User Manuals) like the rest of us. I don't think ST's website and downloads are blocked in India, are they? If they are, you'll just have to find a way around that. You don't need some dubious courses, you just sit down and do the thing, come up with a project and realise it. One of the main skills you're going to need is getting comfortable with thousands of pages of documentation, and you might as well start right now. You skim them quick to get an overall feel of the structure and things you may find, then later pick and choose what you want to read to get things done. Have a goal, learn to ask pointed questions. Once you have a clear question on your head, you are likely well on the path to finding an answer by yourself. But also connect to communities which can answer these questions for you. Here's some books for your deliberation though. * Computer Organization and Design: The Hardware/Software Interface, ARM Edition - Patterson/Hennesy. Very broad strokes general stuff, with ARM being only there for examples, not terribly ARM specific. Fundamental processor knowledge. * The Definitive Guide to ARM Cortex-M3 and Cortex-M4 Processors - Joseph Yiu. Earlier edition doesn't have M4, but there's really little difference. It's about what it says on the tin; i don't know whether it's valuable, but it can help you find your bearings and fill in the missing info. * The Designer’s Guide to the Cortex-M Processor Family - Trevor Martin. It's an extremely short book at only 500 pages. It's pretty hands-on, but then, it's not trying to be very comprehensive at all. And here's a problem with books - it starts off with "download Keil", and that instantly ages it. This is why you're better off with just official documentation for the stuff you're actually using. I don't know whether it's worth getting, or maybe skim for inspiration? Oh, here's a fun fact: sometimes completely reasonable questions, like how does something work, or what happens when you do something, are unanswerable, because nobody knows the answer. I mean SOMEONE knows the answer, but there's no way you'll get hold of those 2 or 3 people in the world, and some of them might be a good six feet under the ground. You'll just have to roll with whatever information you can get, or whatever you can find yourself by experimentation, with limitations that if the datasheets don't say that you're good, your conclusions might have a very limited reach. But still, as you may have found, following a boot camp or a tutorial tends to leave you with more questions than answers, this is why you ideally want to back it up with more fundamental approach. Ultimately i don't know how your brain works and which approach you may find more or less usable; but you definitely need to develop your ability to deal with primary documentation. My opinion though is that ARM Cortex M3 and M4 will possibly drastically lose relevance over the course of next 10 years, to the advantage of RISC-V. And to put things into perspective, 10 years ago, STM stuff wasn't actually a thing pretty much, you would rather see Freescale and NXP ARM devices instead. Cortex M-series won't outright disappear until maybe 20-30 years later, but i expect that it might no longer become the first choice in a few years. Anyway these kinds of things is why STM32cube isn't taught in university. Curriculum changes slowly, for example i was taught machine language on a VAX which was more then 25 years out of date by that point - and we were taught on whiteboard and paper, because they could never get their VAX machine actually going, for all we knew it was just a coffin with gubbins in it. University is not there to give you a hands-on skill that is immediately useful in the industry, it's there to give you the fundamental skill to acquire the skill that you need. From the university perspective, any knowledge that isn't transferable onto whatever other technology you might be later working with, is useless junk and might as well not be conveyed. In turn it's the industry's task to give you a working skill that you need, for example with an internship. Though nowadays, things are a bit different, the industry sometimes forgets about its educational obligation, and either just runs you from one internship to the other, exploiting young people for cheap labour, or hires people who acquired experience doing actual projects by themselves. Good luck!

Life did 🤣 I'm planning on trying to make some content coming up. I'll have a video explaining what's been going on and then what's going forward from now on.

@@ZygalStudios Cool! I’m trying to learn embedded systems myself since no one wants to hire me for an entry level job. I’ll take all the knowledge I can get!