Suricatta Update Status Bootloader Environment Variable

79 views
Skip to first unread message

Ben Eck

unread,
Apr 11, 2019, 6:50:30 PM4/11/19
to swup...@googlegroups.com, Eric John
Howdy,

I'm working to integrate SWUpdate and Hawkbit on a buildroot based embedded linux device. I'm currently able to install images from Hawkbit, however, I'm having trouble getting the device to report that it has finished/tested the update to Hawkbit. After downloading and installing the image, I get the following message from SWUpdate whenever it polls the Hawkbit server, even after restarting SWUpdate, as they suggest.

[TRACE] : SWUPDATE running :  [get_state] : Read state=1 from persistent storage.

[WARN ] : SWUPDATE running :  [server_has_pending_action] : An already installed update is pending testing, ignoring available update action.
[INFO ] : SWUPDATE running :  [server_has_pending_action] : Please restart SWUpdate to report the test results upstream.
[DEBUG] : SWUPDATE running :  [start_suricatta] : No pending action to process.

So, I have a few questions:

1) What is the name of the bootloader environment state variable that stores the update status? Looking at config.in, seems like it's configurable via menuconfig, and defaults to ustate?

2) Running fw_printenv, it doesn't look like I have any variable named ustate in uboot's environment (and I know that I haven't configured one). If the update status is stored in "ustate" , but that variable hasn't been set up in uboot, how is SWUPdate able to "[get_state] : Read state=1 from persistent storage."?

3) Is it the responsibility of the end user to run tests and update the update status environment variable back to "OK"? I.e. restarting swupdate alone won't do anything unless I change the update status environment variable. I think the answer is yes, but I need to know how to access the variable to do this :)

Thanks!

Ben Eck

Embedded Systems Engineer


OneRain

The Rainfall Company


1531 Skyway Drive | Unit D | Longmont | Colorado 80504

Toll Free  1-800-758-RAIN (7246)

Phone +1-303-774-2033

Fax +1-303-774-2037

E-mail ben...@onerain.com

www.onerain.com

Follow us on LinkedIn and Facebook

An AE Monitoring member company

Stefano Babic

unread,
Apr 13, 2019, 12:24:08 PM4/13/19
to Ben Eck, swup...@googlegroups.com, Eric John
Hi Ben,

On 12/04/19 00:50, Ben Eck wrote:
> Howdy,
>
> I'm working to integrate SWUpdate and Hawkbit on a buildroot based
> embedded linux device. I'm currently able to install images from
> Hawkbit, however, I'm having trouble getting the device to report that
> it has finished/tested the update to Hawkbit. After downloading and
> installing the image, I get the following message from SWUpdate whenever
> it polls the Hawkbit server, even after restarting SWUpdate, as they
> suggest.
>
> [TRACE] : SWUPDATE running :  [get_state] : Read state=1 from persistent
> storage.
>
> [WARN ] : SWUPDATE running :  [server_has_pending_action] : An already
> installed update is pending testing, ignoring available update action.
> [INFO ] : SWUPDATE running :  [server_has_pending_action] : Please
> restart SWUpdate to report the test results upstream.
> [DEBUG] : SWUPDATE running :  [start_suricatta] : No pending action to
> process.
>

This was already discussed, see :

https://groups.google.com/forum/#!searchin/swupdate/hawkbit%7Csort:date/swupdate/UPkuPbmk5X4/XRQBBwL9CwAJ

You have to inform SWUpdate if the new software runs flawlessly. In most
cases, system reboots after an update and the new software should start
SWUPdate with the "-c <state>" parameter. This is forwarded to Hawkbit.

> So, I have a few questions:
>
> 1) What is the name of the bootloader environment state variable that
> stores the update status? Looking at config.in <http://config.in>, seems
> like it's configurable via menuconfig, and defaults to ustate?
>

Yes - you can change it via menuconfig.

> 2) Running fw_printenv, it doesn't look like I have any variable named
> ustate in uboot's environment (and I know that I haven't configured
> one). If the update status is stored in "ustate" , but that variable
> hasn't been set up in uboot, how is SWUPdate able to "[get_state] : Read
> state=1 from persistent storage."?

If you set U-Boot as bootloader, the variable is handled by SWUpdate.
Its value should become "1" (installed).


>
> 3) Is it the responsibility of the end user to run tests and update the
> update status environment variable back to "OK"?

OK ?

> I.e. restarting
> swupdate alone won't do anything unless

Of course, not.

> I change the update status
> environment variable. I think the answer is yes, but I need to know how
> to access the variable to do this :)

Variable is set / reset by SWUpdate if you start it after an update with
-u "-c <state>".

Best regards,
Stefano Babic

--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

Ben Eck

unread,
Apr 15, 2019, 10:52:20 AM4/15/19
to Stefano Babic, swup...@googlegroups.com, Eric John
Ah, how could I miss that? Thanks Stefano. To be clear though, if I wanted to modify ustate in a UBoot script as well instead of starting with the -c option, I can create a UBoot environment variable named ustate and modify it in bootloader scripts and that should also work?

Ben Eck

Embedded Systems Engineer


OneRain

The Rainfall Company


1531 Skyway Drive | Unit D | Longmont | Colorado 80504

Toll Free  1-800-758-RAIN (7246)

Phone +1-303-774-2033

Fax +1-303-774-2037

E-mail ben...@onerain.com

www.onerain.com

Follow us on LinkedIn and Facebook

An AE Monitoring member company


stefano babic

unread,
Apr 15, 2019, 2:39:36 PM4/15/19
to Ben Eck, Stefano Babic, swup...@googlegroups.com, Eric John
Hi Ben,

Am 15.04.19 um 16:51 schrieb Ben Eck:
> Ah, how could I miss that? Thanks Stefano. To be clear though, if I
> wanted to modify ustate in a UBoot script as well instead of starting
> with the -c option,

No.

If you do not start with "-c", SWUpdate does not know which is the
status afetr installing - if new software could not be started, after a
fallback the old software is still running. SWUpdate cannot distinguish
between a fresh update or a reboot, and it won't send anything to
Hawkbit letting the transaction open.

> I can create a UBoot environment variable named
> ustate and modify it in bootloader scripts and that should also work?

You just can reset the variable, but it won't work.

Best regards,
Stefano Babic

>
> Ben Eck
>
> Embedded Systems Engineer
>
>
> OneRain
>
> The Rainfall Company
>
>
> 1531 Skyway Drive | Unit D | Longmont | Colorado 80504
>
> Toll Free 1-800-758-RAIN (7246)
>
> Phone +1-303-774-2033
>
> Fax +1-303-774-2037
>
> E-mail...@onerain.com <mailto:ben...@onerain.com>
>
> www.onerain.com <https://onerain.com/>
>
> Follow us onLinkedIn
> <https://www.linkedin.com/company/onerain>andFacebook
> <https://www.facebook.com/onerain.inc/>
> sba...@denx.de <mailto:sba...@denx.de>
> =====================================================================
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To post to this group, send email to swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

Ben Eck

unread,
Apr 15, 2019, 6:47:25 PM4/15/19
to stefano babic, swup...@googlegroups.com, Eric John
Hi Stefano,

Pardon me for being a little confused, but using a uboot environment variable named 'ustate' instead of the -c flag does in fact seem to work for notifying a hawkbit of a successful update. The status assigned with the suricatta -c flag just seems to override the uboot persistent state set by the ustate variable. 

Are the update_state_t enumerated in state.h  supposed to be the same as the statuses given for the -c flag? E.g  1=AGAIN, 2=SUCCESS, 3=FAILED? They seem to be, except that 2=SUCCESS doesn't seem to match STATE_TESTING.

Thanks again for your help! Your project has been super helpful in getting our software update system off the ground.

Ben Eck

Embedded Systems Engineer


OneRain

The Rainfall Company


1531 Skyway Drive | Unit D | Longmont | Colorado 80504

Toll Free  1-800-758-RAIN (7246)

Phone +1-303-774-2033

Fax +1-303-774-2037

An AE Monitoring member company


Stefano Babic

unread,
Apr 16, 2019, 7:03:37 AM4/16/19
to Ben Eck, stefano babic, swup...@googlegroups.com, Eric John
On 16/04/19 00:47, Ben Eck wrote:
> Hi Stefano,
>
> Pardon me for being a little confused, but using a uboot environment
> variable named 'ustate' instead of the -c flag does in fact seem to work
> for notifying a hawkbit of a successful update.

