From nobody Thu Mar 30 01:09:00 2023 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 4Pn50p0FM0z428q6 for ; Thu, 30 Mar 2023 01:09:14 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns4.genyosha.net (ns4.genyosha.net [50.53.250.75]) (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 "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pn50n3YBhz4L7Q for ; Thu, 30 Mar 2023 01:09:13 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; none Received: from dragon.home.genyosha.net (ops.genyosha.net [50.53.250.77]) by ns4.genyosha.net (8.17.1/8.16.1) with ESMTPS id 32U195Wh001115 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Mar 2023 18:09:06 -0700 (PDT) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 32U1909p000421; Wed, 29 Mar 2023 18:09:00 -0700 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 32U1901s000420; Wed, 29 Mar 2023 18:09:00 -0700 Date: Wed, 29 Mar 2023 18:09:00 -0700 From: Steve Rikli To: Marcin Cieslak Cc: "freebsd-arm@freebsd.org" Subject: Re: Boot stops at loader after build/install cycle Message-ID: References: <20230327164919.GA65182@www.zefox.net> <20230327183055.GB65182@www.zefox.net> <44509923-0218-5no7-42pp-90ss0sns9457@fncre.vasb> <20230329164845.GA75320@www.zefox.net> 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: X-Greylist: inspected by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Wed, 29 Mar 2023 18:09:06 -0700 (PDT) for IP:'50.53.250.77' DOMAIN:'ops.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Wed, 29 Mar 2023 18:09:06 -0700 (PDT) X-Rspamd-Queue-Id: 4Pn50n3YBhz4L7Q X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20055, ipnet:50.53.0.0/16, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Mar 30, 2023 at 12:24:13AM +0000, Marcin Cieslak wrote: > On Wed, 29 Mar 2023, bob prohaska wrote: > > > If not maybe try different hardware (cables, usb-serial adapters, > > power supplies and so on) with an eye to any changes of behavior. > > At this stage making the problem worse might be more useful than > > making it better. Disconnecting the serial-end ground might be > > worth a try. If the connection still works it suggests you have > > multiple grounds, which can cause trouble. I ended up lifting > > the ground on one of my serial connections. AFAIK both Ethernet > > and USB power supplies are floating, so multiple grounds are very > > unlikely. But something might be faulty. > > The characters look too regular to me, just like a normal terminal > codes, not a line noise. I test the device now powered from the > same USB hub as the USB-serial converter. Rockchip needs 1500000 bps > console, pretty fest. OK, then let's assume your serial cables & hoods etc. are OK for the moment. What does serial console config on the rpi look like? When I specified the rpi4 serial console speed in the config to match my serial terminal server, rather than let it "float" (default 9600), my loader interruptions stopped, and no more stray characters on the serial console after boot either. > Also, uboot autoboot prompt never gets interrupted. > > I also noticed that "resizewin" complains about not getting > information about the terminal upon login on the serial console > while being in the vt(4) text mode. > > Looks like the bootloader tries to send/receives some terminal control > sequences and this fails, interupting the autoboot. It may be something along those lines. When I was getting loader stops during reboot on my rpi4, my guess was the default FreeBSD speed 9600 vs. my serial terminal server setting of 115200 was causing stray characters on the line during boot, loader interpretted that as a keystroke, so it stopped. Cheers, sr.