[ECOS] Mmu and Memory Layout

[Dan Conti]

You shouldn't have to modify the mlt files for that. If you take a look,
under the Cirrus board you can choose between RAM and ROM startup. ROM
startup implies no gdb, and will generate images linked to 0xe0000000.
All you need to do is compile your test program against a ROM kernel,
objcopy it to bin, then burn it onto the board.

I recommend saving your ROM kernel into a new directory.

-Dan

> -----Original Message-----
> From: Nicola Bergamin [BW] [ mailto:nicola.bergamin@bluewind.it ]
> Sent: Tuesday, June 12, 2001 9:34 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Mmu and Memory Layout
> 
> 
> 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?
> 
> Thankyou 
> - Nicola
> 
> 
> ------------------------------------------
>  Nicola Bergamin
>  BlueWind Embedded Systems Design
>  Via Steffani, 7/B
>  I-31033 Castelfranco Veneto (TV)
> 
>  Office: +39 0 423 723431
>  Fax   : +39 0 423 744738
>  GSM   : +39 335 7556736
>  mailto:nicola.bergamin@bluewind.it
>  http://www.bluewind.it
> ------------------------------------------
> 
>