CodeWarrior 10.6 secures K70

cancel
Showing results for 
Search instead for 
Did you mean: 

CodeWarrior 10.6 secures K70

294 Views
Specialist V

Hi All

 

Is this a problem with CodeWarrior and its operation with the K70?

 

I use the Flash utility to program a binary file to the K70F120 on the TWR-K70F120M, which works and allows the program to operate. However when I want to program another code or debug with any debugger I get the message that the device is secured and a mass erase is executed in order to be able to continue.

Thinking that I must have an error in the Flash configuration I checked in the binary and it is like this:

 

17802_17802.pngpastedImage_0.png

 

The FSEC setting is 0xbe, which is
KEYEN 10 (backdoor key access enabled)
MEEN 11 (mass erase enabled)

FSLACC11 (Freescale factory access granted)

SEC 10 (MCU security is unsecure)

 

Therefore this is not securing the device based on the value.

 

 

So I checked the state of Flash that had been programmed to the chip by using the memory debugger that is built into the program that was loaded. It gives:

0x00000400 00 00 00 00 00 00 00 00 ff ff ff ff bf 07 ff ff

and shows that teh device is indeed secured since the value 0xbf has been programmed rather than the value 0xbe that is in the binary file.

 

I only have a problem with K70 programming so my question is: does the programmer for the K70 do this on purpose and / or make an error in setting this byte??

 

Regards

 

Mark

Labels (1)
0 Kudos
4 Replies

86 Views
NXP TechSupport
NXP TechSupport

hi Mark,

how does it work if you set SEC as 11 ?

i don't have board for the moment but last week i set FSEC as 7C on a K20 board. it get secured well.

Best Regards,

Zhang Jun

=========================================

this answer is for you. if it helps, please click on "Correct Answer " button. thanks!

0 Kudos

86 Views
Specialist V

Hi

I am not sure that you understood the probem. I am trying NOT to secure the device when programming code with CodeWarrior but it IS securing it (which is not what the code is set for). If 11 is set in SEC it would then be "intentionally" securing it, which is waht must be avoided.

Regards

Mark

0 Kudos

86 Views
NXP TechSupport
NXP TechSupport

Hi Mark,

please set FSEC as 0x32 that is for unsecure flash.


Best Regards,

Zhang Jun

=========================================

this answer is for you. if it helps, please click on "Correct Answer " button. thanks!

0 Kudos

86 Views
Specialist V

Hi

What I have found in the meantime is that if I set the flash configuration to

0x00000400 00 00 00 00 00 00 00 00 ff ff ff ff fe ff ff ff


then I do get this content written to the Flash when loading with CW flashing utility. Therefore this workaround can be used.

The effect if however reproducable whenever the orignal values are used so looks to be a problem with the flasher.


Regards

Mark


0 Kudos