Method and device for managing chip resource access authority and electronic equipment

Abstract

The invention provides a method and a device for managing chip resource access authority, and electronic equipment. The method comprises the following steps: dividing resources needing authority management into a master device module only initiating a request, a slave device module only receiving the request and a system memory; respectively distributing the at least one master device module to a corresponding master device group in the at least one master device group, respectively distributing the at least one slave device module to a corresponding slave device group in the at least one slave device group, and dividing a corresponding storage space from the system memory according to the storage area; and configuring the corresponding access authority of the at least one master device group to the at least one slave device group or the corresponding access authority of the at least one master device group to the at least one storage area. According to the method, the flow of permission configuration is simplified by realizing batch setting, the master device group, the slave device group and the memory block are mutually independent and can be randomly associated to realize permission configuration, and the configuration process is simple.

Description

Technical Field

[0001] The present invention relates to the field of chip design, and in particular to a method and device for managing chip resource access rights, and an electronic device. Background Art

[0002] To accommodate complex use cases, existing products often require multiple systems to be integrated onto a single chip. For example, in a car, the instrument cluster uses a different system than the multimedia device. To ensure the security and independence of each system, complex access rights management solutions are required to isolate system-related resources. Summary of the Invention

[0003] The present invention provides a method and device for managing chip resource access rights, and an electronic device, providing a more convenient access rights configuration mode for chip resource access.

[0004] In one aspect of the present invention, a method for managing chip resource access permissions is provided. The method includes the steps of: dividing resources requiring permission management into master device modules that only initiate requests, slave device modules that only receive requests, and system memory; assigning at least one of the master device modules to a corresponding master device group in at least one master device group, assigning at least one of the slave device modules to a corresponding slave device group in at least one slave device group, and dividing corresponding storage space from the system memory based on storage areas; and configuring corresponding access permissions for at least one of the master device groups to at least one of the slave device groups or for at least one of the storage areas.

[0005] In another aspect of the present invention, a device for managing chip resource access permissions is provided. The device comprises: at least one master device group, each including at least one master device module assigned thereto, the master device module being a resource that only initiates requests; at least one slave device group, each including at least one slave device module assigned thereto, the slave device module being a resource that only receives requests; and at least one storage area, each including at least one storage space partitioned from system memory, wherein at least one of the master device groups is configured with corresponding access permissions for at least one of the slave device groups or for at least one of the storage areas.

[0006] In yet another aspect of the present invention, an electronic device is provided, including a memory configured to store information associated with access rights; and at least one processor electrically coupled to the memory and configured to execute the above method.

[0007] According to the technical solution of the present invention, the resources in the chip that need to be managed for permissions are classified according to the initiation of requests and the reception of requests. The resources that only initiate requests are recorded as master device modules, and the resources that only receive requests are recorded as slave device modules. By grouping the master device modules and the slave device modules into master device groups and slave device groups respectively, the access permissions between the groups are configured to achieve batch configuration of access permissions; and the access to different storage areas of the system memory is isolated by performing access control on the system memory according to the storage area; in the process of configuring chip access permissions, there is no need to set individual resources separately, and batch setting is achieved, which simplifies the process of permission configuration; and the master device group, slave device group and memory block are all independent of each other, and can be arbitrarily associated to achieve permission configuration, and the configuration process is simple. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a flowchart of a method for managing chip resource access permissions according to an embodiment of the present invention; Figure 2 is another flow chart of a method for managing chip resource access permissions according to an embodiment of the present invention; Figure 3 This is a schematic diagram of permission configuration results according to an embodiment of the present invention; Figure 4 A schematic structural diagram of a device for managing chip resource access rights according to an embodiment of the present invention; Figure 5 Schematic diagram of the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0009] To illustrate the technical content, achieved objectives and effects of the present invention in detail, the following description is given in conjunction with the embodiments and accompanying drawings.

