Embedded Linux development
 help / color / mirror / Atom feed
From: Fundu <fundu_1999@yahoo.com>
To: linux embedded <linux-embedded@vger.kernel.org>
Subject: "kernel access of bad area" while accessing flash
Date: Tue, 26 Aug 2008 20:13:39 -0700 (PDT)	[thread overview]
Message-ID: <425469.77736.qm@web63401.mail.re1.yahoo.com> (raw)

I have a PPC440GX based board.

Do I need to reinitialize Peripheral Bank Configuration Registers (EBC0_B0CR-EBC0_B7CR) from the kernel ?
I'm quite sure that we don't, but just want to make sure. Because the problem
that i'm seeing strongly suggest that it's probably not accessible. 

Here's the problem, i'm getting "kernel access of bad
 area" when i erase any of the upper 64mb out of 128mb flash region, surprisingly i can easily erase (all of the flash) from u-boot. which makes me ask the earlier question.   

any insights welcome.

thanks ! 


      

             reply	other threads:[~2008-08-27  3:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  3:13 Fundu [this message]
2008-08-27 11:33 ` "kernel access of bad area" while accessing flash Josh Boyer

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=425469.77736.qm@web63401.mail.re1.yahoo.com \
    --to=fundu_1999@yahoo.com \
    --cc=linux-embedded@vger.kernel.org \
    /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