From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio Estevam <festevam@gmail.com>
Date: Mon, 10 Apr 2017 17:14:54 -0300
Subject: [U-Boot] i.Mx6q u-boot stuck
In-Reply-To: <2007927372.113767.1491854856064@pim.register.it>
References: <CAAbSMk=qvhywc32EL6sPYQQnU3brnYiYzcU7h=L3t+FyoSqgAg@mail.gmail.com>
 <CAOMZO5BcnOZbzFYotLh2LebYUFo_XUaxuHaXa5--BYAdfQO_Tw@mail.gmail.com>
 <CAAbSMkmt=593HfwoD7m5gahaVq=RPQpsuwsM9e-9JqjuVGabPQ@mail.gmail.com>
 <CAOMZO5A+Pf8Ghoid_ysANjdfzKD1Y2w22eCB9Z2CDZ+5nOp0JA@mail.gmail.com>
 <2007927372.113767.1491854856064@pim.register.it>
Message-ID: <CAOMZO5DpcLtL5rCaJu41UChT8ZoZwXDphAixbUpsKwTu4Y=cCw@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Mon, Apr 10, 2017 at 5:07 PM, Fausto Sessego
<fausto.sessego@infomob.it> wrote:
> It is right because it is a custom board designed  by my self.
>
> I renamed CONFIG_TARGET_MX6BOARD=y
>
> Do you have any hint?

You can try removing the line ""mmcbooterror=echo Boot from mmc
ERROR!!; " from your CONFIG_EXTRA_ENV_SETTINGS.