Yes, the parameter can override the value of the ustate variable. It is
ok how you set it.

> The status assigned with
> the suricatta -c flag just seems to override the uboot persistent state
> set by the ustate variable. 

Correct.

>
> Are the update_state_t enumerated in state.h 
> <https://github.com/sbabic/swupdate/blob/master/include/state.h> supposed to
> be the same as the statuses given for the -c flag? E.g  1=AGAIN,
> 2=SUCCESS, 3=FAILED? They seem to be, except that 2=SUCCESS doesn't seem
> to match STATE_TESTING.

It could be a little confusing. Anyway, 1=INSTALLED is set automatically
after a successful update, and putting the state into 2=TESTING (aks
SUCCESS) means that the new software was started and a feedback is sent
to Hawkbit.

>
> Thanks again for your help! Your project has been super helpful in
> getting our software update system off the ground.

You're welcome.

Best regards,
Stefano Babic

>
> Ben Eck
>
> Embedded Systems Engineer
>
>
> OneRain
>
> The Rainfall Company
>
>
> 1531 Skyway Drive | Unit D | Longmont | Colorado 80504
>
> Toll Free 1-800-758-RAIN (7246)
>
> Phone +1-303-774-2033
>
> Fax +1-303-774-2037
>
> E-mail...@onerain.com <mailto:ben...@onerain.com>
>
> www.onerain.com <https://onerain.com/>
>
> Follow us onLinkedIn
> <https://www.linkedin.com/company/onerain>andFacebook
> <https://www.facebook.com/onerain.inc/>
>
> An AE Monitoring member company
>
>
>
> On Mon, Apr 15, 2019 at 12:39 PM stefano babic <sba...@denx.de
> <mailto:sba...@denx.de>> wrote:
>
> Hi Ben,
>
> Am 15.04.19 um 16:51 schrieb Ben Eck:
> > Ah, how could I miss that? Thanks Stefano. To be clear though, if I
> > wanted to modify ustate in a UBoot script as well instead of starting
> > with the -c option,
>
> No.
>
> If you do not start with "-c", SWUpdate does not know which is the
> status afetr installing - if new software could not be started, after a
> fallback the old software is still running. SWUpdate cannot distinguish
> between a fresh update or a reboot, and it won't send anything to
> Hawkbit letting the transaction open.
>
> > I can create a UBoot environment variable named
> > ustate and modify it in bootloader scripts and that should also work?
>
> You just can reset the variable, but it won't work.
>
> Best regards,
> Stefano Babic
>
> >
> > Ben Eck
> >
> > Embedded Systems Engineer
> >
> >
> > OneRain
> >
> > The Rainfall Company
> >
> >
> > 1531 Skyway Drive | Unit D | Longmont | Colorado 80504
> >
> > Toll Free 1-800-758-RAIN (7246)
> >
> > Phone +1-303-774-2033
> >
> > Fax +1-303-774-2037
> >
> > E-mail...@onerain.com <mailto:E-mail...@onerain.com>
> <mailto:ben...@onerain.com <mailto:ben...@onerain.com>>
> >
> > www.onerain.com <http://www.onerain.com> <https://onerain.com/>
> >
> > Follow us onLinkedIn
> > <https://www.linkedin.com/company/onerain>andFacebook
> > <https://www.facebook.com/onerain.inc/>
> >
> > An AE Monitoring member company
> >
> >
> >
> > On Sat, Apr 13, 2019 at 10:24 AM Stefano Babic <sba...@denx.de
> <mailto:sba...@denx.de>
> >     sba...@denx.de <mailto:sba...@denx.de> <mailto:sba...@denx.de
> <mailto:sba...@denx.de>>
> >   
>  =====================================================================
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "swupdate" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to swupdate+u...@googlegroups.com
> <mailto:swupdate%2Bunsu...@googlegroups.com>
> > <mailto:swupdate+u...@googlegroups.com
> <mailto:swupdate%2Bunsu...@googlegroups.com>>.
> > To post to this group, send email to swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>
> > <mailto:swup...@googlegroups.com <mailto:swup...@googlegroups.com>>.

Stefano Cordibella

