Memory sharing application method, device and equipment for motherboard system and medium

Abstract

The application discloses a memory sharing application method and device for a mainboard system, equipment and a medium. The method comprises the following steps: sending a memory sharing instruction to set the memory as a sharing mode; reading a basic file corresponding to an embedded controller in the memory and integrating the basic file with a configuration file of the embedded controller to obtain a corresponding integrated file; sending the integrated file to the embedded controller for flashing; inputting the integrated file into the memory for storage and obtaining a corresponding memory mapping address; if the controller detects power-on again, reading the integrated file corresponding to the memory mapping address from the memory and configuring an interface function through the integrated file. The above method can share the data information in the memory by setting the data sharing permission, which can not only enrich the operation mode of the transmitted data information, but also greatly improve the data transmission efficiency and the interface function configuration efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for memory sharing applications in motherboard systems. Background Technology

[0002] Computers, all-in-one PCs, and other terminal devices are equipped with motherboards, on which a BIOS (Basic Input Output System) component acts as a controller. The controller and the EC (Embedded Controller) component on the motherboard can only communicate through the RAM (Random Access Memory) within the EC component. However, this communication method, using 62 / 66 or 68 / 6C, only shares 256 bytes of data (the EC component provides 256 bytes of RAM space that can be read and written by the system). This not only limits the communication data, leading to low communication efficiency, but also makes the communication process cumbersome and results in poor data sharing, affecting the application effect of the motherboard interface functions. Therefore, existing technologies suffer from low communication efficiency when the motherboard controller communicates with the embedded controller. Summary of the Invention

[0003] This invention provides a method, apparatus, device, and medium for memory sharing in a motherboard system, aiming to solve the problem of low communication efficiency when the motherboard controller communicates with the embedded controller in existing methods.

[0004] In a first aspect, embodiments of the present invention provide a memory sharing application method for a motherboard system, wherein the method is applied to a controller mounted on the motherboard, and the motherboard further includes memory and an embedded controller that are communicatively connected to the controller; the method includes:

[0005] Execute the pre-stored memory sharing instructions to set the memory to shared mode;

[0006] Read the base file corresponding to the embedded controller from memory;

[0007] The base file is integrated with the configuration file of the embedded controller to obtain the corresponding integrated file;

[0008] The integrated file is sent to the embedded controller for flashing;

[0009] The integrated file is input into the memory for storage, and the corresponding memory mapping address is obtained;

[0010] If the controller detects a power-on re-energization, it reads the integration file corresponding to the memory-mapped address from the memory and configures the interface functions using the integration file.

[0011] In a second aspect, embodiments of the present invention also provide a memory sharing application device for a motherboard system, wherein the device is configured in a controller disposed on the motherboard, and the motherboard is further provided with a memory and an embedded controller communicatively connected to the controller, the device being used to execute the memory sharing application method for a motherboard system as described in the first aspect above, the device comprising:

[0012] A memory sharing instruction sending unit is used to execute a pre-stored memory sharing instruction to set the memory to a shared mode;

[0013] A basic file reading unit is used to read the basic file corresponding to the embedded controller in memory;

[0014] An integration unit is used to integrate the base file with the configuration file of the embedded controller to obtain a corresponding integrated file;

[0015] A sending unit is used to send the integrated file to the embedded controller for flashing;

[0016] The storage unit is used to input the integrated file into the memory for storage and obtain the corresponding memory mapping address;

[0017] The interface function configuration unit is used to read the integration file corresponding to the memory mapping address from the memory and configure the interface function through the integration file if the controller detects that the power is turned on again.

[0018] Thirdly, embodiments of the present invention also provide a computer device, wherein the device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0019] Memory, used to store computer programs;

[0020] When the processor executes a program stored in memory, it implements the steps of the memory sharing application method for a motherboard system described in the first aspect above.

[0021] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the memory sharing application method for a motherboard system as described in the first aspect above.

