• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 514 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.

Problem with RMAN_assignResources

Wai-Ming Lai
Prodigy 40 points

Hi,

I recently increased the total number of EDMA linked transfers from 147 to 211 in the video decoder I'm working on.  It doesn't have any problem on CCS, but on Linux, I got a return status of 1 from RMAN_assignResources.  The framework components trace output did not explain what actually happened.

My questions are why there is a difference between CCS and Linux?  And how I could get around it?

Any advice is appreciated.

  • 0
    TI__Expert 7415 points

    The difference between the 'no OS' and 'Linux" builds of your app is that when no OS is being used, you get ownership of all the EDMA3 resources.

    When you run on Linux, Framework Components requests for resources from the Linux kernel. Most likely not enough resources are available on your system for codec (211).

    Depending on what else you are running on your system that uses DMA, you may be able to build your kernel so that it uses fewer resources. Linux experts might be able to comment on that.

  • 0 in reply to Gunjan
    TI__Prodigy 40 points

    Gunjan,

    Thanks for the reply.  I think first I have to find out which resouces it fails to assign.  I've printed out the trace but it didn't tell me much.  The only thing it said was return status = 1.  What does that mean?  How can I get more info?

    And how do I build my kernel to use fewer resources?

    Thanks,

    Ming

  • 0 in reply to Wai-Ming Lai
    TI__Expert 7415 points

    Ming,

    Which function call returns the status = 1 ? Maybe you can share the the log on this forum ?

    Also, does the codec documentation indicate what resources it needs ? There may be a difference between the codec requirements of the codec you swapped out with the new one. You should check that and see if you can change the codec/scratch group association in your cfg file.

    Since RMAN is a Framework Components module, you may also want to enable trace specifically for Framework Components. Use the link below to determine how to enable trace for your particular release of Framework Components:-

    http://processors.wiki.ti.com/index.php/Trace_in_Framework_Components#Trace_in_Framework_Components

    Might help to share that trace here, will give you an idea of which resource is causing it to fail.