mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: 郑小军 <jameszxj@gmail.com>
To: barebox@lists.infradead.org
Subject: No oob scheme defined for oobsize 224 on imx6ull board
Date: Fri, 18 Dec 2020 17:11:11 +0800	[thread overview]
Message-ID: <CADbCKyKLBG=eSoKeqnvvGMCGdkpwNo_xGvH1D1xHHTgk0tMU1Q@mail.gmail.com> (raw)

Hi, all
    I am trying to run barebox on my i.mx6ull board.  I inherit from
nxp-imx6ull-evk. When I added nand flash support, system crashed. I
found that the pointer "chip->legacy.set_features" and
"chip->legacy.get_features" in nand_mxs.c was NULL.
I replaced it with nand_set_features() and nand_get_features().
Barebox didn't crash again, but I get the errors:
        nand_base: device found, Manufacturer ID: 0x2c, Chip ID: 0xdc
        nand_base: Micron MT29F4G08ABAEAWP
        nand_base: 512 MiB, SLC, erase size: 256 KiB, page size: 4096,
OOB size: 224
        WARNING: at drivers/mtd/nand/nand_base.c:5591/nand_scan_tail()!
        WARNING: No oob scheme defined for oobsize 224
        mxs_nand 1806000.nand-controller@1806000.of: probe failed:
Invalid argument

dts:
&gpmi {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_gpmi_nand>;
nand-on-flash-bbt;
status = "okay";
};

Did I miss something?

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-12-18  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  9:11 郑小军 [this message]
2021-01-06 10:35 ` Sascha Hauer
2021-01-07  2:27   ` =?gb18030?B?amFtZXN6eGo=?=
     [not found]   ` <tencent_38A3D28635D0E3DF1085571FDB818F5D420A@qq.com>
2021-02-23  0:21     ` =?gb18030?B?amFtZXN6eGo=?=
2021-02-23  7:51     ` Sascha Hauer

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='CADbCKyKLBG=eSoKeqnvvGMCGdkpwNo_xGvH1D1xHHTgk0tMU1Q@mail.gmail.com' \
    --to=jameszxj@gmail.com \
    --cc=barebox@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