public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Bean Huo <beanhuo@micron.com>, JaimeLiao <jaimeliao.tw@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [EXT] Re: Boot failed after patch "mtd: rawnand: Support for sequential cache reads"
Date: Mon, 5 Jun 2023 10:39:43 +0200	[thread overview]
Message-ID: <20230605103943.064d142e@xps-13> (raw)
In-Reply-To: <CAP1tNvTS=kW_pPM5Vn4COmCXR7L6wj+CXtKs_Tnf=UQk2i7=Bg@mail.gmail.com>

Hi Alexander,

eagle.alexander923@gmail.com wrote on Fri, 2 Jun 2023 12:52:08 +0300:

> Hello.
> 
> > As you mentioned no ECC error.  And SquashFS complains: Unable to read data cache.
> > We want to see I/Ox, RE#, WE# and R/B#, to check if command input and data output properly.
> > It is better to capture the command 31h, and its following data.  
> 
> I only have a two-channel oscilloscope :)
> In any case, in order to capture the right moment, I need to somehow
> loop command 0x31
> when an error occurs in order to take a picture. Right?
> 
> Please, tell me where I can patch the nand_base to get such an
> infinity loop on error?

Anywhere in the core you could just make your own exec_op sequence and
call it in a loop I guess?

Bean, what are you trying to picture precisely? Have you ever had any
issues with these commands? Can Alexander try to add a surgical delay
somewhere?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-06-05  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  7:48 Boot failed after patch "mtd: rawnand: Support for sequential cache reads" Alexander Shiyan
2023-05-26 18:14 ` Miquel Raynal
2023-05-29  6:10   ` Alexander Shiyan
2023-05-29  8:12     ` Miquel Raynal
2023-05-29 10:33       ` Alexander Shiyan
2023-05-29 11:46         ` Miquel Raynal
2023-05-30 14:48           ` [EXT] " Bean Huo
2023-05-31  9:02             ` Alexander Shiyan
2023-06-01  7:37               ` Miquel Raynal
2023-06-01 16:55                 ` Bean Huo
2023-06-02  9:52                   ` Alexander Shiyan
2023-06-05  8:39                     ` Miquel Raynal [this message]
2023-06-05 15:45                       ` Bean Huo
2023-06-26  9:22                         ` Bean Huo
2023-07-03  9:16                           ` Alexander Shiyan

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=20230605103943.064d142e@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=beanhuo@micron.com \
    --cc=eagle.alexander923@gmail.com \
    --cc=jaimeliao.tw@gmail.com \
    --cc=linux-mtd@lists.infradead.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