STM32 entry development board choose wildfire or punctual atom?

Both can be said to be industry benchmarks .

You can't say which is better , Have distinguishing feature each , It's the best to fit yourself , Peers refer to each other to do .

Let me compare from the following dimensions ：

1. course

2. Code

3. Development board price

4. Advanced

One 、 course

Both tutorials are completely open source , We have a lot of praise for the course of wildfire , The first few chapters explained very well from shallow to deep .

There are some c People who don't have a good foundation can keep up , Can understand STM32 The bottom layer of peripherals is also code secondary encapsulation from register configuration .

Some later chapters seem to have changed teachers , The explanation is more biased towards the actual project , From the perspective of beginners , Maybe it sounds a little hard , But death can also learn a lot .

In the case of a punctual atom, the opposite is true , The first few chapters may not be very friendly to novices , On the contrary, the second half is more suitable for beginners .

For beginners , In fact, we don't need to talk more deeply , The most important thing is to make you understand .

Two 、 Code style.

Wildfire's code macros have many definitions , Although beginners find it very difficult , Is not intuitive 、 But more rigorous , Generally, in the actual project development, this practice is conducive to program scalability and portability .

I think what netizens spray most is the punctual code , The code style is not suitable as a reference for actual projects .

I think , Anyway , Or that sentence ： It's important for you to understand , Don't cross the river and tear down the bridge .

Everyone's positioning is different , Since you are a beginner , Just getting started again STM32.

Don't worry about the code style , Program architecture , It's good to realize the function .

The first step is to try the function , The implementation process will certainly step on the pit , Then think about why ？ How to optimize the ？

You only go through this process , You have a better understanding of good code , Otherwise, your understanding will always stay on the surface .

like , You think it's professional to use pointer programs , In fact, it doesn't solve any pain points at all , Just pretend to force .

3、 ... and 、 Development board price

Development board price as a final consideration , There's a reason .

There is little difference between the two prices , On the whole, the quality of atomic development board is better than wildfire .

The quality is good or bad , Not the core issue , It must work normally anyway , It's just good or bad texture .

Now my development boards are eating ash in a corner , It's usually used in experiments , Just throw it away .

Four 、 Advanced

Through the development board , Basically, we can successfully break through the novice period , The rest is advanced , Is to achieve the level of independent function .

Don't expect the development board to make a qualitative leap in your level , The purpose of development board is to let you learn how to use MCU peripherals , That's it .

Learn peripherals , Doesn't mean you'll do the project , Because there is still a lack of Two abilities ：

1. Project thinking

That is to give you a functional requirement , What peripherals will it use ？ How to collect data ？ Or use some signal to control ？ How to realize the logic function by program ？

2. Programming level

When you have an idea , You also have to have a certain level of programming and write code to realize .

Of course , In the first few years of work , I basically just want to realize the function , No consideration of program architecture at all , Regardless of how well the code is written , Do not consider whether the customer needs to change the function later .

It's because of thoughtlessness , I suffered a lot , The direct embodiment is to often work overtime to change the code .

If the program architecture is good , These problems may be solved in a few minutes .

3. How to improve

Can only be accumulated through continuous projects , But there are no shortcuts .

The shortcut is to find a senior person to learn , Follow him on the project , Learn his project thinking and programming experience .

In this way, you can save a lot of time on your own exploration .

for instance , Same function , The novice's writing may be like this ：

The code structure of our endless MCU Course Project is like this ：

Although the essence is polling to execute , But the flexibility is obvious. We write higher , You can control the execution time of each function separately, and so on .

Last egg time ！！！

Recently, many little friends asked me for some MCU learning materials , Then I based on my ten years of experience , How many nights did you stay up , Carefully organize a 「 MCU introduction to advanced tutorial + tool kit 」, All free sharing to everyone ！！！

in addition to , Then share with tears what I pressed at the bottom of the box 22 A hot open source project , Include source code + Schematic diagram +PCB+ documentation , Let you quickly advance into an expert ！

It is said that there are small partners who have successfully entered BAT Big factory , So if you save it, you must study hard .

The tutorial package and detailed learning path can be seen at the beginning of my following article .

MCU entry to advanced open learning path ( Tutorial attached + Tools )https://blog.csdn.net/weixin_43982452/article/details/114134096