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.

TMS320F28P659DH-Q1: what will happen when core configuration in properties can't match used device.

Part Number: TMS320F28P659DH-Q1

Tool/software:

Hi experts,

Good day! I am asking for customer. The customer is now using F28P659DK-Q1, but they choose TMS320F28P659SH6-Q1 in "Variant and Core" in Properties, what will be influenced when Core PN can't match actual used PN?

Best Regards

Kita

  • Hi Kita,

    That variable gets passed in CCS and based on this, will use device-specifc XML at compile, debug and run-time.  The XML will use the associated register properties for the specified device type.  In this particular case where actual device is F28P659DK-Q1 but XML chosen is for SH6, then registers and functions pertaining to CPU2 will "seem" not to exist and may return a run-time error if CPU2 will be used in the application.  With SH6 chosen as the device variant, lockstep feature may also not be supported but if the application is not using CPU2 or lockstep, there might not be a problem during run-time or debug.  To be sure, customer has to do full validation of the application if they cannot revert back to variant DK6.  There are several instances in compile-time and run-time where device dependency is used that I may not be able to cover here.

    Regards,

    Joseph