• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 278 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.

C6201 Rev. 2 to C6201 Rev. 3 silicon... require recompile?

Jim Chase
Prodigy 75 points

The migration guide does not stipulate a recompile.  However, does the memory modification potentially cause an issue with binary compatibility?

This is a resurrection of a very old design and it is not feasible to do a recompile.  However, it is expensive to roll the CCA and it is imperative that there is 100% confidence in the binary compatibility between the two device revisions.

  • 0
    TI__Guru* 84110 points

    The datasheets and errata documents are the legal descriptions of the features and capabilities of the devices. We make great efforts to ensure that these documents are complete and robust and accurate.

    TI cannot warrant any device to a specific customer application above or beyond the contents of these documents. If you have other resources available for considering this question, please let us know what result you get.

  • 0 in reply to RandyP
    TI__Guru*** 125430 points

    The memory map did not change, just the internal structure.  The new structure will reduce the number of stalls which will modestly improve performance (mileage may vary).

    I think if you start throwing out terms like "100% guarantee" that everyone is going to run for cover as that sounds like a legal trap.  The code should not need a recompile because of the internal memory change, but if the customer's code has something crazy in it where the (modestly) improved performance causes their code to function different then there could be issues.  So I don't think you're going to see any guarantees from TI that the customer's code will work flawlessly.  All TI can guarantee is that our device will perform to our specifications, basically what Randy said.

    Note there are also errata that have been fixed as discussed in the errata manual.  For example it also mentions a change to the "hold" feature in the EMIF.  Those are all things the customer should consider.  TI cannot guarantee to this customer that their code will work flawlessly.  That will depend on how they have written their code.  As far as I can tell it looks like they stand a good chance of moving their code to the new revision very smoothly, but I won't guarantee it 100%.