RPi2 with RedBear IoT pHat cannot boot

[Adrian Chadd]

Right, but we're missing the "use sdio for non-mmc" bits, which is
what is currently under development. :)


-a


On 15 September 2016 at 10:08, Russell Haley <russ.haley at gmail.com> wrote:
> Please see https://wikidevi.com/wiki/Broadcom under the SDIO section. The two chipsets are in the same group of devices.
>
> Russ
>
> Sent from my BlackBerry 10 smartphone on the Virgin Mobile network.
>   Original Message
> From: Russell Haley
> Sent: Thursday, September 15, 2016 12:59 PM
> To: gabor at zahemszky.hu; freebsd-arm at freebsd.org
> Subject: Re: RPi2 with RedBear IoT pHat cannot boot
>
> Sorry for the top post.
>
> I said similar or the same, I don't have a lot of bandwidth to check these things right now.
>
> 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. ‎He has previously mentioned that the chips are very complex and porting them will be time consuming.
>
> There is currently a new SDIO driver making its way into the head branch but it will not be in FreeBSD 11. Mr. Warner Losh could speak more to that.
>
> Please see ‎https://reviews.freebsd.org/D4761 for more details on the new CAMMMC driver.
>
> As I am not a hardware/FTD expert, I would guess that the issue you are seeing is the same both ways: the phat is modifying the hardware signature of the device, causing the dtb to fail to load. ‎But that's just a guess.
>
> Russ
>
> Sent from my BlackBerry 10 smartphone on the Virgin Mobile network.
>   Original Message
> From: gabor at zahemszky.hu
> Sent: Thursday, September 15, 2016 12:35 PM
> To: freebsd-arm at 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 )
> there is
>
> AP6212A Wireless with BCM43438 (Wifi + Bluetooth) module.
>
> (the same Broadcom BCM43438 is in the Pi3.)
>
> Thanks,
>
> Gábor
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"