From: Rico Pahlisch <rico.pahlisch@kiwigrid.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Raspberry CM3 eMMC Boot
Date: Tue, 18 Jun 2019 10:51:53 +0200 [thread overview]
Message-ID: <CAHBg2Lcn_V+=1iEw2LS642bQyGuOkCxM0pM=ydL3nj27Ha-A8w@mail.gmail.com> (raw)
In-Reply-To: <20190618075723.hnc5uabshtrypfda@pengutronix.de>
This are the logs first without the patch and then with patch.
Only with the patch I get a barebox promt.
Not working logs:
Board: RaspberryPi Compute Module 3
bcm2835-gpio 3f200000.gpio@7e200000.of: probed gpiochip-1 with base 0
bcm2835_mci 3f300000.sdhci@7e300000.of: registered as mci0
<NULL>: Failed to get 'vmmc' regulator.
bcm2835-sdhost 3f202000.mmc@7e202000.of: registered as mci1
Working logs:
Board: RaspberryPi Compute Module 3
bcm2835_mci 3f300000.sdhci@7e300000.of: registered as mci0
<NULL>: Failed to get 'vmmc' regulator.
bcm2835-sdhost 3f202000.mmc@7e202000.of: registered as mci1
mci0: detected MMC card version 5.1
mci0: registered disk0
state: New state registered 'state'
state: Using bucket 0@0x00000000
bcm2835-gpio 3f200000.gpio@7e200000.of: probed gpiochip-1 with base 0
malloc space: 0x0fe7e2e0 -> 0x1fcfc5bf (size 254.5 MiB)
environment load /boot/barebox.env: No such file or directory
Maybe you have to create the partition.
Am Di., 18. Juni 2019 um 09:57 Uhr schrieb Sascha Hauer
<s.hauer@pengutronix.de>:
>
> Hi Rico,
>
> On Mon, Jun 17, 2019 at 03:44:17PM +0200, Rico Pahlisch wrote:
> > Hello,
> >
> > I try to boot from the internal eMMC with the raspberry CM3 barebox
> > build but I dont get a promt.
> > After changing the code barebox works fine. Does any one else have
> > problems with the raspberry 3 compute module.
> >
> > diff --git a/drivers/pinctrl/pinctrl-bcm2835.c
> > b/drivers/pinctrl/pinctrl-bcm2835.c
> > index 5fd5740..56daa04 100644
> > --- a/drivers/pinctrl/pinctrl-bcm2835.c
> > +++ b/drivers/pinctrl/pinctrl-bcm2835.c
> > @@ -209,4 +209,4 @@ static int bcm2835_gpio_add(void)
> > {
> > return platform_driver_register(&bcm2835_gpio_driver);
> > }
> > -coredevice_initcall(bcm2835_gpio_add);
> > +device_initcall(bcm2835_gpio_add);
>
> I have no idea why this helps. Do you have any logs that explain the
> issue?
>
> 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 |
--
Rico Pahlisch
Senior Software Developer
Kiwigrid GmbH
Kleiststraße 10 a – c | 01129 Dresden | Germany
rico.pahlisch@kiwigrid.com | www.kiwigrid.com
Registered Office/ Sitz der Gesellschaft: Dresden
Registered Court/ Registergericht: Amtsgericht Dresden | HRB 30058
Chairman of the Advisory Board/ Beiratsvorsitzender: Hans-Peter Villis
Managing Directors/ Geschäftsführer: Matthias Hertel (Speaker/
Sprecher), Tim Ulbricht
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-06-18 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 13:44 Rico Pahlisch
2019-06-18 7:57 ` Sascha Hauer
2019-06-18 8:51 ` Rico Pahlisch [this message]
2019-06-18 12:17 ` Tomaž Šolc
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='CAHBg2Lcn_V+=1iEw2LS642bQyGuOkCxM0pM=ydL3nj27Ha-A8w@mail.gmail.com' \
--to=rico.pahlisch@kiwigrid.com \
--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