• Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 242 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Framework Components usage questions

Franck
Intellectual 685 points

Hi,

I am pretty new in using the XDC tools to configure and use RTSC modules. Before, I was using some Framework Components modules but configured them without the XDC tools (directly from my app). Now, I want to migrate their configuration through the XDC tool .cfg file and I have some questions.

I am using the Framework Components ACPY3, DMAN3, DSK2 and edma3.Settings modules. I am also using the EDMA3 LLD driver and resource manager packages. So I would like to specify DMAN3 to use the EDMA3 LLD resource manager to get a centralized EDMA3 resource management. I could find on some posts that this is possible by setting the "DMAN3.useExternalRM" flag to true, which I did. Then, this configuration parameter specifies that the edma3.Settings module should be loaded and configured accordingly. I therefore loaded the module in the .cfg file and hoped I could use its default settings. But when I try to compile, I get a complaint about semCreateFxn, semDeleteFxn, semPendFxn and semPostFxn being not initialized. Do I need to explicitly implement such functions in my application and refer them in the .cfg file? If so, I saw that the function declaration always involves a parameter called "key". What does this parameter means and how should I handle it?

In my application, I am using the EDMA3 LLD driver module which makes use of several configuration parameters during its instance creation (EDMA3_DRV_GblConfigParams and EDMA3_DRV_InstanceInitConfig). I also see that the edma3.Settings module needs similar initialization parameters (globalConfig, regionConfig, maxTccs, maxPaRams, maxEdmaChannels...). I am confused in how those parameters are used by the LLD driver module and the edma3.Settings module. I have the feeling that some of these parameters are actually global EDMA3 Resource Manager (RM) module parameters which should be set only once in the application, while some others are linked to instances created with the EDMA3 RM. What parameters in both modules should I configure for the underlying Resource Manager to be adequately configured?

What is exactly the meaning of the edma3.Settings.globalInit flag? Has it something to do with my preceding question?

Thanks for your help.

Franck