CN115080069A

CN115080069A - Debugging method and device for baseboard management controller, electronic equipment and storage medium

Info

Publication number: CN115080069A
Application number: CN202210689010.5A
Authority: CN
Inventors: 黄帅; 朱英澍; 冯俊东
Original assignee: Suzhou Inspur Intelligent Technology Co Ltd
Current assignee: Suzhou Inspur Intelligent Technology Co Ltd
Priority date: 2022-06-16
Filing date: 2022-06-16
Publication date: 2022-09-20

Abstract

The application discloses a debugging method and device of a baseboard management controller, electronic equipment and a storage medium, and relates to the technical field of computers. The method comprises the following steps: compiling a target program to generate a substrate management controller image file, and a kernel file and a network file system corresponding to the image file; and linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection mode, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory. The method and the device can flexibly debug the mirror image of the substrate management controller, shorten the debugging period and achieve the purposes of modifying codes and compiling and debugging at the same time.

Description

Debugging method and device for baseboard management controller, electronic equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for debugging a baseboard management controller, an electronic device, and a storage medium.

Background

Platform management represents a series of monitoring and control functions, and the object of operation is system hardware. Such as by monitoring the temperature, voltage, fan, power supply, etc. of the system and making adjustments to ensure that the system is in a healthy state. Of course, if the system is not normal, the system can be restarted in a reset mode. Meanwhile, the platform management is also responsible for recording information and log records of various hardware and is used for prompting a user and positioning subsequent problems. The above functions can be implemented by integrating the above functions into a Controller, which is called a Baseboard Management Controller (BMC). The sensors of the baseboard management controller can measure parameters of the hardware components by embedding the hardware components. The baseboard management controller needs to be debugged before detecting the hardware components of the server.

In the prior art, implementation of each function of the BMC needs corresponding firmware support, and an existing server supports one flash chip or two active and standby flash chips to store a BMC firmware file. When the baseboard management controller is debugged, firstly, functions to be realized are written into engineering codes in a code module mode, then the whole engineering codes are compiled into an independent mirror image file, then the mirror image file is uploaded to the inside of the current BMC, and finally an upgrading command is called to erase the whole flash chip. And the process of flashing the image file into the flash takes longer time. Therefore, the debugging process of the baseboard management controller is inefficient and takes a long time.

Disclosure of Invention

In order to solve at least one of the problems mentioned in the background art, the present application provides a method and an apparatus for debugging a BMC, an electronic device, and a storage medium, which can flexibly debug a BMC image, shorten a debugging period, and achieve the purposes of modifying a code and compiling and debugging at the same time.

The embodiment of the application provides the following specific technical scheme:

in a first aspect, a method for debugging a baseboard management controller is provided, where the method is applied to a debugging end, and the method includes:

compiling a target program to generate a substrate management controller image file, and a kernel file and a network file system corresponding to the image file;

and linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection mode, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory.

Further, the step of linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection manner, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory, includes:

the directory where the kernel file is located and the directory where the network file system is located are linked to a target directory in a soft connection mode;

and configuring a simple file transfer protocol service and a network file system service according to the target directory so that a baseboard management controller remotely guides the kernel file according to the simple file transfer protocol service and mounts the network file system according to the network file system service.

Further, after configuring the trivial file transfer protocol service and the network file system service according to the target directory, the method further comprises:

restarting a port mapping service and a network file system kernel service to enable the network file system service.

In a second aspect, a baseboard management controller debugging method is provided, and is applied to a baseboard management controller, the method includes:

entering a U-boot configuration mode;

the method comprises the steps of communicating to a target directory of a local compiling environment through a network, and remotely guiding a kernel file generated by compiling the local compiling environment according to the target directory;

and mounting the network file system generated by compiling the local compiling environment according to the target directory.

Further, the target directory connected to the native compilation environment via the network includes:

setting the own ip address of the U-boot through a command line in the configuration mode;

configuring an ip address of the local compiling environment;

