[X-Shield] Module of the Embedded Boards initialization
最后更新于
最后更新于
The Embedded Boards initialization (EBIM) is a module of the X-Shield. It is used for initializing the embedded board containing the embedded board initialization, firmware updating by “one-key“. It is the GUI tool running on the Windows and Ubuntu systems. Now the board platforms can be supported as follows:
nxp-layerscape
The repo is https://github.com/carloscn/qt/tree/master/zynq_tool
For embedded devices, there are usually two ways to save the firmware (boot image, boot script, Linux kernel, Linux rootfs, ramdisk etc):
Using the SD way;
Using the onboard FLASH or eMMC.
Many boards select the SD card as the firmware storage. According to the Xilinx zynq and NXP s32g booting rules, the zynq, s32g, and layerscape can be booted from an SD card. The function of the EBIM GUI tool is shown in the following figure:
The Xilinx provides a way to burn the boot image to onboard flash using the JTAG: https://www.centennialsoftwaresolutions.com/post/flashing-qspi-over-jtag-on-zynq-without-using-gui
The EBIM is a GUI app for Windows OS and Ubuntu OS basing the Qt framework. There are 4 classes for the EBIM and the 4 classes are dispatched by the MainWindow (The MainWindow class is the GUI class defined by the Qt framework), which contains the device scanning, the sd card operations, the flash operations, and files management. The class architecture is shown in the following figure:
Note, the name of the prefixed with the 'Q' Class is offered by the Qt framework. The figure only lists the main Qxxx class. The QProcess class is used to start external programs and to communicate with them. We make use of the QProcess to execute the external scripts. QThread class provides a platform-independent way to manage threads. We declare the sdops and flashops as threads independent of MainWindow. The EBIM also calls various other Qt classes, including QFile, QMutex, QString, QByteArray, etc. in addition to QProcess and QThread. please refer to the EBIM code and Qt API document https://doc.qt.io/qt-5/classes.html
The functions of the EBIM contain the following:
The class Device Scan: Identify and scan available devices and return device information. The device information will be inserted into the MainWindow DeviceList.
The class SD card Operations: Responsible for executing scripts about SD card operations that contain the sd card formatting, the making filesystem for the sd card, and copying the files to the SD card.
The class FLASH Operations: Responsible for executing the scripts about flash operations that contain flash initialization and flash writing.
The succinct UML figure is shown in the following figure. For detailed UML block, please refer to the corresponding low-level design.
aIn the nutshell, the EBIM will list all the available devices and run the corresponding scripts. The really touching and operating of the device is programmed in the bash/bat script. The following figure shows the task flow of the EBIM.
The following screenshot is the GUI design of the EBIM:
The functions of the EBIM contain the following:
The class Device Scan
The class SD card Operations
The class FLASH Operations
The class of Device Scan is to list all available devices that are connected to the host. The UML figure of the Device Scan is shown in the following figure:
For the Linux Device, the SD device list can be listed by ll /dev/sd*, and the corresponding model name is stored in the /sys/block/dev/sdx/device/model. Moreover, the size of the device can be obtained by Linux ioctl API. Finally, combine all the information, and return them.
or the Window Device, wmic diskdrive get name,interfacetype,size,model command can help us to get the disk information. The information is shown in the following figure:
The EBIM just extracts devices by the InterfaceType 'USB', the size and model name can be obtained.
For the burning flash devices, we need to get the information from the JTAG driver.
Reserve the interface, and add the module when necessary.
The class of the Sd Operation is to format the target available device that is inserted into the host. The UML figure of the Sd Operation is shown in the following figure:
The tarball mode will recognize that the input file is a tar.gz file, and divide the task into five steps. The SD operation uses a series of scripts to finish the task. The developer shall add his scripts to the corresponding folder. The SD operation class will call it automatically.
The scripts are listed in the following figure:
The img mode will recognize that the input file is an img format file and only run one step. The script will use the dd command to burn the img to the SD card. This mode will burn for a long time.
Reserve the interface, and add the module when necessary.
