From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question regarding SWUpdate ..... from command line
Date: Fri, 1 Mar 2019 13:26:20 +0100 [thread overview]
Message-ID: <20190301132620.41862f06@jawa> (raw)
In-Reply-To: <cf8ddc2f-61b7-6243-6144-1c7ff28f5f53@denx.de>
Hi Stefano,
> Hallo Lukasz,
>
> On 27/02/19 10:13, Lukasz Majewski wrote:
> > Hi Stefano.
> >
> >> Hi Lukasz,
> >>
> >> I have the use case and a tbot testcase. But we are now at EW,
> >> please wait until I am back.
> >
> > Ach.... I've just realised this :-)
> > Have a nice time there :-)
> >
>
> We are back, but I think today I just answer to mails...
I hope that you (all) enjoyed EW ;-)
>
> I have added our tbot experts to the list because we have discussed
> some topics at EW.
I've also shared some thoughts/feedback with Harald regarding tbot.
>
> >>
> >> Stefano
> >>
> >> On 25/02/19 23:57, Lukasz Majewski wrote:
> >>> On Mon, 25 Feb 2019 16:03:48 +0100
> >>> Lukasz Majewski <lukma@denx.de> wrote:
> >>>
> >>>> Dear Stefano,
> >>>>
> >>>> I'm wondering if there is any way to emulate SWUpdate http
> >>>> frontend from command line (to send *.swu images via command
> >>>> line)?
> >>>>
> >>>> I'm looking for a solution to automatically flash debug images on
> >>>> the target (and no interaction with browser is necessary).
> >>>>
> >>>> Have you had previously any such use case?
> >>>
> >>> The exact use case is to:
> >>>
> >>> - Re-build production images with
> >>> EXTRA_IMAGE_FEATURES="empty-root-password"
> >>>
> >>> - Force the board to SWUpdate (this is done from production
> >>> on-board SW)
> >>>
> >>> - Use some scripts to send *.swu images and prepare that board for
> >>> testing.
> >>>
> >>> Some curl magic like:
> >>>
> >>> curl -v --insecure --request POST --data-binary
> >>> "@swu-image-emmc-backup-display5.swu" http://192.168.2.130:8080
> >>>
> >>> Is not (yet) working properly - but some page info is displayed.
> >>>
>
> I have written a tbot testcase that I have already used on a couple of
> board and it covers an update using the internal Webserver (your case,
> in fact). I have also dome other case in my list, ant last but not
> least, also a tc working with Hawkbit is in my list (I have to refresh
> my Java knowledge..). We discussed also how to share this - we agree
> that tc should be shared, not yet clear how.
Ok. Good :-)
>
> In the meantime, I can propose I will push a public repo with just tc
> (no boards, no labs at all) and we can use it as container for tc we
> currently have. tc could be picked up later from this container andwe
> could also dropped this repo in future after replacing with something
> better. Any thought (pro or contra) ?
Yes, I think that it is a good idea.
>
> Best regards,
> Stefano
>
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190301/97e2ccf8/attachment.sig>
prev parent reply other threads:[~2019-03-01 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190225160348.03e213bc@jawa>
[not found] ` <20190225235708.77f3c525@jawa>
[not found] ` <bfc82bc7-0ec2-5e1b-44ff-f669dd1366a5@denx.de>
[not found] ` <20190227101316.2eef8ea8@jawa>
2019-03-01 12:17 ` [U-Boot] Question regarding SWUpdate ..... from command line Stefano Babic
2019-03-01 12:26 ` Lukasz Majewski [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=20190301132620.41862f06@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.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