Dave SDK help-content-------Resource Group



ResourceGroup

from the point of view of MCU software, the bit field of register is the smallest function unit. HW Resource Groupis a series of can beURI(Uniform Resource Identifier)The collection of bit fields that are recognized. In addition, this register bit field implements the function and composition of the hardware function block,e.g. CCU8a piece ofCC8The unit contains multiple register bit fields, which correspond to theURIis a"peripheral/ccu8/*/cc8/*","*"represents"any"unit orSlice. This naming method is useful in that it can contain all the hardware units (withFPGAthe same concept).

Note: Although it is a bit field of the same register, it may also appear in a different HW Resource Group the.

A full-format hardware resource group is like this:

Http://www.infineon.com/0.1.30/peripheral/ccu8/0/cc8/0/gidls_ssi

written in Manifest in:

resourcegroupuri=["Peripheral", "ccu8", "*", "CC8", "*";

in order to find specific MCU the specific HW ResourceGroup we can use DAVE? SDK Device Explorer.

in this case, HW ResourceGroup the corresponding is xmc4500-f144 of the "peripheral/ccu8/0/cc8/0" , you can see the function block CCU8 the composition.

in the Manifest we can use one or more Resource Group , define the virtual signals and write their names according to the appropriate application requirements. You can Establish a connection between the signals in different apps, you can also define the signal is not connected, the user is connected in Dave .

from a more general point of view, we can define a hardware unit as containing io one or more of the signals Resource Groups , with this Resource Groups Some specific functions can be implemented.

There are a lot of related connections between hardware units, so it's hard to take care of all the connections manually. So,solver will solve this problem for us,theAPP Developers just need to define resourcegroupsconnection between the. For example: Imagine that we now have4A resource group{p1/0, P1/1, p2/0, p3/0}("P"Representative"Peripheral" (Peripherals)), each hardware group contains someresourcegroups("RG")

2. {rga/0, RGA/1} ? p1/0

4. {rga/0, RGA/1} ? P1/1

6. {rgb/0, RGB/1} ? p2/0

8. {rgz/0, RGZ/1} ? p3/0

each member represents the corresponding hardware or resource group. In the following scenario, we have two corresponding hardware groups ("p1/0" and "P1/1"),their internalThe name of the resource group is the same, for example, two usic modules have two channelrespectively.

In the course of your observation you can see the connection between modules with lots of hardware ( form Interconnection network to interconnectionwork " but it doesn't matter, we have solver ! Via solver We just need to care about the connection to the resource group

whenSolverdecide if you need to connect to the requiredResource Groupafter that, you can pass thetempletesorManifestRequirements inSolverreturn the appropriate register address, or you can use the existingAPPLet them configure for you.

in the end, as a APP developers and users you just care about the virtual signal connection, do not need to care about the hardware connection.

Dave SDK help-content-------Resource Group