Review of Domestic Alternatives to STM32 (6)

At the request of readers, Embedded ARM will continue to introduce domestic products that can replace STM32. Today, we present the Dongsoft Carrier ES32F369x, which can perfectly replace STM32.Dongsoft Carrier was formerly known as Shanghai Haier Integrated Circuit Co., Ltd., and later renamed Shanghai Dongsoft Carrier Microelectronics Co., Ltd. Dongsoft Carrier has an 8-bit MCU series, 32-bit ES/HR8P, 32-bit ES32 M0, and 32-bit ES32M3.

Today, we will introduce the M3 core ES32F369x. Recently, the 21ic forum conducted a testing event for the ES32F369x series. How is the performance of this product? Instead of talking too much, let’s directly look at some evaluations from 21ic users:[Simple Evaluation of Dongsoft Carrier ES32F369x] Simple configuration with vscode and gccUser: Daft DiodeShanghai Dongsoft Carrier Microelectronics, formerly known as Shanghai Haier Integrated Circuit, has an office in Qingdao. As a Qingdao native, I have a good impression of Dongsoft. A high school buddy of mine studied computer science in college, and at that time, he complained to me that their school had a partnership with Dongsoft. I wonder if that Dongsoft is the same as Dongsoft Carrier…I have previously used Dongsoft Carrier’s products, and customers expressed great satisfaction with the sensitivity. Here is the proof~I must praise the customer service, who was very communicative. At that time, I was in a hurry to catch a flight, so I wanted to send it via SF Express. I originally thought it could only be sent on Monday since Sunday is a holiday, but the customer service arranged for SF Express on Sunday, which was very impressive~Thanks to my aunt and Dongsoft Carrier for organizing this event. I was fortunate to apply for the ES32F3696 development board, and I hope to fully utilize this prototype development board for solution validation in the future~First, let’s introduce the resources of the ES32F3696 and compare it with the STM32F103 that everyone is most familiar with.The ES32F3696 currently has two sub-models, and the MCU model for this event is the LQFP64 packaged ES32F3696LT.The ES32F3696LT features a Cortex-M3 core, which is a very classic and excellent Arm core, with a frequency of 96MHz that can meet most working scenarios.The pinout is essentially pin-to-pin compatible with STM32, making it very easy for engineers familiar with STM32 to get started.With 512K of Flash and 96K of SRAM, the configuration is quite luxurious, and running a system is completely feasible.It supports a wide voltage range, directly driving from 2.0V to 5.5V, which is much more convenient than STM32. Previously, there was a project that required compatibility with both 3.3V and 5.0V voltages.It comes with CRC, arithmetic accelerators, true random number generators, AES encryption, DES encryption, and other computational units that are usually only found in M4.What interests me the most is that the ES32F3696 has an on-chip USB HS PHY. This is a rare feature among M3 products, giving it a significant edge over similar products.The event also provided an ESLINK2 for easy programming and debugging, but there is no ESLINK2 option in Keil and IAR. In fact, ESLINK2 is essentially an open-source CMSIS-DAP, and you can use it normally by selecting CMSIS-DAP during programming and debugging.I downloaded the SDK package and the Keil5 ES32F396 chip PACK from the official website.Double-clicking the mdk project, configuring the programmer, compiling, and downloading went very smoothly. I will start by turning on a light~I want to praise Dongsoft Carrier’s SDK and documentation.To be honest, I have encountered quite a few domestic microcontrollers, and very few can provide such comprehensive SDK and documentation.Most domestic MCU manufacturers either provide only a few demos in the SDK, or have numerous bugs, or require you to directly use ST’s standard library, or do not even have an RM manual, or only provide DS and RM without any other manuals.However, Dongsoft Carrier’s SDK is indeed very comprehensive, providing not only three driver libraries but also a wealth of examples and rare manuals.Moreover, Dongsoft Carrier has also partnered with RT-Thread to add support for Dongsoft products in RTT. In the third-party component folder of the accompanying SDK, you can find RTT examples.SDK’s driver libraries include:1. MD, Micro Driver, which focuses on register operations for maximum execution efficiency.2. ALD, Abstraction Layer Driver, which encapsulates commonly used functions again. ALD drivers can provide interfaces for upper-layer applications as well as operating systems, file systems, and other application and system-level software, improving portability and optimizing development efficiency.3. BSP, Board Support Package, which corresponds to the driver for this prototype development board.In addition to the necessary Datasheet and Reference Manual, there are application notes and detailed descriptions of the corresponding driver libraries. Any software package you are unsure how to use comes with accompanying documentation, which is quite rare among domestic manufacturers.Moreover, if you take a closer look at the various manuals, the information is detailed, and there is no sign of plagiarism. The accompanying compilation templates include not only the common Keil and IAR but also GCC, which is rarely provided by other domestic manufacturers! You can feel Dongsoft Carrier’s attitude and sincerity in their work!Every example in the SDK comes with project files for Keil and IAR, making compilation and downloading very easy once you install the corresponding MCU pack.However, I personally prefer to use vscode and gcc. Not to mention that Keil and IAR are paid software, I find IAR not very user-friendly, and Keil lacks even the most basic code formatting functionality (although it can be added via plugins), and I feel it is no different from blindly typing code!Since I often write in C, C++, C#, Python, JavaScript, and TypeScript, installing too many IDEs is really exhausting, so it’s better to unify them. Moreover, vscode is indeed user-friendly.I searched for other users’ evaluation posts, and it seems that very few have used vscode for development, so I will provide a simple tutorial here and mention two pitfalls I encountered during the configuration process. Currently, there are two approaches to developing ES32 with vscode: 1. Configure gcc yourself, 2. Use the vscode plugin provided by Dongsoft Carrier.Personally, I prefer the former because it is flexible and can be configured for all chips, making it more universal.The gcc configuration for vscode has a tutorial written by a master in this version, so I won’t elaborate on it here. I will only mention the issues I encountered while compiling with gcc:I will skip the process of downloading and installing arm-none-eabi. After configuring arm-none-eabi, there is a gcc directory under the corresponding example code. In the gcc directory, just type make and press enter to compile the project! However, it is important to note that the official accompanying makefile has a pitfall, and direct compilation will fail.This is due to either a permission issue or a flaw in the makefile, which lacks a temporary directory for obj files.As shown in the figure, create an obj folder in the parent directory of gcc, at the same level as the gcc directory. Then, make again, and the results will come out smoothly!Next, let’s discuss how to configure the project in Dongsoft Carrier’s vscode.First, download the integrated development environment VSCode For essemi from the official website, install the vscode plugin after downloading, and once installed, open vscode, and you will see an E icon.This icon is the Dongsoft Carrier vscode plugin.The plugin has functions for creating new projects, opening projects, and adding projects, but the “Create New Project” function requires you to configure the paths for the ALD or MD driver libraries yourself, which is relatively cumbersome. So, we will look for a shortcut by importing the configuration from Keil and IAR projects, which is much faster~First, click the open project icon, find the corresponding Keil or IAR project file, and select the file type in the lower right corner as other project. I will take importing a Keil project as an example.After importing the project, you can right-click on example to compile.However, at this point, the compilation will definitely report an error.Although Dongsoft Carrier’s vscode plugin also comes with a user manual for a plugin, it is somewhat rough and does not detail the issues encountered and configurations, only briefly mentioning how to create a project while simply mentioning the steps for importing a project.In fact, after carefully examining the compilation error codes, it is relatively easy to troubleshoot the issues. Since we imported a Keil project, the startup file for the ES32F3696 is configured for the Keil compiler, but now we are using clang and gcc for development, so we need to replace the startup file as well. First, delete the startup_es32f36xx.s file.Then, right-click on the startup group and select Add File.From the path shown in the figure below, find the assembly startup file used by gcc.Replacing the startup file and recompiling will still result in errors because the vscode plugin provided by Dongsoft Carrier has some bugs when importing projects and does not import macro definitions, so here we need to right-click on example and go to properties.Switch to the last page, “Compile Options,” and fill in the macro definition field with ES32F36xx.After making the modifications, remember to click the “Save Compile Configuration” button in the lower right corner.At this point, when recompiling, it will indicate that the compilation was successful.Overall, I am extremely satisfied with this event.Not only does the chip itself meet my needs, but the materials provided by Dongsoft Carrier are also very comprehensive.By the way, in the materials provided by Dongsoft Carrier, there is mention of a 32-bit MCU based on the RISC-V architecture. I am very much looking forward to Dongsoft Carrier releasing a new model with a pin-to-pin compatibility similar to the current ES32F3696 based on RISC-V architecture. Although the licensing fees for ARM may be much cheaper when spread out, I still hope Dongsoft Carrier can design a completely self-owned intellectual property RISC-V 32-bit MCU to replace ARM…I look forward to Dongsoft Carrier’s future products!Dongsoft Carrier ES32F369x + ADC SamplingUser: freeelectron1. The pin used is PA5, which is ADC channel 92. Pin Multiplexing FunctionThe multiplexing function is function 0,so it needs to be configured as multiplexing function 0 in the software configuration.3. ADC InitializationIn hardware design, VDD is used as the reference, so it should also be configured to use VDD in the software configuration.

void adc_init(void){        md_gpio_init_t x;
        x.mode  = MD_GPIO_MODE_INPUT;        x.pupd  = MD_GPIO_PUSH_UP;        x.odos  = MD_GPIO_PUSH_PULL;        x.podrv = MD_GPIO_OUT_DRIVE_1;        x.nodrv = MD_GPIO_OUT_DRIVE_1;        x.flt   = MD_GPIO_FILTER_DISABLE;        x.type  = MD_GPIO_TYPE_CMOS;        x.func  = MD_GPIO_FUNC_0;        md_gpio_init(GPIOA, MD_GPIO_PIN_5, &x);
        md_adc_init_t h_adc;  md_adc_nch_conf_t config;
  md_adc_struct_init(&h_adc);        md_adc_normal_struct_init(&config);        md_adc_init(ADC0, &h_adc);        md_adc_normal_channel_config(ADC0, &config);}

4. Get ADC Value

uint32_t get_adc_value(void){        uint32_t value=0;                /* Start normal convert */        md_adc_set_normal_channel_conv_start_nchtrg(ADC0);        /* Wait convert finish */        while (md_adc_get_stat_nche(ADC0) == 0);        /* Clear complete flag */        md_adc_set_clr_nche(ADC0);        /* Read normal convert result */        value = md_adc_get_normal_channel_val(ADC0);
        return value;}

5. PhenomenonBy adjusting the resistance value of R8, you can see the change in ADC sampling values.Dongsoft Carrier ES32F369x – Low Power Test DataUser: litchijunMost of the projects I work on have low power requirements, so I specifically tested the power consumption of the ES32F3696LT. This board is not very friendly for testing MCU power consumption, as there are no test points and it requires cutting traces.# Trace Cutting PreparationI used ESLINK II for power supply. Looking at the traces, the chip has multiple VDD pins without a suitable aggregation point, so it is necessary to cut off other networks of VDD to test the current flowing into the MCU.1. Cut off USB Power, otherwise there will be a backflow of 6mA2. Remove R41, otherwise it will draw 700+uA here3. PCB Cutting Points# DataSheet Power Consumption Data# Test Project and DataProject: SDK discovered one (ES32_SDK_V1.09\Projects\ES32F36xx\Examples_ALD\PMU\02_low_power_mode_command), directly usable.Looking at the project’s initialization, it enables all peripheral clocks.Measured data:

Measured current waveforms:STOP 1:STOP 2:STANDBY:[Dongsoft Carrier ES32F369x Development Board] Hardware I2C TestUser: WoodDataThis test is for the I2C peripherals, using ROHM sensors: the illuminance sensor RPR-0521RS, the pressure sensor BM1383AGLV, and the geomagnetic sensor BM1422AGMV. These sensors all use the I2C interface and can be connected together for I2C testing.As shown: using the Arduino interface plugged into the development board. I2C uses I2C0, corresponding pins are PB8:SCL, PB9:SDA.I have used these sensors before, so I directly used the previous code, just adjusting the I2C interface initialization and the I2C read/write functions.I was careless at first and did not enable the clock for I2C0 during initialization, so there was no response from I2C. After adding it, everything worked smoothly.

