[coldfire-gnu-discuss] m68k-elf-sprite 4.2-125 crashing

[Matt Cohn]

Thank you, I'm running the GNU tools via cygwin on Windows XP for clarification.  I found and used USBDeview.exe to uninstall my USB drivers to be reinstalled - they reinstalled fine but it did not alleviate the problem.  I don't have testcfz.exe, it wasn't on the CD that came with the M52233DEMO, and I wasn't able to find it anywhere on pemicro.com.  Do you know where I can find a copy?  Also I connected an external power supply and that had no effect.

What's so frustrating about this problem is I can't find any evidence of anyone else having anything similar!  Most of the time when leaving code executing for a couple minutes I'm simply unable to suspend again.  If I'm stepping through, invariably after so many steps (anywhere from 5 to 50) I recieve one of:

m68k-elf-sprite: error: Lost connection to hardware device
Error from remote target: Lost connection to hardware device

--or--


m68k-elf-sprite: error: Lost connection to hardware device
m68k-elf-sprite: Not closing port because of lost connection
Remote communication error: No error.

--or-- 

nothing on the console and m68k-elf-sprite will simply consume lots of CPU while eclipse does nothing, the step buttons grayed out, pressing halt or suspend grays out the corrosponding button.

I additionally installed XP SP3 as well as a few other Windows updates, disabled as many startup programs as I could bare to be without, updated Zylin Embedded Debug to its latest version, and tried using "GDB Hardware Debugging" instead of "Zylin Embedded debug" today with no effect.

Any ideas or things to try are sincerely appreciated - thank you!

--Matt



> Just to test the BDM interface I have a utility (PC/Windows based) call
> Testcfz.exe.  With the M52233DEMO connect to PC via the USB cable, it
> will find the ColdFire device and run a simple test and report PASS or
> FAILURE.  
> I've seen weird things if the PC USB port doesn't supply the 500mA.  You
> might try using external power supply to rule that out.
> Does your issue happen when not using verbose mode?
> I haven't sparked up my Linux box with CodeSourcery tools for awhile.
> I'll try to find some time to do that.
> I have used a utility called "USBDeview.exe" (again PC/Windows based) to
> remove/uninstall the USB drivers so that I can start fresh and new.
> Regards, 
> David  
> 
> 
> David E Seymour
> 
> http://www.freescale.com/coldfire
> 
> 
> -----Original Message-----
> From: Matt Cohn [mailto:codesourcery at mymail.mattcohn.com] 
> Sent: Thursday, September 04, 2008 2:18 PM
> To: Seymour David-RA2693
> Subject: RE: [coldfire-gnu-discuss] m68k-elf-sprite 4.2-125 crashing
> 
> Thanks David, I gave it a shot, but I wasn't able to locate updated
> firmware you mentioned.  From here:
> http://www.pemicro.com/support/download_processor.cfm the only relevent
> updates I found were to the hardware interface drivers (which I updated
> just to be sure).
> 
> The M52233DEMO board lists its onboard BDM as equivalent to USB-ML-CF,
> here:
> http://www.pemicro.com/products/product_viewDetails.cfm?product_id=163&C
> FID=1912140&CFTOKEN=57896256
> whose downloads section doesn't list any updated firmware.
> 
> Do you have any further ideas or things for me to try?
> 
> Thank you,
> --Matt
> 
> 
> > We've been having issues with the version of P&E USB BDM firmware.  
> > You might register on www.pemicro.com and download the latest BDM test
> 
> > utility and firmware to see if that helps.
> > Regards,
> > David
> > 
> > 
> > David E Seymour
> > 
> > http://www.freescale.com/coldfire
> > 
> > 
> > -----Original Message-----
> > From: Nathan Sidwell [mailto:nathan at codesourcery.com]
> > Sent: Tuesday, September 02, 2008 3:26 AM
> > To: Matt Cohn
> > Cc: coldfire-gnu-discuss at codesourcery.com
> > Subject: Re: [coldfire-gnu-discuss] m68k-elf-sprite 4.2-125 crashing
> > 
> > Matt Cohn wrote:
> > > Hia,
> > > 
> > > I am debugging a M52233DEMO board using the P&E USB BDM.  I connect 
> > > to
> > it via m68k-elf-sprite.  I turned on the verbose console and put the 
> > sprite in verbose mode, and here's the problem I'm experiencing.
> > > 
> > > Usually debugging will work fine for a while.  I will be able to
> > continue, suspend, step, break, and continue again without problems.
> > After leaving the program running for a while (a couple minutes) or 
> > doing a lot of stepping (anywhere, not in one particular place) I will
> 
> > experience the following.
> > > 
> > > If the code was running and I try to do a suspend, m68k-elf-sprite
> > uses a lot of CPU and doesn't respond.  Eventually GDB times out with 
> > "Target request failed: Failed to interrupt".  During this there is no
> 
> > response on the console.
> > 
> > > I should also note that occasionally (about 1/5th of the time) when
> > programming my board using CF Flasher, it will hang, timeout, fail 
> > validation and need to be flashed again.  Flashing again works fine.  
> > I have tried disconnecting all of my USB devices, using a different 
> > USB port, and killing all background processes and services to no
> avail.
> > Any advice is sincerely appreciated.
> > 
> > This sounds very much like a hardware problem, because you're getting 
> > it from two independent software tools.
> > 
> > nathan
> > 
> > -- 
> > Nathan Sidwell    ::   http://www.codesourcery.com   ::
> > CodeSourcery
> > 
>