Date: Tue, 17 Dec 2019 16:31:24 -0600 From: Kyle Evans <kevans@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: No suitable SOC memory configuration found. Message-ID: <CACNAnaGC2WtBARnsTghCp4XL07c0B4wAMR-tc%2BeRhYROu9=1Yg@mail.gmail.com> In-Reply-To: <20191217221157.GA18825@www.zefox.net> References: <20191217221157.GA18825@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 17, 2019 at 4:12 PM bob prohaska <fbsd@www.zefox.net> wrote: > > > After updating 12-stable on a Pi2B with a GENERIC kernel the machine > started to fall into an endless boot cycle, reporting in part: > ..... > iichb1: <BCM2708/2835 BSC controller> mem 0x804000-0x80401f irq 10 on simplebus0 > spi0: <BCM2708/2835 SPI controller> mem 0x204000-0x20401f irq 11 on simplebus0 > spibus0: <OFW SPI bus> on spi0 > bcm_dma0: <BCM2835 DMA Controller> mem 0x7000-0x7fff,0xe05000-0xe05fff irq 12,13,14,15,16,17,18,19,20,21,22,23,24 on simplebus0 > Checking root against brcm,bcm2836 > panic: No suitable SOC memory configuration found. > cpuid = 0 > time = 1 > Uptime: 1s > Automatic reboot in 15 seconds - press a key on the console to abort > ..... > > I don't think it's the kernel, because two other kernels, one in the 11-stable > vintage, do the same thing. I did make some changes to /boot/loader.conf and > would like to try skipping it in a boot to single-user to see what happens. > The changes didn't cause obvious/immediate problems, but I've no better ideas. > > Is there some way let the kernel boot -s without reference to loader.conf? > > Thanks for reading, > > bob prohaska Hi, Unfortunately, that error is quite fatal as it needs to be able to deduce what the mappings look like for vcbus <-> armc, otherwise there's an absolutely awesome chance that your board will turn into a raspberry anyways as it can't do DMA. I think you can possibly recover for the time being by dropping to loader prompt and changing /compatible to "brcm,bcm2836" with `fdt prop /compatible brcm,bcm2836` The proper fix is something like the following patch, because the RPi 2B v1.2 (which must be the one you're running here) is actually a 64-bit BCM2837 that we run in an armv7 config, the lowest common denominator of the RPi 2 series. The naming of the new (to armv[67]) option is inconsistent with the other armv[67] broadcom boards, but it's consistent with the arm64 version of this same SoC and I'd prefer to keep it consistent for the same SoC. Thanks, Kyle Evans diff --git a/sys/arm/conf/GENERIC b/sys/arm/conf/GENERIC index c5f39ef916f..9fbc31cb247 100644 --- a/sys/arm/conf/GENERIC +++ b/sys/arm/conf/GENERIC @@ -57,6 +57,7 @@ options SOC_ALLWINNER_A83T options SOC_ALLWINNER_H2PLUS options SOC_ALLWINNER_H3 options SOC_BCM2836 +options SOC_BRCM_BCM2837 options SOC_MV_ARMADA38X options SOC_MV_ARMADAXP options SOC_TI_AM335X diff --git a/sys/conf/options.arm b/sys/conf/options.arm index 1bea34a5865..34229044fbf 100644 --- a/sys/conf/options.arm +++ b/sys/conf/options.arm @@ -47,6 +47,7 @@ SOC_ALTERA_ARRIA10 opt_global.h SOC_ALTERA_CYCLONE5 opt_global.h SOC_BCM2835 opt_global.h SOC_BCM2836 opt_global.h +SOC_BRCM_BCM2837 opt_global.h SOC_IMX51 opt_global.h SOC_IMX53 opt_global.h SOC_IMX6 opt_global.h
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaGC2WtBARnsTghCp4XL07c0B4wAMR-tc%2BeRhYROu9=1Yg>