This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Redboot and Ecos build for IQ80310 eval board
- To: khatri at us dot ibm dot com
- Subject: Re: [ECOS] Redboot and Ecos build for IQ80310 eval board
- From: Mark Salter <msalter at redhat dot com>
- Date: Thu, 30 Aug 2001 23:24:57 -0400
- CC: ecos-discuss at sources dot redhat dot com
- References: <OF9314C74F.04AE1C9E-ON85256AB8.0045B641@raleigh.ibm.com>
>>>>> Barry Khatri writes:
> Hi All,
> I am using the xscale tools from the CD that came with the iq80310 eval
> board. I have built the redboot using the ecosconfig tool version 1.4.13
> and the source from CVS dated 8/23/2001.
How are you configuring and building RedBoot?
> Problem 1:
> I have flashed the redboot.bin file using the flash utility provided on the
> CD. After flashing the redboot.bin that I built, The iq80310 hangs with
> LED's "04". In my debug I have found that the code in vectors.s module
> where it copies ROM data to RAM, it overwrites the code being executed.
The code is being executed from flash in low memory. RAM is above 0xA0000000.
> Problem 2:
> I also build ecos build and tests for iq80310 platform using the ecosconfig
> tool version 1.3.14 and the source from CVS dated 8/23/2001. I flashed the
> redboot.bin from the CD that came with the iq80310 ( which works by the way
> and connection is made via serial and ethernet link to GDB host ). When
> downloading the ecos test; the GDB communications stops with target almost
> right after ROM vectors are loaded. I noticed that when I change the memory
> for target RAM starts at 0xA0000000 instead of 0 and build both ecos and
> the ecos tests; I am able to load the ecos test. When I run the test, again
> the iq80310 hangs with LED's "04".
Usable RAM starts at 0xa000A000. The area below that is used for
exception vectors and the mmu page table.
--Mark