This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ecos redboot compile problem.
- From: "Doyle, Patrick" <WPD at dtccom dot com>
- To: "'Beymer, Mike'" <Mike dot Beymer at itron dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 25 Apr 2003 14:45:20 -0400
- Subject: RE: [ECOS] ecos redboot compile problem.
> Another point just discovered,
> An arm-elf-objdump -h of redboot.img reveals .rom_vectors as
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> arm-elf-objdump -h of redboot-SRAM.out show .rom_vectors as
> CONTENTS, ALLOC, LOAD, CODE
>
I don't know why it changed from when I created redboot-SRAM.out to now, but
it doesn't matter. The READONLY attribute is just a flag to loader.
RedBoot, at startup just scribbles to locations in SRAM (which is writable,
despite what hints might be in some files somewhere on the host computer),
so why do you think that is putting you in an infinite loop?
> if the READONLY means that code is not allowed to be
> changed i.e. protected
> space. Then trying to rewrite the 0x12345678 and 0x87654321
> would fail and
> put me into an infinite loop. How do I get this READONLY
> turned off??
--wpd
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss