[ECOS] eCos and AT91SAM7S-EK

[ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

Hi,

I'm the beginner eCos user. Now I'm trying to run eCos
on the AT91SAM7S-EK. I've downloaded newest version of
eCos source code and the configtool from cvs. After
setup for AT91 I have successfully compiled eCos libs
with default compilation options except -g option. I
have removed -g option from options to  minimize size
of  kernel.
I wanted to run the “Hello, eCos world!” example, I
have compiled those examples using default Makefile
from /examples directory. Then I have downloaded
result (“examples/hello”) using SAM-BA to the 
AT91SAM7S-EK board. The board was connected to PC via
SERIAL0 and DBGU to PC where I have got 2
hyperterminals (38400 8-n-1 non-flow control). 
I'm expecting to observe “Hello, eCos world!” on one
of the hyperterminals, but after reset there was no
output.

How should I configure or compile the example to run
examples?
How should I download compilation result to board?
Is it possible to change arm-serial port for printf
function?
Is there any tutorial for eCos on AT91SAM7S-EK?

Pete


       
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222

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

Re: [ECOS] eCos and AT91SAM7S-EK

[Andrew Lunn]

On Sat, Jun 30, 2007 at 01:04:03AM -0700, wavecom wavecom wrote:
> Hi,
> 
> I'm the beginner eCos user. Now I'm trying to run eCos
> on the AT91SAM7S-EK. I've downloaded newest version of
> eCos source code and the configtool from cvs. After
> setup for AT91 I have successfully compiled eCos libs
> with default compilation options except -g option. I
> have removed -g option from options to  minimize size
> of  kernel.
> I wanted to run the ?Hello, eCos world!? example, I
> have compiled those examples using default Makefile
> from /examples directory. Then I have downloaded
> result (?examples/hello?) using SAM-BA to the 
> AT91SAM7S-EK board. The board was connected to PC via
> SERIAL0 and DBGU to PC where I have got 2
> hyperterminals (38400 8-n-1 non-flow control). 
> I'm expecting to observe ?Hello, eCos world!? on one
> of the hyperterminals, but after reset there was no
> output.

I've never used SAM-BA, so maybe a dumb question. What exactly did you
download? The elf or a binary image? Where did you download it to?
What address?

In order to do any serious work with the AT91SAM7S devices you are
going to need a JTAG device for both code download and debugging.

      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

Re: [ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

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”. 
I have got wiggler-jtag interface, but I didn't try it
with the eCos. 

Pete



--- Andrew Lunn <andrew@lunn.ch> wrote:

> On Sat, Jun 30, 2007 at 01:04:03AM -0700, wavecom
> wavecom wrote:
> > Hi,
> > 
> > I'm the beginner eCos user. Now I'm trying to run
> eCos
> > on the AT91SAM7S-EK. I've downloaded newest
> version of
> > eCos source code and the configtool from cvs.
> After
> > setup for AT91 I have successfully compiled eCos
> libs
> > with default compilation options except -g option.
> I
> > have removed -g option from options to  minimize
> size
> > of  kernel.
> > I wanted to run the ?Hello, eCos world!? example,
> I
> > have compiled those examples using default
> Makefile
> > from /examples directory. Then I have downloaded
> > result (?examples/hello?) using SAM-BA to the 
> > AT91SAM7S-EK board. The board was connected to PC
> via
> > SERIAL0 and DBGU to PC where I have got 2
> > hyperterminals (38400 8-n-1 non-flow control). 
> > I'm expecting to observe ?Hello, eCos world!? on
> one
> > of the hyperterminals, but after reset there was
> no
> > output.
> 
> I've never used SAM-BA, so maybe a dumb question.
> What exactly did you
> download? The elf or a binary image? Where did you
> download it to?
> What address?
> 
> In order to do any serious work with the AT91SAM7S
> devices you are
> going to need a JTAG device for both code download
> and debugging.
> 
>       Andrew
> 



       
____________________________________________________________________________________
Choose the right car based on your needs.  Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/

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

Re: [ECOS] eCos and AT91SAM7S-EK

[Andrew Lunn]

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 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.

            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

Re: [ECOS] eCos and AT91SAM7S-EK

[Andrew Lunn]

> > Where can I find such pre-build version?
> 
> I have insalled
> bu-2.17_gcc-4.2.0-c-c++_nl-1.15.0_gi-6.6.exe from
> www.gnuarm.org . Is it enough for eCos build?

See:

http://ecos.sourceware.org/getstart.html

The toolchains are there.

    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

Re: [ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

> > > Andrew, could you describe me your method of
> > running
> > > and debugging eCos application, maybe I'm able
> to
> > > reproduce it on my hardware. 
> > > I'd like to ask about configuration of outgoing
> > > messages. Where can I check if the output of
> > prontf
> > > commands is ARM-COM1?
> > 
> > I use Linux, not M$.
> > 
> > I build ROM applications, which for the AT91SAM7
> > platforms is the
> > default. I use the toolchain which you can
> download
> > from the eCos
> > website.  I use a JTAG device to load the image
> into
> > the target. The
> > JTAG device i use understands ELF, so i just give
> it
> > a URL and the
> > device grabs the elf file, converts it as
> necessary,
> > and loads it onto
> > FLASH. I then use gdb, to connect to the JTAG
> device
> > in much the same
> > way as you did. I there use the gdb version you
> > download as part of
> > the toolchain, or sometimes i use a newer version
> > which i built
> > myself. I would recommend you use the pre-build
> > version to start with
> > since it is known to work.
> 
> Where can I find such pre-build version?

I have insalled
bu-2.17_gcc-4.2.0-c-c++_nl-1.15.0_gi-6.6.exe from
www.gnuarm.org . Is it enough for eCos build?

> 
> > 
> > The default configuration of the AT91SAM7SEK is to
> > use the debug port
> > for I/O.
> > 
> >     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
> > 
> > 
> 
> 
> 
>      
>
____________________________________________________________________________________
> Fussy? Opinionated? Impossible to please? Perfect. 
> Join Yahoo!'s user panel and lay it on us.
>
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
> 
> 
> 
> -- 
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
> 
> 



       
____________________________________________________________________________________
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
http://new.toolbar.yahoo.com/toolbar/features/mail/index.php

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

Re: [ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

--- Andrew Lunn <andrew@lunn.ch> wrote:

> > Andrew, could you describe me your method of
> running
> > and debugging eCos application, maybe I'm able to
> > reproduce it on my hardware. 
> > I'd like to ask about configuration of outgoing
> > messages. Where can I check if the output of
> prontf
> > commands is ARM-COM1?
> 
> I use Linux, not M$.
> 
> I build ROM applications, which for the AT91SAM7
> platforms is the
> default. I use the toolchain which you can download
> from the eCos
> website.  I use a JTAG device to load the image into
> the target. The
> JTAG device i use understands ELF, so i just give it
> a URL and the
> device grabs the elf file, converts it as necessary,
> and loads it onto
> FLASH. I then use gdb, to connect to the JTAG device
> in much the same
> way as you did. I there use the gdb version you
> download as part of
> the toolchain, or sometimes i use a newer version
> which i built
> myself. I would recommend you use the pre-build
> version to start with
> since it is known to work.

Where can I find such pre-build version?

> 
> The default configuration of the AT91SAM7SEK is to
> use the debug port
> for I/O.
> 
>     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
> 
> 



      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 


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

Re: [ECOS] eCos and AT91SAM7S-EK

[Andrew Lunn]

> Andrew, could you describe me your method of running
> and debugging eCos application, maybe I'm able to
> reproduce it on my hardware. 
> I'd like to ask about configuration of outgoing
> messages. Where can I check if the output of prontf
> commands is ARM-COM1?

I use Linux, not M$.

I build ROM applications, which for the AT91SAM7 platforms is the
default. I use the toolchain which you can download from the eCos
website.  I use a JTAG device to load the image into the target. The
JTAG device i use understands ELF, so i just give it a URL and the
device grabs the elf file, converts it as necessary, and loads it onto
FLASH. I then use gdb, to connect to the JTAG device in much the same
way as you did. I there use the gdb version you download as part of
the toolchain, or sometimes i use a newer version which i built
myself. I would recommend you use the pre-build version to start with
since it is known to work.

The default configuration of the AT91SAM7SEK is to use the debug port
for I/O.

    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

Re: [ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

--- wavecom wavecom <wavecomw@yahoo.com> wrote:

> > > I've just tried procedure form eCos pdf-s.
> First,
> > I
> > > have downloaded the redboot from
> > >
> >
>
?\htdocs\boards\redbootbins\at91sam7s\redboot_rom.bin?
> > > (cvs path). Now on ARM-COM1 I've got console:):
> > > ?
> > >  RedBoot(tm) bootstrap and debug environment
> [ROM]
> > > Non-certified release, version UNKNOWN - built
> > > 22:08:24, Feb 19 2006
> > > 
> > > Platform: Atmel (at91sam7s) (ARM7TDMI)
> > > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red
> > Hat,
> > > Inc.
> > > 
> > > RAM: 0x00200000-0x00210000,
> > [0x00206ca0-0x0020c800]
> > > available
> > > FLASH: 0x00100000 - 0x140000, 1024 blocks of
> > > 0x00000100 bytes each.
> > > RedBoot>
> > > RedBoot>
> > 
> > O.K. This is good. It shows your download process
> is
> > working.
> > 
> > > ?
> > > 
> > > After that I was tried to use gdb:
> > > ?
> > > C:\cygwin\opt\ecos\ecos-2.0\examples>"c:\Program
> > > Files\yagarto\bin\arm-elf-gdb.e
> > > xe" -nw hello
> > > GNU gdb 6.5.50.20060612-cvs
> > > Copyright (C) 2006 Free Software Foundation,
> Inc.
> > > GDB is free software, covered by the GNU General
> > > Public License, and you are
> > > welcome to change it and/or distribute copies of
> > it
> > > under certain conditions.
> > > Type "show copying" to see the conditions.
> > > There is absolutely no warranty for GDB.  Type
> > "show
> > > warranty" for details.
> > > This GDB was configured as
> "--host=i686-pc-mingw32
> > > --target=arm-elf"...
> > > (gdb) set remotebaud 38400
> > > (gdb) target remote COM7
> > > Remote debugging using COM7
> > > 0x00104954 in Cyg_StdioStreamBuffer::set_buffer
> > > (this=0xd3, size=6,
> > >     new_buffer=0x5
> > >
> >
>
"?\237&#328;\030?\237&#328;\030?\237&#328;\030?\237&#328;&#9632;
> > >  &#341;\030?\237&#328;\030?\237&#328;
> > > &#9568;")
> > >     at
> > >
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/stre
> > > ambuf.cxx:84
> > > 84     
> > >
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/str
> > > eambuf.cxx: No such file or directory.
> > >         in
> > >
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/
> > 
> > Are you really using eCos 2.0? It is very old. I
> > would suggest you
> > update to anoncvs.
> 
> This is the newest verion of eCos from CVS, I've
> only
> copied to existing directory.
> 
> > 
> > > streambuf.cxx
> > > Current language:  auto; currently c++
> > > (gdb) load
> > > Loading section .rom_vectors, size 0x40 lma
> > 0x100000
> > > Loading section .text, size 0x7ba4 lma 0x100040
> > > Loading section .rodata, size 0x238 lma 0x107be4
> > > Loading section .data, size 0x42c lma 0x107e1c
> > > Start address 0x100040, load size 33352
> > > Transfer rate: 26681 bits/sec, 370 bytes/write.
> > > (gdb) break main
> > > Breakpoint 1 at 0x10055c: file hello.c, line 6.
> > > (gdb) cont
> > > Continuing.
> > 
> > You can single step the startup code and see where
> > it goes wrong.
> > However i've never done this with a RAM
> application
> > on the AT91SAM7
> > platforms. I've always used ROM applications and
> > used gdb attached to
> > JTAG and used hardware breakpoints.
> > 
> 
> I've tried to step program, but after the step
> command
> debugging hands up. I don't know how to change
> loading
> from RAM to ROM.
> 
> > > Program still don't show any messages or even
> stop
> > at
> > > defined breakpoint.
> > > There are warnings ?No such file or directory.?
> -
> > > program has been compiled on cygwin but gdb was
> > called
> > > from DOS prompt.
> > 
> > You can solve this last one by using the bash
> shell.
> 
> I can't use cygwin-bash because cygwin does not
> recognize COM ports from windows:
"
Windows COM7 on cygwin has /dev/ttyS6:
$ arm-elf-gdb hello
GNU gdb 6.4.0.20051202-cvs
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin
--target=arm-elf"...
(gdb) set remotebaud 38400
(gdb) target remote /dev/ttyS6
Remote debugging using /dev/ttyS6
0x00104954 in Cyg_StdioStreamBuffer::set_buffer
(this=0xd3, size=6,
    new_buffer=0x5
"&#273;\237&#314;\030&#273;\237&#314;\030&#273;\237&#314;\030&#273;\237&#314;4\214\222\213\030&#273;\237&#314;\
030&#273;\237&#314;&#282;")
    at
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/stre
ambuf.cxx:84
84              if (call_free) {
Current language:  auto; currently c++
(gdb) load
Loading section .rom_vectors, size 0x40 lma 0x100000
Loading section .text, size 0x7ba4 lma 0x100040
Loading section .rodata, size 0x238 lma 0x107be4
Loading section .data, size 0x42c lma 0x107e1c
Start address 0x100040, load size 33352
Transfer rate: 26506 bits/sec, 370 bytes/write.
(gdb) break main
Breakpoint 1 at 0x10055c: file hello.c, line 6.
(gdb) continue
Continuing.
"
still after a continue or a step command the gdb hangs
up.

> “
> (gdb) target remote COM7
> get_tty_state failed: Inappropriate ioctl for device
> set_tty_state failed: Inappropriate ioctl for device
> Remote debugging using COM7
> get_tty_state failed: Inappropriate ioctl for device
> set_tty_state failed: Inappropriate ioctl for device
> “
> or even /dev/ttyS7
> 
> Andrew, could you describe me your method of running
> and debugging eCos application, maybe I'm able to
> reproduce it on my hardware. 
> I'd like to ask about configuration of outgoing
> messages. Where can I check if the output of prontf
> commands is ARM-COM1?
> 




 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/

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

Re: [ECOS] eCos and AT91SAM7S-EK

[wavecom wavecom]

> > I've just tried procedure form eCos pdf-s. First,
> I
> > have downloaded the redboot from
> >
>
?\htdocs\boards\redbootbins\at91sam7s\redboot_rom.bin?
> > (cvs path). Now on ARM-COM1 I've got console:):
> > ?
> >  RedBoot(tm) bootstrap and debug environment [ROM]
> > Non-certified release, version UNKNOWN - built
> > 22:08:24, Feb 19 2006
> > 
> > Platform: Atmel (at91sam7s) (ARM7TDMI)
> > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red
> Hat,
> > Inc.
> > 
> > RAM: 0x00200000-0x00210000,
> [0x00206ca0-0x0020c800]
> > available
> > FLASH: 0x00100000 - 0x140000, 1024 blocks of
> > 0x00000100 bytes each.
> > RedBoot>
> > RedBoot>
> 
> O.K. This is good. It shows your download process is
> working.
> 
> > ?
> > 
> > After that I was tried to use gdb:
> > ?
> > C:\cygwin\opt\ecos\ecos-2.0\examples>"c:\Program
> > Files\yagarto\bin\arm-elf-gdb.e
> > xe" -nw hello
> > GNU gdb 6.5.50.20060612-cvs
> > Copyright (C) 2006 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General
> > Public License, and you are
> > welcome to change it and/or distribute copies of
> it
> > under certain conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type
> "show
> > warranty" for details.
> > This GDB was configured as "--host=i686-pc-mingw32
> > --target=arm-elf"...
> > (gdb) set remotebaud 38400
> > (gdb) target remote COM7
> > Remote debugging using COM7
> > 0x00104954 in Cyg_StdioStreamBuffer::set_buffer
> > (this=0xd3, size=6,
> >     new_buffer=0x5
> >
>
"?\237ň\030?\237ň\030?\237ň\030?\237ň■
> >  ŕ\030?\237ň\030?\237ň
> > ╠")
> >     at
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/stre
> > ambuf.cxx:84
> > 84     
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/str
> > eambuf.cxx: No such file or directory.
> >         in
> >
>
/opt/ecos/ecos-2.0/packages/language/c/libc/stdio/current/src/common/
> 
> Are you really using eCos 2.0? It is very old. I
> would suggest you
> update to anoncvs.

This is the newest verion of eCos from CVS, I've only
copied to existing directory.

> 
> > streambuf.cxx
> > Current language:  auto; currently c++
> > (gdb) load
> > Loading section .rom_vectors, size 0x40 lma
> 0x100000
> > Loading section .text, size 0x7ba4 lma 0x100040
> > Loading section .rodata, size 0x238 lma 0x107be4
> > Loading section .data, size 0x42c lma 0x107e1c
> > Start address 0x100040, load size 33352
> > Transfer rate: 26681 bits/sec, 370 bytes/write.
> > (gdb) break main
> > Breakpoint 1 at 0x10055c: file hello.c, line 6.
> > (gdb) cont
> > Continuing.
> 
> You can single step the startup code and see where
> it goes wrong.
> However i've never done this with a RAM application
> on the AT91SAM7
> platforms. I've always used ROM applications and
> used gdb attached to
> JTAG and used hardware breakpoints.
> 

I've tried to step program, but after the step command
debugging hands up. I don't know how to change loading
from RAM to ROM.

> > Program still don't show any messages or even stop
> at
> > defined breakpoint.
> > There are warnings ?No such file or directory.? -
> > program has been compiled on cygwin but gdb was
> called
> > from DOS prompt.
> 
> You can solve this last one by using the bash shell.

I can't use cygwin-bash because cygwin does not
recognize COM ports from windows:
“
(gdb) target remote COM7
get_tty_state failed: Inappropriate ioctl for device
set_tty_state failed: Inappropriate ioctl for device
Remote debugging using COM7
get_tty_state failed: Inappropriate ioctl for device
set_tty_state failed: Inappropriate ioctl for device
“
or even /dev/ttyS7

Andrew, could you describe me your method of running
and debugging eCos application, maybe I'm able to
reproduce it on my hardware. 
I'd like to ask about configuration of outgoing
messages. Where can I check if the output of prontf
commands is ARM-COM1?



 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/

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