This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: MMU, chip select on AT91
- From: Andrew Lunn <andrew at lunn dot ch>
- To: J?r?my Alles <jeremy dot alles at orange-ftgroup dot com>
- Cc: 'eCos Discussion' <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 7 Mar 2008 11:13:43 +0100
- Subject: Re: [ECOS] MMU, chip select on AT91
- References: <200803071003.m27A3Kqd001141@smtp.silicomp.fr>
On Fri, Mar 07, 2008 at 11:03:31AM +0100, J?r?my Alles wrote:
> Hi,
>
> I?m using a AT91 processor on a AT91RM9200DK board. I?m using a port that
> someone in my company did some years ago. Here is my problem: I would like
> to use the graphic possibilities of the board. In the development kit, I
> have an example driver (source code and bin file).
>
> If I run the bin file from Zooboot it works fine.
> If I build the driver (using arm-elf-gcc) and launch it from Redboot (using
> eCos environment) it doesn?t work anymore.
>
> I?ve traced down the problem to the chip select line 2 (NCS2). This chip
> select should be enable when I access data at 0x30000000 but it?s not. I was
> thinking that it might be a problem with the MMU initialization that is done
> in eCos in AT91 common code.
There is no port for the AT91RM9200DK in anonymous CVS. Without the
code i cannot say what the MMU is doing. However it does sound like an
MMU problem.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss