[HC32F460 Development Board Review] NO.1 Unboxing Introduction
[Copy link]
【Foreword】
I have reviewed the GD32E503 development board before and felt that it was very user-friendly. Since then, I have been full of confidence in the rise of domestic MCUs. This time, I was fortunate to apply for Huada's HC32F460 development board, and I have the opportunity to review another domestic 32-bit MCU again. I am very grateful to the original manufacturer and EEWorld.
【Arrival unpacking】
I was honored to receive the development board from HuaDa, and I couldn't wait to open the package. Although the packaging of this development board is not as exquisite as the previous GD32E503, and it is a bit overshadowed by the gift box-like shell, fortunately, the resources of this development board are very rich, and it suddenly looks very high-end and large, and the overall style is very similar to the board style of foreign company NXP.
The dark green double-layer board is small and compact. There are indeed many components on it, but it does not look messy. The layout of each peripheral is also reasonable, and 4 plastic fixing columns are specially installed. The hardware design is still very thoughtful, very good, and worth learning from! ! ! This just proves that the domestic MCU workmanship and service have begun to serve customers more refinedly! Huada's service is also very good at present. I also believe in domestic products and am willing to contribute a little bit of my ability to the use of domestic chips!
【BGI official ecosystem】
This is not the first time I have used BGI MCU, but I still want to share the known BGI ecological resources to help others find the right entrance at the first time.
Official resource link of Huada: https://www.hdsc.com.cn/mcu
Previously, the official resources of HuaDa were all placed on an FTP server, and you had to find an agent or the original manufacturer's support staff to get the download link. Now they are all placed on the official website. Currently, the official website of HuaDa covers a lot of files, from software and hardware design documents and library routines, to tool kits, to application instructions, etc. As an original manufacturer, it has taken the lead among domestic products.
Official resource link of Huada: https://bbs.21ic.com/iclist-616-1.html
This is the 21IC technical forum officially operated by BGI. It contains quite a lot of technical posts from domestic engineers and official information sharing sections. You can browse it when you have nothing to do and perhaps gain a lot.
BGI's Github: Just search "hdscmcu" on Github, but Github is very slow. It is recommended that the official switch to domestic Gitee or Gitlab later, and share and open source more meaningful projects.
Huada's QQ group: 228652096
It is recommended that after joining the group, everyone should concentrate on studying and sharing technology, and avoid spamming and chatting about empty things, which is not conducive to the growth and development of the domestic MCU ecosystem.
[HC32F460 development board resources]
HC32F460 is a high-performance ARM Cortex-M4F core general-purpose MCU from HuaDa Semiconductor, with 512KB Flash, 192KB SRAM, and a main frequency of up to 200MHz.
The main features of the HC32F460 series products are as follows:
The 40nm manufacturing process fully unleashes the high-speed computing performance of the Cortex-M4F, and the efficient Cache and Prefetch ensure CPU 0-Wait execution.
Fine-grained low-power management, CPU dynamic power consumption 80μA/MHz, power consumption as low as 1.8μA in Power down mode.
High-performance analog features (2 independent 12-bit 2.5MSPS ADCs, 1 PGA with adjustable gain 2~32 times, 3 high-speed comparators).
All serial communication ports (UART, I2C, SPI, CAN, I2S) can be freely mapped to 64 GPIOs, easily handling PCB board making.
Data security mechanism, comprehensive protection of user code, prevent unauthorized access to sensitive data and code brute force cracking.
Industry-leading anti-ESD, anti-Latch up, low EMI, 5V voltage-resistant I/O and other performance.
The main control of HC32F460-EVB development board is HC32F460PETB, which has ARM Cortex-M4 core, integrated FPU , MPU, 512KB Flash, 192KB SRAM, USB FS (Device/Host), 14 Timers , 2 ADCs, 1 PGA, 3 CMPs, , up to 83 GPIOs, up to 20 various communication interfaces , and the functions are very powerful. The following is the system block diagram of the main control:
The HC32F460-EVB development board has rich resources, including SWD and JTAG interfaces for simulation debugging, external Flash, eeprom, 3 independent buttons and 9 column buttons, and various communication interfaces. It has basically all kinds of peripherals, and there is also a black box that I have never seen before - smartcard module. I have never touched this before, and I can't wait to play with it.
The development board also comes with a wealth of entry-level resources, including all the resources designers need: software, hardware, documentation, toolkits, etc.
After getting all the files, I opened each one and read them. Here are my thoughts and opinions:
1. The archiving and design layout of the schematic diagram are really standardized. The homepage contains the version and function information of the document, and other modules are displayed and arranged in pages. They are combined together through the cross-page bus network connection form, which is a system-level schematic diagram;
2. In terms of programs, a DDL library is provided. It is said that there is also a lite library. I took a preliminary look at the DDL library routines. They are written in a very standardized and original style and can be used in engineering projects. It has changed the previous chaotic style. I didn't expect that Huada has grown very rapidly in the past six months and is doing practical things in a low-key manner;
3. Having mentioned two aspects that I agree with, let's talk about what can be done better. The board does not come with a BSP board-level support SDK package, and does not provide targeted functional test and verification routines for the board, which is extremely unfriendly to developers. A design that does not help engineers shorten the application cycle cannot be called a good design, and GD32 does this very well.
4. I opened a keil project and compiled it, but found it was very time-consuming. The reason was that I was still using the ARM AC5 compiler as the default option. I tried to switch to AC6 and tried to compile. Although I could compile successfully without warning, I found that the function was abnormal after downloading, which showed that the underlying driver library was not compatible with AC5 to AC6. Why do we need to use the AC6 compilation option? I think the development engineers know that the compilation speed and optimization level are more optimized than AC5. For MCUs with cores such as M3, M4, M33, and M7, adding a few more large peripheral applications will increase the amount of code. If we still use AC5, it will be a waste of time. GD32 also takes this into consideration.
5. There is no onboard CMSIS-DAP-Link debugger, and this review did not include a debugger, which seems to lower the grade a bit. Now almost all larger original development boards will come with a debugger.
【First experience of the function 】
The development environments supported by the HC32F460 series MCU are: IAR and MDK. I am using MDK here, version V5.30. There are many tutorials on the Internet for MDK installation methods. If you are installing and using MDK for the first time, you may need to install ARM's official library CMSIS, which can be installed in the MDK software, or you can go to the github repository https://github.com/ARM-software/CMSIS_5 provided by ARM to install it. After that, you need to install the chip support package. Huada provides chip support packages for IAR and MDK. There are 3 chip packages in MDK. Here I install the latest one.
Next, open the routine compilation and find the GPIO routine in the official HC32F460_SDK to turn on the light. After opening the project, you need to go to the Options for Target page and check Create HEX file. After successful compilation, a HEX file will be generated. This file will be used when the ISP burns the program.
Click Compile to view.
There are three ways to power the board, namely using two USB ports for power supply and DC_IN pin for power supply. There are two MicroUSB ports on the development board, one is used as a serial port to print out data, and the other is used as a USB port. Both can be used as power supply ports, but you need to use jumper caps to short-circuit J2 and J15 (shorted by default). You can also use a DC 5V power supply, connect TP1 to 5V, and TP3 to GND for power supply. The
HC32F460 development board can be used for software burning in three ways, JTAG, SWD, and ISP burning. I chose the JTAG method of J-link here, click Download, the program is burned successfully, and the marquee has lit up.
I am a little confused: after the first power-on at the factory, the OLED screen should normally display something, but mine does not display anything. I don’t know if it is damaged or if the firmware is not burned. I will do an OLED function evaluation to verify this later.
This is the beginning of the article. The next article will focus on the detailed evaluation of the onboard peripherals and official library routines. There are many resources for the HC32F460 development board. I hope that you can play with them all and contribute a little reference to the friends who come later.
|