From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 25 May 2022 17:23:30 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ntsrB-008ofu-O2 for lore@lore.pengutronix.de; Wed, 25 May 2022 17:23:30 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1ntsrB-0007fQ-0G; Wed, 25 May 2022 17:23:29 +0200 Received: from mail.benfm.de ([2a01:238:435a:9a00:9878:863:66f:ea56] helo=h2956758.stratoserver.net) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntsqR-0007fG-4I for ptxdist@pengutronix.de; Wed, 25 May 2022 17:22:45 +0200 Message-ID: <8f755f04-56ea-127b-ce7e-48018a7bc1b8@benfm.de> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benfm.de; s=2020; t=1653492162; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=05kW66xQgquVhifX8CEum+1IoQ7i/E5Ku23aacp7bxI=; b=QRev+YxRcqB90qD8tkEu2+CT7iuKS5zMqdemaeYTrjjiBWjlK1Maw5zYYXf/W22uqiWmDH 3o+ndAXGjRjMHvyipWMnqmll8KxCa6DR4uADNW1xyhG9xkPDWZvPA2j+/kgFW7+yqN7pTK roTQWbNxYmZzTBM24lcMF+gMQKS6e5KxAgMe0WmFhA1p/3zVGsN4j5sb/YTC6TND6/Lixk ScNstOz1zYFvCq+Tr+ocPh6mjziWmz94ZYs7yg9/S7cX246FuWyE8UrvkyNcyFkO6QHlCW WsDFaRk94iFlCnR3sftYhak4LpjFwydVpKledyQ6qceJ3kFxpRUWMvo1ckeD0Q== Date: Wed, 25 May 2022 17:22:41 +0200 MIME-Version: 1.0 Content-Language: en-US To: ptxdist@pengutronix.de From: Felix Mellmann Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Authentication-Results: ORIGINATING; auth=pass smtp.auth=flix@benfm.de smtp.mailfrom=flix.ptxdist@benfm.de X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: [ptxdist] Best practice integrating firmwares in U-Boot builds X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hi, when I tried to set up a PTXdist environment for a NXP i.MX8MP based board (Phytec phyBoard Pollux) I stumbled across the need to provide firmware images during the U-Boot build process (LPDDR4 training data and TF-A BL31 firmware). Is there a best practice on how to provide those firmwares during build? Currently I helped myself and modified u-boot.make to copy the firmware files at the very beginning of the compile stage to the build directory... Best regards, Felix