4276 views|1 replies

288

Posts

0

Resources
The OP
 

MM32F103 Development Board Evaluation: Unboxing and Environment Setup [Copy link]

This post was last edited by yangjiaxu on 2018-10-29 21:57
I am very happy today and honored to apply for MM32. Thanks to the trust of EEWORLD forum and the support of new driver. I have been in contact with MM32 before. To be honest, it is very fun, and the official technical support of MM32 is also very good, so I am very happy to apply for the board this time. Without further ado, let's open the box first.
Figure 1 is the front of the MM32F103C8T6 board. It is very delicate. All peripherals are led out with double-row pins with a spacing of 2.54, which is convenient for testers to develop. Figure 2 is the serial port part. The U-to-serial chip - CH340 is used in the serial port part, so that it can communicate with the computer. Jumpers are used for selection during the process. The CH340 U-to-serial converter can be used alone. It is quite thoughtful.
Figure2 Serial port part
Figure 3 is the ADC part. There is no hardware representation on the board, so we can look at the schematic diagram - Figure 4
Figure3 ADC part
Figure4 ADCSchematic diagram part
There is also a more important place, the D2 indicator light. On the board, the D2 indicator light is not connected to PA8. If you want to use it, you need a jumper cap to short it, as shown in Figure 5.
Figure5 Short circuitPA8Pin part
Figure 6 is the back of the board. The back is relatively simple, without the placement of components. It only prints the company logo, website, board name and pin silk screen of NewDrive. This pin silk screen is quite considerate, so you don't have to look at the pin position in the front.
Figure6 Back of the board
After briefly introducing the board, let's start to build the development environment. The development environment used this time is keil 5.25 FOR ARM. The work that needs to be done is:
1. Download the keil development environment and install it. I won't go into details here. 2. Download the MM32 PACK support package, which is in the MM32F103 data .RAR file package shared by the community, or you can download it from Keil official or Lingdong Microelectronics official. I won’t go into details here. 3. Use the downloader and corresponding driver. I use the MM official downloader here, so you need to download the corresponding driver (if you are not using the MMLINK emulator, please ignore step 3 and refer to step 4). Download the MM32-LINK Debugger driver package_Ver1.1.0 from the Lingdong Microelectronics official website, and double-click to install DriverSetup4Win7_WinXp.exe and KEILSetup.exe. After both are installed, plug in the MM-link and a virtual COM number and MM32-LINK will be displayed in the computer--device manager. This means that the driver has been installed successfully.
4. In the keil software, open Project -Options for Target projectgroup – Debug – Select the emulator selection option and there will be an additional MM32-LINK Debugger option. Select this to use the MMLINK emulator (if you are not using MMLINK, you need to select the corresponding emulator option). Select MM32F103 128KB flash in flash download to configure the environment.
After completing the above steps, you can use the MM32 development board smoothly. The following are screenshots of the compilation and photos of the board working.
Interface of compilation and downloading
Board working status display

1.png (949.67 KB, downloads: 0)

1.png
 
 

288

Posts

0

Resources
2
 
I finished writing it a long time ago, but forgot to save it as a draft and forgot to publish it. I was so embarrassed. Why didn't I get a single click? Hahahaha
 
 
 

Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号
快速回复 返回顶部 Return list