Soc-based cross-domain peripheral configuration system, method, storage medium and chip

Abstract

The application discloses a SOC-based cross-domain peripheral configuration system and method, a storage medium and a chip, and belongs to the technical field of chips. A CPU sends configuration information to a configuration unit; the configuration unit receives and stores the configuration information through a register of the configuration unit, and sends a trigger signal to a configuration update initiation unit after receiving the configuration information; the configuration update initiation unit sends a configuration update request to a configuration update receiving unit according to the trigger signal; the configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, and stores the configuration information in a register of the configuration update receiving unit; and the configuration information is obtained from a peripheral to the configuration update receiving unit. The application can reduce the required register during cross-domain processing, reduce the chip area, and prevent the configuration information from being lost from the peripheral. The configuration information from the peripheral will not change with the abnormal change of a main peripheral, thereby reducing the power consumption of the chip. The application will not cause a timing problem due to too long distance, thereby reducing the complexity of communication.

Description

TECHNICAL FIELD

[0001] The present application relates to the chip technical field, and particularly relates to a cross-domain peripheral configuration system and method based on an SOC, a storage medium and a chip. BACKGROUND

[0002] A system on chip (SOC) contains a central processing unit (CPU) and multiple domains, wherein at least one master peripheral is arranged in one domain, and multiple slave peripherals are arranged in another domain, and data communication between each master peripheral and multiple slave peripherals is usually achieved in a point-to-point (P2P) or point-to-multi-point (P2MP) hardwired manner.

[0003] As shown in FIG. 1, a master peripheral in a first domain (domain1) communicates with five slave peripherals in a second domain (domain2), and the master peripheral is provided with a configuration unit. Figure 1 When the CPU writes configuration information into multiple registers in the configuration unit through an advanced peripheral bus (APB), the configuration unit sends the written configuration information to a cross-domain (domain) processing unit corresponding to each slave peripheral in real time, and each cross-domain processing unit sends the configuration information to the corresponding peripheral after cross-domain processing.

[0004] Since the master peripheral and the slave peripheral are located in different domains, when the configuration unit writes configuration information to the cross-domain processing unit in real time, the number of registers in each cross-domain processing unit needs to be at least 2 to 3 times the number of registers in the configuration unit to perform cross-domain processing, and each slave peripheral corresponds to a cross-domain processing unit, which results in excessive chip area and power consumption. If the master peripheral is reset or powered off, the configuration information will be lost, as shown in FIG. 2. Figure 2 In addition, for a complex SOC system, the data communication between peripherals becomes complex due to factors such as power supply / clock / reset and physical distance between peripherals. SUMMARY

[0005] The present application provides a cross-domain peripheral configuration system and method based on an SOC, a storage medium and a chip, which are used to solve the problems of large chip area and power consumption, loss of configuration information of slave peripherals when the master peripheral is reset or powered off, and complex communication during cross-domain communication between peripherals.

[0006] According to a first aspect of the present application, a SOC-based cross-domain peripheral configuration system is provided, which comprises a central processing unit (CPU), a first domain and a second domain, the first domain and the second domain corresponding to different clock domains;

[0007] At least one master peripheral is arranged in the first domain, and each master peripheral is internally arranged with a configuration unit and a configuration update initiation unit;

[0008] At least one slave peripheral group is arranged in the second domain, and each slave peripheral group is internally arranged with a configuration update receiving unit and at least one slave peripheral;

[0009] The configuration unit is connected to the CPU, the configuration update initiation unit and the configuration update receiving unit respectively, and the configuration update initiation unit is connected to the CPU, the configuration unit and the configuration update receiving unit respectively;

[0010] The configuration update receiving unit is connected to each slave peripheral in the same peripheral group.

[0011] According to a second aspect of the present application, a SOC-based cross-domain peripheral configuration method is provided, which is used in the peripheral configuration system as described above, and the method comprises:

[0012] The CPU sends configuration information to the configuration unit;

[0013] The configuration unit receives and stores the configuration information through its own register, and sends a trigger signal to the configuration update initiation unit after receiving the configuration information;

[0014] The configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal;

[0015] The configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, and stores the configuration information in its own register;

[0016] Each slave peripheral acquires the configuration information from the configuration update receiving unit.

[0017] In a possible implementation, the CPU sends configuration information to the configuration unit, which comprises:

[0018] The CPU queries the configuration update initiation unit whether the last configuration update is completed;

