This is the mail archive of the ecos-discuss@sources.redhat.com 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: Size of Standalone Flash based redboot image


We did try out the changes you mentioned. Here is the problem that we are facing:

Our current code size is around 220K. If we add code (even a printf statement) to any file say file1.c, then the
system misbehaves. It hangs at some random location. Then, if we delete
some (totally unrelated ) code in another file say file2.c, and recompile, the board comes up successfully.


This leads us to conclude that increase in code size results in unstable behavior. Please let us have suggestions to overcome this
issue.


Thanks,
G.Muruganandam


At 09:37 PM 3/24/2004 +0100, Andrew Lunn wrote:
On Wed, Mar 24, 2004 at 12:10:04PM -0800, G.Muruganandam wrote:
> Hi,
>

> I understand that the standalone flash based Redboot image occupies
> flash address 0x00000000 to 0x0003ffff.  I would like to increase
> the size allocated for the flash image.

The location and size of the image depends on the platform.

To change it you need to change the platform memory map. You need to
edit the mlt_*_rom.ldi and mlt*_rom.h files for your
platform. Increase the symbol CYGMEM_REGION_rom_SIZE in the .h and the
rom LENGTH in the .ldi.

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]