mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Middelschulte, Leif" <Leif.Middelschulte@klsmartin.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: imx6 nand: dbbt version/layout
Date: Thu, 22 Apr 2021 12:13:59 +0000	[thread overview]
Message-ID: <78f79375e21e753086868b2212485b488443bcb1.camel@klsmartin.com> (raw)

Hi,

I'm in the process of fixing up imx-kobs to support
- boot configuration dumps
- boot stream extracts/updates
on iMX6QDL using the GPMI-NAND interface, as provided by some more
"recent" kernels.

I updated barebox on the NAND flash storage using another instance of
barebox. Now it turns out that the dbbt version used (i.e. written) by
barebox and supported by imx-kobs (as it was) is not documented in the
i.MX6 QDL reference manual.
Barebox uses[0] DBBT version 0x1000000, while the reference manual
describes (i.MX6DQRM Rev 3., section 8.5.2.4) layout version 0x1.

Besides that, the reference manual apparently does not describe the
field `BBMarkerPhysicalOffsetInSpareData` at the end of the FCB
structure. Yet again, imx-kobs and barebox are reading/writing it.

So I'm wondering which behavior is correct?

[0]
https://git.pengutronix.de/cgit/barebox/tree/common/imx-bbu-nand-fcb.c?id=af0f068a6edad45b033e772056ac0352e1ba3613#n675


Best regards,

Leif
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions expressed are solely those of the author and do not necessarily represent those of KLS Martin. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


             reply	other threads:[~2021-04-22 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:13 Middelschulte, Leif [this message]
2021-05-03 12:32 ` Sascha Hauer
2021-06-11 15:16   ` Middelschulte, Leif

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=78f79375e21e753086868b2212485b488443bcb1.camel@klsmartin.com \
    --to=leif.middelschulte@klsmartin.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