Видео

@artful bytes can you make vedio for linkerscrpit

Thanks for the video! Why did you switch to vscode? Is it possible to replicate it in stm32cubeIDE?

Thanks a lot for creating this video. I really learned something, and it helped me understand the issue behind one of my programs' failure. Thank you!

👏👏👏

i learnt more in these 30 minutes than in 3 years of studies - thanks a lot man

gold

TLDR: He never explains HOW a microcontroller starts. He only shows what the STMicro-controller does AFTER it is started. So basically a click-bait title (at the time of my comment: "How a Microcontroller starts").

Well sometimes you seem to skip explaination or skip focus on important things and spend time on unnecessary things... If this was nkt done then the imapct of the videos coukd have been way more ...But either way i will also say overall everything is very well put!

bro i need complete embedded system course please upload as soon as possible.

Is there a roadmap to do this I Alr know C nd some arduino

The content is great. However this is not an action movie, no need for fast cuts. This is a bit heavy topic, it'd be better to slow down a bit.

6:01 I think the SP is actually changing after the mov sp, r0 Amazing video so far, watching till the end.

Really nice content!

This is brilliant. I started watching embedded tutorials on ROS2, stm32 HAL, etc. Those toolchains are too bloated and cover up too many things under the hood, which is bad for learning. I love your approach and clarity.

just wow. very cool. 👍 will it run PHP tho 🤣

The value of sp increases from 0x200017f8 to 0x20001800 on running the first two assembly code lines. If estack was 0x20001800, then why was sp initialized by HW to 0x200017f8?

long time no see !!!!

Welcome back, keep uploading :)

It’s the most useful video i’ve ever seen. My life will never be the same. Awesome, please, do more like this. Maybe compile smallest linux kernel for stm32?🤓

Awesome!

Hi! Could you explain in more detail why you copy the values from adc_dtc_block to adc_dtc_block_cache once more? The way I understand it is your ADC finishes sampling the sequence of channels and once that is finished the DMA autonomously transfers data to adc_dtc_block without the processor having to be involved. Once this is done, it raises a DMA transfer finished interrupt, and then inside of that ISR, it transfers the values from adc_dtc_block to adc_dtc_block_cache. My question is, isn't this doing double the work and couldn't you just access the values directly from adc_dtc_block? I know in the video you said you didn't want the application to touch the same array the DMA is touching and my understanding is it's easier to briefly disable interrupts and access it from adc_dtc_block_cache than disable DMA or the ADC while trying to read from adc_dtc_block directly, but I'm not sure if I understood it correctly. Would appreciate any insight. Sorry for the all the questions, it's my first time getting deep into embedded and DMA has been quite confusing to get set up haha. As always the video series has been really enlightening and using it as a reference to do my own project has been a godsend! Thanks!

Your hands are doing constant sign language.

Can you do a long series like you did the past but with STM32 microcontrollers, I really wanted to write code on it from scratch, and understand all the concept MCU-related also, but I can’t find any suitable resources than yours. Thank you for bringing this such a nice educational videos!

The use of simple data types (such as uint8_t) and the direct manipulation of pointers and ISR function registration indicates your attempt to write code that is intended to run very efficiently on small, resource-limited Atmel microcontrollers. Rather than being called, inline functions are inserted directly at the call point, eliminating the overhead associated with calling the function (stack preparation, jumping to the function and returning). This can save several CPU cycles. As I wrote this is a good resource if you need to stuff a lot of code into a limited microcontroller.

Best explanation of interrupts I have ever seen! Please keep making such quality content.

Super informative! I do not work with embedded systems, but I found it fascinating to see how the start up process works here. Thank you!

9:38 Just curious what reason is there not to use -std=c23 every time?

So I am lost at 10:48, in the GCC tool chain folder, if I go to the included folder, I don't have the msp430.h file. Can someone guide me if I am doing something wrong? When I execute the command find -name "msp430.h". As per the video, I get only one path that is the first path in the video.

Watching the video in 2024 with my headphones in Ukraine. And could not distinguish at first either it's background noise from video or Russian rockets exploding in city I live. It appeared to be both

This is the type of content, I want to pay the internet bill for. Thanks a lot bro❤

Deep. Learned so much!

Hi! In 7:14, doesn't debug trace usually move forward in a program?

I programmed an STM32 for the first time 2 days ago. This really gave me a so much deeper insight into how these controllers work. Honestly loving how simple stupid it really is. I am also once again surprised and also not surprised that we can just use C to generate the startup assembly only using a few compiler flags.

These videos are a gem 💎 This will teach you lot more about embedded system than any beginner course on internet will do. Hat's off to you and thanks for doing it for the enthusiastic people like us. Really appreciate the efforts you made.. and Your video are vety detailed and interesting to watch.

This project just got me subscribed and liked. Thank you.

What Desktop Environment so you use?

Thank you for the amazing content 🎉

Amazing Video. Thank you for creating this.

I wish I could've seen this two years ago 😅

Great video! Two small notes: most recent controllers will actually run vendor code from a ROM before jumping into user code - you sadly can't debug that in many cases since the debugger gets enabled after that... What is done there? E.g. loading calibration values that must be loaded in all circumstances. And the other: even without linking the C standard library you may have to provide memset/memcpy/... since gcc will (at some optimization levels) replace loops with those functions - independent of command line flags

Nice to see this channel uploading again! Hope to see more content on low-level stuffs!

hi, can you please advise if the capturing of NEC pulses could also be achieved by using the capture mode of the 16-bit Timer?

welcome back for detailed teaching

simply wow

Excellent, very straightforward explanation that completely cleaned up my confusions. I'm trying to bringup my own programming language on RP2040, that was super helpful to me. Although I have a few questions about bootloaders: * how and where do they fit into the whole picture * why someone would need one * how to deal (or not) with them from the point of view of writing everything from scratch. Basically how to write a barebones C program that will work under a bootloader.

Amazing video! Great work!! I learned a lot!

Very clearly, thanks man. I also devevop the bare metal embedded at the MCU company. This is very valuable lesson.

I have stm32 bule phill it comes under arm Cortex m3 architecture I but doesn't reach main it goes half fault . I don't where the mistake is where any problem in openocd

Can you make video about make files for stm32.

Eu não entendi nada, mas entendi tudo. ótimo trabalho amigo.