BPI_M3-Robs

Hi, I tried to boot R1S-H5 with: Buster minimal kernel 5.4 boots sucessfully Buster server kernel 5.3 did not boot (I had no time to monitor the UART output yet) So the output is from "Buster minimal kernel 5.4" uname -r: 5.4.2-sunxi64 here output of dmesg -t : lsusb: lsusb -v -d 0bda: If anyone needs more information, please let me know Robert

Hi Martin, I don't use the wifi module on my banana Pi M3, so I can live with Armbian Stretch 4.19 (armbian next). You are right with this kernel the internal wifi doesn't work "out of the box", I have not tried to get it working. According to the kernel changelog and http://linux-sunxi.org/Linux_mainlining_effort wifi and bluetooth was integrated into mainline in kernel 5.0 for A83T. So there is some hope to get wifi runnig if armbian boots with kernel >5.0. Could you send a link for Banana Pi M3 and arch linux?

By the way: Nothing new at 5.2 (dev-tree) Boot not successfully.

Hmm. I installed my old linux-dtb-dev-sunxi_5.76_armhf.deb into the new image, but the result is (more or less) unchanged: By the way. The dmesg of the running 4.20.12 is:

@ martinayotte: Thanks. This creates a lot of output, but for me the root-cause is still unclear. There is dump related to axp20x-ac-power-supply and many erros like: sun8i-a83t-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pf not found, using dummy regulator

Hi, after running successfully armbian dev (kernel 4.19.y and 4.20.y) for a while on my BPI M3, I tried to update to kernel series 5.0.y by compiling a complete new dev-image (debian stretch). Compiling and writing the image to an SD-card was no problem, but BPI M3 did not boot. On the serial console it came to an endless-loop (see below). The new uboot (2019.04) seem not to be the main issue, because I can use the new uboot with the 'old' kernel images (4.19 / 4.20) by installing the uboot package with dpkg and it still boots well. It looks (for me) that the kernel boots, but at the end the kernel itself makes an reboot (WHY?). Is there way to get more "output" from the booting kernel? Any other ideas or hints?

Hi, I use very successfully Banana Pi M3 with armbian (dev tree). To get wired network working stable the following patch must be active: https://github.com/armbian/build/pull/1071 Regards Robert

Hi, I found a solution for my problem. Here a short description: My self made i2c-device is connected to the pinheaders Pins 3(SDA)+5(SCL). Those pins are routed to internally to PH4+5 Acc to: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/sun8i-a83t.dtsi?h=v4.18&amp;id=f066f46ce5a518b66ff728b4903c0b916ea7ca41 the pin-definitions of i2c2 in sun8i-a83t.dtsi are missing intentionally. To activate i2c on those pins a patch is needed to assign the pins (copied to userpatches/kernel/sunxi-dev/): diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi b/arch/arm/boot/dts/sun8i-a83t.dtsi index 0233008..aa48aa7 100644 --- a/arch/arm/boot/dts/sun8i-a83t.dtsi +++ b/arch/arm/boot/dts/sun8i-a83t.dtsi @@ -882,6 +882,8 @@ interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_I2C2>; resets = <&ccu RST_BUS_I2C2>; + pinctrl-names = "default"; + pinctrl-0 = <&i2c2_ph_pins>; status = "disabled"; #address-cells = <1>; #size-cells = <0>; and activate on the target: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-a83t"; fragment@0 { target-path = "/aliases"; __overlay__ { i2c2 = "/soc/i2c@01c2b400"; }; }; fragment@1 { target = <&i2c2>; __overlay__ { status = "okay"; }; }; }; So its working now fine for me. Why don`t I send a PR? I do not like to cause interferences with other devices, because i2c-2 is missing intentionally. So if somebody needs i2c on PH4 and PH5 will find this here by google. And not so may people use i2c on Banana Pi M3 :-). Regards Robert banana-pi-m3-i2c-2.patch sun8i-a83t-i2c2.dts

Hi, I`m now testing the actual armbian on my Banana Pi M3(kernel 4.17.13). It's working quite well (networking included), but I'm suffering on a special issue: I need the I2C on the PinHeaders running. After several hours testing with https://docs.armbian.com/Hardware_Allwinner_overlays/#armbianenvtxt-entries-reference I have to surrender. Is there any way to create /boot/dtb/overlay/sun8i-a83t-i2c1.dtbo? Thanks for any hint about i2c on a83t Robert

The wired issue can perhaps solved by: https://patchwork.kernel.org/patch/10515589/ Regards Robert

Hi, well I don't want to support an overpriced product, but support the product I'm using (more or less successfully) since ~2 years. When I bought this product it was the only simple to get and available board in Europe with 2 GB RAM, Giga-Bit-Ethernet and Raspberry compatible IOs. And the offered Operating System was more or less useable and state of the art. But there was no further development, so it's no longer sate of the art. I believe that there are more users of this board in a similar situation. So I won't call it "support an overpriced product", but "enhance the time of usage for product". Regards Robert P.S. So X-MAS is over, but any help for this product is still welcome. And YES, I would pay money for better support of Banana Pi M3, and to give the results to the community.

Hi to everyone, I'm new at armbian forum, but following the project since some month. As far as I can tell all contributors make a great job to enable a stable debian based distribution to many as possible arm-based boards. Thanks a lot for this great job. I bought one of the first available Banana Pi M3-boards in Germany, because I wanted (and did it already very successfully) to set up a small server for email, music storage, mythtv-backend, read out my central heating.... Until now I use a stripped down image based on the provided Ubuntu 16.04 image from http://www.banana-pi.org/m3-download.html As you all know the "support" and further development of the OEM is more or less not there, and the provided image is based on kernel 3.4 (and not updated for ages). Until now it was more-or-less a "beauty mistake" for me, but not a real problem. But some weeks ago the mythtv-project released a new version, and installing this new version needs more-or-less a newer version of ubuntu (or debian in general). So now I have 2 possibility: 1. Buy a better supported board 2. Get the latest armbian running on this board Solution 1 seems to be the simplest way, but I don't want to go this way until 2nd is not completely impossible. But I have not the knowledge to make way 2 by myself. I know Banana Pi M3 is very very unloved in the community, but as far as I understand https://linux-sunxi.org/Linux_mainlining_effort and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=359b5a1e1c2d81af6d68de509e11d08ab4c150dc great success was made to implement this board into kernel 4.14. So I want to make a promise to give a donation of 100€ to the armbian project if this board will be supported by armbian until X-mas 2017. Main goals which have to work: - Boot into CLI debian Stretch - onboard USB host - onboard I2C - onboard Ethernet Networking - actual mainline Kernel (4.14?) - support for this board on regular level (.conf) instead of actual level (.csc) Not needed (but of course not "forbidden") - Graphical support - Sound - USB OTG Please be so kind and tell what you think about this idea. Thanks Robert