From: Andrej Picej <andrej.picej@norik.com>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: i.MX: xload-gpmi-nand: apply errata 007117
Date: Fri, 22 Jan 2021 10:47:09 +0100 [thread overview]
Message-ID: <65415553-750c-810d-7902-b1052d764bec@norik.com> (raw)
In-Reply-To: <20210122081215.GM19063@pengutronix.de>
On 22. 01. 21 09:12, Sascha Hauer wrote:
> On Thu, Jan 21, 2021 at 01:23:16PM +0100, Andrej Picej wrote:
>> Hi Sascha,
>>
>> yes, unfortunately we have. We applied this just because we experienced
>> hangs in device booting tests. After this patch the NAND booting problems
>> went away. The booting failed during DMA page reading.
>> I just tested this again and after excluding the changes in this patch the
>> device fails at executing DMA commands. The boot fails in approximately one
>> out of 10 boots.
>
> Where exactly did it hang? In the xloader or later in the real barebox
> driver?
> You probably mean that it hangs in the xloader. Sorry to ask, but I'm
> still trying to understand. That would mean the ROM leaves the GPMI in
> an unusable state and I really wonder how this can happen.
>
> Sascha
>
Sorry for not being clear enough the first time. You are correct, it
hangs in xloader.
Maybe some additional information that may be relevant. When we boot
barebox without PBL support barebox boots without problem and NAND
behaves normal, so i guess the ROM sets the GPMI in usable state.
Just a thought: could it be that the problem is in xloader and we
somehow repair or reset the GPMI with this errata fix, so it works with
xloader?
Andrej
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-01-22 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:51 [PATCH 0/3] GPMI NAND xload for i.MX6 Andrej Picej
2021-01-20 12:51 ` [PATCH 1/3] ARM: i.MX: move BCB structures to header file Andrej Picej
2021-01-20 12:51 ` [PATCH 2/3] ARM: i.MX: implement GPMI NAND xload Andrej Picej
2021-01-20 21:45 ` Roland Hieber
2021-01-21 9:01 ` Sascha Hauer
2021-01-21 10:28 ` Andrej Picej
2021-01-25 9:15 ` Sascha Hauer
2021-01-25 9:43 ` Andrej Picej
2021-01-26 11:40 ` Andrej Picej
2021-01-26 12:08 ` Sascha Hauer
2021-01-26 12:18 ` Andrej Picej
2021-01-20 12:51 ` [PATCH 3/3] ARM: i.MX: xload-gpmi-nand: apply errata 007117 Andrej Picej
2021-01-21 9:11 ` Sascha Hauer
2021-01-21 12:23 ` Andrej Picej
2021-01-22 8:12 ` Sascha Hauer
2021-01-22 9:47 ` Andrej Picej [this message]
2021-01-25 8:57 ` 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=65415553-750c-810d-7902-b1052d764bec@norik.com \
--to=andrej.picej@norik.com \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox