Shanghai Hangxin ACM32G103 development board study notes 01 (build the development environment of ACM32G103 and master the development board schematic diagram)

qzc0927

Shanghai Hangxin ACM32G103 development board study notes 01 (build the development environment of ACM32G103 and master the development board schematic diagram) [Copy link]

 

## ==Shanghai Hangxin ACM32G103 Development Board Study Notes 01 (Building the development environment of ACM32G103 and mastering the development board schematic)== ## ==1: Overview of development board resources== 1. MCU: ACM32G103RCT6, LQFP64 (10mm*10mm), FLASH: 320KB, SRAM: 64KB. 2. 1 power indicator, 1 Link indicator, 1 user indicator. 3. 1 power supply/access port. 4. 1 boot mode selection jumper to select the chip boot mode 5. 1 system reset button for resetting the MCU 6. 1 user function button. 7. Provides CMSIS-DAP mode download, debugging, and USB virtual serial port printing functions. 8. All IO ports are brought out, including the IO ports occupied by the crystal oscillator. The distribution of hardware physical resources is as follows:  For detailed descriptions, please refer to the information provided by the forum.  Data address: [【Fresh experience: Shanghai Hangxin ACM32G103 development board】Review|【Fresh experience: Shanghai Hangxin ACM32G103 development board】Free trial_Electronic Engineering World (eeworld.com.cn)](https://en.eeworld.com/bbs/elecplay/content/ca31236e) The content directory of the data package is as follows:   ### 1.1: Hardware schematic diagram  ## ==2: Development environment setup== ### 2.1: Chip support package installation Generally, the chips of domestic development boards are not supported by keil by default. You need to install the pack package corresponding to the chip. This package is included in the downloaded data package, with keil version and IAR version respectively. The pack package is in our IDE support package.  Click directly until it is completed. ### 2.2: Development board library file selection The data package contains two types of library files, namely the standard library and the HAL library.  Here I choose the standard library, and the subsequent projects are also based on the standard library.  ### 2.3: Download, debug and burn the board. First download the program and output debugging to facilitate subsequent work. Here we choose the serial port UART project.  Click to download and burn, then open the serial port debugging assistant to view the data.  After burning, it was found that there was no data output from the serial port. At first, I thought it was a program problem. Later, I pressed the reset button again and there was data.  The serial port outputs data once every second. ## ==3: Create a new project== ### 3.1: Project creation If you don't like the official project directory structure, you can create a project yourself to deepen your impression. Just create a new project under keil. The created project is as follows:  ### 3.2: Add the minimum project directory Compile and find that the file is reported. ### 3.3: Error information processing First, refer to the original project configuration for project configuration:  For files that cannot be found, remove unused files.  Shield and delete and recompile, and continue to report errors.  Add the missing files. The core structure of the development board: core chip (U1), model ACM32G103RCT6, based on ARMv8-M architecture, supports Cortex-M33 and Cortex-M4F instruction sets. Supports up to 120MHz system operating frequency, supports floating-point operations and DSP. Recompile and continue to report errors.  These error messages should be due to the lack of corresponding standard library files.  Recompile and continue to report errors.  Modify it directly to this. ```C #ifdef USE_FULL_ASSERT // void assert_failed(uint8_t* file, uint32_t line); #define assert_param(expr) ((expr) ? (void)0 : 404) #else #define assert_param(expr) ((void)0U) #endif ``` Do not use this error warning display, and directly report 404 error. Recompile Success! ! ! ### 3.4: Online debugging and verify whether the online debugging system clock is 120M. First set a breakpoint, as shown below:  Then click Debug-Run:  Check the debug information window and look at the system clock:  Done! ! ! 

Jacktang

Did you forget to upload something?

qzc0927

Jacktang posted on 2023-12-22 07:33 Did you forget to upload anything?

What forgot to upload?

aing123

How stable is this thing?

qzc0927

aing123 posted on 2023-12-25 15:25 How stable is this thing?

Still testing, there should be no problem with basic applications