From: Jens-Christian Lache <lache@tu-harburg.de>
To: crossgcc@sourceware.cygnus.com
Subject: ARM7TDMI/At91M40xxx on At91EB01 with Angel monitor
Date: Sat, 11 Nov 2000 07:40:00 -0000 [thread overview]
Message-ID: <Pine.HPX.4.21.0011111637180.14889-100000@erasmus.rz.tu-harburg.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
Hi everybody!
I´ am new to the mailing-list crossgcc. Since last week I have to deal with
an ARM7TDMI proc. on an At91EB01 board from Atmel. This board includes Angel
as monitor program.
If there is anybody, how has experience with these components and how wants to
"chat"
with me, please do so!!
I managed to compile the components binutil, gcc, insight as explained in
http://sources.redhat.com/ecos/install-linux.html --> ARM target.
I didn´t applied the patch for eCos for gcc, it just didn´t compile with it.
I have to check out, what´s in the At91M40xxx/ARM7TDMI. So eCos is an option
for me, but not
that important at the moment.
I have found a crt0.S file in arm-uc-libc.tar.gz and in
tar:/home/yo/uC-libc-310899.tar.gz
Does this file (see below) work with the angel debug monitor? I am really
afraid to delete s.th. in
the flash while installing the gdb-stubs. With this evaluation board also
shipps an evaluation version
of MULTI, which also includes a crt0 file. Is this file compiler-depened?
Is there an other mailing list, which could be usefull for me?
Thanks a lot!
Jens-Christian Lache
--
Jens-Christian Lache
www.tu-harburg.de/~sejl1601
lache@ngi.de
lache@tu-harburg.de
Tel.: 01759610756 (Hamburg)
.global __start
.global __main
.global _end
.global __data_start
.bss
.global environ
environ:
.long 0
.text
__start:
nop
nop
movea.l %d5, %a5
move.l 8(%sp), %d5
move.l %d5, environ(%a5)
bsr main
move.l %d0,%sp@-
bsr exit /* Invoke exit() routine */
#ifdef NO_LIBGCC
/* If that didn't kill us, ... */
_exit:
move.l %sp@+,%d1
moveq #1,%d0 /* SYS_exit */
trap #0
__main:
rts
#else
.global _cleanup
_cleanup:
move.l %sp@+,%d1
moveq #1,%d0 /* SYS_exit */
trap #0
#endif /* NO_LIBGCC */
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-11-11 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 7:40 Jens-Christian Lache [this message]
2000-11-11 14:13 ` CharPtr to double Manuel Molina
2000-11-13 1:48 ` ARM7TDMI/At91M40xxx on At91EB01 with Angel monitor Richard Earnshaw
2000-11-13 1:55 ` Jens-Christian Lache
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.HPX.4.21.0011111637180.14889-100000@erasmus.rz.tu-harburg.de \
--to=lache@tu-harburg.de \
--cc=crossgcc@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).