Problems with MMU on PXA255

From: Christoph Baumann (cb_at_sorcus.com)
Date: 06/09/04 

Date: Wed, 09 Jun 2004 16:03:22 +0200

Hi!

Currently i'm developing a boot loader for a custom PXA255-based board.
Everything seems to work fine so far. What causes me troubles is the
access of hardware connected via CS1-4. Without MMU the HW behaves as
expected but with MMU (CS1 is mapped from 0x0400_0000 to 0x9000_0000 as
section with R/W access) the system crashes. The settings for this
mapping are the same as for memory mapped IO (not cachable, not
bufferable) which work fine. Any ideas?

Christoph

Relevant Pages

  • Problem with MMU on PXA255
    ... Currently i'm developing a boot loader for a custom PXA255-based board. ... What causes me troubles is the ... Without MMU the HW behaves as ...
    (microsoft.public.windowsce.embedded)
  • Re: Problems with MMU on PXA255
    ... > Currently i'm developing a boot loader for a custom PXA255-based board. ... What causes me troubles is the ... > section with R/W access) the system crashes. ...
    (comp.os.linux.embedded)
  • Re: MMU questions
    ... It depends on the boot loader. ... The only requirement is that the MMU is OFF ... enable the cache as some CPUs require the MMU for caching. ... Steve Maillet ...
    (microsoft.public.windowsce.platbuilder)
  • Re: how to use ICE to debug eboot under platbuilder?
    ... eboot.exe is renamed to nk.exe in the boot.bib files for the boot loader. ... Typically ICE debuggers will stop at the reset vector for the ... the code after the MMU is on using a hardware breakpoint with the new ... virtual address (Even if it's a 1:1 mapping you need a hardware breakpoint ...
    (microsoft.public.windowsce.platbuilder)