1181 views|0 replies

8

Posts

0

Resources
The OP
 

[Atria AT32WB415 Series Bluetooth BLE 5.0 MCU] + Unboxing Review & IDE Installation & Keil Installation [Copy link]

[Atria AT32WB415 Series Bluetooth BLE 5.0 MCU] + Unboxing Review

  • Evaluation board actual style

1.1. The onboard factory program is a running light.

  • Function Introduction

2.1. Onboard link circuit, the circuit has: SW, USART, SPI, boot, reset interface.

The interesting thing about this evaluation board of Arteli is that Link has SPI interface, while the original LINK does not have SPI interface. According to the circuit schematic of the evaluation board, the Link SPI interface is connected to p04~p07 of MCU. Checking the manual, it is confirmed that its functional interface is indeed used for programming the Bluetooth module.

2.2. Board antenna interface

2.3. Bluetooth reset and MCU reset

2.4、boot0 rotation jumper cap

2.5, RTC crystal oscillator circuit and external crystal oscillator circuit

2.6. USB circuit and power supply circuit. The power supply circuit is worth referring to, and its cost performance is very good.

2.7. LED indicator and pin header interface

  • Software Installation

3.1、AT32 series chips support three development environments: IAR, KEIL and AT32IDE. AT32IDE is a cross-platform ARM embedded system software development environment based on Eclipse. Experience the AT32IDE development environment. . . .

3.2. The installation of AT32IDE_V1.0.0_Setup.exe software is very convenient and simple. You only need to select the installation path and it will automatically install until the installation is completed.

3.3. AT32 IDE user manual. According to the user manual, I tried the process of creating a new project.

3.4、Create a new project to test whether the connection is normal and whether the code download is normal. The new project needs to be debugged in the IDE.

  • Keil Environment

4.1、Officially provided DFP for MDK4 and MDK5, supporting AT32 MCU models to run on Keil MDK.

4.2. The official engineering files are mainly based on Keil. Most routines have Keil projects, and there are very few IAR and IDE development environment projects. If you use a development environment other than Keil, you need to transplant the code. For example, if I use the Bluetooth function later, its code routine is also established with the Keil development environment, and there are no engineering files for other development environments.

4.3. The code project is compiled normally and the installation environment is correct.

4.4 Actual operation effect

  • Code structure

5.1. The BSP (standard library) code structure is used, which is also common in the development process of chips from other companies. Its structure is somewhat different from the HAL library. It can also be said that the BSP structure is older.

The Board Support Package (BSP) is a layer between the motherboard hardware and the driver layer program in the operating system. It is generally considered to be a part of the operating system. Its main function is to implement support for the operating system and provide a function package for the upper-level driver to access the hardware device registers so that it can run better on the hardware motherboard.

The Hardware Abstraction Layer (HAL) is an interface layer between the operating system kernel and the hardware circuit, and its purpose is to abstract the hardware. It hides the hardware interface details of a specific platform and provides a virtual hardware platform for the operating system, making it hardware-independent and portable on multiple platforms.

5.2. The BSP (standard library) code structure is shown in the figure.

5.3. API documentation. API documentation is provided in the code examples. The API documentation introduces how to call the function and is accompanied by code examples to facilitate everyone's understanding and use of its function code.

This post is from RF/Wirelessly
 

Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

快速回复 返回顶部 Return list