linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Conn Clark <clark@esteem.com>
To: Paul Miller <pmiller9@users.sourceforge.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405EP peripheral memory access
Date: Wed, 29 Oct 2003 09:32:27 -0800	[thread overview]
Message-ID: <3F9FF9AB.6000406@esteem.com> (raw)
In-Reply-To: <200310290808.00654.pmiller9@users.sourceforge.net>


Paul Miller wrote:
> Hi,
>
> I am new to Linux embedded programming.  I have experience programming
> microcontrollers and DSPs without an operating system, so I have some
> idea what I'm doing.  Anyhow, I'm trying to use the peripheral memory
> bus on my 405EP CerfCube from Intrinsyc.  Does anyone have an example
> that I can work from?

If I remember correctly the Cerf Cube uses PPCboot/U-Boot and ships with
the source on a CD.

>
> To setup the memory's timings, I need access to the DCR register.  In
> the PowerPC datasheet it says to use assembly instructions mtdcr and
> mfdcr.  I don't know much about assembly, but I found a kernel patch
> that uses these functions.  So, working off this patch, I tried making
> a simple program to read these registers.  When I run it, Linux reports
> an "Illegal instruction" and doesn't let me access the register.

Did you make calls to the patched kernel or paste this function into
your user mode program? Some registers are priviledged and only the
kernel is allowed to touch them. If you had this function in a user
program it won't work.
>
> Does access to this bus need to be done in "kernel mode"?  If so, where
> can I find more information about writing a kernel driver?  Ideally,
> I'd like to just open a device file and read/write to the bus.
>

I wrote my first kernel driver based on an example found at
http://www.denx.de . Though It was for kernel version 2.2.x and the
Motorla 8xx processor, the example was quite helpful and could still be
for you. Its at the botom of the page here
http://www.denx.de/e/index1.php?head=solution-se-head&main=solution-se&subnav=solution-se-subnav&logo=logo-se&mainnav=softwarenav&bottom=bottom-se

One aproach you might take is modifying the PPCBoot source and mapping
your device to a memory address and access it using the memory map
functions in the kernel.
> Thanks!
> -Paul
>
>

Its going to be ruff in the begining, but it gets easier. Have fun.

Conn Clark


--

*****************************************************************
   If you live at home long enough, your parents will move out.
  (Warning they may try to sell their house out from under you.)
*****************************************************************

Conn Clark
Engineering Stooge				clark@esteem.com
Electronic Systems Technology Inc.		www.esteem.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-29 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 14:08 405EP peripheral memory access Paul Miller
2003-10-29 17:32 ` Conn Clark [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-29 14:31 Steven Blakeslee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F9FF9AB.6000406@esteem.com \
    --to=clark@esteem.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pmiller9@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).