mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
Cc: d.schultz@phytec.de, barebox@lists.infradead.org,
	ptxdist@pengutronix.de, c.hemp@phytec.de
Subject: Re: [ptxdist] boot problem w/ barebox
Date: Mon, 11 Sep 2017 09:16:14 +0200	[thread overview]
Message-ID: <20170911071614.ubhmelfunysejs4a@pengutronix.de> (raw)
In-Reply-To: <6e6e8b7d-3fe7-04ca-c275-efbf89cec410@gr13.net>

On Sat, Sep 09, 2017 at 11:01:34AM +0200, Enrico Weigelt, metux IT consult wrote:
> Hi folks,
> 
> 
> I've got a really strange booting problem on an phycore-imx6
> based board (pretty much the same as mira):
> 
> * barebox v2017.06.1-phy2 comes up properly, but cant boot
>   the kernel (v4.13) - just hangs w/o any output (not even
>   uncompression message)
> * putting the kernel manually into the factory-image (sdcard)
>   w/ old 2015 barebox boots the kernel
> * w/ DEBUG_LL + earlyprintk it doesn't even does that, just
>   hangs like w/ new barebox
> 
> 
> Here's the last output I've got: (added few more debug outputs)
> 
> > Loading ARM Linux zImage '/mnt/mmc/boot/zImage'
> > Loading devicetree from '/mnt/mmc/boot/imx6q-phytec-mira-rdk-emmc.dtb'
> > Updating DT commandline:  console=ttymxc1,115200n8 root=/dev/mmcblk0p2
> rootwait rw earlyprintk=1
> > DT commandline:  console=ttymxc1,115200n8  root=/dev/mmcblk0p2 rootwait rw
> earlyprintk=1
> > booting kernel with devicetree
> > start_linux: kernel entry point: 12000000
> >                            dtb: 18000000
> >                           swap: 0
> >                           arch: 0
> > shutting down barebox
> 
> My first suspicion was zero'ed DT memory node (which OTOH doesn't
> explain why earlyprintk doesn't work), but fixing that didn't help.
> 
> Could there be any vital low-level init missing in the new bbx ?
> Maybe the entry point correct ?
> 
> Any ideas where I could have a deeper look at ?

Try adding a #define DEBUG in linux-4.13/arch/arm/boot/compressed/head.S
and make sure enabled DEBUG_LL and selected the right UART in your
.config.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-09-11  7:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-09  9:01 Enrico Weigelt, metux IT consult
2017-09-11  7:16 ` Uwe Kleine-König [this message]
2017-09-11 18:47   ` Enrico Weigelt, metux IT consult
2017-09-12  8:32     ` Uwe Kleine-König
2017-09-13 10:56       ` Enrico Weigelt, metux IT consult

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=20170911071614.ubhmelfunysejs4a@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=c.hemp@phytec.de \
    --cc=d.schultz@phytec.de \
    --cc=enrico.weigelt@gr13.net \
    --cc=ptxdist@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