[0022] This invention provides a method, apparatus, device, and medium for memory sharing in a motherboard system. The method includes: sending a memory sharing instruction to set the memory to a shared mode; reading a basic file corresponding to an embedded controller from memory and integrating it with the embedded controller's configuration file to obtain a corresponding integrated file; sending the integrated file to the embedded controller for flashing; storing the integrated file in memory and obtaining the corresponding memory mapping address; if the controller detects a power-on re-energization, reading the integrated file corresponding to the memory mapping address from memory and configuring interface functions through the integrated file. This method, by setting data sharing permissions to share data information in memory, not only enriches the ways to operate on transmitted data information but also significantly improves data transmission efficiency, enhancing the configuration efficiency and application effect of motherboard interface functions. Attached Figure Description

[0023] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart of a memory sharing application method for a motherboard system provided in an embodiment of the present invention;

[0025] Figure 2 This is a schematic diagram illustrating an application scenario of the memory sharing method for a motherboard system provided in an embodiment of the present invention.

[0026] Figure 3 This is a schematic block diagram of a memory sharing application device for a motherboard system provided in an embodiment of the present invention;

[0027] Figure 4 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0028] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0029] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0030] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0031] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0032] The embodiments of this invention application provide a memory sharing application method for a motherboard system, such as... Figure 2 As shown, this method is applied to a controller 10 mounted on a motherboard 1. The motherboard 1 also has a memory 20 and an embedded controller 30 that are communicatively connected to the controller 10. The controller 10 executes the stored software program to implement the above-described memory sharing application method for the motherboard system. The motherboard 1 can be installed in terminal devices such as desktop computers, laptops, tablets, and all-in-one computers. The controller 10 can be a BIOS (Basic Input Output System) component. The controller is independent of the central processing unit (CPU) mounted on the motherboard and controls the various interface functions of the motherboard. The memory 20 is the RAM (Random Access Memory) mounted on the motherboard, and the embedded controller 30 is the EC component. The EC component is a 16-bit microcontroller that is always running, regardless of whether the computer is powered on or off.

[0033] like Figure 1 As shown, the method includes steps S110 to S160.

[0034] S110. Execute the pre-stored memory sharing instruction to set the memory to shared mode.

[0035] The controller can first retrieve and execute pre-stored memory sharing instructions to configure memory control information. Memory control information refers to the parameters used to control the memory as a whole. This information includes mode information and permission parameters for each component. The permission parameters of a component include its specific permissions to access data in memory (such as read, modify, and write permissions). The mode information of a component includes the mode options and parameters for data sharing with that component. The mode information controls the component's access to data in memory. Mode options include hidden or shared, and the parameter parameters are the specific parameters used to select a particular mode option. If "hidden" is selected in the component's mode options, the memory is hidden from that component, and the component cannot access or share the memory. If "shared" is selected, the memory is shared with that component, and the component can access and share the data stored in memory.

[0036] Specifically, the controller executes a memory sharing instruction, reads the default parameter values ​​corresponding to the mapping information in the memory according to the memory sharing instruction, and configures the memory control information using the default parameter values ​​to set the memory to shared mode. A "shared" mode option can be added to the memory control information and the corresponding mode information of the controller, and the "shared" mode option can be selected. The corresponding permission parameters of the controller can be modified to read, modify, and write. That is, when the controller is set to shared mode for memory, a dedicated storage area is allocated to the controller in memory. Therefore, the controller can access the allocated storage area in memory and obtain the data information stored in that storage area for use. The controller can not only access and read the data information stored in this storage area, but also modify and write the data information stored in it.

[0037] S120. Read the basic file corresponding to the embedded controller from memory.

[0038] The system further reads the base file corresponding to the embedded controller from memory. This base file is the EC file, which is the firmware file of the EC component (EC chip). It contains the program code that controls the operation of the EC component. This code implements various functions of the EC component, such as power management, keyboard input processing, and fan speed control. The EC file is the core of the EC component's specific functions. It determines which tasks the EC component can perform and how it interacts with other hardware components. The EC file must ensure the integrity and correctness of the code to ensure that the EC component can operate stably and reliably. There are different versions of the EC file, which may contain fixes for specific problems, performance optimizations, or new features.

[0039] In a specific embodiment, step S120 includes the following sub-steps: sending a memory information sharing instruction to the embedded controller to control the embedded controller to perform memory sharing settings; and reading the corresponding base file from the memory according to the base address of the embedded controller.

