It's a bit difficult for me to sort out the order, so I won't do it. I have a lot of boards on hand.
When I wrote that blog before (without taking photos), I simply sorted out at least ten boards, which was really terrible.
I don't have any interest in tinkering with new boards, so basically every board I bought has a purpose.
So, each development board has a story, or a purpose.
Let's go through them one by one, starting with the sofa.
This is a very ordinary stm32f103 board.
I got it at first when I was tinkering with rc522 with KDY Baiding and others.
But it was a rip-off.
Now that I think about it, at that time, KDY didn't seem to let me figure out the password, and I didn't ask him what to do specifically - I mean, I didn't have to figure out any password mechanism myself, that was relatively more complicated, and I got a little confused in the end. I
didn't continue because I was distracted.
But now that I think about it, I don't seem to have ever figured out what KDY was going to do specifically?
In fact, in the past year, I have chatted more with the three of them, and the other one is QQ in the discussion group, so we can be regarded as forum friends with more exchanges of ideas. Although I have my own ideas about some things and I don't plan to change them, I have to say that when I face them, especially KDY, I often feel that I am a failure~
Forget it, what's the lesson...
The picture above
Later, I used this board as a verification board.
Because I personally don't know how to use 103. First of all, this series is very old. No matter in terms of price, it has no advantages. In terms of performance and cost performance, it is also mediocre. Personally, because I focus on node applications such as WSN, I prefer the cost-effective and relatively large storage space of stm32f030 or 0x0.
But I have long known that F1 is the earliest mainstream series launched by STM32, so almost all the main routines are based on it.
Especially for some things like lwip contiki freertos, the routines for stm32 that can be seen are based on it.
Therefore, keeping such a board, for me, can be used to verify many routines I have obtained, as a starting point for porting to f0 or f3.
Of course, even if it is not because of RC522, I will get a board back for backup. However,
this board does not lead out all IOs, and the wiring is also very casual, which is very uncomfortable to use. So when I was working on enj28c60 this time, I thought about it and decided to buy another core board on Taobao last night.
The reason I bought the core board was because it was just for verification, and it was too expensive and unnecessary.
As for which model to choose, I chose vet6, the same as the battleship of Zhengdian Atom, because the information and routines it provides are really numerous and detailed.
The other two so-called second and third are far behind it. Like Wildfire, the tutorial of this enj28c60 is not detailed enough, and people have to buy books, so I gave up directly.
stm32f3 board
First picture
In fact, if you are familiar with the stm discover series, many people will know that this is the stm32f3discover board when they see this picture.
Yes, it is the board with a 3D gravity sensor and an acceleration sensor.
As for this board, I haven't used it much yet.
However, it also helped me a lot when I was working on GNU-ARM.
At that time, I didn't know how to modify the makefile, and the makefile of the routine provided in the software was too complicated. I also tried to find other third-party libraries and third-party tool chains. The same was true when I was at a loss.
I tried to search on github, and I really found one, and it was unbiased, it was for this board.
So far, I have solved this problem, and based on that makefile, I modified it into a makefile that can be used for other stm32 chips.
At first, I made this board, actually without any special purpose, just because I was very interested in gravity sensors and acceleration sensors at that time, and I heard that this board has them, and then this board was actually introduced to me by a friend who is an STM32 agent.
But now I am mainly working on stm32f0.
These boards are basically put aside and not used for the time being.
But they have other uses. I wonder if you noticed the jtag port adapter next to the board.
Yes, I have a stm32f103 board, but I hate jlink, so I often use the SWD interface of this to download the emulator.
This small adapter board is very useful. It has JTAG 20-pin, 10-pin, 8-pin and SWD. Very convenient.
Next is a stm32f030 board.
The development board is the core board, which is also what I use to DIY my mobile phone. For this reason, I built it on an expansion board made of a universal board.
About this board
1. This is the board I use most at present. No matter FreeRTOS, Contiki, or lwip, I will eventually port them to this chip.
There is no special reason for choosing this board and this model of stm32.
The main reason may be that it belongs to the 030 value series.
Its RAM is as high as 8K, and FLASH is as high as 64K.
This capacity makes me feel that the cost performance is quite high.
I mentioned earlier that because I am more concerned about node applications, I am destined not to use any high-end models. Including the STM32F3 with a main frequency of up to 140M.
This expansion board is mainly for mobile phone DIY.
So there are some very basic components, a 12864 (actually I regret this now). Because I am used to 320×240 tft, and from the current situation, 12864 basically has no special advantages.
The other is an ordinary matrix membrane keyboard.
Unfortunately, it is not the 12-digit pound sign and asterisk + five-way key commonly used in mobile phones, but this is not a problem.
The one at the bottom is the nrf24l01 wireless module that I added later.
By the way, there was originally a GPRS module on this board, but I took it off temporarily because I am currently working on a 12864-based UI.
This is useless and it is quite a nuisance when placed together (I will post a separate picture of it later).
(It was originally installed near the nrf24l01 module, where I opened four screw holes)
Next is the gprs module I mentioned earlier that I temporarily removed, based on SIM900A.
This module can be said to be the most shameless and rubbish module I bought on Taobao.
First, the picture
To be honest, because I am less and less interested in hardware modules (all my energy and interest have turned to software)
, most of the time I choose to buy ready-made hardware directly (which is completely different from the RMB in the development board exchange group, loftap and others)
. I have talked about why and how I chose this module in several posts on mobile phone DIY.
But what disappointed me was that
this board was really poorly made, and it was not a copycat, or the problem of not washing the board, or the wiring was messy, but the implementation of the basic circuit was very bad.
On this board, you may have noticed the heat sink, yes, that was the circuit I made later to generate 4V power.
The SIM900A module is indeed strange enough.
However, because I don’t know the hardware of GPRS modules, I won’t comment.
I just think that its power supply requirement of 3.8V to 4.4V is very bad.
3.8V, even lithium batteries can’t power it, 4.4V. It just won't let me go up to 5V, so a lot of adapters or USB can't be used directly (of course, they are all GPRS modules, and you still use USB, so forget it.)
And the module I bought originally allows 5V output, what's the situation? At first I was quite touched (but I didn't look at the specific SIM900A electrical parameter table at that time, because my logic was that I bought it ready-made, and I was asked to pay attention to these, isn't it a waste of my time?).
I didn't expect that I was half-dead by it.
I can't remember the specific reason, anyway, in the end I found that the reason was that I input 5V to it, and basically the whole module didn't work properly.
AT didn't respond normally.
Later, I checked the electrical parameter table myself, and then measured the actual connected voltage, damn it was not right.
Finally, I looked at the power supply circuit for a long time, and found that it actually used two diodes to reduce the voltage for me. Haha, one diode drops 0.7V, right, two diodes are 1.4V, right, and 5V is added up to 3.6V. 3.6V can be used. Damn, it's too bold, who told him to reduce the voltage like this...
I remember that it was fine when I used it under normal low current conditions, such as taking power from the USB port.
But once I used a 2A current adapter, it didn't work because the current was too high, and the voltage to the module was wrong, which made me suffer so much.
So, there was nothing else to do, I made a 4V power supply for it with 317.
Given that it was so bold that it could mess up the power supply for me, I couldn't believe its microphone and speaker circuits even more, but the mobile phone DIY made me procrastinate too much, and now I don't have the confidence and energy to realize all the functions of an ordinary mobile phone, so I don't care about these functions.
Next is a small development board that I put together with the modules I bought.
The main control is the smallest package of the stm32f030 series, and I don’t remember the specific model.
The other one is the nrf24l01 for wireless communication.
This board is related to the DIY mobile phone board just now, which is a pair of wireless transceiver modules.
I made this thing just to use it for node networking.
I use nrf24l01 for wireless, and I originally planned to make 485, but it was quite troublesome to use a multi-purpose board to add the module, so I gave up after I finished 24l01. What’s more, there is no software written for this thing.
Front
On the other hand
Next is a stm8s105 discover
This is the main board I used when I was using stm8s.
So I added a lot of pin headers and a flash chip sst25vf080 to the second half of the universal board
.
Later, there was an opportunity, and a friend asked me to try to make something for him (but it turned out to be a failure).
That was the only time I made a board so far.
But the project turned out to be a failure.
The main reason was that this friend and I didn't know much about the specific things we were going to do.
He only had a very empty idea: he saw something similar about irrigation in Israel, and he wanted to try it (the things he made were used to verify whether this idea could be done in the early stage.)
And I still understand electronics, but I don't understand specific machinery - so when I asked him about the specific situation of the equipment later, we couldn't talk.
And later I also found that he didn't think much about this matter.
Later, I also encountered a lot of trouble when choosing the corresponding sensors. In the end, there was no way, and this matter was shelved.
Next is the CC430 launched by TI MSP430,
which is actually MSP430+CC2500.
BTW, this CC2500 is just an RF transceiver module, which is now the so-called on-chip integrated radio frequency device.
But it is actually in the same vein as the later CC2530, except that the latter is a SOC that not only has RF transceiver, but also a single-chip microcomputer core.
There is so much to say about this thing.
So much that I don't know how to say it, and I am even worried that I might accidentally fall into the embarrassing situation of being sentimental and always aiming too high but not doing anything.