When using STM32 for power conversion control, you are always 1uS from disaster. That's why I use "bare metal" programming rather than HAL. HAL seems like a complex abstraction layer that is removed from the basic spec sheet and programming reference manual. Am I wrong? Is HAL worth learning?
4 роки тому+1
I have used HAL in medical devices and was deemed as good library to use. The functions are larger than something like LL drivers, so when computing precision and fast functions are wanted, I would go for LL. I have not used any uC for power conversion control as I left those jobs to particular ICs so I cannot comment on that. I can just say that I have not experienced any problems with HAL. As far as usage goes, HAL and LL have similar structure of functions and actions. When translating HAL project to LL I find it very easy to do, certain functions are same in functionality.
Hey, im using STM32L0 discovery board and trying to do little intro project with 3 LEDs and 3 GPIO output pins, but only 1, PA0 pin outputs HIGH level, PA1 and PA2 doesnt respond. Maybe you know where is the problem?
3 роки тому+1
Hey, I mentioned this in my last video(38). Discovery boards are ment for learning so they can pack lots of onboard peripherals. This means that certain pins of microcontrollers are not free and can be connected to such devices. Usually PA0 is connected to a user pushbutton, just like on your board. I took a look at your board schematic, which you should download for these kind of things, and indeed PA1 and PA2 are connected to MFX_wakeup and touchsensor peripherals. This way, these devices can set hard states for the pin. Thats why you should search for a pin that is free as in only connected to uC. You can either search in board schematic or download your dicovery board users manual and on page 25 you will find a table for all pins and you want to find ones that have a label in collumn "Free I/O". I would advise you to change PA0 led to a free pin as well despite it working, because you could set a hard LOW state on the pin and if you would push the button by accident, a low resistance path would be created from 3v3 to GND through PA0 and thus destroying it, because pushbutton is directly connected to 3v3 rail. Hope this finds you well. I will make a video on this, looks like very important topic.
One more question, is that what a embedded developer like you basically do at work?
3 роки тому+2
This is a part of it. I do all tasks that concern an electronics engineer. That can be designing pcbs, soldering prototypes, debugging new or existing hardware, writing embedded code and python and of course research and learning. Its is a big field.
@ I am so curious. How did you learn embedded software and hardware design? I mean both of them are very big field. I have spent a lot of time to learn 8-bits microcontroller PIC and now still spend lot of time to learn programming with stm32 and never touch in hardware design. Maybe you could share some experiences, what was your plan to learn embedded, what should a newbie start to learn, should I learn software and hardware in the same time or firstly master software then do hardware and so on..
3 роки тому+4
I thik that there are two embedded paths, one is mostly software and algorothms, other is embedded hardware. The first one would be just writing software for fpga-s, dsp and the way of writing code does not change much from pc, just that resources are smaller. Hardware part is what I do on this channel and its about microcontrollers that bridge gap between high level world and low level hardware. Not just that, it provides expansion in form of dogital sensors and actuators that you couldnt use with just doscrete hardware. That said, you seem to have experience in coding, which is great, that part burns a lot of time for me. But if your goals are on embedded hardware, then I would suggest you start learning about electronics, there are lots of yt channels and websites. Most educated embedded engineers become that as electronics engineers because you have to understand electronics around the microcontroller in order to write code, choose ics and much more. Its not just about code. Learn dogital and analog systems, find good project where you are good at some things and unfamilliar at others. This balance will motivate you and once you design a few boards and use a bunch of different peripherals, you will gain lots of experience. With different projects, you will learn new skills on different areas, so dont worry if it looks a bit much. I for example have been learning and using c++ in embedded for last 4 months. Keep learning and making cool projects because that is the only way. Oh yea, and dont loose passion, that is the main driving force. I will post more videos around electronics and a few starting videos.
@ Thank you very much for your advices. It is very useful for newbie like me. Actually I study electronic and information technology. Basically, I have a little bit knowledge about electronic components and 8-bits microcontroller. But that is all I got from university. Thus, I have learnt by myself stm32 and maybe later msp432 from ti to fill the gap of knowledge. I also want to learn pcb design but it seems a strange topic for me. Your advice has encouraged me so much. Ja, stay turn and keep going forward.
3 роки тому+1
That's great. University will not be able to give you all the knowledge. I would suggest to try building projects on discovery boards and buy individual sensor/actuator modules (dont but sets, its a waste of money) and you will learn plenty. Start learning about hardware when you get more free time, design some analog/discrete component pcbs to learn, buy a breadboard, some components, draw pcbs and then integrate a microcontroller into a pcb. Don't pick too difficult project as you'll get demotivated. Cheers
Hey, which theme did you use for the IDE? It looks cool.
4 роки тому+2
It is Devstyle along with its icon pack(by default it is not checked at install time) with Darkest dark theme. I have custom syntax coloring from somewhere that is very close to jetbrains style, which I like.
Great video sir, very helpful
Hmm I have not known about that trace function, very cool. THX
Hi, firstly thank you very much for your very useful tutorial. Can you please make a tutorial for a custom stm32 board?
I will make one in the future, but for now I recommend Phil's Lab youtube channel, it has great content on this topic.
Superb !!
When using STM32 for power conversion control, you are always 1uS from disaster. That's why I use "bare metal" programming rather than HAL. HAL seems like a complex abstraction layer that is removed from the basic spec sheet and programming reference manual. Am I wrong? Is HAL worth learning?
I have used HAL in medical devices and was deemed as good library to use. The functions are larger than something like LL drivers, so when computing precision and fast functions are wanted, I would go for LL. I have not used any uC for power conversion control as I left those jobs to particular ICs so I cannot comment on that. I can just say that I have not experienced any problems with HAL.
As far as usage goes, HAL and LL have similar structure of functions and actions. When translating HAL project to LL I find it very easy to do, certain functions are same in functionality.
Hey, im using STM32L0 discovery board and trying to do little intro project with 3 LEDs and 3 GPIO output pins, but only 1, PA0 pin outputs HIGH level, PA1 and PA2 doesnt respond. Maybe you know where is the problem?
Hey,
I mentioned this in my last video(38). Discovery boards are ment for learning so they can pack lots of onboard peripherals. This means that certain pins of microcontrollers are not free and can be connected to such devices.
Usually PA0 is connected to a user pushbutton, just like on your board.
I took a look at your board schematic, which you should download for these kind of things, and indeed PA1 and PA2 are connected to MFX_wakeup and touchsensor peripherals. This way, these devices can set hard states for the pin. Thats why you should search for a pin that is free as in only connected to uC.
You can either search in board schematic or download your dicovery board users manual and on page 25 you will find a table for all pins and you want to find ones that have a label in collumn "Free I/O".
I would advise you to change PA0 led to a free pin as well despite it working, because you could set a hard LOW state on the pin and if you would push the button by accident, a low resistance path would be created from 3v3 to GND through PA0 and thus destroying it, because pushbutton is directly connected to 3v3 rail.
Hope this finds you well. I will make a video on this, looks like very important topic.
Sir do you hav any video for sensored 3 phase bldc motor control with stm32 cube or any link so i can get help thank you
Sorry, I haven't done much work directly with BLDC motors.
Thanks!
One more question, is that what a embedded developer like you basically do at work?
This is a part of it. I do all tasks that concern an electronics engineer. That can be designing pcbs, soldering prototypes, debugging new or existing hardware, writing embedded code and python and of course research and learning. Its is a big field.
@ I am so curious. How did you learn embedded software and hardware design? I mean both of them are very big field. I have spent a lot of time to learn 8-bits microcontroller PIC and now still spend lot of time to learn programming with stm32 and never touch in hardware design. Maybe you could share some experiences, what was your plan to learn embedded, what should a newbie start to learn, should I learn software and hardware in the same time or firstly master software then do hardware and so on..
I thik that there are two embedded paths, one is mostly software and algorothms, other is embedded hardware. The first one would be just writing software for fpga-s, dsp and the way of writing code does not change much from pc, just that resources are smaller. Hardware part is what I do on this channel and its about microcontrollers that bridge gap between high level world and low level hardware. Not just that, it provides expansion in form of dogital sensors and actuators that you couldnt use with just doscrete hardware.
That said, you seem to have experience in coding, which is great, that part burns a lot of time for me. But if your goals are on embedded hardware, then I would suggest you start learning about electronics, there are lots of yt channels and websites. Most educated embedded engineers become that as electronics engineers because you have to understand electronics around the microcontroller in order to write code, choose ics and much more. Its not just about code. Learn dogital and analog systems, find good project where you are good at some things and unfamilliar at others. This balance will motivate you and once you design a few boards and use a bunch of different peripherals, you will gain lots of experience. With different projects, you will learn new skills on different areas, so dont worry if it looks a bit much. I for example have been learning and using c++ in embedded for last 4 months. Keep learning and making cool projects because that is the only way. Oh yea, and dont loose passion, that is the main driving force.
I will post more videos around electronics and a few starting videos.
@ Thank you very much for your advices. It is very useful for newbie like me. Actually I study electronic and information technology. Basically, I have a little bit knowledge about electronic components and 8-bits microcontroller. But that is all I got from university. Thus, I have learnt by myself stm32 and maybe later msp432 from ti to fill the gap of knowledge. I also want to learn pcb design but it seems a strange topic for me. Your advice has encouraged me so much. Ja, stay turn and keep going forward.
That's great. University will not be able to give you all the knowledge. I would suggest to try building projects on discovery boards and buy individual sensor/actuator modules (dont but sets, its a waste of money) and you will learn plenty. Start learning about hardware when you get more free time, design some analog/discrete component pcbs to learn, buy a breadboard, some components, draw pcbs and then integrate a microcontroller into a pcb. Don't pick too difficult project as you'll get demotivated. Cheers
Hey, which theme did you use for the IDE? It looks cool.
It is Devstyle along with its icon pack(by default it is not checked at install time) with Darkest dark theme. I have custom syntax coloring from somewhere that is very close to jetbrains style, which I like.
exchange youtube channel