[coldfire-gnu-discuss] Problem with P&E ParallelPortCable - Sourcery g++ Lite 4.2-8

Christof Frey Christof.Frey at varian.com
Thu Sep 27 09:49:57 UTC 2007


 

> -----Original Message-----
> From: Nathan Sidwell [mailto:nathan at codesourcery.com] 
> Sent: Thursday, September 27, 2007 11:18 AM
> To: Christof Frey
> Cc: coldfire-gnu-discuss at codesourcery.com
> Subject: Re: [coldfire-gnu-discuss] Problem with P&E 
> ParallelPortCable - Sourcery g++ Lite 4.2-8
> 
> Christof Frey wrote:
> > I am working with the P&E parallel cable and have installed the 
> > supplied drivers from CodeSourcery.
> > Unable to debug.
> > Getting the following:
> >  
> > C:\Projects\helloworld_mcf523x\src>m68k-elf-sprite -i CodeSourcery 
> > ColdFire Debug Sprite (Sourcery G++ Lite 4.2-8)
> > pe: [speed=<n:0-31>&memory-timeout=<n:0-99>] P&E Adaptor
> >   pe://CycloneProMaxSerial:1 - COM1 : Serial Port 1
> >   pe://ParallelPortCable:1 - LPT1 : Parallel Port 1 (Address $0378)
> 
> This shows that the pe library has detected two P&E devices.  
> You can use the URLs it lists to select devices unabiguously.
> 
> > (gdb) target remote | m68k-elf-sprite pe: m5235evb Remote debugging 
> > using | m68k-elf-sprite pe: m5235evb m68k-elf-sprite:Opening P&E 
> > CycloneProMaxSerial port 1 (COM1 : Serial Port 1) Ignoring packet 
> > error, continuing...
> > warning: unrecognized item "timeout" in "qSupported" 
> response Ignoring 
> > packet error, continuing...
> >  
> > Why is the sprite trying to open the P&E 
> CycloneProMaxSerial port 1 ? 
> > (instead of the known ParallelPort on address $0378)
> 
> You've given the URL 'pe:', therefore the first reported p&e 
> device that matches will be selected.  As you can see from 
> the above -i output, that will be the cyclonepromaxserial.  
> Use 'pe://ParallelPortCable:1' to explicitly select your 
> parallel port device.
> 
> > Additionally I get a dialog box indicating that there is a driver 
> > update for the CycloneProMaxSerial  going on (and finally fails)!!
> 
> Do you have a cyclonepromaxserial connected?
No, there is no connection at all on my COM1 port

I have a Edgeport USB to 4x serial converter on a USB port connected for
getting terminal output from the board. May this cause the trouble ?
> 
> >  
> > so, trying to configure the correct adapter with the whole 
> descriptor 
> > instead of just pe:
> >  
> > (gdb) target remote | m68k-elf-sprite 
> pe://ParallelPortCable m5235evb 
> > Remote debugging using | m68k-elf-sprite pe://ParallelPortCable 
> > m5235evb Ignoring packet error, continuing...
> > warning: unrecognized item "timeout" in "qSupported" 
> response Ignoring 
> > packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> 
> Can you try with
>    target remote | m68k-elf-sprite -v pe://ParallelPortCable 
> m5235evb That will provide more logging information.
> 
Did not get more logging information (as before):

(gdb) target remote | m68k-elf-sprite -v pe://ParallelPortCable m5235evb
Remote debugging using | m68k-elf-spm68k-elf-sprite:CodeSourcery
ColdFire Debug
Sprite (Sourcery G++ Lite 4.2-8)
rite -v pe://ParallelPortCable m5235evb
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...

Get additionally a windows dialog box from application
m68k-elf-sprite.exe:

"The instruction at "0x004037c5" referenced memory at "0x00000000", the
memory could not be "read".


> nathan
> -- 
> Nathan Sidwell    ::   http://www.codesourcery.com   ::       
>   CodeSourcery
> 
> 



More information about the coldfire-gnu-discuss mailing list