From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Çağlar Kilimci" <ckilimci@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Barebox State Framework
Date: Fri, 17 Mar 2017 08:39:33 +0100 [thread overview]
Message-ID: <20170317073933.xiq2uej4qn6c3tp4@pengutronix.de> (raw)
In-Reply-To: <CAGUZs0mnJVHpN59qB5zsZsZA193pnhCpb=vATo-asaKVMj0HfQ@mail.gmail.com>
Hi,
On Thu, Mar 16, 2017 at 04:55:07PM +0300, Çağlar Kilimci wrote:
> Hello all,
>
> As my general purpose of updating a system with RUAC [1], I need to
> use Barebox State Framework but I could not run it properly. I have
> appended Barebox config these:
>
> CONFIG_STATE=y
> CONFIG_STATE_CRYPTO=y
> CONFIG_CMD_SHA1SUM=y
> CONFIG_CMD_SHA224SUM=y
> CONFIG_CMD_SHA256SUM=y
> CONFIG_CMD_SHA384SUM=y
> CONFIG_CMD_SHA512SUM=y
> CONFIG_CMD_STATE=y
> CONFIG_STATE_DRV=y
> CONFIG_DIGEST_HMAC=y
> CONFIG_DIGEST_SHA1_GENERIC=y
> CONFIG_DIGEST_HMAC_GENERIC=y
> CONFIG_CRYPTO_KEYSTORE=y
> CONFIG_BOOTCHOOSER=y
> CONFIG_CMD_BOOTCHOOSER=y
>
> And also, I include below into my dts:
> state: state@0 {
> magic = <0x27031977>;
> compatible = "barebox,state";
> backend-type = "raw";
> backend = "partname:state";
This looks wrong. This should be a phandle pointing to the partition you
want to use.
Otherwise it looks ok. Could you provide a boot log?
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-03-17 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:55 Çağlar Kilimci
2017-03-17 7:39 ` Sascha Hauer [this message]
2017-03-20 4:39 ` Çağlar Kilimci
2017-03-20 7:01 ` 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=20170317073933.xiq2uej4qn6c3tp4@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ckilimci@gmail.com \
/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