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

CCS/TDA3XEVM: __pblock variable takes up WMEM space in EVE

Henry2333
Intellectual 490 points
Part Number: TDA3XEVM

Tool/software: Code Composer Studio

Hi,friends.

I am using EVE and implemented my kernel on a .k file.

I noticed this variable(__pblock_func ) in the .h file builded by the .k will take up some space in WMEM.

This makes the first address of vcop_malloc applying for WMEM increase.

As a result, the available WMEM space becomes smaller.

In my algorithm, I need to use WMEM to store some intermediate variables.

This means that as the number of operators increases, the space available to WMEM decreases, and the calculation efficiency becomes lower, which affects the overall performance.

Can I put the variable in other memory spaces without affecting performance?

If so, what should I do?

  • 0
    TI__Guru 56820 points

    Hi,

      The amount of memory required for pBlocks is not very high, it is recommended to kept in WMEM and hence you will have to reduce your WMEM consumption to account for the memory required for it.

      What do you mean by  "Can I put the variable in other memory spaces without affecting performance"? Any data which is processed on VCOP should be available in one of the internal memory of EVE ( IBUFL, IBUFH or WMEM) as VCOP cannot access any  other memory.


    Regards,

    Anshu

  • 0 in reply to Anshu Jain
    Intellectual 490 points

    Hi,Anshu

    Thank you for the reply.

    I have implemented most of the operators now, and I will continue to increase in the future.

    The WMEM address I am applying with vcop_malloc is 0x40040a20.

    This means that I have consumed about 2.5k of space to store these variables?

    I noticed that the size of the __pblock variable in different operators is different, some are 10 and some are 152.

    I was wondering if I could modify my code to minimize the size of the __pblock variable in some operators.

    With the increase of operators, will there be other variables that will occupy Wbuf space in addition to __pblock?

    What factors are related to the size of the __pblock variable?

  • 0 in reply to Henry2333
    TI__Guru 56820 points

    Hi Henry,

          The _pBlock memory size is dependent on the operations you are doing in the VCOP kernel so until unless you change your kernel it won't change. WMEM is totally under the developers control. So apart from pBlock memory rest all depends on how  you are using it.

    Regards,

    Anshu