All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI2000 with ppc440epx.
Date: Fri, 2 May 2008 09:19:53 +0200	[thread overview]
Message-ID: <200805020919.53505.sr@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C02529384@ehost011-3.exch011.intermedia.net>

Hi Leonid,

On Thursday 01 May 2008, Leonid wrote:
> Thank you very much for your answer, it shows that our minds are working
> alike :-). I didn't know what the problem is but I did exactly the thing
> you suggest - put indefinite loop in the nand_boot() function with
> condition, checking some address in RAM. I set breakpoint after this
> loop and them modify memory via BDI and get my breakpoint!
>
> The issue I am investigating is that CPU ceased to boot from NAND flash
> when we switched from NAND01GW3B2AZA6 ST Micro flash to another
> NAND01GW3B2BZA6. They are presumably the same (page, block size, etc...)
> only word 3 is 0 for first and 0x80 fort second.

Word or byte? You are referring to the offset in the OOB, correct? Are you are 
using the latest U-Boot version with 2k page size NAND booting support? On 
large page NAND chips the bad block marker is in byte 0.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2008-05-02  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:02 [U-Boot-Users] BDI2000 with ppc440epx Leonid
2008-05-01 12:34 ` Stefan Roese
2008-05-01 15:31   ` Leonid
2008-05-02  7:19     ` Stefan Roese [this message]

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=200805020919.53505.sr@denx.de \
    --to=sr@denx.de \
    --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.