[0040] A memory sharing instruction can be sent to the embedded controller, thereby controlling the embedded controller to perform memory sharing settings. That is, after the embedded controller completes the settings according to the memory sharing instruction, it can share the memory and the base address stored in the memory. After memory sharing is set up, a dedicated storage area is allocated in memory for the embedded controller. Therefore, the embedded controller can access the allocated storage area in memory and obtain the data stored in that area for use. At the same time, other components (such as the controller) can obtain the base address shared by the embedded controller in memory.

[0041] After completing the memory sharing settings, the controller can obtain the base address of the embedded controller and read the base file corresponding to the storage location of the base address from memory based on the base address.

[0042] S130. Integrate the basic file with the configuration file of the embedded controller to obtain the corresponding integrated file.

[0043] After obtaining the basic files, they are integrated with the embedded controller's configuration file, which is also the EC component's configuration file (hereinafter referred to as the EC configuration file). The EC configuration file is used to configure the EC component's operating parameters and options. It contains some top-level configuration parameters, which, based on the EC file, determine the EC component's working mode and characteristics in different scenarios. The EC configuration file allows users to customize the EC component's functions and parameters according to specific motherboard designs and requirements; for example, fan speed thresholds and battery charging parameters can be set through the configuration file. In simple terms, the EC file is used to set various functions of the EC component, while the EC configuration file is used to select from the functions set in the EC file and configure the parameters of the selected functions. The specific configuration information involved in the configuration text for configuring the corresponding functions is shown in Table 1:

[0044] Table 1

[0045]

[0046] SMBIOS, or System Management BIOS, is a standard for transmitting management information through system firmware, created by the DMTF (Distributed Management Task Force). LEDs are the LEDs on the motherboard used to display the operating status of the motherboard and / or hard drive. PCIe, or Peripheral Component Interconnect Express, is a high-speed serial computer expansion bus standard used on the motherboard. USB (Universal Serial Bus) is a standard interface technology used for transferring data and providing power between a computer and external devices.

[0047] Users can configure the configuration file according to their own needs. The configuration file generated based on the user's settings is stored in the memory in the storage area corresponding to the controller. The controller integrates the read base file with the configuration file of the embedded controller in memory to obtain the corresponding integrated file.

[0048] In a specific embodiment, step S130 includes the following sub-steps: concatenating the basic file and the configuration file to obtain corresponding combination information; adjusting the format of the combination information according to a preset file format to integrate and obtain the integrated file.

[0049] Specifically, the base file and configuration file are concatenated and combined to obtain the corresponding combined information. For example, if the base file is 96KB and the configuration file is 31KB, the combined information is 127KB; alternatively, if the base file is 96KB and the configuration file is 3KB, the combined information is 99KB. The configuration file size can be adjusted as needed.

[0050] The combined information is formatted according to a pre-set file format in the controller. During the format adjustment process, an integrated file corresponding to the combined information needs to be generated based on the file format. For example, a checksum corresponding to the combined information can be generated first according to the checksum generation rules in the file format. The checksum is then used as the last digit and combined with the combined information to obtain 128KB of file information. The file information is then saved as the corresponding integrated file according to the format specifier set in the file format; for example, if the format specifier is "BIN", the file information can be saved as a BIN file as the corresponding integrated file.

[0051] The generated checksum can be used to verify the integrity of the integrated file, preventing information tampering. Furthermore, the checksum generation rule can be set to a modulo function, converting the 127KB combined information into a hexadecimal string, and then performing a modulo operation based on this function. The remainder obtained can be used as a 1KB checksum (padding with zeros to reach 1KB length if necessary). Alternatively, the checksum generation rule can also be set to a hash function, hashing the hexadecimal string to obtain a digest; the hash operation on the hexadecimal string yields a digest, which is then used as a 1KB checksum (padding with zeros to reach 1KB length if necessary). The hash function can be based on SHA256, in which case SHA256 (Secure Hash Algorithm 256) will generate a 32-byte data set for any length (in bits), i.e., a hash value.

[0052] In a specific embodiment, before concatenating the base file and the configuration file to obtain the corresponding combination information, the method further includes: verifying the configuration parameters of the configuration file based on the base file to obtain a verification result; if the verification result is successful, the step of concatenating the base file and the configuration file is executed.