and communicating the ip address of the local compiling environment to the target directory through a network.

Further, the communicating to the target directory through a network according to the ip address of the native compilation environment includes:

setting an environment variable of the U-boot, wherein the environment variable specifies an ip address of the native compilation environment and the target directory;

and communicating the environment variable to the target directory through a network.

In a third aspect, a baseboard management controller debugging apparatus is provided, which is applied to a debugging end, and the apparatus includes:

the compiling module is used for compiling the target program and generating a substrate management controller image file and a kernel file and a network file system which correspond to the image file;

and the link module is used for linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection mode, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory.

In a fourth aspect, a baseboard management controller debugging apparatus is provided, which is applied to a baseboard management controller, and the apparatus includes:

the U-boot configuration module is used for entering a U-boot configuration mode;

the network guide module is used for communicating to a target directory of a local compiling environment through a network and remotely guiding a kernel file generated by compiling the local compiling environment according to the target directory;

and the network mounting module is used for mounting the network file system generated by compiling the local compiling environment according to the target directory.

In a fifth aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the baseboard management controller debugging method when executing the computer program.

In a sixth aspect, a computer-readable storage medium is provided, which stores computer-executable instructions for performing the baseboard management controller debugging method.

The embodiment of the application has the following beneficial effects:

according to the debugging method and device for the baseboard management controller, the electronic equipment and the storage medium, the BMC mirror image can be flexibly debugged, and the debugging period is shortened; based on the mirror image guide function of the U-boot, the kernel file and the network file system generated by local compiling are mounted on the baseboard management controller, which is equivalent to the baseboard management controller running the code compiled by the debugging end, so that the purposes of modifying the code and compiling and debugging are achieved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a general flowchart illustrating a baseboard management controller debugging method applied to a debugging end according to an embodiment of the present application;

fig. 2 is a general flowchart illustrating a baseboard management controller debugging method applied to a baseboard management controller according to an embodiment of the present application;

FIG. 3 illustrates a structural diagram of a target directory according to one embodiment of the present application;

FIG. 4 shows a detailed flowchart of a baseboard management controller debugging method applied to a baseboard management controller according to an embodiment of the present application;

fig. 5 is a schematic structural diagram illustrating a baseboard management controller debugging apparatus applied to a debugging end according to an embodiment of the present application;

fig. 6 is a schematic structural diagram illustrating a baseboard management controller debugging apparatus applied to a baseboard management controller according to an embodiment of the present application;

FIG. 7 illustrates an exemplary system that can be used to implement the various embodiments described in this application.

Detailed Description

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be understood that throughout the description and claims of this application, unless the context clearly requires otherwise, the words "comprise", "comprising", and the like, are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is, what is meant is "including, but not limited to".

Example one

The application provides a debugging method of a baseboard management controller, which is applied to a debugging end and includes the following steps:

s1, compiling a target program to generate a mirror image file of the baseboard management controller, and a kernel file and a network file system corresponding to the mirror image file;

and S2, linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection mode, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory.

Specifically, in the routine development process of the BMC firmware, firstly, functions to be realized are written into engineering codes in the form of code modules, then, the whole engineering codes are compiled into an independent mirror image file, then, the mirror image file is uploaded into the current BMC, and finally, an upgrade command is called to erase and write the whole flash chip. The whole process often takes a long time, and even a small function change may require multiple steps of compiling, erasing flash images, verifying, and the like. In the whole debugging process, the most time-consuming part is the BMC Flash burning process, and operations such as restarting and the like are required after burning, so that the total time consumption is long. And by compiling the target program, the kernel file and the network file system generated by compiling are mounted on the BMC ARM processor, and the BMC can directly run the code compiled by the debugging end in a network mounting mirror image mode, so that the process of burning a Flash chip during debugging is omitted, and the debugging period is greatly shortened.

