• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 97 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.

TMS320F28377D: CCS v7.2.0.00013 vs. CCS v9.1.0.00010 Debugging on TMS320F28377D and TMS320F28379D

Mario Ambühl
Prodigy 40 points

Part Number: TMS320F28377D
Other Parts Discussed in Thread: TMS320F28379D, , C2000WARE

Hello support

I'm currently porting software from a TMS320F28379D to a TMS320F28377D. I'm using CCS v7.2.0.00013 for this.

I'm able to debug on the TMS320F28379D using CCS v7.2.0.00013. However, I'm not able to debug on the TMS320F28377D using CCS v7.2.0.00013. I'm using the exact same output file. To debug on the TMS320F28377D, I need to use CCS v9.1.0.00010.

Error message from TMS320F28377D and CCS v7.2.0.00013:

C28xx_CPU1: File Loader: Verification failed: Values at address 0x88000@Program do not match Please verify target memory and memory map.

But if I use a sample file from C2000Ware, I can debug on both microcontrollers using CCS v7.2.0.00013.

Furthermore, I switched back to CCS v7.2.0.00013 but now I'm able to debug my own software with CCS v7.2.0.00013.

It is not my intension to continoue using old CCS versions. My intension is to understand what's causing the issue and whether I still have an issue somewhere. May you know the cause?

Thank you in advance for your support.

  • +1
    TI__Intellectual 2280 points

    Hi Mario ,
    Your verification failure at address 0x88000 with CCS v7.2.0.00013 on the TMS320F28377D is a known CCS Flash plugin incompatibility with newer silicon revisions of the TMS320F2837x family. This is not a problem with your software it's a toolchain issue.

    CCS v7.2.0 contains an outdated Flash plugin that cannot correctly program these newer device revisions, causing the verification failure after the write operation

    We recommend you,  shift to new version of CCS

  • 0 in reply to Lakshya Verma
    Prodigy 40 points

    Hi Lakshya

    Thank you so much for your answer. That's exactly what I wanted to know.