Huawei has officially released the DevEco Studio 2.2 Beta 1 version update, which comes with three changes to developers: new support for a variety of development boards and modules, and a new ext3/4 file system for the Hi3516DV300 development board.
DevEco Device Tool is a one-stop integrated development environment for smart device developers. It supports on-demand customization of HarmonyOS components, supports code editing, compilation, burning and debugging, performance monitoring and other functions, supports C/C++ language, and plug-ins Deployed in Visual Studio Code, supports Windows10 64-bit or Ubuntu18 and above.
1: Added support for multiple development boards and modules
DevEco Device Tool 2.2 Beta1 version adds support for the following development boards and modules:
- Added support for compiling and burning of Neptune (chip W800) development board
- Added support for compilation and programming of BearPi-HM Nano (chip Hi3861) development board
- Added support for compiling and burning of Realtek rtl8720 development board
- Added support for compilation based on BL602 chip module
- Added support for compilation based on ASR582x chip module
So far, DevEco Device Tool originally supports Huawei HiSilicon’s Hi3516, Hi3518 and Hi3861 series development boards, as well as Sanfang’s NXP and Xradio series development boards, and supports a total of 8 development boards and 2 modules.
2: For Hi3516DV300 development board, add ext3/4 file system to burn
In order to be compatible with the burning of the ext3/4 file system, DevEco Device Tool 2.2 Beta1 adds the burning function of the ext3/4 file system for the Hi3516DV300 development board, that is, in the “System” option of the burning configuration page, a new ” ext3/4” option.
3: New programming configuration wizard function
If the compiled file is not generated directly by local compilation, when burning the file, the developer needs to complete the burning configuration one by one on different configuration pages. In order to reduce the programming and configuration work, DevEco Device Tool 2.2 Beta1 has added the “Programming Configuration Wizard Function”, that is, all programming-related configurations are completed in one configuration page, reducing the developer’s operation to switch back and forth between different configuration pages.
In addition to the above three surprises, DevEco Device Tool 2.2 Beta 1 also has many basic capabilities, such as providing code search, code highlighting, code automatic completion, code input prompts, code checking and other functions to improve coding efficiency at the same time, it provides single-step Debugging capabilities, support to view debugging information such as memory, variables, call stacks, registers, assembly, etc.
DevEco Device Tool 2.2 Beta1 also enhanced two existing features and fixed seven remaining issues. Details are as follows:
- The task status icon display is optimized. When the developer clicks the task button in PROJECT TASKS (for example, Build), the corresponding task operation will be triggered. The icon in front of the task button will remain rotating, indicating that the task is being executed. The person can know whether the task has been successfully started.
- Tool chain pre-configuration optimization, DevEco Device Tool 2.2 Beta1 presets a batch of commonly used tool chain configurations for device development. Developers only need to name the imported tool chain according to a specific name, and the imported tool chain will take effect directly in the compilation phase, saving Going to the tedious part of toolchain configuration in the configuration page.
- Solved the problem that the developer could not open the project normally after clicking Open after creating the project through New DevEco Project.
- Solved the problem that Hi3516 and Hi3518 cannot be compiled normally when the Java environment is not configured in the developer’s system environment variables.
- Solved the problem that when the developer opened the DevEco project with Blank Board through New DevEco Project/Open DevEco Project, PROJECT TASKS was empty and could not operate normally.
- Fixed the problem of inconsistent file selection dialogs when clicking the Load raw log and Log JSON buttons in the Profiling function interface.
- Solved the problem that the Install to project button in the HPM interface was disabled and unusable after the developer misoperation.
- Solved the problem that the error message in the pop-up window is not clear when the developer downloads the code through the Install to project button of the HPM interface.
- Solved the problem that PROJECT TASKS is empty and cannot operate normally when the verbose_output option is added in the developer configuration page but is not checked.