cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 4 MCU

johac_3222466
New Contributor

Hello,

Our product uses a CY8C4127LQI-BL473 for Bluetooth.  Our manufacturing line uses a Segger JLink to ensure that the latest version of product firmware is installed in the chip.  We just released a new version of the firmware, and have discovered that the JLink does not appear to handle the chip protection correctly.  The new version of firmware comes with the chip protection in the "Protected" state.  The JLink is unable to connect to the chip, and therefore cannot even allow a simple checksum operation.  Also, this revealed that the JLink does not successfully write the chip protection if an unlocked chip is presented to the JLink.

I found several older threads loosely related to this on both the Cypress and Segger websites, but which appeared to address the HEX file contents more than the actual chip protection interactions.  The closest I have come to locating a solution is the following page on the Segger wiki site:

https://wiki.segger.com/PSoC_4xxx_series_readout_protection#Unsecuring_device_before_reprogramming

When we use the JLink to perform the Exit steps after programming listed in this article, the sequence appears to execute properly, but the chip remains unlocked.

Is there a way to get the JLink to correctly lock and unlock the CY8C4127LQI-BL473? 

We are using a 5-wire SWD interface for all programming connections.  We used the MiniProg3 for development, and to confirm that the issue is isolated to the way JLink handles the chip protection.

Thank you and best regards,

Joel

0 Likes
1 Solution
AnkitaS_51
Employee

Hi Joel,

I can mention how  chip protection is done for PSoCs by certain register writes.Write Protection system call is explained under topic "Performing System call" at page#336 in this doc:

https://www.cypress.com/file/137266/download

I am not sure why JLINK is unable to secure the device which consists of multiple read / write accesses to special function registers of the CY8C4xxx and CYBLExxxx series devices when it mentions that it can do so.

I think you need to contact Segger for this.

Thanks,

Ankita

View solution in original post

0 Likes
1 Reply
AnkitaS_51
Employee

Hi Joel,

I can mention how  chip protection is done for PSoCs by certain register writes.Write Protection system call is explained under topic "Performing System call" at page#336 in this doc:

https://www.cypress.com/file/137266/download

I am not sure why JLINK is unable to secure the device which consists of multiple read / write accesses to special function registers of the CY8C4xxx and CYBLExxxx series devices when it mentions that it can do so.

I think you need to contact Segger for this.

Thanks,

Ankita

View solution in original post

0 Likes