[0010] In existing technologies, on chips that need to run multiple systems, isolating resources in the chip usually requires a complex permission configuration process. For example, access rights between two resources are separately configured as needed, which is not convenient for subsequent permission modification and management.

[0011] In order to solve at least the above-mentioned technical problems, the present disclosure provides a method for managing chip resource access rights. According to the present disclosure, the resources in the chip that require access control are divided into a master device module that only initiates requests and a slave device module and system memory that only receives requests, and are divided into different groups according to the requirements of the permission configuration, and the system memory is divided into memory areas, and access rights are configured for the groups and memory areas. In this way, according to the embodiments of the present disclosure, batch configuration of access rights to resources in the chip can be achieved, and there is no association relationship between each group and memory area, and the permissions between the two can be arbitrarily configured, which is more flexible.

[0012] Hereinafter, the technical solutions according to the present disclosure will be described with reference to specific embodiments and in conjunction with the accompanying drawings.

[0013] Figure 1 FIG. 1 is a flow chart illustrating a method 100 for managing chip resource access rights according to an embodiment of the present disclosure. Figure 1 , the method 100 includes the following steps 102 to 106.

[0014] In step 102, the resources requiring permission management are divided into a master module (which only initiates requests), a slave module (which only receives requests), and system memory. The access requests issued by the master module can be of two types: secure and non-secure.

[0015] In some embodiments, the distinction between master and slave modules is determined by device functionality and is fixed and non-configurable. Taking a DMA (Direct Memory Access) device as an example, its basic functionality is to accept CPU register configuration requests and then move data from memory. The DMA slave module (with its own slave ID) receives CPU register configuration requests, while the DMA master module (with its own master ID) reads and writes memory (initiates read and write requests to memory). Therefore, the DMA module consists of both master and slave modules, and there are many such devices in the system. The master module can be understood as the accessor, while the slave module is the accessee. A large module can be both accessor and accessee, but a module assigned an ID only has the ability to initiate or receive requests, facilitating hardware-level permission configuration.

[0016] In step 104, at least one of the master device modules is assigned to a corresponding master device group (master-group) in at least one master device group, at least one of the slave device modules is assigned to a corresponding slave device group (slave-group) in at least one slave device group, and corresponding storage space is divided from the system memory according to a memory region. Multiple master device groups and slave device groups are predefined in this application, and master device modules and slave device modules can be assigned to at least one of the predefined master device groups or slave device groups.

[0017] In some embodiments, at least one of the master device modules is assigned to a corresponding master device group in at least one of the master device groups based on the access type. In addition, at least one of the slave device modules is assigned to a corresponding slave device group in at least one of the slave device groups based on the access type. In this way, if the access type of the master device module or the slave device module is known, the master device module and the slave device module are directly assigned to the master device group and the slave device group based on the access type. The probability of the master device modules of the same access type or the slave device modules of the same access type having the same access rights is high, which can reduce the number of adjustments to the master device group or the slave device group.

[0018] In some embodiments, the master device group includes a master device group identifier, and the master device module includes a master module identifier. Furthermore, the slave device group includes a slave device group identifier, and the slave device module includes a slave device identifier. In this way, the master device group, the master device modules within the master device group, the slave device group, and the slave device modules within the slave device group are all uniquely identified by identifiers, making it easier to locate the module initiating access and the module to be accessed when a request is made, and to search for access permissions. Furthermore, no additional storage space is allocated for system memory that does not require permission management, thereby saving the storage required for permission configuration and avoiding redundant permission confirmation processes.

[0019] In some embodiments, a master device module can only correspond to one master device group, and a slave device module can only correspond to one slave device group. In this way, the problem of repeated permission definition or permission definition conflict is avoided.

[0020] In some embodiments, dividing the corresponding storage space from the system memory according to the storage region includes configuring a block number and an address range for the storage space. In this manner, by defining the storage region using an address range in conjunction with a block number, the address range can be directly adjusted to adjust the size of the storage region according to different requirements, thereby facilitating the adjustment of the size of the storage region corresponding to different access permissions in the memory according to requirements, and providing flexible configuration.

