From: Hans-Ulrich Schlieben <hu.schlieben@codewrights.de>
To: Enrico Joerns <ejo@pengutronix.de>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: [yocto] #yocto bootchooser: Cannot get state 'state'
Date: Wed, 15 Jan 2020 13:26:53 +0000 [thread overview]
Message-ID: <DB8PR03MB54983C09B221B210D29A26AAFE370@DB8PR03MB5498.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <1579093362.13056.13.camel@pengutronix.de>
Hi Enrico,
thank you very much for your help.
I'm using barebox_2019.01.0-phy4-r7.0 now. In thud I used barebox_2017.12.0
The image is built using my own ims layer which depends on core-image-minimal
LAYERDEPENDS_ims-layer = "core-image-minimal openembedded-layer phytec-layer"
Its using the meta-phytec Layer and a custom layer from phytec named meta-ksp0663.
Forgot to mention that rauc is used too, which moved from 1.1 to now 1.2.
Just changed the LAYERSERIES_COMPAT to "zeus" here to check whether yocto zeus works.
Is there some info what to change in the devicetree and so on when moving to warrior/zeus?
In thud this worked.
Thank you
Regards
hu
> -----Original Message-----
> From: Enrico Joerns <ejo@pengutronix.de>
> Sent: Wednesday, 15 January 2020 14:03
> To: Hans-Ulrich Schlieben <hu.schlieben@codewrights.de>; yocto@lists.yoctoproject.org
> Cc: barebox@lists.infradead.org
> Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state'
>
> Hi,
>
> this is mainly a barebox-related question, thus I'd suggest asking it on the barebox ML.
>
> [cc-ing barebox mailing list]
>
> On Wed, 2020-01-15 at 04:10 -0800, hu.schlieben@codewrights.de wrote:
> > Hi,
> >
> > booting the new yocto zeus system manually by "boot mmc" works fine
> > but default bootchooser fails with:
> >
> > bootchooser: Cannot get state 'state'
> > Nothing bootable found on 'bootchooser'
> > Nothing bootable found
>
> Looks like the state node is missing in your device tree.
> Which version of barebox do you use?
> And from which layer / recipe?
>
> > Building the "same" image in yocto thud works fine. The boot variables
> > are:
> >
> > * BOOT_system0_.default: 3
> > * BOOT_system1_.default: 3
> > * allow_color: 0
> > * autoboot_timeout: 3
> > * boot.default: bootchooser
> > boot.watchdog_timeout: 0
> > bootchooser.default_attempts: 3
> > bootchooser.default_priority: 1
> > bootchooser.disable_on_zero_attempts: 0
> > bootchooser.reset_attempts: (list: "power-on", "all-zero")
> > bootchooser.reset_priorities:
> > bootchooser.retry: 0
> > * bootchooser.state_prefix: state.bootstate
> > * bootchooser.system0.boot: mmc
> > * bootchooser.system0.default_attempts: 3
> > * bootchooser.system0.default_priority: 20
> > * bootchooser.system1.boot: mmc1
> > * bootchooser.system1.default_attempts: 3
> > * bootchooser.system1.default_priority: 21
> > * bootchooser.targets: system0 system1
> > bootm.appendroot: 0
> > ...
> >
>
> Regards, Enrico
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-01-15 13:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r276.1579090214262888471.6UJY@lists.yoctoproject.org>
2020-01-15 13:02 ` Enrico Joerns
2020-01-15 13:26 ` Hans-Ulrich Schlieben [this message]
2020-01-15 13:38 ` Ahmad Fatoum
2020-01-15 13:39 ` Ahmad Fatoum
2020-01-15 14:25 ` Hans-Ulrich Schlieben
2020-01-15 14:36 ` Ahmad Fatoum
2020-01-15 14:47 ` Enrico Joerns
2020-01-16 15:13 ` Hans-Ulrich Schlieben
2020-01-20 15:31 ` Ahmad Fatoum
2020-01-21 18:28 ` Hans-Ulrich Schlieben
2020-01-21 20:18 ` Ahmad Fatoum
2020-01-22 17:59 ` Robert Berger@yocto.user
2020-01-23 15:30 ` Hans-Ulrich Schlieben
2020-01-23 15:36 ` Ahmad Fatoum
2020-01-23 16:11 ` Hans-Ulrich Schlieben
2020-01-23 16:17 ` Ahmad Fatoum
2020-01-23 16:31 ` Hans-Ulrich Schlieben
2020-01-16 15:09 ` Hans-Ulrich Schlieben
2020-01-20 15:23 ` Ahmad Fatoum
2020-01-21 17:51 ` Hans-Ulrich Schlieben
2020-01-21 20:21 ` Ahmad Fatoum
2020-01-23 15:37 ` Hans-Ulrich Schlieben
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=DB8PR03MB54983C09B221B210D29A26AAFE370@DB8PR03MB5498.eurprd03.prod.outlook.com \
--to=hu.schlieben@codewrights.de \
--cc=barebox@lists.infradead.org \
--cc=ejo@pengutronix.de \
--cc=yocto@lists.yoctoproject.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