I am so glad I found this! I am studying electronics and embedded development by myself and this material is helping me a lot. The way you explain things is very charming and keeps me focused. Your English pronunciation is very clear as well, I love it. I also watched your recent videos about the xv6 OS and I gotta say they are superb! I am learning a ton. Keep it up, buddy. Best wishes.
This sounds awesome! How much C do you have to know in order to be able to follow along? I am well-versed with multiple other languages but have never done any low-level programming, so I've never touched C before.
Aiming for: if you know some other programming languages, and are comfortable with some of thr other things I've covered on the chanel, then you'll be able to pick it up along the way! I'm trying to explain any C specific things that come up.
This is a goldmine, thank you SO SO much for this course! It's exactly what I hoped to find. Just ordered my board and so excited to jump in when it arrives.
Watching with curiosity. I really do enjoy seeing low level implementations laid out cleanly, makes understanding what's going on at higher levels far more clear too. I'm also gonna be especially interested in the "signed firmware" bit, as I regularly get frustrated with locked-out devices that the IoT industry churns out. Very curious how far these devices actually go to prevent updates.
How about I follow this series using my custom cpu instead of an stm32? ;) In all seriousness, I have high hopes for this series, can't wait for this to unfold.
I think it sounds like a great plan haha I don't know how close your architecture comes to Cortex-M, but I'm sure that the broad conceptual strokes will be applicable to any platform. Let me know if you do end up trying that - I'd love to see the progress/result!
Just got recommended this video and I want to follow along, only know powershell and some python. Would i be able to do this on : "ST LINK Stlink ST-Link V2 Mini STM8 STM32 Simulator"? Since I cant find the board youre using on any stores in my country I have to order from ali express.
I don't know about that item, though it doesn't sound quite right. If I search aliexpress for "nucleo stm32", I see several development boards for cortex m4. Even if they don't look the same, you should be able to use one to follow along. Amazon usually stocks multiple different kinds of nucleo, and you wouldn't need the exact board that I have. Anything with a cortex m3 or m4 should be fine. As for programming experience, I'm trying to explain any C specific concepts I come across, so if you're comf9rtable with the essential programming ideas, you'll be alright 👍
I was really intrigued by the prototyping connector you used for programming the STM32 with a J-Link instead of the ST-Link. Could you please provide more details about how you set up this connector? I'd love to replicate it for the project Series. Thanks in advance for your help!
Maybe I will put together a schematic, but in essence, all I've really done is to break out all of the pins on the nucleo that are used for debugging (the SWD pins) out on to a set of headers that match the pinout of the jlink. I did later break out the uart port as well, just because having a dedicated connector is much nicer that having a bunch of jumpers all over the place.
@@LowByteProductions My current setup is to map the Jlink pins directly to the SWD pins on the ST-Link section of the board and power the board via the USB on the ST-Link section. However, I'm also curious as to how you connect the Jlink pins directly onto the 'main' section of the board to facilitate both flashing and powering of the board without the ST-Link. I assume it involves connecting the 5V pin from Jtag to Vin on board and fussing with solder bridges? The UART break out would also be nice to see
The black pill would work fine for this series. You might need to make a few adjustments in the makefile and/or linkerscript to ensure the right CPU and amount of memory are specified.
OK, its the weekend and I am starting off at quarter to midnight on a Saturday. Just finished episode 0 and already popped over to Mouser and bought the Nucleo board. Only $14 and I needed to buy a few things anyway! Should be here Tuesday to have a play around with! Off to episode 1! Thank you again for all of this!!!
hmmm i guess 5 dislikes were having a very bad day xd. thanks alot sir for sharing you knowledge with us, i cant wait to finish all of it 🙏🙏do you suggest books or certifications!
It's a cortex m3, but most things will translate. You will have to make little changes here and there (clock configuration, for example), but it's not too much. So yes, you totally can.
Love this! I was a ASM programmer for PIC microcontrollers in the early 2000's and it rendered me a nice career. I still miss those days, now working with cloud code...
Blue pill is an M3 if I'm not mistaken? Still, certainly a viable board to follow along with. In both the blue pill case and the NXP, I guess a fair few changes will be needed, but thats part of the fun!
Hey man, i love the kind of content that you do on this channel and I was wondering what kind of degree can help me learn more about stuff like this? Do I even need a degree? And if you don't mind me asking if you have a degree, what is it in?
Thanks for the kind words! I'll answer your second question first: No you don't need a degree! You can absolutely learn all of this kind of stuff and more completely independently, using free resources and readily available books. Self directed learning can be tricky - especially in the beginning - but it is 100% possible. That is in fact how I've learned pretty much everything I know about embedded. I will temper that by saying that I'm not claiming university to be worthless, however. I did get a degree in Game Design, and I loved every minute of it - mostly for meeting so many interesting people, and collaborating on projects. You learn a lot in lectures and through the course material, but you end up learning so much more from each other. If you have the time and money, I think it can be worthwhile. As far as choosing a degree that would bring you into these kinds of subjects, computer science is of course the quintessential subject. If you're going to study CS somewhere, just take the time to see what courses the degree offers. Not every CS course will get you into low level hardware, but plenty will. There are also degrees in Embedded Engineering, where you'll learn a (hopefully) equal mix of hardware and software, with the goal being that you can fully understand and build entire embedded systems. There's also Electrical Engineering. Of course, with EE, the focus is on the hardware first and foremost - but there are many paths into software from there. Just keep in mind that EEs tend not to be the best programmers (not to be controversial). In my experience, they don't really like to spend much time thinking about the broader areas of software like design, architecture, maintainability, abstractions, interfaces, etc. Another often overlooked area of study is mechatronics, where you learn about mechanical engineering, electrical engineering, and software engineering, with the goal of building complete systems (think industrial robotics etc). From what I know from others that have studied it, it usually has a very practical focus, gets you into the guts of low level systems, and has you solving a wide range of problems. I hope some of that can be of help to you. Best of luck with your future studies!
I am so glad I found this! I am studying electronics and embedded development by myself and this material is helping me a lot. The way you explain things is very charming and keeps me focused. Your English pronunciation is very clear as well, I love it. I also watched your recent videos about the xv6 OS and I gotta say they are superb! I am learning a ton. Keep it up, buddy. Best wishes.
same for me hahaha, thanks a lot
me too guys🎉🎉
Precisely what I was looking for! Thank you for this series! :)
Glad to hear it!
looking forward to this series!
this is good, so much to learn here.
Great stuff! Watching now, can't wait for the rest!
thank you for this series
Thanks for this series man🫡
Thanks f9r this bro I really really appreciate
Can't wait for next video
Just ordered a STM32Nucleo and this video popped up on recommendation, what a coincidence :)
Awesome, hope you'll be able to follow along!
This sounds awesome! How much C do you have to know in order to be able to follow along? I am well-versed with multiple other languages but have never done any low-level programming, so I've never touched C before.
Aiming for: if you know some other programming languages, and are comfortable with some of thr other things I've covered on the chanel, then you'll be able to pick it up along the way!
I'm trying to explain any C specific things that come up.
Cool talk
Thanks
best mcu programming course I see until now that explains correctly how to program a mcu Sci without library.
This is a goldmine, thank you SO SO much for this course! It's exactly what I hoped to find. Just ordered my board and so excited to jump in when it arrives.
So how was the journey?
@@newb_embedded040 Moved across the country and pivoted to a different hobby, wish you luck if you're starting yours!
Thin abstraction layers, Avoiding CubeMX and shouting out to James Sharman... sounds good to me.
Watching with curiosity. I really do enjoy seeing low level implementations laid out cleanly, makes understanding what's going on at higher levels far more clear too. I'm also gonna be especially interested in the "signed firmware" bit, as I regularly get frustrated with locked-out devices that the IoT industry churns out. Very curious how far these devices actually go to prevent updates.
How about I follow this series using my custom cpu instead of an stm32? ;)
In all seriousness, I have high hopes for this series, can't wait for this to unfold.
I think it sounds like a great plan haha I don't know how close your architecture comes to Cortex-M, but I'm sure that the broad conceptual strokes will be applicable to any platform. Let me know if you do end up trying that - I'd love to see the progress/result!
I don't know how to thank you.
I just applied for a software embedded developer job and your videos are worthy like water for me
Thank you for your time and effort! This is a great series to watch even for an embedded developer used to proprietary tools.
Just got recommended this video and I want to follow along, only know powershell and some python. Would i be able to do this on : "ST LINK Stlink ST-Link V2 Mini STM8 STM32 Simulator"? Since I cant find the board youre using on any stores in my country I have to order from ali express.
I don't know about that item, though it doesn't sound quite right. If I search aliexpress for "nucleo stm32", I see several development boards for cortex m4. Even if they don't look the same, you should be able to use one to follow along. Amazon usually stocks multiple different kinds of nucleo, and you wouldn't need the exact board that I have. Anything with a cortex m3 or m4 should be fine.
As for programming experience, I'm trying to explain any C specific concepts I come across, so if you're comf9rtable with the essential programming ideas, you'll be alright 👍
I was really intrigued by the prototyping connector you used for programming the STM32 with a J-Link instead of the ST-Link. Could you please provide more details about how you set up this connector? I'd love to replicate it for the project Series.
Thanks in advance for your help!
Maybe I will put together a schematic, but in essence, all I've really done is to break out all of the pins on the nucleo that are used for debugging (the SWD pins) out on to a set of headers that match the pinout of the jlink. I did later break out the uart port as well, just because having a dedicated connector is much nicer that having a bunch of jumpers all over the place.
@@LowByteProductions My current setup is to map the Jlink pins directly to the SWD pins on the ST-Link section of the board and power the board via the USB on the ST-Link section. However, I'm also curious as to how you connect the Jlink pins directly onto the 'main' section of the board to facilitate both flashing and powering of the board without the ST-Link. I assume it involves connecting the 5V pin from Jtag to Vin on board and fussing with solder bridges? The UART break out would also be nice to see
share the source to code to program using inbuilt stlink
It's in the repo
Instant subscription!
Would it be a hindrance to have the “black pill” form factor of this microcontroller?
The black pill would work fine for this series. You might need to make a few adjustments in the makefile and/or linkerscript to ensure the right CPU and amount of memory are specified.
OK, its the weekend and I am starting off at quarter to midnight on a Saturday. Just finished episode 0 and already popped over to Mouser and bought the Nucleo board. Only $14 and I needed to buy a few things anyway! Should be here Tuesday to have a play around with! Off to episode 1! Thank you again for all of this!!!
Good work, keep it up!
hmmm i guess 5 dislikes were having a very bad day xd. thanks alot sir for sharing you knowledge with us, i cant wait to finish all of it 🙏🙏do you suggest books or certifications!
Sir, Can I follow this series while my development board is the stm32 blue-pill?
It's a cortex m3, but most things will translate. You will have to make little changes here and there (clock configuration, for example), but it's not too much. So yes, you totally can.
@@LowByteProductions Thank you so much, sir!
What are the major differences between STM32F7 and STM32H7 ?
This is exactly what I am looking for! I had a course with ATmega16 and we were only allowed to use assembly. This feels like a great next step!
Can i follow along with a STM32 Blue pill?
Finally someone who doesn't use HAL
First comment! thanks for the content
Love this! I was a ASM programmer for PIC microcontrollers in the early 2000's and it rendered me a nice career. I still miss those days, now working with cloud code...
😢. what do cloud programmers do? i guessyou still write c or rust?
How much extra complexity would it involve in case I have a board with Cortex A-9 Multicore CPU board.
A lot
Sounds like "The Blue Pill"... i am using NXP Cortex M7... its a beastly little guy.
Blue pill is an M3 if I'm not mistaken? Still, certainly a viable board to follow along with. In both the blue pill case and the NXP, I guess a fair few changes will be needed, but thats part of the fun!
Thank you soooo much!
🤍🤍🤍🤍🤍🥇🥇🥇🥇🥇
Hey man, i love the kind of content that you do on this channel and I was wondering what kind of degree can help me learn more about stuff like this? Do I even need a degree? And if you don't mind me asking if you have a degree, what is it in?
Thanks for the kind words! I'll answer your second question first: No you don't need a degree! You can absolutely learn all of this kind of stuff and more completely independently, using free resources and readily available books. Self directed learning can be tricky - especially in the beginning - but it is 100% possible. That is in fact how I've learned pretty much everything I know about embedded.
I will temper that by saying that I'm not claiming university to be worthless, however. I did get a degree in Game Design, and I loved every minute of it - mostly for meeting so many interesting people, and collaborating on projects. You learn a lot in lectures and through the course material, but you end up learning so much more from each other. If you have the time and money, I think it can be worthwhile.
As far as choosing a degree that would bring you into these kinds of subjects, computer science is of course the quintessential subject. If you're going to study CS somewhere, just take the time to see what courses the degree offers. Not every CS course will get you into low level hardware, but plenty will. There are also degrees in Embedded Engineering, where you'll learn a (hopefully) equal mix of hardware and software, with the goal being that you can fully understand and build entire embedded systems. There's also Electrical Engineering. Of course, with EE, the focus is on the hardware first and foremost - but there are many paths into software from there. Just keep in mind that EEs tend not to be the best programmers (not to be controversial). In my experience, they don't really like to spend much time thinking about the broader areas of software like design, architecture, maintainability, abstractions, interfaces, etc. Another often overlooked area of study is mechatronics, where you learn about mechanical engineering, electrical engineering, and software engineering, with the goal of building complete systems (think industrial robotics etc). From what I know from others that have studied it, it usually has a very practical focus, gets you into the guts of low level systems, and has you solving a wide range of problems.
I hope some of that can be of help to you. Best of luck with your future studies!
@@LowByteProductions Thank you so much for the response, it really helps out