MCF5223X EZ Port Tools

[LI_Dave]

I'm struggling with a dilemma on how to provide field updates for an MCF5223X based design.  I'd really like to be able to load new code without going through the trouble of a boot loader.  I also don't want to have to give out JTAG probes.  The EZPORT seems like the best solution.  I should be able to create a low pincount rugged interface that can load an entire image.  The problem is that there doesn't seem to be much in the way of third party tools out there...   Ideally I'd like a simple USB to EZport dongle that ran with CF Flasher.  Is anybody aware of such a thing?  Has anybody else used the EZPORT for field upgrades?    I'd be happy to create the hardware for the dongle and share it if I could get PC side software support. 

Another possibility is to make a programming dongle that takes a USB thumb drive.   This way you could update units without a PC.   Just plug a the USB thumb drive in one side and the target EZport in the other and away you go.   I'm kind of surprised this hasn't come up already.   Appreciate any comments.

Regards,
Dave

[Obetz]

Hello Dave,

it's indeed "surprising" that there are not more Products supporting EzPort .

I also asked several programmer suppliers but no one supported EzPort. I guess you could order a custom software for Softec's Flashrunner but I would better spend the money otherwise.

I would try the "Asagao" SPI Flash Writer software for FT2232 adapters.

Other candidates, likely not (yet) supporting EzPort:

The "Aardvark" I2C/SPI Host Adapter from http://www.totalphase.com/ with "Flash Center" Software doesn't list EzPort or Coldfire although it shouldn't be that difficult. Maybe worth to ask them.

usbprog from http://www.embedded-projects.net/ no EzPort.

There have been requests in the Ponyprog forum - no success.

Oliver

[Petter]

I've made my own programmer that I use for EzPort programming. I also use this to program Altera and Xilinx FPGA's as well as Microchip microcontrollers (also FLASH devices indirectly through JTAG).

I'm thinking about making this programmer into a product, but I'm also wondering about what type of connector to use. My first thought was to use a JTAG style connector.

For some of my own boards I'm planning to use an edge connector (i.e. a PCIe 1x style edge) that way there is no connector on the board but the board will slide into a slot for EzPort programming and JTAG testing.

[LI_Dave]

I'm still trolling around for a solution to this problem and may have found something or at least a start.  It seems someone in Japan has created a simple app that can download to the MCF5223X parts.

http://sourceforge.net/projects/asagao/

It requires a FTDI FT2232 based USB JTAG debugger such as the Amontec unit or more interestingly the GNice which is open source.  Not much to it beyond the FTDI part.

Unfortunately the documentation is in Japanese, but if you download the source there are some text files in English that explain things.    I'll try it as soon as I get my hands on compatible debug cable.

Has anybody else tried this?   

Regards, Dave

[MrBean]

I've looked at it, but i dont know much about it. Same dead end encountered.

Have you looked at the qspi-clone source Rich T provides on this page ?

I think it uses qspi from a master MCF5x to flash a slave MCF5x via the EZport.

Download the skeleton.zip at the bottom of the page and take a look at project/sources/clone.c inside the zip.

I hope it helps.

[RichTestardi]

So I'll mention I do the clones one of two ways:

1. if I don't care about security, I integrate a clone command directly into each target, and then any board can clone its bits to any other board.

2. if I care about security, I don't put the clone command into the target, but instead, run the "Flasher" RAM target once the target flash is programmed -- this required a BDM (to run the "Flasher" RAM target), but has the advantage that the target can't then be re-cloned.

One other thing...

If you look in upgrade.[ch], you'll see an S19 file parser.  If you look in ftdi.[ch] and usb.[ch], you'll see a USB virtual COM port driver, and if you look in clone.[ch] you'll see a qspi master clone driver.  It seems like someone could link these together and have a single-purpose USB device made out of any DEMO board that allowed you to connect to it from a PC, download an S19 file, and then pass it on out the qspi master to an EzPort...  Maybe after my current (good :smileyhappy: firedrill I'll take a stab at that.

[LI_Dave]

Once again revisiting this topic.  Some good news:  I did get the Asagao programming software to work.  It's a bit crude, but it does let you download to a MCF52233 over the EZ-PORT.   The software is available here:

http://sourceforge.net/projects/asagao/

For the USB to SPI it looks like any of the FTDI 2232 based USB JTAG adapters will work.  This one was pretty inexpensive and I can report that it does work:

http://www.xverve.com/development-tools/signalyzer-tool/signalyzer-lite-dt-usb-slite.html

It seems to address the issue.  The software could use some work and it would be nice if it had a bit more interactive device recognition and error checking.  If I have some time I'll take a cut at that.

Regards,

Dave

[mjbcswitzerland]

Hi Dave

This is a strange status indeed. I have been involved with two production projects where the EZport was decided on and in each case we never managed to find anything on the market to do it, and in both cases the solution was to use an EVB (or DEMO) board with code to program it via QSPI.

There is some reference code here.
http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&message.id=3911&query.id=30163#M...

Regards

Mark

[LI_Dave]

Well, maybe it's time to do something!   I may just give this a try.  First thing is to define a connector.  I'd like something fairly small and rugged that a field service guy could handle.   Small so I can put a rubber or plastic cover over a port on the side of my enclosure and use that to access the port.   The first thing that comes to mind is the mini USB connectors, or maybe even an RJ-11?   The danger with each of these is that it could be mistaken for another function.  Evena Mini-DIN like a PS/2 keyboard or mouse might work.  Please feel free to make suggestions.

If we can agree on something perhaps we can get it accepted by FS as a standard?

Dave