Flash Magic Forum

In-System Programming Support => ARM Cortex => Topic started by: mikro on March 28, 2012, 07:04:53 AM

Title: Unable to communicate after erasing
Post by: mikro on March 28, 2012, 07:04:53 AM
Hello,

I've got a "classic" problem with Flash Magic. After I erase the flash, I see Programming... status and then "Unable to communicate. (transmit/receive). I attach a debug file. I tried everything -- double check the device is flashable (on another computer), different USB2Serial converters, different cables, ... I have no idea what's wrong. What's even creepier, it used to work. In the meantime I re-installed Windows (7, in both cases) and it doesn't work anymore. But! Now my colleague says he has downloaded the newest version (6.30) and it doesn't work for him anymore as well! He used 5.x. So maybe it's a bug in FM after all.
Title: Re: Unable to communicate after erasing
Post by: mikro on March 28, 2012, 07:16:14 AM
Confirmed. I managed to find 5.94 version (tough luck since you can't find it anywhere in the Internet) and my LPC1754 works again. I'm open to help you with debugging if you want.
Title: Re: Unable to communicate after erasing
Post by: tonythi on March 28, 2012, 08:29:29 AM
Hi mikro! I'm having the very same problem! Do you still have V5.94 around nad could you email it to me (info@zephyr.de)? That would be great! Many thanks, Tony
Title: Re: Unable to communicate after erasing
Post by: tonythi on March 28, 2012, 08:38:12 AM
Hi mikro! Found version 6.03 which solved my problem!
Title: Re: Unable to communicate after erasing
Post by: smarly on March 28, 2012, 08:43:37 AM
Hi tonythi,
I have the same problem, could you share the release 6.03 ?
Many thanks.
Stan
Title: Re: Unable to communicate after erasing
Post by: mikro on March 29, 2012, 01:14:08 AM
5.94 version till the issue is resolved: http://ge.tt/8rkxddF/v/0?c
Title: Re: Unable to communicate after erasing
Post by: smarly on March 29, 2012, 01:15:59 AM
Thanks, it is working.
Title: Re: Unable to communicate after erasing
Post by: Andy Ayre on March 30, 2012, 01:52:54 AM
This should be fixed in version 6.31. Please post here if it is not.

Andy