Implementing non-blocking SRIO DIO socket with multi-thread

Hui-kwon Yang

Intellectual 325 points

I use C6670 TI DSP.(TMS320C6670). CCS version 5.5.0.00077 and SYSBIOS version 6.37.2.27

I want to program to output periodic data via SRIO.

I designed two task.

-One sends data (via SRIO) periodically.(test main task): send 8KB data every 100ms

-The other just print at idle time. (test dummy task): print some character during main task is sending data

The source code for the two task is shown below.

When I execute this code, main task seems to be worked.(periodic SRIO is output to external device)

But the dummy task does not print any character.

What is wrong?

I use DIO socket(blockingsocket option of Srio_sockOpen() is "FALSE").

Please let me know, if you need more information.

===============================

U8 gTestChar='0';
S32 gTestCnt=0;

VOID Test_DummyTASK_Fxn(UArg a0, UArg a1)
{
while(1){

   if(gTestChar!='0')
     {
       System_printf("%c", gTestChar+gTestCnt);
       gTestCnt++;
   }
  else
      Task_sleep(1);
   }

}

#define TEST_BUFF_SIZE 8192
U8 gTestBuff[TEST_BUFF_SIZE];
VOID Test_MainTASK_Fxn(UArg a0, UArg a1)
{
S32 i, data_len;

data_len = TEST_BUFF_SIZE;
for(i=0; i<TEST_BUFF_SIZE; i++)
gTestBuff[i] = i;

while(1){
      if(gTestChar=='A')
        gTestChar = 'a';
      else
        gTestChar = 'A';
      gTestCnt = 0;

      SRIO_Write((U8 *)gTestBuff, 0x40000000, data_len);
      gTestChar = '0';
      System_printf("<Tx done>\r\n");
      Task_sleep(10);
}

}

VOID Task_Start()
{
Task_Params taskParams;
Task_Handle task_a, task_b;

   Task_Params_init(&taskParams);
taskParams.instance->name = "TestDummy";
   taskParams.priority = 6;
   taskParams.stackSize = 1024;
   task_b = Task_create(Test_DummyTASK_Fxn, &taskParams, NULL);
System_printf ("[] %s task created pri:%d\n", taskParams.instance->name, taskParams.priority);

Task_Params_init(&taskParams);
   taskParams.instance->name = "TestMain";
   taskParams.priority = 9;
   taskParams.stackSize = 1024;
   task_b = Task_create(Test_MainTASK_Fxn, &taskParams, NULL);
   System_printf ("[] %s task created pri:%d\n", taskParams.instance->name, taskParams.priority);

}

Srio_SockAddrInfo gSRIO_Addrinfo_Write;

S32 SRIO_Write(U8 *pBuff, U32 remote_addr, S32 data_len)
{
S32 result;
Srio_DrvBuffer srio_buf;

   gSRIO_Addrinfo_Write.dio.rapidIOMSB    = 0x00;
   gSRIO_Addrinfo_Write.dio.dstID         = DEVICE_ID_FPGA_8BIT;
   gSRIO_Addrinfo_Write.dio.ttype         = Srio_Ttype_Write_NWRITE;
   gSRIO_Addrinfo_Write.dio.ftype         = Srio_Ftype_WRITE;
   gSRIO_Addrinfo_Write.dio.rapidIOLSB    = (U32)remote_addr;

   /* Writeback the contents of the cache. */
CACHE_wbL1d (pBuff, data_len, CACHE_FENCE_WAIT);

   /* Initiate the transfer. */
   srio_buf = (Srio_DrvBuffer)l2_global_address((U32)pBuff);
result = Srio_sockSend (SRIO_Socket_Data, srio_buf, data_len, &gSRIO_Addrinfo_Write);
if(result < 0)
{
      System_printf ("Error: Unable to send payload over DIO socket\n");
      return -1;
}
   return data_len;
}

===============================

over 9 years ago

0 judahvang over 9 years ago

TI__Mastermind 32475 points

Can you tell me if you are using SysMin or SysStd as the default System.SupportProxy in your .cfg file?

With SysMin, it will not flush the output until you call System_flush();

SysStd will flush the output for you but it break real-time as it actually halts the processor.

See if you are dong something like below in your .cfg file:

var System = xdc.useModule('xdc.runtime.System');
var SysMin = xdc.useModule('xdc.runtime.SysMin')

SysMin.flushAtExit = true;
System.SupportProxy = SysMin;

Judah

0 Hui-kwon Yang over 9 years ago in reply to judahvang

Intellectual 325 points

Thank you for your reply.

I'm using SysStd. Here is the paragraph.

===========================

var System = xdc.useModule('xdc.runtime.System');
var Startup = xdc.useModule('xdc.runtime.Startup');
var SysStd = xdc.useModule('xdc.runtime.SysStd');
System.SupportProxy = SysStd;

===========================

I think something is wrong for initializing SRIO interrupt or creating SRIO socket.

But I don't know what it is.

0 judahvang over 9 years ago in reply to Hui-kwon Yang

TI__Mastermind 32475 points

Did I misunderstand your original post? I thought you said the main task was working but that you weren't getting anything from your System_printfs?

So if main task is working why do you think something is wrong for initiailizing SRIO interrupt or SRIO socket?

0 Hui-kwon Yang over 9 years ago in reply to judahvang

Intellectual 325 points

I didn't explain exactly.

I want that dummy task gets CPU during main task is waiting "SRIO Tx done" after sending a packet.

But when I execute the code, dummy task is working just after main task is sleeping.

0 Hui-kwon Yang over 9 years ago in reply to Hui-kwon Yang

Intellectual 325 points

What's wrong in this program?

Do you have any idea or advice about this issue?

This is very important for me.

0 Hui-kwon Yang over 9 years ago in reply to Hui-kwon Yang

Intellectual 325 points

knock knock

I'm waiting for your response.

0 judahvang over 9 years ago in reply to Hui-kwon Yang

TI__Mastermind 32475 points

Hey sorry most people are on thanksgiving break now. If it's SRIO specific I really don't know what could be happening.

0 Hui-kwon Yang over 9 years ago in reply to judahvang

Intellectual 325 points

Did you have good holiday?

So, give me your hand to solve my problem.

I wait long time.

0 Hui-kwon Yang over 9 years ago in reply to Hui-kwon Yang

Intellectual 325 points

Is there anybody who gives advice?

0 David Friedland over 9 years ago in reply to Hui-kwon Yang

TI__Mastermind 18320 points

Hui-Kwon,

It appears that your issue is actually related more to the SRIO library functionality and not TI-RTOS, and that we have exhausted suggestions on this forum. I am therefore moving this thread over to the device forum in hopes that someone there can give some additional advice.