[0021] In some embodiments, assigning at least one of the master device modules to the corresponding master device group in at least one master device group includes: using the master device identifier of the master device module as an index, associating the master device identifier with the master device group identifier of the master device group on a register. Assigning at least one of the slave device modules to the corresponding slave device group in at least one slave device group includes: using the slave device identifier of the slave device module as an index, associating the slave device identifier with the slave device group identifier of the slave device group on the register. In addition, dividing the corresponding storage space from the system memory according to the storage area includes: using the block number of the storage space as an index, saving the association relationship between the block number and the address range on the register. In this way, the master device identifier is associated with the master device group identifier as an index, the slave device identifier is associated with the slave device group identifier as an index, and the block number of the storage space is associated with the address range as an index, and the association relationship is stored on the register, thereby realizing the association relationship between the master device module and the master device group to which it belongs, the slave device module and the slave device group to which it belongs, and the address range and block number that need to be subject to permission control divided from the system memory, realizing grouping and convenient search in an indexed manner.

[0022] In some embodiments, the access permissions are stored in a pre-set resource module, which is a slave device module, and the write permission for the resource module is disabled. In this manner, a resource management module is further configured, providing multiple registers for software configuration, thereby enabling modification of the grouping and permissions of each master and slave, thereby enabling permission management through a combination of hardware and software. Once configured, the resource management module begins managing resources based on the configuration of these registers.

[0023] Next, in step 106, corresponding access rights for at least one of the master device groups to at least one of the slave device groups or corresponding access rights for at least one of the storage areas are configured. In an optional embodiment, the master device groups and access objects are associated, and access rights for the access objects under different access types are configured. In this way, access rights for corresponding access objects of master device groups can be individually configured. Master device groups can be configured for different access objects separately, providing high flexibility and enabling batch configuration for master device modules within the master device group.

[0024] In some embodiments, the access type includes secure access and non-secure access, and the access rights include both secure access and non-secure access, neither secure access nor non-secure access, secure access is permitted but non-secure access is not, and secure access is not permitted but non-secure access is permitted. In this way, access rights are controlled by combining the access type of secure / non-secure with whether access is permitted. By associating and storing the access rights with the master device group and the access object, the master device group's access rights to the access object can be limited. This requires few configuration items, is simple to configure, and can be configured in batches.

[0025] In some embodiments, the access permissions are stored in a pre-set resource module, which is a slave device module, and the write permission of the resource module is disabled. In this way, the access permission configuration of the slave device module with disabled write permission cannot be further modified, thereby protecting the security of the access permissions and preventing tampering. If the access permission configuration needs to be modified again, the chip needs to be restarted for verification.

[0026] In some embodiments, each master device group is configured with access rights to each slave device group, and each master device group is configured with access rights to each memory block. In this way, permissions are configured in an exhaustive manner, preventing a master device module from encountering a situation where there are no configured permissions to determine when accessing a slave device module or a memory block, thereby ensuring that the configured access rights are followed between the master device module and the accessed object.

[0027] In some embodiments, the method may further include the following steps 1062 to 1068 .

[0028] In step 1062, an access request is received from the master device module. The access request includes an access type, a master module identifier of the master device module, and an access target, where the access target is the slave device module or the storage space. In an optional embodiment, when the access target is the storage space, the access target includes a block number of the storage space. In this way, the address range of the storage space can be located by the block number, thereby achieving access to the desired storage space.

[0029] When the access object is the slave device module, the access object includes the slave device identification of the slave device module. In this way, the address of the slave device module can be located by the slave device identification to achieve access to the slave device module, and the slave device group corresponding to the slave device module can be retrieved according to the slave device identification.

[0030] The address format can be directly accessed by the hardware after determining whether the access request can be executed, without the need for conversion at the software layer.

