Hi Egnesh,

Thank you for the post. I have split and created a new thread. I am requesting expert to look into this thread.

Please provide more detail about your integration issue,

1. What are the issues faced in integration?

2. Able to build successfully? Able to run ? Running into any issue?

3. Please share some log messages? What is your project? What it does?

etc.

Thank you.

Hi Rajasekharan,

First understand the issue i am facing,...its not about running or log messages....Its about how to Integrate with my
 project......Waiting for your reply.....

hi ,
Thanks for your reply.....
the co-processors in TMS320C6670 doesn't seems to be a user friendly as expected.....
In Tcp3d even to find the blocksize parameter path and input data(.dat) file seems to be very diffcult....
It seems someone who has written this code should give us a code walk through....There are many .dat files...
So we are not able to find correctly which .dat file we have to choose.....Beacuse we have to give our input data with block size for Turbo Decoding process.....
If you advice us to read the docs ....they are not providing the include paths...rather these docs are giving the process of a Tcp3d(turbo decoding).....
Now it seems a headache for us to handle this coprocessor.....It should be like a black box for us...Just giving the our inputs and expecting our ouputs.....So please refer an expert as our project is delayed for 2 months because of this coprocessor...
As we have to meet the frame timing in LTE TTI of 1ms we need the coprocessor role in our project urgently......So please refer an expert immediately.....

Hello,

If you look at the tcp3d/test/gentestvectors folder, all the input parameters and input data is generated through the .cfg files (which are in turn autogenerated by matlab scripts). The config files specify the block size index, number of iterations etc. There is a script called genTestVect.bat which parses these .cfg files and generates the final stimulus .dat files to be parsed by the Example application. In the tcp3d test application, the tcp3d_testset_functions.c reads these .dat files using getTestSetCB API and allocates memory for each of these data (LLR data, reference output data etc). If you would like to do unit test using your own data, you should be able to format your data in the format that the example reads from. i.e your input configuration registers setup should be block0_cfgreg.dat, input LLR data should be block0_llrs.dat etc. (Another alternative would be to have a header file to store all your input data in it and reference this header file in the tcp3d_testset_functions.c)

The test framework shows how to setup the input data and the send and receive tasks for moving data to/from TCP3d. In a real application, all your input data would be pointers to memory.

Regards,

Arun