A secure real-time bus (SRB) debugging method, related device and storage medium
By introducing caching and centralized feedback mechanisms into the secure real-time bus system, the problems of low debugging efficiency and frequent failures in existing technologies are solved, and efficient and reliable debugging information transmission is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- 北京傲星科技有限公司
- Filing Date
- 2025-12-29
- Publication Date
- 2026-05-08
AI Technical Summary
The existing Secure Real-Time Bus (SRB) system has inefficient debugging methods that are prone to errors, and frequent plugging and unplugging of serial cables can easily lead to malfunctions.
The target security real-time bus device periodically stores its own and other devices' debugging information into the local cache, and feeds back the debugging information of all devices when connected to the host computer, thereby achieving centralized management and efficient transmission of information.
It improves debugging efficiency, avoids malfunctions caused by frequent plugging and unplugging of serial cables, and ensures the accuracy and integrity of data transmission.
Smart Images

Figure CN121433993B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of secure real-time bus technology, and in particular to a debugging method for a secure real-time bus (SRB) and related equipment and storage media. Background Technology
[0002] Security Realtime Bus (SRB) technology originates from the proprietary Ethernet for Plant Automation (EPA) technical standard. Specifically, within the EPA technical framework, it is an equipment-specific security real-time bus developed through improvements to meet the application requirements of specialized industries, which demand high real-time performance, high bandwidth, and high reliability.
[0003] To ensure the normal operation of the SRB system, troubleshooting techniques are needed to analyze and locate problems when SRB system malfunctions, such as packet loss or packet errors. The current debugging method involves connecting a serial cable to a USB port on a host computer, and then sequentially plugging this serial cable into the serial ports of each SRB board. Finally, the host computer reads the debugging information from all connected SRB devices. After reading the debugging information from all devices, the information is organized for system debugging.
[0004] However, this method requires multiple operations to read all the debugging information and also necessitates the processing of a large amount of debugging data, making it very inefficient and prone to errors. Furthermore, frequent plugging and unplugging of the serial cable can easily lead to serial cable failure. Summary of the Invention
[0005] In view of the shortcomings of the prior art, this application provides a debugging method for a Secure Real-Time Bus (SRB) and related equipment and storage media to solve the problems of low efficiency and easy error in the prior art.
[0006] To achieve the above objectives, this application provides the following technical solution:
[0007] The first aspect of this application provides a method for debugging a Secure Real-Time Bus (SRB), including:
[0008] The target security real-time bus device periodically stores its current debugging information in the local cache address corresponding to the target security real-time bus device; wherein, the target security real-time bus device can be any designated security real-time bus device;
[0009] The target security real-time bus device receives debug information messages periodically sent by each non-target security real-time bus device; wherein, the non-target security real-time bus devices are all other security real-time bus devices besides the target security real-time bus device; the debug information messages sent by the non-target security real-time bus devices are generated by the non-target security real-time bus devices using their own current debug information;
[0010] The target security real-time bus device extracts the current debugging information of the non-target security real-time bus device from the debugging information message;
[0011] The target security real-time bus device stores the current debugging information of the non-target security real-time bus device in the local cache address corresponding to the non-target security real-time bus device;
[0012] When the target security real-time bus device is connected to the host computer, it feeds back the current debugging information of each security real-time bus device in the cache address corresponding to each security real-time bus device to the host computer, so as to use the current debugging information of each security real-time bus device for debugging.
[0013] Optionally, in the above-described debugging method for the Secure Real-Time Bus (SRB), the target SRB device receives debugging information messages periodically sent by each non-target SRB device, including:
[0014] The target security real-time bus device receives debug information messages sent periodically by each non-target security real-time bus device to the address of the target security real-time bus device via Ethernet; wherein, the debug information message is composed of the non-target security real-time bus data according to the Ethernet header, destination address, source address and its own current debug information; the destination address is the address of the target security real-time bus device and the source address is the address of the non-target security real-time bus data.
[0015] Optionally, in the above-described debugging method for the Secure Real-Time Bus (SRB), the target SRB device stores the current debugging information of the non-target SRB device into the local cache address corresponding to the non-target SRB device, including:
[0016] The target security real-time bus device updates the debugging information and source address in the debugging information message to the cache address in its local cache that corresponds to the source address in the debugging information message.
[0017] Optionally, in the above-described debugging method for the Secure Real-Time Bus (SRB), when the target SRB device is connected to the host computer, it feeds back the current debugging information of each SRB device in the buffer address corresponding to each SRB device to the host computer, including:
[0018] When the target security real-time bus device is connected to the host computer, it feeds back the debugging information and source address in each of the buffer addresses as a message to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address.
[0019] Optionally, in the above-described debugging method for the Secure Real-Time Bus (SRB), the target SRB device receives debugging information messages periodically sent by each non-target SRB device, including:
[0020] The target security real-time bus device receives debugging information messages periodically forwarded by each non-target security real-time bus device through the target switch; wherein, the target switch is the switch to which the target security real-time bus device is connected; each non-target security real-time bus device connected to the target switch directly sends debugging information messages to the target switch; each non-target security real-time bus device not connected to the target switch sends debugging information messages to the target switch through the switch it is connected to.
[0021] Optionally, the above-described debugging method for the Secure Real-Time Bus (SRB) also includes:
[0022] The target security real-time bus device responds to the user's target DIP switch activation operation to enable the networking function; wherein, the target DIP switch of each security real-time bus device is initially in the off state by default.
[0023] The target security real-time bus device configures each security real-time bus device according to the configuration information provided by the configuration software, and realizes networking with each security real-time bus device.
[0024] A second aspect of this application provides a target secure real-time bus device, wherein the target secure real-time bus device is any designated secure real-time bus device, and the target secure real-time bus device includes:
[0025] The first cache unit is used to periodically store its current debugging information into the cache address corresponding to the target security real-time bus device locally;
[0026] A receiving unit is used to receive debug information messages periodically sent by each non-target security real-time bus device; wherein, the non-target security real-time bus device refers to the remaining security real-time bus devices; the debug information messages sent by the non-target security real-time bus devices are generated by the non-target security real-time bus devices using their own current debug information;
[0027] The extraction unit is used to extract the current debugging information of the non-target secure real-time bus device from the debugging information message;
[0028] The second cache unit is used to store the current debugging information of the non-target secure real-time bus device into the local cache address corresponding to the non-target secure real-time bus device;
[0029] The feedback unit is used to feed back the current debugging information of each security real-time bus device in each buffer address to the host computer when connected to the host computer, so as to use the current debugging information of each security real-time bus device for debugging.
[0030] Optionally, in the aforementioned target secure real-time bus device, the receiving unit includes:
[0031] The first receiving unit is configured to receive debug information messages periodically sent by each non-target secure real-time bus device to the address of the target secure real-time bus device via Ethernet; wherein, the debug information message is composed of the non-target secure real-time bus data according to the Ethernet header, destination address, source address and its own current debug information; the destination address is the address of the target secure real-time bus device and the source address is the address of the non-target secure real-time bus data.
[0032] Optionally, in the aforementioned target secure real-time bus device, the second buffer unit includes:
[0033] The second cache subunit is used to update the debugging information and source address in the debugging information message to the cache address in the local cache corresponding to the source address in the debugging information message.
[0034] Optionally, in the aforementioned target security real-time bus device, the feedback unit includes:
[0035] The feedback subunit is used to feed back the debugging information and source address in each of the buffer addresses as a message to the host computer when connected to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address.
[0036] Optionally, in the aforementioned target secure real-time bus device, the receiving unit includes:
[0037] The second receiving unit is used to receive debugging information messages forwarded periodically by each non-target security real-time bus device through the target switch; wherein, the target switch is the switch to which the target security real-time bus device is connected; each non-target security real-time bus device connected to the target switch directly sends debugging information messages to the target switch; each non-target security real-time bus device not connected to the target switch sends debugging information messages to the target switch through the switch to which it is connected.
[0038] Optionally, the aforementioned target security real-time bus device further includes:
[0039] The activation unit is used to respond to the user's target DIP switch activation operation to enable the networking function; the target DIP switches of each security real-time bus device are initially in the off state by default.
[0040] The networking unit is used to configure each security real-time bus device according to the configuration information provided by the configuration software, and to realize networking with each security real-time bus device.
[0041] A third aspect of this application provides an electronic device, comprising:
[0042] Memory and processor;
[0043] The memory is used to store programs;
[0044] The processor is used to execute the program, which, when executed, is specifically used to implement the debugging method of the Secure Real-Time Bus (SRB) as described in any of the above.
[0045] The fourth aspect of this application provides a computer storage medium for storing a computer program, which, when executed by a processor, is used to implement the debugging method of the Secure Real-Time Bus (SRB) as described in any of the preceding claims.
[0046] This application provides a debugging method for a Secure Real-Time Bus (SRB). A target SRB device periodically stores its current debugging information in its local buffer address. The target SRB device can be any designated SRB device. Furthermore, the target SRB device receives debugging information messages periodically sent by each non-target SRB device. The non-target SRB devices are all other SRB devices besides the target SRB device. The debugging information messages sent by the non-target SRB devices are generated by the non-target SRB devices using their own current debugging information. Next, the target SRB device extracts the current debugging information of the non-target SRB devices from the debugging information messages. Then, the target SRB device stores the current debugging information of the non-target SRB devices in its local buffer address. Finally, when the target SRB device connects to a host computer, it feeds back the current debugging information of each SRB device from its buffer address to the host computer for debugging. By improving each secure real-time bus device and designating any one secure real-time bus device, each secure real-time bus device can send debugging data to a single secure real-time bus device. Therefore, the host computer only needs to connect to that secure real-time bus device to consistently obtain debugging data from all secure real-time bus devices, effectively improving efficiency, avoiding errors, and preventing malfunctions caused by frequent plugging and unplugging of serial cables. Attached Figure Description
[0047] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0048] Figure 1 A flowchart illustrating a debugging method for a Secure Real-Time Bus (SRB) provided in this application embodiment;
[0049] Figure 2 A flowchart illustrating a method for setting up a target secure real-time bus device, as provided in this application embodiment;
[0050] Figure 3 This application provides a schematic diagram of the architecture of a secure real-time bus system.
[0051] Figure 4A schematic diagram illustrating the format of a debugging information message provided in an embodiment of this application;
[0052] Figure 5 A schematic diagram of the architecture of a target security real-time bus device provided in this application embodiment;
[0053] Figure 6 This is a schematic diagram of the architecture of an electronic device provided in an embodiment of this application. Detailed Implementation
[0054] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0055] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0056] This application provides a method for debugging a Secure Real-Time Bus (SRB), such as... Figure 1 As shown, it includes the following steps:
[0057] S101. The target security real-time bus device periodically stores its current debugging information into the local cache address corresponding to the target security real-time bus device.
[0058] The target security real-time bus device is any designated security real-time bus device, which can collect debugging information of all security real-time bus devices through a single security real-time bus device, and then feed back the debugging information of all security real-time bus devices to the host computer at once through a single security real-time bus device.
[0059] Other secure real-time bus devices are non-target secure real-time bus devices, that is, non-target secure real-time bus devices are all other secure real-time bus devices besides the target secure real-time bus device.
[0060] Alternatively, all secure real-time bus devices may be updated in the same way to give them the same full functionality, namely, the functions of both target and non-target secure real-time bus devices. This allows each secure real-time bus device to function as either a target or non-target device, enabling efficient switching to the target secure real-time bus device when the current target device fails.
[0061] Optionally, another embodiment of this application provides a method for setting up a target secure real-time bus device, such as... Figure 2 As shown, it includes:
[0062] S201, The target security real-time bus device responds to the user's target DIP switch activation operation and enables the networking function.
[0063] The target DIP switches of each security real-time bus device are initially set to the off state by default.
[0064] Specifically, each secure real-time bus device has a function module DIP switch, also known as the target DIP switch. This function module DIP switch is either "ON" or "OFF". All secure real-time bus devices are shipped with this switch set to "OFF" by default. Before powering on, switch the DIP switch of one of the secure real-time bus devices to "ON".
[0065] S202. The target security real-time bus device configures each security real-time bus device according to the configuration information provided by the configuration software, and realizes networking with each security real-time bus device.
[0066] After power-on, the target security real-time bus devices will self-organize their network and configure themselves according to the configuration information provided by the configuration software. Once configured, they enter the working state. Based on the "ON" state of the DIP switch, the device designated as the debugging information receiving device is identified as the target security real-time bus device. The remaining security real-time bus devices, whose function DIP switches are set to "OFF," all act as transmitting devices, i.e., non-target security real-time bus devices.
[0067] Since the target secure real-time bus device does not need to send debugging information to other devices, and in order for the host computer to sequentially obtain the latest debugging information of all secure real-time bus devices, including its own, the target secure real-time bus device periodically obtains its own current debugging information. For example, it obtains its current debugging information when the timer counts down to 1 second. This obtained current debugging information is then stored in a designated address for later aggregation. To avoid overwriting the debugging information of other secure real-time bus devices and to differentiate between the debugging information of each secure real-time bus device, the target secure real-time bus device's debugging information is stored in the local cache address corresponding to the target secure real-time bus device.
[0068] The debugging information includes, but is not limited to, statistical information: Ethernet packet reception count, Ethernet packet transmission count, Ethernet packet reception verification error information, and alarm information: high temperature alarm, low temperature alarm, high humidity alarm, high current alarm, high voltage alarm, link disconnection alarm, etc.
[0069] S102. The target security real-time bus device receives debugging information messages periodically sent by each non-target security real-time bus device.
[0070] Among them, the debug information messages sent by the non-target secure real-time bus device are generated by the non-target secure real-time bus device using its own current debug information.
[0071] Specifically, each non-target secure real-time bus device independently acquires its own current debugging information at regular intervals, generates a debugging information message, and sends the debugging information message to the target secure real-time bus device. For example, when the timer on a non-target secure real-time bus device counts to 1 second, it acquires its own current debugging information, then uses the current debugging information to generate a debugging information message and sends it to the target secure real-time bus device.
[0072] It should be noted that the time interval for updating its own debugging information and the debugging data of other security real-time bus devices is usually the same, so steps S101 and S102 are usually executed simultaneously.
[0073] Optionally, in another embodiment of this application, one specific implementation of step S102 includes:
[0074] The target security real-time bus device receives debugging information messages periodically forwarded by each non-target security real-time bus device through the target switch.
[0075] The target switch is the switch to which the target security real-time bus devices are connected. Each non-target security real-time bus device connected to the target switch directly sends debug information messages to the target switch. Each non-target security real-time bus device not connected to the target switch sends debug information messages to the target switch through the switch it is connected to.
[0076] In this embodiment, a switch is used to transmit debugging information for each secure real-time bus device. However, a single switch can only support a limited number of secure real-time bus devices, and since there are many secure real-time bus devices, multiple switches are needed to connect them.
[0077] Specifically, such as Figure 3 As shown, a switch connects multiple security real-time bus devices, and these switches are interconnected. Therefore, each security real-time bus device connected to the same switch 1 as the target security real-time bus device (SRB device 1) directly sends debug information messages to switch 1, which then forwards the debug information to SRB device 1. Security real-time bus devices connected to other switches send debug information messages to the switches they are connected to. These switches then forward the messages to switch 1, which in turn forwards them to SRB device 1.
[0078] Optionally, in another embodiment of this application, one specific implementation of step S102 includes:
[0079] The target security real-time bus device receives debug information messages periodically sent by each non-target security real-time bus device to the address of the target security real-time bus device via Ethernet.
[0080] Among them, such as Figure 4 As shown, the debug information message consists of non-target Secure Real-Time Bus (SSL) data, organized into an Ethernet header, destination address, source address, and its own current debug information. The destination address is the address of the target SSL device, and the source address is the address of the non-target SSL data.
[0081] Therefore, the debug information message can be sent to the target secure real-time bus device based on the destination address in the debug information message. Setting the source address in the debug information message allows the target secure real-time bus device to know which non-target secure real-time bus device sent the received debug information message, so that the debug information in the debug information message can be accurately cached in the corresponding address. This makes it easier for the host computer to clearly obtain the debug information of each secure real-time bus device.
[0082] S103. The target security real-time bus device extracts the current debugging information of the non-target security real-time bus device from the debugging information message.
[0083] The target security real-time bus device extracts the current debugging information from each debugging information message it receives.
[0084] S104. The target security real-time bus device stores the current debugging information of the non-target security real-time bus device into the local cache address corresponding to the non-target security real-time bus device.
[0085] Similarly, to prevent the current debugging information stored by different security real-time bus devices from interfering with each other, and to distinguish the current debugging information of each security real-time bus device, a corresponding buffer address is set for each security real-time bus device, including target security real-time bus devices and non-target security real-time bus devices. Therefore, the current debugging information of non-target security real-time bus devices is stored in their corresponding buffer address, overwriting the previously stored information.
[0086] Optionally, the debug information message may use, for example Figure 4 In another embodiment of this application, as shown in the format, step S104 includes:
[0087] The target security real-time bus device updates the debugging information and source address in the debugging information message to the local cache address corresponding to the source address in the debugging information message.
[0088] To facilitate the subsequent acquisition of debugging information by the host computer and to distinguish the debugging information of each security real-time bus device, the debugging information and the source address of the security real-time bus device are cached together. The cache address corresponding to the source address is the cache address corresponding to the security real-time bus device, so the debugging information and the source address are stored in this cache address.
[0089] S105. When the target security real-time bus device is connected to the host computer, it feeds back the current debugging information of each security real-time bus device in the cache address corresponding to each security real-time bus device to the host computer so as to use the current debugging information of each security real-time bus device for debugging.
[0090] Since all the secure real-time bus devices are already cached in the target secure real-time bus device, when debugging is needed, only a serial cable is required to connect the host computer to the target secure real-time bus device. At this time, the target secure real-time bus device feeds back the current debugging information of each secure real-time bus device in its local cache address to the host computer through the connected serial cable.
[0091] Optionally, when the source address is also cached in the cached data, in another embodiment of this application, a specific implementation of step S105 includes:
[0092] When the target security real-time bus device connects to the host computer, it feeds back the debugging information in each buffer address and the source address as a message to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address.
[0093] Since the source address corresponds to the secure real-time bus device, in order to make it easier for the host computer to distinguish which secure real-time bus device the obtained debugging information belongs to, the debugging information in each buffer address and the source address will be fed back to the host computer as a single message.
[0094] Of course, this is just one option. Alternatively, the host computer can be given the address of its buffer, and the corresponding identifier of the secure real-time bus device can be sent at the same time as the debugging information.
[0095] This application provides a debugging method for a Secure Real-Time Bus (SRB). A target SRB device periodically stores its current debugging information in its local buffer address. The target SRB device can be any designated SRB device. Furthermore, the target SRB device receives debugging information messages periodically sent by each non-target SRB device. The non-target SRB devices are all other SRB devices besides the target SRB device. The debugging information messages sent by the non-target SRB devices are generated by the non-target SRB devices using their own current debugging information. Next, the target SRB device extracts the current debugging information of the non-target SRB devices from the debugging information messages. Then, the target SRB device stores the current debugging information of the non-target SRB devices in its local buffer address. Finally, when the target SRB device connects to a host computer, it feeds back the current debugging information of each SRB device from its buffer address to the host computer for debugging. By improving each secure real-time bus device and designating any one secure real-time bus device, each secure real-time bus device can send debugging data to a single secure real-time bus device. Therefore, the host computer only needs to connect to that secure real-time bus device to consistently obtain debugging data from all secure real-time bus devices, effectively improving efficiency, avoiding errors, and preventing malfunctions caused by frequent plugging and unplugging of serial cables.
[0096] Another embodiment of this application provides a target secure real-time bus device, wherein the target secure real-time bus device is any designated secure real-time bus device, such as... Figure 5 As shown, the target security real-time bus device includes:
[0097] The first cache unit 501 is used to periodically store its current debugging information into the cache address corresponding to the target security real-time bus device.
[0098] The receiving unit 502 is used to receive debug information messages periodically sent by each non-target security real-time bus device. The non-target security real-time bus devices are the remaining security real-time bus devices. The debug information messages sent by the non-target security real-time bus devices are generated by the non-target security real-time bus devices using their own current debug information.
[0099] Extraction unit 503 is used to extract the current debugging information of non-target security real-time bus devices from the debugging information message.
[0100] The second cache unit 504 is used to store the current debugging information of the non-target secure real-time bus device into the local cache address corresponding to the non-target secure real-time bus device.
[0101] Feedback unit 505 is used to feed back the current debugging information of each security real-time bus device in each buffer address to the host computer when connected to the host computer, so as to use the current debugging information of each security real-time bus device for debugging.
[0102] Optionally, in another embodiment of the target secure real-time bus device provided in this application, the receiving unit includes:
[0103] The first receiving unit is used to receive debug information messages periodically sent by each non-target secure real-time bus device to the address of the target secure real-time bus device via Ethernet. The debug information message consists of non-target secure real-time bus data with an Ethernet header, destination address, source address, and its own current debug information. The destination address is the address of the target secure real-time bus device, and the source address is the address of the non-target secure real-time bus data.
[0104] Optionally, in another embodiment of the target secure real-time bus device provided in this application, the second buffer unit includes:
[0105] The second cache subunit is used to update the debugging information and source address in the debugging information message to the cache address in the local cache that corresponds to the source address in the debugging information message.
[0106] Optionally, in another embodiment of the target secure real-time bus device provided in this application, the feedback unit includes:
[0107] The feedback subunit is used to feed back the debugging information and source address in each buffer address as a message to the host computer when connected to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address.
[0108] Optionally, in another embodiment of the target secure real-time bus device provided in this application, the receiving unit includes:
[0109] The second receiving unit is used to receive debug information messages periodically forwarded by each non-target secure real-time bus device through the target switch. The target switch is the switch to which the target secure real-time bus devices are connected. Non-target secure real-time bus devices connected to the target switch send debug information messages directly to the target switch. Non-target secure real-time bus devices not connected to the target switch send debug information messages to the target switch through the switch they are connected to.
[0110] Optionally, in another embodiment of the target secure real-time bus device provided in this application, the device further includes:
[0111] The activation unit is used to respond to the user's target DIP switch activation operation to enable the networking function. The target DIP switches of each security real-time bus device are initially in the off state by default.
[0112] The networking unit is used to configure each security real-time bus device according to the configuration information provided by the configuration software, and to realize networking with each security real-time bus device.
[0113] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.
[0114] Another embodiment of this application provides an electronic device, such as... Figure 6 As shown, it includes:
[0115] Memory 601 and processor 602.
[0116] The memory 601 is used to store the program.
[0117] The processor 602 is used to execute the program stored in the memory 601. When the program is executed, it is specifically used to implement the debugging method of the Secure Real-Time Bus (SRB) as provided in any of the above embodiments.
[0118] Another embodiment of this application provides a computer storage medium for storing a computer program, which, when executed by a processor, is used to implement the debugging method of the Secure Real-Time Bus (SRB) as provided in any of the above embodiments.
[0119] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0120] Those skilled in the art will further 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 components and steps of the various examples have been generally described in terms of functionality 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 application.
[0121] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A debugging method for a Secure Real-Time Bus (SRB), characterized in that, include: The target security real-time bus device periodically stores its current debugging information in the local cache address corresponding to the target security real-time bus device; wherein, the target security real-time bus device can be any designated security real-time bus device; The target security real-time bus device receives debug information messages periodically sent by each non-target security real-time bus device; wherein, the non-target security real-time bus devices are all other security real-time bus devices besides the target security real-time bus device; the debug information messages sent by the non-target security real-time bus devices are generated by the non-target security real-time bus devices using their own current debug information; The target security real-time bus device extracts the current debugging information of the non-target security real-time bus device from the debugging information message; The target security real-time bus device updates the debugging information and source address in the debugging information message to the cache address in its local cache that corresponds to the source address in the debugging information message; When the target security real-time bus device is connected to the host computer, it feeds back the debugging information and source address in each of the buffer addresses as a message to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address, and to use the current debugging information of each security real-time bus device for debugging.
2. The method according to claim 1, characterized in that, The target security real-time bus device receives debugging information messages periodically sent by each non-target security real-time bus device, including: The target security real-time bus device receives debug information messages sent periodically by each non-target security real-time bus device to the address of the target security real-time bus device via Ethernet; wherein, the debug information message is composed of non-target security real-time bus data according to the Ethernet header, destination address, source address and its own current debug information; the destination address is the address of the target security real-time bus device and the source address is the address of the non-target security real-time bus data.
3. The method according to claim 1, characterized in that, The target security real-time bus device receives debugging information messages periodically sent by each non-target security real-time bus device, including: The target security real-time bus device receives debugging information messages periodically forwarded by each non-target security real-time bus device through the target switch; wherein, the target switch is the switch to which the target security real-time bus device is connected; each non-target security real-time bus device connected to the target switch directly sends debugging information messages to the target switch; each non-target security real-time bus device not connected to the target switch sends debugging information messages to the target switch through the switch it is connected to.
4. The method according to claim 1, characterized in that it further comprises: The target security real-time bus device responds to the user's target DIP switch activation operation to enable the networking function; wherein, the target DIP switch of each security real-time bus device is initially in the off state by default. The target security real-time bus device configures each security real-time bus device according to the configuration information provided by the configuration software, and realizes networking with each security real-time bus device.
5. A target security real-time bus device, characterized in that, The target secure real-time bus device is any designated secure real-time bus device, and the target secure real-time bus device includes: The first cache unit is used to periodically store its current debugging information into the cache address corresponding to the target security real-time bus device locally; A receiving unit is used to receive debug information messages periodically sent by each non-target security real-time bus device; wherein, the non-target security real-time bus device refers to the remaining security real-time bus devices; the debug information messages sent by the non-target security real-time bus devices are generated by the non-target security real-time bus devices using their own current debug information; The extraction unit is used to extract the current debugging information of the non-target secure real-time bus device from the debugging information message; The second cache unit is used to store the current debugging information of the non-target secure real-time bus device into the local cache address corresponding to the non-target secure real-time bus device; The feedback unit is used to feed back the current debugging information of each security real-time bus device in each buffer address to the host computer when connected to the host computer, so as to use the current debugging information of each security real-time bus device for debugging. The second cache unit includes: The second cache subunit is used to update the debugging information and source address in the debugging information message to the cache address in the local cache that corresponds to the source address in the debugging information message; The feedback unit includes: The feedback subunit is used to feed back the debugging information and source address in each buffer address as a message to the host computer when connected to the host computer, so as to summarize the current debugging information of each security real-time bus device according to the source address.
6. The device according to claim 5, characterized in that, The receiving unit includes: The first receiving unit is configured to receive debugging information messages periodically sent by each non-target secure real-time bus device to the address of the target secure real-time bus device via Ethernet; wherein, the debugging information message is composed of non-target secure real-time bus data according to the Ethernet header, destination address, source address and its own current debugging information; the destination address is the address of the target secure real-time bus device and the source address is the address of the non-target secure real-time bus data.
7. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor is used to execute the program, which, when executed, is specifically used to implement the debugging method of the Secure Real-Time Bus (SRB) as described in any one of claims 1 to 4.
8. A computer storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, is used to implement the debugging method of the Secure Real-Time Bus (SRB) as described in any one of claims 1 to 4.
Citation Information
Patent Citations
Node configuration method for secure real-time bus (SRB) and related device
CN118540213A