This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: Redboot run issues when HAL_MMU_OFF is issued
- From: "Chris Zimman" <czimman at bloomberg dot com>
- To: "joseph biswal" <joseph dot biswal at gmail dot com>, <ecos-discuss at sources dot redhat dot com>, <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 2 Mar 2009 11:34:12 -0500
- Subject: RE: [ECOS] Redboot run issues when HAL_MMU_OFF is issued
> The issue looks like when i do a "RUN" of this same working piece of
> image out of RAM,
> it seems to get stuck.
>
> I debugged using BDI breakpoints as well as "diag_printfs" and looks
> like it does not go beyond ?HAL_MMU_OFF in
> packages/hal/arm/mx31/ads/current/src/redboot_cmds.c. I don't
> understand the flow in LaunchrunImage() ?since it falls on the thin
> line of swtching the MMU on and off. Any hints?
>
> I had previously been successful in loading another version of redboot
> but the only difference i notice on the serial console is in the
> following line:
> RAM: 0x00000000-0x0ff00000, [0x00014020-0x0fed1000] available
>
> The start address 0x00014020 which refers to "heap1" in the redboot
> code seems to be different. Any one has an idea on as to how do i
> trace this start address of RAM?
>
>
>
> void launchRunImg(unsigned long addr)
> {
> ? asm volatile ("mov r12, r0;");
> ? HAL_CLEAN_INVALIDATE_L2();
> ? HAL_DISABLE_L2();
> ? HAL_MMU_OFF();
If you're turning off the MMU and the code is in remapped space that's not
1-1 (eg. phys addr == virt addr), this isn't going to work.
I still don't understand overall what it is that you're trying to do.
--Chris
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss