K53n512 Bricked

[rcl-arm-coder]

While minding my own business and innocently trying out 'example' programs:smileysilly:, I had 'processor expert' pop up in one of the IDE's I was

trying.

This has probably reconfigured internal GPIO assignments that control power/reset modes.

End of day, K53N512 tower board is bricked. The nice people at P + E Micro will gladly sell me (400 usd) a jlinkish debugger

and a mini app that prompts you to power up/down the board, and attempts to halt before the 'dangerous' area, and let you erase the flash.

Hey Freescale - isn't there an easier way to erase the flash and start again non-brick mode?

Thanks

Richie

[adriancano]

Hi,

it is possible that the reconfiguration of the GPIO affected the JTAG pins ans this is causing that behavior. You can try a mass erase how is showed in this post:

Re: PE multilink JTAG/BDM Kinetis programming issue

Also you can try to use the P&E Recovery Utility that is mentioned in this post by colleague Erich Styger:

Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power | MCU on Eclipse

For the TWR-K53 you need to select the USB Multilink (OSBDM) option and JTAG, please refer to the post for more information.

Hope this information can help you.

Best Regards,
Adrian Sanchez Cano
Technical Support Engineer
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[rcl-arm-coder]

Hi Adrian

I read both of those recommended posts before posting the 'kn53 brick' post, because they do not answer the issue.

resources available to me:

1) KN53 tower kit (elevator boards, serial board, KN53 board) - Every sw tool from PE Micro - Kinetis Design Studio - IAR (latest) - Keil.microvision (latest) - Last 5 current versions of Eclipse - All SDK's, tools, examples from Freescale - several varieties of J-Link debugger

 - Fully updates drivers for all of the above (sparing you the details)

In none of the above is a 'K53 example' for any of the IDE's, lots of K60 examples(especially in the K53 downloads!)

Assuming that development time is more important than the cost of another K53 tower board, and thatI 'start fresh' with a non-bricked board, what do you recommend as a development environment"ready to go" for the purpose of evaluating the K53 for our products ?

Cool features would be -

---

- real K53 'project' examples for the chosen (you suggest, I either already have it, or can get it) IDE

- low chance of making another brick, especially with Freescale's own tools and suggested configurations

Don't stress too much about it, at the end of the day we will probably never build more than100,000 products with the K53 - it's not for consumer gear, so no real high volume.

It is however for products that will be used to protect people, prevent harm, look out for national security and hopefully make a difference. Visit kromek.com if curious.

From: Adrian Sanchez Cano <admin@community.freescale.com>

To: richard lowes <richardl10@rocketmail.com>

Sent: Friday, November 28, 2014 7:32 PM

Subject: Re: - K53n512 Bricked

|

|

K53n512 Bricked

reply from Adrian Sanchez Cano in Kinetis Microcontrollers - View the full discussionHi, it is possible that the reconfiguration of the GPIO affected the JTAG pins ans this is causing that behavior. You can try a mass erase how is showed in this post:Re: PE multilink JTAG/BDM Kinetis programming issue Also you can try to use the P&E Recovery Utility that is mentioned in this post by colleague Erich Styger:Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power | MCU on EclipseFor the TWR-K53 you need to select the USB Multilink (OSBDM) option and JTAG, please refer to the post for more information.

Hope this information can help you. Best Regards,

Adrian Sanchez Cano

Technical Support Engineer

[mjbcswitzerland]

Richard

As long as you haven't set flash security to block erasing it may be simplest to use the EZ port to send a mass erase to the device. This requires just 3 signals to be connected and typical SPI Flash commands to be sent. There is an application note for an EZ port programmer on a KwikStik if you search the Freescale web site.

If you have another Kinetis board you can also use this to do it by loading the uTasker project to it - it has an EZ port option which can be enabled which allows commands to be sent.

The uTasker project also includes support of the TWR-K53N512 (USB, Ethernet, SLCD etc.) (as well as most other KE, KL, and K parts out-of-the-box without needing to port from a few standard demo parts). It also allows you to simulate the Kinetis and the board in (approx.) real time so will improve development efficiency dramatically compared to traditional techniques.

Below is a screen shot of the project running the TWR-K53N512 and its SLCD. There is also a video of the SLCD in operation at K40_SLCD.wmv - YouTube and some further details in http://www.utasker.com/docs/uTasker/uTasker_SLCD.pdf (the video shows K40s in operation but the K53 is essentially equivalent for the SLCD interface)

Regards

Mark

http://www.utasker.com/kinetis.html