Unified software mirroring method for video conference terminal equipment

Abstract

The invention provides a unified software mirroring method for video conference terminal equipment, which comprises the following steps of: writing common hardware configuration of different products of the same processor into the same dtsi file according to equipment tree difference of different video conference terminal equipment, and putting differentiated configuration of different products into dts files of corresponding products; the dts file and the dtsi file are compiled into dtb files, each product equipment tree correspondingly generates one dtb file, and all the dtb files are compiled into a Kernel mirror image; in the uboot starting stage, a hardware adc value is read, the product model is judged, a corresponding equipment tree file is matched, a corresponding hardware drive is loaded according to equipment tree configuration, and hardware resource loading and distinguishing are completed; after the system is started and enters rootfs, OEM environment variables of corresponding products are obtained from software mirror images according to different hardware adc values, different product software configurations are loaded, and software function distinguishing is completed. According to the invention, high integration of all mirror images under the same processor can be realized, and the software mirror image management work is greatly reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of video conference terminal equipment, and in particular to a unified software mirroring method for video conference terminal equipment. Background Art

[0002] At present, the production or on-site upgrade process of video conferencing terminals leads to the diversity of software versions due to the requirements of different hardware configurations and product forms. For example, the main processors of the same series of products may be the same, but other hardware configurations (such as memory, storage, interface, etc.) may be different. If corresponding U-boot, Kernel and application images are designed for each product, there will be a problem of multiple hardware and multiple software versions. In addition, the application software under different product forms will also be different, which further leads to a surge in the number of software versions and increases the complexity of maintenance and burning.

[0003] At present, the unified software solution based on different hardware of the same processor is to distinguish and burn the image software corresponding to different hardware according to the hardware ID, and design different kernel images for different hardware. In fact, there is still the problem of multiple software versions corresponding to multiple hardware. In view of this, a method is needed to simplify software version management, reduce the number of versions, and maintain support for different hardware and product forms. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a unified software mirroring method for a video conferencing terminal device to overcome the problem of too many mirroring versions and difficult maintenance caused by multiple Kernel mirroring and multiple uboot mirroring.

[0005] The problem of the present invention is achieved as follows: a unified software mirroring method for a video conferencing terminal device comprises the following steps:

[0006] Step S1, according to the differences in device trees of different video conferencing terminal devices, write the common hardware configurations of different products with the same processor into the same dtsi file as a common configuration, and put the differentiated configurations of different products into the dts file of the corresponding product;

[0007] Step S2, compile the dts file and the dtsi file together into a dtb file, generate a dtb file for each product device tree, and compile all dtb files into the Kernel image;

[0008] Step S3, starting the uboot phase, reading the hardware adc value to determine the product model and matching the corresponding device tree file, loading the corresponding hardware driver according to the device tree configuration, and completing the loading and differentiation of hardware resources;

[0009] Step S4: After the system is started and enters the rootfs, the OEM environment variables of the corresponding products are obtained from the software image according to the different hardware adc values, and the different product software configurations are loaded according to the OEM environment variables to complete the distinction of software functions.

[0010] Furthermore, the naming method of the dtb file is defined as: product model#adc channel=adc value.dtb. If there are multiple adc interfaces, they are separated by #.

[0011] Furthermore, different products with the same processor use the same uboot image.

[0012] Furthermore, the software image includes all software functions and data files of all products.

[0013] Furthermore, the differentiated configurations of the different products include HDMI to MIPI chips, WiFi modules, audio chips and wired network chips.

[0014] Furthermore, the hardware provides a stable voltage value to the specified ADC interface through resistor voltage division. Resistors of different values ​​are used in the hardware circuits of different products to ensure that the voltage obtained by each product is unique.

[0015] Furthermore, the step S2 is specifically as follows: when compiling the Kernel image, the compilation script compiles the related files into a dtb file together according to the dependency relationship between dts and dtsi, the dts corresponding to different products generate a corresponding dtb, all dtb files are packaged into resource.img, and resource.img is packaged into boot.img to complete the packaging of multiple device tree images, and finally the dtb file is stored in boot.img.

[0016] The advantages of the present invention are as follows: different hardware designs of the present invention use the same U-boot image and Kernel image, different hardware resources are loaded according to the hardware ID during kernel startup, and the same file system is used for different hardware designs, the software loads different application configurations according to the hardware ID, and the software functions of different products are distinguished according to the application configuration. By having a common set of software images for different products with different hardware designs, the number of product software versions is greatly reduced, the software image management work in the production process is greatly reduced, and the maintenance work of commercial software versions is greatly reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0018] Figure 1 The present invention is a flowchart of an execution of a unified software mirroring method for a video conferencing terminal device. DETAILED DESCRIPTION

[0019] The embodiment of the present application provides a unified software imaging method for a video conferencing terminal device, which is used to solve the problem of too many existing software versions, and can achieve high integration of all images under the same processor, greatly reducing the software image management work during the generation process.

[0020] like Figure 1 As shown, a unified software mirroring method for a video conferencing terminal device of the present invention comprises the following steps:

[0021] Step S1, according to the differences in the device trees of different video conferencing terminal devices, write the common hardware configurations of different products with the same processor into the same dtsi file as a common configuration, and put the differentiated configurations of different products into the dts files of the corresponding products; for example, the configuration of the debug serial port is the same in multiple products, and the configuration can be put into the same dtsi, while the 5g-hpd plug-and-unplug detection pin is only used by the c01-5G product, so the configuration is put into the dts corresponding to c01-5G, and when there are differences in the chip configuration mounted on i2c3, for example, the chip configuration mounted on i2c3 of the d31_v5 product is placed in the dts corresponding to d31_v5, and the chip configuration mounted on i2c3 of c01 needs to be placed in the dts corresponding to c01;

