This post was last edited by Hot Ximixiu on 2021-6-8 09:58
MM32F013x——Event Recorder Usage
How to use Ozone, RTT-Viewer, and J-Scope on MM32F013x. Although the above methods are simple and convenient, they are only limited to J-Link tools. However, there is no such limitation when using Event Recorder. Event Recorder is a new feature added in MDK version 5.22. It uses the standard SWD download interface and is basically applicable to various Links. As long as the version is MDK v5.22 or above, it supports time measurement, power consumption measurement, printf printing, etc. After version 5.25, this function is more complete, and time measurement and other functions are added.
Introduction to Event Recorder
Event Recorder has the following features:
1. Improve the detection capability during the dynamic execution of the application.
2. Support event type filtering mechanism, such as runtime errors, API calls, internal operations and operation information.
3. It can be called arbitrarily in tasks, RTOS kernels and interrupt service routines. 4. For Cortex-M3/M4/M7/M33 core chips
with ITM function , there is no need to switch interrupt operations during the execution of the record . For Cortex-M0/M0+/M23 without ITM function, it is necessary to switch interrupts. 5. Support printf redirection. 6. All kinds of Links are supported, including J-Link, U-Link and CMSIS-DAP with SWD interface or JTAG interface. 7. For Cortex-M3/M4/M7/M33 core chips with DWT clock cycle counter function, when creating timestamps, the system burden can be effectively reduced, and no dedicated timer is required to implement it. 8. The execution time of Event Recorder is time-deterministic, that is, the execution time is determined and the execution speed is super fast. Therefore, the code in the actual product can still have this part, and there is no need to create debug and release versions. 9. RTX5 and all its middleware support Event Recorder debugging.
|