[0019] If the last configuration update is completed, the CPU sends the configuration information to the configuration unit.

[0020] In a possible implementation, the CPU queries the configuration update initiating unit whether the last configuration update is completed, including:

[0021] The CPU queries the configuration update initiating unit whether there is an update response of the last configuration update, which is sent by the configuration update receiving unit to the configuration update initiating unit after reading the last configuration information.

[0022] If the update response exists in the configuration update initiating unit, the CPU determines that the last configuration update is completed.

[0023] In a possible implementation, the configuration information is obtained by each slave peripheral from the configuration update receiving unit, including:

[0024] When the configuration information includes multi-bit data, each slave peripheral reads data of corresponding bits from the configuration information stored in the configuration update receiving unit as its own configuration information.

[0025] In a possible implementation, the configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, including:

[0026] The configuration update receiving unit performs cross-domain processing on the configuration update request.

[0027] After the cross-domain processing is completed, the configuration update receiving unit reads the configuration information from the register of the configuration unit.

[0028] In a possible implementation, when the peripheral configuration system is powered on, the register in the configuration unit is initialized as a first default value, and the registers in the configuration update receiving unit and each slave peripheral are initialized as a second default value; the method further includes:

[0029] The configuration unit sends a trigger signal to the configuration update initiating unit.

[0030] The configuration update initiating unit sends a configuration update request to the configuration update receiving unit according to the trigger signal.

[0031] The configuration update receiving unit reads the first default value from the register of the configuration unit according to the configuration update request, and sends the first default value to each slave peripheral in the same peripheral group.

[0032] Each slave peripheral writes the first default value into its own register.

[0033] In a possible implementation, the configuration information is configuration information of a firewall.

[0034] According to a third aspect of the present application, a computer readable storage medium is provided, the storage medium storing at least one instruction, the at least one instruction being loaded and executed by a processor to implement the SOC-based cross-domain peripheral configuration method as described above.

[0035] According to a fourth aspect of the present application, a chip is provided, the chip comprising the SOC-based cross-domain peripheral configuration system as described above.

[0036] The beneficial effects of the technical solutions provided by the present application at least include:

[0037] After the configuration unit receives the configuration information, a trigger signal is sent to the configuration update initiation unit, the configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal, the configuration update receiving unit performs cross-domain processing according to the configuration update request, and reads the configuration information from the configuration unit and sends the configuration information to each slave peripheral, so that the update is initiated uniformly after the configuration information is completed, the cross-domain processing of the multi-bit configuration information is converted into the cross-domain processing of the single-bit configuration update request, the number of registers required during the cross-domain processing is greatly reduced, and the chip area is reduced; even if the master peripheral is reset or powered off, since the configuration information is stored in the configuration update receiving unit, the slave peripheral can still read the configuration information from the configuration update receiving unit, and the slave peripheral will not lose the configuration information, and the slave peripheral will not change with the abnormal change of the master peripheral, so that the power consumption of the chip can be reduced; the slave peripheral and the configuration update receiving unit are located in the same domain, so that the timing problem caused by too far physical distance is avoided, and the complexity of communication is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0039] Figure 1 is a structural schematic diagram of the SOC-based cross-domain peripheral configuration system provided by the related art;

[0040] Figure 2 is a timing diagram of the SOC-based cross-domain peripheral configuration system provided by the related art;

[0041] Figure 3 is a structural schematic diagram of the SOC-based cross-domain peripheral configuration system provided by an embodiment of the present application;

[0042] Figure 4This is a software configuration flowchart of a cross-domain peripheral configuration system based on SOC provided in one embodiment of this application;

[0043] Figure 5 This is a software configuration flowchart of a cross-domain peripheral configuration system based on SOC provided in one embodiment of this application;

[0044] Figure 6 This is a hardware configuration flowchart of a cross-domain peripheral configuration system based on a SOC provided in one embodiment of this application;

