Protecting Rows for Psoc 4

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
IgVi_1394436
Level 1
Level 1
First like received

I developed some applications for ProC BLe uC's and I was able to protect rows from Creator 3.3 without problems. I flashed using Programmer and the chip became properly protected.

Some months ago we were forced to migrate future upcoming applications to PsoC BLE equivalent uC's. We're using PSoc Creator 4.0 basically due to new required components.

After developing and tested I tried to protect rows using the same process. Basically, Chip protection selection and later on configuring flash Security.

After that I tried to flash using programmer but I was not able to properly protect the chip. The chiop became unprotected. I check several configurations with no success.

Following the thread, I notice that hex files does not contain the protection information that I got for ProC. Following some comparison for a complete rows protection for both ProC and Psoc 4 families.

---------------------------------------------------------------------------------------------------------------------------------------

PSoc 4:

0200000490303A

:02000000A780D7

:0200000490402A

:4000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C0

:400040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000080

:0200000490501A

:0C00000000021A1711AA00011AA8B92A60

:0200000490600A

:0100000001FE

:00000001FF

ProC:

:0200000490303A

:020000001341AA

:0200000490402A

:40000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00

:40004000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFC0

:0200000490501A

:0C00000000020E02119E00000E0F24DF13

:0200000490600A

:0100000002FD

:00000001FF

---------------------------------------------------------------------------------------------------------------------------------------

Before going on to check other possiibilities,

Is there any known bug in Creator 4.0 ?

What am I going wrong ?

Ignasi Villagrasa

0 Likes
1 Solution

Thanks for answering.

I had already used this option with no successful results.

I've been further investigating however.

At the end I saw what's going on.

I was not regenerating code from Creator 4.00

pastedImage_0.png

There I had true option instead of false option, as I have some generated code modified there and I din't wat

I noticed that VDHL converter is not only regenerating components but also initialization code for protecting chip, between others.

That's the reason why the protection options were not finally reflected in my hex file.

Anyway, thanks for the answer.

View solution in original post

3 Replies
Anonymous
Not applicable

There is a setting to code protect the flash when writing it to the chip using the PSoC Programmer itself; Try turning that setting on and see if it helps.

ChipProtectPSoC.PNG

0 Likes

Thanks for answering.

I had already used this option with no successful results.

I've been further investigating however.

At the end I saw what's going on.

I was not regenerating code from Creator 4.00

pastedImage_0.png

There I had true option instead of false option, as I have some generated code modified there and I din't wat

I noticed that VDHL converter is not only regenerating components but also initialization code for protecting chip, between others.

That's the reason why the protection options were not finally reflected in my hex file.

Anyway, thanks for the answer.

Anonymous
Not applicable

Thanks for posting your solution/answer you found

Epratt

0 Likes