[0053] Specifically, before combining the base file and configuration file, the configuration parameters of the configuration file can be validated based on the base file. The base file specifies the options and parameter ranges for each function. The system can then retrieve the parameter information configured in the configuration file and determine whether each parameter matches the corresponding option in the base file and whether it falls within the corresponding function's parameter range. If all parameters in the configuration file match the corresponding option and fall within the corresponding function's parameter range, the validation result is "passed." If any parameter does not match the corresponding option or falls outside the corresponding function's parameter range, the validation result is "failed."

[0054] If the verification result is successful, the subsequent steps can be performed, namely, the steps of concatenating and combining the base file and the configuration file; if the verification result is unsuccessful, a prompt message can be generated to remind the user.

[0055] S140. Send the integrated file to the embedded controller for flashing.

[0056] The obtained integration file is sent to the embedded controller to be flashed onto the embedded controller. This process is to enable the embedded controller to obtain the latest version of the integration file, so as to facilitate the subsequent implementation of interface function configuration.

[0057] S150. Input the integrated file into the memory for storage and obtain the corresponding memory mapping address.

[0058] Furthermore, the integrated file is input into the storage area in memory corresponding to the controller for storage. After the integrated file is stored, the address corresponding to the storage location of the integrated file can be obtained from memory. This address is also the memory mapping address corresponding to the integrated file.

[0059] S160. If the controller detects a power-on re-energization, it reads the integration file corresponding to the memory-mapped address from the memory and configures the interface functions through the integration file.

[0060] The controller can detect the power-on status of the motherboard. If the controller detects that the motherboard is powered on again, it indicates that the motherboard has restarted and the BIOS system is powered on. The controller reads the integrated file corresponding to the memory mapping address from the memory and completes the corresponding interface function configuration through the integrated file to realize the application of configuring the interface function of the motherboard based on memory sharing.

[0061] In a specific embodiment, step S160 includes the following sub-steps: mapping the memory according to the memory mapping address to obtain the integrated file corresponding to the memory mapping address; parsing the integrated file to obtain the corresponding configuration parameter information; and sending the corresponding configuration instruction according to the configuration items in the configuration parameter information to configure the interface function through the configuration instruction.

[0062] Specifically, memory locations can be mapped based on memory mapping addresses to determine the storage location corresponding to the memory mapping address. The data stored at that location can then be retrieved to obtain the integrated file. The integrated file is parsed to obtain configuration parameter information. Based on the configuration items in this configuration parameter information, corresponding configuration commands are sent. Configuration commands for different configuration items can be sent to specific components via different communication channels. Upon receiving the configuration command, the component configures itself based on the parameter values ​​in the command, thereby completing the interface function configuration. Interface function configuration involves configuring specific parameters such as data transmission and interface function implementation.

[0063] During the parsing of the integrated file, the last 1KB of data in the integrated file can be obtained as a checksum. Based on the aforementioned checksum generation rules, verification information corresponding to the first 127KB of data in the integrated file is generated. Further verification is performed to confirm whether the checksum in the integrated file matches the verification information. If they match, it indicates that the data in the integrated file is complete and has not been tampered with, allowing for subsequent processing. If they do not match, it indicates that the data in the integrated file is incomplete or has been tampered with. In this case, a message indicating that interface function configuration cannot be performed can be issued to remind the user.

[0064] The memory sharing application method for a motherboard system disclosed in the above embodiments includes: sending a memory sharing instruction to set the memory to a shared mode; reading the basic file corresponding to the embedded controller in the memory and integrating it with the configuration file of the embedded controller to obtain a corresponding integrated file; sending the integrated file to the embedded controller for flashing; inputting the integrated file into the memory for storage and obtaining the corresponding memory mapping address; if the controller detects a power-on re-energization, reading the integrated file corresponding to the memory mapping address from the memory and configuring the interface functions through the integrated file. This method, by setting data sharing permissions to share data information in memory, not only enriches the ways to operate on the transmitted data information but also significantly improves data transmission efficiency, enhancing the configuration efficiency and application effect of the motherboard interface functions.

[0065] This invention also provides a memory sharing application device for a motherboard system. This device can be configured in the motherboard controller and is used to execute any of the aforementioned embodiments of the memory sharing application method for a motherboard system. Specifically, please refer to... Figure 3 , Figure 3 This is a schematic block diagram of a memory sharing application device for a motherboard system provided in an embodiment of the present invention.

