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.

[FAQ] Product Change Notice (PCN) 20180523001.1 and PCN 20200115000.2 for TMS320F2837x and TMS320F2807x devices

Other Parts Discussed in Thread: C2000WARE, UNIFLASH, TMS320F28379D


Question: How does PCN 20180523001.1 and PCN 20200115000.2 affect TI Flash programming tools, 3rd party programming tools and customer applications?  


  • TI notified all the relevant customers that TMS320F2837x and TMS320F2807x devices moving forward may use "F65 process" flash to replace "F021 process" flash. Below are the frequently asked questions related to this:

    If you have further questions, please post via the "ask a related thread" button.

    Q) Do we need to use a new Flash API library?

    A) There is no change to the Flash API library. Users can continue to use the same Flash API library (F021_API_F2837xD_FPU32.lib) provided in C2000Ware at C2000Ware_x_xx_xx_xx\libraries\flash_api\f2837xd\lib. This library works for both F65 and F021 processed devices.

    Q) Do we need to update Code Composer Studio (CCS)?

    A) If you use a version of CCS prior to CCSv7.4, you need to update to CCSv7.4 or higher (we recommend CCSv8.3.1 for 32-bit Windows systems and CCSv9.x or higher for 64-bit Windows systems). Once you update to CCSv7.4 or higher, you must check for updates in CCS for below packages and install them (use ‘Help -> Check for Updates’ in CCS and install following):

         i) TI C2000 Device Support: Requires version or greater

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

         iii) Debug Server: Requires version or greater

    Note: Some CCS versions higher than CCSv7.4 may have the latest updates by default for one or more of the above packages, and hence updates may not  show up. Once you update your CCS and install above packages, CCS On-chip Flash Plugin will work for both F65 and F021 processed devices.

    Q) Do we need to update UniFlash?

    A) If you use a version of UniFlash prior to UniFlash v4.6, you need to update to UniFlash v4.6 (for 32-bit windows) or UniFlashV5.1 or higher (for 64-bit windows).

         Note that UniFlashV5.X does not work with 32-bit windows systems.     

         Once you update your UniFlash, it will work for both F65 and F021 processed devices.

    Note: If the boot mode pins are configured for flash boot (instead of the wait-boot), CPU may fetch invalid opcodes from the erased flash (before the emulator gets connected) and this results in ITRAPs/reset.  This may prevent Uniflash from doing flash operations successfully.  Hence, please follow below sequence before initiating any flash operations:

    After the emulator connection is established with the device (Target connect) -> Issue a debugger Reset -> Issue a Free run to let BootROM complete its initialization (resume button) -> Halt after 100ms (by this time, device will be in a known initialized state) -> Proceed with flash operations.            

    You can see above steps implemented in the example DSS script package ( attached to this post.

    Q) PCN says that PARTIDH register will have a new value in the F65 processed devices. Can you explain in detail?

    A) The value of DEVICE_CLASS_ID bit-field (eight most significant bits of PARTIDH register) can be either 0x00 or 0x02. Devices that customers receive in the near future from TI can be a mix of these two valid values. For example, TMS320F28379D device’s PARTIDH register value can be either 0x00F90300 or 0x02F90300. In Device TRM, TI mentioned that the DEVICE_CLASS_ID is a reserved bit-field, suggesting users to not use those bits. Hence, TI expects that the user applications or Flash tools to not use these bits. Hope you are not using them. In case if you are using these bits currently in your application or tools, you need to update them to not use these bits.

    Q) We are using a 3rd party Flash programming tool. Do we need to contact the 3rd party tool supplier regarding this PCN?

    A) Contact them and make sure:
         i) The tool is not using DEVICE_CLASS_ID bit-field in PARTIDH register (see #4 above)
         ii) The tool adheres to errata document in general (pay special attention to PLL and Flash advisories)

    Q) Is there any other info that we need to be aware of?

    A) Flash specifications (like program time, erase time, endurance etc.) in Datasheet does not change with this PCN.

        In general, always, make sure to review device errata and align your application accordingly.

        In general, when possible, always check for updates in CCS or UniFlash to get the latest bug fixes and enhancements, if any.

    Q) Does CCS or UniFlash print any error or warning when it is not updated as per the above suggestion?

    A) When you try to do Flash operations on F65 processed device without the above suggested updates, CCS/UniFlash may display an error saying that the "Target is not connected or does not support current Flash operation.” or "The controller is either not connected or this operation is not allowed.".  However, please note that these errors can occur for other reasons as well. 


    Q) Are there any changes in the device silk screen due to this PCN?

    A) Yes. The Wafer Fab code ('$$' in below image) on the devices used to be ' YF '. Moving forward, it can be ' YF ' or ' $7 ' or '$4 '.


    Vamsi Gudivada

    C2000 System SW Engineer

  • Thanks Vamsi!