RE: [ECOS] Where to get a previous version of prebuilt GNU toolchain?

["wang cui" <iucgnaw at msn dot com>]

I have built a previous verion toolchain with below sources for target 
arm-elf
arm-elf_binutils-2.13.1
gcc-core-3.0.4
gcc-g++-3.0.4
newlib-1.11.0
insight-6.1
Of course these sources are patched as 
http://ecos.sourceware.org/build-toolchain.html

So far, with compile option "-gdwarf-2 -O0", the generated .elf file can be 
eaten by AXD 1.3.1 and most of the codes can be cross debugged now. But 
there are still some problems:

1. the listed file info in AXD is just raw file name without path, such as: 
"alias.c", "arm_stubs.c", etc. Thus I must specify each source file 
manually when debuging, and it's really bothering.
I am sure when I built application with Windriver Tornado 2.2's gun 
toolchain bdfore, the generated image(elf format) contains absolute file 
path info as "C:\Tornado2.2\target\config\all\bootConfig.c", etc. Then the 
AXD can locate all source directly.
So is there some options I should add/modify to generate absolute/relative 
file path info?

2. there are no assembly files list in the .elf, thus I can't debug 
assembly code with source, and just step over the assembly part until enter 
a C function.

3. it seems the AXD can't debug cpp file correctly.

4. The AXD works not as fine as I expected. I am still wandering is there 
other good debug enviroment(fully support of GNU .elf format) with JTAG 
interface to debug the low level program(like redboot itself)? 

Thanks in advance!

> From: "wang cui" <iucgnaw@msn.com>
> To: ecos-discuss@ecos.sourceware.org
> Subject: [ECOS] Where to get a previous version of prebuilt GNU toolchain?
> Date: Thu, 10 Aug 2006 04:07:42 +0000
>
> Hi:
>
> I am working on porting eCos to a LPC2138 based target. I modified 
> from the LPC2106 template from eCos CVS, and build a Redboot image. 
> I use ARM AXD V1.2 as the debugger, and download the redboot.bin to 
> LPC2138's internal flash successfully. Then I load the debug symbols 
> from redboot.elf. The AXD can list the source files and functions in 
> the image, but can't locate to correct source position. Thus I can't 
> do any debugging on it.
>
> I used compile option "-gdwarf -O0" to generate debug symbles. 
> Actually I have tried "-gdwarf-2 -O0" option, but the image is even 
> worse and cause the AXD throw unknown exception.
>
> As I googled, I find someone has faced such problem before, but I 
> can't get any solution on it.
> http://gcc.gnu.org/ml/gcc-prs/2002-06/msg00327.html
>
> So I want to try the arm-elf-gcc 3.0.4 toolchain to see whether I 
> can build a debugable image for AXD. Or anybody can tell me a good 
> solution to debug eCos by AXD?
>
> I am not sure that I can build a toolchain correctly, so can I get 
> the prebuilt version from somewhere?
> My host platform is cygwin on Windows XP.
>
> BTW, I have debugged VxWorks by the same way. I used Tornado2.2 GNU 
> toolchain, and the "-gdwarf -O0" option works very well, and the AXD 
> accecpt the bootrom and VxWorks(both in elf format) images without 
> any problem.
>
>
>
> --
> Before posting, please read the FAQ: 
> http://ecos.sourceware.org/fom/ecos
> and search the list archive: 
> http://ecos.sourceware.org/ml/ecos-discuss



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss