EzPort Cloning

[mjbcswitzerland]

Hi All

I have always been surprised at the limited availability of EzPort programers for production use and some complications involved with their practical use.

After having experienced a number of Coldfire and Kinetis products that have been factory programmed using EzPort it was decided that a general, simple and practical method would often make things simpler.

For this reason the uTasker project has been extended to include an integrated EzPort cloner that allows any device/software to clone itself to other device when they have an EzPort implemented (for example, KL parts don't include EzPort).

The interface is flexible enough to be used to experiment with EzPort operation but optimised enough to allow unsecuring devices, cloning them unsecurely or cloning them securely (that it, the target is also set to the secure mode so that its code can't be read out) with verification, based on a single command.

For simpest use (without need for PC) in the final production environment a push button can be assigned to start the cloning process and the result (pass/failure) displayed on an LED.

A user's guide can be found at http://www.utasker.com/docs/uTasker/uTaskerEzPortCloner.pdf

and I have attached a FRDM-K64F software (with command line interface on its Virtual COM UART port at 115.2kBaud) with EzCloner function. It can clone itself to other FRDM-K64Fs as explaned in the guide.

Regards

Mark

Original Attachment has been moved to: uTaskerV1.4.11_FRDM-K64F_EzCloner_V1.0.bin.zip

[taronhov]

Hello Mark,

  At first, I would like to thank you for the great and hard work done on uTasker project and for open-sourcing it!

  I am currently trying to build the 1.4.11 version of the Application (uTaskerV1.4) with the "EZPORT_CLONER" option/feature enabled but was not able to get it working on FRDM-K22F development board... I have determined, that it only compiles and runs normally (with "USE_MAINTENANCE" defined/activated) only with this additional configuration.
***
#define NO_PERIPHERAL_DEMONSTRATIONS
***
But when the firmware runs, the Data-In and Data-out signals of EzPort remain static after Read/Write transaction commands (while the rest of the signals look and behave just fine). I have tried to assign these signal to different pins of K22 MCU with no luck. For the activation of EzPort interface I am following the steps in your "µTasker – EzPort Cloner" document (e.g. doing "ez_config" + "ez_reset" before Read/Write).

  So, I have bought a FRDM-K64F board and currently am trying to compile the Application and get the EzPort Cloner working on it, instead. In case it fails and as a reference point for comparison, could you, please, re-share the attached evidently good binary? The link to the current attachment seems to be broken/invalid...

Thanks and Regards,
Taron

[cwolff]

Where can I find the source code for the FRDMK64 example?  I am looking at doing something similar but I want the option to use a modified production board as a 'cloner' to program virgin boards in bulk.

[mjbcswitzerland]

Hi

Code is available at http://www.utasker.com/kinetis.html

Enable the EzPort cloner option in the file Applications\uTaskerV1.4\debug.c using #define EZPORT_CLONER

Regards

Mark

[mjbcswitzerland]

Hi All

Thanks to Charles for the following video showing his product using the EzPort cloner for production loading. It clones the uTasker serial loader (as SD card loader from SPI based Flash file system) and his initial application from a FRDM-K64F, requiring a single push of a button:

https://www.youtube.com/watch?v=5fI44hFcF18&feature=youtu.be

Regards

Mark