RE: [ECOS] which gcc toolchain to use ?

RE: [ECOS] which gcc toolchain to use ?

[Harsha D]

Gary,

As i said earlier ... my redboot hangs in do_version.  (at the place
where the RAM range is printed).
I thought may be optimization flag was playing around..(as was in the
case of v4.0).  So just tried 
removing it.

Even then how can optimization flag effect the working of redboot as a
whole ? 


Andrew, 

I just went around looking for the toolchain and i came across this "
... some problems with gnu 
tools on cygwin... ecos on cygwin is not supported... "

And Now i have this doubt "Development on cygwin?" or "Development on
linux?".  Although i am 
more comfortable working on windows, i would definitely like to avoid
extra work needed (if its 
the case) to make it work using cygwin.


regards
hasha


-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: 26 July 2005 18:36
To: Andrew Lunn
Cc: Harsha D; eCos Discussion
Subject: Re: [ECOS] which gcc toolchain to use ?


On Tue, 2005-07-26 at 11:48 +0200, Andrew Lunn wrote:
> On Tue, Jul 26, 2005 at 02:54:57PM +0530, Harsha D wrote:
> > Hi
> > 
> > I have been trying to port ecos on ARM9 based board.
> > I tried with gcc v4.0 (cygwin) and gcc v3.4.3
> > 
> > 
> > In my case i have observed that
> > 
> > in v4.0 > 
> > 	Removing optimization(O2) flag... redboot works
> > 	Including optimization flag... redboot fails 
> > 
> > in v3.4.2	>
> > 	Removing optimization flag... redboot FAILS
> > 	Including optimization flag... redboot works
> > 
> > 
> > also....redboot seems to hang at do_version, printing the RAM range.
> > 
> > 
> > I would like to know which is the best/suitable gcc toolchain to be
used
> > with eCos
> 
> See:
> 
> http://ecos.sourceware.org/getstart.html
> 
> Get the toolchains from there. They are known to work well.

I've also had good luck with 3.4.3.  However, I never build
without optimization (why would you want to?)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


--
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] which gcc toolchain to use ?

[Andrew Lunn]

> Andrew, 
> 
> I just went around looking for the toolchain and i came across this "
> ... some problems with gnu 
> tools on cygwin... ecos on cygwin is not supported... "
> 
> And Now i have this doubt "Development on cygwin?" or "Development on
> linux?".  Although i am 
> more comfortable working on windows, i would definitely like to avoid
> extra work needed (if its 
> the case) to make it work using cygwin.

The toolchain available for download from the eCos site works OK on
cygwin. The configtool has problem with modern versions of cygwin. To
fix that you want to use a recent snapsnot. You can download that from
www.ecoscentric.com, from the DevZone section, or just use the CLI
tool, ecosconfig.

Having said that, i beleave most of the maintainers use Linux as there
host platform. Its generally just less hassle. Also, using the
synthetic target is very useful and it is Linux only.

        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

[ECOS] "Fis init" failed on EB40A

[Jaws]

Hi all,
    I have some problem with flash and fis commands.
I' using the EB40A with the redboot versio

RedBoot> version

RedBoot(tm) bootstrap and debug environment [ROM]
SRI release, ATMEL bootstrap v2.20 - built 11:05:22, Mar  6 2002

Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)
Copyright (C) 2000, 2001, Red Hat, Inc.

RAM: 0x00000000-0x00040000, 0x00009b98-0x0002f000 available
FLASH: 0x01000000 - 0x01200000, 32 blocks of 0x00010000 bytes each.
RedBoot>

when I tried to make the command "fis init' this is the result:

RedBoot>
RedBoot> fis init
About to initialize [format] FLASH image system - are you sure (y/n)? y
*** Initialize FLASH Image System
    Warning: device contents not erased, some blocks may not be usable
... Erase from 0x011f0000-0x01200000: $T0a0f:80018001;0d:e43d0000;#7b

and I have to reset the board.
Any suggestions?

Thanks in advance
Jaws

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

[ECOS] Re: "Fis init" failed on EB40A

[Jani Monoses]

> RedBoot>
> RedBoot> fis init
> About to initialize [format] FLASH image system - are you sure (y/n)? y
> *** Initialize FLASH Image System
>     Warning: device contents not erased, some blocks may not be usable
> ... Erase from 0x011f0000-0x01200000: $T0a0f:80018001;0d:e43d0000;#7b
> 
> and I have to reset the board.
> Any suggestions?

I wonder if it could be the flash bug mentioned in atmel erratas.
Is CYGHWR_DEVS_FLASH_ATMEL_AT49XXXX_ERASE_BUG_WORKAROUND set
in the at49 flash driver cdl?
Jani


-- 
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] Re: "Fis init" failed on EB40A

[Domenico La Fauci]

Thanks for your reply,
    but that flag is already set.
Any other idea?

Jaws

----- Original Message ----- 
From: "Jani Monoses" <jani@iv.ro>
To: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, July 27, 2005 1:17 PM
Subject: [ECOS] Re: "Fis init" failed on EB40A


> 
> > RedBoot>
> > RedBoot> fis init
> > About to initialize [format] FLASH image system - are you sure (y/n)? y
> > *** Initialize FLASH Image System
> >     Warning: device contents not erased, some blocks may not be usable
> > ... Erase from 0x011f0000-0x01200000: $T0a0f:80018001;0d:e43d0000;#7b
> > 
> > and I have to reset the board.
> > Any suggestions?
> 
> I wonder if it could be the flash bug mentioned in atmel erratas.
> Is CYGHWR_DEVS_FLASH_ATMEL_AT49XXXX_ERASE_BUG_WORKAROUND set
> in the at49 flash driver cdl?
> Jani
> 
> 
> -- 
> 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

[ECOS] Re: "Fis init" failed on EB40A

[Jani Monoses]

Domenico La Fauci wrote:
> Thanks for your reply,
>     but that flag is already set.
> Any other idea?
> 

fis init -f ?

Jani


-- 
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] Re: "Fis init" failed on EB40A

[Domenico La Fauci]

Same result!


----- Original Message ----- 
From: "Jani Monoses" <jani@iv.ro>
To: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, July 27, 2005 1:38 PM
Subject: [ECOS] Re: "Fis init" failed on EB40A


> Domenico La Fauci wrote:
> > Thanks for your reply,
> >     but that flag is already set.
> > Any other idea?
> > 
> 
> fis init -f ?
> 
> Jani
> 
> 
> -- 
> 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

Re: [ECOS] "Fis init" failed on EB40A

[Dirk Eibach]

Hi,

>     I have some problem with flash and fis commands.
> I' using the EB40A with the redboot versio

> Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)

Did it come to your mind that there might be a major difference between 
EB40 and EB40A?

EB40A is not supported in ecos 2.0, you have to use cvs.

Cheers
Dirk


-- 
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] "Fis init" failed on EB40A

[Jaws]

Hi Dirk,
i know the difference beetwen the two platforms, but i don't know why the
atmel provide the redboot with the version string "EB40" on the directory
EB40A. So the dubt could be an error on the version string or ont hte
directory name. Anyway the EB40A is supported on ecos 2.01 infact the
redboot image build for my platform is compiled from that version and the
EB40A template exist in it.
My problem is that when I run the RAM version of my redboot on EB40A,
everithing works fine, also the fis init comamnds and so on, But when i
tried to launch the ROM or ROMRAM version the result is the same:

$T0a0f:a08c0202;0d:eccf0e02;#71
$T0a0f:a08c0202;0d:eccf0e02;#71
$T0a0f:a08c0202;0d:eccf0e02;#71

for each time I pressed Enter. i supposed it was a problem related to a
change in the serial baudrate, but I tried different rate with similar
output but nothing related to redboot prompt.

any idea about this?

Thanks
Jaws



----- Original Message -----
From: "Dirk Eibach" <eibach@gdsys.de>
To: <jaws75@tiscali.it>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Wednesday, July 27, 2005 2:55 PM
Subject: Re: [ECOS] "Fis init" failed on EB40A


> Hi,
>
> >     I have some problem with flash and fis commands.
> > I' using the EB40A with the redboot versio
>
> > Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)
>
> Did it come to your mind that there might be a major difference between
> EB40 and EB40A?
>
> EB40A is not supported in ecos 2.0, you have to use cvs.
>
> Cheers
> Dirk
>

-- 
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] "Fis init" failed on EB40A

[Gary Thomas]

On Wed, 2005-07-27 at 18:50 +0200, Jaws wrote:
> Hi Dirk,
> i know the difference beetwen the two platforms, but i don't know why the
> atmel provide the redboot with the version string "EB40" on the directory
> EB40A. So the dubt could be an error on the version string or ont hte
> directory name. Anyway the EB40A is supported on ecos 2.01 infact the
> redboot image build for my platform is compiled from that version and the
> EB40A template exist in it.
> My problem is that when I run the RAM version of my redboot on EB40A,
> everithing works fine, also the fis init comamnds and so on, But when i
> tried to launch the ROM or ROMRAM version the result is the same:
> 
> $T0a0f:a08c0202;0d:eccf0e02;#71
> $T0a0f:a08c0202;0d:eccf0e02;#71
> $T0a0f:a08c0202;0d:eccf0e02;#71
> 
> for each time I pressed Enter. i supposed it was a problem related to a
> change in the serial baudrate, but I tried different rate with similar
> output but nothing related to redboot prompt.

No, this message tells you that RedBoot got an error, probably within
the FLASH access code itself.  In this case the code was executing
at location 0x02028CA0 - you can look this up in your ROM .elf image.

What you see is GDB strings which indicate the failure.  Unless you
connect with a GDB client, you won't be able to make much sense of them.
If you type characters, it will just spit out the same string (unless
you know how to type GDB internal protocol!)

> 
> any idea about this?
> 
> Thanks
> Jaws
> 
> 
> 
> ----- Original Message -----
> From: "Dirk Eibach" <eibach@gdsys.de>
> To: <jaws75@tiscali.it>
> Cc: <ecos-discuss@ecos.sourceware.org>
> Sent: Wednesday, July 27, 2005 2:55 PM
> Subject: Re: [ECOS] "Fis init" failed on EB40A
> 
> 
> > Hi,
> >
> > >     I have some problem with flash and fis commands.
> > > I' using the EB40A with the redboot versio
> >
> > > Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)
> >
> > Did it come to your mind that there might be a major difference between
> > EB40 and EB40A?
> >
> > EB40A is not supported in ecos 2.0, you have to use cvs.
> >
> > Cheers
> > Dirk
> >

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
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] "Fis init" failed on EB40A

[Paul D. DeRocco]

> From: Jaws
>
>     I have some problem with flash and fis commands.
> I' using the EB40A with the redboot versio
>
> RedBoot> version
>
> RedBoot(tm) bootstrap and debug environment [ROM]
> SRI release, ATMEL bootstrap v2.20 - built 11:05:22, Mar  6 2002
>
> Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)
> Copyright (C) 2000, 2001, Red Hat, Inc.
>
> RAM: 0x00000000-0x00040000, 0x00009b98-0x0002f000 available
> FLASH: 0x01000000 - 0x01200000, 32 blocks of 0x00010000 bytes each.
> RedBoot>
>
> when I tried to make the command "fis init' this is the result:
>
> RedBoot>
> RedBoot> fis init
> About to initialize [format] FLASH image system - are you sure (y/n)? y
> *** Initialize FLASH Image System
>     Warning: device contents not erased, some blocks may not be usable
> ... Erase from 0x011f0000-0x01200000: $T0a0f:80018001;0d:e43d0000;#7b
>
> and I have to reset the board.
> Any suggestions?

Are you running with the two halves of the flash swapped? I'm not sure the
driver is smart enough to deduce that.

--

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com


-- 
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] "Fis init" failed on EB40A

[Domenico La Fauci]

Hi Paul,
    sorry but I don't understand what you said. Could you please explain me?
Now I have a new version of Redboot for EB40A that works with all of fis
commands.
The problem that I have now is that the RAM version of redboot works
properly but the ROM or ROMRAM version doesn't start. when the board is
powered up led D1-D5 are on but no communication the serial line.

When I tried to load the ROM version in RAM and launch it, this is the
result:

RedBoot> fis lis
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0x01000000  0x01000000  0x00020000  0x00000000
RedBoot[ROM]      0x01100000  0x01100000  0x00010000  0x02024C00
FIS directory     0x011F0000  0x011F0000  0x0000F000  0x00000000
RedBoot config    0x011FF000  0x011FF000  0x00001000  0x00000000

RedBoot>
RedBoot> fis load RedBoot[ROM] -b %{FREEMEMLO}
RedBoot> go
$T0a0f:a04c0202;0d:eccf0e02;#6d

connecting the gdb this is the function where the program is blocked:

$ arm-elf-gdb redboot.elf
GNU gdb 5.3 (eCosCentric)
Copyright 2002 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) tar rem /dev/ttyS3
Remote debugging using /dev/ttyS3
0x02024ca0 in __remcomOutBuffer ()
(gdb) l

Any idea??

Thanks in advance
Jaws

----- Original Message -----
From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Sent: Wednesday, July 27, 2005 7:06 PM
Subject: RE: [ECOS] "Fis init" failed on EB40A


> > From: Jaws
> >
> >     I have some problem with flash and fis commands.
> > I' using the EB40A with the redboot versio
> >
> > RedBoot> version
> >
> > RedBoot(tm) bootstrap and debug environment [ROM]
> > SRI release, ATMEL bootstrap v2.20 - built 11:05:22, Mar  6 2002
> >
> > Platform: Atmel AT91/EB40 (AT91R40807 ARM7TDMI)
> > Copyright (C) 2000, 2001, Red Hat, Inc.
> >
> > RAM: 0x00000000-0x00040000, 0x00009b98-0x0002f000 available
> > FLASH: 0x01000000 - 0x01200000, 32 blocks of 0x00010000 bytes each.
> > RedBoot>
> >
> > when I tried to make the command "fis init' this is the result:
> >
> > RedBoot>
> > RedBoot> fis init
> > About to initialize [format] FLASH image system - are you sure (y/n)? y
> > *** Initialize FLASH Image System
> >     Warning: device contents not erased, some blocks may not be usable
> > ... Erase from 0x011f0000-0x01200000: $T0a0f:80018001;0d:e43d0000;#7b
> >
> > and I have to reset the board.
> > Any suggestions?
>
> Are you running with the two halves of the flash swapped? I'm not sure the
> driver is smart enough to deduce that.
>
> --
>
> Ciao,               Paul D. DeRocco
> Paul                mailto:pderocco@ix.netcom.com
>
>
> --
> 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

Re: [ECOS] "Fis init" failed on EB40A

[Andrew Lunn]

On Thu, Jul 28, 2005 at 05:22:32PM +0200, Domenico La Fauci wrote:
> Hi Paul,
>     sorry but I don't understand what you said. Could you please explain me?
> Now I have a new version of Redboot for EB40A that works with all of fis
> commands.
> The problem that I have now is that the RAM version of redboot works
> properly but the ROM or ROMRAM version doesn't start. when the board is
> powered up led D1-D5 are on but no communication the serial line.
> 
> When I tried to load the ROM version in RAM and launch it, this is the
> result:
> 
> RedBoot> fis lis
> Name              FLASH addr  Mem addr    Length      Entry point
> RedBoot           0x01000000  0x01000000  0x00020000  0x00000000
> RedBoot[ROM]      0x01100000  0x01100000  0x00010000  0x02024C00
> FIS directory     0x011F0000  0x011F0000  0x0000F000  0x00000000
> RedBoot config    0x011FF000  0x011FF000  0x00001000  0x00000000
> 
> RedBoot>
> RedBoot> fis load RedBoot[ROM] -b %{FREEMEMLO}
> RedBoot> go

This will not work. eCos is position dependant. The ROM version is
linked so that it runs at the address location the ROM is at. 

Another thing a ROM version might do is setup the RAM controller. With
most processors, setting up the RAM controller when running in RAM
will cause a crash.

So if you want to run the ROM version you need to put it into ROM. I
suggest you have a JTAG flash programmer handy. If your ROM image does
not boot you have a dead board which you can only recover using the
programmer.

        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] "Fis init" failed on EB40A

[Jaws]

Thanks Andrew,
    I did also this test with  JTAG programmer but the ROM or ROMARAM
version doesn't work.
The board remains blocked. I don't understand why the RAM version work
properly and the ROm version doesn't.
Could be a problem related to the startup? How can I investigate this
problem?

Thanks
Jaws

----- Original Message -----
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Domenico La Fauci" <mlafauci@tiscali.it>
Cc: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Sent: Thursday, July 28, 2005 5:35 PM
Subject: Re: [ECOS] "Fis init" failed on EB40A


> On Thu, Jul 28, 2005 at 05:22:32PM +0200, Domenico La Fauci wrote:
> > Hi Paul,
> >     sorry but I don't understand what you said. Could you please explain
me?
> > Now I have a new version of Redboot for EB40A that works with all of fis
> > commands.
> > The problem that I have now is that the RAM version of redboot works
> > properly but the ROM or ROMRAM version doesn't start. when the board is
> > powered up led D1-D5 are on but no communication the serial line.
> >
> > When I tried to load the ROM version in RAM and launch it, this is the
> > result:
> >
> > RedBoot> fis lis
> > Name              FLASH addr  Mem addr    Length      Entry point
> > RedBoot           0x01000000  0x01000000  0x00020000  0x00000000
> > RedBoot[ROM]      0x01100000  0x01100000  0x00010000  0x02024C00
> > FIS directory     0x011F0000  0x011F0000  0x0000F000  0x00000000
> > RedBoot config    0x011FF000  0x011FF000  0x00001000  0x00000000
> >
> > RedBoot>
> > RedBoot> fis load RedBoot[ROM] -b %{FREEMEMLO}
> > RedBoot> go
>
> This will not work. eCos is position dependant. The ROM version is
> linked so that it runs at the address location the ROM is at.
>
> Another thing a ROM version might do is setup the RAM controller. With
> most processors, setting up the RAM controller when running in RAM
> will cause a crash.
>
> So if you want to run the ROM version you need to put it into ROM. I
> suggest you have a JTAG flash programmer handy. If your ROM image does
> not boot you have a dead board which you can only recover using the
> programmer.
>
>         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