[0031] In some embodiments, when the access object is the slave device module, the access object includes the slave device identifier of the slave device module. In this way, the access object can be quickly located according to the slave device identifier, and the recipient of the access request can be clearly identified.

[0032] In some embodiments, when the access object is the slave device module, the access object includes the slave device address of the slave device module. In this way, the address is directly used when sending the access request. Access can be achieved directly based on the address at the hardware layer without the need for further conversion.

[0033] In step 1064, the master device group identifier of the master device group where the master device module is located is searched based on the master module identifier.

[0034] In step 1066, the access permission is searched based on the master device group identifier and the access object. In an optional embodiment, when the access object is a memory space, the access permission is searched based on the master device group identifier and the block number. In this way, before accessing a memory block, the corresponding access permission is searched based on the access object identifier (block number) in the access request and the master device identifier of the access request initiator, thereby implementing permission control when the master device module accesses the memory address.

[0035] In some embodiments, when the access object is the slave device module, the slave device group identifier of the slave device group to which the slave device module belongs is searched based on the slave device identifier; and the access permission is searched based on the master device group identifier and the slave device group identifier. In this way, when the master device module accesses the slave device module, the access permission is determined by matching the identifiers of the device groups corresponding to the master and slave devices, thereby achieving access permission control when the master device module accesses the slave device module. Accordingly, when configuring access permissions, there is no need to configure each individual master device or slave device; instead, batch configuration can be performed on the master device group or slave device group.

[0036] In some embodiments, the access object includes a slave device address of a slave device module, and before step 1066, the method may further include matching a slave device identifier based on the slave device address. In this manner, when the access request contains a slave device address, the slave device address is converted to the slave device identifier of the slave device module corresponding to the address before access permission is retrieved. The access request can be directly located to the slave device module based on the slave device address, thereby ensuring access efficiency at the hardware layer while achieving access permission control at the software layer.

[0037] In step 1068, a determination is made as to whether access is permitted based on the relationship between the access permission and the access type. In this manner, the access request is configured to include the access type, the master module identifier of the master device module, and the access object (which can be either a slave device module or a memory block). The master module identifier is then used to retrieve the master device group identifier of the master device group to which it belongs. The configured access permission is then retrieved based on the master device group identifier and the access object to determine whether access is permitted, thereby achieving permission control over the access request.

[0038] In summary, this solution implements permission control by setting up a configuration that can be directly embedded in chip hardware logic and applied to physical grouping and circuit design (registers). Furthermore, the master device module's access to the slave device module, as well as the master device module's access to system memory, is sent via addresses when sending access requests, facilitating direct hardware access. By adding a process for converting slave addresses into identifiers, software can directly configure access permissions using identifiers (device ID and the ID of the group to which the device belongs) as indexes. Furthermore, when multiple access requests are made in parallel, each can obtain access permissions through the identifier ID to determine whether access is permitted, achieving multi-process parallelism without the need for table lookups and achieving high performance.

[0039] Figure 2 FIG. 1 is another flow chart illustrating a method for managing chip resource access rights according to an embodiment of the present invention. Figure 2 As shown, the method includes the following steps 201 to 204.

[0040] In step 201, resources requiring permission management are divided into three categories: master, slave, and memory. Master: The master device module only initiates requests and can issue both secure and non-secure access requests. Slave: The slave device module only receives requests. Memory: System memory.

[0041] In step 202, several master device groups master-group, slave device groups slave-group and memory blocks memory-region are set.

[0042] In step 203, the master device module (master) is independently assigned to a master-group; the slave device modules are independently assigned to a slave-group; and the memory space is divided into memory-regions based on the physical address range. During the division process, master device modules, slave device modules, and physical addresses in the system memory with consistent permissions can be grouped together based on the permissions configured as needed, and then the corresponding groups are created after the number of groups is determined. Alternatively, a certain number of groups can be created and then, as needed, the groups can be bound to the master device modules, slave device modules, or physical addresses in the system memory. This is not limited in this solution, as long as the final binding of groups to device modules or the binding of address ranges in the system memory to memory blocks in this solution can be achieved.

