Re: [ECOS] Smallest GDB stub build?

Re: [ECOS] Smallest GDB stub build?

[harri.siirtola]

I have the insight+dejagnu-20010523.tar.bz2 snapshot. It can sometimes
connect to Angel (about once out of 5 trials), so something is wrong god
knows where. Program loading hangs every time, looking at Insight download
dialog it happens quite soon. Best record is 2560 bytes...

I'm using Atmel EB40 and Cygwin.

TIA for any clues,
	Harri

Re: [ECOS] Smallest GDB stub build?

[Lewin A.R.W. Edwards]

>BTW, is the fact that Insight doesn't work with Angel stated somewhere in
>Redhat web site? I think it should be, to keep people from struggling with it.

Insight _5.0_ is broken. Latest CVS should work. At least, latest CVS for 
command-line GDB works, so I presume Insight does also.


=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"... a man who is endowed with real qualities of leadership will be tempted 
to refrain from taking part in political life; because [...] the situation 
does not call for a man who has a capacity for constructive statesmanship 
but rather for a man who is capable of bargaining for the favour of the 
majority. Thus the situation will appeal to small minds and will attract 
them accordingly."

[ECOS] Smallest GDB stub build?

[harri.siirtola]

I have successfully built the ARM cross compiler and Insight under WIN98
(Cygwin). Also, I built ecos for my platform (Atmel EB40, using EB01 port).
As Insight is broken for Angel monitor, what's the way to go to build the
smallest memory image of GDB stubs (or something else) that could
communicate with Insight?

BTW, is the fact that Insight doesn't work with Angel stated somewhere in
Redhat web site? I think it should be, to keep people from struggling with it.

Thanks,
	Harri