mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: <caglar.kilimci@accenture.com>
To: ejo@pengutronix.de
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Caught an error while installing bundle
Date: Tue, 28 Feb 2017 14:24:15 +0000	[thread overview]
Message-ID: <76b4d9aa3e7c4cc783c13eccda46361a@BL2PR4205MB0417.048d.mgd.msft.net> (raw)
In-Reply-To: <d6378ea5-147e-57e8-c81e-9fe166570199@pengutronix.de>

Hi Enrico,

> -----Original Message-----
> From: Enrico Joerns [mailto:ejo@pengutronix.de]
> Sent: Tuesday, February 28, 2017 4:47 PM
> To: Kilimci, Caglar <caglar.kilimci@accenture.com>
> Cc: rauc@pengutronix.de
> Subject: Re: [RAUC] Caught an error while installing bundle
>
> 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?

I tested and still receive error. Output is:
# rauc install update-2017.02-1.raucb
Error creating proxy: Error calling StartServiceByName for de.pengutronix.rauc: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
D-Bus error while installing `/home/root/update-2017.02-1.raucb`


> Could you also verify that the d-bus configuration file `de.pengutronix.rauc.conf` was installed properly on your target?

Sure, it is installed into the device.

# find / -name de.pengutronix.rauc.conf
/usr/share/dbus-1/system.d/de.pengutronix.rauc.conf

Sincerely,
Caglar


________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com
_______________________________________________
RAUC mailing list

  reply	other threads:[~2017-02-28 14:24 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
2017-02-28 14:24   ` caglar.kilimci [this message]
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=76b4d9aa3e7c4cc783c13eccda46361a@BL2PR4205MB0417.048d.mgd.msft.net \
    --to=caglar.kilimci@accenture.com \
    --cc=ejo@pengutronix.de \
    --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