Newbie questions getting a not yet supported board going (bananapi m2 zero)

Hi all, I recently got myself a bananapi m2 zero. It works well with armbian. Naive as I am, I tried to boot the openSUSE-Tumbleweed-ARM-XFCE-sinovoipbpim2plus.armv7l.raw on it and of course failed miserably :-) Today, with a serial console attached I found out that u-boot did not find the sdcard. OK, I just copied the u-boot from the armbian image over (after finding out it is directly on the SD card unpartitioned "header.." ;-)) and now it boots into GRUB and later even to a login prompt on the serial console. But there is nothing on the display (I would not care) and, worse, no ethernet / WiFi. I guess I'd need a matching device tree file for the board (I also needed to recompile it for armbian to use the USB OTG port as an USB host port), but I failed at finding out where I could specify the dtb file to be used for booting. Any hints on where to look for this? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi,
I would expect it to work, since config has CONFIG_MMC_SUNXI_SLOT_EXTRA=2 to enable it. Could you share a bit more about this SD card failure, please?
The dtb should installed as part of dtb-sun8i package. But we have a kernel failure with -lpae flavor, so there may be a mismatch between dtb and kernel. You may want to try kernel-default instead. Cheers, Guillaume

(this time with the correct list address... m) Hi Guillaume, On 11.12.20 14:15, Guillaume Gardet wrote:
Thanks for the offer, but a pointer what I would need to change to do this on my own would already be enough ;-) I guess that branching openSUSE:Factory:ARM/u-boot, adding the config and _multibuild, then using this in a new image branched from openSUSE:Factory:ARM/JeOS is the way to go? Any other caveats to look out for? This would be a nice project for the upcoming locked down holidays ;-) Best regards, Stefan (I corrected the mailing list address, it looks like opensuse-arm@opensuse.org gets mapped to the mailing list, but it does not get sorted correctly on my side, then for whatever reason)
-- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi Guillaume, I could not wait until the holidays ;-) On 11.12.20 17:31, Stefan Seyfried wrote:
I linked hardware:boot:staging u-boot (where you already enabled bananapi-m2-zero) to home:seife:bananapi, additionally the openSUSE:Factory:ARM JeOS image and this image now boots from SD card \O/ :-) So the first step is done. I'm looking into the missing wifi and ethernet now. Best regards, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi,
;)
Great news! Could you push your changes to openSUSE:Factory:ARM/JeOS please? But, why you did not name your JeOS image bananapim2zero?
So the first step is done. I'm looking into the missing wifi and ethernet now.
There is no Ethernet, according to http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO Are you sure you are running a Bananapi M2 zero? Cheers, Guillaume

On 14.12.20 08:52, Guillaume Gardet wrote:
I just followed the example of the Banana Pi M2 plus which is called sinovoipbpim2plus (sinovoip is the manufacturer IIUC), and thus named it sinovoipbpim2zero :-) So I went for being consistent with other banana pi's It would probably make sense to rename both to "bananapim2{zero,plus}" because I doubt too many people will search for sinovoip. OTOH as long as links in the wiki are pointing to the right image, everything will be fine. I personally don't care too much.
Yes, there is. There's just no connector on the board. But 4 wires and a RJ45 socket will give you an ethernet port: http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO#how_to_use_zero_10.2F100_Eth... This is a case of "I need to patch the dtb to get this going". Unfortunately, just using the dtb from armbian made the ethernet appear (I have not yet soldered the connector, so I cannot tell if it would have worked), but killed WiFi :-) (armbian uses linux-sunxi kernel so probably has other changes to the device tree that conflicts with the upstream kernel). So I'm back to the original question: Can I easily specify which dtb file to load in grub? So that I can try alternate ones without having to resort to "rip the card out of the bananapi, stick it into a PC and fix it again" in case the modified dtb fails to boot? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi Guillaume, On 14.12.20 08:52, Guillaume Gardet wrote:
Hi,
I submitted sr#856052 to JeOS which is what works for me here (did not yet rename the image for now). I have also submitted a kernel-firmware package (sr#856051) which has the firmware links needed to get wifi going out of the box on banana pi m2 plus and m2 zero, so the extra step mentioned in the wiki doc https://en.opensuse.org/HCL:BananaPi_M2%2B#Enable_Wifi_and_Bluetooth_Support here is no longer necessary. I'll also try to create an initial wiki page for the BananaPi M2 zero so that everything is documented for others who want to try. Do we already have a mechanism to provide alternative dtbs for a board and select them? The bpi-m2-zero has an USB-OTG port that can be switched into usb-host mode (as it is default(?) on raspberry pi zero) with a changed dtb. This will be useful for people (like me ;-) who want to use this e.g. as a small headless internet radio box and thus want to use the usb port for an USB sound card. Or for people who want to connect a keyboard / mouse to be able to actually control the desktops of the XFCE/LXQT/X11/E20 images :-) I can always provide a script that does the changing / recompilation of the dtc automatically, but maybe we already have something in place. I'm pretty new to the dtb stuff, so bear with me if my questions are stupid ;-) Best regards and thanks for your help, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi,
I would expect it to work, since config has CONFIG_MMC_SUNXI_SLOT_EXTRA=2 to enable it. Could you share a bit more about this SD card failure, please?
The dtb should installed as part of dtb-sun8i package. But we have a kernel failure with -lpae flavor, so there may be a mismatch between dtb and kernel. You may want to try kernel-default instead. Cheers, Guillaume

(this time with the correct list address... m) Hi Guillaume, On 11.12.20 14:15, Guillaume Gardet wrote:
Thanks for the offer, but a pointer what I would need to change to do this on my own would already be enough ;-) I guess that branching openSUSE:Factory:ARM/u-boot, adding the config and _multibuild, then using this in a new image branched from openSUSE:Factory:ARM/JeOS is the way to go? Any other caveats to look out for? This would be a nice project for the upcoming locked down holidays ;-) Best regards, Stefan (I corrected the mailing list address, it looks like opensuse-arm@opensuse.org gets mapped to the mailing list, but it does not get sorted correctly on my side, then for whatever reason)
-- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi Guillaume, I could not wait until the holidays ;-) On 11.12.20 17:31, Stefan Seyfried wrote:
I linked hardware:boot:staging u-boot (where you already enabled bananapi-m2-zero) to home:seife:bananapi, additionally the openSUSE:Factory:ARM JeOS image and this image now boots from SD card \O/ :-) So the first step is done. I'm looking into the missing wifi and ethernet now. Best regards, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi,
;)
Great news! Could you push your changes to openSUSE:Factory:ARM/JeOS please? But, why you did not name your JeOS image bananapim2zero?
So the first step is done. I'm looking into the missing wifi and ethernet now.
There is no Ethernet, according to http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO Are you sure you are running a Bananapi M2 zero? Cheers, Guillaume

On 14.12.20 08:52, Guillaume Gardet wrote:
I just followed the example of the Banana Pi M2 plus which is called sinovoipbpim2plus (sinovoip is the manufacturer IIUC), and thus named it sinovoipbpim2zero :-) So I went for being consistent with other banana pi's It would probably make sense to rename both to "bananapim2{zero,plus}" because I doubt too many people will search for sinovoip. OTOH as long as links in the wiki are pointing to the right image, everything will be fine. I personally don't care too much.
Yes, there is. There's just no connector on the board. But 4 wires and a RJ45 socket will give you an ethernet port: http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO#how_to_use_zero_10.2F100_Eth... This is a case of "I need to patch the dtb to get this going". Unfortunately, just using the dtb from armbian made the ethernet appear (I have not yet soldered the connector, so I cannot tell if it would have worked), but killed WiFi :-) (armbian uses linux-sunxi kernel so probably has other changes to the device tree that conflicts with the upstream kernel). So I'm back to the original question: Can I easily specify which dtb file to load in grub? So that I can try alternate ones without having to resort to "rip the card out of the bananapi, stick it into a PC and fix it again" in case the modified dtb fails to boot? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
participants (2)
-
Guillaume Gardet
-
Stefan Seyfried