From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL variant of sunxi nand module
Date: Sun, 23 Dec 2018 19:04:02 +0300 [thread overview]
Message-ID: <5C1FB1F2.8040908@yandex.ru> (raw)
In-Reply-To: <5C1F8DBC.1010304@yandex.ru>
Hi again,
23.12.2018 16:29, I wrote:
> > U-Boot SPL 2019.01-rc2 (Dec 20 2018 - 16:30:46 +0300)
> > CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> > DRAM: 1024 MiB
> > Trying to boot from NAND
>
Ok, discovered a special SPL-only sunxi_nand_spl variant, added some
debugging, so the detection is visible:
In nand_detect_config(), start detection...
Considering addr_cycles=5, page_size=2048
Considering ecc_size=1024, ecc_strength=0 failed(a).
Considering addr_cycles=5, page_size=2048 rejected.
Considering addr_cycles=5, page_size=4096
Considering ecc_size=1024, ecc_strength=3 failed(a).
Considering addr_cycles=5, page_size=4096 rejected.
Considering addr_cycles=5, page_size=8192
Considering ecc_size=1024, ecc_strength=4 good(b).
Considering addr_cycles=5, page_size=8192 accepted.
I'm almost 100% sure that correct config would be page_size=8192,
ecc_size=1024, ecc_strength=40 (from nand chip identification structure
for regular linux kernel)
Now the detection routine in sunxi_nand_spl apparently comes up with a
value of ecc_strength=4 instead... Why is that?
Thank you,
Regards,
Nikolai
>
>
> Thank you,
>
> Regards,
> Nikolai
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2018-12-23 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 13:29 [U-Boot] SPL variant of sunxi nand module Nikolai Zhubr
2018-12-23 16:04 ` Nikolai Zhubr [this message]
2018-12-23 15:54 ` Michael Nazzareno Trimarchi
2018-12-23 18:11 ` Nikolai Zhubr
2018-12-23 18:58 ` Nikolai Zhubr
2018-12-23 21:00 ` Nikolai Zhubr
2018-12-23 21:47 ` Nikolai Zhubr
2018-12-29 20:08 ` Nikolai Zhubr
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=5C1FB1F2.8040908@yandex.ru \
--to=n-a-zhubr@yandex.ru \
--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.