• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 628 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.

CCS/TMS320F280049: C2000Ware and CCS version

Akihiko Fujinaka
Expert 3505 points
Part Number: TMS320F280049
Other Parts Discussed in Thread: C2000WARE,

Tool/software: Code Composer Studio

Hello Experts,

I received some questions from our customers.

1. C2000WARE v02.00.00.02 Release Notes says,
there listed total 13 changed as the "Fixed in this release", then they picked up the following changes
which might related to TMS320F280049 device.

C2000DRIVERS-1939 F28004x CLA examples fail in Flash configuration S2-Major
C2000DRIVERS-1907 ADCINTFLG Workaround S1-Critical
C2000DRIVERS-1894 DCAN - some bit rates not working S3-Minor
C2000DRIVERS-1677 EPWM: EALLOW is not being used in APIs related to global reload functionality S2-Major

Are these changes really related to the TMS320F280049 device?
Do they need to move to C2000WARE v02.00.00.02 because of these changes?
Or can they stay on C2000 ware version 1.06.00.00?


2. SPRUI46B.pdf,C2000Ware Quick Start Guide describes as follows.

C2000Ware (v02.00.00.02) requires:
• CCS v9.0.1 or newer
• C2000 Compiler v18.12.1 LTS or newer
• ARM Compiler v18.12.1 LTS or newer

Can you explain the reason why they needs to upgrade to CC v9.0.1 from their current version 7.3?

3. If they need to change the version from 1.06.00.00→2.00.00.02.
Are there any procedure document to change the version?
Especially, they think they need to change the driverlib file, so these related documets are expected.

Regards,
A.Fujinaka

  • 0
    TI__Genius 10215 points

    hi ,

    1. Yes these 4 tickets are applicable to F28004x.

    If any of these changes are of importance/ functionality being used by them like in ADC / EPWM/ CAN then yes they should move . Only 3 of these except C2000DRIVERS-1939 would be applicable . C2000DRIVERS-1939 is for an example.

    2. They wouldn't need to upgrade to the latest CCS unless they are looking at getting support for he new device F2838x.

    The only reason these tools are mentioned are since this latest package has been validated on these tool versions.

    3. Nothing specific . They can just compare the latest files from the 2.00.00.02 version and pick the files for the peripherals or devices they use.

    Regards.

  • 0 in reply to MEGHANA MANAVAZHI
    TI__Expert 3505 points

    Hello

    Thanks for your quick answer.

    Regarding #3, Can I double check ?
    1. Our user already uses a certain project file on version 1.06.00.00 environment.
    2. They want to reuse this project file on version 2.00.00.02 environment.
    3. What kind of operation or procedure will be required for this version change?

    This confirmaiton is because there are 2 new files in the driverlib folder.
    From the previous answer, I recognized just using those files in new version of driverlib folder is enough, but I found new files , driverlib_coff.lib and driverlib_eabi.lib , in C:\ti\c2000\C2000Ware_2_00_00_02\driverlib\f28004x\driverlib\ccs\Release folder. So I am try to confirm again.

    Regards,
    A.Fujinaka

  • 0 in reply to Akihiko Fujinaka
    TI__Genius 10215 points

    hi ,

    Yes when it comes to picking the source files just using the latest files from the version 2.0.0.2 should do.

    This will need rebuilding the driverlib .lib using the CCS project provided in the package.

    But if they want to use the lib then they would need all the 3 libs.

    With the latest version of package we are providing support for both EABI and coff style of object driver library.

    These 2 driverlibs are being indexed using the driverlib.lib to map to the right driverlib based on the proj properties in an example .

    ie. if there is abi= eabi in the example proj properties then the driverlib.lib referenced will be mapped to driverlib_eabi .

    Please check the Driverlib_F2837x_to_F2838x_Migration_Guide.pdf on C2000Ware_2_00_00_02\device_support\f2838x\docs for more detail.

    Regards.

    Regards.