Re: [ECOS] eCos and AT91SAM7S-EK

[Andrew Lunn <andrew at lunn dot ch>]

On Sat, Jun 30, 2007 at 11:13:16AM -0700, wavecom wavecom wrote:
> 
> --- Andrew Lunn <andrew@lunn.ch> wrote:
> 
> > On Sat, Jun 30, 2007 at 09:11:58AM -0700, wavecom
> > wavecom wrote:
> > > Thanks for answer,
> > > SAM-BA is tool provided by Atmel to downloading
> > code
> > > to Atmel arm controllers via USB and others
> > > interfaces. I've downloaded the ?hello? (without
> > > extension) file at start address 0x200000. Make
> > > execution on the examples produces 2 files
> > ?hello.o?
> > > and ?hello?. 
> > 
> > hello is the elf file. Does SAM-BA support elf, or
> > do you need to
> > convert it to binary using objcopy? I think your
> > probably do.
> 
> I have converted elf to bin by excetuting
> ?arm-elf-objcopy.exe -O binary hello hello.bin? than
> hello.bin I've downloaded to board by SAM-BA and
> result was the same ? no output string.

Well, this is the correct procedure....

> > > I have got wiggler-jtag interface, but I didn't
> > try it
> > > with the eCos. 
> > 
> > I suggest you use this with gdb for debugging and
> > use it for
> > downloading code to the device.
> > 
> 
> So I'll try to use wiggler-JTAG to run eCos examples. 
> At first I've started openocd ?openocd-pp.exe -f
> at91sam7s256-wiggler.cfg?. I had been using this
> configuration to debug and download standalone
> programs.  
> After that I've started gdb ?arm-elf-gdb hello? (hello
> elf), in gdb setup target ?target remote
> localhost:3333?
> 
> after the command the following messages appeared:
> ?
> (gdb) target remote localhost:3333
> Remote debugging using localhost:3333
> warning: (Internal error: pc 0x18 in read in psymtab,
> but not in symtab.)

You probably want to search the gdb mailling list for this. It sounds
like a gdb issue, not an eCos issue.

> (gdb) continue
> Continuing.
> warning: (Internal error: pc 0x18 in read in psymtab,
> but not in symtab.?
> ?
> But still no ?Hello, eCos world!?.

My JTAG tool seems to do something funky with the RAM/FLASH
mapping. So i tend to do 

set $pc=0x02000000
continue

so that it runs the code in flash, not the code at 0x0 which could be
the empty RAM.

    Andrew

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