This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RE: networking support for my eCos application


> MEMORY
> {
>     ram : ORIGIN = 0x20000000, LENGTH = 0x00C00000
>     rom : ORIGIN = 0x20C00000, LENGTH = 0x00400000
>     sram : ORIGIN = 0x00000100, LENGTH = 0x00023F00
> }
> 
> versus this for the older (working) version:
> 
> MEMORY
> {
>     ram : ORIGIN = 0x20000000, LENGTH = 0x02000000
>     sram : ORIGIN = 0x00000000, LENGTH = 0x00024000
> }
> 
> 
> Can anyone provide a little clarification on how these files are generated and what I may have screwed up in my config.

The linker file is derived from you hal include/pkgconf/*.ldi files.

My guess is your working binary is a RAM startup application, but your
new application is a ROM startup. Take a look at the value of
CYG_HAL_STARTUP in your working and none working configuration.

                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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]