Thank you so much for coming by and watching my USART receive using interrupts at the register level. I am grateful!! Enjoy and if you have any questions, please let me know.
Thank you so much for making these videos. This is very valuable information and its hard to come by someone who makes such detailed videos like you do. I went to college for mechanical engineering and have been in the field for about 3 years now but somehow I have drifted into learning programming since everything is taking a turn for automation. I started with arduino about 3-4 years ago and I wanted to learn the more fundamental aspects of embedded systems to that I can make my own project and try and sell it. Thank you for your hard work it is very much appreciated
"stayed"... and saw a few typos in your message 😉 I suggest you look into a multi-core MCU, like STM32H755 / STM32H757 and explain the true concurrent code running in two threads at the same time (not just emulated on a single core).
Great Video - as usual. Thank you! However @2:37 I have a question: I expect *three* Wires rather than two: RxD, TxD *and GND* . So wat is the reason you do *not* connect the very vital *GND* level as reference between the Microcontroller and the USBSerial Converter but just the signal lines? 🙄
In a different circuit that doesn't share the computer ground (ST-Link and USB interface), I will definitely connect the ground. The ground is being shared between the computer and the microcontroller via the ST-Link even though they are not directly connected. The computer is connected to the FTDI (USB interface) which has ground on that USB line and the ST-Link has a ground (both coming from the computer. If I built a circuit that did not use the same ground, I would need to connect the ground from the USB interface and the microcontroller. I will make this clear in the next video. Thank you for bringing it up.
Whenever I switch the MCU clock to 48 MHz, it becomes unresponsive and gets stuck during the clock configuration process. This issue occurs consistently. I'm using your development boards for this. To recover from this state, I manually hold the reset pin, initiate a connection in the CubeProgrammer, and then release the reset pin after around 3 seconds. This allows me to erase the memory and attempt the configuration again. Are there any insights into why this might be happening?
Are you connecting the AGND and AVCC? That MCU requires that those connections are made while using that configuration. I explain this problem in previous parts because I had the same problem.
I will be getting into DMA for all peripherals, including I2C. I really want to exploit the DMA as it doesn't need to bother the MCU process. DMA will allow a much better program flow and efficiency. Thanks for the comment. I am grateful!