void i2c_gpio_init( void ){#ifdef I2C_USE_GPIO

#else        gpio_init_t a;
        /* Initialize scl pin */        a.mode = GPIO_MODE_OUTPUT;        a.odos = GPIO_OPEN_DRAIN;        a.pupd = GPIO_PUSH_UP;        a.nodrv = GPIO_OUT_DRIVE_6;        a.podrv = GPIO_OUT_DRIVE_6;        a.flt  = GPIO_FILTER_DISABLE;        a.type = GPIO_TYPE_TTL;        a.func = GPIO_FUNC_5;        ald_gpio_init(I2C_SCL_Port, I2C_SCL_PIN, &a);
        /* Initialize sda pin */        a.mode = GPIO_MODE_OUTPUT;        a.odos = GPIO_OPEN_DRAIN;        a.pupd = GPIO_PUSH_UP;        a.nodrv = GPIO_OUT_DRIVE_6;        a.podrv = GPIO_OUT_DRIVE_6;        a.flt  = GPIO_FILTER_DISABLE;        a.type = GPIO_TYPE_TTL;        a.func = GPIO_FUNC_5;        ald_gpio_init(I2C_SDA_Port, I2C_SDA_PIN, &a);
        /* Initialize I2C struct */        memset(&h_i2c, 0, sizeof(h_i2c));
        /* Enable i2c interrupt *///        ald_mcu_irq_config(I2C1_EV_IRQn, 3, 3, ENABLE);//        ald_mcu_irq_config(I2C1_ERR_IRQn, 3, 3, ENABLE);
        /* Initialize I2C */        h_i2c.perh = I2C0;        h_i2c.init.clk_speed = 100000;        h_i2c.init.module    = I2C_MODULE_MASTER;        h_i2c.init.dual_addr = I2C_DUALADDR_ENABLE;        h_i2c.init.own_addr1 = 0xA0;        h_i2c.init.addr_mode = I2C_ADDR_7BIT;        h_i2c.init.general_call = I2C_GENERALCALL_ENABLE;        h_i2c.init.no_stretch = I2C_NOSTRETCH_ENABLE;
        ald_i2c_reset(&h_i2c);        ald_i2c_init(&h_i2c);#endif}

int main(){        uint32_t         ms,ledms;        uint32_t         key_val,key_old,key_xor;        uint8_t         utbuff[6];
        float press; float temp;        uint16_t ps; float als;       
        /* Initialize ALD */        ald_cmu_init();        /* Configure system clock */        ald_cmu_pll1_config(CMU_PLL1_INPUT_HOSC_3, CMU_PLL1_OUTPUT_96M);        ald_cmu_clock_config(CMU_CLOCK_PLL1, 96000000);        /* Enable peripheral clock */        ald_cmu_perh_clock_config(CMU_PERH_GPIO, ENABLE);        ald_cmu_perh_clock_config(CMU_PERH_UART0, ENABLE);        ald_cmu_perh_clock_config(CMU_PERH_I2C0, ENABLE);
        uart_stdio_init();        memset(uart_buf, 0x0, 64);
        light_init();        key_init();        lcd_gpio_init();        i2c_gpio_init();

        printf_e("System start...\n");        light_ctrl(LIGHT_IDX_2, LIGHT_CTRL_ON);        ald_delay_ms(1000);        light_ctrl(LIGHT_IDX_2, LIGHT_CTRL_OFF);        ald_delay_ms(1000);
        if(BM1422AGMV_Init() == 0)        {                printf_e("BM1422AGMV_Init OK\r\n");        }        if(BM1383AGLV_Init() == 0)        {                printf_e("BM1383AGLV_Init OK\r\n");        }        if(RPR0521RS_Init() == 0)        {                printf_e("RPR0521RS_Init OK\r\n");        }
        ms = ald_get_tick()+10;        ledms = ald_get_tick()+1000;        key_old = 0;        while (1)        {                //按键扫描                if(ms < ald_get_tick())                {                        ms = ald_get_tick()+10;
                        key_val = 0;                        if(ald_gpio_read_pin(KEY_UP_PORT, KEY_UP_PIN) == 0)                        key_val |= 0x01;                        if(ald_gpio_read_pin(KEY_DOWN_PORT, KEY_DOWN_PIN) == 0)                key_val |= 0x02;                        if(ald_gpio_read_pin(KEY_LEFT_PORT, KEY_LEFT_PIN) == 0)                key_val |= 0x04;                        if(ald_gpio_read_pin(KEY_RIGHT_PORT, KEY_RIGHT_PIN) == 0)        key_val |= 0x08;                        if(ald_gpio_read_pin(KEY_CENTER_PORT, KEY_CENTER_PIN) == 0)        key_val |= 0x10;
                        key_xor = key_old ^ key_val;                        if(key_xor & 0x01)                        {                                if(key_val &0x01)                                {                                        printf_e("key up press +\n");                                }else                                {                                        printf_e("key up release -\n");                                }                        }
                        if(key_xor & 0x02)                        {                                if(key_val &0x02)                                {                                        printf_e("key down press +\n");                                }else                                {                                        printf_e("key down release -\n");                                }                        }
                        if(key_xor & 0x04)                        {                                if(key_val &0x04)                                {                                        printf_e("key left press +\n");                                }else                                {                                        printf_e("key left release -\n");                                }                        }
                        if(key_xor & 0x08)                        {                                if(key_val &0x08)                                {                                        printf_e("key right press +\n");                                }else                                {                                        printf_e("key right release -\n");                                }                        }
                        if(key_xor &0x10)                        {                                if(key_val &0x10)                                {                                        printf_e("key center press +\n");                                }else                                {                                        printf_e("key center release -\n");                                }                        }                                               key_old = key_val;                }
                if(ledms < ald_get_tick())                {                        ledms = ald_get_tick()+1000;                        light_ctrl(LIGHT_IDX_1, LIGHT_CTRL_TOGGLE);                        light_ctrl(LIGHT_IDX_2, LIGHT_CTRL_TOGGLE);                        printf_e("Count: %d\n", __cnt++);               
                        BM1422AGMV_get_rawdata(utbuff);                                          printf_e("BM1422AGMV:xx=%u\t\tyy=%u\t\tz=%u\r\n",(uint16_t)(utbuff[1]<<8)|utbuff[0],                                                                                                (uint16_t)(utbuff[3]<<8)|utbuff[2],                                                                                                (uint16_t)(utbuff[5]<<8)|utbuff[4]);                        RPR0521RS_get_psalsval(&ps,&als);                        printf_e("RPR0521RS:Lx=%0.2f\t\tPs=%d\n",als,ps);
                        BM1383AGLV_get_val(&press,&temp);                        printf_e("BM1383AGLV:P=%0.2f\t\tTem=%0.2f\n",press,temp);                }        }}

