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

TMS320F28388D: Quote of Software resource for next generation device

Ryuuichi machida
Guru 12765 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: C2000WARE, TMS320F28379D, , CONTROLSUITE

Hello Expert,

Today, I would like you to ask about way of thinking of software compatiblity due to new device(generation change) of C2000 series.

In case of development tool, I understand that user can develop their production without depending on device itself by using CCS and C2000ware.
However, I would like you to confirm how you consider from viewpoint of software(Device Driver/Firmware/Appication).

For instance, user have already released product which is implemented TMS320F28379D.
And, they are considering next product and consider to use TMS320F28388D.
Then, of course they consider how much they can use software resource of TMS320F28379D for TMS320F28388D.

If you have document which is described how TI consider Roadmap from viewpoint of software, could you please share it to us ?
If you do not have, could you please explain your way of thinging by using above example ?

Best Regards,

  • 0
    TI__Genius 11645 points

    Pls take a look at the below migration guide

    https://www.ti.com/lit/an/spracq1/spracq1.pdf

    You can look at Sec:4 for  more details

    <c2000ware>\device_support\f2838x\docs\Driverlib_F2837x_to_F2838x_Migration_Guide.pdf

    Hope this helps..

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Guru 12765 points

    Hello Karthik-san,

    Thank you for your reply.

    I will confirm it and when I have question, I will ask you again.

    I have additional question.

    * "driverlib" appeard from C2000ware (There were no "driverlib" folder in ControlSuite).

    On the other hand, regacy "peripheral header file" also exist.

    When same function exist, which one is better to use ?

    If you have document how to use properly, could you please let me know ?

    Best Regards, 

  • 0 in reply to Ryuuichi machida
    TI__Genius 11645 points

    Hello Ryuuichi-san,

    I will get some driverlib expert to help you with this. Thanks.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    TI__Mastermind 36055 points

    Hello Ryuuichi-san,

    C2000Ware supports multiple ways of accessing peripheral registers - direct register access, driver library (DriverLib), and bitfields.

    DriverLib APIs are the preferred way of accessing peripherals for the new generation MCUs.

    Bitfield is supported only in the older generation of MCUs.

    But Bitfield headers are provided for the new generation MCUs for compatibility and easy migration.

    The following figure shows the comparison between driverlib and bitfield. 

    ../_images/RegAccess.png

    Refer the following link for more details

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Guru 12765 points

    Hello Siddharth-san,

    I roughly understood about difference/benefit b/w driverlib and header file by referring your reply and following programming guide.

    https://www.ti.com/lit/an/spraa85e/spraa85e.pdf

    Thank you !

    Hello Karthik-san,

    >Pls take a look at the below migration guide

    According to C2000ware, it seems that you have migration guide for only 2837X to 2838X.

    Following is just example. I would like to know thinking of way for C2000 series totally.

    For instance, user have already released product which is implemented TMS320F28379D.
    And, they are considering next product and consider to use TMS320F28388D.
    Then, of course they consider how much they can use software resource of TMS320F28379D for TMS320F28388D.

    Q. Do you have any other migration guide for other devices ?

    (I would like to know documentation folder or URL which user can get this information.)

    Q. If you do not have so much migration guide, Could you please tell me the points to notify in software construction to continue using the C2000 series ?

    Best Regards,

  • 0 in reply to Ryuuichi machida
    TI__Mastermind 36055 points

    Hello Ryuuichi-san,

    Is this resolved? Or do you have any more questions?

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Guru 12765 points

    Hello Siddharth-san,

    >Is this resolved? Or do you have any more questions?

    I do not have question for your answer at this time.

    The reason why I can not close this thread is because I have question for Karthik-san's answer.

    Best Regards,

  • 0 in reply to Ryuuichi machida
    Guru 12765 points

    Hello Karthik-san,

    Could you please send me about your feedback for my following question ?

    Q. Do you have any other migration guide for other devices ?

    (I would like to know documentation folder or URL which user can get this information.)

    Q. If you do not have so much migration guide, Could you please tell me the points to notify in software construction to continue using the C2000 series ?

    Best Regards,

  • 0 in reply to Ryuuichi machida
    TI__Mastermind 36055 points

    Hello Ryuuichi-san,

    I don't think there is a migration guide for other devices. Any particular device that you are looking for ?

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Guru 12765 points

    Hello Siddharth-san

    Thank you for your following up.

    >I don't think there is a migration guide for other devices.

    Understood.

    >Any particular device that you are looking for ?

    Not specially.

    I just want to confirm which point user should take care to continue to use software resource of C2000 which they used on current product to latest/other C2000.
    (If you don't have especially, when user choose next CPU for future product, we think there is no advantage comparing other CPU.)
    Because, actually, they can understand how user can develop by using C2000, but it seems there is no resource for future product.)

    Best Regards,