• Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 714 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.

Different Chip ID between TMX320F28335 and TMS320F28335?

Randy Wu
Expert 3690 points


Hi Champs,

A customer is trying to program (via Signum Systems JTAGjet emulator) the production version of the F28335 and they claim that these newer devices contain a different Chip ID than the TMX versions of the F28335 that they had been using for prototyping.  I believe they are using the Signum Systems PC Flash Programmer Utility that works with the JTAGjet (but I still need to confirm this).  Can someone please confirm if having a different Chip ID in the TMS versions would cause a problem, and how the customer should proceed?  Is this something that Signum Systems needs to fix with their PC-based flash programmer utility?  Is there anything the customer can do?

Thanks,

-Randy

 

 

  • TI__Guru 61235 points

    Randy,

    The TMS device is rev.A silicon.  I think it will have the same device ID, but the rev ID will be different.  The flash API algorithms were updated to work with the rev.A silicon.  Your customer should check with Signum to see if they've updated their utility, or when they plan to do so.

    The CCS C2000 flash plugin has been updated, and will work with the rev.A silicon.  This was done some time ago.

    - David

  • in reply to David M. Alter
    TI__Expert 8500 points

    Randy/David,

    The revA TMS silicon does have a different chip ID than the rev0 TMX silicon. For manufacturing reasons we changed our philosophy. The old PARTID register (address 0x882) is now called the CLASSID register. The PARTID is now found at address 0x380090. See section 3.4 in the device datasheet. As David mentioned, the API was updated to reflect this.

    Regards,
    Dave Foley