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.
HOW TO UNLOCK THE FLASH OF TMS320F28067 USING CODE COMPOSER STUDIO OR UNIFLASH, ACTUALY MY FLASH HAS LOCKED DUE TO THIS I AM UNABLE TO PROGRAM MY CONTROLLER.
IF POSSIBLE KINDLY PROVIDE THE HELP THROUGH PHONE ALSO.
MOB NO: 8800127355
Hi Devershi,
Some questions:
1) Was the device locked through CCS/Uniflash On-Chip Flash tool first? If so, do you believe that the default values were used to lock the device?
2) Was a project used to load the security settings to the device? And if so can you provide the memory map used?
3) Can you please describe the error message when trying to unlock the controller?
More information about the CSM (Section 1.2 of the TRM, ti.com/lit/ug/spruh18i/spruh18i.pdf)
Thanks and regards,
Charles
Sir it happen through UNIFLASH when i was trying to Erase the All Sector of Memory my be due to my mistake controller has locked.
if any Solution is available kindly Suggest me Sir.
Devershi,
If the device was locked by accident, did you try pressing the "unlock" button when you were in Uniflash? The default values are seen as 0xFFFF. Or was the device locked outside the default values?
The flash programming procedure using CCS Studio is as follows:
1) Connect the device to CCS through the generated target configuration
2) Build the project and compile to generate the .out file
3) Load the .out file to the device using the load function of CCS (found in Debug mode)
As the F2806x is an F05 Flash device, here is also a reference to the FAQ guide:
Thanks and regards,
Charles
Hi Devershi,
To clarify, did you attempt to program CSM passwords? If so, are you entering these passwords in Uniflash when you attempt to press the "Unlock" button? Can you share the error message you get when trying to unlock? Is it possible the device was reset during a flash erase operation? This can potentially program unintended 0s in the password locations.
Thank you,
Luke