• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 438 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

total no of descriptors used more than 16K

rajanikanth g81
Prodigy 170 points

Hi,

My Development environment is: CCS ver  5.2.1.00018;

MCSDK Packages: mcsdk_2_01_02_05 ; pdk_C6678_1_1_2_5 packages.

EVM Board : TMDXEVM6678L

Can you please let me know, is there any example project available which used Linking RAM 1 or the total no of descriptors used is more than 16K in QMSS configuration?

 

Thanks in advance.

 

Thanks & Best regards,

Rajanikanth.

 

 

 

  • 0
    TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    For internal linking RAM, the size in bytes is hidden actually, so, the LLD always takes the size in descriptor entries, and if you set linkingRAM0Size to 0 (and linkingRAM0Base to 0) it will fully configure the internal linking RAM which supports 16K entries on K1. Also, the Linking RAM unit size should be 64bits.

    Inorder to use the QMSS’ internal Linking RAM, we need to specify a value of 0x00080000 for KeyStone I, 0x00100000 for KeyStone II’s QM1. Please check Table 4-4 from the user guide below:

    http://www.ti.com.cn/cn/lit/ug/sprugr9h/sprugr9h.pdf

    In general, Queue managers need to be programmed with identical descriptor memory regions and likewise, the linking RAM

    registers in both QMs need to be programmed identically. Please note that, Linking RAM 0 need to be configured to use internal QMSS memory where as for Linking RAM 1, it would use L2 or DDR. For efficiency reasons, it would be best to use the internal QMSS Link RAM memory.

    The Linking RAM Region 0 Base Address Register is used to set the base address for the first portion of the linking RAM. This address is used by the queue manager to calculate the 32-bit linking address for a given descriptor index. For more info. please see Table 4-1 for queue configuration region registers from the above user guide.

    I would recommend you to review the attached QMSS PPT slides for more understanding on QMSS descriptors and descriptor memory regions on slides 18 and 19

    ./cfs-file/__key/communityserver-discussions-components-files/791/6663.0675.KeyStone-Multicore-Navigator.pptx


    Thanks & regards,

    Sivaraj K

    ----------------------------------------------------------------------------------------------------------------

    Please click the "Verify Answer" button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------------

  • 0 in reply to Sivaraj Kuppuraj
    Prodigy 170 points
    Hi Sivaraj,

    Thanks for the reply.

    Can you please let me know, on K1, is there any example project available which used Linking RAM 1 or the total no of descriptors used is more than 16K in QMSS configuration?

    I have checked the example projects like 'qmInsRegionTestProject', but I am unable to find out any project which used the total no of descriptors more than 16K in QMSS configuration.


    Thanks & Best regards,
    Rajanikanth.
  • 0 in reply to rajanikanth g81
    TI__Mastermind 35645 points

    Hi,

    In my opinion, whatever the examples provided by drv folder of "pdk_C6678_1_1_2_6" are the ones which are available and if you need to configure other than the provided basic examples, please refer the api reference document in which, kindly check the data structure "Qmss_DescCfg::descNum" which should be used to allocate the number of descriptors and can configure the same in the code.

    The documentation for this struct was generated from the following file:
    qmss_qm.h

    Please refer the descriptor configuration structure from the below path:
    ~\ti\Keystone_MCSDK_02_01\pdk_C6678_1_1_2_6\packages\ti\drv\qmss\docs\doxygen\html\struct_qmss___desc_cfg.html

    Like wise, the QMSS descriptor configuration based pdk examples from MCSDK 2.1 are as below:

    ~\ti\Keystone_MCSDK_02_01\pdk_C6678_1_1_2_6\packages\ti\drv\exampleProjects\qmDCfgTestProject
    ~\ti\Keystone_MCSDK_02_01\pdk_C6678_1_1_2_6\packages\ti\drv\exampleProjects\qmDescTestProject

    Thanks & regards,
    Sivaraj K

    ----------------------------------------------------------------------------------------------------------------
    Please click the "Verify Answer" button on this post if it answers your question.
    ----------------------------------------------------------------------------------------------------------------