From: Enrico Joerns <ejo@pengutronix.de>
To: caglar.kilimci@accenture.com
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Caught an error while installing bundle
Date: Tue, 28 Feb 2017 14:47:23 +0100 [thread overview]
Message-ID: <d6378ea5-147e-57e8-c81e-9fe166570199@pengutronix.de> (raw)
In-Reply-To: <8795503617fa4662a9fa7e80e75654f7@BL2PR4205MB0417.048d.mgd.msft.net>
Hi Caglar,
On 02/28/2017 01:27 PM, caglar.kilimci@accenture.com wrote:
> Hi all,
>
> First of all thank you such an amazing product. I am really happy to found it.
thank you, too. I hope it will help you solving the update challenges of
your device.
> I have been working on an embedded device which has barebox bootloader and would like to update via RAUC. I have successfully build rauc with meta-ptx layer and I can run rauc on device. In addition, I have created RAUC bundle in my development environment and copied into the device. Even if everything seems fine, I got below error when I would like to install bundle:
> # rauc install update-2017.02-1.raucb
>
> ** (rauc:525): WARNING **: installer is NULL
>
>
> (rauc:525): GLib-GObject-WARNING **: invalid (NULL) pointer instance
>
> (rauc:525): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
>
> ** (rauc:525): ERROR **: failed to connect properties-changed signal caught at main
> Trace/breakpoint trap
we have added some more debugging output and handling to this part since
the last update that has been placed in meta-ptx (note that RAUC support
will be continued in the specialized meta-rauc layer).
Maybe its worth updating to the 0.1 release version of RAUC in your
rauc_%.bbappend file as an initial step. For reference, its sha is
SRCREV = "bce6dcefa01812653fb5b6e087db0c20d930adbe"
Could you test it with this one again and paste the output?
Could you also verify that the d-bus configuration file
`de.pengutronix.rauc.conf` was installed properly on your target?
> Here is my system.conf:
> [system]
> compatible=mydevice
> bootloader=barebox
> mountprefix=/mnt/rauc
>
> [keyring]
> path=/etc/rauc/openssl-ca/dev-ca.pem
>
> [slot.rootfs.0]
> device=/dev/mmcblk0p2
> type=ext4
> bootname=A
>
> [slot.rootfs.1]
> device=/dev/mmcblk0p3
> type=ext4
> bootname=B
>
>
> Here is my manifest file:
> [update]
> compatible= mydevice
> version=2017.02-1
>
> [image.rootfs]
> sha256=265c87e5784fb1ae93fd825f78e6aca0ecd454039019a27e038699d2af311b75
> size=935329792
> filename=rootfs.ext4
These look ok to me.
Best regards
Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2017-02-28 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 12:27 caglar.kilimci
2017-02-28 13:47 ` Enrico Joerns [this message]
2017-02-28 14:24 ` caglar.kilimci
2017-02-28 14:59 ` Enrico Joerns
2017-02-28 15:44 ` caglar.kilimci
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=d6378ea5-147e-57e8-c81e-9fe166570199@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=caglar.kilimci@accenture.com \
--cc=rauc@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