[ECOS] Mmu and Memory Layout

[honda@itri.org.tw]

Hello,

     What's the main difference in  the MMU configuration and Memory Layout
between the 1.3.1 and the current version. Version 1.3.1 did work on
EDB7212, it hang on the MMU_INITIALIZE. But when I modified it for my own
system, it didn't work. By upgrade to the current version, it works. Why?

Kuang-Yang Chuang

OES / ITRI
J220, Bldg. 78, 195-8, Sec. 4, Chung-Hsing Rd.
Chutung, Hsinchu 310, Taiwan, ROC

TEL: 886-3-5917546
FAX: 886-3-5917531

=============================================================================
Since you're starting fresh - please don't use 1.3.1 - it's way too
old and we won't be able to help you much.  Start from the current
anonymous CVS.

Other than that, you have the basic grasp of what needs to be done.

On 12-Jun-2001 Nicola Bergamin [BW] wrote:
> Hi,
> I'm trying to create a new memory layout and mmu mapping  for
> my special board, similar but not same as Cirrus EDB7212 -using
> eCos v1_3_1.
>
> I want to build and program into flash a standalone application, the
> hello world, for example, possibly without using Gdb stuff.
>
> I want just to put the program into flash, and the application must
> be running after power cycle.
>
>>From the eCos User's Guide (page 89), i see that to change
> memory layout it is necessary to modify the mlt_* files in
>
> /ecos/packages/hal/arm/edb7xxx/v1_3_1/include/pkgconf/, and ,
> for a rom application, I intend to modify the following files:
>
> mlt_arm_edb7212_rom.h
> mlt_arm_edb7212_rom.ldi
> mlt_arm_edb7212_rom.mlt
>
> For the mmu, I've seen that this file:
>
> hal_platform_setup.h (/ecos/packages/hal/edb7xxx/v1_3_1/include)
> does the mmu initialization.
>
> Is there any other important file to take care of?
>