• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 299 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.

TMS320F28388S: F2837xPTP to F2838xPTP HW and SW migration?

AnBer
Mastermind 30395 points
Part Number: TMS320F28388S
Other Parts Discussed in Thread: SYSCONFIG

Team,

I have looked at the "F2837x to F2838x migration guide SPRACQ1" already and also at some different E2E posts (like here about power and here about peripherals differences).

On the HW side:
Assuming that the new features/modules of F2838x are not used (as the idea here is to enable additional F283xx IC sourcing option for a same project):
-Are you aware of any successful PCB design that enable one single PCB to be compatible with both F28379s and F28388S?

From the power tree point of view it seems that the power consumption (referring to this E2E post) is within +/-5%.
-Any new info or consideration that need to be taken into account?

-For PTP package are there additional consideration?

From the SW side:
-how easy is it to migrate a CCS project if the new modules features are not used?
-Have we tried to take F28379x CCS example and migrate it to F2838x just by importing it?
-Is using sysconfig an advantage for the migration?
Are there some specific features in the tools for this purpose?
For example a "back compatibility" button for F28388 config that would turn off all peripherals not present on F28379 / set default register config that would not conflict with code being migrated from F28379?

Thanks in advance,

A.

  • 0
    TI__Mastermind 42195 points

    AnBer,

    AnBer said:
    -Are you aware of any successful PCB design that enable one single PCB to be compatible with both F28379s and F28388S?

    Customers typically choose a device and run with it. We have had many customers move from F2837x to F2838x when that device was ramping.

    AnBer said:
    From the power tree point of view it seems that the power consumption (referring to this E2E post) is within +/-5%.
    -Any new info or consideration that need to be taken into account?

    From a power estimates I would tell you to go look at the datasheets. If you are not using the added features on F2838x then I would estimate that the power requirements should be pretty similar.

    For the PTP package go through and verify pin numbers are all identical.

    AnBer said:
    From the SW side:
    -how easy is it to migrate a CCS project if the new modules features are not used?
    -Have we tried to take F28379x CCS example and migrate it to F2838x just by importing it?
    -Is using sysconfig an advantage for the migration?
    Are there some specific features in the tools for this purpose?
    For example a "back compatibility" button for F28388 config that would turn off all peripherals not present on F28379 / set default register config that would not conflict with code being migrated from F28379?

    Its generally pretty easy to port between these devices. 

    If you're using driverlib it really takes care of almost everything. But I'm sure there would be a few differences to resolve, all minor things.

    Running the code built for a F2837x on a F2838x probably wouldn't work I think I remember some clocking changes, and you would want to make sure that you have correctly configured all of the new modules to be shutdown if you're not using them.

    No SW porting or feature disable tool is available.

    Regards,
    Cody