2 Replies Latest reply on Aug 9, 2018 1:42 AM by anks

Code protection with Segger programmer

francesco.gambini_2441671 Jul 27, 2018 5:14 AM

Hi,

in our project we are using the micro CY8C4024LQI-S411 (4000S Family).

In our production line we use the Segger Flash programmer.

We would like to protect the code from reading after programming.

We know that this is possible following these steps:

1 - In PSoc Creator setting "Chip Protection" to Protected

2- In PSoc Programmer checking the "Enable" flag of "Programmer Options"

Is it possible to do the same using the Segger Flash Programmer (Jlink Software)?

Is there a specific register in PSoc4 - 4000S that should be set?

Thank you very much for your help

Francesco

1. Re: Code protection with Segger programmer

anks Jul 29, 2018 9:12 PM (in response to francesco.gambini_2441671)

The last type of nonvolatile information in flash is chip-level protection. This consists of one byte that restricts access to the chip’s resources (register, SRAM, and flash) by an external programmer or debugger.
Please check page# 7-8 and #43 of this doc:
http://www.cypress.com/file/409516/download
Like Show 0 Likes(0)

Actions
2. Re: Code protection with Segger programmer

anks Aug 9, 2018 1:42 AM (in response to francesco.gambini_2441671)

Nonvolatile memory programming refers to the programming of flash memory in the PSoC® 4 device. This chapter explains the different functions that are part of device programming, such as erase, write, program, and checksum calculation.Cypress-supplied programmers and other third-party programmers can use these functions to program the PSoC 4 device with the data in an application hex file.

Please check this discussion , it discusses the limitation of Jlink to program hex file generated by PSoC Creator:
[SOLVED] J-Flash Error: Program does not fit into selected flash sectors - J-Link/Flasher related - SEGGER - Forum

J-Flash should only be used with data files that solely contain (programmable) flash addresses.
This limitation comes because Jlink can't program Nonvolatile memory in the PSoC® 4 device
Please check page#211 of this document, as all system calls are part of Nonvolatile memory
http://www.cypress.com/file/230701/download
So, it seems from all this above info that JLINK can't change the chip protection setting
Like Show 1 Likes(1)

Actions

Go to original post