From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Koelle, Holger" <Holger.Koelle@allegion.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0
Date: Fri, 7 Feb 2020 11:33:23 +0100 [thread overview]
Message-ID: <566f7758-587f-e833-cee7-ee8e7133e3ac@pengutronix.de> (raw)
In-Reply-To: <BL0PR01MB52513F7AE42E4E6ED527380A8F1C0@BL0PR01MB5251.prod.exchangelabs.com>
Hello,
On 2/7/20 11:17 AM, Koelle, Holger wrote:
> Hey there,
>
> this week i updated some imx27 based phycard from Barebox 2019.01 to 2020.01. After the update at Boot nothing happens.. no output on serial.
> Devicetree and Configuration (barebox.config in ptxdist) looks fine...got anyone suggestions for me?
Try finding the offending commit with git-bisect:
git bisect good v2019.01.0
git bisect bad v2020.01.0
# build, flash, run barebox
git bisect good # if it works
git bisect bad # if it doesn't work
There have been 1004 revisions between the two tags, which means, a binary
search will find the offending commit in 10 iterations.
When you've found the commit and need to take a more thorough look (printf-debugging),
you can add low level UART debug support to your board.
Keep us updated!
Cheers
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
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:[~2020-02-07 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 10:17 Koelle, Holger
2020-02-07 10:33 ` Ahmad Fatoum [this message]
2020-02-11 15:33 ` AW: " Koelle, Holger
2020-02-12 8:08 ` Sascha Hauer
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=566f7758-587f-e833-cee7-ee8e7133e3ac@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=Holger.Koelle@allegion.com \
--cc=barebox@lists.infradead.org \
/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