1# hiview Module<a name="EN-US_TOPIC_0000001079122822"></a> 2 3- [Overview](#section469617221261) 4- [Architecture](#section15884114210197) 5- [Repositories Involved](#section767551120815) 6 7## Overview<a name="section469617221261"></a> 8 9The hiview module provides the initialization of the DFX subsystem and controls the startup of each component as required. 10 11## Architecture<a name="section15884114210197"></a> 12 13The DFX initialization consists of two phases: DEVICE\_INIT and CORE\_INIT. 14 15DEVICE\_INIT: 16 171. The config component and core configuration parameters \(enabling or disabling the dump or event function\) of the DFX subsystem are initialized. 18 192. The log component is initialized, without involving the dynamic memory allocation and file operation capabilities. 20 213. The status information about the current DFX subsystem is written into the config component. 22 23CORE\_INIT: 24 251. The log, dump, event, and output components are initialized as required based on the parameters of the config component. 26 272. Memory management and file system operations are started normally. Memory can be requested and files can be created as required. 28 29## Repositories Involved<a name="section767551120815"></a> 30 31[DFX subsystem](https://gitee.com/openharmony/docs/blob/master/en/readme/dfx.md) 32 33[hiviewdfx\_hilog\_lite](https://gitee.com/openharmony/hiviewdfx_hilog_lite/blob/master/README.md) 34 35**hiviewdfx\_hiview\_lite** 36 37[hiviewdfx\_hievent\_lite](https://gitee.com/openharmony/hiviewdfx_hievent_lite/blob/master/README.md)