• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 613 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.

BCP for PDCCH

Aswathy Raj
Prodigy 210 points

Hi,

We are implementing PDCCH chain using BCP hardware accelerator.  Encoder and Rate matcher modules are configured according to the example project given. CRC and remaining modules are implemented on DSP.  We checked the outputs of encoder and rate matcher separately (BCP).  They are not proper. How to verify the output of individual modules in BCP??

thanks and regards,

Aswathy

  • 0
    TI__Guru* 81335 points

    I hope you are using C6670. Please confirm and also provide below information:
    1. S/W packages version (MCSDK, CCS, etc )
    2. Example project name and path
    Thank you.

  • 0
    TI__Mastermind 30405 points
    Hi Ashwathy,

    I am not sure I understood your question correctly. You mentioned that you've checked the outputs of encoder and rate matcher seperately and they appear to be incorrect. But the next line says "How to verify the output of individual modules in BCP??", but I believe you're already able to dump the output of individual sub-modules (encoder and rate-matcher) as you indicated that they appear to be incorrect.

    Could you please clarify your question? Thanks.

    Regards
    -Nitin
  • 0 in reply to Nitin Sakhuja
    Prodigy 210 points
    Hi Nitin,

    We are using pdk C6614 for our project. For testing the output of encoder alone , we commented out the header formation of CRC, RM and MOD in BCP example project. When we checked for the output, we were only getting the input data. Parity bits were missing. In the BCP manual they have written data should be aligned on 128 bit boundary. Since the global header(2 words), encoder header(4 words) and TM header(2 words) makes the data to begin with 128 bit boundary we didn't add filler words while forming the header. In the same method we checked the output of individual modules using pdkc6670. But it was giving correct output.

    thanks for the reply
    Aswathy
  • 0 in reply to Raja
    Prodigy 210 points
    Hi,
    We are using 6614.
    ccs version - 5.5
    mcsdk - sc_mcsdk_bios_2_02_01_03
    Eg project name:- Bcp_exampleProject

    thanks for your reply
    Aswathy