From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gKK2O-0000lH-EB for barebox@lists.infradead.org; Wed, 07 Nov 2018 09:22:13 +0000 Message-ID: <1541582518.2508.36.camel@pengutronix.de> From: Lucas Stach Date: Wed, 07 Nov 2018 10:21:58 +0100 In-Reply-To: References: <20181106143605.29820-1-l.stach@pengutronix.de> Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH] scripts: imx-image: fix first instruction in i.MX8MQ header To: Andrey Smirnov Cc: Barebox List Am Dienstag, den 06.11.2018, 12:54 -0800 schrieb Andrey Smirnov: > > On Tue, Nov 6, 2018 at 6:36 AM Lucas Stach wrote: > > > > The instruction being patched in was a branch to 0x24000, instead of > > the intended 0x9000. This doesn't matter when starting the image from > > a regular boot source, but breaks starting the image via bootm, as we > > rely on the jump in the first header instruction taking us to the > > actual code. > > > > For some reason I thought I submitted a patch fixing this, but > apparently not. Did you have a chance to run this fix with and without > signed HDMI firmware blob? AFAIR, adding it shifts entry point from > 0x9000 to 0x28000 (don't quote me on this), so it's possible that some > code around imx-image.c:894 might have to be added to handle this > problem. This can be a subject for another patch, though. Thanks for the valuable hint. I didn't yet try running with the signed firmware. I'll keep this mind for when I do. Regards, Lucas _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox