Kinetis locked

[intern]

Hi Mark

I have somehow locked a TWR-k60F120M and i don't understand why.
i have read http://www.utasker.com/forum/index.php?topic=1737.msg6229;topicseen#msg6229 but still have some questions.
The uTaskerV1_4.bin file you are talking about, when is this file made?
because when i build the project (uTaskerKinetisV1.4.1) the file doesn't show up. And i can't see any bin file in the folder for kinetis for codewarrior even .

Thanks in advance
Intern..

[mark]

Hi

When building the Rowely Crossworks project the binary output is
\Applications\uTaskerV1.4\Rowley_Kinetis\THUMB Release\uTaskerV1_4.bin
GCC doesn't work correctly if names like uTaskerV1.4.1.bin are used.
This is the binary file referenced to in that post because it was a Rowely Crossworks project.

In other projects the binary usually has a slightly different name but the one being referred to is the one built by the project when targeted for standalone operation in Flash, or the output from boot loaders.

Generally is is not easy to fully lock a board since it requires a certain pattern in the binary file. Often the tools used also do some unexpected things like setting security (although this is not requested by anyone). Usually using the Flash tool to perform a full chip erase solves this. There are other things that can presumably happen and some tools have special utilities for "unlocking" such things.

Personally I never had this issue so didn't have to solve it. I would recommend checking out the Freescale Kinetis and Codewarrior forums since there are various threads there discussing such things. Im most cases people found a solution so it was probably not a fully locked-up state, which can not be recovered from.

https://community.freescale.com/community/kinetis
https://community.freescale.com/community/codewarrior

Regards

Mark