[ECOS] --entry= (slightly off topic)
Fabrice Gautier
Fabrice_Gautier@sdesigns.com
Thu Sep 20 15:18:00 GMT 2001
I think you have it right, but setting the entry point does'nt influence the
memory map. It just set some value in the elf headers.
What is the result of objdump -f on the resulting elf file? It should
display the start adress (ake entry-point)
> -----Original Message-----
> From: Trenton D. Adams [ mailto:tadams@theone.dnsalias.com ]
> Sent: Thursday, September 20, 2001 3:08 PM
> To: 'eCos Discussion'
> Subject: [ECOS] --entry= (slightly off topic)
>
>
> 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
>
More information about the Ecos-discuss
mailing list