Specifically, the BMC guides the kernel file through TFTP based on a U-boot image guide function, and mounts the network file system through NFS. Among them, TFTP (Trivial File Transfer Protocol) is a small and easy-to-implement File Transfer Protocol. TFTP is based on UDP (User Datagram Protocol) datagrams, which require its own error correction measures. TFTP only supports file transfer, does not support interaction, does not have a large command set, does not have directory listing functionality, and does not enable user authentication. But the code of the method occupies a smaller memory, the TFTP code can be solidified without a hard disk, and the method is very suitable for smaller computers and special-purpose equipment and is a protocol for carrying out simple file transmission between a client and a server through a TCP/IP protocol. NFS (Network File System), one of the File systems supported by FreeBSD, allows sharing of resources between computers in a Network over a TCP/IP Network. NFS allows an application process to open a remote file and start reading and writing data at a specific location in the file, puts the embedded root file system in a medium on the network through NFS, and transmits commands through UDP datagrams in ethernet.

In some embodiments, S2 includes:

s21, linking the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection mode;

s22, configuring the simple file transfer protocol service and the network file system service according to the target directory, so that the baseboard management controller remotely boots the kernel file according to the simple file transfer protocol service and mounts the network file system according to the network file system service.

Specifically, first, NFS and TFTP services need to be configured in a local compilation environment, where NFS is used to mount a BMC network file system and TFTP is used to remotely boot a kernel file. In the local compilation environment, a Build/tftpbook directory (directory where the ui kernel file is located) and a Build/output/im tree directory (directory where the im tree network file system is located) are generated, and the structures of the two directories are shown in fig. 3. The local compiling environment refers to an actual compiling environment of the BMC mirror Image, namely a process of compiling the BMC source code into the Image mirror Image. Generally, only whether the BMC image (bin file) can be successfully compiled is concerned, and the bin file is burned into the BMC Flash through a burner or an online upgrade mode after the successful compiling is generally performed. In this embodiment, network boot is performed at the U-boot startup stage by means of TFTP and NFS on the uinimage (the kernel file) and the ImageTree (the network file system) corresponding to the image file generated in the BMC image compilation process, so as to omit the burning process of the bin file.

Illustratively, a soft link of the target root file system is established first, and the two directories are linked to the target directory in a soft link manner. For a TFTP server, softly linking a directory where a user image (kernel file) generated in the local compiling environment compiling process to a local/home/company/tftpboot directory through ln-s/home/company/workpage/built/tftpboot/home/company/tftpboot; and for the NFS server, softly linking a directory in which an ImageTree (file system) generated in the local compiling environment compiling process is located to a local/home/complex/NFS directory through ln-s/home/complex/works-space/built/ImageTree/home/complex/NFS. This facilitates subsequent related configuration of the tftpboot/nfs service.

Illustratively, then, the NFS service is configured accordingly. Modifying/etc/exports, wherein the/etc/exports is a related configuration file of the NFS and can be modified by a simple vim editing instruction; then configuration is performed through/home/match/nfs (rw, sync, no _ root _ square), and updated using the command superimports fs-r. The name/file/NFS is to make the NFS server of the local compilation environment recognize the directory, indicates that any NFS client can access the directory, sync is in a synchronization mode, and no _ root _ square indicates a user accessing the NFS shared directory, and if the user is a root user, the user has root authority, that is, authority-related configuration, for the directory. In such a way, the NFS service end of the local compiling environment is configured to have the capability of providing NFS service for the U-boot stage, and can be normally used when the U-boot uses the NFS to access the network file system. Similarly, a TFTP shared directory is added (by creating/etc/xinetd.d/TFTP files and configuring), and TFTP server side configuration of the local compiling environment is configured, so that the TFTP server side configuration can provide TFTP service for a U-boot phase and can be normally used when the U-boot uses the TFTP to boot the uImage kernel file. After the configuration is completed, the local compiling environment has the capacity of providing kernel files and network file system mounting through the network.

In some embodiments, after configuring the trivial file transfer protocol service and the network file system service according to the target directory, the method further comprises:

restarting the port mapping service and the network file system kernel service to enable the network file system service.

