From: Andreas Geisenhainer <Andreas.Geisenhainer@atsonline.de>
To: barebox@lists.infradead.org
Subject: Re: Oselas 2018.12.0 toolchain seems to break barebox for AM335x
Date: Wed, 10 Jul 2019 10:14:10 +0200 [thread overview]
Message-ID: <a3b5da64-bfab-3f51-cbcd-f75e100b24e4@atsonline.de> (raw)
In-Reply-To: <20190710075821.vhbdbkv67raa4zf4@pengutronix.de>
Hello Sascha, hello ML.
On 2019-07-10 9:58 a.m., Sascha Hauer wrote:
> Hi Andreas,
>
> On Mon, Jul 08, 2019 at 04:15:00PM +0200, Andreas Geisenhainer wrote:
>> We're running barebox an a Phytec PhyCORE AM335x platform, and the
>> behaviour does emerge for the default "barebox-am335x-phytec-phycore.img"
>> image from barebox.
> I just tried to reproduce this on a beaglebone black as this is at least
> the same SoC. Unfortunately I was not successful.
>
> Unfortunately this disappeared after some changes and never came back.
Thanks for trying.
> Does your barebox always crash or does the behaviour change when you try
> adding debugging? you might want to add some putc_ll() at earlier places
> to see how far you get.
It crashes every time, as far as i can tell, since there is no more output.
I'm working around the the problem for a bit, but will investigate further
into it. There should be a Beaglebone Black around here. I'll try to
reproduce it on this platform and get back to you.
kind regards
Andreas
--
_
__ _| |_ ___
/ _` | __/ __|
| (_| | |_\__ \
\__,_|\__|___/
Elektronik GmbH
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-07-10 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 14:15 Andreas Geisenhainer
2019-07-10 7:58 ` Sascha Hauer
2019-07-10 8:14 ` Andreas Geisenhainer [this message]
2019-10-25 8:48 ` Andreas Geisenhainer
2019-11-12 7:48 ` Andreas Geisenhainer
2019-11-12 11:00 ` Sascha Hauer
2019-11-12 14:37 ` Andreas Geisenhainer
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=a3b5da64-bfab-3f51-cbcd-f75e100b24e4@atsonline.de \
--to=andreas.geisenhainer@atsonline.de \
--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