From 0c269b03180b076f67e98ab5e02619e13ecea7e1 Mon Sep 17 00:00:00 2001 From: stesen <5200794+stesen@user.noreply.gitee.com> Date: Mon, 14 Sep 2020 16:21:47 +0800 Subject: [PATCH 1/2] update dfx subsystem readme --- docs-en/readme/dfx.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs-en/readme/dfx.md b/docs-en/readme/dfx.md index 90b3da09d6b..01e84be97ee 100755 --- a/docs-en/readme/dfx.md +++ b/docs-en/readme/dfx.md @@ -8,7 +8,7 @@ As chip resources are limited and hardware platforms are diversified, component- - mini: This framework is intended for hardware platforms with Cortex-M or equivalent processing capabilities. The system memory is generally less than 512 KB. There is only one lightweight file system that can be used in limited scenarios, or no file system at all. The mini framework complies with the Cortex Microcontroller Software Interface Standard \(CMSIS\). -- featured: This framework is intended for hardware platforms with Cortex-A or equivalent processing capabilities. The system memory is greater than 512 KB. There is a comprehensive file system for storing a large amount of data. The featured framework complies with the Portable Operating System Interface \(POSIX\) specifications. +- featured: This framework is intended for hardware platforms with Cortex-A or equivalent processing capabilities. The system memory is generally greater than 512 KB. There is a comprehensive file system for storing a large amount of data. The featured framework complies with the Portable Operating System Interface \(POSIX\) specifications. ## Directory Structure @@ -130,7 +130,7 @@ The mini framework is a simple and compact DFX design that provides the logging Add the following code to the initialization process of Module A to register it with the logging framework: ``` - HiLogRegisterModule(HILOG_MODULE_SAMGR, "A"); + HiLogRegisterModule(HILOG_MODULE_A, "A"); ``` @@ -155,7 +155,6 @@ The mini framework is a simple and compact DFX design that provides the logging
OUTPUT_OPTION_DEBUG: Logs are directly output to the serial port without cross-task scheduling. This value is used only for temporary debugging.
OUTPUT_OPTION_FLOW (default value): Logs are output as data flow to the serial port.
OUTPUT_OPTION_TEXT_FILE: Logs are output as text files.
-OUTPUT_OPTION_BIN_FILE (to be supported): Logs are output as binary files.