Warning - Code Warrior can destroy your MMEVS

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Warning - Code Warrior can destroy your MMEVS

8,107 Views
bigmac
Specialist III
I wonder if anyone else has had a similar experience!
 
I have a MMEVS comprised of M68MMEVS05PFB (1994) base module, and EML08QY (2002) emulation module. This has been successfully used in conjunction with the P&E debugger program for about three years, for HC908QT/QY target devices.
 
I recently attempted to use the MMEVS in conjunction with the CW 5.0 debugger (used as a stand-alone utility, and not via IDE) - I had previously used the debugger only in simulation mode.
 
When I first selected MMEVS mode within the debugger, there was a flurry of data activity, as indicated by flashing of the LED on the MMEVS.  I was then presented with an error message that the file "firm0508.mon" did not load, or could not be found, even though this file was located in the directory specified.
 
All subsequent attempts to communicate with the MMEVS now fail, whether using CW or the P&E debugger. Connecting a terminal emulation program directly to the MMEVS generates nothing after power-up - I would expect some sort of "banner" message to be displayed.  It appears that the existing MMEVS firmware has been erased by CW.  No prior warning was given by the program that a firmware upgrade was needed, and that this would automatically occur.
 
A request to Freescale support has been less than helpful - with the response "it sounds like your firmware is corrupted or damaged", and that I would therefore need to purchase a new MMEVS - (contrived obsolescence??).
 
Does anyone know what steps are necessary to re-instate the original MMEVS firmware, as I would expect that this should be possible?  After this experience, I have nil confidence in using Code Warrior - what other hidden "updates" might it attempt?
 
Regards,
Mac
 
Labels (1)
Tags (1)
0 Kudos
25 Replies

225 Views
peg
Senior Contributor IV

Hi Mark,

I understand your dilemma here.

The advice having to be acknowledged is the greater part of the problem covered. From memory the upgrade was done in a few seconds and so the message while it was being done is too fast.

How about closing down completely if the update is rejected?

Regards David

Apologies to Mac for hijacking his thread.

Message Edited by peg on 2006-08-24 07:36 AM

0 Kudos

225 Views
P_EMark
Contributor III
Closing down completely is not really an option-- especially when dealing with Third Party software, etc....

Regards,
Mark
0 Kudos

225 Views
rocco
Senior Contributor II
Peg brings up a good point.

We never-ever upgrade our tools in the middle of a project. It can be a serious schedule-destroyer.

But we often evaluate new tools during a project for future projects. Management would be seriously upset if a product that we were evaluating upset our hardware environment. That product would never be bought.

Message Edited by rocco on 2006-08-23 02:33 PM

0 Kudos

225 Views
P_EMark
Contributor III


rocco wrote:
Peg brings up a good point.

We never-ever upgrade our tools in the middle of a project. It can be a serious schedule-destroyer.

But we often evaluate new tools during a project for future projects. Management would be seriously upset if a product that we were evaluating upset our hardware environment. That product would never be bought.

Message Edited by rocco on 2006-08-23 02:33 PM





Well, the firmware update procedure *IS* covered in the manual.... :smileyhappy: But we all know how many of us engineers actually read the manual, right??

Anyways, a valid point-- however, my devil's advocate argument would be to isolate development systems from test systems-- especially for mission critical development.

AND, it should of course be noted that it's always possible to revert to old firmware if absolutely necessary-- we will always help a customer with this process if it becomes necessary...

Regards,
Mark
0 Kudos

225 Views
P_EMark
Contributor III
So, your take is, a notification dialog is sufficient?

(We currently do display a dialog to indicate that a firmware update is occuring, however we close it as soon as the update is complete-- without waiting for user acknowledgement, etc).

- Mark
0 Kudos