unread,
Oct 15, 2025, 9:41:44 AM (7 days ago) Oct 15
to swupdate
Dear Stefano,
    I'm writing on this old post because I have the same doubt: I'm not clear on why the value 2 should be used after an update to report that the update was successful.
In the documentation at https://sbabic.github.io/swupdate/swupdate-best-practise.html#update-concept, I also see that the ustate variable should be set to 0.
Am I misunderstanding something, or does the documentation need to be updated?

Best regards,
Stefano.

Stefano Babic

unread,
Oct 15, 2025, 9:48:29 AM (7 days ago) Oct 15
to Stefano Cordibella, swupdate
On 10/15/25 15:04, Stefano Cordibella wrote:
> Dear Stefano,
>     I'm writing on this old post because I have the same doubt: I'm not
> clear on why the value 2 should be used after an update to report that
> the update was successful.
> In the documentation at https://sbabic.github.io/swupdate/swupdate-best-
> practise.html#update-concept <https://sbabic.github.io/swupdate/
> swupdate-best-practise.html#update-concept>, I also see that the ustate
> variable should be set to 0.

Documentation is correct, ustate is reset to 0 when the transaction is
completed.

SWUpdatwe handles autoimatic the transition 0 (NORMAL) to 1 (INSTALLED).
When the system is booting, you have still the possibility to introduce
another state (if required), or you complete the transaction (as I
usually do, and ustate is set to 0). As Framework, you have free hands.

You decide yourself when the update is successfully tested. Note that
the flag passed to SWUpdate via -c is not the ustate. It declares the
final status of the transaction to be passed to the server. So yes,
SWUpdate will be started with "-c 2" (it means success), and at the same
time the ustate env variable is reset to 0.

Best regards,
Stefano Babic

