From owner-freebsd-arm@freebsd.org Thu Sep 15 17:08:21 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF63FBDAA7E for ; Thu, 15 Sep 2016 17:08:21 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7DB6EFB for ; Thu, 15 Sep 2016 17:08:21 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id 93so30715779qtg.2 for ; Thu, 15 Sep 2016 10:08:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:content-transfer-encoding:message-id:date:subject:from :in-reply-to:references:to; bh=m5TUcRpQZH+HB6aQzTC7TVmUAts1tPUT3AJDP5xyOhg=; b=EmY8LBtInYZ3LloPlw5KozxOnxuNN5dZxNG7RjK9t03AfWSmGlXwIT+YzExJYdGuNZ YLin6MG0vEv4yOUpNVG7JusG2+5jPZ0XQEJlYaGzfu4lvN2h01MOSwv66vjSALQaCDFZ oWYWxwM0kw3f9e+Q2hpn/vxN5p935SqCFzncGHgVKomca5w1l4vZItHUou6VnTaVGLCd 6TwrFyZ9eJX+BzrkwlyWF/tbyEFGvPujASs+CKe+WnHn68W50cK4DNLGcDoB0XDB8gDS +FLiLZPdnyv+D2Hv9zrQ7kjK1ENPOhZQ92ren1x5EoMoC4RypE4Y79AISUWI5/syxfpd zDBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:content-transfer-encoding :message-id:date:subject:from:in-reply-to:references:to; bh=m5TUcRpQZH+HB6aQzTC7TVmUAts1tPUT3AJDP5xyOhg=; b=OLy3DUzWFwXN36NCYPm1XS/bJhmUMFPwfv6idbuf04hj0qiNHQSsKziRkQYE7q8tS9 MsEL77V6pwSFaDGC9WylDQ2VvPT3BcUTTgtJuj9OqFrBo2nVnYjxgNz8ev9dI1W/VgZa Q2uBGnR5y9Z0c09QlzlHLZH/i8UO7NGlys0Q4ukGDUQ0PhyCnRVN7Er4sNbVWEH0vYsq FnS1JRZbVlNvob+1lKjrkKDSTW8Eh8BFSZ0CKQDmy+e6uzPh3ECkq8vktp+okCvQt2PV PZJAFpdTySCllE7htfXGZLOJQ66bL6ZdjIGkndVZiX3Xx3mOUY5rhvkuZISLqpx5RAxq Cddw== X-Gm-Message-State: AE9vXwOMnult2nuKe1wmnQDMFWrQfJfmc1H9im1TCUV0tLd4lKcO7J0H9URnZRVZd2qMRg== X-Received: by 10.200.38.147 with SMTP id 19mr10797402qto.67.1473959300698; Thu, 15 Sep 2016 10:08:20 -0700 (PDT) Received: from [127.0.0.1] (c-73-134-53-137.hsd1.md.comcast.net. [73.134.53.137]) by smtp.gmail.com with ESMTPSA id x201sm2302808qkx.32.2016.09.15.10.08.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 15 Sep 2016 10:08:20 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160915170819.5320786.4442.11843@gmail.com> Date: Thu, 15 Sep 2016 13:08:19 -0400 Subject: Re: RPi2 with RedBear IoT pHat cannot boot From: Russell Haley In-Reply-To: <20160915165950.5320786.36203.11840@gmail.com> References: <20160914113900.5320786.47379.11733@gmail.com> <53760d65abcb76c0ee3acf5fe86ad603@zahemszky.hu> <20160915165950.5320786.36203.11840@gmail.com> To: gabor@zahemszky.hu, freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2016 17:08:22 -0000 Please see https://wikidevi.com/wiki/Broadcom under the SDIO section. The t= wo chipsets are in the same group of devices.=C2=A0 Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Virgin=C2=A0Mobile=C2=A0network. =C2=A0 Original Message =C2=A0 From: Russell Haley Sent: Thursday, September 15, 2016 12:59 PM To: gabor@zahemszky.hu; freebsd-arm@freebsd.org Subject: Re: RPi2 with RedBear IoT pHat cannot boot Sorry for the top post.=C2=A0 I said similar or the same, I don't have a lot of bandwidth to check these = things right now.=C2=A0 SDIO (the hardware interface for both chips) is not currently supported by = the FreeBSD kernel and there does not seem to be support for the underlying= Broadcom chips (as there is no SDIO support!), but Mr. Adrian Chadd may be= able to speak more to that. =E2=80=8EHe has previously mentioned that the = chips are very complex and porting them will be time consuming.=C2=A0 There is currently a new SDIO driver making its way into the head branch bu= t it will not be in FreeBSD 11. Mr. Warner Losh could speak more to that.= =C2=A0 Please see =E2=80=8Ehttps://reviews.freebsd.org/D4761 for more details on t= he new CAMMMC driver.=C2=A0 As I am not a hardware/FTD expert, I would guess that the issue you are see= ing is the same both ways: the phat is modifying the hardware signature of = the device, causing the dtb to fail to load. =E2=80=8EBut that's just a gue= ss.=C2=A0 Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Virgin=C2=A0Mobile=C2=A0network. =C2=A0 Original Message =C2=A0 From: gabor@zahemszky.hu Sent: Thursday, September 15, 2016 12:35 PM To: freebsd-arm@freebsd.org Subject: Re: RPi2 with RedBear IoT pHat cannot boot Hi! The saga continues. Under Raspbian, I upgraded the pHAT's firmware from the factory default v0.2 to v0.3. After the FW-upgrade, under Raspbian, it works fine. But under FreeBSD, it got worse, as now it failed to boot at all. The actual message is: Net: Net Initialization Skipped No ethernet found. libfdt fdt_check_header(): FDT_ERR_BADMAGIC Hit any key to stop autoboot: 0 U-Boot> So there is another problem. > I don't know why your getting a dtb error but the modem on the phat is > similar or the same as the Bananapi Pro and is not currently > supported. Well, thats wrong. In the Banana Pro, we can find (from : http://www.lemaker.org/product-bananapro-specification.html ) AP6181 Wifi module. On the RedBear IoT pHAT (from : https://github.com/redbear/IoT_pHAT )=20 there is AP6212A Wireless with BCM43438 (Wifi + Bluetooth) module. (the same Broadcom BCM43438 is in the Pi3.) Thanks, G=C3=A1bor _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"