[0022] Step S2, compile the dts file and the dtsi file into a dtb file together, generate a dtb file for each product device tree, and compile all the dtb files into the Kernel image; preferably, the step S2 is specifically as follows: when compiling the Kernel image, the compilation script compiles the related files into a dtb file together according to the dependency relationship between dts and dtsi, and the dts corresponding to different products generate a corresponding dtb, and all the dtb files are packaged into resource.img, and resource.img is packaged into boot.img to complete the packaging of multiple device tree images, and the final dtb file is stored in boot.img. Specifically, when packaging resource.img, use resource_tool to package logo.bmp, logo_kernel.bmp, and the dtb files corresponding to the device tree we need into the image.

[0023] Step S3, starting the uboot phase, reading the hardware adc value to determine the product model and matching the corresponding device tree file, loading the corresponding hardware driver according to the device tree configuration, and completing the loading and differentiation of hardware resources;

[0024] Step S4: After the system is started and enters the rootfs, the OEM environment variables of the corresponding products are obtained from the software image according to the different hardware adc values, and the different product software configurations are loaded according to the OEM environment variables to complete the distinction of software functions.

[0025] Preferably, the dtb file naming method is defined as: product model#adc channel=adc value.dtb. If there are multiple adc interfaces, they are separated by #.

[0026] Preferably, different products with the same processor use the same uboot image.

[0027] Preferably, the software image includes all software functions and data files of all products.

[0028] Preferably, the differentiated configurations of the different products include HDMI to MIPI chips (LT6911C, RK628D), WiFi modules (AP6256, CM256SM), audio chips (AL5672, ES8388) and wired network chips (QCA8337), etc.

[0029] In step S3, the corresponding hardware ID value is obtained by reading the hardware adc value. Uboot uses the hardware ID to compare with the device tree dtb file packaged in resource.img. If the parameters in the hardware ID and dtb naming are consistent, the device tree that the device needs to use can be determined. This method requires the hardware to provide a stable voltage value to the specified adc interface through resistor voltage division. Resistors of different resistance values ​​are used in the hardware circuits of different products to ensure that the voltage obtained by each product is unique. Uboot determines the product by reading the voltage value of the adc interface.

[0030] The method of judging the product by reading the ADC value requires less hardware resources than the existing method of judging the product by reading the GPIO. Although the resistance value may have errors and the circuit may have problems, the ADC value obtained by the method of judging the product by reading the ADC value may have certain errors. However, since the voltage division accuracy is not too high, the ADC error in the actual application process can be ignored. Compared with the existing method of judging the product by reading the GPIO, which requires the hardware to pull up or pull down the GPIO, and then the Uboot determines the product according to the level values ​​of multiple GPIO pins, the ADC of the present invention occupies fewer GPIO pins and has better effects.

[0031] In summary, the present invention loads the device tree corresponding to different hardware according to the hardware ID when the system starts, completes the loading and differentiation of hardware resources, and loads different default software configurations according to the hardware ID when the software starts to distinguish software functions. Devices with different hardware designs use the same U-boot image and Kernel image. The Kernel image contains the device tree configuration of all hardware solutions. The software images of different products are exactly the same, realizing the unification of software images, greatly reducing the number of product software versions, greatly reducing the software image management work in the production process, and greatly reducing the maintenance work of commercial software versions.

[0032] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A unified software mirroring method for a video conferencing terminal device, characterized in that: The steps include: Step S1, according to the differences in device trees of different video conferencing terminal devices, write the common hardware configurations of different products with the same processor into the same dtsi file as a common configuration, and put the differentiated configurations of different products into the dts file of the corresponding product; Step S2, compile the dts file and the dtsi file together into a dtb file, generate a dtb file for each product device tree, and compile all dtb files into the Kernel image; Step S3, starting the uboot phase, reading the hardware adc value to determine the product model and matching the corresponding device tree file, loading the corresponding hardware driver according to the device tree configuration, and completing the loading and differentiation of hardware resources; Step S4: After the system is started and enters the rootfs, the OEM environment variables of the corresponding products are obtained from the software image according to the different hardware adc values, and the different product software configurations are loaded according to the OEM environment variables to complete the distinction of software functions.

2. A unified software mirroring method for a video conferencing terminal device as claimed in claim 1, characterized in that: The naming method of the dtb file is defined as: product model#adc channel=adc value.dtb. If there are multiple adc interfaces, they are separated by #.

3. A unified software mirroring method for a video conferencing terminal device as claimed in claim 1, characterized in that: Different products with the same processor use the same uboot image.

4. A unified software mirroring method for a video conferencing terminal device as claimed in claim 1, characterized in that: The software image contains all software functions and data files of all products.

5. A unified software mirroring method for a video conferencing terminal device as claimed in claim 1, characterized in that: The differentiated configurations of the different products include HDMI to MIPI chips, WiFi modules, audio chips and wired network chips.

6. A unified software mirroring method for video conferencing terminal equipment as claimed in claim 1, characterized in that: The hardware uses resistor voltage division to provide a stable voltage value to the specified ADC interface. Resistors of different values ​​are used in the hardware circuits of different products to ensure that the voltage obtained by each product is unique.

7. A unified software mirroring method for video conferencing terminal equipment as claimed in claim 1, characterized in that: The step S2 is specifically as follows: when compiling the Kernel image, the compilation script compiles the related files into a dtb file together according to the dependency relationship between dts and dtsi, the dts corresponding to different products generate a corresponding dtb, all dtb files are packaged into resource.img, resource.img is then packaged into boot.img, the packaging of multiple device tree images is completed, and finally the dtb file is stored in boot.img.

Images