M4 MCU, 120MHZ, 1M flash, 256kb ram, compared with my common 8MHZ, MCU，1KB ROM，+128BYTE RAM， It's so strong. Even compared with the used STM32, it is much better.

First of all, let's put up the unpacking drawing.

The package of the K64 development board is very simple. Open the package to see a development board and a small resource specification. Various pin descriptions and interface definitions fully reflect Freescale's style as a big factory, which is worth praising.

The following parts are not too many, and the interface distribution is also reasonable. However, I think the manufacturer has made too many jumpers and other things on the PCB in order to consider the difference between too many use targets, which makes the overall feeling a bit messy, not neat and beautiful. However, for use, it is still practical, and there is nothing wrong with it. It is estimated that designers also want to achieve a big and comprehensive goal, but in reality, product design is always faced with a compromise choice, and it is impossible to achieve all the possibilities in one thing.

The interface definition, jumper definition and various PIN pin numbers on the back of the development board are also very detailed, and the designer is really careful.

On the left is a comparison of a small board of USB products. In fact, this board is small enough, only half a slap in the face.

After I finished downloading various resources, the installation process was also very tortuous. The compatibility of KDS IDE in XP system was a big problem, and the resource requirements were too high. I lost my temper with 2GB memory and cards. After KDSK1.3 was installed, there was another problem with the IDE. I installed the IDE and KSDK twice, and it took a day to fix it, but another problem occurred, It was found that the company's computer did not recognize the virtual serial port, and only the 1M drive letter appeared. After trying various online methods, there was no solution, so we had to use online MBED to play this. It was really painful not to debug online..

KSDK is very complete. All kinds of underlying interfaces are encapsulated in it. It is also very convenient to use.

For example, IO settings can be directly selected from the following tabs. You can easily configure them without reading the manual, and you don't have to initialize various REGs yourself.

Resource requirements are too high. It takes one minute and 38 seconds for a computer to compile an LED flash. I'm really drunk.

I don't know what the problem is when I encounter a problem that cannot be debugged. I have tried many times, but I still don't think so. Recently, the project has also been completed as soon as possible, so I don't have time to go deep into it.

MBED online IDE, which has not been contacted before. The bottom layer is also encapsulated. It has an API directly related to K64F resources, which is also very useful. After writing the code, directly download the compiled file and directly put it into the MBED disk to burn and run. First, write a DEMO with flashing LED. The board is in the company, but the picture has not been taken.

Rich resources and comprehensive interfaces are a perfect platform for developing intelligent hardware.

Recently, the company has been working overtime on projects, and I haven't been to Lei Feng for a week. Ha ha, let's stop here.