[0045] Figure 7 This is a timing diagram of a cross-domain peripheral configuration system based on SOC provided in one embodiment of this application. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0047] like Figure 3 As shown, the peripheral configuration system includes a CPU ( Figure 3 (not shown in the image), first domain (domain1) and second domain (domain2), and the first domain (domain1) and the second domain (domain2) correspond to different clock domains.

[0048] The first domain (domain1) includes at least one main peripheral device 310, and each main peripheral device 310 includes a configuration unit 311 and a configuration update initiation unit 312. The configuration unit 311 includes registers, and the number of registers is greater than or equal to the number of bits of configuration information. The configuration update initiation unit 312 includes registers, and the number of registers is greater than or equal to the number of bits of the configuration update request. In an optional embodiment, the configuration update request is a 1-bit signal.

[0049] The second domain (domain 2) is provided with at least one slave peripheral group 320, and each slave peripheral group 320 is provided with a configuration update receiving unit 321 and at least one slave peripheral 322. The configuration update receiving unit 321 is provided with a register, and the number of registers is greater than or equal to the sum of the number of registers required by the configuration information and the number of registers required by the cross-domain processing of the configuration update request. Assuming that the number of registers required by the cross-domain processing of a certain information is twice the number of bits of the information, the configuration information is 10 bits, the configuration update request is 1 bit, and the number of registers required by the cross-domain processing of the configuration update request is 1*2=2, then the number of registers in the configuration update receiving unit 321 is 10+2=12. In the related art, each slave peripheral needs to perform cross-domain processing, and the number of registers required by all cross-domain processing in the slave peripheral is 10*2*number of slave peripherals. Compared with the related art, the number of registers required by the cross-domain processing can be greatly reduced, thereby reducing the area of the chip.

[0050] The configuration unit 311 is connected with the CPU, the configuration update initiating unit 312, and the configuration update receiving unit 321 respectively, the configuration update initiating unit 312 is connected with the CPU, the configuration unit 311, and the configuration update receiving unit 321 respectively, and the configuration update receiving unit 321 is connected with each slave peripheral 322 in the same peripheral group.

[0051] As shown in Figure 4 , a method flowchart of a cross-domain peripheral configuration method based on SOC is shown, which can be applied to the peripheral configuration system shown in Figure 3 . The cross-domain peripheral configuration method based on SOC can include the following steps.

[0052] In step 401, the CPU sends configuration information to the configuration unit.

[0053] The CPU can send the configuration information to the configuration unit in the master peripheral through a bus, and the bus can be an Advanced eXtensible Interface (AXI), an Advanced High-performance Bus (AHB), an Advanced Peripheral Bus (APB), etc.

[0054] When the configuration information is a multi-bit signal, the CPU can send the configuration information to the configuration unit in multiple times.

[0055] In step 402, the configuration unit receives and stores the configuration information through the register of the configuration unit, and sends a trigger signal to the configuration update initiating unit after receiving the configuration information.

[0056] The configuration unit receives the configuration information sent by the CPU in multiple times, and stores the configuration information received in each time in a register. After receiving all the configuration information, the configuration unit sends a trigger signal to the configuration update initiation unit.

[0057] In step 403, the configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal.

[0058] After receiving the trigger signal, the configuration update initiation unit determines that the master peripheral needs to issue new configuration information to the slave peripheral, and then sends a configuration update request to the configuration update receiving unit.

[0059] In step 404, the configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, and stores the configuration information in a register of the configuration update receiving unit.

[0060] The configuration update receiving unit can perform cross-domain processing according to the configuration update request, and then read all the configuration information from the register of the configuration unit and store the configuration information in a register of the configuration update receiving unit.

[0061] In step 405, each slave peripheral acquires the configuration information from the configuration update receiving unit.

[0062] Each slave peripheral can directly read the configuration information required by the slave peripheral from the configuration update receiving unit and configure based on the configuration information, or read the configuration information required by the slave peripheral from the configuration update receiving unit, write the configuration information into a register of the slave peripheral, and then configure based on the configuration information.

[0063] In summary, the SOC-based cross-domain peripheral configuration method provided by the embodiments of the present application sends a trigger signal to the configuration update initiation unit after the configuration unit receives the configuration information, the configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal, the configuration update receiving unit performs cross-domain processing according to the configuration update request and reads the configuration information from the configuration unit, and sends the configuration information to each slave peripheral, so that the update is initiated uniformly after the configuration information is completed, the cross-domain processing of multi-bit configuration information is converted into the cross-domain processing of single-bit configuration update request, the number of registers required for cross-domain processing is greatly reduced, and the chip area is reduced. Even if the master peripheral is reset or powered off, since the configuration information is stored in the configuration update receiving unit, the slave peripheral can still read the configuration information from the configuration update receiving unit, so that the slave peripheral does not lose the configuration information, and the slave peripheral does not change with the abnormal change of the master peripheral, so that the power consumption of the chip can be reduced. The slave peripheral and the configuration update receiving unit are located in the same domain, so that the timing problem caused by too far physical distance is avoided, and the complexity of communication is reduced.

[0064] As shown in Figure 5 Fig. 1 is a flowchart illustrating a method for configuring a cross-domain peripheral based on an SOC according to an embodiment of the present application. The method can be applied to a peripheral configuration system as shown in Figure 3 Fig. 2. The method for configuring a cross-domain peripheral based on an SOC can include the following steps.

[0065] In step 501, the CPU queries the configuration update initiating unit whether the last configuration update is completed.

[0066] In this embodiment, the configuration information is stored in the configuration unit and waits to be read by the configuration update receiving unit. If the CPU issues new configuration information to the configuration unit again when the configuration update receiving unit has not read the last configuration information, i.e., the last configuration update is not completed, the new configuration information will overwrite the last configuration information, resulting in an error in the last configuration update. In order to avoid this problem, the CPU needs to query whether the last configuration update is completed before issuing the configuration information.

[0067] Specifically, the CPU queries the configuration update initiating unit whether the last configuration update is completed, including: the CPU queries the configuration update initiating unit whether there is an update acknowledgement of the last configuration update, the update acknowledgement being sent by the configuration update receiving unit to the configuration update initiating unit after reading the last configuration information; if there is the update acknowledgement in the configuration update initiating unit, the CPU determines that the last configuration update is completed.

[0068] The configuration update initiating unit sends a configuration update request (request) to the configuration update receiving unit to notify the configuration update receiving unit to read the configuration information from the configuration unit every time the configuration update is performed. After reading all the configuration information, the configuration update receiving unit sends an update acknowledgement (ack) to the configuration update initiating unit to indicate that the configuration update is completed.

[0069] That is, the configuration update initiating unit receives an update acknowledgement after each configuration update. The CPU can determine whether the last configuration update is completed according to whether there is an update acknowledgement of the last configuration update in the configuration update initiating unit. If there is the update acknowledgement of the last configuration update in the configuration update initiating unit, it means that the last configuration update is completed, and step 502 is performed. If there is no update acknowledgement of the last configuration update in the configuration update initiating unit, it means that the last configuration update is not completed, and the CPU needs to query the configuration update initiating unit again after a period of time. This process can be referred to as flow control of the configuration update.

[0070] In step 502, if the last configuration update is completed, the CPU sends the configuration information to the configuration unit.

[0071] When the application is applied to the master peripheral device configuring the firewall for the plurality of slave peripheral devices, the configuration information is the configuration information of the firewall.

[0072] The CPU can send the configuration information to the configuration unit in the master peripheral device through a bus, and the bus can be AXI, AHB, APB, etc.

[0073] When the configuration information is a multi-bit signal, the CPU can send the configuration information to the configuration unit in multiple times.

[0074] In step 503, the configuration unit receives and stores the configuration information through its own register, and sends a trigger signal to the configuration update initiating unit after receiving the configuration information.

[0075] The configuration unit receives the configuration information sent by the CPU in multiple times, and stores the configuration information received each time in the register. After receiving all the configuration information, the configuration unit sends a trigger signal to the configuration update initiating unit.

[0076] In step 504, the configuration update initiating unit sends a configuration update request to the configuration update receiving unit according to the trigger signal.

[0077] After receiving the trigger signal, the configuration update initiating unit determines that the master peripheral device needs to issue new configuration information to the slave peripheral device, and then sends a configuration update request to the configuration update receiving unit.

[0078] In step 505, the configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, and stores the configuration information in its own register.

[0079] Specifically, the configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, including: the configuration update receiving unit performs cross-domain processing on the configuration update request; after completing the cross-domain processing, the configuration update receiving unit reads the configuration information from the register of the configuration unit.

[0080] The configuration update receiving unit can perform cross-domain processing according to the configuration update request, and then read all the configuration information from the register of the configuration unit and store the configuration information in its own register.

[0081] In step 506, each slave peripheral device obtains the configuration information from the configuration update receiving unit.

[0082] Specifically, each slave peripheral device obtains the configuration information from the configuration update receiving unit, including: when the configuration information includes multi-bit data, each slave peripheral device reads the data corresponding to the bit from the configuration information stored in the configuration update receiving unit as its own configuration information.

[0083] Each slave peripheral can directly read the configuration information required by itself from the configuration update receiving unit and configure based on the configuration information; or read the configuration information required by itself from the configuration update receiving unit, write the configuration information into the register of itself, and then configure based on the configuration information.

[0084] To sum up, the SOC-based cross-domain peripheral configuration method provided by the embodiments of the present application sends a trigger signal to the configuration update initiating unit after the configuration unit receives the configuration information, the configuration update initiating unit sends a configuration update request to the configuration update receiving unit according to the trigger signal, the configuration update receiving unit performs cross-domain processing according to the configuration update request and reads the configuration information from the configuration unit, and sends the configuration information to each slave peripheral, so that the update is initiated uniformly after the configuration information is completed, the cross-domain processing of multi-bit configuration information is converted into the cross-domain processing of single-bit configuration update requests, the number of registers required for cross-domain processing is greatly reduced, and the chip area is reduced. Even if the master peripheral is reset or powered off, since the configuration information is stored in the configuration update receiving unit, the slave peripheral can still read the configuration information from the configuration update receiving unit, so that the slave peripheral does not lose the configuration information, and the slave peripheral does not change with the abnormal change of the master peripheral, so that the power consumption of the chip is reduced. The slave peripheral and the configuration update receiving unit are located in the same domain, so that there is no timing problem due to too far physical distance, and the complexity of communication is reduced.

[0085] In addition to the above-mentioned software configuration method, the peripheral configuration system can also be configured in hardware. The hardware configuration means that when the peripheral configuration system is powered on, the registers in the configuration unit are initialized to the first default value, and the registers in the configuration update receiving unit and each slave peripheral are initialized to the second default value, and the second default value needs to be updated to the first default value. As shown in Figure 6 The specific configuration process is as follows:

[0086] Step 601, the configuration unit sends a trigger signal to the configuration update initiating unit.

[0087] After the registers in the configuration unit are initialized, the configuration unit sends a trigger signal (trigger) to the configuration update initiating unit.

[0088] Step 602, the configuration update initiating unit sends a configuration update request to the configuration update receiving unit according to the trigger signal.

[0089] After receiving the trigger signal, the configuration update initiating unit determines that the master peripheral needs to issue new configuration information to the slave peripheral, and then sends a configuration update request to the configuration update receiving unit. At this time, the configuration information is the first default value.

[0090] In step 603, the configuration update receiving unit reads the first default value from the register of the configuration unit according to the configuration update request, and sends the first default value to each slave peripheral in the same peripheral group.

[0091] The configuration update receiving unit can perform cross-domain processing according to the configuration update request, and then read the first default value from the register of the configuration unit and send the first default value to each slave peripheral in the same peripheral group.

[0092] In step 604, each slave peripheral writes the first default value into the register of itself.

[0093] Each slave peripheral replaces the second default value in the register with the first default value.

[0094] As shown in Figure 7 , the register in the configuration unit of the master peripheral is configured as a default value after power-on, and the registers in the slave peripherals are also configured as the default value through hardware configuration update. Then, the configuration unit receives configuration information A / B / C, and after receiving all the configuration information A / B / C, the configuration update initiating unit in the master peripheral sends an update request; after the configuration update receiving unit in the slave peripheral receives the update request, it responds to the update request to perform cross-domain processing, and then reads the configuration information A / B / C from the configuration unit, and the slave peripheral obtains the configuration information A / B / C from the configuration update receiving unit. If the register in the master peripheral is restored to the default value due to reset or power-off, the configuration information in the slave peripheral remains unchanged.

[0095] As shown in Figure 3 , a structure block diagram of a cross-domain peripheral configuration system based on SOC is shown, which can be applied in the SOC, and the peripheral configuration system includes a CPU, a first domain and a second domain, the first domain and the second domain correspond to different clock domains;

[0096] At least one master peripheral 310 is arranged in the first domain, and each master peripheral 310 is arranged with a configuration unit 311 and a configuration update initiating unit 312;

[0097] At least one slave peripheral group 320 is arranged in the second domain, and each slave peripheral group 320 is arranged with a configuration update receiving unit 321 and at least one slave peripheral 322;

[0098] The configuration unit 311 is connected with the CPU, the configuration update initiating unit 312 and the configuration update receiving unit 321 respectively, the configuration update initiating unit 312 is connected with the CPU, the configuration unit 311 and the configuration update receiving unit 321 respectively;

[0099] The configuration update receiving unit 321 is connected with each slave peripheral 322 in the same peripheral group.

[0100] In an optional embodiment, the CPU is further configured to send the configuration information to the configuration unit 311.

[0101] The configuration unit 311 is configured to receive and store the configuration information through its own register, and send a trigger signal to the configuration update initiating unit 312 after receiving the configuration information.

[0102] The configuration update initiating unit 312 is configured to send a configuration update request to the configuration update receiving unit 321 according to the trigger signal.

[0103] The configuration update receiving unit 321 is configured to read the configuration information from the register of the configuration unit 311 according to the configuration update request, and store the configuration information in its own register.

[0104] Each slave peripheral 322 is configured to obtain the configuration information from the configuration update receiving unit 321.

[0105] In an optional embodiment, the CPU is further configured to:

[0106] query the configuration update initiating unit 312 whether the last configuration update is completed.

[0107] If the last configuration update is completed, send the configuration information to the configuration unit 311.

[0108] In an optional embodiment, the CPU is further configured to:

[0109] query the configuration update initiating unit 312 whether there is an update response of the last configuration update, wherein the update response is sent by the configuration update receiving unit 321 to the configuration update initiating unit 312 after reading the last configuration information.

[0110] If the update response exists in the configuration update initiating unit 312, it is determined that the last configuration update is completed.

[0111] In an optional embodiment, when the configuration information includes multi-bit data, each slave peripheral 322 is further configured to read the data of corresponding bits from the configuration information stored by the configuration update receiving unit 321 as its own configuration information.

[0112] In an optional embodiment, the configuration update receiving unit 321 is further configured to:

[0113] perform cross-domain processing on the configuration update request.

[0114] read the configuration information from the register of the configuration unit 311 after completing the cross-domain processing.

[0115] In an optional embodiment, when the peripheral configuration system is powered on, the register in the configuration unit 311 is initialized to a first default value, and the register in the configuration update receiving unit 321 and each slave peripheral 322 is initialized to a second default value;

[0116] The configuration unit 311 is further configured to send a trigger signal to the configuration update initiating unit 312;

[0117] The configuration update initiating unit 312 is further configured to send a configuration update request to the configuration update receiving unit 321 according to the trigger signal;

[0118] The configuration update receiving unit 321 is further configured to read the first default value from the register of the configuration unit 311 according to the configuration update request, and send the first default value to each slave peripheral 322 in the same peripheral group;

[0119] Each slave peripheral 322 is further configured to write the first default value into the register thereof.

[0120] In an optional embodiment, the configuration information is configuration information of a firewall.

[0121] In summary, the SOC-based cross-domain peripheral configuration system provided by the embodiments of the present application sends a trigger signal to the configuration update initiating unit after the configuration unit receives the configuration information, the configuration update initiating unit sends a configuration update request to the configuration update receiving unit according to the trigger signal, the configuration update receiving unit performs cross-domain processing according to the configuration update request, and reads the configuration information from the configuration unit and sends the configuration information to each slave peripheral, so that the update is initiated uniformly after the configuration information is completed, the cross-domain processing of multi-bit configuration information is converted into the cross-domain processing of single-bit configuration update request, the number of registers required for cross-domain processing is greatly reduced, and the chip area is reduced. Even if the master peripheral is reset or powered off, since the configuration information is stored in the configuration update receiving unit, the slave peripheral can still read the configuration information from the configuration update receiving unit, so that the slave peripheral does not lose the configuration information, and the slave peripheral does not change with the abnormal change of the master peripheral, so that the power consumption of the chip can be reduced. The slave peripheral and the configuration update receiving unit are located in the same domain, so that the timing problem caused by too far physical distance does not occur, and the complexity of communication is reduced.

[0122] An embodiment of the present application provides a computer readable storage medium, the storage medium stores at least one instruction, the at least one instruction is loaded and executed by a processor to implement the SOC-based cross-domain peripheral configuration method as described above.

[0123] An embodiment of the present application provides a chip, the chip comprises any SOC-based cross-domain peripheral configuration system described above.

[0124] It should be noted that the SOC-based cross-domain peripheral configuration system provided by the above-mentioned embodiments, when performing SOC-based cross-domain peripheral configuration, only divides the above-mentioned functional modules for example, and in actual application, the above-mentioned functions can be completed by different functional modules according to needs, that is, the internal structure of the SOC-based cross-domain peripheral configuration system is divided into different functional modules to complete all or part of the functions described above. In addition, the SOC-based cross-domain peripheral configuration system and the SOC-based cross-domain peripheral configuration method embodiments provided by the above-mentioned embodiments belong to the same concept, and the specific implementation process is described in the method embodiments, which will not be repeated here.

[0125] Those of ordinary skill in the art can understand that all or part of the steps of the above-mentioned embodiments can be completed by hardware, or by programs instructing relevant hardware to complete, and the programs can be stored in a computer readable storage medium. The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0126] The above description does not limit the embodiments of the present application. Any adjustment, equivalent replacement, improvement, etc. made within the spirit and principles of the embodiments of the present application shall be included in the protection scope of the embodiments of the present application.

