mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: Steffen Kothe <steffen.kothe.gc1993@googlemail.com>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] RAUC fails to mark slot as good --> fw_utils access error on mmc
Date: Tue, 14 May 2019 11:47:52 +0200	[thread overview]
Message-ID: <413f3f61-684b-3ddd-cbe8-d05e78ed8753@pengutronix.de> (raw)
In-Reply-To: <1556115423.10295.13.camel@googlemail.com>

Hi Steffen,

On 4/24/19 4:17 PM, Steffen Kothe wrote:
> Hello mailinglist,
> 
> Following error message occured after start of system.
> Log output comes from systemd (rauc.service)
> systemctl status rauc.service
> 
> Apr 24 13:48:43 pixi-cdl100 rauc[478]: Write error on
>>   /dev/mmcblk3boot0: Operation not
>>   permitted                                       > Apr 24 13:48:43
> pixi-cdl100 rauc[478]: Error: can't write fw_env to
>>   flash                                                              >
> Apr 24 13:48:43 pixi-cdl100 rauc[478]: [[0;1;39mrauc mark: Failed
>>   marking 'rootfs.0' as good: Failed to run fw_setenv: Child process
> ex> ited with code
>>   1[[0m
>>                                                      > Apr 24 13:53:51
> 
> fw_utils have the correct setup, a manual call of fw_utils
> shows the correct environment of uboot.
> 
> I fixed this problem with a script, starting before the rauc daemon,
> forcing the mmcblk3bootX devices to enable read/write.
> 
> Why do I need to set the "force_ro" to 0, before rauc can access the u-
> boot environment?
> Why RAUC does not handle the "force_ro" after start?
> 
> Attached the script, which is triggered before the rauc daemon.
> 
> #!/bin/bash                              echo 0 &gt;> /sys/block/mmcblk3boot0/force_ro
> echo 0 $gt;> /sys/block/mmcblk3boot1/force_ro

sorry for being a bit unresponsive, but I was only rarely in the office the last 
weeks. Did you resolve your issue?

Is that intentionally that you have the environment in the eMMC boot partitions? 
Don't you loose the state after updating the bootloader?

We had a similar question as issue on GitHub some time ago:

https://github.com/rauc/rauc/issues/165

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

      reply	other threads:[~2019-05-14  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 14:17 Steffen Kothe
2019-05-14  9:47 ` Enrico Joerns [this message]

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=413f3f61-684b-3ddd-cbe8-d05e78ed8753@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    --cc=steffen.kothe.gc1993@googlemail.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