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.
We are developing UDS CAN bootloader for firmware upgradation. In that, I am developing flash handlers for read and write.
I was modifying the example code , for checking erase and write for flash, but after some point of time , I observed below error. And now I am not able to program anything to that board.
Do you know how to come out of this error?
Hello Vamsi,
I did not touch the DCSM OTP.
I was just modifying the flash example code, and trying to test erase and write for flash.
How to know, that DCSM is getting accessed via code?
also , I do not know the password, do you have any other way to come out of this issue?
Hi Yogini,
I will remind our security expert to help you.
Thanks and regards,
Vamsi
Hi Yogini,
I checked now and our security expert is not available this week. I will guide you further.
Please check the table Figure 3-15. Location of Zone-Select Block Based on Link-Pointer for Bank0 in the TRM and you would notice the ZxOTP_CSMPSWD0, ZxOTP_CSMPSWD1, ZxOTP_CSMPSWD2, ZxOTP_CSMPSWD3.
Please check those locations in the debugger memory window. You can copy those values in to the CCS flash plugin GUI's password locations and click on unlock.
Thanks and regards,
Vamsi
Ok Yogini. I will keep this thread in pause until you come back.
Thanks and regards,
Vamsi
Hello Vamsi,
I verified the passwords at their memory locations , nothing is overwritten there. Also , i entered the same in GUI for unlocking, but I still see the error.
Hi Yogini,
As discussed offline, the device is permanently locked due to all 0s password.
You might have programmed all 0s by mistake either by GUI or from the application image - please check your application's map file to see what is mapped to those locations.
I will assign this to our security expert to help you further since I will out of office for this week.
Thanks and regards,
Vamsi
hi Vamsi,
ohh, is there anything that we should take care to avoid writing these registers which locks the boards permanently?
Yogini,
Vamsi is out of office until Tuesday. Please expect response by Tuesday.
Thanks & Regards,
Santosh
Hi Yogini,
Sorry for the delay in my reply. This is assigned to me today.
1. Always check your linker command file and map file to see if anything is mapped to DCSM OTP area unintentionally.
2. Check the password fields in the flash programming tool to make sure they are as intended.
3. If you are using the flash API to program the OTP and flash, make sure the application is not programming unintended data to DCSM OTP area.
Thanks and regards,
Vamsi