LAUNCHXL-F280049C: After programming Z1OTP-PSWDLOCK programming doesn't work any more.

Are you reading the passwords values from OTP in your application?

Vivek Singh

No, the application doesn't unlock or read any values from the OTP.

That is very strange. PSWDLOCK only impact the visibility of password values and should not have any impact on application if you have not programmed any other setting. Have you program any other security settings?  Also after connecting to CCS, can you check the value in flash locations and see if you are able to read it ?

Regards,

Vivek Singh

I did a load image and a verify image. And both are successful in uniflash.

This are the registers now: I updated the linkpointer. But the board still don't work.

I removed the password by updating B0-Z1OTP-LINKPOINTERx

But I can't still program with CCS?

IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)

Can you change the password value in GUI field for "Z2OTP-CSMPSWD1" to "0xf1ffffff" (default password) instead of "0xe3ffffff" and then try.

Also which CCS version you are trying ? We had some issue in CCS9.3 which may cause issue in programming device. If using 9.3 then try CCS9.2 and see if that fixes the issue.

Regards,

Vivek Singh

In which zone are the peripherals? Can read/writing them be a problem?  When my program is in zone1 in locked mode. And Z1OTP-PSWDLOCK is also locked?

thanks

Vivek Singh said:

Can you change the password value in GUI field for "Z2OTP-CSMPSWD1" to "0xf1ffffff" (default password) instead of "0xe3ffffff" and then try.

Also which CCS version you are trying ? We had some issue in CCS9.3 which may cause issue in programming device. If using 9.3 then try CCS9.2 and see if that fixes the issue.

Regards,

Vivek Singh

Remove 9.3

installed 9.2

Verified that it works correctly.

Set default password for Z1OTP-CSMPSWDx (0x4BFFFFFF)

Set default password for Z2OTP-CSMPSWDx (0xE3FFFFFF)

C28xx_CPU1: Warning: Failed unlocking device (zone 1) after reset.
C28xx_CPU1: Warning: Failed unlocking device (zone 2) after reset.
C28xx_CPU1: Flash Programmer: Error erasing Sector 0. FMSTAT value = 1040. Operation Cancelled (0).
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\Users\spronse\Documents\GIT\Cremer_Bootloader\LAUNCHXL-280049-Debug\Cremer_Bootloader.out: Load failed.

Hi,

installed 9.2

Verified that it works correctly.

Please continue working with CCS9.2. We will have CCS10 released soon which will have this fix and also a patch will be available for CCS9.3 if someone wants to continue using CCS9.3. Sorry that this issue caused you lot's of debug.

Regards,

Vivek Singh

NONO!! This didn't solve my problem with Z1OTP-PSWDLOCK!!!!!

I checked if the installation was correct and debug my code works correctly.

Edit: This bricks my device and I can't find any reason why.

I understand. To debug that I would suggest that you unlock the ECSL by providing matching password for 64bit only (ECSL Unlock) and then step through the code and see where it fails.

Regards,

Vivek Singh

I have 2 a launchXL-280049 and run 9.2

Both has there Z1OTP-PSWDLOCK programmed and both don't run any code in standalone mode

First one is not locked.

 This works fine when I run the code in CCS debug mode. but won't run standalone. I can't find any reason why

The other one is unlocked with: B0-Z1OTP-LINKPOINTERx = 0x1FFFFFFC

 programming with uniflash works.

 with B0-Z1OTP-LINKPOINTERx = 0x1FFFFFFC and Z1OTP-CSMPSWD1 = 0x 4BFFFFFF. CCS debug Fails and I doubt that this works in the first place.

 And also this doesn't work standalone.

For now I can't continue. Because both are bricked. Hopefully Monday I receive new boards and I can try again.

 I'm planning to try this:

 Z1OTP-PSWDLOCK = FB7FFF0F maybe this make a difference(who knows).  The documentation is not very clear and protection where you can read the password very ease is not very useful.

Hi,

This works fine when I run the code in CCS debug mode. but won't run standalone. I can't find any reason why

When you say it worked in debug mode, do you mean unlocked or locked? If it works in debug mode with security enable then device is not having any issue. Right?

with B0-Z1OTP-LINKPOINTERx = 0x1FFFFFFC and Z1OTP-CSMPSWD1 = 0x 4BFFFFFF. CCS debug Fails and I doubt that this works in the first place.

This does not work even with CCS9.2?

Z1OTP-PSWDLOCK = FB7FFF0F maybe this make a difference(who knows).  The documentation is not very clear and protection where you can read the password very ease is not very useful.

You have to program FB7FFFF0 only to lock the password. I did not understand your comment "and protection where you can read the password very ease is not very useful". Can you elaborate it a bit more.

Regards,

Vivek Singh

Hi Vivek,

- I'm working with a fresh version of CCS9.2

What I did:

 I programmed in a new LAUNCHXL-280049 the OTP register: Z1OTP-PSWDLOCK = FB7FFFF0.  nothing more so unlocked. This bricks the device!

 I can't get it working in standalone mode any more. Only when I use CCS debug the application runs fine.  So it seems that programming Z1OTP-PSWDLOCK also affect the bootmode start option. But I can't find any reason why? Suggestions.

I don't understand that Z1OTP-PSWDLOCK exits in the first place. One more option to make a really costly potential error.

Hi,

Thank you for the detail. I was able to create this issue (PSWDLOCK related)  here and we are looking into this further.

Regards,

Vivek Singh

Vivek Singh said:

Hi,

Thank you for the detail. I was able to create this issue (PSWDLOCK related)  here and we are looking into this further.

Regards,

Vivek Singh

Any news?

Hi,

Yes, we have found issue with the tool. It is programming incorrect ECC for that field hence you are seeing this issue. We are working on CCS  patch to fix this issue.

Regards,

Vivek Singh

Vivek,

When will the updated software be available?

Thank,

Hi,

Patch is available for CCS9.3. Please click on "Check for update" under Help and down load the patch. This should fix the issue.

Regards,

Vivek Singh

Ok, Is there also a new version of uniflash for programming the Z1OTP-PSWDLOCK lock?

Thanks

I started this problem on 12 febr. And I have to wait to the end of April. So I can continue complementing this(I may hope)

why is this not working in the first place? Writing configure registers is basis functionality. So why is this not properly tested.

Does TI care that much about there products That the customer is the tester engineer and needs to hope for the best to get thing working. This is not to first time a come across a problem see my post record. I spend so much time debugging similar issues.

How can I design a product as the TI building blocks I'm using aren't reliable.  What do you expect me so say to my supervisor(and customer) that product development is delayed because TI software didn't work properly and the decision to use TI products in our next project.

Hi,

We understand your concern and our sincere apology for the inconvenience it has caused. We have already provided the CCS patch to fix this issue and work in progress on patch for Uniflash. Please note that this is issue with GUI option. On this device we do not have USER OTP values default as 0xFFFFFFFF and while programming the ECC value for PSWDLOCK field this was not taken care hence ECC value is getting program incorrectly. Since the actual value is programmed correctly and running it with debugger connected does not show the issue, it got missed during tool validation. I hope you can continue your development with CCS.

Regards,

Vivek Singh