From nobody Mon Sep 26 01:04:20 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 4MbPfW65Lhz4cPwS; Mon, 26 Sep 2022 01:04:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MbPfV3sL6z41D3; Mon, 26 Sep 2022 01:04:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 28Q14Kdi064781 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 25 Sep 2022 18:04:20 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 28Q14KhW064780; Sun, 25 Sep 2022 18:04:20 -0700 (PDT) (envelope-from fbsd) Date: Sun, 25 Sep 2022 18:04:20 -0700 From: bob prohaska To: Mark Millard Cc: FreeBSD Mailing List , freebsd-arm Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <20220926010420.GA64437@www.zefox.net> References: <20220921154240.GA37735@www.zefox.net> <8CC2A42B-21AC-44C6-BD02-44D320CADF63@yahoo.com> <20220921175026.GA45144@www.zefox.net> <5DB9C93B-B9E1-418D-ABA3-8A0CFCE85C0F@yahoo.com> <3781CF46-C4F7-4579-8655-B7558B724C0A@yahoo.com> <20220922014500.GA46697@www.zefox.net> <20220925160531.GA63213@www.zefox.net> <20220925193415.GA63733@www.zefox.net> <0C5BA8D9-0EEB-421A-99E7-2E6F10D5D425@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0C5BA8D9-0EEB-421A-99E7-2E6F10D5D425@yahoo.com> X-Rspamd-Queue-Id: 4MbPfV3sL6z41D3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-0.82 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; NEURAL_HAM_LONG(-0.73)[-0.733]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org,freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[zefox.net]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, Sep 25, 2022 at 03:57:34PM -0700, Mark Millard wrote: > On 2022-Sep-25, at 12:34, bob prohaska wrote: > > > > . . . > > > > IIRC I did try replacing the Sabrent enclosure with the Startech > > enclosure, which worked and seemed to implicate the Sabrent as > > the culprit. Thus my interest in u-boot debug information. > > Looking at https://u-boot.readthedocs.io/en/latest/develop/logging.html > it appears the logging availability has to be enabled at compile time: > > QUOTE > Enabling logging > > The following options are used to enable logging > at compile time: > > ??? CONFIG_LOG - Enables the logging system > ??? CONFIG_LOG_MAX_LEVEL - Max log level to > build (anything higher is compiled out) > ??? CONFIG_LOG_CONSOLE - Enable writing log > records to the console > > If CONFIG_LOG is not set, then no logging will be available. > > The above have SPL and TPL versions also, e.g. > CONFIG_SPL_LOG_MAX_LEVEL and CONFIG_TPL_LOG_MAX_LEVEL. > > If logging is disabled, the default behaviour is to output > any message at level LOGL_INFO and below. If logging is > disabled and DEBUG is defined (at the very top of a C file) > then any message at LOGL_DEBUG will be written. > END QUOTE > I looked at the page but didn't understand where/how to set those parameters. Do they go in a configuration or Makefile somewhere? I tried using setenv CONFIG_LOG 1 setenv CONFIG_LOG_CONSOLE 1 setenv CONFIG_LOG_MAX_LEVEL 4 [The numbers were guessed at] All showed up in an env command, but the the resulting u-boot.bin executable did not change size and behaves as before. Apologies if I'm being dense! bob prohaska