From: John Parker <John.Parker@lucyautomation.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: FW: Barebox on Karo TX25
Date: Fri, 29 Nov 2013 10:41:30 +0000 [thread overview]
Message-ID: <EAF1F21DA385DA4797F21C5DCAEF6BAC467D346808@AUTOSERVER1.auto.local> (raw)
In-Reply-To: <20131129094623.GB24559@pengutronix.de>
Fantastic! That works!
Many thanks
Regards
John
-----Original Message-----
From: John Parker
Sent: 29 November 2013 10:27
To: 'Sascha Hauer'
Cc: Baruch Siach; barebox@lists.infradead.org
Subject: RE: FW: Barebox on Karo TX25
Thank you Sascha, I'll give that a go and report back
Regards
John
-----Original Message-----
From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
Sent: 29 November 2013 09:46
To: John Parker
Cc: Baruch Siach; barebox@lists.infradead.org
Subject: Re: FW: Barebox on Karo TX25
On Fri, Nov 29, 2013 at 08:16:21AM +0000, John Parker wrote:
> Hi Baruch
>
> Thank you for this. I've now found this info in the reference manual - not under the watchdog section but elsewhere - under the boot modes.
>
> So now I can concentrate on why the zbarebox.bin wont run!
Sorry, John. I can confirm the startup is broken since:
commit cf4271ee12f8ce61598a327a72026226441dca72
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Thu Jan 24 17:09:00 2013 +0100
ARM i.MX: prepare external nand boot for SoC specific entry
i.MX will get SoC specific entry points for barebox. To find the
correct one we have to call these from the SoC specific
imx*_barebox_boot_nand_external functions.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Unfortunately I haven't figured out yet how to fix this. For now you could go back before this commit by checking out cf4271ee12f8ce61598a~1. This should work.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-11-29 10:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 11:28 John Parker
2013-11-27 12:56 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image Sascha Hauer
2013-11-27 12:56 ` [PATCH 2/2] scripts: imx-image: Add i.MX25 support Sascha Hauer
2013-11-27 14:49 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image John Parker
2013-11-27 13:02 ` FW: Barebox on Karo TX25 Sascha Hauer
2013-11-27 13:18 ` John Parker
2013-11-27 15:49 ` John Parker
2013-11-27 21:01 ` Sascha Hauer
2013-11-28 16:13 ` John Parker
2013-11-28 16:22 ` Baruch Siach
2013-11-29 8:16 ` John Parker
2013-11-29 9:46 ` Sascha Hauer
2013-11-29 10:27 ` John Parker
2013-11-29 10:41 ` John Parker [this message]
2013-12-02 9:13 ` John Parker
2013-12-03 9:26 ` Sascha Hauer
2013-12-03 19:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-05 15:24 ` Sascha Hauer
2013-12-05 16:48 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-19 14:14 ` John Parker
2013-11-27 19:45 ` John Parker
2013-11-27 20:15 ` Eric Bénard
2013-11-27 20:54 ` Sascha Hauer
2013-11-28 4:16 ` Alexander Aring
2013-11-28 7:20 ` Sascha Hauer
2013-11-28 7:37 ` Alexander Aring
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=EAF1F21DA385DA4797F21C5DCAEF6BAC467D346808@AUTOSERVER1.auto.local \
--to=john.parker@lucyautomation.co.uk \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox