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.
Below are a few different things that you can try to improve the flashing performance when using TI's CCS On-chip Flash Plugin or UniFlash.
a. Use a faster emulator like XDS200. Performance of this emulator is comparable to that of XDS510, but it is cheaper.
b. There is no need to erase the entire Flash bank every time a flash program operation is initiated. In the On-Chip Flash Plugin GUI, user can choose the option "Necessary Sectors Only (for Program Load)" under Erase settings. This will erase only the sectors that are supposed to be reprogrammed (based on their linker cmd file). However, if any un-erased locations exist in other sectors that are not erased, application can not use those locations at run-time. Also, the checksum of the bank might not meet the expected value.
c. If this is a production environment, you can choose “Program Only” option as units come erased from TI.
d. You can un-check "Verify Flash after Program" under Download Settings. Please note that verify of the image will not be done after the program operation when you choose this. You can use checksum option in Plugin after the program operation to verify the authenticity of the image, if it is acceptable for you. Note that the checksum operation may need you to unlock the device if a reset is issued between the program and checksum initiation.
e. If the application has multiple sections in the linker cmd file, you can try enabling "Combine Sections during Program Load to increase Performance" under Performance Settings. If there are not many sections, this is not suggested. When this feature is used, multiple sections in the executable will be combined together and programmed at once - While doing this, all the holes in between the sections will be filled with all 1s data and ECC also gets programmed for this all 1s data. Hence, those all 1s locations can not be used at application runtime if needed.
f. You can disable blank check after erase. If you choose this option, tools will not check whether the erase operation erased all the bits or not. Hence, if a bit is not erased properly, the program operation will fail when a 0->1 transition happens as part of the program operation.
Thanks and regards,
Thank you for the tips.
C2000 Microcontroller Applications, Texas Instruments, Houston.
If my reply answered your question, please click the “This resolved my issue” button.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.