From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6F429C433EF for ; Fri, 26 Nov 2021 07:53:57 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id E84F38372E; Fri, 26 Nov 2021 08:53:54 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=fail (p=none dis=none) header.from=etri.re.kr Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=dooray.com header.i=@dooray.com header.b="yG7OBDMu"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id D54CF8371F; Fri, 26 Nov 2021 08:53:52 +0100 (CET) Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 9E92883019 for ; Fri, 26 Nov 2021 08:53:44 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=etri.re.kr Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=ckim@etri.re.kr Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 26 Nov 2021 16:53:40 +0900 X-Original-SENDERIP: 211.180.235.152 X-Original-MAILFROM: ckim@etri.re.kr X-Original-RCPTTO: u-boot@lists.denx.de Received: from [10.162.225.112] (HELO smtp002-imp.gov-dooray.com) ([10.162.225.112]) by send001-relay.gov-dooray.com with SMTP id 3684700d61a09284; Fri, 26 Nov 2021 16:53:40 +0900 DKIM-Signature: a=rsa-sha256; b=yG7OBDMuxnk0XmMWcQ3cCx3PHNzaMEXiCfmEHkouUsWKvfjnn+6n6lhDXycoKBDNPM05MT42rH GIsov1oEbklitOoitsjK9jtTLMNPuyZODXdrYORETqH94DrpwF8E/dmNPHIsDXxR5Wk0nxzsgniz 5fzEYV9HzkPL+PCEkXTl6QlBc1B8RIDLXxCYjiJMgGS7Jnbr2zpQJIquU00f+nqUuxqbc7cZYoUk 2ygsNleao3vTt1lFVarwyZ7/qsfjhQq/9LBgUp4+IQgt9J1kIygHbb3MnRWl26Plap6DHq0Sv4Ay n3dj1y+tap3+MceEfs6ulrXKpT6RAZgLPtziV8Gw==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=tQbbTE8hZas7yJZDEYXsEBVm2kd/tGL3kSVMvvBj6ew=; h=From:To:Subject:Message-ID; Received: from [129.254.132.39] (HELO CHANKIMPC) ([129.254.132.39]) by smtp002-imp.gov-dooray.com with SMTP id c4f60acc61a09283; Fri, 26 Nov 2021 16:53:40 +0900 From: "Chan Kim" To: "'Alex G.'" , "'U-Boot Mailing List'" References: <027001d7e1cb$14bc3b90$3e34b2b0$@etri.re.kr> <27ce6d77-2a3e-a9e2-cce2-00f76d7af57e@gmail.com> In-Reply-To: <27ce6d77-2a3e-a9e2-cce2-00f76d7af57e@gmail.com> Subject: RE: a question about falcon mode Date: Fri, 26 Nov 2021 16:53:38 +0900 Message-ID: <02c901d7e29a$b8e89450$2ab9bcf0$@etri.re.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Content-Language: ko Thread-Index: AQJ5aaDc+BW56ASqsIz9Bx90TdqoXAGmVeQvqsUp78A= X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.37 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean Hi Alex, Thanks for the reply. So I gather that to be able to use 'spl export fdt' to store the = 'snapshot' to the storage I should make the spl program runnable at = least to that stage. (being able to load kernel image, dtb, initrd and = give the spl export command to capture it to storage like SD card). What I'm thinking of is to let another processor(cortext-M7 based scp, = system control processor) load the u-boot-spl.bin into on-chip RAM and = kernel(including initramfs)and dtb into SDRAM all from SD card (RAW = mode, no file system) and let the AP(application processor) start from = u-boot-spl.bin. In this scheme u-boot-spl doesn't need to load anything = and DRAM is already initialized and it just needs to run from kernel = image after very minimal setup (passing kernel arguments). Do you think = this is possible or an absurd idea? Any comment will be a big help for me. Thanks! Chan=20 > -----Original Message----- > From: Alex G. > Sent: Thursday, November 25, 2021 11:57 PM > To: Chan Kim ; U-Boot Mailing List = > Subject: Re: a question about falcon mode >=20 > On 11/25/21 1:07 AM, Chan Kim wrote: > > Hello all, > > > > I'm trying to implement falcon mode for our board. Then should I = first > > implement the normal mode(spl + proper)? > > > > It looks like so while I'm reading doc/README.falcon. (It says, = after > > loading kernel, DT etc. I should give 'spl export' command). > > >=20 > Falcon mode is a bit board dependent. There are a couple of ways you > could go about this. >=20 > The first is to have an "fdtargs" partition. This is where "spl = export" > comes in. Once you run "spl export", it will give a modified dtb at > "$fdtargsaddr". It's that DTB that you need to write to your ftdargs > partition. For example: >=20 > > spl export fdt $loadaddr - $fdt_addr_r > > mmc write $fdtargsaddr 0x9800 0x8000 >=20 > In this example the ftdargs partition starts at sector 0x9800, and is > 0x800 sectors long. >=20 >=20 > The second option is to forget about "spl export" and "fdtargs", and > package your kernel, devicetree, and overlays in a FIT container. = You'd > make sure to enable SPL_LOAD_FIT_APPLY_OVERLAY. There isn't much more = to > this other than the usual gotcha's with FIT and overlays. >=20 > Alex >=20 >=20