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.

TMS320F28069:

Part Number: TMS320F28069

Requesting for a certificate of volatility for this microcontroller part (TMS320F28069PZPS), attached datasheet for your reference.

tms320f28069.pd.pdf

  • Hi Ben,

    This isn't a document we have readily available. I will get back to you on this next week.

    Thanks,

    Kevin

  • Hi Kevin,

    Just want to follow up if we have any more updates on getting the COV for this part?

    Thanks,

    Ben Wang

  • Hi Ben,

    Sorry for the delay. Still working internally to get more info on the document. Will let you know when I have more information to provide.

    COV's are not something our team has provided in the past.

    Best,

    Kevin

  • Ben,

    I'm working internally to understand how we best communicate this, either in an explicit note in the DS or a seperate document. As Kevin mentioned previously this is not a document we have seen a request for until now.

    At any rate, in terms of how the device behaves, I would say that all Flash, OTP,  and ROM memory are non-volatile for the operating life of the device and the on-chip SRAMs will hold their data while the device is operating within the voltage tolerances listed in the datasheet here: http://www.ti.com/document-viewer/TMS320F28069/datasheet/recommended-operating-conditions-tsprs698-83120041015401-picb#tsprs698_83120041015401_PICB.

    Let me know if you have further questions.

    Best,

    Matthew

  • Hi Matthew,

    Thank you for the information, we would like to request a letter for the Certificate of Volatility from TI for our sanitization record. This document contains information about all the memories on this part, and recommended methods for sanitizing/clearing the non volatile memory content. Let me know if you have additional questions.

    Thanks

    Ben Wang

  • Ben,

    I appreciate the additional information here, it will help me resolve this correctly.

    Is there any 3rd party/global type specification that you or your customer is looking to meet in the system that might help me understand the expectation from TI in our communication?

    Assuming the device is to be re-used, I would just recommend erasing the main array, which will put everything back to 0xFFFF type state.  OTP would be a different matter, since it is one time programmable the only way to "delete" the information would be to program all bits to 0, but then the OTP would not be usuable again.

    Any thoughts here are appreciated.  

    Best,
    Matthew

  • Hi Matthew,

    We don't have any specifications required for the letter, as long as the letter provide sufficient details on the procedures/steps to clear these memory components would be adequate, the more details the better.

    Thanks,

    Ben Wang

  • Ben,

    I've been able to make some progress on this internally, I believe I should have something to share by the end of next week based on what I know now.  If that changes in any way I'll let you know, else I think we can plan on having this letter by then.

    Best,
    Matthew

  • Ben,

    Apologies for the last minute update, I'm waiting on one more approval/review on this document and I should be able to share once that happens.  In the meantime, if you can confirm that the email address associated with your my.ti account is correct; that is what I will use to share the statement of volatility once I have approval.

    Best,

    Matthew

  • Ben,

    I went ahead and share the document with you via box.com cloud share that TI uses to share documents externally.  I used the email you have on file, I'm going to mark this thread as TI thinks resolved.  If you don't see the file or have further questions on this topic, feel free to reply back and the system will notify me.

    Best,

    Matthew

  • Hi Matthew,

    The company firewall blocks me from viewing the document you shared, would you be able to attach that to this thread?

    Thanks,

    BinHua Wang

  • Ben,

    Thanks for letting me know.  I'm going to reach out to you using the E2E chat function.  We can share a file that way as well.  I'll need to send you a friend request, once you accept I'll send the file.

    Best,

    Matthew