From nobody Mon Oct 3 03:26:35 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MgmTW5C7qz4fHj0 for ; Mon, 3 Oct 2022 03:26:39 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MgmTV6tktz3Fxf for ; Mon, 3 Oct 2022 03:26:38 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-ej1-x630.google.com with SMTP id sd10so19545311ejc.2 for ; Sun, 02 Oct 2022 20:26:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date; bh=M2C0GmAqkMD5FYTEMNgNRmlMty/5bOvwxrS+c8yg2YA=; b=ca+41UrrG2IvZMUJ+Sw6dxKCAjeokCSVZGbGfaWe1qLBeElwRtdHEMnN1NjBuGu6nY 7fkRlm0eW9sqG1PHLzdwuk+1QN1CrnkAKonRz7kMwtrR+cscJsat03tl2EIlPS8/ywKm F/KvXWhNvH2KOhdpZq2uNiX6Q9v5hMmvh5uk8VUM5Pkgpu0KaGu8wsntJrZIbirPAkYN 6MIcoeVYY3SsGCgwyv4MFInQPJhnZVWVYguVjWN2eH4Vkcc5Jqoq+DYW3ksBeGH74KsG HcWPN0B6cQZWQ6AHaz8Og33Y/DB7RdNR6PMVZeGzTLCjLOBkgPXRwjdQpgLOHM3pot2M qJPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date; bh=M2C0GmAqkMD5FYTEMNgNRmlMty/5bOvwxrS+c8yg2YA=; b=ZF6ExNIx4SUrqvTU51sA7U+csio2uoAslXle8YndtZxzNZq9aZu/EhB2AOBwK/BL6G MMpp1UOqAbS23b6EDzvQWOK8BXAhym5bRH8j5sBFgZWmPyOLhVlFKW2Qx28NaG5rqUC/ 7nYK631kZx8pjlEnY39nHyT5PKFaIMdkKwtJSJ80guEa3+57Q8tf28sHY/qL5enNHiDB Luw/SBbV3EK6TiML9YNLhSFK+xIQZb5Ur3obuyFLp1ke5xEb2MfERf1N1krZ4wSB4g4e jCO7OJcew1oWHxvrDy+NBdMJzgsG671IUTV0t8jbX7blww8+F9TEfGf5UIKYvlzB5THC yXHQ== X-Gm-Message-State: ACrzQf0hnQiiN0vmxkxgGbYklbxDVI3BE1uWdWfJ/a1zb0NljiWon1Xq ttNeVKn8fpWv7ux1ANtG8oT1cTTxF0wKWw== X-Google-Smtp-Source: AMsMyM6e52/xnGZ+B1Uj0J+xKqowgAVU39ek50wJIvPcoEMf1gurgEDo8JBHdt1xjxLOBUv1Qy9glQ== X-Received: by 2002:a17:906:fc6:b0:72f:d080:416 with SMTP id c6-20020a1709060fc600b0072fd0800416mr13835307ejk.1.1664767597875; Sun, 02 Oct 2022 20:26:37 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-061-084.46.114.pool.telefonica.de. [46.114.61.84]) by smtp.googlemail.com with ESMTPSA id e6-20020aa7d7c6000000b00451319a43dasm6493125eds.2.2022.10.02.20.26.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Oct 2022 20:26:37 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Date: Mon, 3 Oct 2022 05:26:35 +0200 References: <20221001174724.GA98055@www.zefox.net> <20221001193033.GA98348@www.zefox.net> <46226720-D867-4AD3-9559-A4365FAC28C4@yahoo.com> <6DB88FC9-629C-43E6-9673-32640FC547F7@yahoo.com> <20221002182049.GA2255@www.zefox.net> <5FFDAA6A-AD8C-4E40-A2EB-4082E5086679@googlemail.com> <38DFEB91-AC60-4FD1-8088-95B0A06C5E5D@yahoo.com> <20221003004624.GA3381@www.zefox.net> To: Mark Millard , bob prohaska , freebsd-arm@freebsd.org In-Reply-To: Message-Id: <385E11EB-A2AB-4218-AA6C-91752B0899A7@googlemail.com> X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4MgmTV6tktz3Fxf X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=googlemail.com header.s=20210112 header.b=ca+41Urr; dmarc=pass (policy=quarantine) header.from=googlemail.com; spf=pass (mx1.freebsd.org: domain of maciphone2@googlemail.com designates 2a00:1450:4864:20::630 as permitted sender) smtp.mailfrom=maciphone2@googlemail.com X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.984]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::630:from]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[googlemail.com:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com,www.zefox.net,freebsd.org]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N > Am 03.10.2022 um 04:30 schrieb Mark Millard : >=20 > On 2022-Oct-2, at 17:46, bob prohaska wrote: >=20 >> On Sun, Oct 02, 2022 at 10:18:28PM +0200, Klaus K??chemann wrote: >>>=20 >>> hard to read and remember every log but I thought Bob wrote about = aprox. 30 successful reboots after the mdelay patch, >>=20 >> That is correct. Shortly afterward I tried a second usb-sata = enclosure. >>=20 >> I didn't immediately notice a difference and though it didn't matter. >> You comments served to make me think again. >>=20 >>> while of course that could be coincidence, who really knows what = happens in this untrackable inconsistent behavior of the usb-boot?! >>=20 >> Unfortunately in this case, human inconsistency (my own, alas) was = compounding at least >> part of the trouble.=20 >>=20 >> The more troublesome bridge contains a JMS577 chip, the less = troublesome JMS576. >=20 > I'm confused. The logs I have show 0x0583 (earlier) and 0x577 (later). > I'm not aware of a 0x0576 example in the set at all. >=20 > (The JMS??? naming and the 0x0??? product ID's normally match for > the ??? part.) >=20 >> = https://pdf1.alldatasheet.com/datasheet-pdf/view/1136441/JMICRON/JMS576.ht= ml >> Contains a brief description, but I didn't see much quantitative = information. >>=20 >> I've reverted the host to the less troublesome JMS576 and will try to=20= >> reproduce some of the earlier results as a sanity check. >=20 > I'll note that I've reverted my active environment back to > its normal content. I've not figured out a way to get > reasonable evidence, given the combinations we have observed. >=20 > I'll note that RPi3 EDK2 UEFI is not an option as far as I > know. I've never had it work for two things that I checked > up front: >=20 > A) microsd cards: Even pre-existing file names for msdosfs > end up messed up. >=20 > B) Serial console: once multi-user (or so) starts it is > garbage >=20 > (I can ssh into the boot but I've not done much that way, > given the problems reported above.) >=20 > Another issue is that Device Tree is needed instead of > ACPI because the ACPI is non-standard [matching Microsoft]. > (For RPi4B EDK2 I use UEFI/ACPI, it being based on the > standard. Some of the RPi4B's normally run under the > UEFI/ACPI environment.) >=20 > I retried RPi3B EDK2 today and the above is still the > status for it. >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com you can probably fix issue B)(MultiUserGarbage) by changing the baudrate = on the fly=E2=80=A6 IIRC e.g. with picocom it was by pressing ctrl-k or so =E2=80=A6 But from past experience I also think that EDK2 is not the solution=E2=80=A6= > Am 03.10.2022 um 04:10 schrieb bob prohaska : > I'd like to see FreeBSD run well on readily available, inexpensive = hardware. That. used to be an i386 PC clone. Soon it'll be something = else. I hope some flavor of Pi. .. > .. I'm just a squeaky wheel. We squeaky wheels tend to use squeaky Operating Systems on squeaky = hardware :-) Ha Ha.. For the Pi platform we would have to immediately begin developing = drivers like Wifi, audio, perhaps graphics=20 to be an appropriate fbsd-client-setup. Understanding bootloaders like here is a good starting point but if we = are not willing to start the driver thing on our own, Without the help of any fbsd-developer, that will be the end of aarch64 cheap hardware for FreeBSD. Instead a cheaper amd64 will do it(makes good progress but even amd is = sometimes frustrating lacking features such as appropriate=20 Bluetooth audio or so). Regards Klaus