This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
woes on making redboot RAM to be redboot ROM
- From: "liang rainti" <rainti_1212 at hotmail dot com>
- To: ecos-discuss at sources dot redhat dot com
- Cc: bartv at ecoscentric dot com
- Date: Mon, 19 Sep 2005 02:31:43 +0000
- Subject: [ECOS] woes on making redboot RAM to be redboot ROM
- Bcc:
hi,all,
i have successfully made redboot RAM mcf5272 template,but i occured hard
knocks on changing redboot RAM to redboot ROM .
Redboot ROM hung up arch\hal_startup.c"hal_init_ram_sections"
codes.would you give me some hits ?
My Redboot ROM procedure as following:
power-on---- __exception_reset{
move.w #2700, %sr
.extern hal_hardware_init
bra hal_hardware_init
move.l hsr_stack, %sp
lea hw_vsr_stack,%sp
lea 0,%fp
link %fp,#0
.extern hal_reset
jbsr hal_reset
}
----hal_reset()
{
hung up --- hal_init_ram_sections();
#ifdef
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
hal_if_init();
#endif
......
}
hal_init_ram_section()
{
// Initialize the RAM data section from the ROM image of the data
// section.
memcpy(__rom_data_start, __ram_data_start, (size_t)__ram_data_size);
// Initialize the bss and sbss sections to zero.
memset(__bss_start, 0, (size_t)__bss_size);
memset(__sbss_start, 0, (size_t)__sbss_size);
}
attachment is my linker script for ROM,and "m68k.ld" "vector.S"
_________________________________________________________________
与联机的朋友进行交流,请使用 MSN Messenger: http://messenger.msn.com/cn
Attachment:
mlt_m68k_mcf52xx_mcf5235_mcf5235evb_rom.ldi
Description: Binary data
Attachment:
mlt_m68k_mcf52xx_mcf5235_mcf5235evb_rom.h
Description: Binary data
Attachment:
vectors.S
Description: Text document
Attachment:
m68k.ld
Description: Text document
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss