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]

What Generates mlt_arm_xscale_ixdp425_rom.h & SDRAM Configuration


Hello all,

I am bringing up a custom board and am modifying the ixdp425 RedBoot to fit
our changes. One thing I noticed is that there are several places that need
to be modified to accomplish changes to the SDRAM size and configuration
(yes I have read the Intel document on customizing RedBoot, and it does not
cover all). Things are beginning to run, but it was a somewhat painful
process of discovery.


What generates the:

	
packages/hal/arm/xscale/ixdp425/current/include/pkgconf/mlt_arm_xscale_ixdp4
25_rom.h

file? It says it is automatically generated, but what do I change and then
invoke to generate this updated file? I see that a lot of ram & heap values
are hard defined in this, but would it be better to get them automatically
based on the (the below) memory initialization information?


In:
	packages/hal/arm/xscale/ixdp425/current/include/ixdp425.h

is there a reason why SDRAM_SIZE is not based on IXP425_SDRAM_CONFIG_INIT
settings as this is what determines the available SDRAM? Is there a better
platform startup that actually looks at some GPIO bits (or eeprom) and
determines the SDRAM size on the fly (we are considering supporting several
memory sizes, and would like to no have different code images)? 

Much thanks for entertaining my questions,

Steven J. Herbold
Viadux, Inc.
San Diego, CA 92121 

-- 
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]