All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex889 <alex889@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Error during NAND access
Date: Tue, 19 Oct 2010 06:03:26 -0700 (PDT)	[thread overview]
Message-ID: <29999994.post@talk.nabble.com> (raw)


Hi,
I have strange phenomena.
I have DM365 baaed board.
In some boards (Not all of them), I get this strange case:
Accessing the NAND (Erase/write), like with saveenv command, followed by
Ethernet access (TFTP/PING) stuck the SW.
Accessing the NAND without prior access to ETHERNET works fine.
I tried to debug this with TI code composer studio.
When accessing the NAND, it seems that the CPUs data bus is hung, and I get
the following message from code composer: 

Warning:

0x40000020/-1032 @ marker 1022
Warning during: Execution, 

The pipeline is stalled owing to 'data bus not ready'
Did you ever encounter such a problem?
Do you know if it is caused by HW problem (Corrupt NAND/DM365), or a fixable
SW bug?

Thanks in advance
Alex

-- 
View this message in context: http://old.nabble.com/Error-during-NAND-access-tp29999994p29999994.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

                 reply	other threads:[~2010-10-19 13:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=29999994.post@talk.nabble.com \
    --to=alex889@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.