[0066] like Figure 3 As shown, the memory sharing application device 100 for the motherboard system includes a memory sharing instruction sending unit 110, a basic file reading unit 120, an integration unit 130, a sending unit 140, a storage unit 150, and an interface function configuration unit 160.

[0067] The memory sharing instruction sending unit 110 is used to execute a pre-stored memory sharing instruction to set the memory to a shared mode.

[0068] The basic file reading unit 120 is used to read the basic file corresponding to the embedded controller in memory.

[0069] In a specific embodiment, the basic file reading unit 120 includes: an instruction sending unit, used to send a memory information sharing instruction to the embedded controller to control the embedded controller to perform memory sharing settings; and a reading unit, used to read the corresponding basic file from the memory according to the base address of the embedded controller.

[0070] Integration unit 130 is used to integrate the basic file with the configuration file of the embedded controller to obtain a corresponding integrated file.

[0071] In a specific embodiment, the integration unit 130 includes: a splicing and combining unit, used to splice and combine the basic file and the configuration file to obtain corresponding combination information; and a format adjustment unit, used to adjust the format of the combination information according to a preset file format to integrate and obtain the integrated file.

[0072] The sending unit 140 is used to send the integrated file to the embedded controller for flashing.

[0073] Storage unit 150 is used to input the integrated file into the memory for storage and obtain the corresponding memory mapping address.

[0074] The interface function configuration unit 160 is used to read the integration file corresponding to the memory mapping address from the memory and configure the interface function through the integration file if the controller detects that the power is turned on again.

[0075] The memory sharing application device for a motherboard system provided in this embodiment of the invention applies the aforementioned memory sharing application method for a motherboard system. It sends a memory sharing instruction to set the memory to shared mode; reads the basic file corresponding to the embedded controller in memory and integrates it with the embedded controller's configuration file to obtain a corresponding integrated file; sends the integrated file to the embedded controller for flashing; inputs the integrated file into memory for storage and obtains the corresponding memory mapping address; if the controller detects a power-on re-energization, it reads the integrated file corresponding to the memory mapping address from memory and configures the interface functions through the integrated file. This method, by setting data sharing permissions to share data information in memory, not only enriches the ways to operate on transmitted data information but also significantly improves data transmission efficiency, enhancing the configuration efficiency and application effect of motherboard interface functions.

[0076] The aforementioned memory sharing application device for motherboard systems can be implemented as a computer program, which can be used in, for example... Figure 4 It runs on the computer device shown.

[0077] Please see Figure 4 , Figure 4 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. The computer device may be a controller used to execute a memory-sharing application method for a motherboard system to achieve communication with an embedded controller based on memory sharing and to configure interface functions.

[0078] See Figure 4 The computer device 500 includes a processor 502, a memory, and a communication interface 505 connected via a communication bus 501. The memory may include a storage medium 503 and internal memory 504.

[0079] The storage medium 503 may store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it causes the processor 502 to execute a memory-sharing application method for the motherboard system. The storage medium 503 may be a volatile storage medium or a non-volatile storage medium.

[0080] The processor 502 provides computing and control capabilities to support the operation of the entire computer device 500.

[0081] The internal memory 504 provides an environment for the execution of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute a memory sharing application method for the motherboard system.

[0082] This communication interface 505 is used for network communication, such as providing data transmission. Those skilled in the art will understand that... Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the computer device 500 to which the present invention is applied. The specific computer device 500 may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0083] The processor 502 is used to run the computer program 5032 stored in the memory to implement the corresponding functions in the memory sharing application method for the motherboard system described above.

[0084] Those skilled in the art will understand that Figure 4 The embodiments of the computer device shown do not constitute a limitation on the specific configuration of the computer device. In other embodiments, the computer device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. For example, in some embodiments, the computer device may include only memory and a processor. In such embodiments, the structure and function of the memory and processor are different from those shown. Figure 4 The embodiments shown are consistent and will not be described again here.

[0085] It should be understood that, in this embodiment of the invention, the processor 502 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0086] In another embodiment of the invention, a computer-readable storage medium is provided. This computer-readable storage medium may be volatile or non-volatile. The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps included in the above-described method for memory sharing in a motherboard system.

