All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nand boot on imx6q board is broken
Date: Thu, 31 Jan 2019 20:56:24 +0530	[thread overview]
Message-ID: <CAMty3ZCaLo3qGpYiBG=D0d75LLCz-OYLj_iDsWWfzvja8DY1Xw@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7x+ZufjOnLODeFkSzw3oZWjanO=jSxnKvYARyVZrmn-1xw@mail.gmail.com>

On Thu, Jan 31, 2019 at 8:53 PM Adam Ford <aford173@gmail.com> wrote:
>
> On Wed, Jan 30, 2019 at 11:40 PM Shyam Saini <shyam@amarulasolutions.com> wrote:
> >
> > Hi Everyone,
> >
> > I'm trying to boot imx6q board from nand but it seems like mainline
> > u-boot nand boot support for imx6q board is broken.
>
> I spent some time trying to make the imx6q_logic board boot from SPL
> from NAND, but I needed to patch a few things.   Some of them have yet
> to be approved, but if they work for you, maybe it will help get them
> approved.
>
> There was a broken function pointer here that was fixed and applied
> the imx-master, but pending merge with master
> http://patchwork.ozlabs.org/patch/1019440/
>
> Configure ECC from SPL here:
> http://patchwork.ozlabs.org/patch/1020160/
>
> Remove hard-coded ECC parameters since the patch above can autoset them.
> http://patchwork.ozlabs.org/patch/1026638/
>
> With those 3 patches and some minor changes to my individual board
> file and config file, I was able to boot 2019.01 via SPL from NAND.
> Since it was working for you before, I am guessing the board file
> stuff and config file stuff is probably already for you.

Thanks for your inputs Adam.

I was initially fixed the board and spl nand detection changes, I hope
these changes would resolve. let's see.

  reply	other threads:[~2019-01-31 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  7:38 [U-Boot] Nand boot on imx6q board is broken Shyam Saini
2019-01-31 15:22 ` Adam Ford
2019-01-31 15:26   ` Jagan Teki [this message]
2019-01-31 15:57   ` Shyam Saini
2019-01-31 17:25     ` Adam Ford
2019-01-31 19:32       ` Michael Nazzareno Trimarchi
2019-02-02 13:16   ` Jörg Krause
2019-02-02 13:27     ` Adam Ford

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='CAMty3ZCaLo3qGpYiBG=D0d75LLCz-OYLj_iDsWWfzvja8DY1Xw@mail.gmail.com' \
    --to=jagan@amarulasolutions.com \
    --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.