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.

ti6638k2k SRIO and IPC not working on Integration

Hi,

When I try to run SRIO on all 8 cores on 6638 board, it works fine. But when I integrate the same with IPC,  SRIO works fine on core 0 bu  , SRIO on cores 1-7 stops working. I tried to debug it and found that it fails at qmss_start function.  I receive " Unable to start the QMSS" print on console. Can you please provide some inputs.

P.S: I have taken the SRIO reference from srioloopbackexample.

Regards,

Ruchika

  • Can you please try the following IPC-SRIO based example from MCSDK ?
    C:\ti\pdk_keystone2_3_01_04_07\packages\exampleProjects\transportIpcSrioMultiBoardProducerK2KExampleProject
    C:\ti\pdk_keystone2_3_01_04_07\packages\ti\transport\ipc\c66\srio\example\k2k
  • In addition to what Titus wrote:

    You can start debugging the problem.  Make sure that everything is built using full symbolic debug and no optimization, then step through the code (in CCS F5 is step in) and find out where exactly the error message is generated.

    It will help to figure out what is the problem

    Ran

  • Hi,

    Thanks for help. Just to update that we are using DIO and above mentioned examples are using Type9 and Type11. Is qmss really required for DIO?

    We tried to debug using step in,  qmss_start API gives non-zero value so we get " Unable to start the QMSS" message.

    Meanwhile, I'm working on the given suggestions.

    Regards,

    Ruchika

  • I think that you are right and that DIO mode does not use the Navigator (QMSS and CPPI). If you look at the SRIO block (look at the User's Guide) you see that there are different hardware modules for the message based SRIO (Type 9 and 11) and for DIO including an internal DMA that writes the incoming data to the memory.

    My only other comment is that SRIO data transfer uses SES and SMS MPEX register set number 9 so they need to be configured to what physical address you want the data to go.

    Ran
  • Hi Ran,
    Yes, as per user guide DIO does't require (QMSS and CPPI) but in C:\ti\pdk_keystone2_3_01_04_07\packages\exampleProjects\SRIO_LpbkDioIsrK2KC66BiosExampleProject , (QMSS and CPPI) is used in SRIO even though its using DIO. So, I'm confused whether to use it or not.

    qmss does't create problem when I use it in SRIO alone. But the moment I integrate my IPC code with SRIO , qmss_start fails.

    Regards,
    Ruchika
  • You can go through the example SRIO_LpbkDioIsrK2KC66BiosExampleProject and see if indeed QMSS and CPPI are used and for what case. It might be a left over from older project, or I may be wrong all along

    In any rate, just for fun, try to debug the code and see what cause the qmss_start to fail

    Ran
  • I'm having this fun for last 3-4 months. I made it working but it breaks when I integrate with IPC.
    SRIO_LpbkDioIsrK2KC66BiosExampleProject is using QMSS and CPPI. In Srio_device_init function and

    drvCfg.u.drvManagedCfg.rxCfg.rxCompletionQueue = Qmss_queueOpen (Qmss_QueueType_HIGH_PRIORITY_QUEUE,
    coreToQueueSelector[coreNum], &isAllocated);

    I'm thinking to remove Qmss. If you could give me the hint around it.(which sections to remove)

    Regards,
    Ruchika
  • I apologize for the "fun" reference.

    First copy the example project to a back-up

    Next try to eliminate any reference to QMSS and CPPI from the CFG file and from the code and try and build it again. If you have issues please post it here and I will try to produce your issue

    Best Regards

    Ran
  • Hi Ran,

    I tried to eliminate QMSS things one by one. Started with its usage where driver is configured. Eliminated  Qmss_queueOpen (Qmss_QueueType_HIGH_PRIORITY_QUEUE, coreToQueueSelector[coreNum], &isAllocated);.

    SRIO worked with above changes. But as soon as I removed qmss_start; driver initialization failed.

     Could you please look into it.

    regards,

    Ruchika

  • Just came from vacation and notice that I did not answer this e2e

    Can you update the status of your issue?

    Thanks

    Ran

  • No update for a week.  Can I close the thread?

    Ran

  • Hi Ran,

    We got it working with QMSS. Sorry for the delayed response. You can close the thread.

    Thanks,
    Ruchika