Possible Bricked MK20DX256?

Follow

Lee Jones

• February 24, 2017 08:45

Hello,

 

I was wondering if it was possible for CrossStudio Output Window to inform me of the exact value in the security register when connecting to an MK20DX256.

 

I believe I may have changed the security bits on the MK20 and disabled mass erase. 

Ideally, I would like the output to either show me the contents of the FSEC register after it have got the device IDCODE. Is there a setting to do this? or somewhere I can edit to allow this. 

 

Below is the exact information I get in the Output window at the bottom.

 

Executing connect script

Loading target script file Kinetis_Target.js

Executing script Connect()

IDCODE 0x2ba01477 SW-DP VERSION 1

AP 0 0x24770011 AHB-AP for CM3 Rev 2 Little Endian

AP 1 0x001c0000 JEP 106 code = 0x0 0xe Class not a MEM-AP ID 0x0 Rev 0

Executing get part name script

Loading target script file Kinetis_Target.js

Executing script GetPartName()

MassErase failed

Identifying

ROM Table 0xe00ff000

Core type mismatch

Detected core type doesn't agree with debug interface type project property

 

 

 

Any help would be appreciated!

0

• 

  Michael Johnson

  • February 24, 2017 16:38

  You may be able to modify the target script to output the value of FSEC register.

  0

  Comment actions Permalink
• 

  Lee Jones

  • February 25, 2017 07:49

  That is something I would love to try....

  However, I have failed at the first hurdle and been unable to locate the Kinetis_Target.js file....

   

  Any one know where I may be able to find it. 

  0

  Comment actions Permalink
• 

  Michael Johnson

  • February 25, 2017 08:03

  Using the project properties dialog/window right click on the Target Script File project property and select "Open"

  1

  Comment actions Permalink
• 

  Lee Jones

  • February 28, 2017 08:41

  Perfect, Found it. Thank you Michael.

  Interestingly, there is already a function which prints out the status register info... It seems to use the command "wscript.echo"..... 

  Apparently this should print in the output terminal.... Although I never see these messages.

  I have got around it by printing the same message using the "TargetInterface.message" command. It would be good to know where the "wscript.echo" messages should be appearing..

  Anyway.... turns out I have infact locked myself of the MK20.... except that  Backdoor Access is enabled. 

  So my next question, does anybody know how to utilise backdoor access with crossworks?

  Thanks.

   

   

   

  0

  Comment actions Permalink

Please sign in to leave a comment.