Message Edited by rocco on 2006-08-23 02:09 PM
Not quite the same league but the first time I used my P&E USB Multilink with Codewarrior it just decided all by itself that it needed to be updated. Flashed a window up while it did so that then dissappeared by itself.
This actually caused no problems and I had none before BUT..........
If I had been asked I would have rejected the upgrade until a less dangerous (for me) time.
If I had of looked away or blinked when the update occurred I would never have known and if some problems did crop up I would never have known to blame the upgrade. I still don't know the previous version number and never took any notice before.
I have written about this before here.
Yes, I did recall your experience with the USB Multilink. This is a primary reason why I have not yet tried to use Code Warrior in conjunction with my Mon08 Multilink.
Another of the questions I posed to Freescale Support, in addition to the MMEVS issue -
"I am also using a Mon08 Multilink (parallel port version) for programming purposes. Does CW burner or debugger also require to erase its firmware, without giving any warning or choice in the matter."
I received the response -
"The multilink automatically updates its firmware. CW does not to my knowledge."
Curiouser and curiouser!
Dear David and Mac,
Multilink is P&E Micro and not Freescale. I think what the person wanted to tell you is that CodeWarrior does not see the firmware update and it is internal to the P&E Micro programming DLL.
It does not address the question on MMEVS though...
Instead of taking my message as "finger pointing" you could well take it as "check-with-P&E-Micro suggestion to go forward" ...
I'm not P&E Micro Techical Support and I don't see them here regularly !
They have a Forum on their website.
Message Edited by Alban on 2006-08-23 12:16 PM
As this forms part of the basic Codewarrior package and escpecially as it is more of suggestion of something to be looked into rather than a bug or something I would have though pointing it out here would have been sufficient to prompt Freescale to act on this themselves in order to produce a better user experience for their product.
My car is made up of many components/sub-assemblies not actually made by the manufacturer of the car. When I have a problem with one of these I talk to the car manufacturer, not the component manufacturer, and I think most people would expect them to deal with it.
I love your analogy even if I completely disagree (when I buy a house...).
My aim is to solve members problem, it doesn't matter to me if Freescale or a thrid party screwed up (I don't get paid more one way or another, it's still on my free time). My final goal is for it to work.
That's why I contacted P&E Micro and asked for their opinion.
Nevertheless, not to take anybody's defense (coz it's not my role anyway), IMHO having automatic updates does create "a better user experience for (...) product" generally speaking. (antivirus, Windows, firewall, calendars...)
We'll see if they want to put a switch/check box for developpers who want total control.
It's a fact of life . . . Firmware updates can fail.
I would like to know when ANY firmware update occurs, so that I am not chasing my tail, wondering what's gone wrong, on those few occasions when the update does fail.
Yes they do! I had a Windows CE terminal fail completely during an update just yesterday! The power went off during the update and there is now apparently nothing I can do except have it replaced. This was a deliberate upgrade initiated by me in this case.
I have Win XP updates completely automatic on my desktop, but on my notebook I have them set to "ask before" or something like that.
This is EXACTLY for the same as my reason (1) for not liking fully auto updates. My desktop is "backed up" by my notebook but my notebook in the field is on its own. Only I know when it is essential that it functions normally (the next day during a large interstate commissioning for example). All the updates are done on both at present, I just pick a "safe" time to do them on the notebook.
As for reason (2), if something starts not working properly soon after an upgrade you can blame the upgrade or try to go back to the previous version etc IF YOU KNOW THAT IT HAPPENED!
As for my Multilink, I was in the middle of adding some functionality to one of our products using older standalone P&E software. I was just experimenting with Codewarrior "after hours", given the choice I would have rejected the upgrade attempt at that time.
Please Mark, if you are going to add a dialogue box can't it be before the upgrade with a button to bail out? This should be no harder to implement but would cover all possibilities. Thank you for you assistance with this.
With these facts it would be reasonable to assume that my problem is due to a malfunction of a Freescale program. Yet in a subsequent service request to Freescale, I was informed that I would need to purchase a new MMEVS since the existing unit was faulty (probably 1000 - 1500 AUD for a new base module). I consider this response to be totally unreasonable, and will not be doing so. This will certainly inhibit my future product development using 908Q series devices.
This leaves me with a bad taste with respect to Code Warrior, especially since I had previously used P&E assembler and debugger without any problems, and since I have no need of C for these low end devices.
Message Edited by bigmac on 2006-08-29 02:54 AM
Message Edited by bigmac on 2006-08-29 01:49 PM