• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 442 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/TMS320F28377D: Unable to program new device

Richard Day1
Intellectual 265 points

Part Number: TMS320F28377D
Other Parts Discussed in Thread: UNIFLASH,

Tool/software: Code Composer Studio

Hi,

We have been using CCS version 8.1 for a number of years and have used it over several issues of a proprietary board using a TMS320F28377D with an XDS200 emulator.  With the latest issue of this board however, CCS fails to program the device.  Note that both CCS version 9.1 and Uniflash version 5 work correctly with the new board.  However, we are reluctant to change to using CCS 9.1 as we will no longer be able to use XDS510 emulators of which we have several.

Using the same project that works without issue on previous issues of the board, CCS 8.1 completely fails to program the device on the new issue of the board.  The error messages that were output for the new board are:

C28xx_CPU1: Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.
C28xx_CPU1: File Loader: Verification failed: Values at address 0xBD5EC@Program do not match Please verify target memory and memory map.
C28xx_CPU1: GEL: File: xxxxx.out: a data verification error occurred, file load failed.

By 'one or more' I suspect that CCS believes all sections are not in writable memory because there appears to be no attempt to program flash at all.

I used CCS's verbose logging feature and ran tests on old and new boards to attempt to find the issue. I did identify an difference which I believe explains the problem but I would like further explanation.  The relevant bits of the log file for old and new boards are:


Old board 1 (works):
 FLASH I: FlashC2000F021 Constructor - Device ID: 0x00771553
 FLASH I: FlashC2000F021 Constructor - Part Revision: 0x00000003
 FLASH I: FlashC2000F021 Constructor - Config File: F2837xD.CPU1.xml

Old board 2 (works):
 FLASH I: FlashC2000F021 Constructor - Device ID: 0x00771553
 FLASH I: FlashC2000F021 Constructor - Part Revision: 0x00000003
 FLASH I: FlashC2000F021 Constructor - Config File: F2837xD.CPU1.xml

New board 1 (does not work):
 FLASH I: FlashC2000F021 Constructor - Device ID: 0x00771820
 FLASH I: FlashC2000F021 Constructor - Part Revision: 0x00000003
 FLASH I: FlashC2000F021 Constructor - Config File:

New board 2 (does not work):
 FLASH I: FlashC2000F021 Constructor - Device ID: 0x00771820
 FLASH I: FlashC2000F021 Constructor - Part Revision: 0x00000003
 FLASH I: FlashC2000F021 Constructor - Config File:

On the two old boards (which CCS works okay with) there is a valid 'config file'  found whereas on the two new boards (which CCS does not work with) there is no config file.  The difference seems to be the reported 'Device ID'.

This device ID is NOT the same as the published device ID (found by reading 0x0005D00A (PARTIDH)).  Note that the published device ID's of both devices are identical, as is the silicon revision (noted above).

My conclusion was that the device ID reported by the device is not known by CCS 8.1 (but is known by CCS 9.1 and Uniflash) and therefore CCS is not aware of the flash on the device and assumes there is no flash.

My questions are:

  1. Is this the correct cause of the programming issue?
  2. What does this device ID represent?
  3. Why has the device ID changed?
  4. Will some future device ID change mean that CCS 9.1 and/or Uniflash will no longer program new devices?

Thanks,

Richard.

  • 0
    TI__Guru* 87155 points

    Richard,

    Please take a look at https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/729543?-FAQ-Product-Change-Notice-PCN-20180523001-1-for-TMS320F2837x-and-TMS320F2807x-devices

    Could you check whether your CCS installation has below packages or not?  

         i) TI C2000 Device Support: Requires version 4.2.5.0 or greater

         ii) CCS Flash Content (sometimes this package is named as “Debug Server Flash”): Requires version 8.1.0.1297 or greater

         iii) Debug Server: Requires version 7.4.0.1313 or greater

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Hi Vamsi,

    I've read the referenced forum post and it doesn't really answer any of my questions I'm afraid.  I presume that PCN 20180523001.1 is relevant, do you have a link to the PCN itself?

    I note that the forum post mentions that the wafer fab part code has changed, what does this mean in terms of the processor itself?  What has changed in the processor?

    As for the various versions, can you please explain what requires those versions?  Are you saying the 'new' part requires those versions?

    Thanks,

    Richard.

  • 0 in reply to Richard Day1
    TI__Guru* 87155 points

    Richard,

    Looking at the log details that you copied, I am sure the issue is related to the PCN.

    I can not attach PCN on the E2E forum.  I sent you a friend request.  Please accept it.  Let me know once you accept it; I can send you the PCN offline.

    There is no any change in the processor functionality.  It is just that the devices are manufactured in a different fab process and hence is the change in the Device ID that you see in the log (and this is not a documented ID for users. It is for TI-internal use and hence you can ignore that).  This Device ID is not the PARTIDH.  

    As you can see in the FAQ E2E that I shared with you, the new fab devices have a new PARTIDH value.

    Please update the tools so that they can identify the new device as a valid device and allow Flash operations.

    There are no further ID changes apart from this.

    Please check for updates in CCS and install the packages that I mentioned above. It should resolve the issue. If not, please let me know and we will be able to help you.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Thanks Vamsi, that's very useful information!

    We weren't aware of this change so were a bit surprised/concerned when we were unable to program the devices but it makes sense now.  I will be following up internally within my company to find out why we weren't notified of the change.

    Thanks,

    Richard.

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Hi Vamsi,

    Just a further note on this, I checked with our SCM and although they received the PCN, it wasn't clear that the part had changed and that the consequence would be incompatibility with existing tools.

    As I've still not got access to the PCN itself, I cannot ascertain whether, had I seen it, whether I would have realised the consequences either!

    Thanks,

    Richard.

  • 0 in reply to Richard Day1
    TI__Guru* 87155 points

    Richard,

    Thank you for the update. 

    Once you receive the PCN from your SCM, please let us know if you have further questions.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Apologies, a bit of confusion: I didn't ask our SCM to send me the PCN, I was hoping you would.

    Could you send me the PCN, I'm not sure whether our SCM still has it?

    Thanks,

    Richard.

  • 0 in reply to Richard Day1
    TI__Guru* 87155 points

    Richard,

    Got it. No problem. I will send it to you.  Let me look in to the procedure.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Guru* 87155 points

    Richard,

    I sent it to you via E2E private message.

    Please acknowledge once you receive it.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Hi Vamsi,

    Thanks for the PCN, I have read it and it claims that CCS 8.1 works with the device whereas we have found that CCS 8.1 does NOT work with the updated device.  I have since found that CCS 8.3 works correctly with the device so that is our solution going forward.

    Had we received this PCN we would not have thought to update CCS from the information in it.  It seems that the PCN is either not the cause of the issue or the information in the PCN is incorrect.

    Thanks,

    Richard.

  • 0 in reply to Richard Day1
    TI__Guru* 87155 points

    Richard,

    Glad that you can use CCSv8.3 moving forward.

    Thank you for the feedback.  I sent your feedback to the PCN team.

    CCSv8.1 was tested to work for this PCN.  Not sure why it is not working for you now.  I will raise a ticket internally to check if anything changed in between.  

    I am closing this ticket since you are able to program fine now.

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Hi Vamsi,

    Thank you for the response, I agree that closing this ticket is the right thing to do and separately trying to find out whether/why CCS 8.1 is still an issue.

    Thanks,

    Richard.