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.

TMS320F28379D: T-Format Library functions CPU cycles

Part Number: TMS320F28379D

Hi Champion

My customer evaluated T-format, and have a question as below:

The User Guide said PM_fformat_receiveData need 500 CPU cycles, but when we debug in the CCS, it will take 2000+ CPU cycles. We also use oscilloscope to measure the execution time, it's about 11us (CPU @ 200Mhz Freq).

Other functions all looks good except PM_fformat_receiveData, is there anything wrong?

Thanks a lot.

BR,

Sam 

  • Hello Samsai,

    Cycles taken by PM_fformat_receiveData function depends on the command being used, type of the encoder, data width, CRC polynomial/check etc.
    As noted in the document -
    "CPU cycle data depends on Encoder under test, and the commands/data being used along with certain function. These numbers could vary significantly depending on the command and corresponding data, and so forth."

    So, to answer your question - "Other functions all looks good except PM_fformat_receiveData, is there anything wrong?" 
    I don't think there is anything wrong so long as you are receiving and sending data and your CRC checks are passing as expected.

    -Bharathi