• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 606 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/TMS320F280048: F280048 Support in Latest CCS v8.3.0.00009

Ricky Zhang
Genius 9520 points

Part Number: TMS320F280048

Tool/software: Code Composer Studio

Hi, Champs,

My customer is using F280048 and he found the latest CCS v8.3.0.00009 can not support this device.

I asked him to try updating C2000 device support package but it indicated no updates.

He is now choosing F280049 for debugging but has some issues on reading ADC results in debug mode.

Please advise how should we fix this issue.

Best Regards,

Ricky Zhang

  • 0
    TI__Guru* 85670 points
    Ricky,
    I will look into the missing F280048 line item, in terms the selection of F280049 it should work for the F280048 device. The only difference is that GPIO12/13 are not on the F280048 to support Q grade temp in the 64 pin package. I would use the F280049 PN and not the F280049M device, however, as the "M" device is no longer being produced.

    Can you describe more on the ADC result issue in debug mode? Is the conversion incorrect/high error, or some other issue?
    Matt
  • 0 in reply to MatthewPate
    TI__Genius 9520 points

    Matt,

    Thanks for your quick response.

    Customer is now choosing F280049 for debugging and they told the ADC issue of not updating as expected in the view is fixed - I'm also doubting what the issue is and trying to get more details.

    Btw, when can we confirm why v8.3.0 missed F280048 or if we need to add a patch or update the device support package?

    Best Regards,

    Ricky Zhang 

  • 0 in reply to Ricky Zhang
    TI__Guru* 85670 points
    Ricky,
    I looked and I beleive they have been missing in 8.2.0 as well and I filed a bug report for that release. I have escalated the bug request since it was missed for 8.3.0. I beleive the next official release is sometime in Jan, this should get fixed worst case then.

    Matt
  • 0 in reply to MatthewPate
    TI__Genius 9520 points

    Matt,

    Okay, thanks for your confirmation and escalation. I will let customer know the update.

    Best Regards,

    Ricky Zhang