This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: an incompatibility between redboot/decompress.c v1.7,redboot/main.c v1.36, redboot/net/net_io.c v1.31 and ASSERT in a ROM build
- From: Mark Salter <msalter at redhat dot com>
- To: stephen dot goadhouse at adiengineering dot com
- Cc: gthomas at ecoscentric dot com, ecos-discuss at sources dot redhat dot com
- Date: Wed, 25 Sep 2002 15:46:41 -0400
- Subject: Re: [ECOS] an incompatibility between redboot/decompress.c v1.7,redboot/main.c v1.36, redboot/net/net_io.c v1.31 and ASSERT in a ROM build
- References: <NEBBILPKDKKCCPHDKENAAEIIFAAA.stephen.goadhouse@adiengineering.com>
>>>>> Stephen Goadhouse writes:
> Sorry I did not include it. Here it is:
> +$T0a0f:feffffff;0d:48d400c0;#1f+$T0a0f:feffffff;0d:48d400c0;#1f
> The value 0x48d400c0 makes no sense to me. This is an invalid section of
> our memory map, so I don't expect it to be an address.
How about 0xc000d448? ;-)
That's the SP address, BTW.
The PC address of 0xfffffffe doesn't make any sense either. Kinda points
to stack corruption.
> If I retarget the build so that the ROM version starts at Flash address
> 0x140000, I get the following GDB messages when I tried to bootup at
> 0x140000:
> +$T0a0f:feffffff;0d:38d400c0;#1e+$T0a0f:feffffff;0d:38d400c0;#1e
> Also, I discovered that decompress.c v1.6 is okay. It's only decompress.c
> v1.7 along with main.c v1.35 and net_io.c v1.31 that cause this to happen.
You'll also need an updated services/compress/zlib/current/inflate.c v1.2
which has a related fix to go along with decompress.c.
--Mark
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss