This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
--entry= (slightly off topic)
- To: "'eCos Discussion'" <ecos-discuss at sourceware dot cygnus dot com>
- Subject: [ECOS] --entry= (slightly off topic)
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Thu, 20 Sep 2001 16:08:02 -0600
I'm doing the following. stack_manager.s doesn't have any entry points,
and I don't know how to make one. So, I figured I'd just pass
--entry=0x0 to the linker which should create the entry at 0.
arm-elf-gcc.exe -nostdlib -nostartfiles -O1 -Wl,--entry=0x0
stack_manager.s bootcode-J3-rev4.c
stack_manager.s
However, it ends up like this.
00008000 <Prepare_To_Flash-0xc>:
8000: e3a0d201 mov sp, #268435456 ; 0x10000000
8004: e38ddc96 orr sp, sp, #38400 ; 0x9600
8008: ebffffff bl 800c <Prepare_To_Flash>
8000 is the default entry point, and that's not what I want. I want
0x00000000.
So, how do I either:
- create an entry point in stack_manager.s
- specify an entry point on the command line
???
I tried a
start:
label before the first instruction in the .s file, but that didn't work.
Trenton D. Adams
Extreme Engineering
#17, 6025 - 12 St. SE
Calgary, Alberta, Canada
T2H 2K1
Phone: 403 640 9494 ext-208
Fax: 403 640 9599
http://www.extremeeng.com