Mongoose update confirmation

[sajjad ahmed]

Hi Stefano, 

After success with hawkbit based update server, now working on mongoose server, I can update firmware from the web interface and reboot the device, now I'm looking for the status update (confirmation option as Hawkbit) by mongoose server. Is there any?

Thanks

Sajjad

[Stefano Babic]

Hi Sajjad,

The browser gets the whole information vie websocket and the result of
the install is reported. This is before you run reboot (or before a
automatically started reboot).

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
=====================================================================

[sajjad ahmed]

Hi, Stefano,

Ok, so after reboot mongoose demon doesn't report the browser about the successful upgrade as suricatta do. Also, the reboot page in the browser has to be reset (to the home page) manually and will not connect to the target automatically after reboot. Right?

Best regards,

Sajjad

[Stefano Babic]

Hi Ahmed,

On 08/04/2018 19:38, sajjad ahmed wrote:
> Hi, Stefano,
>
> Ok, so after reboot mongoose demon doesn't report the browser about the
> successful upgrade as suricatta do. Also, the reboot page in the browser
> has to be reset (to the home page) manually and will not connect to the
> target automatically after reboot. Right?

No. The browser signals during a reboot that connection is lost because
system is restarting, and it connects automatically again when system is
up. You have maybe the old (legacy) website.

[sajjad ahmed]

Hi Stefano,

I'm using the " www/ " directory fetched by yocto's swupdate_2017 recipes. In my case after rootfs update (and target jump to upgraded rootfs), the target does connect to the browser but refreshing the last page [ http://ip_address:8080/rebootTarget ] reboots the target again, so my question is if this is the intended operation and user have to reset the address like [http://ip_address:8080]. Is this some old approach and any better solution is available?

Thanks

Sajjad

[Stefano Babic]

Hi Sajjad,

On 08/04/2018 20:12, sajjad ahmed wrote:
> Hi Stefano,
>
> I'm using the " www/ " directory fetched by yocto's swupdate_2017
> recipes.

This is the legacy website and pages are static, the browser does not
reconnect again. Please use 2018.03 instead.

> In my case after rootfs update (and target jump to upgraded
> rootfs), the target does connect to the browser but refreshing the last

> page [ /http://ip_address:8080/rebootTarget/ ] reboots the target again,

Yes, you are telling to the device to reboot again.

> so my question is if this is the intended operation and user have to
> reset the address like [http://ip_address:8080].
> Is this some old
> approach and any better solution is available?

There is a better approach - use 2018.03.

Regards,