[0043] In some embodiments, a master device identifier master-id is assigned to the master device module master; a master device group identifier master-group-id is assigned to each master device group; a slave device identifier slave-id is assigned to each slave device module slave, a slave device group identifier slave-group-id is assigned to each slave device group, and a memory block memory region is assigned a block number region-id; the master device module and its corresponding master device group are bound by associating the master device group identifier and the master device identifier, and the slave device module and its corresponding slave device group are bound by associating the slave device group identifier and the slave device identifier.

[0044] Figure 3 Schematic diagram showing the result of authority configuration according to an embodiment of the present invention. Figure 3 As shown, in step 204, each master device group master-group is configured with access rights to each slave device group slave-group and each master device group master-group is configured with access rights to each memory region. The access types of the access requests sent by the master device group include secure and non-secure access. Therefore, when configuring access rights, the following options are available: secure access and non-secure access are both possible; secure access and non-secure access are not possible; secure access is possible but non-secure access is not possible; and secure access is not possible but non-secure access is possible. Figure 3 The xx in the xx represents one of the four access rights mentioned above. The access rights can be saved with a preset number of bits, so as to achieve persistent access rights in the hardware and facilitate the hardware to directly read the access rights. Figure 3As shown, access rights are stored using two bits. The first bit indicates the access type (e.g., 0 for unsafe and 1 for safe). The second bit indicates whether access is allowed (e.g., 0 for denied and 1 for allowed). This two-bit approach allows access rights to be stored, saving storage space and facilitating direct hardware processing of access rights. Multiple bits can be configured to represent access rights based on hardware storage space to improve fault tolerance. The data presented in this solution is only an example and is not intended to limit the number of bits.

[0045] For example, if you need to set master-A's access rights to slave-A as secure access, but not non-secure access, you can assign master-A to master-group0, then assign slave-A to slave-group0, and finally configure master-group0's access rights to slave-group0 as secure access, but not non-secure access. Alternatively, if master-group0 already has access rights to slave-group0 as secure access, but not non-secure access, you can directly assign master-A to master-group0 and slave-A to slave-group0. For another example, if you need to set master-A's access rights to memory addresses a0 to a1 as secure access, but not non-secure access, you can first assign master-A to master-group0, then bind the address range a0-a1 to memory region0, and finally configure master-group0's access rights to memoryregion0 as secure access, but not non-secure access. The system memory is segmented by binding the address range (physical address) to the block number. This is convenient and easy to use. The first address and the last address can be directly stored, or the address range can be stored by combining the first address with the address length (size). There is no limitation here.

[0046] In some embodiments, during the process of permission configuration, access rights are set through the association between the master device group identifier master-group-id, the slave device group identifier slave-group-id and the block number region-id, which makes it easier for operators to understand the access permission configuration object and the storage of the upper-level software.

[0047] In some embodiments, all access requests in the chip system, including those for code and data, must undergo permission arbitration by the resource management module before execution. The access permission configuration process described above is implemented in the resource management module, and the resource management module is managed as a slave device module. In the default state after the chip is reset, the resource management module is assigned to a default slave-group A0. The master (master device module) that is allowed to modify the resource management module, such as the main CPU, is assigned to a default master-group B0. This slave-group A only allows secure access from master-group B0 and not from other master-groups. Because a security authentication process is typically configured during the use of the master device module, limiting access to a single master device group limits the scope of modifiable resource management modules, thereby protecting the security of the permission configuration. Simultaneously, the master in master-group B0 can modify the resource management module configuration based on actual needs. It is also possible to add or remove certain masters from master-group B0, thereby adding or removing masters that can modify the resource management module. After configuring the resource management module, if the system no longer allows subsequent modifications to the resource management module's configuration, you can disable the module's configuration by setting the write lock bit in the resource management module to 1. The write lock bit is designed to be irreversible once set to 1, preventing further modifications to the resource management module unless the chip is reset.

[0048] The following uses an access request from the master device module master to the slave device module slave as an example. After step 204, the following steps are also included: 1) receiving the access request and indexing the master-group-id through the master-id in the access request; 2) converting the address of the access object into the slave-id, and then indexing the slave-group-id through the slave-id; 3) querying the master-group's access rights to the slave-group based on the master-group-id and slave-group-id; and then combining the master's security attributes to determine whether the master has access rights to the slave.

[0049] If the master accesses the memory, the block number region-id can be directly indexed based on the memory address only in step 2).

[0050] In the resource management module, permission arbitration processes can be executed in parallel. For example, the "master-ID indexing master-group-ID" and "access address conversion to slave-ID, and slave-ID indexing to slave-group-ID" processes can be executed in parallel. Similarly, the "master-ID indexing master-group-ID" and "access address conversion to memory-region-ID" processes can be executed in parallel. Furthermore, the "access address conversion to slave-ID" and "access address conversion to memory-region-ID" processes, both of which simultaneously match the access address with addresses in multiple address ranges (slave-address-range, memory-region), are also a form of parallelism.

[0051] The arbitration process described above is all completed automatically by the chip, and multiple processes can be processed in parallel, ensuring rapid response. Only two hardware register bits (a security attribute bit and an access control bit) are used to implement permission control, making it simple and efficient.

[0052] According to another aspect of the present invention, Figure 4 FIG. 3 is a block diagram illustrating an apparatus 300 for managing chip resource access rights according to an embodiment of the present invention. Figure 4 The apparatus 300 for managing chip resource access rights includes at least one master device group 302 , at least one slave device group 304 , and at least one storage area 306 .

[0053] At least one master device group 302 includes at least one master device module assigned thereto, each of which is a resource that only initiates requests. At least one slave device group 304 includes at least one slave device module assigned thereto, each of which is a resource that only receives requests. At least one storage area 306 includes at least one storage space allocated from system memory.

[0054] At least one of the master device groups 302 is respectively provided with corresponding access rights for at least one of the slave device groups 304 or corresponding access rights for at least one of the storage areas 306. In addition, the configuration or management of the access rights can be implemented by the method described in the above embodiment, which will not be repeated here.

[0055] According to yet another aspect of the present invention, Figure 5 Schematic diagram of an electronic device 400 according to an embodiment of the present invention. Figure 5The electronic device 400 includes a memory 402, a processor 404, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the various steps of the method for managing chip resource access rights as described above are implemented.

[0056] In summary, the method and apparatus for managing chip resource access rights and the electronic device provided by the present invention are simple, because in a chip, the master device module usually has the same access rights to the slave device module, so the access rights are configured in the form of groups, instead of configuring the access rights for each master device module and slave device module individually, which simplifies the module design and saves the area of ​​the chip. At the same time, in the process of grouping, each master device module can only correspond to one master device group, and each slave device module can only correspond to one slave device group, avoiding the situation where conflicting access rights affect access after the access rights are configured. In addition, the master device group's permissions to the slave device group and the memory block can be flexibly configured one by one without additional binding, and the access rights are limited by the access type of the access request and whether the access type is allowed. The design is simple, easy to store the access rights configuration results, and can meet the requirements of permission management. In addition, the access type can meet the resource isolation requirements of the chip running multiple systems at the same time and the more complex permission management requirements that may exist in the future.

[0057] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's description and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for managing chip resource access rights, characterized in that: include: The resources that require permission management are divided into master device modules that only initiate requests, slave device modules that only receive requests, and system memory; Allocating at least one of the master device modules to a corresponding master device group in at least one master device group, allocating at least one of the slave device modules to a corresponding slave device group in at least one slave device group, and dividing corresponding storage space from the system memory according to the storage area; as well as The corresponding access rights of at least one of the master device groups to at least one of the slave device groups or the corresponding access rights of at least one of the master device groups to at least one of the storage areas are configured.

