Date: Thu, 15 Sep 2016 13:08:19 -0400 From: Russell Haley <russ.haley@gmail.com> To: gabor@zahemszky.hu, freebsd-arm@freebsd.org Subject: Re: RPi2 with RedBear IoT pHat cannot boot Message-ID: <20160915170819.5320786.4442.11843@gmail.com> In-Reply-To: <20160915165950.5320786.36203.11840@gmail.com> References: <f398b7d9aaec916522dbff9149326223@zahemszky.hu> <20160914113900.5320786.47379.11733@gmail.com> <53760d65abcb76c0ee3acf5fe86ad603@zahemszky.hu> <20160915165950.5320786.36203.11840@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160915170819.5320786.4442.11843>