Illustratively, the NFS service may be enabled by restarting the portmap service and the NFS-kernel-server service. The port map service (port mapping service) and the NFS-kernel-server service (network file system kernel service) are both services related to the NFS server, and after the NFS server is configured, the two services need to be restarted to enable the configuration to take effect. After taking effect, the BMC can use the NFS function in the U-boot stage to directly and remotely mount the file system generated in the local compiling environment.

In this embodiment, the kernel file generated in the local compilation environment and the directory corresponding to the network file system can be linked to the target directory in a soft connection manner, and NFS service is configured for TFTP service, so that the baseboard management controller remotely guides the kernel file according to the simple file transfer protocol service, and mounts the network file system according to the network file system service, thereby saving a process of burning a Flash chip during modification and debugging, and greatly reducing a debugging period.

Example two

The application provides a debugging method of a baseboard management controller, which is applied to the baseboard management controller, and with reference to fig. 2, the debugging method includes:

s3, entering a U-boot configuration mode;

s4, communicating with a target directory of the local compiling environment through a network, and remotely guiding a kernel file generated by compiling the local compiling environment according to the target directory;

and S5, mounting the network file system generated by compiling the local compiling environment according to the target directory.

Specifically, the BMC mirror mainly comprises two parts, namely a U-boot and a uImage (kernel). Generally, a U-boot, as a BootLoader, must provide an initialization code when a system is powered on, and after initializing a relevant environment when the system is powered on, the BootLoader needs to boot a complete operating system, and then hands a controller to the operating system. The BootLoader is simply a small program, which is executed when the system is powered on, and through the small program, hardware devices can be initialized, such as a Central Processing Unit (CPU), a Flash, a serial port, a network, and the like, and after the initialization is completed, an operating system kernel (kernel) is called, and the size of the part is only dozens of KB. The uinmage part mainly comprises a system kernel, a BMC file partition and the like, is the most important part in the BMC image, and is a time-consuming part in the burning file.

This is further illustrated below in conjunction with fig. 4:

in some embodiments, a target directory communicated to a native compilation environment over a network, comprises:

s41, setting the self ip address of the U-boot through a command line in the configuration mode;

s42, configuring the ip address of the local compiling environment;

and S43, communicating to the target directory through the network according to the ip address of the local compiling environment.

Specifically, a U-boot configuration mode is entered, an ip address of the U-boot is set through a command line in the configuration mode to ensure network connectivity, an ip address of a local compiling environment is set, a target directory needs to be pointed according to the ip address of the local compiling environment in a network connection mode, a kernel file is guided under the target directory, and a network file system is mounted.

In some embodiments, S43 includes:

s431, setting an environment variable of the U-boot, wherein the environment variable specifies an ip address and a target directory of the local compiling environment;

and S432, communicating to the target directory through a network according to the environment variable.

Specifically, bootargs nfroot parameters need to be configured. bootargs are the most important of the environment variables, and even the entire environment variable can be said to be set around bootargs. bootargs are very flexible, and different collocation of the kernel and the network file system can have different setting methods, or even the bootargs can be directly written into the kernel without setting the bootargs (the setting can be performed in options for configuring the kernel), which causes difficulty in using the bootargs. And root is the location used to specify the kernel and file system. Illustratively, environment variables are configured through root ═ dev/nfs nfsproot ═ xx.xx.xx.xx.xx.xx.xx.xp, tcp, wherein xx.xx.xx.xx.xx.xx.refers to the ip address of the native compilation environment, that is, the environment variables describe a method for directing to an ip address lower/home/compiler/nfs directory of the native compilation environment, a ui kernel file can be guided according to a specified address through a tftpboost command, and after the kernel file is guided, an nfs network file system can be mounted for use.

In this embodiment, the kernel file and the network file system generated by local compilation can be mounted on the baseboard management controller based on the mirror image boot function of the U-boot, which is equivalent to the baseboard management controller running the code compiled by the debugging end, so as to achieve the purpose of modifying the code and compiling and debugging at the same time.

