From owner-freebsd-arm@freebsd.org Sun Oct 11 13:38:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A5F5A3F4AD8 for ; Sun, 11 Oct 2020 13:38:49 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C8NF44sBqz4FSm; Sun, 11 Oct 2020 13:38:48 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sun, 11 Oct 2020 13:38:39 +0000 To: Klaus Cucinauomo From: Robert Crowston Cc: Kyle Evans , "gonzo@freebsd.org" , Mark Millard , "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]? Message-ID: In-Reply-To: References: <2B1B21CB-1A63-42CE-8917-98870C88CACE@yahoo.com> <3E9D015B-5702-4A52-9366-49E20BDDA5F4@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch X-Rspamd-Queue-Id: 4C8NF44sBqz4FSm X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.55 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; RCPT_COUNT_FIVE(0.00)[5]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-0.80)[-0.800]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.83)[-0.831]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.92)[-0.922]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from]; FREEMAIL_CC(0.00)[freebsd.org,FreeBSD.org,yahoo.com]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2020 13:38:49 -0000 After updating to the latest dtb firmware from https://github.com/raspberry= pi/firmware/tree/63b192231130f1bdd074f3ae0794889d53bdeb06/boot, and flashin= g the eeprom to the 2020-09-03 version, my system boots just fine. https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5703 All I did was remove the device_tree_address=3D0x4000 from config.txt. # cat config.txt arm_64bit=3D1 armstub=3Darmstub8-gic.bin dtoverlay=3Ddisable-bt dtoverlay=3Dmmc enable_jtag_gpio=3D1 enable_uart=3D1 kernel=3Du-boot.bin (I have not tried updating u-boot yet.) Am I missing something here? =E2=80=94 RHC. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Sunday, 11 October 2020 14:17, Klaus Cucinauomo wrote: > > > > Am 11.10.2020 um 15:11 schrieb Robert Crowston crowston@protonmail.com: > > > > > That=E2=80=99s the problem, armstub8-gic should have been removed whe= n using modern firmware because it no longer depends on it. > > > > So are you telling me that I could rip out all the startup logic from t= he armstub and just leave our CPU spin up logic? > > =E2=80=94 RHC. > > yes, exactly, even : > $rm /Volumes/MSDOSBOOT/armstub8-gic.bin > > ( while I wouldn't swear that the initialization of your pcie driver from= fdt will continue to run smoothly in the boot-process directly from SSD, > I expect necessary adjustments..) > > K.