> Am I misunderstanding something, or does the documentation need to be
> updated?
>
> Best regards,
> Stefano.
>
> On Tuesday, April 16, 2019 at 1:03:37 PM UTC+2 Stefano Babic wrote:
>
> On 16/04/19 00:47, Ben Eck wrote:
> > Hi Stefano,
> >
> > Pardon me for being a little confused, but using a uboot environment
> > variable named 'ustate' instead of the -c flag does in fact seem
> to work
> > for notifying a hawkbit of a successful update.
>
> Yes, the parameter can override the value of the ustate variable. It is
> ok how you set it.
>
> > The status assigned with
> > the suricatta -c flag just seems to override the uboot persistent
> state
> > set by the ustate variable.
>
> Correct.
>
> >
> > Are the update_state_t enumerated in state.h
> > <https://github.com/sbabic/swupdate/blob/master/include/state.h
> <https://github.com/sbabic/swupdate/blob/master/include/
> state.h>> supposed to
> > be the same as the statuses given for the -c flag? E.g  1=AGAIN,
> > 2=SUCCESS, 3=FAILED? They seem to be, except that 2=SUCCESS
> doesn't seem
> > to match STATE_TESTING.
>
> It could be a little confusing. Anyway, 1=INSTALLED is set
> automatically
> after a successful update, and putting the state into 2=TESTING (aks
> SUCCESS) means that the new software was started and a feedback is sent
> to Hawkbit.
>
> >
> > Thanks again for your help! Your project has been super helpful in
> > getting our software update system off the ground.
>
> You're welcome.
>
> Best regards,
> Stefano Babic
>
> >
> > Ben Eck
> >
> > Embedded Systems Engineer
> >
> >
> > OneRain
> >
> > The Rainfall Company
> >
> >
> > 1531 Skyway Drive | Unit D | Longmont | Colorado 80504
> >
> > Toll Free 1-800-758-RAIN (7246)
> >
> > Phone +1-303-774-2033 <tel:(303)%20774-2033>
> >
> > Fax +1-303-774-2037 <tel:(303)%20774-2037>
> >
> > E-mail...@onerain.com <mailto:ben...@onerain.com>
> <https://onerain.com/>>
> >
> > Follow us onLinkedIn
> > <https://www.linkedin.com/company/onerain <https://
> www.linkedin.com/company/onerain>>andFacebook
> > <https://www.facebook.com/onerain.inc/ <https://www.facebook.com/
> > > Phone +1-303-774-2033 <tel:(303)%20774-2033>
> > >
> > > Fax +1-303-774-2037 <tel:(303)%20774-2037>
> > >
> > > E-mail...@onerain.com <mailto:E-mail...@onerain.com>
> > <mailto:ben...@onerain.com <mailto:ben...@onerain.com>>
> > >
> > > www.onerain.com <http://www.onerain.com> <http://
> <https://onerain.com/>>
> > >
> > > Follow us onLinkedIn
> > > <https://www.linkedin.com/company/onerain <https://
> www.linkedin.com/company/onerain>>andFacebook
> > > <https://www.facebook.com/onerain.inc/ <https://
> hawkbit%7Csort:date/swupdate/UPkuPbmk5X4/XRQBBwL9CwAJ <https://
> groups.google.com/forum/#!searchin/swupdate/hawkbit%7Csort:date/
> swupdate/UPkuPbmk5X4/XRQBBwL9CwAJ>
> > >
> > >     You have to inform SWUpdate if the new software runs
> > flawlessly. In most
> > >     cases, system reboots after an update and the new software
> > should start
> > >     SWUPdate with the "-c <state>" parameter. This is forwarded to
> > Hawkbit.
> > >
> > >     > So, I have a few questions:
> > >     >
> > >     > 1) What is the name of the bootloader environment state
> > variable that
> > >     > stores the update status? Looking at config.in <http://
> config.in>
> > <http://config.in <http://config.in>> <http://config.in <http://
> config.in>>
> > >     <http://config.in <http://config.in>>, seems
> > >     Phone: +49-8142-66989-53 <tel:+49%208142%206698953> Fax:
> +49-8142-66989-80 <tel:+49%208142%206698980> Email:
> > > sba...@denx.de <mailto:sba...@denx.de> <mailto:sba...@denx.de
> > <mailto:sba...@denx.de>>
> > >
> >
>  =====================================================================
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "swupdate" group.
> > > To unsubscribe from this group and stop receiving emails from
> it, send
> > > an email to swupdate+u...@googlegroups.com
> > <mailto:swupdate%2Bunsu...@googlegroups.com>
> > > <mailto:swupdate+u...@googlegroups.com
> > <mailto:swupdate%2Bunsu...@googlegroups.com>>.
> > > To post to this group, send email to swup...@googlegroups.com
> > <mailto:swup...@googlegroups.com>
> > > <mailto:swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>>.
> > > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
> >
> > --
> >
> =====================================================================
> > DENX Software Engineering GmbH,      Managing Director: Wolfgang
> Denk
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> Germany
> > Phone: +49-8142-66989-53 <tel:+49%208142%206698953> Fax:
> +49-8142-66989-80 <tel:+49%208142%206698980> Email:
> > sba...@denx.de <mailto:sba...@denx.de>
> >
> =====================================================================
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "swupdate" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to swupdate+u...@googlegroups.com
> > <mailto:swupdate+u...@googlegroups.com>.
> > To post to this group, send email to swup...@googlegroups.com
> > <mailto:swup...@googlegroups.com>.
> > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> =====================================================================
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 <tel:+49%208142%206698953> Fax:
> +49-8142-66989-80 <tel:+49%208142%206698980> Email: sba...@denx.de
> =====================================================================
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> swupdate/97631b4e-8237-48a6-865d-229f6eb9a9dcn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> swupdate/97631b4e-8237-48a6-865d-229f6eb9a9dcn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Stefano Cordibella

unread,
Oct 15, 2025, 9:55:59 AM (7 days ago) Oct 15
to swupdate
Thank you Stefano for the clarification (and the quick reply).

I understand the flexibility given by the tool.
So it is wrong to set ustate to 2 in env after a reboot and a successful update before the swupdate startup?
Looking into the code if I set ustate to 2 then swupdate will set it to 0 after sending the "transaction close" message to the server.

Best regards,
Stefano.

Stefano Babic

unread,
Oct 15, 2025, 10:03:10 AM (7 days ago) Oct 15
to Stefano Cordibella, swupdate
On 10/15/25 15:55, Stefano Cordibella wrote:
> Thank you Stefano for the clarification (and the quick reply).
>
> I understand the flexibility given by the tool.
> So it is wrong to set ustate to 2 in env after a reboot and a successful
> update before the swupdate startup?

The bootloader touces ustate only in case of a fallback, that is new
software does not start. In that case, it should marked the update as
failed by setting ustate=3.

