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.

TMS320F280049C: CMPSS step response time

Part Number: TMS320F280049C

Dear C2000 team,

is there a chance to make a statement to the CMPSS step response time distribution across multiple CMPSS modules on a chip?

In the Datasheet we specify this time with typ. 21ns and max. 60ns.

The question which I have got now, is related to the behavior of multiple CMPSS modules in a single chip.

Would this time be similar/the same on all CMPSS modules on a chip, or can we expect variations between typ. and max. value across the different CMPSS modules on the same chip?

Thanks,

BR,
Matthias

  • Hi Matthias,

    There isn't a significant variation across CMPSS modules for CMPSS parameters. This includes response time. If you look through the DS, you'll notice this isn't exclusive to the CMPSS as most of the other modules are also specified this way where performance isn't indicated per module instance.

    Nevertheless, even if there is variation, all instances should still be within the max 60ns spec. Are you seeing big variation across instances?
  • Hi Frank,

    the customer is trying to find a way to compensate these delays in their system design. There might be ways, if for all CMPSS modules in a device this step response would be almost equal (does not matter at which value up to 60ns). If this step response is varying between lets say 21 and 60ns across the multiple CMPSS modules in a device, it might be more challenging (or not even possible) to compensate for that.

    So can we make an statement on how many ns the step response time might vary between the different CMPSS modules on a single device?

    BR,
    Matthias
  • Hi Matthias,

    I understand where you are coming from. It's generally good practice for customers to design their application against the max spec especially if one is given as this makes their design more robust. Designing an application that is too sensitive to instance-to-instance variation can leave the application very open to mysterious bugs because a lot of factors can affect this variation. That is just my 2 cents.

    Nevertheless, I have seen variation of about 5ns across CMPSS modules. Please keep in mind that this is observation on a few devices. Even though it is likely that all devices will behave similarly in regards to this, we give no guarantee that they would.