[Shanghai Hangxin ACM32F070 development board + touch function evaluation board] Development environment construction and initial experience

qinyunti

[Shanghai Hangxin ACM32F070 development board + touch function evaluation board] Development environment construction and initial experience [Copy link]

 

演示视频

refer to

Hangxin Data-F070 Development Board & Touch Board Introduction, LCD Board Schematic.rar\ACM32F0x0_FP0X Series Chip Development Quick Start V0.5.pdf

Prepare

Connect the TYPE-C USB cable to the computer, and the device manager can see the COM devices and USB compatible devices.

Otherwise, refer to ACM32F0x0_FP0X Series Chip Development Quick Start V0.5.pdf to install the driver

Install MDK, this step is omitted.

Double-click the firmware library\Aisinochip.ACM32F0X0.1.0.1.pack to import the chip database into MDK.

Unzip ModulesDemo_Rev2.0.2 in the firmware library

Double-click ModulesDemo_Rev2.0.2\LCD_TK\demo\MDK_Project\Project.uvprojx to open

Project Configuration

Right click on the left Project->Options for Target 'Project'...

Select chip model

Confirm the emulator connection

Burning algorithm

Automatic configuration, confirm as follows, if not add it manually

Specify the pre-emulation burn as follows

Startup Mode

Short-circuit J8 and pull BOOT0 low to enter eFLASH boot mode. Otherwise, it is ROM boot mode.

By default, it is pulled low. We download the program to eFLASH and boot from eFLASH.

Compile

Simulation Run

Menu bar Debug->Run full speed run

You can see the display

Various simulation operations are no different from using STM32, and the experience is good.

Code structure overview

To facilitate subsequent development, first take a look at the code structure.

Startup_ACM32F0x0.s

Reset_Handler is the program entry

First call System_ACM32F0x0.c

System_Core_Config initializes the underlying

Then call the entry __main provided by the compiler

Initialize the C runtime environment

Finally, call main.c's main

Then

Initialize the system

System_Init();

\Core_Drivers\HAL_Driver is the peripheral library of the chip.

Summarize

The development environment support is good, the support for MDK is perfect, and the simulation debugging is no different from developing STM32.

The firmware library provided is also relatively complete and standardized.

lugl4313820

The development environment support is good, the support for MDK is perfect, and the simulation debugging is no different from developing STM32.

The firmware library provided is also relatively complete and standardized.

It seems that this development board is good for getting started, and the manufacturer's Keil package is also powerful.

freebsder

Thanks for sharing, looking forward to the follow-up!

eew_rgzc15

Thanks for sharing. I'll buy a set to learn from when I get a chance.