Re: [Suit] SUIT architecture examples

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 23 June 2018 14:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 581C3130E5B for <suit@ietfa.amsl.com>; Sat, 23 Jun 2018 07:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64RwfeLjsSI0 for <suit@ietfa.amsl.com>; Sat, 23 Jun 2018 07:26:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77BC5130E58 for <suit@ietf.org>; Sat, 23 Jun 2018 07:26:13 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1536420090; Sat, 23 Jun 2018 10:40:37 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 633F817DD; Sat, 23 Jun 2018 10:23:09 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6131E17DB; Sat, 23 Jun 2018 10:23:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: David Brown <david.brown@linaro.org>
cc: suit <suit@ietf.org>
In-Reply-To: <20180621172040.GA24927@davidb.org>
References: <20180621172040.GA24927@davidb.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Sat, 23 Jun 2018 10:23:09 -0400
Message-ID: <31986.1529763789@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/TeSnIkA3bvnQYIfVwCJKEYQgKWU>
Subject: Re: [Suit] SUIT architecture examples
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2018 14:26:15 -0000

David Brown <david.brown@linaro.org> wrote:
    > ### Dual CPU, other bus

    > This configuration has two or more CPUs, each having their own memory.
    > There will be a communication channel between them, but it will be used
    > as a peripheral, not via shared memory.  In this case, each CPU will
    > have to be responsible for its own firmware upgrade.  It is likely that
    > one of the CPUs will be considered a master, and will direct the other
    > CPU to do the upgrade.  This configuration is commonly used to offload
    > specific work to other CPUs.  Firmware dependencies are similar to the
    > other solutions above, sometimes allowing only one image to be
    > upgraded, other times requiring several to be upgraded atomically.
    > Because the updates are happening on multiple CPUs, upgrading the two
    > images atomically is challenging.

Is there sometimes an ordering constrained between images?
I.e. upgrade CPU-A to version X, before you upgrade CPU-B to version X?

Does the Manifest need to specify this constraint, or would it be implied?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-