The data read below shows the values of the three sensors displayed on the serial port.Dongsoft Carrier ES32F369x-v1.3 ES-PDS Development Board Hands-On Experience (Beginner’s Perspective)User: zhongchshHVHands-on experience with the Dongsoft Carrier ES32F369x-v1.3 ES-PDS development board (Beginner’s Perspective) Note: I have almost no experience with 32 series microcontrollers, so this evaluation report can better reflect the completeness of Dongsoft Carrier’s 32 microcontroller documentation, technical support, and other aspects.(1) Received Evaluation Board.I am a university teacher, teaching microcontroller principles (51 core). During my lectures, I have deeply experienced the rapid progress of domestic microcontrollers in recent years, especially with the rapid rise of domestic free PCB software from Lichuang EDA, which has lowered the threshold for designing microcontroller systems. I deeply feel that using domestic software and chips will be an inevitable trend in the future. Due to the 8-bit microcontroller, domestic MCUs can almost completely replace foreign products. In my class, I have already had students use 51 core domestic microcontrollers, such as the STC15 series, to design practical projects (drawing PCBs and successfully soldering and debugging), and all students have completed them. Therefore, I sincerely hope that 32-bit microcontrollers can be the same. Although I have been away from 21ic for a long time, I happened to see the evaluation activity for Dongsoft Carrier’s ES32 development board on 21ic, and I was very happy to successfully apply and receive the development board, along with a beautiful calendar, as shown:D:\CZ\Onedrive-group\OneDrive – Office365尊享版 5T\10软件安装包与教程\东软载波ES32\截图(2) Technical Support and Development Materials It is understandable that one cannot compare a newcomer with a traditional leader; as long as one is diligent enough, it is sufficient. When I started connecting the debugger, I encountered some basic issues and was often too shy to ask for help, fearing it would affect everyone’s work. So I first thought of customer service, and I was pleasantly surprised that the customer service could quickly respond to questions and provided very specific answers. Customer service can be accessed through the official website (technical support link), and I have attached a screenshot of the Q&A, which deserves a thumbs up. Additionally, through the WeChat group for this evaluation activity, the questions I asked were also responded to, and Dongsoft’s technical staff answered questions in the group! Furthermore, various data sheets, application notes, and reference documents are relatively comprehensive. For example, when I opened the chip’s data sheet, it felt no different from those of mature foreign companies, and I could sense the professionalism and time and effort invested by the developers of domestic chips. Although reading manuals is not for beginners, it is still a good start.(3) Establishing the Debugging and Simulation Environment For newcomers, this is the most important aspect. I was very pleased to see that Dongsoft Carrier has developed its own IDE, called IDesigner. I am happy because I am increasingly unwilling to use (two words omitted here, you know what I mean) software. After all, using domestic free software feels more secure, and I don’t have to search everywhere for (two words omitted here, you know what I mean) packages and guides. In our classes, we also encourage students to use genuine domestic software. Similarly, Dongsoft provides a very complete development package (ES32_SDK), which is rich in content. It supports MDK (Keil5) and IAR development environments, but it is a bit regrettable that the examples for iDesigner are not yet provided. I hope they can be available soon so that we can confidently use domestic IDEs. I believe that day is not far off. For now, I will use Keil 5. Of course, the support package for Keil5 can be downloaded from the official website, as shown in the figure and link (Keil support package). The installation method for this pack file is as follows: Project -> Manage -> pack installer… (Here I am revealing that I am a beginner). This evaluation provided an ESLINK-II debugger. Regarding the driver for this debugger, there is a saying that in Windows 10, you need to permanently disable digital signature enforcement. You can check Dongsoft Carrier’s Bilibili video for specific methods (Bilibili video), as shown:I followed the steps on one computer and successfully connected to the development board. With a try-and-see attitude, I also connected to another Windows 10 computer without disabling digital signature enforcement, and it automatically installed the driver and connected successfully. It seems that for Windows 10, this debugger can be used directly. The burning software used is ESBurner, which can also be downloaded from the official website, and the installation is not complicated. (4) Open Example, Download, and Run In Keil 5, I found an example in the SDK directory as follows: ES32_SDK_V1.09\Projects\ES32F36xx\Templates_ALD\MDK-ARM. I chose it mainly because many examples require relatively complex testing, such as serial ports and AD lights. Running this example allows you to see the blinking of LED1 and LED2. I opened the ALD library file of the project, and after carefully reading it, I felt that the comments in the library file were still quite standardized and detailed, which will help with self-study in the future, as shown in the figure.Looking at the crystal oscillator on the development board, it is 12MHz, so the default 12MHz in the project target option does not need to be changed.Next, in the project, build the target, compile, and it is completely correct. With the ESLINK-II debugger, I tested online simulation, and it worked perfectly. The program was also downloaded to the board, and I could set breakpoints and everything. After unplugging the debugger, the program could run on the development board when powered on (very happy). The moment I saw the lights flashing, every hardware engineer understands that feeling.(5) Summary As I am still a newcomer to 32-bit microcontrollers, I have no authority to speak. I can only share my feelings about the friendliness of Dongsoft ES32 microcontrollers and give it a score of 90. The relatively detailed and professional materials, professional English documentation, and standardized software comments have left a deep impression on me. Moreover, through this evaluation activity, I can feel that many industry professionals are also full of expectations for domestic 32-bit microcontrollers, so I would like to thank Dongsoft Carrier and other companies for their contributions to the localization of microcontrollers. Where there is peace, it is only because someone is carrying the burden forward![Dongsoft Carrier ES32F369x Development Board Application UART Bootloader]User: hello, CAs I am particularly interested in Bootloader development technology, I will evaluate the Bootloader supported by the Dongsoft Carrier ES-PDS-ES32F369x-V1.3 prototype system development board.① In the path ES32_SDK_V1.09\Projects\ES32F36xx\Applications\Bootloader, there are three folders.01_uart_1k_xmode02_usb_dev_fatfs03_usb_host_fatfs② UART is very common, so we choose the 01_uart_1k_xmode method.We need a tool, HyperTerminal, which can be easily downloaded by searching.As for the use of HyperTerminal, please refer to Baidu Experience on how to use HyperTerminal. Here are a few issues I encountered: a. When opening a new connection, it prompts to fill in the area code, etc. Just fill it in, and some can be filled in casually. b. The COM port connection will only show the drop-down connection options after connecting the COM port; otherwise, you can only select TCP/IP options.③ We check the program files in the 01_uart_1k_xmode project, set up HyperTerminal. The baud rate is: 115200, data width: 8, parity: none, stop bit width: 1, hardware flow control: none.④ Compile, link, and download the program from the 01_uart_1k_xmode Keil MDK project to the development board (Erase chip before download).After connecting to the super terminal, the following result will be seen:: Prompting that there is no application program on the current development board and needs to be updated first.⑤ After searching in the 01_uart_1k_xmode folder, we found a Test_bin folder.There are two files in the Test_bin folder: Test_bin/run_in_flash.bin and Test_bin/run_in_sram.bin.After reading the explanation in ReadMe.txt, everything became clear. Dongsoft has prepared two APPs for us to test the Bootloader. We choose Test_bin/run_in_flash.bin.⑥ In the super terminal, after entering es#, I input a few characters, and it displayed: es#CCUnknown cmd: CCes#CUnknown cmd: Ces#AUnknown cmd: AAfter roughly reading the main program and tracing to the shell_task_func function in boot_shell.c.I tried using the Tab key, and the following selectable menus appeared:es# reboot run_flash run_sram updateversionAfter entering versiones#versionBootload: 01-00-00-00After entering reboot, it displayed garbled characters, and then the interface froze.Pressing the reset button on the development board restores normal operation.After entering update, it attempts to connect 10 times.After entering run_flash, it detects that there is no App.After entering run_sram, garbled characters appear, indicating that it should have executed sram.⑦ In the super terminal, press the reset button on the development board.After resetting, entering the update cmd, the development board sends the character C for connection.Then we click on Transfer -> Select Send File.In the pop-up dialog, browse and select the run_in_flash.bin file, protocol: select 1K Xmode,and click Send.The super terminal is sending.The super terminal displays that the update was successful.⑧ Press the reset button on the development board, and in the super terminal.If there are no key operations within three seconds, the App will automatically run, and the output count value will be displayed.If any key is pressed, it will be locked in the bootloader CMD interface.You can execute commands such as run_flash, run_sram, update, etc.After entering run_flash, the App will run, and the output count value will be displayed.After outputting the count value, pressing the reset button on the development board will result in garbled characters, which may appear multiple times in succession.Summary:a. It is quite good to embed the official bootloader program in commonly used electronic products; it is convenient to use, with some minor issues that do not affect usability.b. The module packaging is relatively good; if you want to understand it in depth, you need to carefully read the source program files and refer to the Bootloader help documentation.c. If you want to learn about prototype development systems and understand some layered ideas, the materials provided by Dongsoft Carrier are quite good and worth referencing.d. Although the source file comments are somewhat lacking, understanding them in conjunction with the help documentation should not pose any problems.ENDSource: 21ic Forum, Compiled by Fu Bin▍Recommended ReadingHow do you choose open-source free RTOS?GD32 also starts to have counterfeit and refurbished products flooding the marketWhat is the importance of an engineer’s surname! Don’t call me “Engineer X” anymore!!!→ Follow for more updates ←