2. The method according to claim 1, characterized in that Allocating at least one of the master device modules to a corresponding master device group in at least one master device group includes: allocating at least one of the master device modules to a corresponding master device group in at least one of the master device groups according to an access type; Allocating at least one of the slave device modules to a corresponding slave device group in at least one slave device group includes: allocating at least one of the slave device modules to a corresponding slave device group in at least one of the slave device groups according to an access type; Partitioning a corresponding storage space from the system memory according to the storage area includes: partitioning a storage space having a corresponding address range from the system memory according to the access type.

3. The method according to claim 1, characterized in that The master device group includes a master device group identifier, the master device module includes a master module identifier, and the method further includes: receiving an access request sent by the master device module, the access request including an access type, a master module identifier of the master device module, and an access object, where the access object is the slave device module or the storage space; Searching for a master device group identifier of the master device group where the master device module is located according to the master module identifier; Searching for the access permission according to the master device group identifier and the access object; and Whether access is allowed is determined based on the relationship between the access permission and the access type.

4. The method according to claim 3, wherein dividing the corresponding storage space from the system memory according to the storage area comprises: Configure the block number and address range of the storage space, When the access object is the storage space, the access object includes a block number of the storage space, and searching for the access permission according to the master device group identifier and the access object includes searching for the access permission according to the master device group identifier and the block number.

5. The method according to claim 3, characterized in that The slave device group includes a slave device group identifier, and the slave device module includes a slave device identifier; When the access object is the slave device module, the access object includes a slave device identifier of the slave device module, and searching for the access permission according to the master device group identifier and the access object includes: Searching for a slave device group identifier of the slave device group where the slave device module is located according to the slave device identifier; and The access authority is searched according to the master device group identifier and the slave device group identifier.

6. The method according to claim 5, characterized in that The access object includes a slave device address of a slave device module, and before searching for the access authority according to the master device group identifier and the access object, the method further includes: matching the slave device identifier according to the slave device address.

7. The method according to claim 1, characterized in that Configuring corresponding access rights of at least one master device group to at least one slave device group or corresponding access rights of at least one master device group to at least one storage area includes: The master device group and the access object are associated, and access rights of the access object under different access types are configured.

8. The method according to claim 7, characterized in that The access types include secure access and non-secure access, and the access rights include both secure access and non-secure access, neither secure access nor non-secure access, secure access is possible but non-secure access is not, and secure access is not possible but non-secure access is possible.

9. The method according to claim 1, characterized in that Allocating at least one of the master device modules to a corresponding master device group in at least one master device group comprises: using the master device identifier of the master device module as an index, associating the master device identifier with the master device group identifier of the master device group on a register, Allocating at least one of the slave device modules to a corresponding slave device group in at least one slave device group comprises: using the slave device identifier of the slave device module as an index, associating the slave device identifier with the slave device group identifier of the slave device group on the register, Partitioning the corresponding storage space from the system memory according to the storage area includes: using the block number of the storage space as an index, and saving the association relationship between the block number and the address range in the register.

10. The method according to claim 1, characterized in that Configuring corresponding access rights of at least one master device group to at least one slave device group or corresponding access rights of at least one master device group to at least one storage area includes: Saving the access permission in a preset resource module, where the resource module is a slave device module; Disable write permission for the resource module.

11. A device for managing chip resource access rights, characterized in that: include: at least one master device group, each including at least one master device module allocated thereto, wherein the master device module is a resource that only initiates requests; at least one slave device group, each including at least one slave device module allocated thereto, wherein the slave device module is a resource that only receives requests; as well as at least one storage area, each including at least one storage space divided from the system memory, At least one of the master device groups is respectively provided with a corresponding access right for at least one of the slave device groups or a corresponding access right for at least one of the storage areas.

12. An electronic device, characterized in that: include: a memory configured to store information associated with access rights; as well as At least one processor is electrically coupled to the memory and configured to execute the method according to any one of claims 1 to 10.

Images