It should be noted that the terms "S1", "S2", etc. are used for descriptive purposes only, are not intended to be used in a specific sense to refer to an order or sequence, and are not intended to limit the present application, but are merely used for convenience in describing the methods of the present application and are not to be construed as indicating the order of the steps. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.

EXAMPLE III

In response to the foregoing embodiment, the present application further provides a device 100 for debugging a baseboard management controller, which is applied to a debugging end and includes a compiling module 110 and a linking module 120, with reference to fig. 5.

The compiling module 110 is configured to compile a target program, and generate a mirror image file of a baseboard management controller, and a kernel file and a network file system corresponding to the mirror image file; the link module 120 is configured to link the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection manner, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory.

Further, the link module 120 is further configured to link the directory where the kernel file is located and the directory where the network file system is located to a target directory in a soft connection manner; and the system is used for configuring a simple file transfer protocol service and a network file system service according to the target directory so that a baseboard management controller remotely guides the kernel file according to the simple file transfer protocol service and mounts the network file system according to the network file system service.

Further, the link module 120 is further configured to restart the port mapping service and the network file system kernel service to enable the network file system service.

For specific limitations of the bmc debugging apparatus 100, reference may be made to the above-mentioned limitations related to the bmc debugging method embodiment, and therefore, the details are not repeated herein. The modules in the bmc debugging apparatus 100 may be implemented in whole or in part by software, hardware, or a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

Example four

Corresponding to the foregoing embodiment, the present application further provides a baseboard management controller debugging apparatus 200, referring to fig. 6, applied to a baseboard management controller, where the apparatus includes a U-boot configuration module 210, a network boot module 220, and a network mount module 230.

The U-boot configuration module 210 is configured to enter a U-boot configuration mode; the network guiding module 220 is used for communicating with a target directory of a local compiling environment through a network, and remotely guiding a kernel file generated by compiling the local compiling environment according to the target directory; and a network mounting module 230, configured to mount the network file system generated by compiling the local compiling environment according to the target directory.

Further, the network boot module 220 is further configured to set an ip address of the U-boot itself through a command line in the configuration mode; and an ip address for configuring the native compilation environment; and the system is also used for communicating the IP address of the local compiling environment to the target directory through a network.

Further, the network boot module 220 is further configured to set an environment variable of the U-boot, where the environment variable specifies an ip address of the native compilation environment and the target directory; and the system is used for communicating to the target directory through a network according to the environment variable.

For specific limitations of the bmc debugging apparatus 200, reference may be made to the above-mentioned limitations related to the bmc debugging method embodiment, and therefore, no further description is given here. The modules in the bmc debugging apparatus 200 may be implemented in whole or in part by software, hardware, or a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

EXAMPLE five

Corresponding to the foregoing embodiments, the present application further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and when the processor executes the computer program, the substrate management controller debugging method may be implemented.

As shown in fig. 7, in some embodiments, the system can be used as the electronic device for the baseboard management controller debugging method in any one of the embodiments. In some embodiments, a system may include one or more computer-readable media (e.g., system memory or NVM/storage) having instructions and one or more processors (e.g., processor (s)) coupled with the one or more computer-readable media and configured to execute the instructions to implement modules to perform actions described herein.

For one embodiment, the system control module may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) and/or any suitable device or component in communication with the system control module.

The system control module may include a memory controller module to provide an interface to the system memory. The memory controller module may be a hardware module, a software module, and/or a firmware module.

System memory may be used, for example, to load and store data and/or instructions for the system. For one embodiment, the system memory may comprise any suitable volatile memory, such as suitable DRAM. In some embodiments, the system memory may include a double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

For one embodiment, the system control module may include one or more input/output (I/O) controllers to provide an interface to the NVM/storage and communication interface(s).

For example, the NVM/storage may be used to store data and/or instructions. The NVM/storage may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drive(s) (HDD (s)), one or more Compact Disc (CD) drive(s), and/or one or more Digital Versatile Disc (DVD) drive (s)).