Claims

1. A SOC-based cross-domain peripheral configuration method, characterized in that, The application relates to a cross-domain peripheral configuration system, which comprises a central processing unit (CPU), a first domain and a second domain, wherein the first domain and the second domain correspond to different clock domains; at least one master peripheral is arranged in the first domain, each master peripheral is internally provided with a configuration unit and a configuration update initiation unit; at least one slave peripheral group is arranged in the second domain, each slave peripheral group is internally provided with a configuration update receiving unit and at least one slave peripheral; the configuration unit is connected with the CPU, the configuration update initiation unit and the configuration update receiving unit; the configuration update initiation unit is connected with the CPU, the configuration unit and the configuration update receiving unit; the configuration update receiving unit is connected with each slave peripheral in the same peripheral group; the method comprises the following steps: The CPU sends configuration information to the configuration unit; The configuration unit receives and stores the configuration information through a register of the configuration unit, and sends a trigger signal to the configuration update initiation unit after receiving the configuration information; The configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal; The configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, and stores the configuration information in a register of the configuration update receiving unit; Each slave peripheral obtains the configuration information from the configuration update receiving unit. The CPU sends configuration information to the configuration unit, which comprises the following steps:

2. The SOC-based cross-domain peripheral configuration method according to claim 1, characterized in that, The CPU queries the configuration update initiation unit to check whether the last configuration update is completed; If the last configuration update is completed, the CPU sends the configuration information to the configuration unit. The CPU queries the configuration update initiation unit to check whether the last configuration update is completed, which comprises the following steps:

