Mekol Studio - Little Bear Development Notes 2

Harmony Introduction to compilation and construction

1.      In short, the compilation process is through bearpi-hm_nano\build\lite\product\BearPi-HM_Nano.json Define compilation .c File becomes .a The final output of the file is .bin file

If it's complicated

Here's the picture

Specific video links ：

​ ​https://www.bilibili.com/video/BV1Hi4y1c7dM?from=search&seid=11981477053638768133​​

2.      The specific process of code operation is

​ ​https://blog.csdn.net/qq_42754570/article/details/112184043​​

 

CMSIS-RTOS2 Interface

CMSIS yes Cortex Microcontroller software interface standard （Cortex Microcontroller Software Interface Standard） yes ARM A set of standards followed by some compiler manufacturers and semiconductor manufacturers , By ARM Specifically for Cortex-M Standards proposed in the series . Under the agreement of this standard ,ARM And chip manufacturers will provide some general API Interface to access Cortex Kernel and some special peripherals , In order to reduce the cost of money and time brought by the transplantation of chips and development tools .

 

CMSIS-RTOS2（CMSIS-RTOS API Version 2） yes Arm Cortex-M General purpose of processor RTOS Interface . For needs RTOS Functional software components provide standardized API.

 

CMSIS-RTOS2 It's a universal API, It's related to the bottom RTOS It's not about the kernel , The programmer who writes the application calls... In the user code CMSISRTOS2 API function , Will be more convenient from an application RTOS To another RTOS, Use CMSIS-RTOS2 API Middleware can also avoid a lot of unnecessary transplantation .

Simply put, use CMSIS-RTOS2 You can ignore the difference of the underlying kernel , Applications can run

Hongmeng and CMSIS-RTOS2 Interface contact ：

task management

Task status is usually divided into four types ： be ready 、 function 、 Blocking 、 sign out .

The relationship between them ：

Create tasks ：osThreadNew(osThreadFunc_t func,void * argument,const osThreadAttr_t * attr)

Delete a task ：osThreadTerminate(osThreadId_t thread_id);

Task suspended ：osThreadSuspend(osThreadId_t thread_id)

Mission recovery ：osThreadResume (osThreadId_t thread_id)

 

Software timer

Software timer , It's based on the system Tick A timer that interrupts the clock and is simulated by software , When set Tick After the clock count The user-defined callback function will be triggered . Timing accuracy and system Tick The period of the clock is related to .

The software timer supports ：

Static clipping ： It can turn off the software timer function through macro .

Software timer creation .

The software timer starts .

The software timer stops .

Software timer delete .

Software timer remaining Tick Number acquisition

Create timer ：osTimerNew (osTimerFunc_t func, osTimerType_t type, void *argument, const osTimerAttr_t *attr);

Start timer ：osTimerStart (osTimerId_t timer_id, uint32_t ticks);

Stop timer ：osTimerStop (osTimerId_t timer_id);

Delete timer ：osTimerDelete (osTimerId_t timer_id);