Else ustate is not touched at all.

> Looking into the code if I set ustate to 2 then swupdate will set it to
> 0 after sending the "transaction close" message to the server.

Best regards,
Stefano Babic

>
> Best regards,
> Stefano.
> On Wednesday, October 15, 2025 at 3:48:29 PM UTC+2 Stefano Babic wrote:
>
> On 10/15/25 15:04, Stefano Cordibella wrote:
> > Dear Stefano,
> >     I'm writing on this old post because I have the same doubt:
> I'm not
> > clear on why the value 2 should be used after an update to report
> that
> > the update was successful.
> > In the documentation at https://sbabic.github.io/swupdate/
> swupdate-best- <https://sbabic.github.io/swupdate/swupdate-best->
> > <https://github.com/sbabic/swupdate/blob/master/include/
> <https://github.com/sbabic/swupdate/blob/master/include/>
> > state.h>> supposed to
> > > be the same as the statuses given for the -c flag? E.g  1=AGAIN,
> > > 2=SUCCESS, 3=FAILED? They seem to be, except that 2=SUCCESS
> > doesn't seem
> > > to match STATE_TESTING.
> >
> > It could be a little confusing. Anyway, 1=INSTALLED is set
> > automatically
> > after a successful update, and putting the state into 2=TESTING (aks
> > SUCCESS) means that the new software was started and a feedback
> is sent
> > to Hawkbit.
> >
> > >
> > > Thanks again for your help! Your project has been super helpful in
> > > getting our software update system off the ground.
> >
> > You're welcome.
> >
> > Best regards,
> > Stefano Babic
> >
> > >
> > > Ben Eck
> > >
> > > Embedded Systems Engineer
> > >
> > >
> > > OneRain
> > >
> > > The Rainfall Company
> > >
> > >
> > > 1531 Skyway Drive | Unit D | Longmont | Colorado 80504
> > >
> > > Toll Free 1-800-758-RAIN (7246)
> > >
> > > Phone +1-303-774-2033 <tel:(303)%20774-2033> <tel:
> (303)%20774-2033>
> > >
> > > Fax +1-303-774-2037 <tel:(303)%20774-2037> <tel:(303)%20774-2037>
> > >
> > > E-mail...@onerain.com <mailto:ben...@onerain.com>
> > >
> > <https://onerain.com/ <https://onerain.com/>>>
> > >
> > > Follow us onLinkedIn
> > > <https://www.linkedin.com/company/onerain <https://
> www.linkedin.com/company/onerain> <https://
> > www.linkedin.com/company/onerain <http://www.linkedin.com/
> company/onerain>>>andFacebook
> > > <https://www.facebook.com/onerain.inc/ <https://
> www.facebook.com/onerain.inc/> <https://www.facebook.com/ <https://
> www.facebook.com/>
> > > > Phone +1-303-774-2033 <tel:(303)%20774-2033> <tel:
> (303)%20774-2033>
> > > >
> > > > Fax +1-303-774-2037 <tel:(303)%20774-2037> <tel:
> (303)%20774-2037>
> > > >
> > > > E-mail...@onerain.com <mailto:E-mail...@onerain.com>
> > > <mailto:ben...@onerain.com <mailto:ben...@onerain.com>>
> > > >
> > > > www.onerain.com <http://www.onerain.com> <http://
> www.onerain.com <http://www.onerain.com>> <http://
> www.linkedin.com/company/onerain> <https://
> > www.linkedin.com/company/onerain <http://www.linkedin.com/
> company/onerain>>>andFacebook
> > > > <https://www.facebook.com/onerain.inc/ <https://
> www.facebook.com/onerain.inc/> <https://
> > www.facebook.com/onerain.inc/ <http://www.facebook.com/
> onerain.inc/>>>
> > > >
> > > > An AE Monitoring member company
> > > >
> > > >
> > > >
> > > https://groups.google.com/forum/#!searchin/swupdate/ <https://
> groups.google.com/forum/#!searchin/swupdate/>
> > hawkbit%7Csort:date/swupdate/UPkuPbmk5X4/XRQBBwL9CwAJ <https://
> > groups.google.com/forum/#!searchin/swupdate/hawkbit%7Csort:date/
> <http://groups.google.com/forum/#!searchin/swupdate/
> hawkbit%7Csort:date/>
> > swupdate/UPkuPbmk5X4/XRQBBwL9CwAJ>
> > > >
> > > >     You have to inform SWUpdate if the new software runs
> > > flawlessly. In most
> > > >     cases, system reboots after an update and the new software
> > > should start
> > > >     SWUPdate with the "-c <state>" parameter. This is
> forwarded to
> > > Hawkbit.
> > > >
> > > >     > So, I have a few questions:
> > > >     >
> > > >     > 1) What is the name of the bootloader environment state
> > > variable that
> > > >     > stores the update status? Looking at config.in <http://
> config.in> <http://
> config.in>>> <http://config.in <http://config.in> <http://
> > config.in <http://config.in>>>
> > > >     <http://config.in <http://config.in> <http://config.in
> > > >     Phone: +49-8142-66989-53 <tel:+49%208142%206698953> <tel:
> +49%208142%206698953> Fax:
> > +49-8142-66989-80 <tel:+49%208142%206698980> <tel:
> +49%208142%206698980> Email:
> > > > sba...@denx.de <mailto:sba...@denx.de> <mailto:sba...@denx.de
> > > <mailto:sba...@denx.de>>
> > > >
> > >
> >
>  =====================================================================
> > > >
> > > > --
> > > > You received this message because you are subscribed to the
> Google
> > > > Groups "swupdate" group.
> > > > To unsubscribe from this group and stop receiving emails from
> > it, send
> > > > an email to swupdate+u...@googlegroups.com
> > > <mailto:swupdate%2Bunsu...@googlegroups.com>
> > > > <mailto:swupdate+u...@googlegroups.com
> > > <mailto:swupdate%2Bunsu...@googlegroups.com>>.
> > > > To post to this group, send email to swup...@googlegroups.com
> > > <mailto:swup...@googlegroups.com>
> > > > <mailto:swup...@googlegroups.com
> > <mailto:swup...@googlegroups.com>>.
> > > > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> > <https://groups.google.com/d/optout <https://groups.google.com/d/
> optout>>.
> > >
> > > --
> > >
> >
> =====================================================================
> > > DENX Software Engineering GmbH,      Managing Director: Wolfgang
> > Denk
> > > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> > Germany
> > > Phone: +49-8142-66989-53 <tel:+49%208142%206698953> <tel:
> +49%208142%206698953> Fax:
> > +49-8142-66989-80 <tel:+49%208142%206698980> <tel:
> +49%208142%206698980> Email:
> > > sba...@denx.de <mailto:sba...@denx.de>
> > >
> >
> =====================================================================
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "swupdate" group.
> > > To unsubscribe from this group and stop receiving emails from it,
> > send
> > > an email to swupdate+u...@googlegroups.com
> > > <mailto:swupdate+u...@googlegroups.com>.
> > > To post to this group, send email to swup...@googlegroups.com
> > > <mailto:swup...@googlegroups.com>.
> > > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> > <https://groups.google.com/d/optout <https://groups.google.com/d/
> optout>>.
> >
> >
> > --
> >
> =====================================================================
> > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> Germany
> > Phone: +49-8142-66989-53 <tel:+49%208142%206698953> <tel:
> +49%208142%206698953> Fax:
> > +49-8142-66989-80 <tel:+49%208142%206698980> <tel:
> +49%208142%206698980> Email: sba...@denx.de
> >
> =====================================================================
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "swupdate" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to swupdate+u...@googlegroups.com
> > <mailto:swupdate+u...@googlegroups.com>.
> > To view this discussion visit https://groups.google.com/d/msgid/
> <https://groups.google.com/d/msgid/>
> > swupdate/97631b4e-8237-48a6-865d-229f6eb9a9dcn%40googlegroups.com
> <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/ <https://groups.google.com/d/
> msgid/>
> > swupdate/97631b4e-8237-48a6-865d-229f6eb9a9dcn%40googlegroups.com
> <http://40googlegroups.com>?
> > utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> swupdate/8658f3b9-7b2d-40e7-861b-3336713c8d7bn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> swupdate/8658f3b9-7b2d-40e7-861b-3336713c8d7bn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Reply all
Reply to author
Forward
0 new messages