3. The SOC-based cross-domain peripheral configuration method according to claim 2, characterized in that, The CPU queries the configuration update initiation unit to check whether there is an update response of the last configuration update, wherein the update response is sent by the configuration update receiving unit after reading the last configuration information; If the update response exists in the configuration update initiation unit, the CPU determines that the last configuration update is completed. Each slave peripheral obtains the configuration information from the configuration update receiving unit, which comprises the following steps:

4. The SOC-based cross-domain peripheral configuration method according to claim 1, characterized in that, When the configuration information comprises multi-bit data, each slave peripheral reads the data of corresponding bits from the configuration information stored in the configuration update receiving unit as the configuration information of the slave peripheral. The configuration update receiving unit reads the configuration information from the register of the configuration unit according to the configuration update request, which comprises the following steps:

5. The SOC-based cross-domain peripheral configuration method according to claim 1, characterized in that, The configuration update receiving unit performs cross-domain processing on the configuration update request; After the cross-domain processing is completed, the configuration update receiving unit reads the configuration information from the register of the configuration unit. When the cross-domain peripheral configuration system is powered on, the register in the configuration unit is initialized as a first default value, and the registers in the configuration update receiving unit and each slave peripheral are initialized as a second default value; the method further comprises the following steps:

6. The SOC-based cross-domain peripheral configuration method according to claim 1, characterized in that, The configuration unit sends a trigger signal to the configuration update initiation unit; ​ The configuration update initiation unit sends a configuration update request to the configuration update receiving unit according to the trigger signal; The configuration update receiving unit reads the first default value from the register of the configuration unit according to the configuration update request, and sends the first default value to each slave peripheral in the same peripheral group; Each slave peripheral writes the first default value into its own register.

7. The SOC-based cross-domain peripheral configuration method according to any one of claims 1 to 6, characterized in that, The configuration information is configuration information of a firewall.

8. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is loaded and executed by the processor to implement the SOC-based cross-domain peripheral configuration method in any one of claims 1 to 7.

9. A chip, characterized by The chip is used to implement the SOC-based cross-domain peripheral configuration method in any one of claims 1 to 7.

Images