[0087] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the devices, apparatuses, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0088] In the embodiments provided by this invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Units with the same function may be grouped into one unit. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0089] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0090] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0091] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned computer-readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks.

[0092] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A memory sharing application method for a mainboard system, characterized in that, The method is applied to a controller arranged on a mainboard, and a memory and an embedded controller in communication connection with the controller are further arranged on the mainboard, and the method comprises: executing a pre-stored memory sharing instruction to set the memory as a sharing mode; reading a basic file corresponding to the embedded controller in the memory; integrating the basic file and a configuration file of the embedded controller to obtain a corresponding integrated file; sending the integrated file to the embedded controller for flashing; inputting the integrated file into the memory for storage and obtaining a corresponding memory mapping address; if the controller detects power-on again, reading the integrated file corresponding to the memory mapping address from the memory and performing interface function configuration through the integrated file; the integrating the basic file and the configuration file of the embedded controller to obtain the corresponding integrated file comprises: splicing and combining the basic file and the configuration file to obtain corresponding combination information; adjusting the format of the combination information according to a pre-set file format to obtain the integrated file; before the splicing and combining the basic file and the configuration file to obtain the corresponding combination information, further comprising: performing configuration parameter verification on the configuration file according to the basic file to obtain a verification result; the basic file is provided with selectable items of each function and parameter ranges of each function, each parameter information in the configuration file is obtained and it is judged whether the parameter information matches the selectable items of the corresponding function in the basic file and whether the parameter information is located in the parameter range of the corresponding function, so as to obtain the verification result; if the verification result is passed, the splicing and combining the basic file and the configuration file is executed.

2. The memory sharing application method for a mainboard system according to claim 1, wherein, the reading the basic file corresponding to the embedded controller in the memory comprises: sending a memory information sharing instruction to the embedded controller to control the embedded controller to perform memory sharing setting; reading the corresponding basic file from the memory according to the base address of the embedded controller.

3. The memory sharing application method for a mainboard system according to claim 1 or 2, wherein, the reading the integrated file corresponding to the memory mapping address from the memory and performing interface function configuration through the integrated file comprises: performing position mapping on the memory according to the memory mapping address to obtain the integrated file corresponding to the memory mapping address; analyzing the integrated file to obtain corresponding configuration parameter information; sending a corresponding configuration instruction according to the configuration item in the configuration parameter information to perform interface function configuration through the configuration instruction.

4. A memory sharing application apparatus for a mainboard system, characterized by, The device is arranged in a controller arranged on a mainboard, and a memory and an embedded controller in communication connection with the controller are further arranged on the mainboard, and the device is used for executing the memory sharing application method for the mainboard system according to any one of claims 1-3, and the device comprises: a memory sharing instruction sending unit for executing a pre-stored memory sharing instruction to set the memory as a sharing mode; a basic file reading unit for reading a basic file corresponding to the embedded controller in the memory; The integration unit is configured to integrate the basic file and the configuration file of the embedded controller to obtain a corresponding integrated file; The sending unit is configured to send the integrated file to the embedded controller for flashing; The storage unit is configured to store the integrated file in the memory and obtain a corresponding memory mapping address; The interface function configuration unit is configured to read the integrated file corresponding to the memory mapping address from the memory and perform interface function configuration through the integrated file if the controller detects power-on again.

5. The memory sharing application apparatus for a mainboard system according to claim 4, wherein, The basic file reading unit comprises: The instruction sending unit is configured to send a memory information sharing instruction to the embedded controller to control the embedded controller to perform memory sharing setting; The reading unit is configured to read a corresponding basic file from the memory according to a base address of the embedded controller.

6. The memory sharing application apparatus for a mainboard system according to claim 4, wherein, The integration unit comprises: The splicing and combining unit is configured to splice and combine the basic file and the configuration file to obtain corresponding combination information; The format adjustment unit is configured to adjust the format of the combination information according to a preset file format to obtain the integrated file.

7. A computer device, comprising: The device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus; The memory is configured to store a computer program; The processor is configured to execute the program stored in the memory to implement the steps of the memory sharing application method for the mainboard system in any one of claims 1-3.

8. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the memory sharing application method for the mainboard system in any one of claims 1-3.

Images