Jump to content

BPI-M2 doesn't boot on Armbian 5.1


Bongho Lee

Recommended Posts

I tried all 3 versions but they doesn't boot.

 

I tested using Armbian 4.5. It booted correctly.

 

I used Rufus for writing to SD.

 

Is there anything changed for writing?

 

Also does it support LeMaker official lcd at version 5.1?

 

Thanks.

Link to comment
Share on other sites

One of the beta builds booted normally ... OK, will check. Nothing unusually ... you need to decompress .7z file and write .raw with Rufus. If you wrote .7z without decompression, it wont work - i think Rufus doesn't know how to handle this scenario.

We only provide mainline kernel for M2 where LCD support does not exists - at least not out of the box.

Link to comment
Share on other sites

I tested again with Armbian_5.10_Bananapim2_Debian_jessie_4.5.2.7z which you gave a link, and it doesn't work.

At first, M2 board turn on the red led. And after about 35 seconds, it turned off.

 

When I tested with Armbian_4.5_Bananapim2_Debian_jessie_4.2.3.zip and Armbian_4.5_Bananapim2_Debian_wheezy_4.2.3.zip, it works properly.

At first, M2 board turn on the red led. And after about 8 seconds, it turned green led on.

 

I tested with Armbian_5.00_Bananapim2_Debian_wheezy_4.4.1.zip and Armbian_5.00_Bananapim2_Debian_jessie_4.4.1.zip, and it doesn't work.

 

I used Rufus 2.8.886 in windows 10 Enterprise for writing on MicroSDHC 16GB.

 

My board is BPI-M2, of course. Can you give me advice little bit?

Link to comment
Share on other sites

sun7i-a20-bananapro.dts file is changed. So your patch file doesn't work any more.

 

I changed it a little bit. Please refer below.

 

And I got some compile errors. I don't know how to figure out them.

And Does that patch file also have lcd enable code? It looks only having touch controller patch, not lcd.

I compiled for BPI-M1+(bananapro)

Error: arch/arm/boot/dts/sun7i-a20-bananapro.dts:329.1-15 Label or path reg_usb$
Error: arch/arm/boot/dts/sun7i-a20-bananapro.dts:335.1-15 Label or path reg_usb$
Error: arch/arm/boot/dts/sun7i-a20-bananapro.dts:372.1-18 Label or path usb_pow$
FATAL ERROR: Syntax error parsing input tree
scripts/Makefile.lib:300: recipe for target 'arch/arm/boot/dts/sun7i-a20-banana$
make[1]: *** [arch/arm/boot/dts/sun7i-a20-bananapro.dtb] Error 1
arch/arm/Makefile:338: recipe for target 'dtbs' failed
make: *** [dtbs] Error 2

Patch

diff --git a/arch/arm/boot/dts/sun7i-a20-bananapro.dts b/arch/arm/boot/dts/sun7i-a20-bananapro.dts
index 18fcc87..50f1a36 100644
--- a/arch/arm/boot/dts/sun7i-a20-bananapro.dts
+++ b/arch/arm/boot/dts/sun7i-a20-bananapro.dts
@@ -216,6 +216,25 @@
	status = "okay";
 };

+&i2c3 {
+        status = "okay";
+        pinctrl-names = "default";
+        pinctrl-0 = <&i2c3_pins_a>;
+        edt: edt-ft5x06@38 {
+                        compatible = "edt,edt-ft5x06";
+                        reg = <0x38>;
+                        interrupt-parent = <&pio>;
+                        interrupts = <7 9 IRQ_TYPE_EDGE_FALLING>;
+                        wake-gpios = <7 7 GPIO_ACTIVE_LOW>;
+                        pinctrl-names = "default";
+                        pinctrl-0 = <&edt_ft5x06_pins>;
+                        touchscreen-size-x = <1024>;
+                        touchscreen-size-y = <600>;
+                        touchscreen-inverted-x;
+                        touchscreen-swapped-x-y;
+        };
+};
+
 &ir0 {
	pinctrl-names = "default";
	pinctrl-0 = <&ir0_rx_pins_a>;
@@ -305,6 +305,13 @@
		allwinner,drive = <SUN4I_PINCTRL_10_MA>;
		allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
	};
+
+        edt_ft5x06_pins: edt_ft5x06_pins@0 {
+                allwinner,pins = "PH7", "PH9";
+                allwinner,function = "gpio_out";
+                allwinner,drive = <SUN4I_PINCTRL_40_MA>;
+                allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
+        };
 };

 #include "axp209.dtsi"

Link to comment
Share on other sites

sun7i-a20-bananapro.dts file is changed. So your patch file doesn't work any more.

 

You can't use sun7i-a20-bananapro.dts anyway since you have a totally different device. This was an example which device nodes to add for the TS controller.

 

Regarding LCD it's somewhat complicated. Please start here: http://linux-sunxi.org/LCD

 

You need to find a fex file that correctly described the LCD parameters (somewhat hard when the vendor is SinoVoip since they're 'famous' for providing wrong hardware descriptions like fex files) and then have to translate them to be used with mainline u-boot. There's a script available at the link above but as you can see from the table there A31s seems to be not fully supported. In case you're stuck I would suspect the best place to ask for help is linux-sunxi IRC.

 

To sum it up: You bought the wrong device since software support for A31 still isn't that great. Maybe you have been tricked into believing Banana Pi M2 would be compatible to the real Bananas (all A20 based with very good software support) due to its name?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines