* [ECOS]standalone eCos & proc frequency
@ 2001-03-08 3:57 Andrea Acquaviva
2001-03-08 5:29 ` Lewin A.R.W. Edwards
2001-03-13 12:46 ` Jonathan Larmour
0 siblings, 2 replies; 3+ messages in thread
From: Andrea Acquaviva @ 2001-03-08 3:57 UTC (permalink / raw)
To: ecos-discuss
Hi,
I have a 2 simple question:
1. In order to make a standalone eCos program that runs in flash whitout
gdb,
I made the following steps:
- I set Startup type to ROM ( CYG_HAL_STARTUP = ROM) in ecos.ecc
and recompile eCos;
- I linked the program with eCos;
- I converted the elf executable in a binary format and download it
into the flash;
but the executable doesn't work at all.
Is this the correct procedure?
2. When I use gdb, the processor frequency must always be the same for
the gdb stub
and eCos, right?
(I use eCos on an Assabet board.)
Thanks,
Andrea.
--
Ing. Andrea Acquaviva
D.E.I.S. - Universita' di Bologna
V.le Risorgimento, 2 40136 BOLOGNA (ITALY)
Tel: (+39) 051 20 93787 Fax: (+39) 051 2093786
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS]standalone eCos & proc frequency
2001-03-08 3:57 [ECOS]standalone eCos & proc frequency Andrea Acquaviva
@ 2001-03-08 5:29 ` Lewin A.R.W. Edwards
2001-03-13 12:46 ` Jonathan Larmour
1 sibling, 0 replies; 3+ messages in thread
From: Lewin A.R.W. Edwards @ 2001-03-08 5:29 UTC (permalink / raw)
To: Andrea Acquaviva, ecos-discuss
Hi Andrea,
>1. In order to make a standalone eCos program that runs in flash whitout
>gdb,
> I made the following steps:
I strongly suggest you delete your eCos build tree before rebuilding. I had
similar problems, and they were eventually tracked down to un-cleaned-up
leftovers in the build directories. Just move your ecos.ecc out, rm -rf *,
move the ecos.ecc back in, and ecosconfig tree then make.
The procedure you describe is correct, so I'm pretty sure the above is your
problem.
I don't know about your other question.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS]standalone eCos & proc frequency
2001-03-08 3:57 [ECOS]standalone eCos & proc frequency Andrea Acquaviva
2001-03-08 5:29 ` Lewin A.R.W. Edwards
@ 2001-03-13 12:46 ` Jonathan Larmour
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Larmour @ 2001-03-13 12:46 UTC (permalink / raw)
To: Andrea Acquaviva; +Cc: ecos-discuss
Andrea Acquaviva wrote:
>
> Hi,
>
> I have a 2 simple question:
>
> 1. In order to make a standalone eCos program that runs in flash whitout
> gdb,
> I made the following steps:
> - I set Startup type to ROM ( CYG_HAL_STARTUP = ROM) in ecos.ecc
> and recompile eCos;
> - I linked the program with eCos;
> - I converted the elf executable in a binary format and download it
> into the flash;
> but the executable doesn't work at all.
> Is this the correct procedure?
I take it you've succeeded with a similar process when programming RedBoot
(or GDB stubs) right?
> 2. When I use gdb, the processor frequency must always be the same for
> the gdb stub
> and eCos, right?
>
> (I use eCos on an Assabet board.)
The GDB stub acts primarily as a loader, and its debugging abilities are
independent of the clock, so I would guess it wouldn't matter that much
actually.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-03-13 12:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-03-08 3:57 [ECOS]standalone eCos & proc frequency Andrea Acquaviva
2001-03-08 5:29 ` Lewin A.R.W. Edwards
2001-03-13 12:46 ` Jonathan Larmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).