The NVM/storage may include storage resources that are physically part of the device on which the system is installed, or it may be accessible by the device and not necessarily part of the device. For example, the NVM/storage may be accessible over a network via the communication interface(s).

The communication interface(s) may provide an interface for the system to communicate over one or more networks and/or with any other suitable device. The system may wirelessly communicate with one or more components of the wireless network according to any of one or more wireless network standards and/or protocols.

For one embodiment, at least one of the processor(s) may be packaged together with logic for one or more controllers (e.g., memory controller modules) of the system control module. For one embodiment, at least one of the processor(s) may be packaged together with logic for one or more controllers of the system control module to form a System In Package (SiP). For one embodiment, at least one of the processor(s) may be integrated on the same die with logic for one or more controllers of the system control module. For one embodiment, at least one of the processor(s) may be integrated on the same die with logic of one or more controllers of a system control module to form a system on a chip (SoC).

In various embodiments, the system may be, but is not limited to being: a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, the system may have more or fewer components and/or different architectures. For example, in some embodiments, a system includes one or more cameras, a keyboard, a Liquid Crystal Display (LCD) screen (including touch screen displays), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and speakers.

It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.

In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Those skilled in the art will appreciate that the form in which the computer program instructions reside on a computer-readable medium includes, but is not limited to, source files, executable files, installation package files, and the like, and that the manner in which the computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. In this regard, computer readable media can be any available computer readable storage media or communication media that can be accessed by a computer.

Communication media includes media by which communication signals, including, for example, computer readable instructions, data structures, program modules, or other data, are transmitted from one system to another. Communication media may include conductive transmission media such as cables and wires (e.g., fiber optics, coaxial, etc.) and wireless (non-conductive transmission) media capable of propagating energy waves such as acoustic, electromagnetic, RF, microwave, and infrared. Computer readable instructions, data structures, program modules, or other data may be embodied in a modulated data signal, for example, in a wireless medium such as a carrier wave or similar mechanism such as is embodied as part of spread spectrum techniques. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The modulation may be analog, digital or hybrid modulation techniques.

An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.

EXAMPLE six

Corresponding to the foregoing embodiments, the present application further provides a computer-readable storage medium storing computer-executable instructions for executing a baseboard management controller debugging method.

In the present embodiment, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. For example, computer-readable storage media include, but are not limited to, volatile memory such as random access memory (RAM, DRAM, SRAM); and non-volatile memory such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic/ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disk, tape, CD, DVD); or other now known media or later developed that can store computer-readable information/data for use by a computer system.

While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all changes and modifications that fall within the true scope of the embodiments of the present application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A debugging method of a baseboard management controller is applied to a debugging end, and is characterized by comprising the following steps:

2. The baseboard management controller debugging method of claim 1, wherein the linking the directory in which the kernel file is located and the directory in which the network file system is located to a target directory in a soft connection manner, so that the baseboard management controller remotely guides the kernel file and mounts the network file system according to the target directory, comprises:

3. The baseboard management controller debugging method of claim 2, wherein after configuring the SNTP service and the network file system service according to the target directory, the method further comprises:

4. A debugging method of a baseboard management controller is applied to the baseboard management controller, and is characterized by comprising the following steps:

entering a U-boot configuration mode;

5. The baseboard management controller debugging method of claim 4, wherein the communicating over a network to an object directory of a local compilation environment comprises:

configuring an ip address of the local compiling environment;

6. The baseboard management controller debugging method of claim 5, wherein the communicating to the target directory over a network according to the ip address of the native compiled environment comprises:

7. The utility model provides a base plate management controller debugging device, is applied to the debugging end, its characterized in that, the device includes:

8. A debugging device of a baseboard management controller is applied to the baseboard management controller, and is characterized by comprising:

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the baseboard management controller debugging method according to any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium storing computer-executable instructions for performing the baseboard management controller debugging method according to any one of claims 1 to 6.