mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <>
To: "Middelschulte, Leif" <>
Cc: "" <>
Subject: Re: imx6 nand: dbbt version/layout
Date: Mon, 3 May 2021 14:32:33 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Leif,

On Thu, Apr 22, 2021 at 12:13:59PM +0000, Middelschulte, Leif wrote:
> 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 layout version 0x1.

It's stored in big endian. Just endianess swap 0x01000000 and you have
your 0x00000001.

> 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.

barebox doesn't actively sets the value to anything else than 0x0. I
have no idea if and how the ROM interprets this value. Indeed the name
of the field seems to be inconsistent to the reference manual.


Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

barebox mailing list

  reply	other threads:[~2021-05-03 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:13 Middelschulte, Leif
2021-05-03 12:32 ` Sascha Hauer [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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