• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 346 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.

TMS320F28386S: Can Projects Work with Multiple Processor Families?

Ed Sanders
Genius 4085 points
Part Number: TMS320F28386S
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Greetings,

Our final code is built from several projects one of which is specific to the product.  The others are general projects which are designed to run on any product.  Each is built into an abs file, and the collection of those are linked to make the final image.  Now we are adding a second processor family, and using the same general projects we had used before.  Obviously, the main project must be tied to the correct processor.  But do the other projects need  to, especially if they don’t access any HW?  BTW both families are using C28 processors.

Thank you,

Ed

  • 0
    TI__Mastermind 21080 points

    Hi Ed,

    Which two processor families are you trying to use? Do these general projects use any of the device peripherals? There are subtle differences between every device family in device hardware and software.

    Best Regards,

    Delaney

  • 0 in reply to Delaney Woodward
    Genius 4085 points

    Hi Delaney,

    We are using the TMS320F28379 and the TMS320F28388 families.  I don’t expect HW portions to work where the IP and addresses aren’t identical.  Only one of the general projects involve HW, and we expect that it will change because of the differences between the two families.

    The projects which don’t involve HW are the projects of concern.  Currently, they are set up for the 379 and a specific Debug Probe.  But the main project could have that combination or could have a 388 with a different Debug Probe.  So the question is whether or not those non-HW 379 projects will link correctly with a 388 project and can be debugged in the 388 environment without modifying them.  If so, then we can use those projects on products based on both families.

    Thank you,

    Ed

  • +1 in reply to Ed Sanders
    TI__Mastermind 21080 points

    Hi Ed,

    If the main concern is the debug probe, that is configured by the target configuration file in your CCS project, so it should be sufficient to change the ccxml file you are using. You would also want to change the linker cmd file to use one for the F2838x device family (which was mentioned in the other thread you linked). And you want to ensure the functions used to initialize the device from device.h and device.c are referencing the F2838x files. For this, I would suggest importing an empty F2838x project from C2000ware and copying your code over to that.

    Let me know if you run into any other issues. It may be helpful to take a look at our migration tool as well: C2000 Migration.

    Best Regards,

    Delaney

  • 0 in reply to Delaney Woodward
    Genius 4085 points

    Hi Delaney,

    I wasn’t aware that the debugger is controlled by the target configuration file.  That is good to know.  And yes, we have changed our cmd file, but not for the projects which are purely logical.  We expect that any projects which do use the HW peripherals will require new projects which will be tied to the 388.

    Thank you,

    Ed