Banana Pi Wiki - User contributions [en]

Getting Started with BPI-W2

2023-03-31T09:52:06Z

Czj: /* Android */

[[zh:快速上手_香蕉派 BPI-W2]]
=Introduction=

[[File:Android_6.0_1.jpg|thumb|Overview: BPI-W2 Android 6.0]]
[[File:W2_debian.jpg|thumb|[http://forum.banana-pi.org/t/banana-pi-bpi-w2-new-image-debian-9-linux-image-release-2018-09-18/6797 Debian 9 Linux Image Release 2018-09-18]]]
[[File:W2_ubuntu.jpg|thumb|[http://forum.banana-pi.org/t/bananapi-w2-ubuntu-18-04-new-image-release-2018-09-17/6790 BananaPI-W2 Ubuntu 18.04 New Image Release 2018-09-17]]]
[[File:W2_rasbian.jpg|thumb|[http://forum.banana-pi.org/t/banana-pi-bpi-w2-new-image-raspbian-9-4-new-image-release-2018-09-17/6824 BananaPI-W2 Raspbian 9.4 New Image Release 2018-09-17]]]
[[File:Rpitc.jpg|thumb|[http://forum.banana-pi.org/t/bpi-w2-new-iamge-rpitcv3-1-12-demo-bpi-w2-beta-2018-09-03/6686 RPiTCv3_1.12-demo-bpi-w2-beta-2018-09-03]]]

Read more: [[Banana Pi BPI-W2]]

=Development=
Let's get start to develop on BPI-W2, see amazing things happen.
Old page：[[Getting Started with BPI-W2]]

==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on W2

[[Image:Debug_console_wire.png]]

[[Image:W2_debug_console.jpg]]

===Load your first image on W2===
1.You could download latest image from our forum

2.Install bpi-tools on your system
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into W2, and press power button setup W2.

===Build your own image on W2===
====How to make a SD card with bootloader====

there are two ways to boot w2, controlled by SW4

[[File:Bootsw4.jpg]]

*0 boot from emmc.
*1 boot from SPI + SD card.

After power on, there are 3 steps must be done before loading kernel,(Normally they all are called bootloader):

*step 1: CPU init - the code is inside CPU;
*step 2: init the flash device on which we boot from; (normally it’s called preloader)
*step 3: u-boot;

RTD1296 supports booting from eMMC and SPI flash, so if we want to boot W2 from SD card, (that means we put u-boot on the SD card.) the second step code must be written to SPI flash, normally it’s done in factory before the board sending out, and the code is fixed and provided by RTK without source. We need not care about it, it does a simple job.

In fact, if the board will boot from eMMC, the second code must be written to eMMC first too, remember that we introduced how to do it with u-boot together on other pages. Normally it’s also been done in factory.

The u-boot for eMMC and SD card are different, normally eMMC u-boot 's name is '''dvrboot.exe.bin''', and u-boot for SD card name is '''u-boot.bin'''.

Write u-boot to SD card

The u-boot file for booting from SD card is here: https://drive.google.com/drive/folders/17ShSHLOvxeYA6tI9HQXOAb3O7RjqfD_6?usp=sharing

*step 1: build a SD card system according:
::2.1.3.2.1 How to make and run the 64-bit ubuntu 16.04 on SD card 2018-4-28

*step 2: boot up the board with eMMC and press ‘Esc’ key to let board stays on u-boot prompt;
*step 3: using tftp to get u-boot.bin file from network;
tftp 0x1500000 u-boot.bin
*step4: using sd command to write it to SD card:
sd write 0x1500000 0x50 0x3f0
*forum pthread
::http://forum.banana-pi.org/t/how-to-make-a-sd-card-with-bootloader/5767

====Ubuntu====
=====How to make and run the 64-bit ubuntu 16.04 on SD card 2018-4-28=====

1.Requirement：
*1.A PC with ubuntu as the host;
*2.A banana Pi W2 board;
*3.A SD card;
*4.Downloaded latest ubuntu base tar file (ubuntu-base-16.04.4-base-arm64.tar.gz) from url:
::http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ 17

*5.Hardware configuration file, u-boot binary file, kernel image file and audio file, which can be downloaded from:
::https://drive.google.com/file/d/1LX4FwXcSzkuI4BUPEVxbUyeG_UYwIkwY/view?usp=sharing 17
::::oRTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin – hardware config
::::odvrboot.exe.bin – u-boot binary
::::ouImage – kernel image
::::obluecore.audio – audio and video firmware for RTK1296

2.Write the bootloader to the Banana Pi W2 flash:

Banana Pi W2 board can boot from EMMC flash or SPI flash on the board, the difference is the location of the bootloader, so if you will not participate in the development of u-boot, this will not matter to you. So here is how to write bootloader to EMMC.

Normally the W2 board you got had been programed in the factory, but if the version of the bootloader isn’t the latest one, I recommend you to program it by yourself again. The latest version of bootloader is available on the Banana Pi website.

Requirement:

*1.A windows PC runs serial terminal tool like hypertrm. (I recommend using “hypertrm”, because other tools sometimes fail to transmit data);
*2.Latest version u-boot binary file from Banana Pi website (dvrboot.exe.bin);
*3.A hardware configuration binary file for W2 （RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin);

Steps:

*1.Connect the serial port between the host and the board correctly, run the terminal software and set up the relevant parameters (115200, 8N1, none);
*2.press “ctrl+q” then to power on the board, and when the screen appears’ d/g/r ', it can be released;
*3.Input “h” and send hardware configuration binary files (RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin) in Y-modem mode on the terminal side.
*4.Wait for the transfer to complete, then input below in console:
s98007058
01500000
*5.Input “d” and send u-boot binary files (dvrboot.exe.bin) in Y-modem mode on the terminal side.
*6.Wait for the transmission to complete. Enter “g” then the u-boot will be programed to the EMMC automatically.

3.Make a ubuntu root file system for W2 on a ubuntu PC.

Ubuntu has the version for arm64 architecture, it’s suitable for the Banana Pi W2, most of packages built by ubuntu for arm64 can run on the W2 board.

Requirement:
*1.A PC runs linux (recommend ubuntu)
*2.The latest version of ubuntu tar file for arm64 (ubuntu-base-16.04.4-base-arm64.tar.gz) is downloaded from ubuntu website: http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ 17

Steps: (on the host)：
*1.mkdir rootfs
*2.su root
*3.tar zxvf ubuntu-base-16.04.4-base-arm64.tar.gz -C rootfs
*4.write a shell script file, please copy below contents to the file ch-mount.sh (vi ch-mount.sh and copy):

!/bin/bash

function mnt() {
echo "MOUNTING"
sudo mount -t proc /proc ${2}proc
sudo mount -t sysfs /sys ${2}sys
sudo mount -o bind /dev ${2}dev
sudo mount -o bind /dev/pts ${2}dev/pts
sudo chroot ${2}
}

function umnt() {
echo "UNMOUNTING"
sudo umount ${2}proc
sudo umount ${2}sys
sudo umount ${2}dev/pts
sudo umount ${2}dev
}

if [ "$1" == "-m" ] && [ -n "$2" ] ;
then
mnt $1 $2
elif [ "$1" == "-u" ] && [ -n "$2" ];
then
umnt $1 $2
else
echo ""
echo "Either 1'st, 2'nd or both parameters were missing"
echo ""
echo "1'st parameter can be one of these: -m(mount) OR -u(umount)"
echo "2'nd parameter is the full path of rootfs directory(with trailing '/')"
echo ""
echo "For example: ch-mount -m /media/sdcard/"
echo ""
echo 1st parameter : ${1}
echo 2nd parameter : ${2}
fi

*5.apt-get install qemu-user-static
*6.cp /usr/bin/qemu-aarch64-static rootfs/usr/bin
*7.cp -b /etc/resolv.conf rootfs/etc/
*8../ch-mount.sh -m rootfs/
*9.apt-get install iputils-ping
*10.apt-get install udev
*11.apt-get install net-tools
*12.Modify the root password by running: “passwd root”
*13.exit
*14../ch-mount.sh -u rootfs/

Until now, the ubuntu file system have been built successfully on the host, next we will write it to the SD card.

4.Write the system to the SD card (on the host)：

Requirement:
*1.A SD card;
*2.Device tree binary file downloaded from Banana Pi website: bpi-w2.dtb;
*3.Kernel image file downloaded from Banana Pi website: uImage;
*4.Video and Audio firmware file downloaded from Banana Pi website: bluecore.audio;

Steps:

*1.Using fdisk tool to create two partitions in SD card: format the first partition as FAT32, and the second partition as ext4; It’s recommended that the first partition size should not be less than 100M;
*2.Copy the three files: bpi-w2.dtb, uImage, bluecore.audio to the first partition;
*3.Copy the all files in root filesystem which just built by us to the second partition using root privilege:
cp -a rootfs/* /media/xxx/sdxx/
sync
*4.Eject the SD card and insert it to the W2 board, after power on the board, you can see the ubuntu is running now.
*5.Set up network and get packages by using apt-get from ubuntu repository

Steps:

*1.Log in with root and the password was set by yourself;
*2.Ifconfig eth0 or eth1: ifconfig eth1 192.168.2.231
*3.Add default gateway to let the board can reach internet: route add default gw 192.168.2.1
*4.Add a DNS: echo ‘nameserver 8.8.8.8’ >> /etc/resolv.conf
*5.apt-get update
*6.then you can fetch and install any packages from ubuntu by using apt-get.

6.Furthermore：

Some functions are not available on the W2 now, because the kernel is not fully functional, we are working hard to make it more and more complete, please follow our official website update.

PDF format file download

http://forum.banana-pi.org/uploads/default/original/2X/c/c6dc409abc249c57a4cb2b7aedaddec6b80a9026.pdf

===== Ubuntu 16.04 Install and run Node.js and http-server=====

* insltall Node.js

After running Ubuntu 16.04, it's easy to install packages on the W2. Please follow below steps to install node.js:

1. apt-get install nodejs
2. apt-get install npm
3. npm install -g http-server
4. make a link to nodejs: cd /usr/bin/; ln -sf nodejs node

then Node.js is ready on your system.

====OpenWrt====

=====Burn OpenWRT with Linux kernel 4.4 =====

1.About this release

This release is for banana pi W2 board to run OpenWRT，you will know how to burn and run OpenWRT on W2.

2.Burn OpenWRT on W2 steps：

The Bootloader of OpenWRT is u-boot64, there are two ways to burn it on W2 EMMC.

A. Use RTK MP_Tool burn uboot on W2：

1）You need these files and tool：
* MP_Tool
* RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866.config（hardware configuration file）
* dvrboot.exe.bin（u-boot binary file）

2）Connect W2 debug console to windows PC，and run MP_Tool：

[[File:Burun_openwrt.jpg]]

* Set your console parameters
* Choose config file and uboot file
* Choose "LK option"
* Click Wirte button and then power on W2, and waiting for response "OK"

B. Use hypertrm burn uboot on W2：

1）You need these files and tool：
* hypertrm
* RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin（hardware configuration binary file）
* dvrboot.exe.bin（u-boot binary file）

2）Connect W2 debug console to windows PC：
* Run hypertrm ，config console parameters right
* Holding on press “ctrl + q” and power on board，after the screen show “d/g/r”，then loose “ctrl + q”
* Input “h”，use Y-modem way to send “RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin” to W2 board
* After finish transferred，input these parameters：

::s98007058
::01500000
* Input “d”，and send u-boot binary file
* after finish transferred，input “g” to burn u-boot file on W2 EMMC

After succeed to burn u-boot on W2, then install OpenWRT on W2.

1）You need these tools and files：
* U disk
* install.img

2）Burn OpenWRT on W2 steps：
* Format U disk as FAT32 filesystem
* Copy install.img to U disk root directory
* Decompress install.img to get four files：

emmc.uImage

rescue.root.emmc.cpio.gz_pad.img

bluecore.audio

rescue.emmc.dtb

* Plug U disk to W2 USB3.0 interface，holding press “Esc” button to power on W2 board
* Then W2 board will go into u-boot console
* Input these commands step by step：

setenv bootargs "earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 loglevel=7

init=/etc/init root=/dev/mmcblk0p1 rootfstype=squashfs rootwait"

save

go ru

* Waiting for OpenWRT burning，after finished，W2 will reboot and go into OpenWRT system.

[[File:Burun_openwrt_1.jpg]]

3.Image & Tools link：

Baidu Drive： https://pan.baidu.com/s/1Rs9F46wNJibORaeCfVh4wg PinCode：1w4w

Google Drive：https://drive.google.com/file/d/10kfP142Jw0sA92uwaIYZt7CeXcDKelO1/view?usp=sharing

4.BPI-W2 run OpenWRT video：

https://youtu.be/eTaRy8Jnfpk

==Advanced Development==
===GPIO===
====GPIO Control====

====PWM Control====

===Develop 4G module with W2===

===WiFi and Ap mode on W2===
====WiFi Client====

====AP mode====

===Make your own image===

==FAQ==

Getting Started with BPI-W2

2023-03-31T09:31:57Z

Czj: /* Load your first image on W2 */

[[zh:快速上手_香蕉派 BPI-W2]]
=Introduction=

[[File:Android_6.0_1.jpg|thumb|Overview: BPI-W2 Android 6.0]]
[[File:W2_debian.jpg|thumb|[http://forum.banana-pi.org/t/banana-pi-bpi-w2-new-image-debian-9-linux-image-release-2018-09-18/6797 Debian 9 Linux Image Release 2018-09-18]]]
[[File:W2_ubuntu.jpg|thumb|[http://forum.banana-pi.org/t/bananapi-w2-ubuntu-18-04-new-image-release-2018-09-17/6790 BananaPI-W2 Ubuntu 18.04 New Image Release 2018-09-17]]]
[[File:W2_rasbian.jpg|thumb|[http://forum.banana-pi.org/t/banana-pi-bpi-w2-new-image-raspbian-9-4-new-image-release-2018-09-17/6824 BananaPI-W2 Raspbian 9.4 New Image Release 2018-09-17]]]
[[File:Rpitc.jpg|thumb|[http://forum.banana-pi.org/t/bpi-w2-new-iamge-rpitcv3-1-12-demo-bpi-w2-beta-2018-09-03/6686 RPiTCv3_1.12-demo-bpi-w2-beta-2018-09-03]]]

Read more: [[Banana Pi BPI-W2]]

=Development=
Let's get start to develop on BPI-W2, see amazing things happen.
Old page：[[Getting Started with BPI-W2]]

==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on W2

[[Image:Debug_console_wire.png]]

[[Image:W2_debug_console.jpg]]

===Load your first image on W2===
1.You could download latest image from our forum

2.Install bpi-tools on your system
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into W2, and press power button setup W2.

===Android===
To flash Android to BPI-W2, please refer: https://forum.banana-pi.org.cn/t/topic/2970

===Build your own image on W2===
====How to make a SD card with bootloader====

there are two ways to boot w2, controlled by SW4

[[File:Bootsw4.jpg]]

*0 boot from emmc.
*1 boot from SPI + SD card.

After power on, there are 3 steps must be done before loading kernel,(Normally they all are called bootloader):

*step 1: CPU init - the code is inside CPU;
*step 2: init the flash device on which we boot from; (normally it’s called preloader)
*step 3: u-boot;

RTD1296 supports booting from eMMC and SPI flash, so if we want to boot W2 from SD card, (that means we put u-boot on the SD card.) the second step code must be written to SPI flash, normally it’s done in factory before the board sending out, and the code is fixed and provided by RTK without source. We need not care about it, it does a simple job.

In fact, if the board will boot from eMMC, the second code must be written to eMMC first too, remember that we introduced how to do it with u-boot together on other pages. Normally it’s also been done in factory.

The u-boot for eMMC and SD card are different, normally eMMC u-boot 's name is '''dvrboot.exe.bin''', and u-boot for SD card name is '''u-boot.bin'''.

Write u-boot to SD card

The u-boot file for booting from SD card is here: https://drive.google.com/drive/folders/17ShSHLOvxeYA6tI9HQXOAb3O7RjqfD_6?usp=sharing

*step 1: build a SD card system according:
::2.1.3.2.1 How to make and run the 64-bit ubuntu 16.04 on SD card 2018-4-28

*step 2: boot up the board with eMMC and press ‘Esc’ key to let board stays on u-boot prompt;
*step 3: using tftp to get u-boot.bin file from network;
tftp 0x1500000 u-boot.bin
*step4: using sd command to write it to SD card:
sd write 0x1500000 0x50 0x3f0
*forum pthread
::http://forum.banana-pi.org/t/how-to-make-a-sd-card-with-bootloader/5767

====Ubuntu====
=====How to make and run the 64-bit ubuntu 16.04 on SD card 2018-4-28=====

1.Requirement：
*1.A PC with ubuntu as the host;
*2.A banana Pi W2 board;
*3.A SD card;
*4.Downloaded latest ubuntu base tar file (ubuntu-base-16.04.4-base-arm64.tar.gz) from url:
::http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ 17

*5.Hardware configuration file, u-boot binary file, kernel image file and audio file, which can be downloaded from:
::https://drive.google.com/file/d/1LX4FwXcSzkuI4BUPEVxbUyeG_UYwIkwY/view?usp=sharing 17
::::oRTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin – hardware config
::::odvrboot.exe.bin – u-boot binary
::::ouImage – kernel image
::::obluecore.audio – audio and video firmware for RTK1296

2.Write the bootloader to the Banana Pi W2 flash:

Banana Pi W2 board can boot from EMMC flash or SPI flash on the board, the difference is the location of the bootloader, so if you will not participate in the development of u-boot, this will not matter to you. So here is how to write bootloader to EMMC.

Normally the W2 board you got had been programed in the factory, but if the version of the bootloader isn’t the latest one, I recommend you to program it by yourself again. The latest version of bootloader is available on the Banana Pi website.

Requirement:

*1.A windows PC runs serial terminal tool like hypertrm. (I recommend using “hypertrm”, because other tools sometimes fail to transmit data);
*2.Latest version u-boot binary file from Banana Pi website (dvrboot.exe.bin);
*3.A hardware configuration binary file for W2 （RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin);

Steps:

*1.Connect the serial port between the host and the board correctly, run the terminal software and set up the relevant parameters (115200, 8N1, none);
*2.press “ctrl+q” then to power on the board, and when the screen appears’ d/g/r ', it can be released;
*3.Input “h” and send hardware configuration binary files (RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin) in Y-modem mode on the terminal side.
*4.Wait for the transfer to complete, then input below in console:
s98007058
01500000
*5.Input “d” and send u-boot binary files (dvrboot.exe.bin) in Y-modem mode on the terminal side.
*6.Wait for the transmission to complete. Enter “g” then the u-boot will be programed to the EMMC automatically.

3.Make a ubuntu root file system for W2 on a ubuntu PC.

Ubuntu has the version for arm64 architecture, it’s suitable for the Banana Pi W2, most of packages built by ubuntu for arm64 can run on the W2 board.

Requirement:
*1.A PC runs linux (recommend ubuntu)
*2.The latest version of ubuntu tar file for arm64 (ubuntu-base-16.04.4-base-arm64.tar.gz) is downloaded from ubuntu website: http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ 17

Steps: (on the host)：
*1.mkdir rootfs
*2.su root
*3.tar zxvf ubuntu-base-16.04.4-base-arm64.tar.gz -C rootfs
*4.write a shell script file, please copy below contents to the file ch-mount.sh (vi ch-mount.sh and copy):

!/bin/bash

function mnt() {
echo "MOUNTING"
sudo mount -t proc /proc ${2}proc
sudo mount -t sysfs /sys ${2}sys
sudo mount -o bind /dev ${2}dev
sudo mount -o bind /dev/pts ${2}dev/pts
sudo chroot ${2}
}

function umnt() {
echo "UNMOUNTING"
sudo umount ${2}proc
sudo umount ${2}sys
sudo umount ${2}dev/pts
sudo umount ${2}dev
}

if [ "$1" == "-m" ] && [ -n "$2" ] ;
then
mnt $1 $2
elif [ "$1" == "-u" ] && [ -n "$2" ];
then
umnt $1 $2
else
echo ""
echo "Either 1'st, 2'nd or both parameters were missing"
echo ""
echo "1'st parameter can be one of these: -m(mount) OR -u(umount)"
echo "2'nd parameter is the full path of rootfs directory(with trailing '/')"
echo ""
echo "For example: ch-mount -m /media/sdcard/"
echo ""
echo 1st parameter : ${1}
echo 2nd parameter : ${2}
fi

*5.apt-get install qemu-user-static
*6.cp /usr/bin/qemu-aarch64-static rootfs/usr/bin
*7.cp -b /etc/resolv.conf rootfs/etc/
*8../ch-mount.sh -m rootfs/
*9.apt-get install iputils-ping
*10.apt-get install udev
*11.apt-get install net-tools
*12.Modify the root password by running: “passwd root”
*13.exit
*14../ch-mount.sh -u rootfs/

Until now, the ubuntu file system have been built successfully on the host, next we will write it to the SD card.

4.Write the system to the SD card (on the host)：

Requirement:
*1.A SD card;
*2.Device tree binary file downloaded from Banana Pi website: bpi-w2.dtb;
*3.Kernel image file downloaded from Banana Pi website: uImage;
*4.Video and Audio firmware file downloaded from Banana Pi website: bluecore.audio;

Steps:

*1.Using fdisk tool to create two partitions in SD card: format the first partition as FAT32, and the second partition as ext4; It’s recommended that the first partition size should not be less than 100M;
*2.Copy the three files: bpi-w2.dtb, uImage, bluecore.audio to the first partition;
*3.Copy the all files in root filesystem which just built by us to the second partition using root privilege:
cp -a rootfs/* /media/xxx/sdxx/
sync
*4.Eject the SD card and insert it to the W2 board, after power on the board, you can see the ubuntu is running now.
*5.Set up network and get packages by using apt-get from ubuntu repository

Steps:

*1.Log in with root and the password was set by yourself;
*2.Ifconfig eth0 or eth1: ifconfig eth1 192.168.2.231
*3.Add default gateway to let the board can reach internet: route add default gw 192.168.2.1
*4.Add a DNS: echo ‘nameserver 8.8.8.8’ >> /etc/resolv.conf
*5.apt-get update
*6.then you can fetch and install any packages from ubuntu by using apt-get.

6.Furthermore：

Some functions are not available on the W2 now, because the kernel is not fully functional, we are working hard to make it more and more complete, please follow our official website update.

PDF format file download

http://forum.banana-pi.org/uploads/default/original/2X/c/c6dc409abc249c57a4cb2b7aedaddec6b80a9026.pdf

===== Ubuntu 16.04 Install and run Node.js and http-server=====

* insltall Node.js

After running Ubuntu 16.04, it's easy to install packages on the W2. Please follow below steps to install node.js:

1. apt-get install nodejs
2. apt-get install npm
3. npm install -g http-server
4. make a link to nodejs: cd /usr/bin/; ln -sf nodejs node

then Node.js is ready on your system.

====OpenWrt====

=====Burn OpenWRT with Linux kernel 4.4 =====

1.About this release

This release is for banana pi W2 board to run OpenWRT，you will know how to burn and run OpenWRT on W2.

2.Burn OpenWRT on W2 steps：

The Bootloader of OpenWRT is u-boot64, there are two ways to burn it on W2 EMMC.

A. Use RTK MP_Tool burn uboot on W2：

1）You need these files and tool：
* MP_Tool
* RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866.config（hardware configuration file）
* dvrboot.exe.bin（u-boot binary file）

2）Connect W2 debug console to windows PC，and run MP_Tool：

[[File:Burun_openwrt.jpg]]

* Set your console parameters
* Choose config file and uboot file
* Choose "LK option"
* Click Wirte button and then power on W2, and waiting for response "OK"

B. Use hypertrm burn uboot on W2：

1）You need these files and tool：
* hypertrm
* RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin（hardware configuration binary file）
* dvrboot.exe.bin（u-boot binary file）

2）Connect W2 debug console to windows PC：
* Run hypertrm ，config console parameters right
* Holding on press “ctrl + q” and power on board，after the screen show “d/g/r”，then loose “ctrl + q”
* Input “h”，use Y-modem way to send “RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866_padding.bin” to W2 board
* After finish transferred，input these parameters：

::s98007058
::01500000
* Input “d”，and send u-boot binary file
* after finish transferred，input “g” to burn u-boot file on W2 EMMC

After succeed to burn u-boot on W2, then install OpenWRT on W2.

1）You need these tools and files：
* U disk
* install.img

2）Burn OpenWRT on W2 steps：
* Format U disk as FAT32 filesystem
* Copy install.img to U disk root directory
* Decompress install.img to get four files：

emmc.uImage

rescue.root.emmc.cpio.gz_pad.img

bluecore.audio

rescue.emmc.dtb

* Plug U disk to W2 USB3.0 interface，holding press “Esc” button to power on W2 board
* Then W2 board will go into u-boot console
* Input these commands step by step：

setenv bootargs "earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 loglevel=7

init=/etc/init root=/dev/mmcblk0p1 rootfstype=squashfs rootwait"

save

go ru

* Waiting for OpenWRT burning，after finished，W2 will reboot and go into OpenWRT system.

[[File:Burun_openwrt_1.jpg]]

3.Image & Tools link：

Baidu Drive： https://pan.baidu.com/s/1Rs9F46wNJibORaeCfVh4wg PinCode：1w4w

Google Drive：https://drive.google.com/file/d/10kfP142Jw0sA92uwaIYZt7CeXcDKelO1/view?usp=sharing

4.BPI-W2 run OpenWRT video：

https://youtu.be/eTaRy8Jnfpk

==Advanced Development==
===GPIO===
====GPIO Control====

====PWM Control====

===Develop 4G module with W2===

===WiFi and Ap mode on W2===
====WiFi Client====

====AP mode====

===Make your own image===

==FAQ==

Getting Started with M2 Ultra & Berry

2023-03-30T00:36:29Z

Czj: /* Linux */

[[zh:快速上手香蕉派 BPI-M2 Ultra / BPI-M2 Berry]]
=Introduction=
==BPI-M2U==
[[File:Banana_pi_BPI-M2_Ultra_4.JPG|thumb|Overview [[Banana Pi BPI-M2U ]]]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|Overview [[Banana Pi BPI-M2 Berry]]]]
[[File:M2p_respbian.png|thumb|Overview: BPI-M2U respbian linux]]

Banana Pi BPI-M2 Ultra is a quad-core mini single board computer built with Allwinner R40 SoC. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2U]]

===Key Features===
* Quad Core ARM Cortex A7 CPU R40
* 2GB DDR3 SDRAM
* 8 GB eMMC storage
* WiFi (AP6212) & Bluetooth onboard
* SATA Interface

==BPI-M2 Berry==
Banana Pi BPI-M2 Berry is a quad-core mini single board computer built with Allwinner V40 SoC. It features 1GB of RAM . It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 4 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2 Berry]]

===Key Features===
* Quad Core ARM Cortex A7 CPU V40.
* 1GB DDR3 SDRAM.
* WiFi (AP6212) & Bluetooth onboard.
* SATA Interface

=Development=
Let's get start to develop on BPI-M2U, see amazing things happen.
==Basic Development==
===Linux===
* Prepare 8G/above TF card, USB-Serial interface, PC with Windows System
* Using your USB-Serial Connect debug console on M2P

1.You could download the latest image from our wiki.
* BPI-M2U: https://wiki.banana-pi.org/Banana_Pi_BPI-M2U#Image_Release
* BPI-M2 Berry: https://wiki.banana-pi.org/Banana_Pi_BPI-M2_Berry#Image_Release

2.Put the TF card into a TF-USB adapter and plug it to your PC USB interface.

3.Download the flashing tools "BalenaEtcher" and start it.

4.Click "Flash from file" to select your image file.(.img or .zip)

5.Click "Select target" to choose your USB device.

6.Start to flash and wait for burning completely.

[[Image:Etcher.jpg | 600px]]

===Android===
1.You could download latest image from our forum.

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===Load your first image on M2U EMMC===
1.Bootup your M2U with Micro SD card
2.Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
3.Plug your USB disk in M2U
4.Mount the USB disk and flash the image file to eMMC

* bpi-tools
curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools|sudo -E bash
mount /dev/sda1 /mnt
cd /mnt
bpi-copy xxx-sd-emmc-xxx.img.zip /dev/mmcblk0

* dd command
mount /dev/sda1 /mnt
cd /mnt
unzip -p xxx-sd-emmc-xxx.img.zip |pv| dd of=/dev/mmcblk0 bs=10M status=noxfer

5.Then power off M2U, take TF card out, power on M2U

==Advanced Development==
===How to build uboot & kernel===
====Install tools====
* apt-get udpate
* apt-get install gcc-arm-linux-gnueabihf u-boot-tools
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
====Clone code====
* git clone: https://github.com/BPI-SINOVOIP/BPI-M2U-bsp.git
* ./build.sh
===SATA===
1. Mount SATA on M2U

[[Image:M2U_Sata.png]]

* After insert sata interface, execute "fdisk -l"
[[Image:M2U_Sata_fdisk_l.png]]

* Then "mount /dev/sdx /mnt/xxx"

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===OTG===
1. On M2U console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up
[[Image:M2P_ADBD.png]]

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2U and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2U OTG
* If yes, we could execute "adb shell" to connect M2U by adb now
[[Image:M2P_ADBD_Shell.png]]

===LCD 5" & LCD 7"===
* Execute "bpi-bootsel", you'll see a list of boot files
* Find "BPI_M2U_LCD7.img.gz"
* Then execute "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m2u/BPI_M2U_LCD7.img.gz"
[[Image:M2U_bootsel_lcd7.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M2U console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M2U_Gmac_test.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:

[[Image:M2U_bluetooth.png]]

===WiFi on M2U===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
====Shell====
* We also have built-in command in "/usr/local/bin" to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===IR function===
* Execute "getevent"
* Use your IR device to send information to M2U

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

===Install Qt5.7 & Qtcreator===
1.Prepare a 32Gb TF card

2.Use GParted to resize root point '/' as 32Gb

3.apt-get install libxcb*

4.download qt5.7

5.make & make install

6.apt-get install qtcreator

7.Config qtcreator

==FAQ==

=Reference Link=

http://www.banana-pi.org/m2plus.html

http://forum.banana-pi.org/

Getting Started with M2 Ultra & Berry

2023-03-30T00:36:06Z

Czj: /* Linux */

[[zh:快速上手香蕉派 BPI-M2 Ultra / BPI-M2 Berry]]
=Introduction=
==BPI-M2U==
[[File:Banana_pi_BPI-M2_Ultra_4.JPG|thumb|Overview [[Banana Pi BPI-M2U ]]]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|Overview [[Banana Pi BPI-M2 Berry]]]]
[[File:M2p_respbian.png|thumb|Overview: BPI-M2U respbian linux]]

Banana Pi BPI-M2 Ultra is a quad-core mini single board computer built with Allwinner R40 SoC. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2U]]

===Key Features===
* Quad Core ARM Cortex A7 CPU R40
* 2GB DDR3 SDRAM
* 8 GB eMMC storage
* WiFi (AP6212) & Bluetooth onboard
* SATA Interface

==BPI-M2 Berry==
Banana Pi BPI-M2 Berry is a quad-core mini single board computer built with Allwinner V40 SoC. It features 1GB of RAM . It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 4 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2 Berry]]

===Key Features===
* Quad Core ARM Cortex A7 CPU V40.
* 1GB DDR3 SDRAM.
* WiFi (AP6212) & Bluetooth onboard.
* SATA Interface

=Development=
Let's get start to develop on BPI-M2U, see amazing things happen.
==Basic Development==
===Linux===
* Prepare 8G/above TF card, USB-Serial interface, PC with Windows System
* Using your USB-Serial Connect debug console on M2P

1.You could download the latest image from our wiki.
* BPI-M2U: https://wiki.banana-pi.org/Banana_Pi_BPI-M2U#Image_Release
* BPI-M2 Berry: https://wiki.banana-pi.org/Banana_Pi_BPI-M2_Berry

2.Put the TF card into a TF-USB adapter and plug it to your PC USB interface.

3.Download the flashing tools "BalenaEtcher" and start it.

4.Click "Flash from file" to select your image file.(.img or .zip)

5.Click "Select target" to choose your USB device.

6.Start to flash and wait for burning completely.

[[Image:Etcher.jpg | 600px]]

===Android===
1.You could download latest image from our forum.

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===Load your first image on M2U EMMC===
1.Bootup your M2U with Micro SD card
2.Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
3.Plug your USB disk in M2U
4.Mount the USB disk and flash the image file to eMMC

* bpi-tools
curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools|sudo -E bash
mount /dev/sda1 /mnt
cd /mnt
bpi-copy xxx-sd-emmc-xxx.img.zip /dev/mmcblk0

* dd command
mount /dev/sda1 /mnt
cd /mnt
unzip -p xxx-sd-emmc-xxx.img.zip |pv| dd of=/dev/mmcblk0 bs=10M status=noxfer

5.Then power off M2U, take TF card out, power on M2U

==Advanced Development==
===How to build uboot & kernel===
====Install tools====
* apt-get udpate
* apt-get install gcc-arm-linux-gnueabihf u-boot-tools
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
====Clone code====
* git clone: https://github.com/BPI-SINOVOIP/BPI-M2U-bsp.git
* ./build.sh
===SATA===
1. Mount SATA on M2U

[[Image:M2U_Sata.png]]

* After insert sata interface, execute "fdisk -l"
[[Image:M2U_Sata_fdisk_l.png]]

* Then "mount /dev/sdx /mnt/xxx"

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===OTG===
1. On M2U console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up
[[Image:M2P_ADBD.png]]

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2U and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2U OTG
* If yes, we could execute "adb shell" to connect M2U by adb now
[[Image:M2P_ADBD_Shell.png]]

===LCD 5" & LCD 7"===
* Execute "bpi-bootsel", you'll see a list of boot files
* Find "BPI_M2U_LCD7.img.gz"
* Then execute "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m2u/BPI_M2U_LCD7.img.gz"
[[Image:M2U_bootsel_lcd7.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M2U console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M2U_Gmac_test.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:

[[Image:M2U_bluetooth.png]]

===WiFi on M2U===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
====Shell====
* We also have built-in command in "/usr/local/bin" to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===IR function===
* Execute "getevent"
* Use your IR device to send information to M2U

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

===Install Qt5.7 & Qtcreator===
1.Prepare a 32Gb TF card

2.Use GParted to resize root point '/' as 32Gb

3.apt-get install libxcb*

4.download qt5.7

5.make & make install

6.apt-get install qtcreator

7.Config qtcreator

==FAQ==

=Reference Link=

http://www.banana-pi.org/m2plus.html

http://forum.banana-pi.org/

Banana Pi BPI-M5

2023-03-27T09:03:18Z

Czj: /* Content */

[[zh:香蕉派_BPI-M5]]
=BPI-M5 Introduction=
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]] with S905x3 design]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D/S922 chip]]
[[File:Banana_Pi_BPI-M5_1.JPG|thumb|Amlogic S905X3 Processor]]
[[File:Banana_Pi_BPI-M5_2.jpg|thumb|Amlogic S905X3 Processor]]

[[File:BPI-M5_case_1.jpg|thumb|BPI-M5 case design]]
[[File:Wifibt_module_1.jpeg|thumb|WiFi&BT board, 802.11 a/b/g/n/ac 2T2R WiFi and Bluectooch 5.0]]

Banana Pi BPI-M5 is the next generation single board computer from Banana Pi in 2020. It is powered by Amlogic S905X3 quad-core Cortex-A55 (2.0 XXGHz) processor.Onboard 4GB LPDDR4 memory and 16GB EMMC storage, and supports 4 USB 3.0 interface, a gigabit network port.

[[File:Banana_Pi_BPI-M5.jpg]]

=Key Features=
* Amlogic S905X3 quad core Cortex-A55 (2.0xxGHz)
* Mali-G31 GPU
* 4GB LPDDR4
* 16GB eMMC flash
* 4 USB 3.0
* 1 GbE ethernet
* HDMI output

==Getting Start==
*[[Getting Started with M5/M2Pro]]

=Hardware=
==Hardware interface==
[[File:Banana_Pi_BPI-M5_interface1.jpg]]

==Hardware spec==
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-M5'''
|-
|CPU|| Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz)
|-
| GPU||Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz)
|-
| Memory|| 4 GB LPDDR4
|-
| Storage|| MicroSD slot with support for up to 256GB expansion and 16G eMMC flash with support for up to 64GB
|-
| Network|| 10/100/1000 Mbit/s Ethernet ,Optional WiFi USB dongle
|-
|Video Output(s)|| 1 x HDMI 2.1 (up to 4K@60Hz with HDR, CEC, EDID)
|-
| Audio Output(s)|| 3.5mm jack and 1 x HDMI digital output
|-
| USB ports|| USB 3.0 PORT (x4)
|-
|GPIO|| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). GPIO pins can be used for UART, I2C, SPI or PWM
|-
|Switches|| Reset, Power and U-boot
|-
| LED|| Power Status and Activity status
|-
| Power Source|| 5 volt @3A via Micro USB (TYPE C)
|-
|Size & Weight|| 92x60mm, 48g
|-
|OS|| Android and Linux
|}

==Wifi & BT support via expansion board==

===SDIO interface Wifi&BT===

* WiFi&BT board, 802.11 a/b/g/n/ac 2T2R WiFi and Bluetooth 5.0 , support BPI-M5 and BPI-F2P

[[File:Wifibt_module1_.jpeg]]

*how to use : https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Wifi.2FBT_support
*discuss on forum : http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846
*RT8822CS Bluetooth and WiFi adapter for Banana Pi BPI-M5：https://www.magazinmehatronika.com/en/rt8822cs-bluetooth-and-wifi-adapter-for-banana-pi-m5/?fbclid=IwAR0Oqm4TCa2SAXBTMJgRmWMJI-VQREqFxLh1-LnT_XzA5MAvYh_BL9-L7Xk
*easy to buy sample : https://www.aliexpress.com/item/1005002550783568.html?spm=5261.ProductManageOnline.0.0.34ed4edfgdV59j

===standard USB interface Wifi&BT===

*Banana Pi Wifi&BT 4.2 expansion Board, standard USB interface, so support all open source boards via USB port.IEEE 802.11b/g/n/ac(1T1R) USB WLANAnd BT Module

[[File:Usb_wifi_bt_board_3.jpg]]

*how to use : https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Wifi.2FBT_support
*discuss on forum : http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162

==BPI-M2 Pro VS BPI-M5 VS Odroid C4 VS RPI 4 ==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''BPI-M2 Pro VS BPI-M5 VS Odroid C4 VS RPI 4'''
|-
|||[[Banana Pi BPI-M2 Pro]]||[[Banana Pi BPI-M5]]|| Odroid C4|| Raspberry Pi 4||
|-
|Processor||Amlogic S905X3 Quad-Core Cortex-A55 ARMv8.2-A 64-bit 1.5GHz ||Amlogic S905X3 Quad-Core Cortex-A55 ARMv8.2-A 64-bit 1.5GHz || Amlogic S905X3 Quad-Core Cortex-A55 ARMv8.2-A 64-bit 1.5GHz || Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz
|-
|GPU ||Mali-G31 MP2 GPU ||Mali-G31 MP2 GPU || Mali-G31 MP2 GPU || Broadcom VideoCore VI
|-
|RAM ||2GB LPDDR4 ||4GB LPDDR4 ||DDR4 4GiB with 32-bit bus width ||2GB, 4GB or 8GB LPDDR4-3200 SDRAM
|-
|Storage || micro SD card slot & 16GB eMMC flash on board|| micro SD card slot & 16GB eMMC flash on board ||micro SD card slot , eMMC connector for option ||micro SD card slot, non EMMC
|-
|Network ||1 GbE ,WiFi&BT5.0 onbard|| GbE ,Optional WiFi USB dongle || GbE ||GbE, 2.4 GHz and 5.0 GHz IEEE 802.11ac wireless, Bluetooth 5.0, BLE
|-
|Video Output || 1 x HDMI 2.1 (up to 4K@60Hz with HDR, CEC, EDID)|| 1 x HDMI 2.1 (up to 4K@60Hz with HDR, CEC, EDID) || 1 x HDMI 2.1 (up to 4K@60Hz with HDR, CEC, EDID) || 2 × micro-HDMI 2.0
|-
|Audio Output || 1 x HDMI digital output ||3.5mm jack and 1 x HDMI digital output || Optional SPDIF optical output || 3.5 mm analogue audio-video jack
|-
|DSI ||N/A ||N/A ||N/A || 2-lane MIPI DSI display port
|-
|CSI ||N/A ||N/A ||N/A ||2-lane MIPI CSI camera port
|-
|USB ||USB 3.0 x 2 1 Micro USB 2.0||USB 3.0 x 4 TYPE C ||USB 3.0 x 4, 1 x Micro USB 2.0 port (OTG) || 2 USB 3.0 ports; 2 USB 2.0 ports;
|-
|Power ||5 volt @3A via DC power ||5 volt @3A via Micro USB (TYPE C) ||1 x DC power jack (Outer diameter : 5.5mm, inner diameter : 2.1mm) || 5V DC via USB-C connector (minimum 3A*)
|-
|IR ||Yes||Yes ||Yes ||N/A
|-
|GPIO ||40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND).||40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). || 40 x GPIO pins ||40-pin GPIO header, populated
|-
|Button ||Reset, user and U-boot ||Reset, user and U-boot || N/A || N/A ||
|-
|LED || Power Status and Activity status|| Power Status and Activity status || Power Status and Activity status || Power Status and Activity status
|-
|Dimensions & weight||65mm x 65mm,58g ||85mm x 56mm, 48g ||85mm x 56mm 59g ||88 mm × 58 mm, 46 g
|-
|System Support|| Linux & Android || Linux & Android ||Linux & Android ||Linux & Android
|}

==GPIO PIN define ==

===BPI-M5 40PIN GPIO (CON2)===
{| class="wikitable"
|-
|GPIO Pin Name ||Default Function ||Function2|| Function3
|-
|CON1-P01 ||VCC-3V3|| ||
|-
|CON1-P02|| VCC5V || ||
|-
|CON1-P03|| GPIOX_17 ||I2C_M2_SDA||
|-
|CON1-P04|| VCC5V ||||
|-
|CON1-P05|| GPIOX_18|| I2C_M2_SCL ||
|-
|CON1-P06|| GND ||||
|-
|CON1-P07|| GPIOX_5 SDIO_CMD||||
|-
|CON1-P08|| GPIOX_12|| UART_A_TX ||
|-
|CON1-P09|| GND ||||
|-
|CON1-P10|| GPIOX_13 ||UART_A_RX ||
|-
|CON1-P11|| GPIOX_3 SDIO_D3 ||||
|-
|CON1-P12|| GPIOAO_8|| TDMB_SCLK ||
|-
|CON1-P13|| GPIOX_4 SDIO_CLK||||
|-
|CON1-P14|| GND ||||
|-
|CON1-P15|| GPIOX_7 PWM_F ||||
|-
|CON1-P16|| GPIOX_0 SDIO_D0 ||||
|-
|CON1-P17|| VCC-3V3 ||||
|-
|CON1-P18|| GPIOX_1 SDIO_D1 ||||
|-
|CON1-P19|| GPIOX_8 PCM_DIN ||||
|-
|CON1-P20|| GND ||||
|-
|CON1-P21|| GPIOX_9 PCM_DOUT||||
|-
|CON1-P22|| GPIOX_2 SDIO_D2 ||||
|-
|CON1-P23|| GPIOX_11|| PCM_CLK ||
|-
|CON1-P24|| GPIOX_10 ||PCM_SYNC ||
|-
|CON1-P25|| GND ||||
|-
|CON1-P26|| GPIOX_16 ||PWM_E ||
|-
|CON1-P27|| GPIOA_14|| I2C_M3_SDA ||
|-
|CON1-P28|| GPIOA_15|| I2C_M3_SCL||
|-
|CON1-P29|| GPIOX_14|| UART_A_CTS ||
|-
|CON1-P30|| GND ||||
|-
|CON1-P31|| GPIOX_15 ||UART_A_RTS ||
|-
|CON1-P32|| GPIOX_19|| PWM_B ||
|-
|CON1-P33|| GPIOX_6 PWM_A ||||
|-
|CON1-P34|| GND ||||
|-
|CON1-P35|| GPIOAO_7|| TDMB_FS ||
|-
|CON1-P36|| GPIOH_5 SPDIF_IN||||
|-
|CON1-P37|| GPIOAO_9|| I2S_MCLK||
|-
|CON1-P38|| GPIOAO_10|| TDMB_DIN|| SPDIF_OUT
|-
|CON1-P39|| GND ||||
|-
|CON1-P40|| GPIOAO_4|| TDMB_DOUT||
|}

===BPI-M5 Debug UART(CON1) ===
{| class="wikitable"
|-
|CON2-P1|| GND
|-
|CON2-P2|| UART0-RX
|-
|CON2-P3|| UART0-TX
|-
|}

=Development=
==Source code==

=== BPI-M5 runs wiringpi gpio===
*https://github.com/BPI-SINOVOIP/amlogic-wiringPi
===Android===
android 9 source code: https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9

[http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Build_Android_Source_Code How to build the Android Source Code]

*BPI-M5/M2 PRO Android9 source code:
:Baidu Cloud: https://pan.baidu.com/s/1TmmR_075b49lPSt1Phq0ag?pwd=8888 (pincode: 8888)
:Google Drive:

===Linux BSP source code===
Linux BSP source code: https://github.com/BPI-SINOVOIP/BPI-M5-bsp

[http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Build_Linux_Source_Code How to build the Linux BSP Source Code]

== Resources==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
*[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FDocuments%2FBPI-M5%2FBPI-M5-SCH-V10-Release.pdf BPI-M5 schematic diagram]
*[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FDocuments%2FBPI-M5%2FBPI-M5-PCB-V10-DXF.rar BPI-M5 PCB DXF file]
*[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FDocuments%2FBPI-M5%2FS905X3_Public_Datasheet_Hardkernel.pdf Amlogic S905x3 datasheet]
*[http://wiki.banana-pi.org/Product_certification Banana Pi BPI-M5 CE,FCC,RoHS Certification]
*Install OpenGapps on Bananapi BPI-M5 Android 9.0:https://www.youtube.com/watch?v=fXOKmWfpqF8
*BANANA PI BPI-M5 REVIEW & BENCHMARKS：https://bret.dk/banana-pi-m5-review/
*BANANA PI M5 VS RASPBERRY PI 4 – BENCHMARKS ： https://bret.dk/banana-pi-m5-vs-raspberry-pi-4/

=System image=

==Android==
:[http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Android How to flash Android Image]

* '''2023-03-01-bpi-m5-m2pro-tablet-android9.img'''
:Baidu Cloud:https://pan.baidu.com/s/1cjzNgiE0-XJhvZgY0tQuHg?pwd=8888 （pincode: 8888)
:Google Drive:https://drive.google.com/drive/folders/144OU7NMTxLUqxNN2tXESgAoE3VXYgA_F?usp=share_link

*'''2023-03-01-bpi-m5-m2pro-mbox-android9.img'''
:Baidu Cloud:https://pan.baidu.com/s/1SAfGM0WxOHW0vYCkjQUfbQ?pwd=8888 (pincode: 8888)
:Google Drive:https://drive.google.com/drive/folders/1Ipg8vZvKN_0xX0Fu24BW5UcDAHGhP7oH?usp=share_link

* '''2022-09-07 release, BPI-M2 PRO/M5-Mbox-Android9'''
:Baidu Cloud: https://pan.baidu.com/s/1vqFGBDzY0gdqIIkX8ap5GA?pwd=uex1 (pincode: uex1)
:Google Drive:https://drive.google.com/file/d/1qmVfN-ocQJ2WqTdFw3vk1f5_kDnRGZeM/view?usp=sharing
:MD5: ac9ac49c3b37b9cd85de65bd64f9552f

* '''2022-09-07 release, BPI-M2 PRO/M5-Tablet-Android9'''
:Baidu Cloud: https://pan.baidu.com/s/1vrmPlyPttoKU-FkPZZE-Jg?pwd=ds7a (pincode: ds7a)
:Google Drive:https://drive.google.com/file/d/1m-b5wYWazMM_QgnQ5iQZiPRRD6AmF-Ao/view?usp=sharing
:MD5: 84d60f44761a4d4958a50e47eee7a62a

==Linux==
:[http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux How to flash Linux Image]

===Ubuntu===

* '''2023-03-01-ubuntu-20.04-mate-desktop-bpi-m5-m2pro-aarch64-sd-emmc.img'''
:Baidu Cloud: https://pan.baidu.com/s/1aFY5XEN-dsEESX39-Bxa5g?pwd=8888 (pincode: 8888)
:Google Drive:https://drive.google.com/drive/folders/1yJSBk6AOJaRoF01-pqoVhB3eqqxqKEIL?usp=share_link

*'''2023-03-01-ubuntu-20.04-server-bpi-m5-m2pro-aarch64-sd-emmc.img'''
:Baidu Cloud:https://pan.baidu.com/s/1eiPnqFUdbxa7_kfHrJP4gw?pwd=888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1gEbIXcaUzGQa0MPB1NwfnWlYJnFW-NbP?usp=share_link

* '''2022-09-06 release Ubuntu Mate Desktop 20.04 with Kernel 4.9'''
:Baidu Cloud: https://pan.baidu.com/s/1XE2K_KlVwP0hvjv_AChVgg?pwd=38vx (pincode: 38vx)
:Google drive: https://drive.google.com/file/d/1OGNaEylMR-VlfY6ynRkGQNuljLcvxoqe/view?usp=sharing
:MD5: 4b0528065ddcf634e9a43b6b7a6363b1

*'''2022-09-06 release, Ubuntu server 20.04 with Kernel 4.9'''
:Baidu Cloud: https://pan.baidu.com/s/15g52JerxZejcwywH7zZOlg?pwd=jtv5 (pincode: jtv5)
:Google drive:https://drive.google.com/file/d/15Y80CDT07HfEgo2YVjTkLSeIUGk8GQUo/view?usp=sharing
:MD5: f377dc5246f9ed7133db95c9d34b5201

===Debian===

*'''2023-03-01-debian-10-buster-bpi-m5-m2pro-aarch64-sd-emmc.img'''
:Baidu Cloud:https://pan.baidu.com/s/1pEdZUVE70IzZJamdam_W3g?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/159Xyb7gWFlTnDAnnBL-jGn_p8s6ECFw2?usp=share_link

*'''2023-03-01-debian-10-buster-xfce-bpi-m5-m2pro-aarch64-sd-emmc.img'''
:Baidu Cloud:https://pan.baidu.com/s/1Ys6c64JRnO1CLpgNhHE-tg?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1JNbMay5W257bPBX7PBjzab6ISAmBe5XD?usp=share_link

*'''2022-09-06 release, Debian-10-buster with Kernel 4.9'''
:Baidu Cloud: https://pan.baidu.com/s/1BEdv5AWEYgkMcUX_ju4DPQ?pwd=2cw4 (pincode: 2cw4)
:Google Drive:https://drive.google.com/file/d/1IZ7IEFeb21ZnaAuknz9lr00jo95UX6ml/view?usp=sharing
:MD5: f6cbe3518e8a02267224a0aa0256ce11

==Third part image==

===Raspbian===
*'''BPI-M5 BPI-M2 Pro new image:Raspbian image, 2022-4-09 update, Raspbian image for linux kernel 4.9 and 5.17. support 32bit and 64 bit,please choose the right image'''
:Google driver: https://drive.google.com/drive/folders/1oqamIMl5Kmb3LVYMPFw-1tilvwKQI6n-
:discuss on forum : https://forum.banana-pi.org/t/bpi-m5-bpi-m2-pro-new-image-rasbian-image-2022-4-09-update/13246

===Armbian===
:'''Image From Armbian Official website:'''
::https://www.armbian.com/bananapi-m5/

:'''Image From Bananapi Released on 2023-03''', build from Armbian main branch source code, fix some bugs and support i2c, uart, spi and rtl8822cs overlays, you can enable the overlay in /boot/armbianEnv.txt
::Baidu Cloud: https://pan.baidu.com/s/1Wgg_0Z7Db6DSKqoIjf16PQ?pwd=8888 (pincode: 8888)
::Google Drive: https://drive.google.com/drive/folders/1Yds8Rru_26S0wN2B-pIM6XkyxUXiceNl?usp=share_link

===EmuELEC===
*This is a porting of EmuELEC v4.5 for BPI-M5. I ported from odroid c4 official EmuELEC image. PS3 a XBOX ONE S gamepad controllers were tested and work fine.
*https://forum.banana-pi.org/t/emuelec-for-bpi-m5/12095
===CoreELEC===
:[https://coreelec.org/ CoreELEC] official support Bananapi M5 and M2Pro since 19.2-Matrix_rc1
::Download: https://coreelec.org/#download
::Install Guide: https://coreelec.org/#install
::Source Code: https://github.com/CoreELEC/CoreELEC
::how to install: https://wiki.coreelec.org/coreelec:bpim2pro

===Volumio===
:Download:
::Google drive: https://drive.google.com/drive/folders/1B7nsy4Jxt2lBgXoA6XEnaamEQvZyHI8f
::Baidu cloud : https://pan.baidu.com/s/1mj9OC8P2VSI5GAMnIKGBqA PinCode: mrrb
:User Guide: https://cdn.volumio.org/wp-content/uploads/2019/01/Quick-Start-Guide-Volumio.pdf
:Source code: https://github.com/Dangku/volumio-build
:Platform prebuild package: https://github.com/Dangku/volumio-platform-bananapi
:Development guilde: https://volumio.github.io/docs/User_Manual/Quick_Start_Guide.html

===Odroid Android image===
*Base on Odroid android source code and build for bananapi m5/m2pro
:Download:
::Google Drive: https://drive.google.com/drive/folders/1u_CddlHvpAMu2VZJfIfUKTsFFyigCWig
:Install Guide: https://forum.odroid.com/viewtopic.php?f=204&t=38579

*Odroid ubuntu IMG for BPI-M5：
::https://forum.banana-pi.org/t/odroid-ubuntu-img-for-bpi-m5/12169

===Ubuntu Core 20===
:Ubuntu Core 20 demo image for bananapi m5/m2pro.
:Download:
::Google drive: https://drive.google.com/drive/folders/1TdAQ-HdggKrOPmWi0chpHDJY0SMWlUaC
::Baidu cloud :
:Install Guide: https://ubuntu.com/core/docs/uc20/install

===Archlinux===
*Archlinux xfce and minimal demo image, kernel 4.9, image build refer to [https://archdroid.org/ Archdroid]
:login: alarm/alarm, or root/root
:Download:
::Google drive:https://drive.google.com/drive/folders/1rSSNgbseY2mwTMIauGR1yrXN8RPKzuk6
::Baidu link : https://pan.baidu.com/s/1Ck_H51jPUyAv98o73I8oAw Pincode: rbv2
::discuss on forum : https://forum.banana-pi.org/t/bpi-m5-bpi-m2-pro-new-image-archlinux-2021-9-14/12595

===HuaWei OpenEuler===
*OpenEuler demo image, bpi kernel 4.9
:Download:
::Baidu link ：https://pan.baidu.com/s/12b7q3y-m3YRyD7GwhKE0QA Pincode：lv50
:SIG gitee link : https://gitee.com/openeuler/raspberrypi
:Discuss on fourm : http://forum.banana-pi.org/

===Manjaro for BPI-M5===

Manjaro porting for BPI-M5 from Official Image for Odroid C4, the ported image use kernel 5.10. If anyone is interested on give it a try, the download link is below.
*Download Link: https://mega.nz/folder/BuZWkLhC#phC9KSsassB4bmkAegYykA
*discuss on forum : https://forum.banana-pi.org/t/manjaro-for-bpi-m5/12726

=Easy to buy=

*[https://pt.aliexpress.com/item/1005001871842695.html?spm=a2g0o.productlist.0.0.59976fff0GL35q&algo_pvid=24dfc96b-f6c1-4850-9ff4-fd177ee36648&algo_expid=24dfc96b-f6c1-4850-9ff4-fd177ee36648-0&btsid=0bb47a2216147586025791703e886c&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_ buy it form aliexpress ]

*easy to buy RTL8822 wifi module sample : https://www.aliexpress.com/item/1005002550783568.html?spm=5261.ProductManageOnline.0.0.34ed4edfgdV59j

* Mass order,please contact : judyhuang@banana-pi.com

Banana Pi BPI-M5

2023-03-27T09:02:50Z

Czj: /* Easy to buy */

Banana Pi BPI-M64

2023-03-22T08:42:06Z

Czj: /* Armbian */

[[zh:香蕉派_BPI-M64]]
=Introduction=

[[File:Banana_pi_BPI-M64_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M64_2.jpg|thumb|Overview:Allwinner A64]]
[[File:BPI-M3_M2_ultra_Case.jpg|thumb|Premium Aluminum Enclosure]]
[[File:Bpi-m2_ultar_case_1.jpg|thumb|BPI-M64 acrylic case]]
[[File:BPI_iot_design.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] : A64 for smart home design]]
[[File:A64_for_IoT_gateway.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] :A64 for IoT gateway design]]

Banana Pi BPI-M64 is a 64-bit quad-core mini single board computer. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M64 has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, and lastly a DC power port. The processor is pin-to-pin comptialbe with R18, so it comes with two versions:M64 and M64-R18.

[[File:BPI-M64_960x360.jpg]]

Also being a member of the Banana Pi family, the M64 is a big jump from the octa-core BPI-M3. This is because this Banana Pi BPI is named after its 64-bit SoC. BPI-M64 will be reserved for an upcoming board

BPI-M64 is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==
* Allwinner A64 1.2 Ghz Quad-Core ARM Cortex A53 64-Bit Processor.
* 2 GB DDR3 SDRAM
* 8G EMMC
* 10/100/1000Mbps Ethernet
* WiFi (AP6212) & Bluetooth
* MIPI LCD interface
* Camera interface

==Getting Start==
*How to burn image : [[Quick Start Banana pi SBC]]
*how to development: [[Getting Started with M64]]

=Hardware=
==Hardware interface==
[[File:BPI-M64_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-M64'''
|-
|CPU|| Allwinner 64 Bit Quad Core ARM Cortex A53 1.2 GHz CPU
|-
| GPU|| Dual core Mali 400 MP2 GPU
|-
| Memory|| 2GB LPDDR3 (shared with GPU)
|-
| Storage|| MicroSD slot with support for up to 256GB expansion and 8G eMMC flash with support for up to 64GB
|-
| Network|| 10/100/1000 Mbit/s Ethernet + Wi-Fi 802.11 b/g/n + Bluetooth 4.0
|-
|Video Input(s)|| A CSI input connector allows for the connection of a designed camera module
|-
|Video Output(s)|| 1080p capable HDMI port and multi-channel audio output (NO H./X.265 capabilities)
|-
| Audio Input(s)|| On board microphone
|-
| Audio Output(s)|| 3.5mm jack and HDMI
|-
| USB ports|| USB 2.0 PORT (x2), USB OTG (x1)
|-
| Remote|| IR Receiver
|-
|GPIO|| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). GPIO pins can be used for UART, I2C, SPI or PWM
|-
|Switches|| Reset, Power and U-boot
|-
| LED|| Power Status and 8P8C
|-
| Power Source|| 5 volt @2A via DC Power and/or Micro USB (OTG)
|-
|Size & Weight|| 92x60mm, 48g
|-
|OS|| Android and Linux
|}

==GPIO PIN define ==

Banana Pi BPI-M64 has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M64'''
|-
|GPIO Pin Name||Default Function||Function2：GPIO||Function3
|-
|CON2-P01|| VCC-3V3 ||　|| 　
|-
|CON2-P02|| VCC-5V|| ||　　
|-
|CON2-P03|| TWI1-SDA|| PH3|| 　
|-
|CON2-P04|| VCC-5V|| ||　 |　
|-
|CON2-P05|| TWI1-SCK|| PH2||
|-
|CON2-P06|| GND|| 　|| 　
|-
|CON2-P07|| PH6|| PH6|| 　
|-
|CON2-P08|| UART2-TX|| PB0|| 　
|-
|CON2-P09|| GND|| ||　　
|-
|CON2-P10|| UART2-RX|| PB1|| 　
|-
|CON2-P11|| PH7|| PH7|| 　
|-
|CON2-P12|| UART2-CTS|| PB3 ||　
|-
|CON2-P13|| DMIC-CLK|| PH10|| 　
|-
|CON2-P14|| GND|| || 　　
|-
|CON2-P15|| DMIC-DIN|| PH11|| 　
|-
|CON2-P16|| UART2-RTS|| PB2|| 　
|-
|CON2-P17|| VCC-3V3|| || 　　
|-
|CON2-P18|| PD4|| PD4 ||　
|-
|CON2-P19|| SPI1-MOSI|| PD2|| UART4-TX
|-
|CON2-P20|| GND|| || 　　
|-
|CON2-P21|| SPI1-MISO|| PD3|| UART4-RX
|-
|CON2-P22|| PC0|| PC0|| 　
|-
|CON2-P23|| SPI1-CLK|| PD1|| UART3-RX
|-
|CON2-P24|| SPI1-CS ||PD0|| UART3-TX
|-
|CON2-P25|| GND|| ||　　
|-
|CON2-P26|| PC2|| PC2 　||
|-
|CON2-P27|| PC4|| PC4 　||
|-
|CON2-P28|| PC3|| PC3 　||
|-
|CON2-P29|| PC7|| PC7 　||
|-
|CON2-P30|| GND ||　|| 　
|-
|CON2-P31|| PCM0-BCLK|| PB5 ||
|-
|CON2-P32|| PCM0-DIN|| PB7 ||　
|-
|CON2-P33|| PCM0-SYNC|| PB4 ||
|-
|CON2-P34|| GND ||　|| 　
|-
|CON2-P35|| PCM0-DOUT|| PB6 　||
|-
|CON2-P36|| PL9|| PL9 ||　
|-
|CON2-P37|| PL12|| PL12|| 　
|-
|CON2-P38|| PL7|| PL7 ||　
|-
|CON2-P39|| GND|| || 　　
|-
|CON2-P40|| PL8|| PL8||　
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “Camera”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI camer PIN define of Banana pi BPI-M64'''
|-
|CSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN5-P01|| NC|| 　
|-
|CN5-P02|| GND|| 　
|-
|CN5-P03|| CSI0-SDA|| PE13
|-
|CN5-P04|| CSI0-AVDD|| 　
|-
|CN5-P05|| CSI0-SCK|| PE12
|-
|CN5-P06|| CSI0-Reset|| PE16
|-
|CN5-P07|| CSI0-VSYNC|| PE3|
|-
|CN5-P08|| CSI0-PWDN|| PE17
|-
|CN5-P09|| CSI0-HSYNC|| PE2
|-
|CN5-P10|| CSI0-DVDD|| 　
|-
|CN5-P11|| CSI0-DOVDD|| 　
|-
|CN5-P12|| CSI0-D7|| PE11
|-
|CN5-P13|| CSI0-MCLK|| PE1
|-
|CN5-P14|| CSI0-D6|| PE10
|-
|CN5-P15|| GND|| 　
|-
|CN5-P16|| CSI0-D5|| PE9
|-
|CN5-P17|| CSI0-PCLK|| PE0
|-
|CN5-P18|| CSI0-D4|| PE8
|-
|CN5-P19|| CSI0-D0|| PE4
|-
|CN5-P20|| CSI0-D3|| PE7
|-
|CN5-P21|| CSI0-D1|| PE5
|-
|CN5-P22|| CSI0-D2|| PE6
|-
|CN5-P23|| GND ||　
|-
|CN5-P24|| CSI0-AFVCC||
|-
|}

'''MIPI DSI (Display Serial Interface)'''

The display Connector is a 40-pin FPC connector which can connect external LCD panel (MIPI DSI) and touch screen (I2C) module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''MIPI DSI display PIN define of Banana pi BPI-M64'''
|-
|DSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN6-P01|| VCC ||　
|-
|CN6-P02|| IPSOUT|| 　
|-
|CN6-P03|| VCC ||　
|-
|CN6-P04|| IPSOUT||　
|-
|CN6-P05|| GND|| 　
|-
|CN6-P06|| IPSOUT ||　
|-
|CN6-P07|| GND 　||
|-
|CN6-P08|| IPSOUT ||　
|-
|CN6-P09|| NC ||　
|-
|CN6-P10|| GND 　||
|-
|CN6-P11|| NC ||
|-
|CN6-P12|| DSI-D0N 　||
|-
|CN6-P13|| NC ||　
|-
|CN6-P14|| DSI-D0P 　||
|-
|CN6-P15|| NC ||　
|-
|CN6-P16|| GND 　||
|-
|CN6-P17|| TWI0-SDA|| PH1
|-
|CN6-P18|| DSI-D1N ||
|-
|CN6-P19|| TWI0-SCK|| PH0
|-
|CN6-P20|| DSI-D1P 　||
|-
|CN6-P21|| CTP-INT|| PH4
|-
|CN6-P22|| GND|| 　
|-
|CN6-P23|| CTP-RST|| PH8
|-
|CN6-P24|| DSI-CKN ||
|-
|CN6-P25|| GND 　||
|-
|CN6-P26|| DSI-CKP ||　
|-
|CN6-P27|| LCD-BL-EN|| PD5
|-
|CN6-P28|| GND 　||
|-
|CN6-P29|| LCD-RST ||PD6
|-
|CN6-P30|| DSI-D2N ||　
|-
|CN6-P31|| LCD-PWR-EN ||PD7
|-
|CN6-P32|| DSI-D2P ||　
|-
|CN6-P33|| GND 　||
|-
|CN6-P34|| GND ||　
|-
|CN6-P35|| LCD-PWM|| PL10
|-
|CN6-P36|| DSI-D3N 　||
|-
|CN6-P37|| GND 　||
|-
|CN6-P38|| DSI-D3P ||　
|-
|CN6-P39|| NC 　||
|-
|CN6-P40|| GND 　||
|-
|}

'''UART specification:'''

The header CON2 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart PIN define of Banana pi BPI-M64'''
|-
|CON2 Pin Name|| Default Function|| GPIO
|-
|CON2 P03||UART0-TXD|| PB8
|-
|CON2 P02|| UART0-RXD|| PB9
|-
|CON2 P01|| GND ||　
|-
|}

=Software=

=Development=

==Basic Development==

===Win 10 IoT ===
banana pi BPI-M64 IOT certifying pass by Microsoft:windows 10 iot core

BPI-M64 for Win10 IoT : https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

[[File:Win10_1.png]]

link: https://azure.microsoft.com/en-us/documentation/articles/iot-hub-tested-configurations/

get start:

https://github.com/Azure/azure-iot-sdks/blob/master/doc/get_started/windows10-iot-core-banana-pi-bpi-m64-csharp.md

test on BPI-M64

[[File:Win10_2.jpg]]

discuss on forum: http://forum.banana-pi.org/t/banana-pi-bpi-m64-iot-certifying-pass-by-microsoft-windows-10-iot-core/2090

'''Windows 10 IoT Core for BPI-M64 Release Note'''

The Unified Extensible Firmware Interface (UEFI]) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers
AllWinner UEFI Firmware Release Notes

This document describes how to build AllWinner UEFI Firmware and bring a AllWinner dev board up with it. The AllWinner UEFI Firmware, as the major boot system for AllWinner-Windows platform, is based on the EDK2 framework which is open-source and with some AllWinner platform software packages injected.

Some updates:
::1. Update the OS version to build v.10.0.15063.0 $Creators Update$
::2. New page style of Device Portal, visit [https://deviceipaddr:8080](https://deviceipaddr:8080) to check it
::3. Built-in Cortana assistant, need to be enabled in settings page in default app and Device Portal
::4. Support on-screen keyboard, need to be enabled in Device Portal
::5. Enable 100M Ethernet and fix some bugs
::6. Support built-in UART bus in A64 SoC$not built in the ffu, later provide driver binary and deployment helper$
::7. Support built-in IR module in A64 SoC$not built in the ffu, later provide source code and dev doc for developers in community$

Known Issues:
::Kernel debug is enabled by default. This will slow the bring-up process. If a kernel debug is not necessary for you, visit Device Portal and navigate to Processes->Run Command page, run this command to disable : Bcdedit /store C:\EFIESP\EFI\Microsoft\boot\BCD /set {default} debug off
::An PnP bug in audio device may cause a blue screen when acting software shutdown
::Ethernet device may not start with problem code 12 at the first time to bring up

And another bomb! I uploaded core driver binaries and packaging toolchains on GitHub!

Here is the repo address: https://github.com/Leeway213/BSP-aw1689

And also some driver source code here with A64 datasheet in readme: https://github.com/Leeway213/driver-samples

Welcome makers developers and anyone-elsers to post your feedback.

===Microsoft Azure IoT===
* we have test BPI-M64 with Microsoft Azure IoT with aarch64 Ubuntu 18.04 Linux
::Microsoft Azure IoT Edge using DPS with TPM 2.0 SLB9670 : https://www.youtube.com/watch?v=k9_GSQgKlqk&feature=youtu.be
::Microsoft Azure IoT Edge using DPS with TPM 2.0 ST33 i2c : https://www.youtube.com/watch?v=2MrO1-esjwI&feature=youtu.be

=Resources=
==Source code==
*BPI-M64 Android 7 source code
:: download link : https://github.com/BPI-SINOVOIP/BPI-A64-Android7

*BPI-M64 Android 6.0.1 source code
:: download link : https://drive.google.com/open?id=0B_YnvHgh2rwjdTRVRVFaSHd2cnc

*BPI-M64 (allwnner A64) Linux 4.4 source code
::https://github.com/BPI-SINOVOIP/BPI-M64-bsp-4.4
::Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-allwnner-a64-linux-4-4-source-code-public-on-github/6706

*BPI-M64 Linux kernel 3.4 BSP code:
:: github link : https://github.com/BPI-SINOVOIP/BPI-M64-bsp

*BPI-M64 Win10 IoT source code
::https://bananapi.gitbooks.io/bpi-m64/content/en/sourcecodeongithub.html

*BPI-M64 Robot Operating System (ROS):
::github: https://github.com/techping/BPI-robot-1
::discuss on forum: http://forum.banana-pi.org/t/discuss-robot-operating-system-ros-on-banana-pi/10967

== documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram:
::google driver :[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
::baidu cloud : http://pan.baidu.com/s/1kVRpcYb
* DXF file google download link :https://drive.google.com/file/d/0B4PAo2nW2KfnajlEY0xsdjNxY3c/view?usp=sharing
*Allwinner A64 chip datasheet:https://drive.google.com/file/d/0B4PAo2nW2KfnSW9lQnZ0d1RoVW8/view?usp=sharing
*Allwinner A64 user’s manual (720 pages):https://drive.google.com/file/d/0B4PAo2nW2KfnNHk4dkFJZEdqYXc/view?usp=sharing
*AXP803 Datasheet V1.0.pdf :https://drive.google.com/file/d/1nRbP1T02KlNZBbTJx4BHW5wVWvQPmDxC/view?usp=sharing
*A64 chip linux-sunxi wiki:http://linux-sunxi.org/A64
*BPI-M64 linux-sunxi wiki: https://linux-sunxi.org/Banana_Pi_M64
*other document about allwinner A64 chip:http://bundie.neterra.net:8080/a64/
*battery interface spec ： https://drive.google.com/file/d/0B4PAo2nW2KfnSmVuVDhQc0NLdG8/view?usp=sharing
*BPI-M64 quality guarantee
::BPI-M64 BT Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64bt40labtest.html
::BPI-M64 WIFI Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m264wifilabtest.html
::BPI-M64 Validation test : https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64validationtestreport.html
::CE FCC RoHS : http://forum.banana-pi.org/t/bpi-m64-ce-fcc-rohs-certification/2747

== Amazon AWS Greengrass==

Banana Pi BPI-M64 passed Amazon AWS Greengrass:https://devices.amazonaws.com/detail/a3G0h000000OvPoEAK/Banana-Pi-BPI-M64

=Image Release=

==Android ==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Android_Image How to install the Android image]

*2020-07-10 update, Android 7.1, base on kernel 3.10
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2FAndroid7.1&mode=list Download Android 7.1 image]

*2018-10-24 update Android 6.0 & 7.0 & 8.1, based on kernel 3.10.

:M64 Android 6.0 HDMI & LCD7
::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1Em7ZXVvbJI7wMXy_TM4VNwHo6Oa-vVBc
::::Baidu Drive : https://pan.baidu.com/s/1ZginIvO3LVakqokIZAX1Xw

::LCD7 Version Image Links:
:::: Google Drive : https://drive.google.com/open?id=1Tts1krZyzwz9mL90j1ilTzVrJm6hh_J4
::::Baidu Drive : https://pan.baidu.com/s/1oKMx_Ml5K1Jv7-qeS-NMsQ

:M64 Android 7.0 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_7.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1mvKyK6KuPixs-jLD0FocIaV465bJ1Eig
::::Baidu Drive : https://pan.baidu.com/s/15b32TXdh6752c-GBnR-Zeg

::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=16Ffc5xiZgD7JYgrMtCGaOYLCuZdQGcnY
::::Baidu Drive : https://pan.baidu.com/s/1a9RYKSTRhCO-UzFfIoGCtQ

*BPI-M64 Android 8.1 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1UBaH9CNbmC9-n3jGImrFIAPZ8aZhqMJz
::::Baidu Drive : https://pan.baidu.com/s/1lz57HrqNHx6f_Q6nk0oZvA
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1wktuCcvolfozMFkLmugfZtGziHDj-1EM
::::Baidu Drive : https://pan.baidu.com/s/1MteYqyBp8LeECjcDteCTZQ
*Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-android-6-0-7-0-8-1-release-2018-10-24/7107

*2018-9-17 update android 6.0
::Features Map :http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=19ExJ9Ztfy3UgK9NZ4SiaVZAMozgyCJl7
::::Baidu Drive : https://pan.baidu.com/s/1s_orgiEI7JU_hUgjnpd25w
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1gWD_IT0P4NvdeqtK5I4MnJjwzsP7SXJc
::::Baidu Drive : https://pan.baidu.com/s/1K0HYPiQe6nGvAS5bAAFHow
::Forum pthread :　http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796
*2018-08-17 update,android 8.1
::This release is for banana pi M64 board which is based on Allwinner A64, We have two images release，Android 8.1 is based on kernel 4.9
::BPI-M64 Android 8.1 Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI-LCD-Version:
::Google Drive : https://drive.google.com/open?id=11XjvTAbPw57R6H5kL27GVXry4xu18dVs
::Baidu Drive : https://pan.baidu.com/s/1PQgJCUo6cY3wWxJ7rZrk-A
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

* 2018-05-20 update ,android 7.0
::hdmi-Version and Lcd 5.0 version
::baidu cloud : https://pan.baidu.com/s/1O3PsI73WmFFvhxMmzEscIQ

* 2017-05-11 update ,android 6.0
::HDMI-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjcF9USm1MWWtxSXc
::Baidu Cloud:https://pan.baidu.com/s/1bHWhlW
::MD5: f85281213b9c5b88008a487dd1b6963c
::LCD-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjdHpFbHJMQWtsbFk
::Baidu Cloud:https://pan.baidu.com/s/1kVJVPGV
::MD5:be27e4eced96d3de81d46e512fd978eb
::forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-android-6-0-version-v3/3240/4

==Linux==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Linux_Image How to install BPI Linux Image]

* 2020-08-26 update, Ubuntu Mate 18.04, Ubuntu Server 16.04, Raspbian Stretch, base on kernel 4.4
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2Flinux&mode=list Download Image]

* 2020-04-21 update, Rasbian Stretch, Ubuntu 16.06 Mate Desktop, Ubuntu 16.06 Server and Ubuntu 18.04 Mate Desktop, base on kernel 4.4
::google drive:https://drive.google.com/drive/folders/0B_YnvHgh2rwja3I4SllZN2VkYm8
::baidu cloud:https://pan.baidu.com/s/18XH8_uusUGBusbp4xw4txQ Pincode：36R0

=== Ubuntu===

* 2018-11-02 update, based on kernel 3.10 & kernel 4.4.
::BPI-M64 Ubuntu 16.04 Desktp
::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::::Google Drive : https://drive.google.com/file/d/1YzdkY8i-IsXzXLkbPCPNbAuhYbHmUwgv/view
::::Baidu Drive : https://pan.baidu.com/s/1XhOJBQtPkhvidjgipFNdzg
::::md5sum : 3564f0d3de9936aa26b93eaf027703a0

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_aarch64_16.04
::::Google Drive : Chttps://drive.google.com/file/d/1MglySZLvquRPu1Wj8oLwdKBkFnRzLUL-/view
::::Baidu Drive : https://pan.baidu.com/s/1_ZTDCuL9QZf6qrqaE4gbgQ
::::md5sum : 7422e02daa01bff6de808490e89b436e

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 4.4
::::features Map:http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89
::::Google Drive : https://drive.google.com/file/d/1g_m1NLn1-wUQ8jjPKEAwQcSj4d4P9vRP/view
::::Baidu Drive : https://pan.baidu.com/s/1JmKQGRKvJ9DwL_ij0K79FA
::::md5sum : ea9bba6ab7fc78f7b8478bfd013a9b50

:: forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-ubuntu16-04-desktop-aarch64-release-2018-11-1/7159/1

::Debian 9.5 AARCH64 Kernel 3.10

::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Image Links: Google Drive : Coming soon
::::Baidu Drive: https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum: 71fe25c1922c7f9ef81bb88e0f544de6

*2018-4-17 update Ubuntu 16.04.4 with linux kernel 4.4.89
::image name:2018-04-17-ubuntu-16.04-mate-desktop-demo3-k4.4.89-vdpau-3-mic-docker-bpi-r18-avs-aarch64-sd-emmc.img.zip
::Google Drive: https://drive.google.com/open?id=1dlfo9LGNcrc-_cpKd1uJnrNx0PdonBnK
::MD5: 4b7e163d260e58a39ba8905e7ed39943
::Forum pthread:http://forum.banana-pi.org/t/bpi-r18-avs-new-image-ubuntu-16-04-4-with-linux-kernel-4-4-89-2018-4-17/5435

*2018-09-18 This release is for banana pi M64 board which is based on Allwinner A64, We release three Images, Ubuntu 16.04 Desktop & Android is based on kernel 3.10.
::Features Map ：http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::Google Drive :
::Baidu Drive : https://pan.baidu.com/s/1wANJ4SwfNwKtBcd02WcbWA
::forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796

*2018-08-17 update Ubuntu 16.04 Server kernel 3.10.105
::Google Drive : https://drive.google.com/open?id=1K-B4u8jGcv17s3I9v-Pr0xv5u5txvfok
::Baidu Drive : https://pan.baidu.com/s/1HcrR8NsL9_1RwbZNa7uwmg
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

*2017-08-14 update based on ubuntu 16.04.3 LTS Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive: https://drive.google.com/file/d/0B_YnvHgh2rwjN1h1U0xDYUxET00/view?usp=sharing
::baidu cloud: http://pan.baidu.com/s/1pLkbdTT
::MD5: ae34baa840874276858d936a7ca85c4f
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-14-ubuntu-16-04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc/3695

===Debian===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim64_bullseye_edge_5.19.7_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1UUbn24l3q_OsVP4XWT6eVQN531tHPzX0/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1vFR9sUR0FhWgS1pemk9lTg?pwd=ina6 (pincode: ina6)

*2018-11-2 update , This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Debian 9.5 AARCH64 is based on kernel 3.10 & kernel 4.4.

::M64 Debian 9.5 AARCH64 Kernel 3.10
::::Features Map : * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google driver : https://drive.google.com/file/d/10qGv2gVrSgwXMBLDsCF0nQFc9EJnnkeS/view
::::Baidu Drive : https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum : 71fe25c1922c7f9ef81bb88e0f544de6

::M64 Debian 9.5 AARCH64 Kernel 4.4
::::Features Map: * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google Drive : https://drive.google.com/file/d/17fh3YY6cwOzHMsqwnRQRTu9cXjKU4_tV/view
::::Baidu Drive : https://pan.baidu.com/s/1sOR6WFz2U9MT0ltq6zYnJA
::::md5sum : f3c2391b0232178018fda7ebfd64b14c
::forum pthread:http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-debian-9-5-aarch64-release-2018-11-02/7166

*2017-08-13 debian 8.9 jessie Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjazlNRTRHei1NbmM/view?usp=sharing
::baidu cloud:http://pan.baidu.com/s/1eSeTQeA
::MD5: 9ddf067457ebaf193de63c5c7141446a
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-13-debian-8-jessie-mate-desktop-preview-aarch64-bpi-m64-sd-emmc/3694

===Armbian===
*Armbian_23.02.0-trunk_Bananapim64_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapim64_jammy_edge_6.1.11_xfce_desktop.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m64-new-armbian-image/15161

*2022-09-07 Armbian_22.11.0-trunk_Bananapim64_jammy_edge_5.19.7_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1_BaSpSdIaxJYy-QjaXLsOrJ25Ja7vA78/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1uOex7pm2tPhfJ47hoXIuGA?pwd=7hms (pincode: 7hms)

*[https://www.armbian.com/bananapi-m64/ Armbian Image] is base on Linux Mainline kernel

=== Raspbian===

*2018-11-06 update : This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Raspbian 9.4 is based on kernel 3.10 & kernel 4.4.
::BPI-M64 Raspbian 9.4 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Raspbian_9.4_AARCH64
::::Google Drive : https://drive.google.com/file/d/1qoKCVDgiuEj0IVEzuPgzuFLjFR9hTLH8/view
::::Baidu Drive : https://pan.baidu.com/s/1MlIzQRpjs_soBDXOKf8NAw
::::md5sum : e321c6dbb096a0348fceb9d4a0b6c210
::BPI-M64 Raspbian 9.4 Kernel 4.4
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89_4
::::Google Drive : https://drive.google.com/file/d/1WnsHKnbI_FWQVkHQmbCcJ3yJ38oWaHGy/view
::::Baidu Drive : https://pan.baidu.com/s/1Bu-xiqiYsnau_xZp8-QEkw
::::md5sum : 1d4f00680e6869e2c4e66e205e61d93d
::forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-raspbian-9-4-kernel-3-10-4-4-release-2018-11-06/7195

===Fedora Linux===
*BPI-M64 fedora image download(not support desktop): fedora 31 with grub (u-boot-2019.07 + kernel 5.3.0)
::https://drive.google.com/file/d/1dIr943Ke28lEtCDpy8cI3q1dBUtHymJP/view?usp=drivesdk
::https://drive.google.com/file/d/1F3nYOw9AiLLaz8be0umz_9nlnhDP3t0s/view?usp=drivesdk
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-fedora-31-with-grub-u-boot-2019-07-kernel-5-3-0/9938

===Manjaro===
*2019-01-15 update,BananaPi BPI-M64 Support Run Manjaro AArch64 System
::Baidu Drive: https://pan.baidu.com/s/18drwPBFKAzf4lFe6IPjaPA
::Google Drive: https://drive.google.com/open?id=1Lu8xw4sAVyiHJT4eYcolNTAIKG154gm6
::Bpi Ftp Server: https://dev.banana-pi.org.cn/Image/BPI-M64/Manjaro/
::md5sum : 8c9964fbd80836228c72fa205eb62f78
::username: manjaro/root
::password: bananapi
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-manjaro-aarch64-system-2019-01-16/7696

===FreeBSD===

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

===Clonezilla===

*Clonezilla support arm64 (Banana Pi BPI-M64),Thanks to Steven Shiau (NCHC Free Software Labs in Taiwan) & https://clonezilla.org/ 1, this image just for test .
*image download:https://drive.google.com/file/d/15oj0RjoU1TPC-jOXJ2bfhLb3vAiMf7p2/view
*discuss on forum: http://forum.banana-pi.org/t/bpi-m64-new-image-clonezilla-support-arm64-on-bpi-m64/10789

===Others===
* others image ,you can download at forum ： http://forum.banana-pi.org/c/BPI-M64/M63image

==Win 10 IoT==

* 2017-1-13 updae Win10 IoT Core beta0.2
::baidu cloud :http://pan.baidu.com/s/1c2ce100

*Win10 IoT Core 10586 beta0.1
::download link : https://drive.google.com/open?id=0B_YnvHgh2rwjODJOSS1TdkRvcEk
::baidu link : http://pan.baidu.com/s/1dEQyGgD
::MD5: 1c09118cd45bf0c3b61d1846710a3649

*BPI-M64 win10 IoT: https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

=FAQ=
*1,How-to use ubuntu system to support lcd7**?
::1."vi /media/pi/BPI-BOOT/bananapi/bpi-m64/linux/lcd7/uEnv.txt"
::2.If you use HC070TG lcd7 screen, change "touch=gt9xxnew_ts" But if you use S070WV20 lcd7 screen, you don't need to change.
::3. "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m64/u-boot-with-dtb-bpi-m64-lcd7-8k.img.gz"
::4.reboot
::[[File:BPI-M64_LCD7.png]]
::For more operation details please see Wiki: http://wiki.banana-pi.org/Getting_Started_with_M64

Banana Pi BPI-M64

2023-03-22T08:41:55Z

Czj: /* Armbian */

Banana Pi BPI-M64

2023-03-22T08:41:40Z

Czj: /* Ubuntu */

[[zh:香蕉派_BPI-M64]]
=Introduction=

[[File:Banana_pi_BPI-M64_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M64_2.jpg|thumb|Overview:Allwinner A64]]
[[File:BPI-M3_M2_ultra_Case.jpg|thumb|Premium Aluminum Enclosure]]
[[File:Bpi-m2_ultar_case_1.jpg|thumb|BPI-M64 acrylic case]]
[[File:BPI_iot_design.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] : A64 for smart home design]]
[[File:A64_for_IoT_gateway.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] :A64 for IoT gateway design]]

Banana Pi BPI-M64 is a 64-bit quad-core mini single board computer. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M64 has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, and lastly a DC power port. The processor is pin-to-pin comptialbe with R18, so it comes with two versions:M64 and M64-R18.

[[File:BPI-M64_960x360.jpg]]

Also being a member of the Banana Pi family, the M64 is a big jump from the octa-core BPI-M3. This is because this Banana Pi BPI is named after its 64-bit SoC. BPI-M64 will be reserved for an upcoming board

BPI-M64 is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==
* Allwinner A64 1.2 Ghz Quad-Core ARM Cortex A53 64-Bit Processor.
* 2 GB DDR3 SDRAM
* 8G EMMC
* 10/100/1000Mbps Ethernet
* WiFi (AP6212) & Bluetooth
* MIPI LCD interface
* Camera interface

==Getting Start==
*How to burn image : [[Quick Start Banana pi SBC]]
*how to development: [[Getting Started with M64]]

=Hardware=
==Hardware interface==
[[File:BPI-M64_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-M64'''
|-
|CPU|| Allwinner 64 Bit Quad Core ARM Cortex A53 1.2 GHz CPU
|-
| GPU|| Dual core Mali 400 MP2 GPU
|-
| Memory|| 2GB LPDDR3 (shared with GPU)
|-
| Storage|| MicroSD slot with support for up to 256GB expansion and 8G eMMC flash with support for up to 64GB
|-
| Network|| 10/100/1000 Mbit/s Ethernet + Wi-Fi 802.11 b/g/n + Bluetooth 4.0
|-
|Video Input(s)|| A CSI input connector allows for the connection of a designed camera module
|-
|Video Output(s)|| 1080p capable HDMI port and multi-channel audio output (NO H./X.265 capabilities)
|-
| Audio Input(s)|| On board microphone
|-
| Audio Output(s)|| 3.5mm jack and HDMI
|-
| USB ports|| USB 2.0 PORT (x2), USB OTG (x1)
|-
| Remote|| IR Receiver
|-
|GPIO|| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). GPIO pins can be used for UART, I2C, SPI or PWM
|-
|Switches|| Reset, Power and U-boot
|-
| LED|| Power Status and 8P8C
|-
| Power Source|| 5 volt @2A via DC Power and/or Micro USB (OTG)
|-
|Size & Weight|| 92x60mm, 48g
|-
|OS|| Android and Linux
|}

==GPIO PIN define ==

Banana Pi BPI-M64 has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M64'''
|-
|GPIO Pin Name||Default Function||Function2：GPIO||Function3
|-
|CON2-P01|| VCC-3V3 ||　|| 　
|-
|CON2-P02|| VCC-5V|| ||　　
|-
|CON2-P03|| TWI1-SDA|| PH3|| 　
|-
|CON2-P04|| VCC-5V|| ||　 |　
|-
|CON2-P05|| TWI1-SCK|| PH2||
|-
|CON2-P06|| GND|| 　|| 　
|-
|CON2-P07|| PH6|| PH6|| 　
|-
|CON2-P08|| UART2-TX|| PB0|| 　
|-
|CON2-P09|| GND|| ||　　
|-
|CON2-P10|| UART2-RX|| PB1|| 　
|-
|CON2-P11|| PH7|| PH7|| 　
|-
|CON2-P12|| UART2-CTS|| PB3 ||　
|-
|CON2-P13|| DMIC-CLK|| PH10|| 　
|-
|CON2-P14|| GND|| || 　　
|-
|CON2-P15|| DMIC-DIN|| PH11|| 　
|-
|CON2-P16|| UART2-RTS|| PB2|| 　
|-
|CON2-P17|| VCC-3V3|| || 　　
|-
|CON2-P18|| PD4|| PD4 ||　
|-
|CON2-P19|| SPI1-MOSI|| PD2|| UART4-TX
|-
|CON2-P20|| GND|| || 　　
|-
|CON2-P21|| SPI1-MISO|| PD3|| UART4-RX
|-
|CON2-P22|| PC0|| PC0|| 　
|-
|CON2-P23|| SPI1-CLK|| PD1|| UART3-RX
|-
|CON2-P24|| SPI1-CS ||PD0|| UART3-TX
|-
|CON2-P25|| GND|| ||　　
|-
|CON2-P26|| PC2|| PC2 　||
|-
|CON2-P27|| PC4|| PC4 　||
|-
|CON2-P28|| PC3|| PC3 　||
|-
|CON2-P29|| PC7|| PC7 　||
|-
|CON2-P30|| GND ||　|| 　
|-
|CON2-P31|| PCM0-BCLK|| PB5 ||
|-
|CON2-P32|| PCM0-DIN|| PB7 ||　
|-
|CON2-P33|| PCM0-SYNC|| PB4 ||
|-
|CON2-P34|| GND ||　|| 　
|-
|CON2-P35|| PCM0-DOUT|| PB6 　||
|-
|CON2-P36|| PL9|| PL9 ||　
|-
|CON2-P37|| PL12|| PL12|| 　
|-
|CON2-P38|| PL7|| PL7 ||　
|-
|CON2-P39|| GND|| || 　　
|-
|CON2-P40|| PL8|| PL8||　
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “Camera”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI camer PIN define of Banana pi BPI-M64'''
|-
|CSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN5-P01|| NC|| 　
|-
|CN5-P02|| GND|| 　
|-
|CN5-P03|| CSI0-SDA|| PE13
|-
|CN5-P04|| CSI0-AVDD|| 　
|-
|CN5-P05|| CSI0-SCK|| PE12
|-
|CN5-P06|| CSI0-Reset|| PE16
|-
|CN5-P07|| CSI0-VSYNC|| PE3|
|-
|CN5-P08|| CSI0-PWDN|| PE17
|-
|CN5-P09|| CSI0-HSYNC|| PE2
|-
|CN5-P10|| CSI0-DVDD|| 　
|-
|CN5-P11|| CSI0-DOVDD|| 　
|-
|CN5-P12|| CSI0-D7|| PE11
|-
|CN5-P13|| CSI0-MCLK|| PE1
|-
|CN5-P14|| CSI0-D6|| PE10
|-
|CN5-P15|| GND|| 　
|-
|CN5-P16|| CSI0-D5|| PE9
|-
|CN5-P17|| CSI0-PCLK|| PE0
|-
|CN5-P18|| CSI0-D4|| PE8
|-
|CN5-P19|| CSI0-D0|| PE4
|-
|CN5-P20|| CSI0-D3|| PE7
|-
|CN5-P21|| CSI0-D1|| PE5
|-
|CN5-P22|| CSI0-D2|| PE6
|-
|CN5-P23|| GND ||　
|-
|CN5-P24|| CSI0-AFVCC||
|-
|}

'''MIPI DSI (Display Serial Interface)'''

The display Connector is a 40-pin FPC connector which can connect external LCD panel (MIPI DSI) and touch screen (I2C) module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''MIPI DSI display PIN define of Banana pi BPI-M64'''
|-
|DSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN6-P01|| VCC ||　
|-
|CN6-P02|| IPSOUT|| 　
|-
|CN6-P03|| VCC ||　
|-
|CN6-P04|| IPSOUT||　
|-
|CN6-P05|| GND|| 　
|-
|CN6-P06|| IPSOUT ||　
|-
|CN6-P07|| GND 　||
|-
|CN6-P08|| IPSOUT ||　
|-
|CN6-P09|| NC ||　
|-
|CN6-P10|| GND 　||
|-
|CN6-P11|| NC ||
|-
|CN6-P12|| DSI-D0N 　||
|-
|CN6-P13|| NC ||　
|-
|CN6-P14|| DSI-D0P 　||
|-
|CN6-P15|| NC ||　
|-
|CN6-P16|| GND 　||
|-
|CN6-P17|| TWI0-SDA|| PH1
|-
|CN6-P18|| DSI-D1N ||
|-
|CN6-P19|| TWI0-SCK|| PH0
|-
|CN6-P20|| DSI-D1P 　||
|-
|CN6-P21|| CTP-INT|| PH4
|-
|CN6-P22|| GND|| 　
|-
|CN6-P23|| CTP-RST|| PH8
|-
|CN6-P24|| DSI-CKN ||
|-
|CN6-P25|| GND 　||
|-
|CN6-P26|| DSI-CKP ||　
|-
|CN6-P27|| LCD-BL-EN|| PD5
|-
|CN6-P28|| GND 　||
|-
|CN6-P29|| LCD-RST ||PD6
|-
|CN6-P30|| DSI-D2N ||　
|-
|CN6-P31|| LCD-PWR-EN ||PD7
|-
|CN6-P32|| DSI-D2P ||　
|-
|CN6-P33|| GND 　||
|-
|CN6-P34|| GND ||　
|-
|CN6-P35|| LCD-PWM|| PL10
|-
|CN6-P36|| DSI-D3N 　||
|-
|CN6-P37|| GND 　||
|-
|CN6-P38|| DSI-D3P ||　
|-
|CN6-P39|| NC 　||
|-
|CN6-P40|| GND 　||
|-
|}

'''UART specification:'''

The header CON2 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart PIN define of Banana pi BPI-M64'''
|-
|CON2 Pin Name|| Default Function|| GPIO
|-
|CON2 P03||UART0-TXD|| PB8
|-
|CON2 P02|| UART0-RXD|| PB9
|-
|CON2 P01|| GND ||　
|-
|}

=Software=

=Development=

==Basic Development==

===Win 10 IoT ===
banana pi BPI-M64 IOT certifying pass by Microsoft:windows 10 iot core

BPI-M64 for Win10 IoT : https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

[[File:Win10_1.png]]

link: https://azure.microsoft.com/en-us/documentation/articles/iot-hub-tested-configurations/

get start:

https://github.com/Azure/azure-iot-sdks/blob/master/doc/get_started/windows10-iot-core-banana-pi-bpi-m64-csharp.md

test on BPI-M64

[[File:Win10_2.jpg]]

discuss on forum: http://forum.banana-pi.org/t/banana-pi-bpi-m64-iot-certifying-pass-by-microsoft-windows-10-iot-core/2090

'''Windows 10 IoT Core for BPI-M64 Release Note'''

The Unified Extensible Firmware Interface (UEFI]) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers
AllWinner UEFI Firmware Release Notes

This document describes how to build AllWinner UEFI Firmware and bring a AllWinner dev board up with it. The AllWinner UEFI Firmware, as the major boot system for AllWinner-Windows platform, is based on the EDK2 framework which is open-source and with some AllWinner platform software packages injected.

Some updates:
::1. Update the OS version to build v.10.0.15063.0 $Creators Update$
::2. New page style of Device Portal, visit [https://deviceipaddr:8080](https://deviceipaddr:8080) to check it
::3. Built-in Cortana assistant, need to be enabled in settings page in default app and Device Portal
::4. Support on-screen keyboard, need to be enabled in Device Portal
::5. Enable 100M Ethernet and fix some bugs
::6. Support built-in UART bus in A64 SoC$not built in the ffu, later provide driver binary and deployment helper$
::7. Support built-in IR module in A64 SoC$not built in the ffu, later provide source code and dev doc for developers in community$

Known Issues:
::Kernel debug is enabled by default. This will slow the bring-up process. If a kernel debug is not necessary for you, visit Device Portal and navigate to Processes->Run Command page, run this command to disable : Bcdedit /store C:\EFIESP\EFI\Microsoft\boot\BCD /set {default} debug off
::An PnP bug in audio device may cause a blue screen when acting software shutdown
::Ethernet device may not start with problem code 12 at the first time to bring up

And another bomb! I uploaded core driver binaries and packaging toolchains on GitHub!

Here is the repo address: https://github.com/Leeway213/BSP-aw1689

And also some driver source code here with A64 datasheet in readme: https://github.com/Leeway213/driver-samples

Welcome makers developers and anyone-elsers to post your feedback.

===Microsoft Azure IoT===
* we have test BPI-M64 with Microsoft Azure IoT with aarch64 Ubuntu 18.04 Linux
::Microsoft Azure IoT Edge using DPS with TPM 2.0 SLB9670 : https://www.youtube.com/watch?v=k9_GSQgKlqk&feature=youtu.be
::Microsoft Azure IoT Edge using DPS with TPM 2.0 ST33 i2c : https://www.youtube.com/watch?v=2MrO1-esjwI&feature=youtu.be

=Resources=
==Source code==
*BPI-M64 Android 7 source code
:: download link : https://github.com/BPI-SINOVOIP/BPI-A64-Android7

*BPI-M64 Android 6.0.1 source code
:: download link : https://drive.google.com/open?id=0B_YnvHgh2rwjdTRVRVFaSHd2cnc

*BPI-M64 (allwnner A64) Linux 4.4 source code
::https://github.com/BPI-SINOVOIP/BPI-M64-bsp-4.4
::Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-allwnner-a64-linux-4-4-source-code-public-on-github/6706

*BPI-M64 Linux kernel 3.4 BSP code:
:: github link : https://github.com/BPI-SINOVOIP/BPI-M64-bsp

*BPI-M64 Win10 IoT source code
::https://bananapi.gitbooks.io/bpi-m64/content/en/sourcecodeongithub.html

*BPI-M64 Robot Operating System (ROS):
::github: https://github.com/techping/BPI-robot-1
::discuss on forum: http://forum.banana-pi.org/t/discuss-robot-operating-system-ros-on-banana-pi/10967

== documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram:
::google driver :[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
::baidu cloud : http://pan.baidu.com/s/1kVRpcYb
* DXF file google download link :https://drive.google.com/file/d/0B4PAo2nW2KfnajlEY0xsdjNxY3c/view?usp=sharing
*Allwinner A64 chip datasheet:https://drive.google.com/file/d/0B4PAo2nW2KfnSW9lQnZ0d1RoVW8/view?usp=sharing
*Allwinner A64 user’s manual (720 pages):https://drive.google.com/file/d/0B4PAo2nW2KfnNHk4dkFJZEdqYXc/view?usp=sharing
*AXP803 Datasheet V1.0.pdf :https://drive.google.com/file/d/1nRbP1T02KlNZBbTJx4BHW5wVWvQPmDxC/view?usp=sharing
*A64 chip linux-sunxi wiki:http://linux-sunxi.org/A64
*BPI-M64 linux-sunxi wiki: https://linux-sunxi.org/Banana_Pi_M64
*other document about allwinner A64 chip:http://bundie.neterra.net:8080/a64/
*battery interface spec ： https://drive.google.com/file/d/0B4PAo2nW2KfnSmVuVDhQc0NLdG8/view?usp=sharing
*BPI-M64 quality guarantee
::BPI-M64 BT Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64bt40labtest.html
::BPI-M64 WIFI Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m264wifilabtest.html
::BPI-M64 Validation test : https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64validationtestreport.html
::CE FCC RoHS : http://forum.banana-pi.org/t/bpi-m64-ce-fcc-rohs-certification/2747

== Amazon AWS Greengrass==

Banana Pi BPI-M64 passed Amazon AWS Greengrass:https://devices.amazonaws.com/detail/a3G0h000000OvPoEAK/Banana-Pi-BPI-M64

=Image Release=

==Android ==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Android_Image How to install the Android image]

*2020-07-10 update, Android 7.1, base on kernel 3.10
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2FAndroid7.1&mode=list Download Android 7.1 image]

*2018-10-24 update Android 6.0 & 7.0 & 8.1, based on kernel 3.10.

:M64 Android 6.0 HDMI & LCD7
::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1Em7ZXVvbJI7wMXy_TM4VNwHo6Oa-vVBc
::::Baidu Drive : https://pan.baidu.com/s/1ZginIvO3LVakqokIZAX1Xw

::LCD7 Version Image Links:
:::: Google Drive : https://drive.google.com/open?id=1Tts1krZyzwz9mL90j1ilTzVrJm6hh_J4
::::Baidu Drive : https://pan.baidu.com/s/1oKMx_Ml5K1Jv7-qeS-NMsQ

:M64 Android 7.0 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_7.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1mvKyK6KuPixs-jLD0FocIaV465bJ1Eig
::::Baidu Drive : https://pan.baidu.com/s/15b32TXdh6752c-GBnR-Zeg

::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=16Ffc5xiZgD7JYgrMtCGaOYLCuZdQGcnY
::::Baidu Drive : https://pan.baidu.com/s/1a9RYKSTRhCO-UzFfIoGCtQ

*BPI-M64 Android 8.1 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1UBaH9CNbmC9-n3jGImrFIAPZ8aZhqMJz
::::Baidu Drive : https://pan.baidu.com/s/1lz57HrqNHx6f_Q6nk0oZvA
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1wktuCcvolfozMFkLmugfZtGziHDj-1EM
::::Baidu Drive : https://pan.baidu.com/s/1MteYqyBp8LeECjcDteCTZQ
*Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-android-6-0-7-0-8-1-release-2018-10-24/7107

*2018-9-17 update android 6.0
::Features Map :http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=19ExJ9Ztfy3UgK9NZ4SiaVZAMozgyCJl7
::::Baidu Drive : https://pan.baidu.com/s/1s_orgiEI7JU_hUgjnpd25w
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1gWD_IT0P4NvdeqtK5I4MnJjwzsP7SXJc
::::Baidu Drive : https://pan.baidu.com/s/1K0HYPiQe6nGvAS5bAAFHow
::Forum pthread :　http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796
*2018-08-17 update,android 8.1
::This release is for banana pi M64 board which is based on Allwinner A64, We have two images release，Android 8.1 is based on kernel 4.9
::BPI-M64 Android 8.1 Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI-LCD-Version:
::Google Drive : https://drive.google.com/open?id=11XjvTAbPw57R6H5kL27GVXry4xu18dVs
::Baidu Drive : https://pan.baidu.com/s/1PQgJCUo6cY3wWxJ7rZrk-A
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

* 2018-05-20 update ,android 7.0
::hdmi-Version and Lcd 5.0 version
::baidu cloud : https://pan.baidu.com/s/1O3PsI73WmFFvhxMmzEscIQ

* 2017-05-11 update ,android 6.0
::HDMI-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjcF9USm1MWWtxSXc
::Baidu Cloud:https://pan.baidu.com/s/1bHWhlW
::MD5: f85281213b9c5b88008a487dd1b6963c
::LCD-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjdHpFbHJMQWtsbFk
::Baidu Cloud:https://pan.baidu.com/s/1kVJVPGV
::MD5:be27e4eced96d3de81d46e512fd978eb
::forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-android-6-0-version-v3/3240/4

==Linux==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Linux_Image How to install BPI Linux Image]

* 2020-08-26 update, Ubuntu Mate 18.04, Ubuntu Server 16.04, Raspbian Stretch, base on kernel 4.4
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2Flinux&mode=list Download Image]

* 2020-04-21 update, Rasbian Stretch, Ubuntu 16.06 Mate Desktop, Ubuntu 16.06 Server and Ubuntu 18.04 Mate Desktop, base on kernel 4.4
::google drive:https://drive.google.com/drive/folders/0B_YnvHgh2rwja3I4SllZN2VkYm8
::baidu cloud:https://pan.baidu.com/s/18XH8_uusUGBusbp4xw4txQ Pincode：36R0

=== Ubuntu===

* 2018-11-02 update, based on kernel 3.10 & kernel 4.4.
::BPI-M64 Ubuntu 16.04 Desktp
::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::::Google Drive : https://drive.google.com/file/d/1YzdkY8i-IsXzXLkbPCPNbAuhYbHmUwgv/view
::::Baidu Drive : https://pan.baidu.com/s/1XhOJBQtPkhvidjgipFNdzg
::::md5sum : 3564f0d3de9936aa26b93eaf027703a0

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_aarch64_16.04
::::Google Drive : Chttps://drive.google.com/file/d/1MglySZLvquRPu1Wj8oLwdKBkFnRzLUL-/view
::::Baidu Drive : https://pan.baidu.com/s/1_ZTDCuL9QZf6qrqaE4gbgQ
::::md5sum : 7422e02daa01bff6de808490e89b436e

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 4.4
::::features Map:http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89
::::Google Drive : https://drive.google.com/file/d/1g_m1NLn1-wUQ8jjPKEAwQcSj4d4P9vRP/view
::::Baidu Drive : https://pan.baidu.com/s/1JmKQGRKvJ9DwL_ij0K79FA
::::md5sum : ea9bba6ab7fc78f7b8478bfd013a9b50

:: forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-ubuntu16-04-desktop-aarch64-release-2018-11-1/7159/1

::Debian 9.5 AARCH64 Kernel 3.10

::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Image Links: Google Drive : Coming soon
::::Baidu Drive: https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum: 71fe25c1922c7f9ef81bb88e0f544de6

*2018-4-17 update Ubuntu 16.04.4 with linux kernel 4.4.89
::image name:2018-04-17-ubuntu-16.04-mate-desktop-demo3-k4.4.89-vdpau-3-mic-docker-bpi-r18-avs-aarch64-sd-emmc.img.zip
::Google Drive: https://drive.google.com/open?id=1dlfo9LGNcrc-_cpKd1uJnrNx0PdonBnK
::MD5: 4b7e163d260e58a39ba8905e7ed39943
::Forum pthread:http://forum.banana-pi.org/t/bpi-r18-avs-new-image-ubuntu-16-04-4-with-linux-kernel-4-4-89-2018-4-17/5435

*2018-09-18 This release is for banana pi M64 board which is based on Allwinner A64, We release three Images, Ubuntu 16.04 Desktop & Android is based on kernel 3.10.
::Features Map ：http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::Google Drive :
::Baidu Drive : https://pan.baidu.com/s/1wANJ4SwfNwKtBcd02WcbWA
::forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796

*2018-08-17 update Ubuntu 16.04 Server kernel 3.10.105
::Google Drive : https://drive.google.com/open?id=1K-B4u8jGcv17s3I9v-Pr0xv5u5txvfok
::Baidu Drive : https://pan.baidu.com/s/1HcrR8NsL9_1RwbZNa7uwmg
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

*2017-08-14 update based on ubuntu 16.04.3 LTS Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive: https://drive.google.com/file/d/0B_YnvHgh2rwjN1h1U0xDYUxET00/view?usp=sharing
::baidu cloud: http://pan.baidu.com/s/1pLkbdTT
::MD5: ae34baa840874276858d936a7ca85c4f
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-14-ubuntu-16-04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc/3695

===Debian===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim64_bullseye_edge_5.19.7_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1UUbn24l3q_OsVP4XWT6eVQN531tHPzX0/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1vFR9sUR0FhWgS1pemk9lTg?pwd=ina6 (pincode: ina6)

*2018-11-2 update , This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Debian 9.5 AARCH64 is based on kernel 3.10 & kernel 4.4.

::M64 Debian 9.5 AARCH64 Kernel 3.10
::::Features Map : * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google driver : https://drive.google.com/file/d/10qGv2gVrSgwXMBLDsCF0nQFc9EJnnkeS/view
::::Baidu Drive : https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum : 71fe25c1922c7f9ef81bb88e0f544de6

::M64 Debian 9.5 AARCH64 Kernel 4.4
::::Features Map: * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google Drive : https://drive.google.com/file/d/17fh3YY6cwOzHMsqwnRQRTu9cXjKU4_tV/view
::::Baidu Drive : https://pan.baidu.com/s/1sOR6WFz2U9MT0ltq6zYnJA
::::md5sum : f3c2391b0232178018fda7ebfd64b14c
::forum pthread:http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-debian-9-5-aarch64-release-2018-11-02/7166

*2017-08-13 debian 8.9 jessie Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjazlNRTRHei1NbmM/view?usp=sharing
::baidu cloud:http://pan.baidu.com/s/1eSeTQeA
::MD5: 9ddf067457ebaf193de63c5c7141446a
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-13-debian-8-jessie-mate-desktop-preview-aarch64-bpi-m64-sd-emmc/3694

===Armbian===
*Armbian_23.02.0-trunk_Bananapim64_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapim64_jammy_edge_6.1.11_xfce_desktop.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m64-new-armbian-image/15161

*[https://www.armbian.com/bananapi-m64/ Armbian Image] is base on Linux Mainline kernel

=== Raspbian===

*2018-11-06 update : This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Raspbian 9.4 is based on kernel 3.10 & kernel 4.4.
::BPI-M64 Raspbian 9.4 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Raspbian_9.4_AARCH64
::::Google Drive : https://drive.google.com/file/d/1qoKCVDgiuEj0IVEzuPgzuFLjFR9hTLH8/view
::::Baidu Drive : https://pan.baidu.com/s/1MlIzQRpjs_soBDXOKf8NAw
::::md5sum : e321c6dbb096a0348fceb9d4a0b6c210
::BPI-M64 Raspbian 9.4 Kernel 4.4
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89_4
::::Google Drive : https://drive.google.com/file/d/1WnsHKnbI_FWQVkHQmbCcJ3yJ38oWaHGy/view
::::Baidu Drive : https://pan.baidu.com/s/1Bu-xiqiYsnau_xZp8-QEkw
::::md5sum : 1d4f00680e6869e2c4e66e205e61d93d
::forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-raspbian-9-4-kernel-3-10-4-4-release-2018-11-06/7195

===Fedora Linux===
*BPI-M64 fedora image download(not support desktop): fedora 31 with grub (u-boot-2019.07 + kernel 5.3.0)
::https://drive.google.com/file/d/1dIr943Ke28lEtCDpy8cI3q1dBUtHymJP/view?usp=drivesdk
::https://drive.google.com/file/d/1F3nYOw9AiLLaz8be0umz_9nlnhDP3t0s/view?usp=drivesdk
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-fedora-31-with-grub-u-boot-2019-07-kernel-5-3-0/9938

===Manjaro===
*2019-01-15 update,BananaPi BPI-M64 Support Run Manjaro AArch64 System
::Baidu Drive: https://pan.baidu.com/s/18drwPBFKAzf4lFe6IPjaPA
::Google Drive: https://drive.google.com/open?id=1Lu8xw4sAVyiHJT4eYcolNTAIKG154gm6
::Bpi Ftp Server: https://dev.banana-pi.org.cn/Image/BPI-M64/Manjaro/
::md5sum : 8c9964fbd80836228c72fa205eb62f78
::username: manjaro/root
::password: bananapi
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-manjaro-aarch64-system-2019-01-16/7696

===FreeBSD===

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

===Clonezilla===

*Clonezilla support arm64 (Banana Pi BPI-M64),Thanks to Steven Shiau (NCHC Free Software Labs in Taiwan) & https://clonezilla.org/ 1, this image just for test .
*image download:https://drive.google.com/file/d/15oj0RjoU1TPC-jOXJ2bfhLb3vAiMf7p2/view
*discuss on forum: http://forum.banana-pi.org/t/bpi-m64-new-image-clonezilla-support-arm64-on-bpi-m64/10789

===Others===
* others image ,you can download at forum ： http://forum.banana-pi.org/c/BPI-M64/M63image

==Win 10 IoT==

* 2017-1-13 updae Win10 IoT Core beta0.2
::baidu cloud :http://pan.baidu.com/s/1c2ce100

*Win10 IoT Core 10586 beta0.1
::download link : https://drive.google.com/open?id=0B_YnvHgh2rwjODJOSS1TdkRvcEk
::baidu link : http://pan.baidu.com/s/1dEQyGgD
::MD5: 1c09118cd45bf0c3b61d1846710a3649

*BPI-M64 win10 IoT: https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

=FAQ=
*1,How-to use ubuntu system to support lcd7**?
::1."vi /media/pi/BPI-BOOT/bananapi/bpi-m64/linux/lcd7/uEnv.txt"
::2.If you use HC070TG lcd7 screen, change "touch=gt9xxnew_ts" But if you use S070WV20 lcd7 screen, you don't need to change.
::3. "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m64/u-boot-with-dtb-bpi-m64-lcd7-8k.img.gz"
::4.reboot
::[[File:BPI-M64_LCD7.png]]
::For more operation details please see Wiki: http://wiki.banana-pi.org/Getting_Started_with_M64

Banana Pi BPI-M64

2023-03-22T06:56:01Z

Czj: /* Armbian */

[[zh:香蕉派_BPI-M64]]
=Introduction=

[[File:Banana_pi_BPI-M64_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M64_2.jpg|thumb|Overview:Allwinner A64]]
[[File:BPI-M3_M2_ultra_Case.jpg|thumb|Premium Aluminum Enclosure]]
[[File:Bpi-m2_ultar_case_1.jpg|thumb|BPI-M64 acrylic case]]
[[File:BPI_iot_design.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] : A64 for smart home design]]
[[File:A64_for_IoT_gateway.JPG|thumb|BPI-M64 for BPI 4.0 [[Successful case]] :A64 for IoT gateway design]]

Banana Pi BPI-M64 is a 64-bit quad-core mini single board computer. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M64 has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, and lastly a DC power port. The processor is pin-to-pin comptialbe with R18, so it comes with two versions:M64 and M64-R18.

[[File:BPI-M64_960x360.jpg]]

Also being a member of the Banana Pi family, the M64 is a big jump from the octa-core BPI-M3. This is because this Banana Pi BPI is named after its 64-bit SoC. BPI-M64 will be reserved for an upcoming board

BPI-M64 is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==
* Allwinner A64 1.2 Ghz Quad-Core ARM Cortex A53 64-Bit Processor.
* 2 GB DDR3 SDRAM
* 8G EMMC
* 10/100/1000Mbps Ethernet
* WiFi (AP6212) & Bluetooth
* MIPI LCD interface
* Camera interface

==Getting Start==
*How to burn image : [[Quick Start Banana pi SBC]]
*how to development: [[Getting Started with M64]]

=Hardware=
==Hardware interface==
[[File:BPI-M64_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-M64'''
|-
|CPU|| Allwinner 64 Bit Quad Core ARM Cortex A53 1.2 GHz CPU
|-
| GPU|| Dual core Mali 400 MP2 GPU
|-
| Memory|| 2GB LPDDR3 (shared with GPU)
|-
| Storage|| MicroSD slot with support for up to 256GB expansion and 8G eMMC flash with support for up to 64GB
|-
| Network|| 10/100/1000 Mbit/s Ethernet + Wi-Fi 802.11 b/g/n + Bluetooth 4.0
|-
|Video Input(s)|| A CSI input connector allows for the connection of a designed camera module
|-
|Video Output(s)|| 1080p capable HDMI port and multi-channel audio output (NO H./X.265 capabilities)
|-
| Audio Input(s)|| On board microphone
|-
| Audio Output(s)|| 3.5mm jack and HDMI
|-
| USB ports|| USB 2.0 PORT (x2), USB OTG (x1)
|-
| Remote|| IR Receiver
|-
|GPIO|| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). GPIO pins can be used for UART, I2C, SPI or PWM
|-
|Switches|| Reset, Power and U-boot
|-
| LED|| Power Status and 8P8C
|-
| Power Source|| 5 volt @2A via DC Power and/or Micro USB (OTG)
|-
|Size & Weight|| 92x60mm, 48g
|-
|OS|| Android and Linux
|}

==GPIO PIN define ==

Banana Pi BPI-M64 has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M64'''
|-
|GPIO Pin Name||Default Function||Function2：GPIO||Function3
|-
|CON2-P01|| VCC-3V3 ||　|| 　
|-
|CON2-P02|| VCC-5V|| ||　　
|-
|CON2-P03|| TWI1-SDA|| PH3|| 　
|-
|CON2-P04|| VCC-5V|| ||　 |　
|-
|CON2-P05|| TWI1-SCK|| PH2||
|-
|CON2-P06|| GND|| 　|| 　
|-
|CON2-P07|| PH6|| PH6|| 　
|-
|CON2-P08|| UART2-TX|| PB0|| 　
|-
|CON2-P09|| GND|| ||　　
|-
|CON2-P10|| UART2-RX|| PB1|| 　
|-
|CON2-P11|| PH7|| PH7|| 　
|-
|CON2-P12|| UART2-CTS|| PB3 ||　
|-
|CON2-P13|| DMIC-CLK|| PH10|| 　
|-
|CON2-P14|| GND|| || 　　
|-
|CON2-P15|| DMIC-DIN|| PH11|| 　
|-
|CON2-P16|| UART2-RTS|| PB2|| 　
|-
|CON2-P17|| VCC-3V3|| || 　　
|-
|CON2-P18|| PD4|| PD4 ||　
|-
|CON2-P19|| SPI1-MOSI|| PD2|| UART4-TX
|-
|CON2-P20|| GND|| || 　　
|-
|CON2-P21|| SPI1-MISO|| PD3|| UART4-RX
|-
|CON2-P22|| PC0|| PC0|| 　
|-
|CON2-P23|| SPI1-CLK|| PD1|| UART3-RX
|-
|CON2-P24|| SPI1-CS ||PD0|| UART3-TX
|-
|CON2-P25|| GND|| ||　　
|-
|CON2-P26|| PC2|| PC2 　||
|-
|CON2-P27|| PC4|| PC4 　||
|-
|CON2-P28|| PC3|| PC3 　||
|-
|CON2-P29|| PC7|| PC7 　||
|-
|CON2-P30|| GND ||　|| 　
|-
|CON2-P31|| PCM0-BCLK|| PB5 ||
|-
|CON2-P32|| PCM0-DIN|| PB7 ||　
|-
|CON2-P33|| PCM0-SYNC|| PB4 ||
|-
|CON2-P34|| GND ||　|| 　
|-
|CON2-P35|| PCM0-DOUT|| PB6 　||
|-
|CON2-P36|| PL9|| PL9 ||　
|-
|CON2-P37|| PL12|| PL12|| 　
|-
|CON2-P38|| PL7|| PL7 ||　
|-
|CON2-P39|| GND|| || 　　
|-
|CON2-P40|| PL8|| PL8||　
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “Camera”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI camer PIN define of Banana pi BPI-M64'''
|-
|CSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN5-P01|| NC|| 　
|-
|CN5-P02|| GND|| 　
|-
|CN5-P03|| CSI0-SDA|| PE13
|-
|CN5-P04|| CSI0-AVDD|| 　
|-
|CN5-P05|| CSI0-SCK|| PE12
|-
|CN5-P06|| CSI0-Reset|| PE16
|-
|CN5-P07|| CSI0-VSYNC|| PE3|
|-
|CN5-P08|| CSI0-PWDN|| PE17
|-
|CN5-P09|| CSI0-HSYNC|| PE2
|-
|CN5-P10|| CSI0-DVDD|| 　
|-
|CN5-P11|| CSI0-DOVDD|| 　
|-
|CN5-P12|| CSI0-D7|| PE11
|-
|CN5-P13|| CSI0-MCLK|| PE1
|-
|CN5-P14|| CSI0-D6|| PE10
|-
|CN5-P15|| GND|| 　
|-
|CN5-P16|| CSI0-D5|| PE9
|-
|CN5-P17|| CSI0-PCLK|| PE0
|-
|CN5-P18|| CSI0-D4|| PE8
|-
|CN5-P19|| CSI0-D0|| PE4
|-
|CN5-P20|| CSI0-D3|| PE7
|-
|CN5-P21|| CSI0-D1|| PE5
|-
|CN5-P22|| CSI0-D2|| PE6
|-
|CN5-P23|| GND ||　
|-
|CN5-P24|| CSI0-AFVCC||
|-
|}

'''MIPI DSI (Display Serial Interface)'''

The display Connector is a 40-pin FPC connector which can connect external LCD panel (MIPI DSI) and touch screen (I2C) module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''MIPI DSI display PIN define of Banana pi BPI-M64'''
|-
|DSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN6-P01|| VCC ||　
|-
|CN6-P02|| IPSOUT|| 　
|-
|CN6-P03|| VCC ||　
|-
|CN6-P04|| IPSOUT||　
|-
|CN6-P05|| GND|| 　
|-
|CN6-P06|| IPSOUT ||　
|-
|CN6-P07|| GND 　||
|-
|CN6-P08|| IPSOUT ||　
|-
|CN6-P09|| NC ||　
|-
|CN6-P10|| GND 　||
|-
|CN6-P11|| NC ||
|-
|CN6-P12|| DSI-D0N 　||
|-
|CN6-P13|| NC ||　
|-
|CN6-P14|| DSI-D0P 　||
|-
|CN6-P15|| NC ||　
|-
|CN6-P16|| GND 　||
|-
|CN6-P17|| TWI0-SDA|| PH1
|-
|CN6-P18|| DSI-D1N ||
|-
|CN6-P19|| TWI0-SCK|| PH0
|-
|CN6-P20|| DSI-D1P 　||
|-
|CN6-P21|| CTP-INT|| PH4
|-
|CN6-P22|| GND|| 　
|-
|CN6-P23|| CTP-RST|| PH8
|-
|CN6-P24|| DSI-CKN ||
|-
|CN6-P25|| GND 　||
|-
|CN6-P26|| DSI-CKP ||　
|-
|CN6-P27|| LCD-BL-EN|| PD5
|-
|CN6-P28|| GND 　||
|-
|CN6-P29|| LCD-RST ||PD6
|-
|CN6-P30|| DSI-D2N ||　
|-
|CN6-P31|| LCD-PWR-EN ||PD7
|-
|CN6-P32|| DSI-D2P ||　
|-
|CN6-P33|| GND 　||
|-
|CN6-P34|| GND ||　
|-
|CN6-P35|| LCD-PWM|| PL10
|-
|CN6-P36|| DSI-D3N 　||
|-
|CN6-P37|| GND 　||
|-
|CN6-P38|| DSI-D3P ||　
|-
|CN6-P39|| NC 　||
|-
|CN6-P40|| GND 　||
|-
|}

'''UART specification:'''

The header CON2 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart PIN define of Banana pi BPI-M64'''
|-
|CON2 Pin Name|| Default Function|| GPIO
|-
|CON2 P03||UART0-TXD|| PB8
|-
|CON2 P02|| UART0-RXD|| PB9
|-
|CON2 P01|| GND ||　
|-
|}

=Software=

=Development=

==Basic Development==

===Win 10 IoT ===
banana pi BPI-M64 IOT certifying pass by Microsoft:windows 10 iot core

BPI-M64 for Win10 IoT : https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

[[File:Win10_1.png]]

link: https://azure.microsoft.com/en-us/documentation/articles/iot-hub-tested-configurations/

get start:

https://github.com/Azure/azure-iot-sdks/blob/master/doc/get_started/windows10-iot-core-banana-pi-bpi-m64-csharp.md

test on BPI-M64

[[File:Win10_2.jpg]]

discuss on forum: http://forum.banana-pi.org/t/banana-pi-bpi-m64-iot-certifying-pass-by-microsoft-windows-10-iot-core/2090

'''Windows 10 IoT Core for BPI-M64 Release Note'''

The Unified Extensible Firmware Interface (UEFI]) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers
AllWinner UEFI Firmware Release Notes

This document describes how to build AllWinner UEFI Firmware and bring a AllWinner dev board up with it. The AllWinner UEFI Firmware, as the major boot system for AllWinner-Windows platform, is based on the EDK2 framework which is open-source and with some AllWinner platform software packages injected.

Some updates:
::1. Update the OS version to build v.10.0.15063.0 $Creators Update$
::2. New page style of Device Portal, visit [https://deviceipaddr:8080](https://deviceipaddr:8080) to check it
::3. Built-in Cortana assistant, need to be enabled in settings page in default app and Device Portal
::4. Support on-screen keyboard, need to be enabled in Device Portal
::5. Enable 100M Ethernet and fix some bugs
::6. Support built-in UART bus in A64 SoC$not built in the ffu, later provide driver binary and deployment helper$
::7. Support built-in IR module in A64 SoC$not built in the ffu, later provide source code and dev doc for developers in community$

Known Issues:
::Kernel debug is enabled by default. This will slow the bring-up process. If a kernel debug is not necessary for you, visit Device Portal and navigate to Processes->Run Command page, run this command to disable : Bcdedit /store C:\EFIESP\EFI\Microsoft\boot\BCD /set {default} debug off
::An PnP bug in audio device may cause a blue screen when acting software shutdown
::Ethernet device may not start with problem code 12 at the first time to bring up

And another bomb! I uploaded core driver binaries and packaging toolchains on GitHub!

Here is the repo address: https://github.com/Leeway213/BSP-aw1689

And also some driver source code here with A64 datasheet in readme: https://github.com/Leeway213/driver-samples

Welcome makers developers and anyone-elsers to post your feedback.

===Microsoft Azure IoT===
* we have test BPI-M64 with Microsoft Azure IoT with aarch64 Ubuntu 18.04 Linux
::Microsoft Azure IoT Edge using DPS with TPM 2.0 SLB9670 : https://www.youtube.com/watch?v=k9_GSQgKlqk&feature=youtu.be
::Microsoft Azure IoT Edge using DPS with TPM 2.0 ST33 i2c : https://www.youtube.com/watch?v=2MrO1-esjwI&feature=youtu.be

=Resources=
==Source code==
*BPI-M64 Android 7 source code
:: download link : https://github.com/BPI-SINOVOIP/BPI-A64-Android7

*BPI-M64 Android 6.0.1 source code
:: download link : https://drive.google.com/open?id=0B_YnvHgh2rwjdTRVRVFaSHd2cnc

*BPI-M64 (allwnner A64) Linux 4.4 source code
::https://github.com/BPI-SINOVOIP/BPI-M64-bsp-4.4
::Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-allwnner-a64-linux-4-4-source-code-public-on-github/6706

*BPI-M64 Linux kernel 3.4 BSP code:
:: github link : https://github.com/BPI-SINOVOIP/BPI-M64-bsp

*BPI-M64 Win10 IoT source code
::https://bananapi.gitbooks.io/bpi-m64/content/en/sourcecodeongithub.html

*BPI-M64 Robot Operating System (ROS):
::github: https://github.com/techping/BPI-robot-1
::discuss on forum: http://forum.banana-pi.org/t/discuss-robot-operating-system-ros-on-banana-pi/10967

== documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram:
::google driver :[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
::baidu cloud : http://pan.baidu.com/s/1kVRpcYb
* DXF file google download link :https://drive.google.com/file/d/0B4PAo2nW2KfnajlEY0xsdjNxY3c/view?usp=sharing
*Allwinner A64 chip datasheet:https://drive.google.com/file/d/0B4PAo2nW2KfnSW9lQnZ0d1RoVW8/view?usp=sharing
*Allwinner A64 user’s manual (720 pages):https://drive.google.com/file/d/0B4PAo2nW2KfnNHk4dkFJZEdqYXc/view?usp=sharing
*AXP803 Datasheet V1.0.pdf :https://drive.google.com/file/d/1nRbP1T02KlNZBbTJx4BHW5wVWvQPmDxC/view?usp=sharing
*A64 chip linux-sunxi wiki:http://linux-sunxi.org/A64
*BPI-M64 linux-sunxi wiki: https://linux-sunxi.org/Banana_Pi_M64
*other document about allwinner A64 chip:http://bundie.neterra.net:8080/a64/
*battery interface spec ： https://drive.google.com/file/d/0B4PAo2nW2KfnSmVuVDhQc0NLdG8/view?usp=sharing
*BPI-M64 quality guarantee
::BPI-M64 BT Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64bt40labtest.html
::BPI-M64 WIFI Lab test :https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m264wifilabtest.html
::BPI-M64 Validation test : https://bananapi.gitbooks.io/bpi-m64/content/en/bpi-m64validationtestreport.html
::CE FCC RoHS : http://forum.banana-pi.org/t/bpi-m64-ce-fcc-rohs-certification/2747

== Amazon AWS Greengrass==

Banana Pi BPI-M64 passed Amazon AWS Greengrass:https://devices.amazonaws.com/detail/a3G0h000000OvPoEAK/Banana-Pi-BPI-M64

=Image Release=

==Android ==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Android_Image How to install the Android image]

*2020-07-10 update, Android 7.1, base on kernel 3.10
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2FAndroid7.1&mode=list Download Android 7.1 image]

*2018-10-24 update Android 6.0 & 7.0 & 8.1, based on kernel 3.10.

:M64 Android 6.0 HDMI & LCD7
::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1Em7ZXVvbJI7wMXy_TM4VNwHo6Oa-vVBc
::::Baidu Drive : https://pan.baidu.com/s/1ZginIvO3LVakqokIZAX1Xw

::LCD7 Version Image Links:
:::: Google Drive : https://drive.google.com/open?id=1Tts1krZyzwz9mL90j1ilTzVrJm6hh_J4
::::Baidu Drive : https://pan.baidu.com/s/1oKMx_Ml5K1Jv7-qeS-NMsQ

:M64 Android 7.0 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_7.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1mvKyK6KuPixs-jLD0FocIaV465bJ1Eig
::::Baidu Drive : https://pan.baidu.com/s/15b32TXdh6752c-GBnR-Zeg

::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=16Ffc5xiZgD7JYgrMtCGaOYLCuZdQGcnY
::::Baidu Drive : https://pan.baidu.com/s/1a9RYKSTRhCO-UzFfIoGCtQ

*BPI-M64 Android 8.1 HDMI & LCD7
::Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=1UBaH9CNbmC9-n3jGImrFIAPZ8aZhqMJz
::::Baidu Drive : https://pan.baidu.com/s/1lz57HrqNHx6f_Q6nk0oZvA
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1wktuCcvolfozMFkLmugfZtGziHDj-1EM
::::Baidu Drive : https://pan.baidu.com/s/1MteYqyBp8LeECjcDteCTZQ
*Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-android-6-0-7-0-8-1-release-2018-10-24/7107

*2018-9-17 update android 6.0
::Features Map :http://wiki.banana-pi.org/M64_Image_Map#Android_6.0
::HDMI Version Image Links：
::::Google Drive : https://drive.google.com/open?id=19ExJ9Ztfy3UgK9NZ4SiaVZAMozgyCJl7
::::Baidu Drive : https://pan.baidu.com/s/1s_orgiEI7JU_hUgjnpd25w
::LCD7 Version Image Links:
::::Google Drive : https://drive.google.com/open?id=1gWD_IT0P4NvdeqtK5I4MnJjwzsP7SXJc
::::Baidu Drive : https://pan.baidu.com/s/1K0HYPiQe6nGvAS5bAAFHow
::Forum pthread :　http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796
*2018-08-17 update,android 8.1
::This release is for banana pi M64 board which is based on Allwinner A64, We have two images release，Android 8.1 is based on kernel 4.9
::BPI-M64 Android 8.1 Features Map:http://wiki.banana-pi.org/M64_Image_Map#Android_8.1
::HDMI-LCD-Version:
::Google Drive : https://drive.google.com/open?id=11XjvTAbPw57R6H5kL27GVXry4xu18dVs
::Baidu Drive : https://pan.baidu.com/s/1PQgJCUo6cY3wWxJ7rZrk-A
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

* 2018-05-20 update ,android 7.0
::hdmi-Version and Lcd 5.0 version
::baidu cloud : https://pan.baidu.com/s/1O3PsI73WmFFvhxMmzEscIQ

* 2017-05-11 update ,android 6.0
::HDMI-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjcF9USm1MWWtxSXc
::Baidu Cloud:https://pan.baidu.com/s/1bHWhlW
::MD5: f85281213b9c5b88008a487dd1b6963c
::LCD-Version
::Google Drive:https://drive.google.com/open?id=0B_YnvHgh2rwjdHpFbHJMQWtsbFk
::Baidu Cloud:https://pan.baidu.com/s/1kVJVPGV
::MD5:be27e4eced96d3de81d46e512fd978eb
::forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-android-6-0-version-v3/3240/4

==Linux==
[http://wiki.banana-pi.org/Getting_Started_with_M64#Install_Linux_Image How to install BPI Linux Image]

* 2020-08-26 update, Ubuntu Mate 18.04, Ubuntu Server 16.04, Raspbian Stretch, base on kernel 4.4
::[https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M64%2Flinux&mode=list Download Image]

* 2020-04-21 update, Rasbian Stretch, Ubuntu 16.06 Mate Desktop, Ubuntu 16.06 Server and Ubuntu 18.04 Mate Desktop, base on kernel 4.4
::google drive:https://drive.google.com/drive/folders/0B_YnvHgh2rwja3I4SllZN2VkYm8
::baidu cloud:https://pan.baidu.com/s/18XH8_uusUGBusbp4xw4txQ Pincode：36R0

=== Ubuntu===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim64_jammy_edge_5.19.7_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1_BaSpSdIaxJYy-QjaXLsOrJ25Ja7vA78/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1uOex7pm2tPhfJ47hoXIuGA?pwd=7hms (pincode: 7hms)

* 2018-11-02 update, based on kernel 3.10 & kernel 4.4.
::BPI-M64 Ubuntu 16.04 Desktp
::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::::Google Drive : https://drive.google.com/file/d/1YzdkY8i-IsXzXLkbPCPNbAuhYbHmUwgv/view
::::Baidu Drive : https://pan.baidu.com/s/1XhOJBQtPkhvidjgipFNdzg
::::md5sum : 3564f0d3de9936aa26b93eaf027703a0

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_aarch64_16.04
::::Google Drive : Chttps://drive.google.com/file/d/1MglySZLvquRPu1Wj8oLwdKBkFnRzLUL-/view
::::Baidu Drive : https://pan.baidu.com/s/1_ZTDCuL9QZf6qrqaE4gbgQ
::::md5sum : 7422e02daa01bff6de808490e89b436e

::BPI-M64 Ubuntu 16.04 AARCH64 Kernel 4.4
::::features Map:http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89
::::Google Drive : https://drive.google.com/file/d/1g_m1NLn1-wUQ8jjPKEAwQcSj4d4P9vRP/view
::::Baidu Drive : https://pan.baidu.com/s/1JmKQGRKvJ9DwL_ij0K79FA
::::md5sum : ea9bba6ab7fc78f7b8478bfd013a9b50

:: forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-ubuntu16-04-desktop-aarch64-release-2018-11-1/7159/1

::Debian 9.5 AARCH64 Kernel 3.10

::::Features Map: http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Image Links: Google Drive : Coming soon
::::Baidu Drive: https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum: 71fe25c1922c7f9ef81bb88e0f544de6

*2018-4-17 update Ubuntu 16.04.4 with linux kernel 4.4.89
::image name:2018-04-17-ubuntu-16.04-mate-desktop-demo3-k4.4.89-vdpau-3-mic-docker-bpi-r18-avs-aarch64-sd-emmc.img.zip
::Google Drive: https://drive.google.com/open?id=1dlfo9LGNcrc-_cpKd1uJnrNx0PdonBnK
::MD5: 4b7e163d260e58a39ba8905e7ed39943
::Forum pthread:http://forum.banana-pi.org/t/bpi-r18-avs-new-image-ubuntu-16-04-4-with-linux-kernel-4-4-89-2018-4-17/5435

*2018-09-18 This release is for banana pi M64 board which is based on Allwinner A64, We release three Images, Ubuntu 16.04 Desktop & Android is based on kernel 3.10.
::Features Map ：http://wiki.banana-pi.org/M64_Image_Map#Ubuntu_Desktop_16.04
::Google Drive :
::Baidu Drive : https://pan.baidu.com/s/1wANJ4SwfNwKtBcd02WcbWA
::forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-release-2018-09-18/6796

*2018-08-17 update Ubuntu 16.04 Server kernel 3.10.105
::Google Drive : https://drive.google.com/open?id=1K-B4u8jGcv17s3I9v-Pr0xv5u5txvfok
::Baidu Drive : https://pan.baidu.com/s/1HcrR8NsL9_1RwbZNa7uwmg
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-a64-new-image-android-8-1-ubuntu-release-2018-08-17/6531

*2017-08-14 update based on ubuntu 16.04.3 LTS Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive: https://drive.google.com/file/d/0B_YnvHgh2rwjN1h1U0xDYUxET00/view?usp=sharing
::baidu cloud: http://pan.baidu.com/s/1pLkbdTT
::MD5: ae34baa840874276858d936a7ca85c4f
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-14-ubuntu-16-04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc/3695

===Debian===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim64_bullseye_edge_5.19.7_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1UUbn24l3q_OsVP4XWT6eVQN531tHPzX0/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1vFR9sUR0FhWgS1pemk9lTg?pwd=ina6 (pincode: ina6)

*2018-11-2 update , This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Debian 9.5 AARCH64 is based on kernel 3.10 & kernel 4.4.

::M64 Debian 9.5 AARCH64 Kernel 3.10
::::Features Map : * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google driver : https://drive.google.com/file/d/10qGv2gVrSgwXMBLDsCF0nQFc9EJnnkeS/view
::::Baidu Drive : https://pan.baidu.com/s/1DJd7CGAT0NiijKfOBq9J4Q
::::md5sum : 71fe25c1922c7f9ef81bb88e0f544de6

::M64 Debian 9.5 AARCH64 Kernel 4.4
::::Features Map: * http://wiki.banana-pi.org/M64_Image_Map#Debian_9.5_AARCH64
::::Google Drive : https://drive.google.com/file/d/17fh3YY6cwOzHMsqwnRQRTu9cXjKU4_tV/view
::::Baidu Drive : https://pan.baidu.com/s/1sOR6WFz2U9MT0ltq6zYnJA
::::md5sum : f3c2391b0232178018fda7ebfd64b14c
::forum pthread:http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-debian-9-5-aarch64-release-2018-11-02/7166

*2017-08-13 debian 8.9 jessie Mate Desktop (64-bit),support BPI-M64 kernel 3.10.105
::Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjazlNRTRHei1NbmM/view?usp=sharing
::baidu cloud:http://pan.baidu.com/s/1eSeTQeA
::MD5: 9ddf067457ebaf193de63c5c7141446a
::Forum pthread:http://forum.banana-pi.org/t/bpi-m64-new-image-2017-08-13-debian-8-jessie-mate-desktop-preview-aarch64-bpi-m64-sd-emmc/3694

===Armbian===
*Armbian_23.02.0-trunk_Bananapim64_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapim64_jammy_edge_6.1.11_xfce_desktop.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m64-new-armbian-image/15161

*[https://www.armbian.com/bananapi-m64/ Armbian Image] is base on Linux Mainline kernel

=== Raspbian===

*2018-11-06 update : This release is for banana pi M64 board which is based on Allwinner A64, We release two Images, Raspbian 9.4 is based on kernel 3.10 & kernel 4.4.
::BPI-M64 Raspbian 9.4 Kernel 3.10
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Raspbian_9.4_AARCH64
::::Google Drive : https://drive.google.com/file/d/1qoKCVDgiuEj0IVEzuPgzuFLjFR9hTLH8/view
::::Baidu Drive : https://pan.baidu.com/s/1MlIzQRpjs_soBDXOKf8NAw
::::md5sum : e321c6dbb096a0348fceb9d4a0b6c210
::BPI-M64 Raspbian 9.4 Kernel 4.4
::::Features Map : http://wiki.banana-pi.org/M64_Image_Map#Kernel_4.4.89_4
::::Google Drive : https://drive.google.com/file/d/1WnsHKnbI_FWQVkHQmbCcJ3yJ38oWaHGy/view
::::Baidu Drive : https://pan.baidu.com/s/1Bu-xiqiYsnau_xZp8-QEkw
::::md5sum : 1d4f00680e6869e2c4e66e205e61d93d
::forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m64-new-images-raspbian-9-4-kernel-3-10-4-4-release-2018-11-06/7195

===Fedora Linux===
*BPI-M64 fedora image download(not support desktop): fedora 31 with grub (u-boot-2019.07 + kernel 5.3.0)
::https://drive.google.com/file/d/1dIr943Ke28lEtCDpy8cI3q1dBUtHymJP/view?usp=drivesdk
::https://drive.google.com/file/d/1F3nYOw9AiLLaz8be0umz_9nlnhDP3t0s/view?usp=drivesdk
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-fedora-31-with-grub-u-boot-2019-07-kernel-5-3-0/9938

===Manjaro===
*2019-01-15 update,BananaPi BPI-M64 Support Run Manjaro AArch64 System
::Baidu Drive: https://pan.baidu.com/s/18drwPBFKAzf4lFe6IPjaPA
::Google Drive: https://drive.google.com/open?id=1Lu8xw4sAVyiHJT4eYcolNTAIKG154gm6
::Bpi Ftp Server: https://dev.banana-pi.org.cn/Image/BPI-M64/Manjaro/
::md5sum : 8c9964fbd80836228c72fa205eb62f78
::username: manjaro/root
::password: bananapi
::Forum pthread:http://forum.banana-pi.org/t/bananapi-bpi-m64-new-image-manjaro-aarch64-system-2019-01-16/7696

===FreeBSD===

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

===Clonezilla===

*Clonezilla support arm64 (Banana Pi BPI-M64),Thanks to Steven Shiau (NCHC Free Software Labs in Taiwan) & https://clonezilla.org/ 1, this image just for test .
*image download:https://drive.google.com/file/d/15oj0RjoU1TPC-jOXJ2bfhLb3vAiMf7p2/view
*discuss on forum: http://forum.banana-pi.org/t/bpi-m64-new-image-clonezilla-support-arm64-on-bpi-m64/10789

===Others===
* others image ,you can download at forum ： http://forum.banana-pi.org/c/BPI-M64/M63image

==Win 10 IoT==

* 2017-1-13 updae Win10 IoT Core beta0.2
::baidu cloud :http://pan.baidu.com/s/1c2ce100

*Win10 IoT Core 10586 beta0.1
::download link : https://drive.google.com/open?id=0B_YnvHgh2rwjODJOSS1TdkRvcEk
::baidu link : http://pan.baidu.com/s/1dEQyGgD
::MD5: 1c09118cd45bf0c3b61d1846710a3649

*BPI-M64 win10 IoT: https://catalog.azureiotsolutions.com/details?title=Allwinner_Banana_Pi_BPI_M64&source=all-devices-page

=FAQ=
*1,How-to use ubuntu system to support lcd7**?
::1."vi /media/pi/BPI-BOOT/bananapi/bpi-m64/linux/lcd7/uEnv.txt"
::2.If you use HC070TG lcd7 screen, change "touch=gt9xxnew_ts" But if you use S070WV20 lcd7 screen, you don't need to change.
::3. "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m64/u-boot-with-dtb-bpi-m64-lcd7-8k.img.gz"
::4.reboot
::[[File:BPI-M64_LCD7.png]]
::For more operation details please see Wiki: http://wiki.banana-pi.org/Getting_Started_with_M64

Banana Pi BPI-M2+

2023-03-22T06:54:22Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M2%2B]]
=Introduction=

[[File:Banana_pi_BPI-M2+_2.jpg|thumb|Overview: Allwinner H3]]
[[File:Banana_pi_BPI-M2+_3.jpg|thumb|Overview: back]]
[[File:Bpi-m2-plus-02.JPG|thumb|Overview:3D design]]
[[File:BPI-M2+_case.jpg|thumb|[[Case]] BPI-M2+ Premium Aluminum Enclosure]]
[[File:Newwork_scu.JPG|thumb|BPI-4.0 OEM&ODM [[Successful case]] H3 for Network security information analysis instrument]]
[[File:NEW_eBlocker_Family_Shop_money_back.png|thumb|BPI-4.0 OEM&ODM [[Successful case]]:H3 for eBlocker VPN router]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design,same size and inerface as BPI-M2+]]

Banana PI BPI-M2+ is the open source hardware platform, use Alliwnner H3 (option H2+ chip and H5 chip ) chip on board. and mini size only 65mm*65mm,

PBI-M2 hardware: 1Ghz ARM7 quad-core processor, 1GB DDR3 SDRAM, 8G eMMC flash on board,and SDIO wifi&BT 4.0 moodule on board.Gigabit ethrnet.

[[File:Banana_Pi_BPI-M2+.jpg]]

BPI-M2+ series run Android,Debian linux,Ubuntu linux, Raspberry Pi image and others image. Banana PI,it can easily run with the game it support 1080P high definition video output and 4K support, the GPIO compatible with Raspberry Pi B+ .

Banana Pi BPI-M2+ not support sata port, so you need use USB for hardisk

==Key Features==

* Allwinner H3 Quad-core 1.2GHz Cortex-A7 (option H2+ H5).
* 1GB DDR3
* 8GB eMMC onboard
* HDMI out
* WiFi and BlueTooth onboard
* 10/100/1000Mbps Ethernet Port
* CSI camera interface

==Getting Start==
*[[Quick Start Banana pi SBC]]
*[[Getting Start with M2P]]

=Hardware=
==Hardware interface==

[[File:BPI-M2plus_800.jpg]]

==Hardware spec==

{| class="wikitable"
|-
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana Pi M2+(Plus)'''
!
|-
! CPU
| H3 Quad-core Cortex-A7 H.265/HEVC 4K
|-
! GPU
| Mali400MP2 GPU @600 MHz,Supports OpenGL ES 2.0
|-
! Memory
| 1GB DDR3 (shared with GPU)
|-
! Flash
| 8GB eMMC flash onboard
|-
! Network
| 10/100/1000 Ethernet
|-
! WIFI&BT
| SDIO AP6212 for Wifi &BT 4.0（option AP6181 AP6335）
|-
! Video Input
| A CSI input connector Camera:1 Supports 8-bit YUV422 CMOS sensor interface,2 Supports CCIR656 protocol for NTSC and PAL, 3 Supports SM pixel camera sensor, 4 Supports video capture solution up to 1080p@30fps
|-
! Video Outputs
| Supports HDMI output with HDCP, Supports HDMI CEC, Supports HDMI 30 function, Integrated CVBS, Supports simultaneous output of HDMI and CVBS
|-
! Audio Outputs
| HDMI
|-
! Power
| 5V/2A DC input can supply power, but USB OTG input don’t supply power
|-
! USB 2.0 ports
| two USB 2.0 HOST, one USB 2.0 OTG
|-
! GPIO
| 40 Pins Header,compatible with Raspberry Pi B+
|-
! LED
| Power led & Status led
|-
! IR
| IR input on board
|-
! OS
| Android, Ubuntu, Debian, Raspberry Pi Image
|}

==GPIO PIN define ==

Banana Pi BPI-M2+ (BPI-M2 Plus) has a 40-pin GPIO header that matches that of the Model Raspberry Pi 3. Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M2+'''
|-
| GPIO Pin Name || Default Function || Function2：GPIO || Function3
|-
| CON2-P01 || VCC-3V3 || ||
|-
| CON2-P02 || VCC-5V || ||
|-
| CON2-P03 || TWI0-SDA || PA12-EINT12 ||
|-
| CON2-P04 || VCC-5V || ||
|-
| CON2-P05 || TWI0-SCK || PA11-EINT11 ||
|-
| CON2-P06 || GND || ||
|-
| CON2-P07 || PWM1 || PA6-EINT6 ||
|-
| CON2-P08 || UART3-TX || PA13-EINT13 || SPI1-CS
|-
| CON2-P09 || GND || ||
|-
| CON2-P10 || UART3-RX || PA14-EINT14 || SPI1-CLK
|-
| CON2-P11 || UART2-RX || PA1-EINT1 ||
|-
| CON2-P12 || UART3-CTS || PA16-EINT16 || SPI1-MISO
|-
| CON2-P13 || UART2-TX || PA0-EINT0 ||
|-
| CON2-P14 || GND || ||
|-
| CON2-P15 || UART2-CTS || PA3-EINT3 ||
|-
| CON2-P16 || UART3-RTS || PA15-EINT15 || SPI1-MOSI
|-
| CON2-P17 || VCC-3V3 || ||
|-
| CON2-P18 || PC4 || PC4 ||
|-
| CON2-P19 || SPI0-MOSI || PC0 ||
|-
| CON2-P20 || GND || ||
|-
| CON2-P21 || SPI0-MISO || PC1 ||
|-
| CON2-P22 || UART2-RTS || PA2-EINT2 ||
|-
| CON2-P23 || SPI0-CLK || PC2 ||
|-
| CON2-P24 || SPI0-CS || PC3 ||
|-
| CON2-P25 || GND || ||
|-
| CON2-P26 || PC7 || PC7 ||
|-
| CON2-P27 || TWI1-SDA || PA19-EINT19 ||
|-
| CON2-P28 || TWI1-SCK || PA18-EINT18 ||
|-
| CON2-P29 || PA7-EINT7 || PA7-EINT7 ||
|-
| CON2-P30 || GND || ||
|-
| CON2-P31 ||PA8-EINT8 || PA8-EINT8 ||
|-
| CON2-P32 || PL2-S-EINT2 || PL2-S-EINT2 ||
|-
| CON2-P33 || PA9-EINT9 || PA9-EINT9 ||
|-
| CON2-P34 || GND || ||
|-
| CON2-P35 || PA10-EINT10 || PA10-EINT10 ||
|-
| CON2-P36 || PL4-S-EINT4 || PL4-S-EINT4 ||
|-
| CON2-P37 || PA17-EINT17 || PA17-EINT17 || SPDIF-OUT
|-
| CON2-P38 || PA21-EINT21 || PA21-EINT21 ||
|-
| CON2-P39 || GND || ||
|-
| CON2-P40 || PA20-EINT20 || PA20-EINT20 ||
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 24-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CSI″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI Camera PIN of Banana pi BPI-M2+'''
|-
| CSI Pin Name || Default Function || Function2：GPIO
|-
| CN3-P01 || NC ||
|-
| CN3-P02 || GND ||
|-
| CN3-P03 || CSI0-SDA || PE13
|-
| CN3-P04 || CSI0-AVDD ||
|-
| CN3-P05 || CSI0-SCK || PE12
|-
| CN3-P06 || CSI0-Reset || PE14
|-
| CN3-P07 || CSI0-VSYNC || PE3
|-
| CN3-P08 || CSI0-PWDN || PE15
|-
| CN3-P09 || CSI0-HSYNC || PE2
|-
| CN3-P10 || CSI0-DVDD ||
|-
| CN3-P11 || CSI0-DOVDD ||
|-
| CN3-P12 || CSI0-D7 || PE11
|-
| CN3-P13 || CSI0-MCLK || PE1
|-
| CN3-P14 || CSI0-D6 || PE10
|-
| CN3-P15 || GND ||
|-
| CN3-P16 || CSI0-D5 || PE9
|-
| CN3-P17 || CSI0-PCLK || PE0
|-
| CN3-P18 || CSI0-D4 || PE8
|-
| CN3-P19 || CSI0-D0 || PE4
|-
| CN3-P20 || CSI0-D3 || PE7
|-
| CN3-P21 || CSI0-D1 || PE5
|-
| CN3-P22 || CSI0-D2 || PE6
|-
| CN3-P23 || GND ||
|-
| CN3-P24 || CSI0-DOVDD ||
|-
|}

'''UART specification:'''

The jumper CON3 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart PIN of Banana pi BPI-M2+'''
|-
| CON3 Pin Name || Default Function || GPIO
|-
| CON3 P03 || UART0-TXD || PA4
|-
| CON3 P02 || UART0-RXD || PA5
|-
| CON3 P01 || GND ||
|-
|}

==Hardware V1.2 Version ==

BPI-M2+ V1.2 hardware version add PMU Voltage regulation design

How to check BPI-M2+ V1.2 hardware version:

[[File:V1.2_hardware_2.jpg]]

BPi-M2+ V1.2 modification
*1,PL0 Instead the drop-down 10K，As a hardware version identification（V1.1 is pull up）
*2,PL1 Change to voltage regulation GPIO
[[File:V1.2_hardware_3.png]]

voltage regulation schematic diagram:

[[File:V1.2_hardware_4.png]]

=Software=

=Development=

==Basic Development==
[[OpenCV 3.4x on BananaPi]]

=Resources=

== source code==
*linux kernel 4.4 on github :https://github.com/BPI-SINOVOIP/BPI-M2P-bsp-4.4
*Linux kernel 3.4 on bithub:https://github.com/BPI-SINOVOIP/BPI-M2P-bsp

== documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
*How To Change The Boot Logo：http://forum.banana-pi.org/t/how-to-change-the-boot-logo/7660
*BPI-M2+ V1.2 schematic diagram
::google drive: [https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
::baidu cloud : https://pan.baidu.com/s/1vjBURLzFF2LYCe8CBcs9Mg
* BPI-M2+ V1.1 schematic diagram: https://drive.google.com/file/d/0B4PAo2nW2KfnMW5sVkxWSW9qa28/view?usp=sharing
* DXF file google download link :[https://drive.google.com/file/d/0B4PAo2nW2KfnaDRVLUpvV3hIVUk/view?usp=sharing BPI-M2+ DXF file]
* 3D design file google download link: [https://drive.google.com/file/d/0B4PAo2nW2KfnVV8zaDhYazRvOU0/view?usp=sharing BPI-M2+ 3D design]
* BPI-M2+ BT Lab test :[https://bananapi.gitbooks.io/bpi-m2-/content/en/bpi-m2+bt40testreport.html BPI-M2+ BT Lab test report]
* BPI-M2+ WIFI Lab test :[https://bananapi.gitbooks.io/bpi-m2-/content/en/bpi-m2+wifilabtest.html BPI-M2+ WIFI Lab test report]
* Validation test :[https://bananapi.gitbooks.io/bpi-m2-/content/en/bpi-m2+validationtestreport.html BPI-M2+ validation test report]
* CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m2-/content/en/bpim2+cefccrohscertification.html BPI-M2+ CE,FCC,RoHS ]
* Allwinner documents:
** allwinner H3 chip doc baidu link: https://pan.baidu.com/s/1qTULll2CR02d0Hw9itq1rw
** Allwinner H2+ chip doc baidu link: https://pan.baidu.com/s/1TGMYr3rhizfhlg5hl6hLyg
*Banana Pi M2 Plus - Unboxing e apresentação da placa.: https://www.youtube.com/watch?v=_87uHfyMIUA&feature=youtu.be
*Sinovoip Banana Pi M2+ - linux-sunxi.org wiki : http://linux-sunxi.org/Sinovoip_Banana_Pi_M2%2B

=Image Release=

==Android==
===Android 7.0===
2018-10-20 android 7.0 share by https://www.facebook.com/vitor1104
*image download link : http://setordigital.blogspot.com/2018/10/android-70-nougat-para-banana-pi-m2.html
::how to install : http://setordigital.blogspot.com/2017/01/como-instalar-o-android-no-orange-pi.html
::Forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m2-new-image-android-7-0-nougat-2018-10-20/7082

2018-06-30 update HDMI-Version
* Image Link:
:: Google Drive : https://drive.google.com/file/d/1TY4CgFxCT3pR6S2nw5w-_XkNsW9fPBhI
:: Baidu Drive : https://pan.baidu.com/s/1ETpbauIezp1228n7kdWo4A
:: Forum thread: http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-image-android7-0-release-2018-6-30/6147
:: How to Google registration: https://www.google.com/android/uncertified/ Android7.0 needs to register devices by youself

===Android 4.4 ===
* Image Link:
:: Google Drive: https://drive.google.com/open?id=0B_YnvHgh2rwjOWg4ZzBnR0VieFU
:: Baidu Drive: https://pan.baidu.com/s/1gfr7vJ9
::Forum thread: http://forum.banana-pi.org/t/bpi-m2-new-image-android-4-4-version-v3/2765

===H3Droid android===

*H3Droid 1.3.5 version image download: https://h3droid.com/download
::forum pthread:http://forum.banana-pi.org/t/h3droid-android-development-on-allwinner-h3-chip-project/3459/14

==Linux==
*2020-04-23 update, Ubuntu 16.04 Mate Desktop, Ubuntu 16.04 Server, Debian 9 and Raspbian Stretch images, base on kernel 4.4
::google drive :https://drive.google.com/drive/folders/0B_YnvHgh2rwjNExjUmlRNXdVNUE
::baidu cloud: https://pan.baidu.com/s/1Tay4F7nJJV1MzI_aO4NjHw pincode：ih9p

===Ubuntu===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim2zero_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1-BXzCnnXr9NvOsfBr646ZGOicQ7Kv9-o/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/19xg6YfySrUR6jclXYrzdOg?pwd=qfys (pincode: qfys)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google drive: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2018-5-17 update : Ubuntu 16.04 V1.1 new eMMC and PMU support, base on kernel 3.4
::Image Link:
::::Google Drive: https://drive.google.com/file/d/1YOiOksFTYwCj0Ow11fiGkb74yEsPpbHJ/view
::::baidu cloud : https://pan.baidu.com/s/1Jf-AZF6a4jZugqqx2QXH3Q
::Source Code Github Repo: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp
::Forum thread:
:::: http://forum.banana-pi.org/t/banana-pi-bpi-m2p-new-image-release-ubuntu-16-04-v1-1/5719

*2017-07-14 update : ubuntu-16.04-mate-desktop, base on kernel 3.4
::Image Link:
::::Google Drive: Google Drive: https://drive.google.com/open?id=1dlfo9LGNcrc-_cpKd1uJnrNx0PdonBnK
::::baidu cloud : http://pan.baidu.com/s/1dEX2TDR
::Source Code Github Repo: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp
:: Forum thread:
:::: http://forum.banana-pi.org/t/bpi-m2-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m2p-sd-emmc-2017-07-14/3572

*2018-11-09 update ,This release is for banana pi M2P board which is based on Allwinner H3, We release three images, Ubuntu 16.04, Raspbian 9 and Debian 9, base on kernel 4.4.
::M2P Ubuntu 16.04
::Features Map:http://wiki.banana-pi.org/M2P-H3_Image_Map#Kernel_4.4.55
::Google Drive : https://drive.google.com/file/d/1dgrtVqbR4I6xYlSfWBJeGwh8xI79L1PD/view?usp=sharing
::Baidu Drive : https://pan.baidu.com/s/1RHZ-b7PcY9ybeiy95C_VIg
::md5sum : 59f2cc29ce045c15e51fac20ff6924aa
::forum pthread: http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-demo-images-release-with-kernel-4-4-2018-11-09/7210

*2018-01-02 update : Ubuntu image, base on Kernel 4.4
::image Link: https://mega.nz/#!haRDBJLC!vE9r-b34WhkPGXt69DJjPdQ65ONuCsuM9RCjnvCUE1s
::Forum thread:
:::: http://forum.banana-pi.org/t/bpi-m2-new-image-bpi-m2-kernel-4-4-55/4577

=== Armbian image ===

*Armbian_23.02.0-trunk_Bananapim2plus_bullseye_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapim2plus_bullseye_edge_6.0.10_xfce_desktop.img.xz
*Armbian_23.02.0-trunk_Bananapim2plus_jammy_edge_6.1.11_xfce_desktop.img.xz
::https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m2-plus-new-armbian-image/15160

*2022-12-06 Armbian_22.11.0-trunk_Bananapim2plus_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1xnyen2FlP3b5kpIC8C70fIT2RUPaeQxo/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/11z-4c1Gj74D7hrT7R-_xhg?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m2-plus-new-image-release-armbian-bullseye/14449

*Armbain have support BPI-M2+，Armbian Bionic and Armbian Stretch version
::image download ： https://www.armbian.com/banana-pi-m2-plus/

* Armbian 5.51 debin Bananapi-m2+ build by BPI 2018-07-12
::google download : https://drive.google.com/open?id=1H_KEVWTRwgSgal5gt8jKqBT-y4IqIX84
::baidu download : https://pan.baidu.com/s/1OaBRKHPGqjgat0mntHyYxg
::discuss on forum : http://forum.banana-pi.org/t/bpi-m2-new-image-2018-07-12-armbian-5-51-debin-bananapi-m2-build-by-bpi-2018-07-12/6265

*Armbian Xenial and Armbian Jessie
::armbin image download: https://www.armbian.com/banana-pi-m2-plus/

=== Openelec Kodi ===
*Openelec Kodi 16.0 (xbmc)
::file name:http:OpenELEC-H3.arm-7.0-devel-20161026220508-r23113-g64b34b3-bpim2p.img.gz
::download link: http://down.nu/images/2016-10-26
::baidu cloud:http://pan.baidu.com/s/1mhMTEnI
::forum pthread:http://forum.banana-pi.org/t/openelec-kodi-16-0-xbmc-on-the-banana-pi-bpi-m2-project/1600

===Debian linux===

*2022-09-07 Armbian_22.11.0-trunk_Bananapim2plus_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/17j0YW8SJKpOG2YKRCuGLKXYHuq1wLSAh/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1prE9mlVuErHidWNJFynKzA?pwd=8ikd (pincode: 8ikd)

*2019-09-18 update,Banana Pi BPI-M2+ boot debian 10 with grub (u-boot-2019.07 + kernel 5.1.1)
::google drive: https://drive.google.com/file/d/1ZQx732W8u83LECsFqCT9DtEPiQati-z6/view?usp=sharing
::
*2018-11-09 update ,This release is for banana pi M2P board which is based on Allwinner H3, We release three images, Ubuntu 16.04, Raspbian 9 and Debian 9 with kernel 4.4.
::M2P Debian 9 Features Map :http://wiki.banana-pi.org/M2P-H3_Image_Map#Kernel_4.4.55_2
::Google Drive : https://drive.google.com/file/d/13HTp2smKPPK_4byHCI_T3Atg8_NfyQ5S/view?usp=sharing
::Baidu Drive : https://pan.baidu.com/s/1h3TSAzY8ootahOjxkoTG1Q
::md5sum : f979f1a68d759e804e0a90654f4577f1
::forum pthread :http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-demo-images-release-with-kernel-4-4-2018-11-09/7210

=== Raspbian ===
*2018-11-09 update ,This release is for banana pi M2P board which is based on Allwinner H3, We release three images, Ubuntu 16.04, Raspbian 9 and Debian 9 with kernel 4.4.
::M2P Raspbian 9 Features Map:http://wiki.banana-pi.org/M2P-H3_Image_Map#Kernel_4.4.55_3 1
::Google Drive :https://drive.google.com/open?id=182a1iSYyW8UMJHOyzbu35RfLi-Wn5H8h
::Baidu Drive : https://pan.baidu.com/s/1g5Suk-Ybd3jdhdX82llBwg
::md5sum : 53ec3986ec3df84fa2548d0742f700fa
::fourm pthread ：http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-demo-images-release-with-kernel-4-4-2018-11-09/7210

*2018-5-22 update : Raspbian jessie 8.0 kernel 3.4
::Image Link:
::::Google Drive: https://drive.google.com/open?id=1-jQNZrJQi_KajZre6c6mbt5bHilF0h1x
::::baidu cloud :https://pan.baidu.com/s/16KJbtwjT_PBCZJkYV79_ag
::Source Code Github Repo: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp
::Forum thread:
::http://forum.banana-pi.org/t/banana-pi-bpi-m2p-new-image-release-raspbian-jessie-8-0-2018-5-22/5788

* 2018-5-22 update : Raspbian 8.0 V1.1 new eMMC and PMU
::Image Link:
::::Google Drive: https://drive.google.com/open?id=1-jQNZrJQi_KajZre6c6mbt5bHilF0h1x
::::baidu cloud : https://pan.baidu.com/s/16KJbtwjT_PBCZJkYV79_ag
::Forum thread:
:::: http://forum.banana-pi.org/t/banana-pi-bpi-m2p-new-image-release-raspbian-jessie-8-0-2018-5-22/5788

===OpenSUSE===
*OpenSUSE have official support Banana Pi BPI-M2+
[[File:Opensuse_m2+.png]]
::image download : http://download.opensuse.org/ports/armv7hl/factory/images/

===FreeBSD===

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

===Lakka TV===
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

===Dietpi ===
*Dietpi have official support BPI-M2+ : http://forum.banana-pi.org/t/dietpi-have-official-support-bpi-m2/1882

===RetroPie===
*RetroPie for Banana Pi BPI-M2+/M2 Zero v.1.2.1 beta
::image download link: http://www.nintendont.it/download/nintendont-retropie-banana-pi-m2-plus-v-1-1-0-beta/
::forum pthread : http://forum.banana-pi.org/t/bpi-m2-zero-new-image-retropie-for-banana-pi-m2-zero-v-1-2-1-beta/4889

===retrorangepi===

* retrorangepi support BPI-M2+ BPI-M2 Zero : http://retrorangepi.download/download/index2.html

==Others image==

BPI-M2+ also support other image. such as Centos Kali,Gentoo .... please choose the newset image .

*others image download link : http://forum.banana-pi.org/c/Banana-pi-BPI-M2/M2image

=FAQ=

Banana Pi BPI-M2+

2023-03-22T06:54:01Z

Czj: /* Armbian image */

Banana Pi BPI-M1+

2023-03-22T06:51:11Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1%2B]]
=Introduction=

[[File:Banana_pi_BPI-M1+_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1+_2.jpg|thumb|Overview]]
[[File:BPI-M1+_3d.jpg|thumb|BPI-M1+ 3D]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]
[[File:BPI-M1+_case.jpg|thumb|BPI-M1+ case]]

Banana Pi BPI-M1+ upgrade is an open-source single-board computer that adds more connectivity to the classic board. It features the same high performance AllWinner A20 dual-core SoC at 1GHz, 1GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections found in classic BPI-M1+ ; but the Banana Pi M1+ features onboard WiFi g/b/n. The board supports all classic projects and even more because of the onboard WIFi chip. Like its sibling, it can run operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

[[File:A_BPI-M1+.jpg]]

The Banana Pi M1+ is our upgraded M1 board. We feel like the onboard WiFi adds a lot more features to the board and makes it more convient for users to set up their linx desktop or router projects.
Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. With a Banana Pi, we want you to explore and experience the world of DIY projects and portable computing. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* Wifi support onboard
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 40 PIN gpio
* 3.7V lithium battery interface

==Get startting ==
*How to burn image : [[Quick Start Banana pi SBC]]
*How to development : [[Getting Started with M1P]]

==Hardware==

===Hardware interface===
[[File:BPI-M1_plus_interface.jpg]]

===Hardware spec===
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1+'''
|-
|-
| CPU
| A20 ARM Cortex -A7 Dual-Core
|-
| GPU
| ARM Mali400MP2Complies with OpenGL ES 2.0/1.1
|-
| Memory
| 1GB DDR3
|-
| Network
| 10/100/1000 Ethernet
|-
| wifi&BT
| Wifi support onboard
|-
| Video Input
| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs
| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs
| 3.5mm jack and HDMI
|-
| Power Source
| 5V/2A via Micro USB (DC in only) and / or Micro USB OTG
|-
| USB 2.0 ports
| 2(direct from Allwinner A20 chip)
|-
| GPIO
| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED
| Power Key & 8P8C
|-
| Storage
| SATA 2.0
|-
| OS
| Android 4.4, Android 4.2, Raspbian, Lubuntu, Open Suse, Debian
|}

===GPIO PIN define ===

Banana Pi BPI-M1+ has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:Gpio define.png]]

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1+'''
|-
|GPIO Pin Name || Default Function || Function2：GPIO
|-
| CON3-P01 || VCC-3V3 ||
|-
| CON3-P02 || VCC-DC ||
|-
| CON3-P03 || TWI2-SDA || PB21
|-
| CON3-P04 || VCC-DC ||
|-
| CON3-P05 || TWI2-SCK || PB20
|-
| CON3-P06 || GND ||
|-
| CON3-P07 || PWM1 || PI3
|-
| CON3-P08 || UART3\_TX ||PH0
|-
| CON3-P09 || GND ||
|-
| CON3-P10 || UART3\_RX || PH1
|-
| CON3-P11 || UART2\_RX || PI19
|-
| CON3-P12 || PH2 || PH2
|-
| CON3-P13 || UART2\_TX || PI18
|-
| CON3-P14 || GND ||
|-
| CON3-P15 || UART2\_CTS || PI17
|-
| CON3-P16 || CAN\_TX || PH20
|-
| CON3-P17 || VCC-3V3 ||
|-
| CON3-P18 || CAN\_RX || PH21
|-
| CON3-P19 || SPI0\_MOSI || PI12
|-
| CON3-P20 || GND ||
|-
| CON3-P21 || SPI0\_MISO || PI13
|-
| CON3-P22 || UART2\_RTS || PI16
|-
| CON3-P23 || SPI0\_CLK || PI11
|-
| CON3-P24 || SPI0\_CS0 || PI10
|-
| CON3-P25 || GND ||
|-
| CON3-P26 || SPI0\_CS1 || PI14
|-
| CON3-P27 || TWI3-SDA || PI1
|-
| CON3-P28 || TWI3-SCK || PI0
|-
| CON3-P29 || I2S\_MCLK || PB5
|-
| CON3-P30 || GND ||
|-
| CON3-P31 || I2S\_BCLK || PB6
|-
| CON3-P32 || I2S\_DI || PB12
|-
| CON3-P33 || I2S\_LRCK || PB7
|-
| CON3-P34 || GND ||
|-
| CON3-P35 || I2S\_DO0 || PB8
|-
| CON3-P36 || UART7\_RX || PI21
|-
| CON3-P37 || IR0\_TX || PB3
|-
| CON3-P38 || UART7\_TX || PI20
|-
| CON3-P39 || GND ||
|-
| CON3-P40 || SPDIF\_DO || PB13
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings.The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI PIN of Banana pi BPI-M1+'''
|-
| CSI Pin Name || Default Function Pin name || Function2：GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || AP-RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well.The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS PIN of Banana pi BPI-M1+'''
|-
| LVDS Pin || Default Function || Function2 || Function3：GPIO
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9 |
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 ||LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 || LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11header CON4 is the UART interface.For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''UART debug PIN of Banana pi BPI-M1+'''
|-
| Pin Name || Default Function || GPIO
|-
| CON4 P03 || UART0-TXD || PB22
|-
| CON4 P02 || UART0-RXD || PB23
|-
| CON4 P01 ||GND ||
|-
|}

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==

* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram: [https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google drive]
* BPI-M1+ DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1+ 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=
==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapim1plus_jammy_edge_6.1.11_xfce_desktop.img.xz,This release is for banana pi M1 Plus board, which is based on Armbian operation system.
jammy edge version with 6.1.11 kernel.
::Baidu Drive: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum : https://forum.banana-pi.org/t/banana-pi-bpi-m1-plus-new-armbian-image/15158

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1+ bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1AMEfQIygT8949sfkX6HIjap7WKpQox4i/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/1ePzBiwN0wEd8j3muk1HOlA?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14447/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/banana-pi-plus/

==Ubuntu linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1hlPkFx-NhGoCxYlHCqe4q9LwuQ0GosQL/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1SOeRKjVmTqTb6rMD71SfAw?pwd=wbnt (pincode: wbnt)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_bullseye_edge_5.19.6_xfce_desktop
::Google Drive:https://drive.google.com/file/d/1XpumxbOR74FSLayoICh4ZN4G3uZ_o0Fo/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1JtqdKE4AsAwCc6i_Wys_VA?pwd=6kgc (pincode: 6kgc)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google driver:https://drive.google.com/file/d/1FhbaO6pDBu5jSPYq1ghd7YKG-KvFy33Q/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

==OpenWRT==
===Officeal OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/gentoolinux.html

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M3

2023-03-22T06:50:50Z

Czj: /* Armbian */

[[zh:香蕉派_BPI-M3]]
=Introduction=

[[File:Banana_pi_BPI-M3_1.jpg|thumb|Overview: Allwinner A83T]]
[[File:Banana_pi_BPI-M3_5.jpg|thumb|Overview: front]]
[[File:3.7V.jpg|thumb|Overview: back]]
[[File:Banana_Pi_BPI-M2U_case_1.jpg|thumb|BPI-M3 Premium Aluminum Enclosure]]
[[File:Bpi-m2_ultar_case_1.jpg|thumb|BPI-M3 acrylic case]]
[[File:A83T.JPG|thumb|BPI 4.0 OEM&ODM server [[Successful case]] : A83T Raid Nas design]]
[[File:Magic_mirror_2.JPG|thumb|BPI 4.0 OEM&ODM server [[Successful case]] : A83T Magic Mirror]]

Banana Pi M3 is a super charged single board computer with an Octa-core processor and 2GB of RAM. Along side the elite processing unit, it features Gigabit Ethernet, 2 USB, SATA, WiFi, Bluetooth, and HDMI connection. It can run on a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

Being a brother of the power hungry M2, the M3 does not want to rest while his brother goes to acquire two more cores. The M3 secretly mastered the powerful art of Octa-core to best even the M2. Unlike his careless brother, the M3 did not lose his SATA port.

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

[[File:BPI-M3_960x360.jpg]]

==Key Features==

* Allwinner A83T Octa-core 1.8GHz Powerful CPU.
* 2 GB LPDDR3 memory.
* 8 GB eMMC storage.
* HDMI out
* IR control
* WiFi & Bluetooth onboard.
* MIPI DSI ingerface
* CSI camera interface

==Getting Start==
*How to burn image to BPI-M3 and begin [[Quick Start Banana pi SBC]]
*How to development [[Getting Start with M3]]

=Hardware=
==Hardware interface==
[[File:M3-hdw-label.jpg]]

==Hardware spec==
{| class="wikitable"
|-
!
! Banana Pi BPI-M3
|-
! CPU
| Allwinner A83T ARM Cortex-A7 Octa-Core 1.8 GHz, 512KB L1 cache and 1MB L2 cache
|-
! GPU
| PowerVR SGX544MP1 Comply with OpenGL ES 2.0 OpenCL 1x, DX9_3
|-
! Memory
| 2 GB LPDDR3 (shared with GPU)
|-
! Storage
| On Board 8GB eMMC Flash, Micro SD-Card slot, SATA 2.0 Port (USB-to-SATA bridge)
|-
! Network
| 10/100/1000 Mbit/s Ethernet (Realtek RTL8211E/D) + Wi-Fi 802.11 b/g/n (AP6212) + Bluetooth BT4.0
|-
! Video Input(s)
| A CSI input connector allows for the connection of a designed camera module
|-
! Video Output(s)
| HDMI 1.4 (Type A Full), MIPI Display Serial Interface (DSI) for raw LCD Panel
|-
! Audio Input(s)
| On board microphone
|-
! Audio Output(s)
| 3.5mm jack and HDMI
|-
! USB ports
| USB 2.0 PORT (x2), USB OTG (x1)
|-
! Remote
| IR Receiver (x1)
|-
! GPIO
| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). Some of I/O Pin can be used for specific functions as UART, I2C, SPI or PWM
|-
! Switches
| Reset, Power and U-boot
|-
! LED
| Power Status and 8P8C
|-
! Power Source
| 5 volt @2A via DC Power and/or Micro USB (OTG)
|-
! Size & Weight
| 92x60mm, 48g
|-
! OS
| Android and Linux
|}

==GPIO PIN define ==

Banana Pi BPI-M3 has a 40-pin GPIO header that matches that of the Model Raspberry Pi 3. Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO define of Banana pi BPI-M3'''
|-
|GPIO Pin Name|| Default Function|| Function2：GPIO|| Function3
|-
|CON1-P01|| VCC-3V3 || ||
|-
|CON1-P02|| DCIN|| ||
|-
|CON1-P03|| TWI2-SDA|| PH5-EINT5||
|-
|CON1-P04|| DCIN|| ||　
|-
|CON1-P05|| TWI2-SCK|| PH4-EINT4||
|-
|CON1-P06|| GND|| ||
|-
|CON1-P07|| S-PWM|| PL10-S-EINT10||
|-
|CON1-P08|| UART2-TX|| PB0-EINT0||
|-
|CON1-P09|| GND|| ||
|-
|CON1-P10|| UART2-RX|| PB1-EINT1||
|-
|CON1-P11|| PC4 PC4|| ||
|-
|CON1-P12|| UART2-CTS|| PB3-EINT3||
|-
|CON1-P13|| PC7|| PC7 ||
|-
|CON1-P14|| GND || ||
|-
|CON1-P15|| PC17|| PC17||
|-
|CON1-P16|| UART2-RTS|| PB2-EINT2||
|-
|CON1-P17|| VCC-3V3 || ||
|-
|CON1-P18|| PL8-ENT8|| PL8-S-ENT8||
|-
|CON1-P19|| SPI0_MOSI|| PC0||
|-
|CON1-P20|| GND || ||
|-
|CON1-P21|| SPI0_MISO|| PC1 ||
|-
|CON1-P22|| PL9-EINT9|| PL9-S-EINT9 ||
|-
|CON1-P23|| SPI0_CLK|| PC2 ||
|-
|CON1-P24|| SPI0_CS|| PC3||
|-
|CON1-P25|| GND|| ||
|-
|CON1-P26|| PH10-ENT10|| PH10-ENT10||
|-
|CON1-P27|| TWI1-SDA|| PH3-EINT3||
|-
|CON1-P28|| TWI1-SCK|| PH2-EINT2||
|-
|CON1-P29|| PC18|| PC18||
|-
|CON1-P30|| GND|| ||
|-
|CON1-P31|| I2S1-BCLK|| PG10-EINT10|| UART3-TX
|-
|CON1-P32|| I2S1-DIN|| PG13-EINT13|| UART3-CTS
|-
|CON1-P33|| I2S1-LRCK|| PG11-EINT11|| UART3-RX
|-
|CON1-P34|| GND || ||
|-
|CON1-P35|| I2S1-DOUT|| PG12-EINT12|| UART3-RTS
|-
|CON1-P36|| PE5|| PE5 ||
|-
|CON1-P37|| PE4|| PE4 ||
|-
|CON1-P38|| OWA-DOUT|| PE18||
|-
|CON1-P39|| GND || ||
|-
|CON1-P40|| PE19|| PE19||
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI camera GPIO of Banana pi BPI-M3'''
|-
|CSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN7-P01|| IPSOUT ||
|-
|CN7-P02|| AFVCC ||
|-
|CN7-P03|| IPSOUT ||
|-
|CN7-P04|| IOVDD ||
|-
|CN7-P05|| GND||
|-
|CN7-P06|| GND ||
|-
|CN7-P07|| CSI2-D3N||
|-
|CN7-P08|| AVDD-CSI||
|-
|CN7-P09|| CSI2-D3P||
|-
|CN7-P10|| DVDD-CSI-R||
|-
|CN7-P11|| GND ||
|-
|CN7-P12|| NC ||
|-
|CN7-P13|| CSI2-D2N||
|-
|CN7-P14|| CSI-RST-R|| PE16
|-
|CN7-P15|| CSI2-D2P|| |
|-
|CN7-P16|| CSI-STBY-R|| PE17
|-
|CN7-P17|| GND||
|-
|CN7-P18|| CSI-PCLK|| PE0
|-
|CN7-P19|| CSI2-CKN||
|-
|CN7-P20|| CSI-MCLK|| PE1
|-
|CN7-P21|| CSI2-CKP||
|-
|CN7-P22|| CSI-HSYNC|| PE2
|-
|CN7-P23|| GND||
|-
|CN7-P24|| CSI-VSYNC|| PE3
|-
|CN7-P25|| CSI2-D1N||
|-
|CN7-P26|| CSI-D9|| PE13
|-
|CN7-P27|| CSI2-D1P||
|-
|CN7-P28|| CSI-D8|| PE12
|-
|CN7-P29|| GND ||
|-
|CN7-P30|| CSI-D7|| PE11
|-
|CN7-P31|| CSI2-D0N||
|-
|CN7-P32|| CSI-D6|| PE10
|-
|CN7-P33|| CSI2-D0P||
|-
|CN7-P34|| CSI-D5|| PE9
|-
|CN7-P35|| GND||
|-
|CN7-P36|| CSI-D4|| PE8
|-
|CN7-P37|| CSI-SCK|| PE14
|-
|CN7-P38|| CSI-D3|| PE7
|-
|CN7-P39|| CSI-SDA|| PE15
|-
|CN7-P40|| CSI-D2|| PE6
|-
|}

'''Display specification'''

MIPI DSI (Display Serial Interface)：

The display Connector is a 40-pin FPC connector which can connect external LCD panel (MIPI DSI) and touch screen (I2C) module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''MIPI DSI PIN define of Banana pi BPI-M3'''
|-
|DSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN6-P01|| VCC-MIPI||
|-
|CN6-P02|| IPSOUT||
|-
|CN6-P03|| VCC-MIPI||
|-
|CN6-P04|| IPSOUT||
|-
|CN6-P05|| GND ||
|-
|CN6-P06|| IPSOUT||
|-
|CN6-P07|| GND ||
|-
|CN6-P08|| IPSOUT||
|-
|CN6-P09|| NC||
|-
|CN6-P10|| GND ||
|-
|CN6-P11|| NC ||
|-
|CN6-P12|| DSI-D0N ||
|-
|CN6-P13|| NC||
|-
|CN6-P14|| DSI-D0P ||
|-
|CN6-P15|| NC ||
|-
|CN6-P16|| GND ||
|-
|CN6-P17|| TWI0-SDA|| PH1-EINT1
|-
|CN6-P18|| DSI-D1N||
|-
|CN6-P19|| TWI0-SCK|| PH0-EINT0
|-
|CN6-P20|| DSI-D1P ||
|-
|CN6-P21|| TP-INT|| PL7-S-EINT7
|-
|CN6-P22|| GND||
|-
|CN6-P23|| TP-RST|| PL6-S-EINT6
|-
|CN6-P24|| DSI-CKN ||
|-
|CN6-P25|| GND ||
|-
|CN6-P26|| DSI-CKP||
|-
|CN6-P27|| LCD-BL-EN|| PD29
|-
|CN6-P28|| GND ||
|-
|CN6-P29|| LCD-RST|| PD26
|-
|CN6-P30|| DSI-D2N ||
|-
|CN6-P31|| LCD-PWR-EN|| PD27
|-
|CN6-P32|| DSI-D2P||
|-
|CN6-P33|| GND ||
|-
|CN6-P34|| GND ||
|-
|CN6-P35|| LCD-PWM|| PD28
|-
|CN6-P36|| DSI-D3N ||
|-
|CN6-P37|| GND ||
|-
|CN6-P38|| DSI-D3P||
|-
|CN6-P39|| AP-RESET#||
|-
|CN6-P40|| GND |||
|-
|}

'''UART specification:'''

The header CON4 is the UART interface.For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart debug pin of Banana pi BPI-M3'''
|-
|CON2 Pin Name ||Default Function|| GPIO
|-
|CON2 P03|| UART0-TXD|| PB9
|-
|CON2 P02|| UART0-RXD|| PB10
|-
|CON2 P01|| GND||
|-
|}

=Software=
==Android==
*How to burn android image to eMMC under windows ： https://bananapi.gitbooks.io/bpi-m3/content/en/how_to_burn_android_image_to_emmc.html
*BPI-M3 How to control GPIO on Android ：https://bananapi.gitbooks.io/bpi-m3/content/en/howtocontrolgpioonandroid.html

==Linux==
*How to burn Linux image to eMMC : https://bananapi.gitbooks.io/bpi-m3/content/en/howtoburnlinuximagetoemmc.html
*GPU for kernel 3.4 : https://bananapi.gitbooks.io/bpi-m3/content/en/gpuforkernel34.html
*How to rotate display screen : https://bananapi.gitbooks.io/bpi-m3/content/en/howtorotatedisplayscreen.html
*how to use fatload uEnv.txt & script.bin & kernel uImage : https://bananapi.gitbooks.io/bpi-m3/content/en/howtousefatloaduenvtxtscriptbinkernel_ui.html

==Opnewrt==
==TinaLinux==

=Development=

==Basic Development==
*[https://bananapi.gitbooks.io/bpi-m3/content/en/howtosetupdockerenvtobuildgithubsourcecod.html How to setup docker env. to build github source code ]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/howtocompilebpi-m3-bspkernelonbpi-m3.html How to compile BPI-M3-bsp kernel on BPI-M3]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3crosscompileteach.html BPI-M3 BSP Cross Compile teach]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3fixrootmydeviceissueforsecurityalert.html BPI-M3 fix rootmydevice issue for Security Alert]

=Resources=
==Source code==
* BPI-M3 android 5.1 source code ： https://drive.google.com/open?id=0B\_YnvHgh2rwjaGhIeUE0eERTZU0
*BPI-M3 Linux BSP code : https://github.com/BPI-SINOVOIP/BPI-M3-bsp

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
*BPI-M3 schematic diagram :[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
*BPI-M3 DXF file : https://drive.google.com/file/d/0B4PAo2nW2KfnNm54VjBlUXhXekU/view
*BPI-M3 3D design file : https://drive.google.com/file/d/0B4PAo2nW2KfnYXVGWXBURDFSeTA/view
*A83T chip Datasheet V1.4 : https://drive.google.com/file/d/0B4PAo2nW2KfnM2VqeTR3SXpGdVE/view?usp=sharing
*Allwinner A83T chip User_Manual V1.5.1 : https://drive.google.com/file/d/0B4PAo2nW2KfnRjlQaU9uR0J0elE/view?usp=sharing
*android 5.0 development document（chinese）：https://drive.google.com/file/d/0B4PAo2nW2KfnekpvMnlNZ2p6NWs/view?usp=sharing
*allwinner chip online datasheet and documents : http://dl.linux-sunxi.org/
*linux-sunxi wiki : http://linux-sunxi.org/Banana_Pi_M3
*BPI-M3 quality guarantee
::BPI-M3 WIFI Lab test report : https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3wifilabtest.html
::BPI-M3 Validation test report : https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3validationtest.html
::BPI-M3 CE,FCC RoHS Certification : http://forum.banana-pi.org/t/bpi-m3-ce-fcc-rohs-certification/984

=Image Release=
==Android 5.1.1 V5==
*2018-06-05 update
*HDMI-Version
::Google Drive : https://drive.google.com/open?id=1mLXOAH_LPT-uqtwWvgvJXw4Vo95tFr_z
::Baidu Cloud : https://pan.baidu.com/s/1byqwqzz9SOIWHYfOabXKNw

*LCD-Version
::Google Drive : https://drive.google.com/open?id=1DAxQIws0eAVPAm0riH5HXc8M36SH_-sC
::Baidu Cloud : https://pan.baidu.com/s/19l7a6Z75FuZb_f9Ls0fN5w

*2017-05-11 update
*HDMI-Version
::Google Drive : https://drive.google.com/open?id=0B_YnvHgh2rwjcXkxczlmOWxWV00
::Baidu Cloud : https://pan.baidu.com/s/1pKF3Ggj
::MD5: d7b7abf3443a49fb0f178ccf2f6e82d0
*LCD-Version
::Google Drive : https://drive.google.com/open?id=0B_YnvHgh2rwjSkM5NHFWYVdlakk
::Baidu Cloud : https://pan.baidu.com/s/1mi2YOeG
::MD5: b27dd45ac5fd1fd3b02db8ffd92c2871
*forum pthread : http://forum.banana-pi.org/t/bpi-m3-new-image-android-5-1-version-v5-2017-05-11/3241

==Ubuntu==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim3_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1iq0gCOAIHjE7bgxeccNPtFp9iK0AtzRM/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1FjNBqpJ0Kv83EpiKt9sZmw?pwd=mtk5 (pincode: mtk5)

*2021-08-03 release, Ubuntu Mate Desktop 16.04 with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FUbuntu16.04%2F2021-08-03-ubuntu-16.04-mate-desktop-bpi-m3-sd-emmc.img.zip 2021-08-03-ubuntu-16.04-mate-desktop-bpi-m3-sd-emmc.img.zip]
::MD5: 4cd6cfb9ed3a2d382dbc32bb478ac149

*2021-08-03 release, Ubuntu Server 16.04 with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FUbuntu16.04%2F2021-08-03-ubuntu-16.04-server-bpi-m3-sd-emmc.img.zip 2021-08-03-ubuntu-16.04-server-bpi-m3-sd-emmc.img.zip]
::MD5: ea5abe3fd6988931df85a2376808501a

*2018-07-18 BPI-M3 Ubuntu 16.04 Mate Desktop (new eMMC)
::Features Map ：http://wiki.banana-pi.org/M3_Image_Map#Ubuntu_16.04
::Google Drive : https://drive.google.com/open?id=1DlOrt08yUY9hAETiUXBiyoyPFHrOxtvq
::Baidu Drive : https://pan.baidu.com/s/1ND5QqoBevzM2TykwqZCkAA
::forum pthread: http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

*2018-07-18 M3 Ubuntu Server (new eMMC)
::Features Map : http://wiki.banana-pi.org/M3_Image_Map#Ubuntu_Lite
::Google Drive : https://drive.google.com/open?id=1Yyd2BepHjyhgXhSmnFh_0Az6YoXPEI3J
::Baidu Drive : https://pan.baidu.com/s/10vSo0AmIiMrVLNPkQ63leQ
::forum pthread: http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

*2018-05-31 update ubuntu 16.04 mate desktop
**HDMI verison baidu cloud :　https://pan.baidu.com/s/1UDktbDgGtXpbqIZn_TI1Tg

*2017-07-13 update ubuntu 16.04 mate desktop
* Image Link:
**HDMI version Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjRThoaHliWVVyZGM/view?usp=sharing
**HDMI verison baidu cloud :　http://pan.baidu.com/s/1nu6hJs9
**Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-ov8865-sd-emmc-2017-07-13/3542
**LCD 7 verison Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjVldzUENFQXpiTHc/view?usp=sharing
**LCD 7 version baidu cloud :　http://pan.baidu.com/s/1o8Uc4Y2
**Forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-lcd7-ov8865-sd-emmc-img-2017-7-13/3543
**LCD 5 Version Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjUlpIVjB6LVVmMGc/view?usp=sharing
**LCD 5 Version baidu cloud : http://pan.baidu.com/s/1hsIJygG
** Forum thread:http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-lcd5-ov8865-sd-emmc-img-2017-7-13/3544

==Debian==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim3_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1vrM4WLq74O4FEOAmBjUwJGbzZptq3hYi/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1w00wkfX15G6D60W2WH52ug?pwd=awza (pincode: awza)

*2018-07-18 BPI-M3 Debian Jessie 9 (new eMMC)
::Features Map : http://wiki.banana-pi.org/M3_Image_Map#Debian_Jessie_9
::Google Drive : https://drive.google.com/open?id=1M997Uf-RVqdFKJkXMjgY0w3fHyiOq4iG
::Baidu Drive : https://pan.baidu.com/s/1yQYG1iOEIrJADV_j-qvdwQ
::Forum pthread : http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

==Armbian==
*Armbian_23.02.0-trunk_Bananapim3_focal_current_5.15.82_xfce_desktop.img
*Armbian_23.02.0-trunk_Bananapim3_jammy_edge_6.1.11_xfce_desktop.img
*Armbian_23.02.0-trunk_Bananapim3_bullseye_edge_6.1.0_xfce_desktop.img
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m3-new-armbian-image/15138

*2022-12-06 Armbian_22.11.0-trunk_Bananapim3_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1Cr0KY0oVqSly-DOipgd_x_a4gQ0oPxm7/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/18M5Tsc91z57NUzBm4rcqlg?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-release-armbian-bullseye/14450

*Armbian with 4.17.y for M3
::Test build:http://ix.io/1fUK
::Broken: wired, wireless network, Bluetooth, ...
::Works: serial console, 8 cores, DVFS, USB, SATA, HDMI, DRM video driver, ...
::image:https://forum.armbian.com/topic/474-banana-pi-m3/?do=findComment&comment=57400
::Forum pthread:http://forum.banana-pi.org/t/armbian-with-4-17-y-for-m3/6174

==Rasbian==
*2021-08-03 release, Raspbian Stretch with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FRaspbian%2F2021-08-03-raspbian-stretch-bpi-m3-sd-emmc.img.zip 2021-08-03-raspbian-stretch-bpi-m3-sd-emmc.img.zip]
::MD5: a9890cedbd779a29ff551a7fc5e1eae6

* 2018-5-28 update : Raspbian 8.0 V1.1
::Image Link:
::::Google Drive: https://drive.google.com/open?id=1DSZru8UQRikI6pImLZIt1DmySVozy0FA
::::baidu cloud : https://pan.baidu.com/s/1Pz_6btHxj6F9w_6aw90Dww
::Forum thread:
:::: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-release-raspbian-jessie-8-0-2018-5-28-v1-1/5847

==Arch Linux ==
*2018-08-19 ArchLinux-4.18.1-1-ARCH : Kernel: 4.18.1-1-ARCH U-Boot: 2018.09-rc1
::U-Boot: 2018.09-rc1,Kernel: 4.18.1-1-ARCH,Ethernet works,Wifi works,HDMI works,LCD needs to be checked(I would appreciate if someone can check it),GPIO works(WiringPi),BPI tools included,I2C enabled(In TDB file)
::source code on github : https://github.com/apankevych/BananaPi-M3-Linux-4.18.1-1-ARCH
::download Image link:https://drive.google.com/file/d/1ia3JSmHH8ksia4e8doalUGSBHnytOgx4/view?usp=sharing
::Forum pthread : http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-archlinux-4-18-1-1-arch-2018-08-19/6544

*2018-07-19 Arch Linux sunxi kernel-4.18-rc3 and uboot- 2018.01 thank Andriy_Pankevych do this great work.
:: Google drive : https://drive.google.com/open?id=1Ve91MG_7d1haawqqmiBo4qCugvF1iLyn
:: Source code: https://github.com/apankevych/BananaPi-M3-Linux-4.18.0-rc3
:: Forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-arch-linux-sunxi-kernel-4-18-rc3-and-uboot-2018-01-2018-07-19/6312

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/
https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-m3

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Others image==
*http://forum.banana-pi.org/c/bpi-m3/M2image

=FAQ=

Banana Pi BPI-M2 Berry

2023-03-22T06:50:34Z

Czj: /* Armbian */

[[zh:香蕉派_BPI-M2_Berry]]
=Introduction=

[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|Overview]]
[[File:Banana_pi_BPI-M2_Berry_4.jpg|thumb|Overview:front]]
[[File:Banana_pi_BPI-M2_Berry_3.JPG|thumb|Overview:back]]
[[File:R40_for_vehicle_license_plate_recognition.JPG|thumb|BPI-M2 Berry for BPI 4.0 [[Successful case]] ：R40 for vehicle license plate recognition ]]
[[File:R40_for_IoT_gateway.JPG|thumb|BPI-M2 Berry for BPI 4.0 [[Successful case]] ：R40 for IoT gateway with Z-wave, zigbee,WiFI]]
[[File:BPI-M2_Berry case.jpg|thumb|BPI-M2 Berry case]]
Banana Pi BPI-M2 Berry is a quad-core mini single board computer built with Allwinner A40i SoC. It features 1GB of RAM . It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 4 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, and last but not least, a SATA port..

[[File:Banana_Pi_BPI-M2_Berry.jpg]]

Also being a member of the Banana Pi family, the M2 Berry is a direct upgrade from the Banana Pi M1/M1+ that support SATA from the SoC. The SATA performance on the V40 is fitting for media related projects such as storage servers. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

all size is same as raspberry pi 3,so you can use raspberry pi 3 case for BPI-M2 Berry.

==Key Features==

* Allwinner A40i/R40/V40 Quad Core ARM Cortex A7 CPU
* 1GB DDR3 SDRAM.
* WiFi (AP6212) & Bluetooth onboard.
* SATA Interface.
* 4*USB 2.0
* MIPI DSI interface
* CSI camera interface

==Getting Start==
*[[Quick Start Banana pi SBC]]

*[[Getting Start with M2 Ultra / Berry]]

=Hardware=
==Hardware interface==
[[File:M2ubinterface.jpg]]

==Hardware spec==
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-M2 Berry'''
|-
|Soc || Allwinner A40i/R40/V40
|-
| CPU || quad-core cortex -A7,the most power efficient CPU core ARM's ever development
|-
| GPU || dual-core MALI-400 MP2 and runs at 500MHz, capable of 1.1 Gpixel/s throughput. Graphics capabilities are slightly higher than the original Xbox’s level of performance. The GPU provides OpenGL ES 2.0, hardware-accelerated OpenVG, 1080p45 H.264 high-profile encode and decode.
|-
| SDRAM || 1GB DDR3 with 733MHz$shared with GPU$
|-
| SATA || suppoort SATA interface
|-
| GPIO || 40 Pins Header, 28×GPIO, some of which can be used for specific functions including UART, I2C, SPI, PWM, I2S.
|-
| On board Network || 10/100/1000Mbps Ethernet $Realtek RTL8211E/D$
|-
| Wifi Module || WiFi 802.11 b/g/n $AP 6212 module on board$
|-
| Bluetooth || BT4.0
|-
| On board Storage || MicroSD $TF$ card,No eMMC onboard
|-
| Display || 4-lane MIPI DSI display,or RGB panel or LVDS panel,TV-out on HDMI V1.4
|-
| Video || Multi-format FHD video decoding, including Mpeg1/2, Mpeg4, H.263, H.264, etc H.264 decode up to 1080P60,support video encodeing:High-deinition$HD$H.264 video encoder is up to 1080P@45fps
|-
| Audio outputs || HDMI, analog audio $via 3.5 mm TRRS jack$, I2S audio $also potentially for audio input$
|-
| Camera || A CSI input connector Camera:Supports 8-bit YUV422 CMOS sensor interface,Supports CCIR656 protocol for NTSC and PAL,Supports 5M pixel camera sensor ,Supports video capture solution up to 1080p@30fps
|-
|-
| USB || 4 USB 2.0 host, 1 USB 2.0 OTG
|-
| Buttons || Reset button, Power button, U-boot button
|-
| Leds || Power status Led and RJ45 Led
|-
| IR || No onboard IR receiver
|-
| DC Power || 5V/2A with micro USB port
|-
| battery || No 3.7V lithium battery power support
|-
| Sizes || 85mmX56mm,same size as raspberry pi 3
|-
| Weight || 40g
|-
|}

==GPIO PIN define ==

Banana Pi BPI-M2 Berry has a 40-pin GPIO header that matches that of the Model Raspberry Pi 3. Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M2 Ultra'''
|-
|GPIO Pin Name || Default Function || Function2：GPIO || Function3
|-
| CON1-P01 || VCC-3V3 || ||
|-
| CON1-P02 || DCIN || ||
|-
| CON1-P03 || TWI2-SDA || PB21 || PWM5
|-
| CON1-P04 || DCIN || ||
|-
| CON1-P05 || TWI2-SCK || PB20 || PWM4
|-
| CON1-P06 || GND || ||
|-
| CON1-P07 || PB3 || PB3 || PWM1
|-
| CON1-P08 || UART2-TX || PI18 || SPI1\_MOSI
|-
| CON1-P09 || GND || ||
|-
| CON1-P10 || UART2-RX || PI19 || SPI1\_MISO
|-
| CON1-P11 || UART7-TX || PI20 || PWM2 |
|-
| CON1-P12 || UART2-CTS || PI17 || SPI1\_CLK
|-
| CON1-P13 || UART7-RX || PI21 || PWM3
|-
| CON1-P14 || GND || ||
|-
| CON1-P15 || PH25 || PH25 || CSI1-FIELD
|-
| CON1-P16 || UART2-RTS || PI16 || SPI1\_CS0
|-
| CON1-P17 || VCC-3V3 || ||
|-
| CON1-P18 || PH26 || PH26 || CSI1-HSYNC
|-
| CON1-P19 || SPI0\_MOSI || PC0 ||
|-
| CON1-P20 || GND || ||
|-
| CON1-P21 || SPI0\_MISO || PC1 ||
|-
| CON1-P22 || PH27 || PH27 || CSI1-VSYNC
|-
| CON1-P23 || SPI0\_CLK || PC2 ||
|-
| CON1-P24 || SPI0\_CS || PC23 ||
|-
| CON1-P25 || GND || ||
|-
| CON1-P26 || PH24 || PH24 || CSI1-PCLK
|-
| CON1-P27 || TWI3-SDA || PI1 ||
|-
| CON1-P28 || TWI3-SCK || PI0 ||
|-
| CON1-P29 || PH0 || PH0 || CSI1-D0
|-
| CON1-P30 || GND || ||
|-
| CON1-P31 || PH1 || PH1 || CSI1-D1
|-
| CON1-P32 || PD20 || PD20 || CSI1-MCLK
|-
| CON1-P33 || PH2 || PH2 || CSI1-D2
|-
| CON1-P34 || GND || ||
|-
| CON1-P35 || PH3 || PH3 || CSI1-D3
|-
| CON1-P36 || UART5-RX || PH7 || CSI1-D7
|-
| CON1-P37 || UART4-TX || PH4 || CSI1-D4
|-
| CON1-P38 || UART5-TX || PH6 || CSI1-D6
|-
| ON1-P39 || GND || ||
|-
| CON1-P40 || UART4-RX || PH5 || CSI1-D5
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 24-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “Camera”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSi Camera connector GPIO of Banana pi BPI-M2 Ultra'''
|-
| CSI Pin Name || Default Function || Function2：GPIO
|-
| CN5-P01 || NC ||
|-
| CN5-P02 || GND ||
|-
| CN5-P03 || CSI0-SDA || PI3
|-
| CN5-P04 || CSI0-AVDD ||
|-
| CN5-P05 || CSI0-SCK || PI2
|-
| CN5-P06 || CSI0-Reset || PI7
|-
| CN5-P07 || CSI0-VSYNC || PE3
|-
| CN5-P08 || CSI0-PWDN || PI6
|-
| CN5-P09 || CSI0-HSYNC || PE2
|-
| CN5-P10 || CSI0-DVDD ||
|-
| CN5-P11 || CSI0-DOVDD ||
|-
| CN5-P12 || CSI0-D7 || PE11
|-
| CN5-P13 || CSI0-MCLK || PE1
|-
| CN5-P14 || CSI0-D6 || PE10
|-
| CN5-P15 || GND ||
|-
| CN5-P16 || CSI0-D5 || PE9
|-
| CN5-P17 || CSI0-PCLK || PE0
|-
| CN5-P18 || CSI0-D4 || PE8
|-
| CN5-P19 || CSI0-D0 || PE4
|-
| CN5-P20 || CSI0-D3 || PE7
|-
| CN5-P21 || CSI0-D1 || PE5
|-
| CN5-P22 || CSI0-D2 || PE6
|-
| CN5-P23 || GND ||
|-
| CN5-P24 || CSI0-AFVCC ||
|-
|}

'''Display specification'''

MIPI DSI $Display Serial Interface$

The display Connector is a 40-pin FPC connector which can connect external LCD panel $MIPI DSI$ and touch screen $I2C$ module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M2 Ultra'''
|-
| DSI Pin Name || Default Function || Function2：GPIO
|-
| CN6-P01 || VCC-3V3 ||
|-
| CN6-P02 || IPSOUT ||
|-
| CN6-P03 || VCC-3V3 ||
|-
| CN6-P04 || IPSOUT ||
|-
| CN6-P05 || GND ||
|-
| CN6-P06 || IPSOUT ||
|-
| CN6-P07 || GND ||
|-
| CN6-P08 || IPSOUT ||
|-
| CN6-P09 || NC ||
|-
| CN6-P10 || GND ||
|-
| CN6-P11 || NC ||
|-
| CN6-P12 || DSI-D0N ||
|-
| CN6-P13 || NC ||
|-
| CN6-P14 || DSI-D0P ||
|-
| CN6-P15 || NC ||
|-
| CN6-P16 || GND ||
|-
| CN6-P17 || TWI0-SDA || PB19
|-
| CN6-P18 || DSI-D1N ||
|-
| CN6-P19 || TWI0-SCK || PB18
|-
| CN6-P20 || DSI-D1P ||
|-
| CN6-P21 || CTP-INT || PI10
|-
| CN6-P22 || GND ||
|-
| CN6-P23 || CTP-RST || PI11
|-
| CN6-P24 || DSI-CKN ||
|-
| CN6-P25 || GND ||
|-
| CN6-P26 || DSI-CKP ||
|-
| CN6-P27 || LCD-BL-EN || PH16
|-
| CN6-P28 || GND ||
|-
| CN6-P29 || LCD-RST || PH17
|-
| CN6-P30 || DSI-D2N ||
|-
| CN6-P31 || LCD-PWR-EN || PH18
|-
| CN6-P32 || DSI-D2P ||
|-
| CN6-P33 ||GND ||
|-
| CN6-P34 || GND ||
|-
| CN6-P35 || LCD-PWM || PB2
|-
| CN6-P36 || DSI-D3N ||
|-
| CN6-P37 || GND ||
|-
| CN6-P38 || DSI-D3P ||
|-
| CN6-P39 || NC ||
|-
| CN6-P40 || GND ||
|-
|}

'''UART specification:'''

The header CON4 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CON4 Uart GPIO of Banana pi BPI-M2 Ultra'''
|-
| CON2 Pin Name || Default Function || GPIO
|-
| CON2 P03 || UART0-TXD ||
|-
| CON2 P02 || UART0-RXD||
|-
| CON2 P01 || GND||
|-
|}

=Software=

==TinaLinux==
Allwinner Tina-IoT os for BPI-M2 Ultra/BPI-M2 Berry

=Development=

==Basic Development==

=Resources=
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* Schematics:[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
* Dimensional diagram [https://drive.google.com/file/d/0B4PAo2nW2Kfnci1xaHd5eWtseEU/view?usp=sharing BPI-M2 Berry dxf file]
* Allwinner R40/V40 datasheet
::[https://drive.google.com/file/d/0B4PAo2nW2KfneE54VzVOdHpITzA/view?usp=sharing Allwinner V40 datasheet]
::[https://drive.google.com/file/d/0B4PAo2nW2KfnbVp2TmRMYUdPUGM/view?usp=sharing Allwinner R40 datasheet]
::[https://github.com/tinalinux/docs/blob/r40-v1.y/Allwinner\_R40\_User\_Manual\_V1.0.pdf Allwinner R40 User Manual v1.0]
::[https://drive.google.com/file/d/0B4PAo2nW2KfnM2pnT19zZW5qOTA/view?usp=sharing axp221s PMU datasheet]
* Banana pi BPI-M2 Berry CE,FCC,RoHS
::[https://bananapi.gitbooks.io/bpi-m2-ultra-open-source-single-board-computer/content/bpi-m2-berry-cefcc-rohs-certification.html CE FCC RoHS]

=Image Release=
== Android 6.0==
*2017-08-25 update
*HDMI-Version,LCD5-Version LCD7-Version,please choose which you are need:

::google Drive : https://drive.google.com/drive/folders/0B_YnvHgh2rwjNFRpVFlhcW56LUk?resourcekey=0-95UrcQ-bb0Bh-RDtLRp-0w

*forum pthread : http://forum.banana-pi.org/t/bpi-m2-ultra-bpi-m2-berry-new-image-android-6-0-version-v1-2017-08-25/3731

==Ubuntu==
*2022-04-16 Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2020-04-19 update, kernel 3.10.108
::Ubuntu 16.04 mate desktop [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M2U%2FUbuntu16.04&mode=list Download]
::Ubuntu 16.04 server [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M2U%2FUbuntu16.04&mode=list Download]

*2019-05-13 update banana pi M2U board which is based on A40I, R40, V40, and it is based on Ubuntu 16.04 & Raspbian 9 & Debian 9 Operation system with kernel 3.10.108
::BPI-M2U Ubuntu 16.04 Features Map:http://wiki.banana-pi.org/M2U/Berry_Image_Map#Ubuntu_16.04
::Desktop images:
::::Google Drive :https://drive.google.com/file/d/1Q8MGksdugAsMhy4slj50Rp9P0eeDUQFo/view?usp=sharing
::::Baidu Drive : https://pan.baidu.com/s/1Aap1emViG6Vh2ejVHPtZhg?pwd=xfd5 (PinCode:xfd5)
::::MD5 : cde8fd1165b54c633bcc5288e8447c2b
::Server images:
::::Google Drive : https://drive.google.com/open?id=1vcuIpQ7O2SFB3cZ4UemOqR2hQkxHy3RF
::::Baidu Drive : https://pan.baidu.com/s/18Cp7zeuHxa82z5OU_tV_oQ (PinCode：qat4)
::::MD5 : 07981887a7a21f5cda72ab8a1e37a834
::Forum pthread : http://forum.banana-pi.org/t/bpi-m2u-berry-new-image-release-ubuntu-16-04-raspbian-9-4-debian-9-4-2019-05-13/9225

*2018-01-04 update BPI-M2 Ultra/Berry Ubuntu 16.04 image
::Google Drive : https://drive.google.com/file/d/1G4Ggkne63ofD51Yt2c-x5-qy9h7BgY4_/view?usp=sharing
::baidu cloud : https://pan.baidu.com/s/1cFHYGY1
::MD5: a61e6f66a5ea2288fff0c3acff12d633
*2017-11-13 update
::Google Drive : https://drive.google.com/file/d/19PI9yuL9iFa4bU6dh7ym3tcCHhjAh-cM/view?usp=sharing
::baidu cloud : http://pan.baidu.com/s/1nvccOlz
::MD5: 4655b896a3c4e1958a15bb8ca45ac4fe
::forum pthread : http://forum.banana-pi.org/t/bpi-m2-ultra-bpi-m2-berry-new-image-2017-11-13-ubuntu-16-04-mate-desktop-beta2-bpi-m2u-sd-emmc-img/4182

==Debian==
*2020-04-19 update, kernel 3.10.108
::Debian 9 stretch mate desktop [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M2U%2FDebian9&mode=list Download]
::Debian 9 stretch lite [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M2U%2FDebian9&mode=list Download]

*2019-05-13 update banana pi M2U board which is based on A40I, R40, V40, and it is based on Ubuntu 16.04 & Raspbian 9 & Debian 9 Operation system with kernel 3.10.108
::BPI-M2U Debian 9 Features Map:http://wiki.banana-pi.org/M2U/Berry_Image_Map#Debian_9
::Desktop images :
::::Google Drive :
::::Baidu Drive : https://pan.baidu.com/s/1ZqDZT4dOQNyvsu0nT4oMTg (PinCode:kshd)
::::MD5 : 7e5d848f804bc5ffb8854a93d7488694
::Server images:
::::Google Drive : https://drive.google.com/open?id=1aoB8mGwSveNztB-EO_fBKLOr-GdzcMNV
::::Baidu Drive : https://pan.baidu.com/s/1V0djGvUR7QJFMeAgZV86zg (PinCode:e0t6)
::::MD5 : b7314d444dc13a40e1dd7b1602436f40
::Forum pthread : http://forum.banana-pi.org/t/bpi-m2u-berry-new-image-release-ubuntu-16-04-raspbian-9-4-debian-9-4-2019-05-13/9225

*2017-11-13 update debian-9-stretch-mate-desktop
::Google Drive : https://drive.google.com/file/d/0B_YnvHgh2rwjeTh4TmlnMGl5X3M/view?usp=sharing
::baidu cloud : http://pan.baidu.com/s/1c1LvS1y
::MD5: 0a1fad281c24902148b16276a79bac12
*2017-11-13 update debian-9-stretch-lite
::Google Drive: https://drive.google.com/file/d/0B_YnvHgh2rwjOWg1OW9heWZsYm8/view?usp=sharing
::baidu cloud: http://pan.baidu.com/s/1c3zxCy 13
::MD5: cff677aa94ca5345fc6e26379cfe4e95
*forum pthread : http://forum.banana-pi.org/t/bpi-m2-ultra-bpi-m2-berry-new-image-2017-08-28-debian-sd-emmc-img/3745/2

==Raspbian==
*2020-04-19 update, kernel 3.10.108
::Raspbian stretch [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-M2U%2FRaspbian&mode=list Download]

*2019-05-13 update banana pi M2U board which is based on A40I, R40, V40, and it is based on Ubuntu 16.04 & Raspbian 9 & Debian 9 Operation system with kernel 3.10.108
::BPI-M2U Raspbian 9 Features Map:http://wiki.banana-pi.org/M2U/Berry_Image_Map#Raspbian_9.4
::Desktop image :
::::Google Drive : https://drive.google.com/file/d/146--P5XiX9F_Dn8JzC3gRApGBQUUcEzH/view?usp=sharing
::::Baidu Drive : https://pan.baidu.com/s/1ngowiaK1q20MbQMQzXabDw?pwd=8888 (PinCode:8888)
::::MD5 : f7ee24ff15654724e2c7ec3bf72c8506
::Forum pthread : http://forum.banana-pi.org/t/bpi-m2u-berry-new-image-release-ubuntu-16-04-raspbian-9-4-debian-9-4-2019-05-13/9225

*2018-05-24 update Raspbian jessie 8.0 V1.1
::Google Drive : https://drive.google.com/file/d/0B_YnvHgh2rwjRGlUMUdqZk5ETDg/view?usp=sharing
::baidu cloud : https://pan.baidu.com/s/1UnMPtGBNp3-8KHDZPhVOUg
::forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m2u-berry-new-image-release-raspbian-jessie-8-0-2018-5-24/5812

*2017-05-25 update raspbian jessie
::Google Drive : https://drive.google.com/file/d/0B_YnvHgh2rwjRGlUMUdqZk5ETDg/view?usp=sharing
::baidu cloud : https://pan.baidu.com/s/1civq4e
::MD5: 60e19ea9138d6841fa6852ece4727b0a
::forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m2-ultra-bpi-m2-berry-new-image-2017-05-25-raspbian-jessie-preview3-bpi-m2u-sd-emmc-img/3306

==Armbian==
*Armbian_23.02.0-trunk_Bananapim2ultra_jammy_edge_6.1.11_xfce_desktop.img
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Disucss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m2-berry-new-armbian-image/15140

*2022-12-06 Armbian_22.11.0-trunk_Banana Pi BPI-M2 Berry_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1vyK13DB2Z1OMjGE9Wd1XHYIMFPZ8UuZI/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/1GMUZGZcWWXPKRSW1X5fRKw?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m2-berry-new-image-release-armbian-bullseye/14451

*Armbain have support BPI-M2 Ultra/BPI-M2 Berry，Armbian Bionic btea and Armbian Stretch beta version
::image download ： https://www.armbian.com/bananapi-m2u/
::Boot logs : http://ix.io/1kVQ
::Forum pthread : http://forum.banana-pi.org/t/armbian-bionic-and-stretch/6573

==Tina IoT Linux ==
*BPI-M2 Ultra / BPI-M2 Berry support Allwinner TinaLinux .
::more please see : [[Tina Linux]]

==RPiTC v3 1.12==
*2017-11-28 updtae
*RPiTC v3 1.12 for Banana Pi (BPI-M2U/BPI-M2B/BPI-M2P/BPI-M3/BPI-M64/BPI-R2): [http://forum.banana-pi.org/t/rpitc-v3-1-12-for-banana-pi-bpi-m2u-bpi-m2b-bpi-m2p-bpi-m3-bpi-m64-bpi-r2/4292 download link]

==Others==
* kali linux,crux linux,archlinux,centos linux for BPI-M2 Ultra & BPI-M2 Berry : [http://forum.banana-pi.org/t/bpi-m2-ultra-bpi-m2-berry-new-image-2017-8-28-kali-linux-crux-linux-archlinux-centos-linux-image/3750 kali linux,crux linux,archlinux,centos linux 2017-08-25]

* please download here: http://forum.banana-pi.org/c/Banana-pi-BPI-M2-Ultra/M2Uimage

=FAQ=

Banana Pi BPI-M3

2023-03-22T06:48:06Z

Czj: /* Armbian */

[[zh:香蕉派_BPI-M3]]
=Introduction=

[[File:Banana_pi_BPI-M3_1.jpg|thumb|Overview: Allwinner A83T]]
[[File:Banana_pi_BPI-M3_5.jpg|thumb|Overview: front]]
[[File:3.7V.jpg|thumb|Overview: back]]
[[File:Banana_Pi_BPI-M2U_case_1.jpg|thumb|BPI-M3 Premium Aluminum Enclosure]]
[[File:Bpi-m2_ultar_case_1.jpg|thumb|BPI-M3 acrylic case]]
[[File:A83T.JPG|thumb|BPI 4.0 OEM&ODM server [[Successful case]] : A83T Raid Nas design]]
[[File:Magic_mirror_2.JPG|thumb|BPI 4.0 OEM&ODM server [[Successful case]] : A83T Magic Mirror]]

Banana Pi M3 is a super charged single board computer with an Octa-core processor and 2GB of RAM. Along side the elite processing unit, it features Gigabit Ethernet, 2 USB, SATA, WiFi, Bluetooth, and HDMI connection. It can run on a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

Being a brother of the power hungry M2, the M3 does not want to rest while his brother goes to acquire two more cores. The M3 secretly mastered the powerful art of Octa-core to best even the M2. Unlike his careless brother, the M3 did not lose his SATA port.

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

[[File:BPI-M3_960x360.jpg]]

==Key Features==

* Allwinner A83T Octa-core 1.8GHz Powerful CPU.
* 2 GB LPDDR3 memory.
* 8 GB eMMC storage.
* HDMI out
* IR control
* WiFi & Bluetooth onboard.
* MIPI DSI ingerface
* CSI camera interface

==Getting Start==
*How to burn image to BPI-M3 and begin [[Quick Start Banana pi SBC]]
*How to development [[Getting Start with M3]]

=Hardware=
==Hardware interface==
[[File:M3-hdw-label.jpg]]

==Hardware spec==
{| class="wikitable"
|-
!
! Banana Pi BPI-M3
|-
! CPU
| Allwinner A83T ARM Cortex-A7 Octa-Core 1.8 GHz, 512KB L1 cache and 1MB L2 cache
|-
! GPU
| PowerVR SGX544MP1 Comply with OpenGL ES 2.0 OpenCL 1x, DX9_3
|-
! Memory
| 2 GB LPDDR3 (shared with GPU)
|-
! Storage
| On Board 8GB eMMC Flash, Micro SD-Card slot, SATA 2.0 Port (USB-to-SATA bridge)
|-
! Network
| 10/100/1000 Mbit/s Ethernet (Realtek RTL8211E/D) + Wi-Fi 802.11 b/g/n (AP6212) + Bluetooth BT4.0
|-
! Video Input(s)
| A CSI input connector allows for the connection of a designed camera module
|-
! Video Output(s)
| HDMI 1.4 (Type A Full), MIPI Display Serial Interface (DSI) for raw LCD Panel
|-
! Audio Input(s)
| On board microphone
|-
! Audio Output(s)
| 3.5mm jack and HDMI
|-
! USB ports
| USB 2.0 PORT (x2), USB OTG (x1)
|-
! Remote
| IR Receiver (x1)
|-
! GPIO
| 40 Pin Header : GPIO (x28) and Power (+5V, +3.3V and GND). Some of I/O Pin can be used for specific functions as UART, I2C, SPI or PWM
|-
! Switches
| Reset, Power and U-boot
|-
! LED
| Power Status and 8P8C
|-
! Power Source
| 5 volt @2A via DC Power and/or Micro USB (OTG)
|-
! Size & Weight
| 92x60mm, 48g
|-
! OS
| Android and Linux
|}

==GPIO PIN define ==

Banana Pi BPI-M3 has a 40-pin GPIO header that matches that of the Model Raspberry Pi 3. Following is the Banana Pi GPIO Pinout:

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO define of Banana pi BPI-M3'''
|-
|GPIO Pin Name|| Default Function|| Function2：GPIO|| Function3
|-
|CON1-P01|| VCC-3V3 || ||
|-
|CON1-P02|| DCIN|| ||
|-
|CON1-P03|| TWI2-SDA|| PH5-EINT5||
|-
|CON1-P04|| DCIN|| ||　
|-
|CON1-P05|| TWI2-SCK|| PH4-EINT4||
|-
|CON1-P06|| GND|| ||
|-
|CON1-P07|| S-PWM|| PL10-S-EINT10||
|-
|CON1-P08|| UART2-TX|| PB0-EINT0||
|-
|CON1-P09|| GND|| ||
|-
|CON1-P10|| UART2-RX|| PB1-EINT1||
|-
|CON1-P11|| PC4 PC4|| ||
|-
|CON1-P12|| UART2-CTS|| PB3-EINT3||
|-
|CON1-P13|| PC7|| PC7 ||
|-
|CON1-P14|| GND || ||
|-
|CON1-P15|| PC17|| PC17||
|-
|CON1-P16|| UART2-RTS|| PB2-EINT2||
|-
|CON1-P17|| VCC-3V3 || ||
|-
|CON1-P18|| PL8-ENT8|| PL8-S-ENT8||
|-
|CON1-P19|| SPI0_MOSI|| PC0||
|-
|CON1-P20|| GND || ||
|-
|CON1-P21|| SPI0_MISO|| PC1 ||
|-
|CON1-P22|| PL9-EINT9|| PL9-S-EINT9 ||
|-
|CON1-P23|| SPI0_CLK|| PC2 ||
|-
|CON1-P24|| SPI0_CS|| PC3||
|-
|CON1-P25|| GND|| ||
|-
|CON1-P26|| PH10-ENT10|| PH10-ENT10||
|-
|CON1-P27|| TWI1-SDA|| PH3-EINT3||
|-
|CON1-P28|| TWI1-SCK|| PH2-EINT2||
|-
|CON1-P29|| PC18|| PC18||
|-
|CON1-P30|| GND|| ||
|-
|CON1-P31|| I2S1-BCLK|| PG10-EINT10|| UART3-TX
|-
|CON1-P32|| I2S1-DIN|| PG13-EINT13|| UART3-CTS
|-
|CON1-P33|| I2S1-LRCK|| PG11-EINT11|| UART3-RX
|-
|CON1-P34|| GND || ||
|-
|CON1-P35|| I2S1-DOUT|| PG12-EINT12|| UART3-RTS
|-
|CON1-P36|| PE5|| PE5 ||
|-
|CON1-P37|| PE4|| PE4 ||
|-
|CON1-P38|| OWA-DOUT|| PE18||
|-
|CON1-P39|| GND || ||
|-
|CON1-P40|| PE19|| PE19||
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI camera GPIO of Banana pi BPI-M3'''
|-
|CSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN7-P01|| IPSOUT ||
|-
|CN7-P02|| AFVCC ||
|-
|CN7-P03|| IPSOUT ||
|-
|CN7-P04|| IOVDD ||
|-
|CN7-P05|| GND||
|-
|CN7-P06|| GND ||
|-
|CN7-P07|| CSI2-D3N||
|-
|CN7-P08|| AVDD-CSI||
|-
|CN7-P09|| CSI2-D3P||
|-
|CN7-P10|| DVDD-CSI-R||
|-
|CN7-P11|| GND ||
|-
|CN7-P12|| NC ||
|-
|CN7-P13|| CSI2-D2N||
|-
|CN7-P14|| CSI-RST-R|| PE16
|-
|CN7-P15|| CSI2-D2P|| |
|-
|CN7-P16|| CSI-STBY-R|| PE17
|-
|CN7-P17|| GND||
|-
|CN7-P18|| CSI-PCLK|| PE0
|-
|CN7-P19|| CSI2-CKN||
|-
|CN7-P20|| CSI-MCLK|| PE1
|-
|CN7-P21|| CSI2-CKP||
|-
|CN7-P22|| CSI-HSYNC|| PE2
|-
|CN7-P23|| GND||
|-
|CN7-P24|| CSI-VSYNC|| PE3
|-
|CN7-P25|| CSI2-D1N||
|-
|CN7-P26|| CSI-D9|| PE13
|-
|CN7-P27|| CSI2-D1P||
|-
|CN7-P28|| CSI-D8|| PE12
|-
|CN7-P29|| GND ||
|-
|CN7-P30|| CSI-D7|| PE11
|-
|CN7-P31|| CSI2-D0N||
|-
|CN7-P32|| CSI-D6|| PE10
|-
|CN7-P33|| CSI2-D0P||
|-
|CN7-P34|| CSI-D5|| PE9
|-
|CN7-P35|| GND||
|-
|CN7-P36|| CSI-D4|| PE8
|-
|CN7-P37|| CSI-SCK|| PE14
|-
|CN7-P38|| CSI-D3|| PE7
|-
|CN7-P39|| CSI-SDA|| PE15
|-
|CN7-P40|| CSI-D2|| PE6
|-
|}

'''Display specification'''

MIPI DSI (Display Serial Interface)：

The display Connector is a 40-pin FPC connector which can connect external LCD panel (MIPI DSI) and touch screen (I2C) module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “DSI”.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''MIPI DSI PIN define of Banana pi BPI-M3'''
|-
|DSI Pin Name|| Default Function|| Function2：GPIO
|-
|CN6-P01|| VCC-MIPI||
|-
|CN6-P02|| IPSOUT||
|-
|CN6-P03|| VCC-MIPI||
|-
|CN6-P04|| IPSOUT||
|-
|CN6-P05|| GND ||
|-
|CN6-P06|| IPSOUT||
|-
|CN6-P07|| GND ||
|-
|CN6-P08|| IPSOUT||
|-
|CN6-P09|| NC||
|-
|CN6-P10|| GND ||
|-
|CN6-P11|| NC ||
|-
|CN6-P12|| DSI-D0N ||
|-
|CN6-P13|| NC||
|-
|CN6-P14|| DSI-D0P ||
|-
|CN6-P15|| NC ||
|-
|CN6-P16|| GND ||
|-
|CN6-P17|| TWI0-SDA|| PH1-EINT1
|-
|CN6-P18|| DSI-D1N||
|-
|CN6-P19|| TWI0-SCK|| PH0-EINT0
|-
|CN6-P20|| DSI-D1P ||
|-
|CN6-P21|| TP-INT|| PL7-S-EINT7
|-
|CN6-P22|| GND||
|-
|CN6-P23|| TP-RST|| PL6-S-EINT6
|-
|CN6-P24|| DSI-CKN ||
|-
|CN6-P25|| GND ||
|-
|CN6-P26|| DSI-CKP||
|-
|CN6-P27|| LCD-BL-EN|| PD29
|-
|CN6-P28|| GND ||
|-
|CN6-P29|| LCD-RST|| PD26
|-
|CN6-P30|| DSI-D2N ||
|-
|CN6-P31|| LCD-PWR-EN|| PD27
|-
|CN6-P32|| DSI-D2P||
|-
|CN6-P33|| GND ||
|-
|CN6-P34|| GND ||
|-
|CN6-P35|| LCD-PWM|| PD28
|-
|CN6-P36|| DSI-D3N ||
|-
|CN6-P37|| GND ||
|-
|CN6-P38|| DSI-D3P||
|-
|CN6-P39|| AP-RESET#||
|-
|CN6-P40|| GND |||
|-
|}

'''UART specification:'''

The header CON4 is the UART interface.For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Uart debug pin of Banana pi BPI-M3'''
|-
|CON2 Pin Name ||Default Function|| GPIO
|-
|CON2 P03|| UART0-TXD|| PB9
|-
|CON2 P02|| UART0-RXD|| PB10
|-
|CON2 P01|| GND||
|-
|}

=Software=
==Android==
*How to burn android image to eMMC under windows ： https://bananapi.gitbooks.io/bpi-m3/content/en/how_to_burn_android_image_to_emmc.html
*BPI-M3 How to control GPIO on Android ：https://bananapi.gitbooks.io/bpi-m3/content/en/howtocontrolgpioonandroid.html

==Linux==
*How to burn Linux image to eMMC : https://bananapi.gitbooks.io/bpi-m3/content/en/howtoburnlinuximagetoemmc.html
*GPU for kernel 3.4 : https://bananapi.gitbooks.io/bpi-m3/content/en/gpuforkernel34.html
*How to rotate display screen : https://bananapi.gitbooks.io/bpi-m3/content/en/howtorotatedisplayscreen.html
*how to use fatload uEnv.txt & script.bin & kernel uImage : https://bananapi.gitbooks.io/bpi-m3/content/en/howtousefatloaduenvtxtscriptbinkernel_ui.html

==Opnewrt==
==TinaLinux==

=Development=

==Basic Development==
*[https://bananapi.gitbooks.io/bpi-m3/content/en/howtosetupdockerenvtobuildgithubsourcecod.html How to setup docker env. to build github source code ]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/howtocompilebpi-m3-bspkernelonbpi-m3.html How to compile BPI-M3-bsp kernel on BPI-M3]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3crosscompileteach.html BPI-M3 BSP Cross Compile teach]
*[https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3fixrootmydeviceissueforsecurityalert.html BPI-M3 fix rootmydevice issue for Security Alert]

=Resources=
==Source code==
* BPI-M3 android 5.1 source code ： https://drive.google.com/open?id=0B\_YnvHgh2rwjaGhIeUE0eERTZU0
*BPI-M3 Linux BSP code : https://github.com/BPI-SINOVOIP/BPI-M3-bsp

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
*BPI-M3 schematic diagram :[https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google driver]
*BPI-M3 DXF file : https://drive.google.com/file/d/0B4PAo2nW2KfnNm54VjBlUXhXekU/view
*BPI-M3 3D design file : https://drive.google.com/file/d/0B4PAo2nW2KfnYXVGWXBURDFSeTA/view
*A83T chip Datasheet V1.4 : https://drive.google.com/file/d/0B4PAo2nW2KfnM2VqeTR3SXpGdVE/view?usp=sharing
*Allwinner A83T chip User_Manual V1.5.1 : https://drive.google.com/file/d/0B4PAo2nW2KfnRjlQaU9uR0J0elE/view?usp=sharing
*android 5.0 development document（chinese）：https://drive.google.com/file/d/0B4PAo2nW2KfnekpvMnlNZ2p6NWs/view?usp=sharing
*allwinner chip online datasheet and documents : http://dl.linux-sunxi.org/
*linux-sunxi wiki : http://linux-sunxi.org/Banana_Pi_M3
*BPI-M3 quality guarantee
::BPI-M3 WIFI Lab test report : https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3wifilabtest.html
::BPI-M3 Validation test report : https://bananapi.gitbooks.io/bpi-m3/content/en/bpi-m3validationtest.html
::BPI-M3 CE,FCC RoHS Certification : http://forum.banana-pi.org/t/bpi-m3-ce-fcc-rohs-certification/984

=Image Release=
==Android 5.1.1 V5==
*2018-06-05 update
*HDMI-Version
::Google Drive : https://drive.google.com/open?id=1mLXOAH_LPT-uqtwWvgvJXw4Vo95tFr_z
::Baidu Cloud : https://pan.baidu.com/s/1byqwqzz9SOIWHYfOabXKNw

*LCD-Version
::Google Drive : https://drive.google.com/open?id=1DAxQIws0eAVPAm0riH5HXc8M36SH_-sC
::Baidu Cloud : https://pan.baidu.com/s/19l7a6Z75FuZb_f9Ls0fN5w

*2017-05-11 update
*HDMI-Version
::Google Drive : https://drive.google.com/open?id=0B_YnvHgh2rwjcXkxczlmOWxWV00
::Baidu Cloud : https://pan.baidu.com/s/1pKF3Ggj
::MD5: d7b7abf3443a49fb0f178ccf2f6e82d0
*LCD-Version
::Google Drive : https://drive.google.com/open?id=0B_YnvHgh2rwjSkM5NHFWYVdlakk
::Baidu Cloud : https://pan.baidu.com/s/1mi2YOeG
::MD5: b27dd45ac5fd1fd3b02db8ffd92c2871
*forum pthread : http://forum.banana-pi.org/t/bpi-m3-new-image-android-5-1-version-v5-2017-05-11/3241

==Ubuntu==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim3_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1iq0gCOAIHjE7bgxeccNPtFp9iK0AtzRM/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1FjNBqpJ0Kv83EpiKt9sZmw?pwd=mtk5 (pincode: mtk5)

*2021-08-03 release, Ubuntu Mate Desktop 16.04 with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FUbuntu16.04%2F2021-08-03-ubuntu-16.04-mate-desktop-bpi-m3-sd-emmc.img.zip 2021-08-03-ubuntu-16.04-mate-desktop-bpi-m3-sd-emmc.img.zip]
::MD5: 4cd6cfb9ed3a2d382dbc32bb478ac149

*2021-08-03 release, Ubuntu Server 16.04 with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FUbuntu16.04%2F2021-08-03-ubuntu-16.04-server-bpi-m3-sd-emmc.img.zip 2021-08-03-ubuntu-16.04-server-bpi-m3-sd-emmc.img.zip]
::MD5: ea5abe3fd6988931df85a2376808501a

*2018-07-18 BPI-M3 Ubuntu 16.04 Mate Desktop (new eMMC)
::Features Map ：http://wiki.banana-pi.org/M3_Image_Map#Ubuntu_16.04
::Google Drive : https://drive.google.com/open?id=1DlOrt08yUY9hAETiUXBiyoyPFHrOxtvq
::Baidu Drive : https://pan.baidu.com/s/1ND5QqoBevzM2TykwqZCkAA
::forum pthread: http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

*2018-07-18 M3 Ubuntu Server (new eMMC)
::Features Map : http://wiki.banana-pi.org/M3_Image_Map#Ubuntu_Lite
::Google Drive : https://drive.google.com/open?id=1Yyd2BepHjyhgXhSmnFh_0Az6YoXPEI3J
::Baidu Drive : https://pan.baidu.com/s/10vSo0AmIiMrVLNPkQ63leQ
::forum pthread: http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

*2018-05-31 update ubuntu 16.04 mate desktop
**HDMI verison baidu cloud :　https://pan.baidu.com/s/1UDktbDgGtXpbqIZn_TI1Tg

*2017-07-13 update ubuntu 16.04 mate desktop
* Image Link:
**HDMI version Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjRThoaHliWVVyZGM/view?usp=sharing
**HDMI verison baidu cloud :　http://pan.baidu.com/s/1nu6hJs9
**Forum pthread: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-ov8865-sd-emmc-2017-07-13/3542
**LCD 7 verison Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjVldzUENFQXpiTHc/view?usp=sharing
**LCD 7 version baidu cloud :　http://pan.baidu.com/s/1o8Uc4Y2
**Forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-lcd7-ov8865-sd-emmc-img-2017-7-13/3543
**LCD 5 Version Google Drive:https://drive.google.com/file/d/0B_YnvHgh2rwjUlpIVjB6LVVmMGc/view?usp=sharing
**LCD 5 Version baidu cloud : http://pan.baidu.com/s/1hsIJygG
** Forum thread:http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-ubuntu-16-04-mate-desktop-beta-bpi-m3-lcd5-ov8865-sd-emmc-img-2017-7-13/3544

==Debian==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim3_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1vrM4WLq74O4FEOAmBjUwJGbzZptq3hYi/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1w00wkfX15G6D60W2WH52ug?pwd=awza (pincode: awza)

*2018-07-18 BPI-M3 Debian Jessie 9 (new eMMC)
::Features Map : http://wiki.banana-pi.org/M3_Image_Map#Debian_Jessie_9
::Google Drive : https://drive.google.com/open?id=1M997Uf-RVqdFKJkXMjgY0w3fHyiOq4iG
::Baidu Drive : https://pan.baidu.com/s/1yQYG1iOEIrJADV_j-qvdwQ
::Forum pthread : http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-new-emmc-ubuntu16-04-debian9-release-2018-07-18/6294

==Armbian==
*Armbian_23.02.0-trunk_Bananapim3_focal_current_5.15.82_xfce_desktop.img
*Armbian_23.02.0-trunk_Bananapim3_jammy_edge_6.1.11_xfce_desktop.img
*Armbian_23.02.0-trunk_Bananapim3_bullseye_edge_6.1.0_xfce_desktop.img
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888 1
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link 2
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m3-new-armbian-image/15138

*2022-12-06 Armbian_22.11.0-trunk_Bananapim3_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1Cr0KY0oVqSly-DOipgd_x_a4gQ0oPxm7/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/18M5Tsc91z57NUzBm4rcqlg?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-release-armbian-bullseye/14450

*Armbian with 4.17.y for M3
::Test build:http://ix.io/1fUK
::Broken: wired, wireless network, Bluetooth, ...
::Works: serial console, 8 cores, DVFS, USB, SATA, HDMI, DRM video driver, ...
::image:https://forum.armbian.com/topic/474-banana-pi-m3/?do=findComment&comment=57400
::Forum pthread:http://forum.banana-pi.org/t/armbian-with-4-17-y-for-m3/6174

==Rasbian==
*2021-08-03 release, Raspbian Stretch with kernel 3.4.39
::Download: [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M3%2FRaspbian%2F2021-08-03-raspbian-stretch-bpi-m3-sd-emmc.img.zip 2021-08-03-raspbian-stretch-bpi-m3-sd-emmc.img.zip]
::MD5: a9890cedbd779a29ff551a7fc5e1eae6

* 2018-5-28 update : Raspbian 8.0 V1.1
::Image Link:
::::Google Drive: https://drive.google.com/open?id=1DSZru8UQRikI6pImLZIt1DmySVozy0FA
::::baidu cloud : https://pan.baidu.com/s/1Pz_6btHxj6F9w_6aw90Dww
::Forum thread:
:::: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-release-raspbian-jessie-8-0-2018-5-28-v1-1/5847

==Arch Linux ==
*2018-08-19 ArchLinux-4.18.1-1-ARCH : Kernel: 4.18.1-1-ARCH U-Boot: 2018.09-rc1
::U-Boot: 2018.09-rc1,Kernel: 4.18.1-1-ARCH,Ethernet works,Wifi works,HDMI works,LCD needs to be checked(I would appreciate if someone can check it),GPIO works(WiringPi),BPI tools included,I2C enabled(In TDB file)
::source code on github : https://github.com/apankevych/BananaPi-M3-Linux-4.18.1-1-ARCH
::download Image link:https://drive.google.com/file/d/1ia3JSmHH8ksia4e8doalUGSBHnytOgx4/view?usp=sharing
::Forum pthread : http://forum.banana-pi.org/t/bananapi-bpi-m3-new-image-archlinux-4-18-1-1-arch-2018-08-19/6544

*2018-07-19 Arch Linux sunxi kernel-4.18-rc3 and uboot- 2018.01 thank Andriy_Pankevych do this great work.
:: Google drive : https://drive.google.com/open?id=1Ve91MG_7d1haawqqmiBo4qCugvF1iLyn
:: Source code: https://github.com/apankevych/BananaPi-M3-Linux-4.18.0-rc3
:: Forum pthread : http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-arch-linux-sunxi-kernel-4-18-rc3-and-uboot-2018-01-2018-07-19/6312

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/
https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-m3

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Others image==
*http://forum.banana-pi.org/c/bpi-m3/M2image

=FAQ=

Banana Pi BPI-M1

2023-03-22T06:41:12Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1]]
=Introduction=

[[File:Banana_pi_BPI-M1_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1_2.jpg|thumb|Overview]]
[[File:BPI-M1_3d.jpg|thumb|BPI-M1 3D ]]
[[File:White-2.JPG|thumb|BPI-M1 with plastic case]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]

The Banana Pi BPI-M1 is a business card-sized and low-power single-board computer featuring a high performance AllWinner A20 dual-core SoC at 1 GHz, 1 GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections. It can run a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

It is the first open source hardware launched by the banana pie team, and also a classic product with the largest cumulative sales of banana pie.There are still a lot of business clients that apply to various projects.A20 chip

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding.

[[File:A_BPI-M1.jpg]]

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV vide out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 26 PIN gpio

==Getting Start==
*[[Quick Start Banana pi SBC]]
*[[Getting Started with M1]]

=Hardware=
==Hardware interface==
[[File:BPI-M1_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1'''
|-
| CPU|| A20 ARM Cortex -A7 Dual-Core
|-
| GPU|| ARM Mali 400 MP2; Complies with OpenGL ES 2.0/1.1
|-
| Memory|| 1GB DDR3
|-
| Network|| 10/100/1000 Ethernet [[Modular connector|8P8C]] ([[1000BASE-T]])
|-
| Video Input|| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs|| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs|| 3.5mm jack and HDMI
|-
| Power Source|| 5 volts DC via Micro USB or GPIO
|-
| USB 2.0 ports|| 2 (direct from Allwinner A20 chip)
|-
| GPIO|| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED|| Power Key & 8P8C
|-
| Storage|| SATA 2.0,
|}

==GPIO PIN define ==

Banana Pi BPI-M1 has a 26-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:BPI-M1_26_pin.png]]

Note: 5V1,5V2 only support output,not support input

'''CSI Camera Connector specification:'''

CSI Camera Connector The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1'''
|-
| CSI GPIO Pin || Pin Name || GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT ||
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS GPIO of Banana pi BPI-M1'''
|-
| LVDS Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27 |
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26 |
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 || LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 ||LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J11 of Banana pi BPI-M1'''
|-
| J11 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || || Multi 1 || Multi 2
|-
| J11 Pin1 || TXD || UART0-TX || PB22
|-
| J11 Pin2 || RXD || UART0-RX || PB23
|-
|}

The jumper J12 provides the power source including 3.3V and 5V. There is a pair of UART TX/RX signals output here.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J12 of Banana pi BPI-M1'''
|-
| J12 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| J12 Pin1 || 5V || ||
|-
| J12 Pin2 || 3.3V || ||
|-
| J12 Pin3 || NC || IO-7 || PH5
|-
| J12 Pin4 || RXD || UART7\_RX || PI21
|-
| J12 Pin5 || NC ||IO-8 || PH3
|-
| J12 Pin6 || TXD || UART7\_TX || PI20
|-
| J12 Pin7 || GND || ||
|-
| J12 Pin8 || GND || ||
|-
|}

'''All GPIO define list:'''

[[File:BPI-M1_all_pin.png]]

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==
* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]

* schematic diagram:https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing
* BPI-M1 DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=

==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1HErsANQ4PsnwQJ-tH0AdTg
::Google Drive:

==Ubuntu Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive: https://drive.google.com/file/d/1WtPL8Hfr9aaE3VRnpgR_R7VYsc7O3Y9P/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1fM-in68EK_ABvSJ7XiY0Ag?pwd=yft7 (pincode: yft7)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2018-7-28 update :Ubuntu Server16.04 HDMI Version Image Link：
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive: https://pan.baidu.com/s/1GYH8oDK3T_WcUFn-0t9YmQ
::Google Drive: https://drive.google.com/open?id=13XTvWe90yvRdqNWiKCLZ0HcMgo33y2r6
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1Tw_99XBZVOmKyavNxCXv3w
::Google Drive:

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_BPI-M1_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1px0h0se8EiRuBiGGxT40hWpU3RWzPedK/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1Vclux6Wb-ToJGOaGQxV6Hg?pwd=m4a3 (pincode: m4a3)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google drive:https://drive.google.com/file/d/1uGYn3BZ9k1K1iqmmZhlCy6pXeeNwfU6P/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapi_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapi_jammy_edge_6.1.11.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m1-new-armbian-image/15157

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1ZSFOd-nVFbAn_xB9AXckx9SEKQvnMB2J/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/12R8mIf7_45HDtruqEvktBw?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14446/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/bananapi/

==OpenWRT==
===Official OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*Gentoo Linux have officeal support banana pi BPI-M1, so you also can use on BPI-M1+,and BPI-R1, all is base on allwinner A20 chip.
*gentoo linux wiki : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M1+

2023-03-22T06:40:21Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1%2B]]
=Introduction=

[[File:Banana_pi_BPI-M1+_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1+_2.jpg|thumb|Overview]]
[[File:BPI-M1+_3d.jpg|thumb|BPI-M1+ 3D]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]
[[File:BPI-M1+_case.jpg|thumb|BPI-M1+ case]]

Banana Pi BPI-M1+ upgrade is an open-source single-board computer that adds more connectivity to the classic board. It features the same high performance AllWinner A20 dual-core SoC at 1GHz, 1GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections found in classic BPI-M1+ ; but the Banana Pi M1+ features onboard WiFi g/b/n. The board supports all classic projects and even more because of the onboard WIFi chip. Like its sibling, it can run operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

[[File:A_BPI-M1+.jpg]]

The Banana Pi M1+ is our upgraded M1 board. We feel like the onboard WiFi adds a lot more features to the board and makes it more convient for users to set up their linx desktop or router projects.
Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. With a Banana Pi, we want you to explore and experience the world of DIY projects and portable computing. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* Wifi support onboard
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 40 PIN gpio
* 3.7V lithium battery interface

==Get startting ==
*How to burn image : [[Quick Start Banana pi SBC]]
*How to development : [[Getting Started with M1P]]

==Hardware==

===Hardware interface===
[[File:BPI-M1_plus_interface.jpg]]

===Hardware spec===
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1+'''
|-
|-
| CPU
| A20 ARM Cortex -A7 Dual-Core
|-
| GPU
| ARM Mali400MP2Complies with OpenGL ES 2.0/1.1
|-
| Memory
| 1GB DDR3
|-
| Network
| 10/100/1000 Ethernet
|-
| wifi&BT
| Wifi support onboard
|-
| Video Input
| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs
| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs
| 3.5mm jack and HDMI
|-
| Power Source
| 5V/2A via Micro USB (DC in only) and / or Micro USB OTG
|-
| USB 2.0 ports
| 2(direct from Allwinner A20 chip)
|-
| GPIO
| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED
| Power Key & 8P8C
|-
| Storage
| SATA 2.0
|-
| OS
| Android 4.4, Android 4.2, Raspbian, Lubuntu, Open Suse, Debian
|}

===GPIO PIN define ===

Banana Pi BPI-M1+ has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:Gpio define.png]]

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1+'''
|-
|GPIO Pin Name || Default Function || Function2：GPIO
|-
| CON3-P01 || VCC-3V3 ||
|-
| CON3-P02 || VCC-DC ||
|-
| CON3-P03 || TWI2-SDA || PB21
|-
| CON3-P04 || VCC-DC ||
|-
| CON3-P05 || TWI2-SCK || PB20
|-
| CON3-P06 || GND ||
|-
| CON3-P07 || PWM1 || PI3
|-
| CON3-P08 || UART3\_TX ||PH0
|-
| CON3-P09 || GND ||
|-
| CON3-P10 || UART3\_RX || PH1
|-
| CON3-P11 || UART2\_RX || PI19
|-
| CON3-P12 || PH2 || PH2
|-
| CON3-P13 || UART2\_TX || PI18
|-
| CON3-P14 || GND ||
|-
| CON3-P15 || UART2\_CTS || PI17
|-
| CON3-P16 || CAN\_TX || PH20
|-
| CON3-P17 || VCC-3V3 ||
|-
| CON3-P18 || CAN\_RX || PH21
|-
| CON3-P19 || SPI0\_MOSI || PI12
|-
| CON3-P20 || GND ||
|-
| CON3-P21 || SPI0\_MISO || PI13
|-
| CON3-P22 || UART2\_RTS || PI16
|-
| CON3-P23 || SPI0\_CLK || PI11
|-
| CON3-P24 || SPI0\_CS0 || PI10
|-
| CON3-P25 || GND ||
|-
| CON3-P26 || SPI0\_CS1 || PI14
|-
| CON3-P27 || TWI3-SDA || PI1
|-
| CON3-P28 || TWI3-SCK || PI0
|-
| CON3-P29 || I2S\_MCLK || PB5
|-
| CON3-P30 || GND ||
|-
| CON3-P31 || I2S\_BCLK || PB6
|-
| CON3-P32 || I2S\_DI || PB12
|-
| CON3-P33 || I2S\_LRCK || PB7
|-
| CON3-P34 || GND ||
|-
| CON3-P35 || I2S\_DO0 || PB8
|-
| CON3-P36 || UART7\_RX || PI21
|-
| CON3-P37 || IR0\_TX || PB3
|-
| CON3-P38 || UART7\_TX || PI20
|-
| CON3-P39 || GND ||
|-
| CON3-P40 || SPDIF\_DO || PB13
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings.The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI PIN of Banana pi BPI-M1+'''
|-
| CSI Pin Name || Default Function Pin name || Function2：GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || AP-RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well.The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS PIN of Banana pi BPI-M1+'''
|-
| LVDS Pin || Default Function || Function2 || Function3：GPIO
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9 |
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 ||LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 || LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11header CON4 is the UART interface.For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''UART debug PIN of Banana pi BPI-M1+'''
|-
| Pin Name || Default Function || GPIO
|-
| CON4 P03 || UART0-TXD || PB22
|-
| CON4 P02 || UART0-RXD || PB23
|-
| CON4 P01 ||GND ||
|-
|}

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==

* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram: [https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google drive]
* BPI-M1+ DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1+ 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=
==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapim1plus_jammy_edge_6.1.11_xfce_desktop.img.xz,This release is for banana pi M1 Plus board, which is based on Armbian operation system.
jammy edge version with 6.1.11 kernel.
::Baidu Drive: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888 1
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link 2
::Discuss on forum : https://forum.banana-pi.org/t/banana-pi-bpi-m1-plus-new-armbian-image/15158

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1+ bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1AMEfQIygT8949sfkX6HIjap7WKpQox4i/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/1ePzBiwN0wEd8j3muk1HOlA?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14447/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/banana-pi-plus/

==Ubuntu linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1hlPkFx-NhGoCxYlHCqe4q9LwuQ0GosQL/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1SOeRKjVmTqTb6rMD71SfAw?pwd=wbnt (pincode: wbnt)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_bullseye_edge_5.19.6_xfce_desktop
::Google Drive:https://drive.google.com/file/d/1XpumxbOR74FSLayoICh4ZN4G3uZ_o0Fo/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1JtqdKE4AsAwCc6i_Wys_VA?pwd=6kgc (pincode: 6kgc)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google driver:https://drive.google.com/file/d/1FhbaO6pDBu5jSPYq1ghd7YKG-KvFy33Q/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

==OpenWRT==
===Officeal OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/gentoolinux.html

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M1+

2023-03-22T06:39:38Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1%2B]]
=Introduction=

[[File:Banana_pi_BPI-M1+_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1+_2.jpg|thumb|Overview]]
[[File:BPI-M1+_3d.jpg|thumb|BPI-M1+ 3D]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]
[[File:BPI-M1+_case.jpg|thumb|BPI-M1+ case]]

Banana Pi BPI-M1+ upgrade is an open-source single-board computer that adds more connectivity to the classic board. It features the same high performance AllWinner A20 dual-core SoC at 1GHz, 1GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections found in classic BPI-M1+ ; but the Banana Pi M1+ features onboard WiFi g/b/n. The board supports all classic projects and even more because of the onboard WIFi chip. Like its sibling, it can run operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

[[File:A_BPI-M1+.jpg]]

The Banana Pi M1+ is our upgraded M1 board. We feel like the onboard WiFi adds a lot more features to the board and makes it more convient for users to set up their linx desktop or router projects.
Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding. With a Banana Pi, we want you to explore and experience the world of DIY projects and portable computing. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project.

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* Wifi support onboard
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 40 PIN gpio
* 3.7V lithium battery interface

==Get startting ==
*How to burn image : [[Quick Start Banana pi SBC]]
*How to development : [[Getting Started with M1P]]

==Hardware==

===Hardware interface===
[[File:BPI-M1_plus_interface.jpg]]

===Hardware spec===
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1+'''
|-
|-
| CPU
| A20 ARM Cortex -A7 Dual-Core
|-
| GPU
| ARM Mali400MP2Complies with OpenGL ES 2.0/1.1
|-
| Memory
| 1GB DDR3
|-
| Network
| 10/100/1000 Ethernet
|-
| wifi&BT
| Wifi support onboard
|-
| Video Input
| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs
| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs
| 3.5mm jack and HDMI
|-
| Power Source
| 5V/2A via Micro USB (DC in only) and / or Micro USB OTG
|-
| USB 2.0 ports
| 2(direct from Allwinner A20 chip)
|-
| GPIO
| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED
| Power Key & 8P8C
|-
| Storage
| SATA 2.0
|-
| OS
| Android 4.4, Android 4.2, Raspbian, Lubuntu, Open Suse, Debian
|}

===GPIO PIN define ===

Banana Pi BPI-M1+ has a 40-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:Gpio define.png]]

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1+'''
|-
|GPIO Pin Name || Default Function || Function2：GPIO
|-
| CON3-P01 || VCC-3V3 ||
|-
| CON3-P02 || VCC-DC ||
|-
| CON3-P03 || TWI2-SDA || PB21
|-
| CON3-P04 || VCC-DC ||
|-
| CON3-P05 || TWI2-SCK || PB20
|-
| CON3-P06 || GND ||
|-
| CON3-P07 || PWM1 || PI3
|-
| CON3-P08 || UART3\_TX ||PH0
|-
| CON3-P09 || GND ||
|-
| CON3-P10 || UART3\_RX || PH1
|-
| CON3-P11 || UART2\_RX || PI19
|-
| CON3-P12 || PH2 || PH2
|-
| CON3-P13 || UART2\_TX || PI18
|-
| CON3-P14 || GND ||
|-
| CON3-P15 || UART2\_CTS || PI17
|-
| CON3-P16 || CAN\_TX || PH20
|-
| CON3-P17 || VCC-3V3 ||
|-
| CON3-P18 || CAN\_RX || PH21
|-
| CON3-P19 || SPI0\_MOSI || PI12
|-
| CON3-P20 || GND ||
|-
| CON3-P21 || SPI0\_MISO || PI13
|-
| CON3-P22 || UART2\_RTS || PI16
|-
| CON3-P23 || SPI0\_CLK || PI11
|-
| CON3-P24 || SPI0\_CS0 || PI10
|-
| CON3-P25 || GND ||
|-
| CON3-P26 || SPI0\_CS1 || PI14
|-
| CON3-P27 || TWI3-SDA || PI1
|-
| CON3-P28 || TWI3-SCK || PI0
|-
| CON3-P29 || I2S\_MCLK || PB5
|-
| CON3-P30 || GND ||
|-
| CON3-P31 || I2S\_BCLK || PB6
|-
| CON3-P32 || I2S\_DI || PB12
|-
| CON3-P33 || I2S\_LRCK || PB7
|-
| CON3-P34 || GND ||
|-
| CON3-P35 || I2S\_DO0 || PB8
|-
| CON3-P36 || UART7\_RX || PI21
|-
| CON3-P37 || IR0\_TX || PB3
|-
| CON3-P38 || UART7\_TX || PI20
|-
| CON3-P39 || GND ||
|-
| CON3-P40 || SPDIF\_DO || PB13
|-
|}

'''CSI Camera Connector specification:'''

The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings.The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''CSI PIN of Banana pi BPI-M1+'''
|-
| CSI Pin Name || Default Function Pin name || Function2：GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || AP-RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well.The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS PIN of Banana pi BPI-M1+'''
|-
| LVDS Pin || Default Function || Function2 || Function3：GPIO
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9 |
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 ||LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 || LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11header CON4 is the UART interface.For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''UART debug PIN of Banana pi BPI-M1+'''
|-
| Pin Name || Default Function || GPIO
|-
| CON4 P03 || UART0-TXD || PB22
|-
| CON4 P02 || UART0-RXD || PB23
|-
| CON4 P01 ||GND ||
|-
|}

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==

* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
* schematic diagram: [https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing google drive]
* BPI-M1+ DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1+ 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=
==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapim1plus_jammy_edge_6.1.11_xfce_desktop.img.xz
::Baidu Drive: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link
::Discuss on forum: https://forum.banana-pi.org/t/banana-pi-bpi-m1-plus-new-armbian-image/15158

*Armbian_23.02.0-trunk_Bananapim1plus_jammy_edge_6.1.11_xfce_desktop.img.xz,This release is for banana pi M1 Plus board, which is based on Armbian operation system.
jammy edge version with 6.1.11 kernel.
::Baidu Drive: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888 1
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link 2
::Discuss on forum : https://forum.banana-pi.org/t/banana-pi-bpi-m1-plus-new-armbian-image/15158

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1+ bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1AMEfQIygT8949sfkX6HIjap7WKpQox4i/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/1ePzBiwN0wEd8j3muk1HOlA?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14447/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/banana-pi-plus/

==Ubuntu linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1hlPkFx-NhGoCxYlHCqe4q9LwuQ0GosQL/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1SOeRKjVmTqTb6rMD71SfAw?pwd=wbnt (pincode: wbnt)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapim1plus_bullseye_edge_5.19.6_xfce_desktop
::Google Drive:https://drive.google.com/file/d/1XpumxbOR74FSLayoICh4ZN4G3uZ_o0Fo/view?usp=sharing
::Baidu Cloud:https://pan.baidu.com/s/1JtqdKE4AsAwCc6i_Wys_VA?pwd=6kgc (pincode: 6kgc)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google driver:https://drive.google.com/file/d/1FhbaO6pDBu5jSPYq1ghd7YKG-KvFy33Q/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

==OpenWRT==
===Officeal OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/gentoolinux.html

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M1

2023-03-22T06:36:11Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1]]
=Introduction=

[[File:Banana_pi_BPI-M1_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1_2.jpg|thumb|Overview]]
[[File:BPI-M1_3d.jpg|thumb|BPI-M1 3D ]]
[[File:White-2.JPG|thumb|BPI-M1 with plastic case]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]

The Banana Pi BPI-M1 is a business card-sized and low-power single-board computer featuring a high performance AllWinner A20 dual-core SoC at 1 GHz, 1 GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections. It can run a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

It is the first open source hardware launched by the banana pie team, and also a classic product with the largest cumulative sales of banana pie.There are still a lot of business clients that apply to various projects.A20 chip

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding.

[[File:A_BPI-M1.jpg]]

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV vide out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 26 PIN gpio

==Getting Start==
*[[Quick Start Banana pi SBC]]
*[[Getting Started with M1]]

=Hardware=
==Hardware interface==
[[File:BPI-M1_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1'''
|-
| CPU|| A20 ARM Cortex -A7 Dual-Core
|-
| GPU|| ARM Mali 400 MP2; Complies with OpenGL ES 2.0/1.1
|-
| Memory|| 1GB DDR3
|-
| Network|| 10/100/1000 Ethernet [[Modular connector|8P8C]] ([[1000BASE-T]])
|-
| Video Input|| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs|| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs|| 3.5mm jack and HDMI
|-
| Power Source|| 5 volts DC via Micro USB or GPIO
|-
| USB 2.0 ports|| 2 (direct from Allwinner A20 chip)
|-
| GPIO|| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED|| Power Key & 8P8C
|-
| Storage|| SATA 2.0,
|}

==GPIO PIN define ==

Banana Pi BPI-M1 has a 26-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:BPI-M1_26_pin.png]]

Note: 5V1,5V2 only support output,not support input

'''CSI Camera Connector specification:'''

CSI Camera Connector The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1'''
|-
| CSI GPIO Pin || Pin Name || GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT ||
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS GPIO of Banana pi BPI-M1'''
|-
| LVDS Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27 |
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26 |
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 || LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 ||LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J11 of Banana pi BPI-M1'''
|-
| J11 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || || Multi 1 || Multi 2
|-
| J11 Pin1 || TXD || UART0-TX || PB22
|-
| J11 Pin2 || RXD || UART0-RX || PB23
|-
|}

The jumper J12 provides the power source including 3.3V and 5V. There is a pair of UART TX/RX signals output here.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J12 of Banana pi BPI-M1'''
|-
| J12 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| J12 Pin1 || 5V || ||
|-
| J12 Pin2 || 3.3V || ||
|-
| J12 Pin3 || NC || IO-7 || PH5
|-
| J12 Pin4 || RXD || UART7\_RX || PI21
|-
| J12 Pin5 || NC ||IO-8 || PH3
|-
| J12 Pin6 || TXD || UART7\_TX || PI20
|-
| J12 Pin7 || GND || ||
|-
| J12 Pin8 || GND || ||
|-
|}

'''All GPIO define list:'''

[[File:BPI-M1_all_pin.png]]

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==
* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]

* schematic diagram:https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing
* BPI-M1 DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=

==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1HErsANQ4PsnwQJ-tH0AdTg
::Google Drive:

==Ubuntu Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive: https://drive.google.com/file/d/1WtPL8Hfr9aaE3VRnpgR_R7VYsc7O3Y9P/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1fM-in68EK_ABvSJ7XiY0Ag?pwd=yft7 (pincode: yft7)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2018-7-28 update :Ubuntu Server16.04 HDMI Version Image Link：
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive: https://pan.baidu.com/s/1GYH8oDK3T_WcUFn-0t9YmQ
::Google Drive: https://drive.google.com/open?id=13XTvWe90yvRdqNWiKCLZ0HcMgo33y2r6
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1Tw_99XBZVOmKyavNxCXv3w
::Google Drive:

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_BPI-M1_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1px0h0se8EiRuBiGGxT40hWpU3RWzPedK/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1Vclux6Wb-ToJGOaGQxV6Hg?pwd=m4a3 (pincode: m4a3)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google drive:https://drive.google.com/file/d/1uGYn3BZ9k1K1iqmmZhlCy6pXeeNwfU6P/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapi_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapi_jammy_edge_6.1.11.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1ZSFOd-nVFbAn_xB9AXckx9SEKQvnMB2J/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/12R8mIf7_45HDtruqEvktBw?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14446/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/bananapi/

==OpenWRT==
===Official OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*Gentoo Linux have officeal support banana pi BPI-M1, so you also can use on BPI-M1+,and BPI-R1, all is base on allwinner A20 chip.
*gentoo linux wiki : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M1

2023-03-22T06:35:47Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1]]
=Introduction=

[[File:Banana_pi_BPI-M1_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1_2.jpg|thumb|Overview]]
[[File:BPI-M1_3d.jpg|thumb|BPI-M1 3D ]]
[[File:White-2.JPG|thumb|BPI-M1 with plastic case]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]

The Banana Pi BPI-M1 is a business card-sized and low-power single-board computer featuring a high performance AllWinner A20 dual-core SoC at 1 GHz, 1 GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections. It can run a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

It is the first open source hardware launched by the banana pie team, and also a classic product with the largest cumulative sales of banana pie.There are still a lot of business clients that apply to various projects.A20 chip

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding.

[[File:A_BPI-M1.jpg]]

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV vide out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 26 PIN gpio

==Getting Start==
*[[Quick Start Banana pi SBC]]
*[[Getting Started with M1]]

=Hardware=
==Hardware interface==
[[File:BPI-M1_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1'''
|-
| CPU|| A20 ARM Cortex -A7 Dual-Core
|-
| GPU|| ARM Mali 400 MP2; Complies with OpenGL ES 2.0/1.1
|-
| Memory|| 1GB DDR3
|-
| Network|| 10/100/1000 Ethernet [[Modular connector|8P8C]] ([[1000BASE-T]])
|-
| Video Input|| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs|| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs|| 3.5mm jack and HDMI
|-
| Power Source|| 5 volts DC via Micro USB or GPIO
|-
| USB 2.0 ports|| 2 (direct from Allwinner A20 chip)
|-
| GPIO|| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED|| Power Key & 8P8C
|-
| Storage|| SATA 2.0,
|}

==GPIO PIN define ==

Banana Pi BPI-M1 has a 26-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:BPI-M1_26_pin.png]]

Note: 5V1,5V2 only support output,not support input

'''CSI Camera Connector specification:'''

CSI Camera Connector The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1'''
|-
| CSI GPIO Pin || Pin Name || GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT ||
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS GPIO of Banana pi BPI-M1'''
|-
| LVDS Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27 |
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26 |
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 || LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 ||LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J11 of Banana pi BPI-M1'''
|-
| J11 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || || Multi 1 || Multi 2
|-
| J11 Pin1 || TXD || UART0-TX || PB22
|-
| J11 Pin2 || RXD || UART0-RX || PB23
|-
|}

The jumper J12 provides the power source including 3.3V and 5V. There is a pair of UART TX/RX signals output here.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J12 of Banana pi BPI-M1'''
|-
| J12 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| J12 Pin1 || 5V || ||
|-
| J12 Pin2 || 3.3V || ||
|-
| J12 Pin3 || NC || IO-7 || PH5
|-
| J12 Pin4 || RXD || UART7\_RX || PI21
|-
| J12 Pin5 || NC ||IO-8 || PH3
|-
| J12 Pin6 || TXD || UART7\_TX || PI20
|-
| J12 Pin7 || GND || ||
|-
| J12 Pin8 || GND || ||
|-
|}

'''All GPIO define list:'''

[[File:BPI-M1_all_pin.png]]

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==
* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]

* schematic diagram:https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing
* BPI-M1 DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=

==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1HErsANQ4PsnwQJ-tH0AdTg
::Google Drive:

==Ubuntu Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive: https://drive.google.com/file/d/1WtPL8Hfr9aaE3VRnpgR_R7VYsc7O3Y9P/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1fM-in68EK_ABvSJ7XiY0Ag?pwd=yft7 (pincode: yft7)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2018-7-28 update :Ubuntu Server16.04 HDMI Version Image Link：
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive: https://pan.baidu.com/s/1GYH8oDK3T_WcUFn-0t9YmQ
::Google Drive: https://drive.google.com/open?id=13XTvWe90yvRdqNWiKCLZ0HcMgo33y2r6
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1Tw_99XBZVOmKyavNxCXv3w
::Google Drive:

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_BPI-M1_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1px0h0se8EiRuBiGGxT40hWpU3RWzPedK/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1Vclux6Wb-ToJGOaGQxV6Hg?pwd=m4a3 (pincode: m4a3)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google drive:https://drive.google.com/file/d/1uGYn3BZ9k1K1iqmmZhlCy6pXeeNwfU6P/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapi_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapi_jammy_edge_6.1.11.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1ZSFOd-nVFbAn_xB9AXckx9SEKQvnMB2J/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/12R8mIf7_45HDtruqEvktBw?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14446/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/bananapi/

==OpenWRT==
===Official OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*Gentoo Linux have officeal support banana pi BPI-M1, so you also can use on BPI-M1+,and BPI-R1, all is base on allwinner A20 chip.
*gentoo linux wiki : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Banana Pi BPI-M1

2023-03-22T06:35:25Z

Czj: /* Armbian image */

[[zh:香蕉派_BPI-M1]]
=Introduction=

[[File:Banana_pi_BPI-M1_1.jpg|thumb|Overview]]
[[File:Banana_pi_BPI-M1_2.jpg|thumb|Overview]]
[[File:BPI-M1_3d.jpg|thumb|BPI-M1 3D ]]
[[File:White-2.JPG|thumb|BPI-M1 with plastic case]]
[[File:MultiQB_front.jpg|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] : smart home gateway]]
[[File:IMG_3036.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :3G Information security terminal]]
[[File:IMG_3085.JPG|thumb|BPI-M1/M1+ for BPI 4.0 [[Successful case]] :4G Industrial safety tablets]]

The Banana Pi BPI-M1 is a business card-sized and low-power single-board computer featuring a high performance AllWinner A20 dual-core SoC at 1 GHz, 1 GB of DDR3 SDRAM, Gigabit Ethernet, SATA, USB, and HDMI connections. It can run a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

It is the first open source hardware launched by the banana pie team, and also a classic product with the largest cumulative sales of banana pie.There are still a lot of business clients that apply to various projects.A20 chip

Banana Pi is an open platform device, it is for anyone who wants to play and build with developer technology instead of simply using consumer technology. Backed by our community, starting a project and building servers is fun and rewarding.

[[File:A_BPI-M1.jpg]]

==Key Features==

* Allwinner A20 Dual-core 1.0GHz CPU
* Mali-400 MP2 with Open GL ES 2.0/1.1.
* 1 GB DDR3 memory.
* 1x SATA interface.
* 1x Gigabit LAN
* 1x USB otg and 2x USB 2.0
* 1X MIC
* AV vide out
* HDMI out
* IR
* CSI camera interface
* DSI display interface
* 26 PIN gpio

==Getting Start==
*[[Quick Start Banana pi SBC]]
*[[Getting Started with M1]]

=Hardware=
==Hardware interface==
[[File:BPI-M1_interface.jpg]]

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Banana Pi BPI-M1'''
|-
| CPU|| A20 ARM Cortex -A7 Dual-Core
|-
| GPU|| ARM Mali 400 MP2; Complies with OpenGL ES 2.0/1.1
|-
| Memory|| 1GB DDR3
|-
| Network|| 10/100/1000 Ethernet [[Modular connector|8P8C]] ([[1000BASE-T]])
|-
| Video Input|| A CSI input connector allows for the connection of a designed camera module
|-
| Video Outputs|| HDMI, CVBS, LVDS/RGB
|-
| Audio Outputs|| 3.5mm jack and HDMI
|-
| Power Source|| 5 volts DC via Micro USB or GPIO
|-
| USB 2.0 ports|| 2 (direct from Allwinner A20 chip)
|-
| GPIO|| GPIO, UART, I2C BUS, SPI BUS, WITH TWO CHIP SELECTS, [[CAN bus]], ADC, PWM, +3.3V, +5V, GND
|-
| LED|| Power Key & 8P8C
|-
| Storage|| SATA 2.0,
|}

==GPIO PIN define ==

Banana Pi BPI-M1 has a 26-pin GPIO header . Following is the Banana Pi GPIO Pinout:

[[File:BPI-M1_26_pin.png]]

Note: 5V1,5V2 only support output,not support input

'''CSI Camera Connector specification:'''

CSI Camera Connector The CSI Camera Connector is a 40-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin definitions of the CSI interface are shown as below. This is marked on the Banana Pi board as “CON1″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''40 PIN GPIO of Banana pi BPI-M1'''
|-
| CSI GPIO Pin || Pin Name || GPIO
|-
| CON1 P01 || LINEINL ||
|-
| CON1 P02 || LINEINR ||
|-
| CON1 P03 || VCC-CSI ||
|-
| CON1 P04 || ADC\_X1 ||
|-
| CON1 P05 || GND ||
|-
| CON1 P06 || ADC\_X2 ||
|-
| CON1 P07 || FMINL ||
|-
| CON1 P08 || ADC\_Y1 ||
|-
| CON1 P09 || FMINR ||
|-
| CON1 P10 || ADC\_Y2 ||
|-
| CON1 P11 || GND ||
|-
| CON1 P12 || CSI-FLASH || PH17
|-
| CON1 P13 || LRADC0 ||
|-
| CON1 P14 || TWI1-SDA || PB19
|-
| CON1 P15 || LRADC1 ||
|-
| CON1 P16 || TWI1-SCK || PB18
|-
| CON1 P17 || CSI-D0 || PE4
|-
| CON1 P18 || CSI0-STBY-EN || PH19
|-
| CON1 P19 || CSI0-D1 || PE5
|-
| CON1 P20 || CSI-PCLK || PE0
|-
| CON1 P21 || CSI-D2 || PE6
|-
| CON1 P22 || CSI0-PWR-EN || PH16
|-
| CON1 P23 || CSI-D3 || PE7
|-
| CON1 P24 || CSI0-MCLK || PE1
|-
| CON1 P25 || CSI-D4 || PE8
|-
| CON1 P26 || CSI0-RESET\# || PH14
|-
| CON1 P27 || CSI-D5 || PE9
|-
| CON1 P28 || CSI-VSYNC || PE3
|-
| CON1 P29 || CSI-D6 || PE10
|-
| CON1 P30 || CSI-HSYNC || PE2
|-
| CON1 P31 || CSI-D7 || PE11
|-
| CON1 P32 || CSI1-STBY-EN || PH18
|-
| CON1 P33 || RESET\# ||
|-
| CON1 P34 || CSI1-RESET\# || PH13
|-
| CON1 P35 || CSI-IO0 || PH11
|-
| CON1 P36 || HPR ||
|-
| CON1 P37 || HPL ||
|-
| CON1 P38 || IPSOUT ||
|-
| CON1 P39 || GND ||
|-
| CON1 P40 || IPSOUT ||
|-
|}

'''LVDS $LCD display interface$'''

The LVDS Connector is a 40-pin FPC connector which can connect external LCD panel $LVDS$ and touch screen $I2C$ module as well. The pin definitions of this connector are shown as below. This is marked on the Banana Pi board as “CON2″.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''LVDS GPIO of Banana pi BPI-M1'''
|-
| LVDS Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| CON2 P01 || IPSOUT$5V output$ || ||
|-
| CON2 P02 || TWI3-SDA || || PI1
|-
| CON2 P03 || IPSOUT$5V output$ || ||
|-
| CON2 P04 || TWI3-SCK || || PI0
|-
| CON2 P05 || GND || ||
|-
| CON2 P06 || LCD0-IO0 || || PH7
|-
| CON2 P07 || LCDIO-03 || || PH12
|-
| CON2 P08 || LCD0-IO1 || || PH8
|-
| CON2 P09 || LCD0-D0 || LVDS0-VP0 || PD0
|-
| CON2 P10 || PWM0 || || PB2
|-
| CON2 P11 || LCD0-D1 || LVDS0-VN0 || PD1
|-
| CON2 P12 || LCD0-IO2 || || PH9
|-
| CON2 P13 || LCD0-D2 || LVDS0-VP1 || PD2
|-
| CON2 P14 || LCD0-DE || || PD25
|-
| CON2 P15 || LCD0-D3 || LVDS0-VN1 || PD3
|-
| CON2 P16 || LCD0-VSYNC || || PD27 |
|-
| CON2 P17 || LCD0-D4 || LVDS0-VP2 || PD4
|-
| CON2 P18 || LCD0-HSYNC || || PD26 |
|-
| CON2 P19 || LCD0-D5 || LVDS0-VN2 || PD5
|-
| CON2 P20 || LCD0-CS || || PH6 |
|-
| CON2 P21 || LCD0-D6 || LVDS0-VPC || PD6
|-
| CON2 P22 || LCD0-CLK || || PD24
|-
| CON2 P23 || LCD0-D7 || LVDS0-VNC || PD7
|-
| CON2 P24 || GND || ||
|-
| CON2 P25 || LCD0-D8 || LVDS0-VP3 || PD8
|-
| CON2 P26 || LCD0-D23 || || PD23
|-
| CON2 P27 || LCD0-D9 || LVDS0-VN3 || PD9
|-
| CON2 P28 || LCD0-D22 || || PD22
|-
| CON2 P29 || LCD0-D10 || || PD10
|-
| CON2 P30 || LCD0-D21 || || PD21
|-
| CON2 P31 || LCD0-D11 || || PD11
|-
| CON2 P32 || LCD0-D20 || || PD20
|-
| CON2 P33 ||LCD0-D12 || || PD12
|-
| CON2 P34 || LCD0-D19 || || PD19
|-
| CON2 P35 || LCD0-D13 || || PD13
|-
| CON2 P36 || LCD0-D18 || || PD18
|-
| CON2 P37 || LCD0-D14 || || PD14
|-
| CON2 P38 || LCD0-D17 || || PD17
|-
| CON2 P39 || LCD0-D15 || || PD15
|-
| CON2 P40 || LCD0-D16 || || PD16
|-
|}

'''UART specification:'''

The jumper J11 is the UART interface. For developers of Banana Pi, this is an easy way to get the UART console output to check the system status and log message.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J11 of Banana pi BPI-M1'''
|-
| J11 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || || Multi 1 || Multi 2
|-
| J11 Pin1 || TXD || UART0-TX || PB22
|-
| J11 Pin2 || RXD || UART0-RX || PB23
|-
|}

The jumper J12 provides the power source including 3.3V and 5V. There is a pair of UART TX/RX signals output here.

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper J12 of Banana pi BPI-M1'''
|-
| J12 Pin || Pin Name || Multiplex Function Select || GPIO
|-
| || ||Multi 1 || Multi 2
|-
| J12 Pin1 || 5V || ||
|-
| J12 Pin2 || 3.3V || ||
|-
| J12 Pin3 || NC || IO-7 || PH5
|-
| J12 Pin4 || RXD || UART7\_RX || PI21
|-
| J12 Pin5 || NC ||IO-8 || PH3
|-
| J12 Pin6 || TXD || UART7\_TX || PI20
|-
| J12 Pin7 || GND || ||
|-
| J12 Pin8 || GND || ||
|-
|}

'''All GPIO define list:'''

[[File:BPI-M1_all_pin.png]]

=Software=

=Development=

==Basic Development==

=Resources=
==Source code==
* Linux kernel 3.4 Source code : https://github.com/BPI-SINOVOIP/BPI-M1-bsp

* Android 4.4 source code
:LCD7 type: https://github.com/BPI-SINOVOIP/BPI-A20-Android-4.4

* Android 4.2.2 source code
:HDMI type: https://github.com/BPI-SINOVOIP/BPI-A20-Android

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]

* schematic diagram:https://drive.google.com/drive/folders/0B4PAo2nW2KfnflVqbjJGTFlFTTd1b1o1OUxDNk5ackVDM0RNUjBpZ0FQU19SbDk1MngzZWM?resourcekey=0-ZRCiv304nGzvq-w7lwnpjg&usp=sharing
* BPI-M1 DXF file download link　:　[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfkd0QmxaU3F2bHBWdkFiS09vT3VoZkVyNW93OXFjM0dHRVdGazhRWmFzZDQ&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs google drive]
*BPI-M1 3D design file download link :[https://drive.google.com/folderview?id=0B4PAo2nW2Kfnfl95clI4ZzRKUmRENWhMcmwzUlVrYW1Ic3BXZENtUjJQcjk5TXc0RHBKdlU&usp=sharing&tid=0B4PAo2nW2Kfndjh6SW9MS2xKSWs　google drive]
*CE FCC RoHS : [https://bananapi.gitbooks.io/bpi-m1/content/en/bpi-m1_ce_fcc_rohs_certification.html BPI-M1 CE,FCC,RoHS ]
*Arch linux wiki for BPI-M1:https://wiki.archlinux.org/index.php/Banana_Pi
*Nas for BPI-M1/BPI-M1+ : https://www.hackster.io/jeffbaocai/bananapi-pro-nas-0815dc?ref=platform&ref_id=8064_popular___&offset=3
*NetBSD/evbarm on Allwinner SoCs : https://wiki.netbsd.org/ports/evbarm/allwinner/#index1h1
*Gentoo for banana pi : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way
*openSUSE for banana pi : https://en.opensuse.org/HCL:BananaPi
*How to booting from SSD using Lubuntu / Raspbian ：https://bananapi.gitbooks.io/bpi-m1/content/en/howtobootingfromssdusinglubunturaspbian.html
*Building the cluster on BPI :　https://www.hackster.io/Penguinfly/banana-pi-cluster-47d566
* Allwinner documents:
::allwinner chip online datasheet and documents: http://dl.linux-sunxi.org/

=Image Release=

==Android 4.4==
*2018-07-28 update android 4.4 LCD version image
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive:https://pan.baidu.com/s/1DfSIiMvW_I-kFjTZMtcVsA
::Google Drive: https://drive.google.com/open?id=1qcH9baIhOphsDdlH_yBADuBiZsvrSKnt
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1HErsANQ4PsnwQJ-tH0AdTg
::Google Drive:

==Ubuntu Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_jammy_edge_5.19.6_xfce_desktop.img
::Google Drive: https://drive.google.com/file/d/1WtPL8Hfr9aaE3VRnpgR_R7VYsc7O3Y9P/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1fM-in68EK_ABvSJ7XiY0Ag?pwd=yft7 (pincode: yft7)

*Banana Pi new image: Ubuntu 16.04 with Allwinner BSP, use MPV play 1080P video,Allwinner BSP kernel 3.4 , BPI-M2 Ultra/Berry use kernel 3.10
::google driver: https://drive.google.com/drive/folders/1DEO7JdMfDhHynC83K7JMxgnNxf1gV82S
::discuss on forum: https://forum.banana-pi.org/t/banana-pi-new-image-ubuntu-16-04-with-allwinner-bsp-use-mpv-play-1080p-video/13272

*2018-7-28 update :Ubuntu Server16.04 HDMI Version Image Link：
::Features Map:http://wiki.banana-pi.org/M1_Image_Map
::Baidu Drive: https://pan.baidu.com/s/1GYH8oDK3T_WcUFn-0t9YmQ
::Google Drive: https://drive.google.com/open?id=13XTvWe90yvRdqNWiKCLZ0HcMgo33y2r6
::Forum pthtread :http://forum.banana-pi.org/t/bananapi-m1-m1p-r1-new-image-release-20180728/6357

* Release Date: 2018-07-26
::Baidu Drive: https://pan.baidu.com/s/1Tw_99XBZVOmKyavNxCXv3w
::Google Drive:

==Debian Linux==

*2022-09-07 Armbian_22.11.0-trunk_Bananapi_BPI-M1_bullseye_edge_5.19.6_xfce_desktop.img
::Google Drive:https://drive.google.com/file/d/1px0h0se8EiRuBiGGxT40hWpU3RWzPedK/view?usp=sharing
::Baidu Cloud: https://pan.baidu.com/s/1Vclux6Wb-ToJGOaGQxV6Hg?pwd=m4a3 (pincode: m4a3)

*2019-9-18 update. Debian 10 buster mate desktop with grub support (boot-2019.07 + kernel 5.1.1)
::google drive:https://drive.google.com/file/d/1uGYn3BZ9k1K1iqmmZhlCy6pXeeNwfU6P/view?usp=sharing
::forum pthread:http://forum.banana-pi.org/t/bpi-m1-m1-r1-new-image-debian-10-buster-mate-desktop-with-grub-support-boot-2019-07-kernel-5-1-1/9916

== Armbian image ==
*Armbian_23.02.0-trunk_Bananapi_jammy_current_5.15.93.img.xz
*Armbian_23.02.0-trunk_Bananapi_jammy_edge_6.1.11.img.xz
::Baidu Cloud: https://pan.baidu.com/s/1hkkl22uVjvRct1V7N4OK2w?pwd=8888
::Google Drive: https://drive.google.com/drive/folders/1VpvVkYMqgmSnmfKXQSrEY2B6wRa-cggL?usp=share_link

*2022-12-06 Armbian_22.11.0-trunk_Bananapi BPI-M1_bullseye_edge_6.0.9.img.xz
::Google Drive:https://drive.google.com/file/d/1ZSFOd-nVFbAn_xB9AXckx9SEKQvnMB2J/view?usp=share_link
::Baidu Cloud:https://pan.baidu.com/s/12R8mIf7_45HDtruqEvktBw?pwd=8888 (pincode: 8888)
::Discuss on forum: https://forum.banana-pi.org/t/bananapi-bpi-m1-new-image-release-armbian-bullseye/14446/2

*Armbian Xenial and Armbian Jessie
::Image lownload link :https://www.armbian.com/bananapi/

==OpenWRT==
===Official OpenWRT===
*BPI-M1/BPI-M1+/BPI-R1 use A20 chip,so easy to run openwrt
*wiki : https://wiki.openwrt.org/toh/lamobo/r1
*openwrt support for allwinner :https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi
*image download : https://downloads.openwrt.org/chaos_calmer/15.05/sunxi/generic/uboot-sunxi-Lamobo_R1/
*opwrt for Allwinner Soc : https://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi?s[]=banana&s[]=pi

===BPI BSP for OpenWRT===
*How to build OpenWRT image from github : https://bananapi.gitbooks.io/bpi-m1/content/en/howtobuildopenwrtimagefromgithub.html

==FreeBSD==

FreeBSD on Allwinner (sunxi) systems for banana pi

Banana pi as the official partner of Allwinner , must banana pi product use Allwinner chip design . such as A20/A31S/H3/H2+/A64/A83T , and FreeBSD have support many Allwinner . so easy to use on banana pi board.
*Allwinner A20 (sun7i), a dual-core Cortex-A7 BPI-M1/BPI-M1+/BPI-R1
*Allwinner A31 and A31s (sun6i), a quad-core Cortex-A7 BPI-M2
*Allwinner A64 (sun50i), a quad-core Cortex-A53 BPI-M64
*Allwinner A83T (sun8i), an octa-core Cortex-A7 BPI-M3
*Allwinner H3 (sun8i), a quad-core Cortex-A7 BPI-M2+/BPI-M2+ EDU/

https://wiki.freebsd.org/FreeBSD/arm/Allwinner

==OpenSuse==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/opensuse.html

==OpenMediaVault==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/openmediavault.html

==Arch Linux==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/arch_linux.html

==Gentoo Linux==
*Gentoo Linux have officeal support banana pi BPI-M1, so you also can use on BPI-M1+,and BPI-R1, all is base on allwinner A20 chip.
*gentoo linux wiki : https://wiki.gentoo.org/wiki/Banana_Pi_the_Gentoo_Way

==RaspBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/raspbsdonbpi-m1.html

==CentOS==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/centos7linuxforbpi.html

==DietPi==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/dietpi.html

==FreeBSD/NetBSD==
*inmage and how to : https://bananapi.gitbooks.io/bpi-m1/content/en/freebsdnetbsd.html

==Lakka TV==
*Banana Pi M2+ with H3 chip
*Banana Pi M3 with A83T chip
*BPI-M1 and BPI-M1+ use A20 chip
*more about this : https://bananapi.gitbooks.io/bpi-m3/content/en/lakkatv.html

http://mirror.lakka.tv/nightly/

==Simplenas==
*simplenas image : https://simplenas.com/download/other/banana-pi-m1

=FAQ=

Getting Started with M3

2023-03-20T01:26:34Z

Czj: /* Load your image on M3 EMMC */

[[zh:快速上手香蕉派 BPI-M3]]
=Introduction=
==BPI-M3==
[[File:Banana_pi_BPI-M3_1.jpg|thumb|Overview: [[Banana Pi BPI-M3]]]]
[[File:M3_respbian.png|thumb|Overview: BPI-M3 respbian linux]]
[[File:BPI-m3_debian.jpg|thumb|Overview: BPI-M3 debian linux]]
[[File:Bpi-m3_ubutnu.jpg|thumb|Overview: BPI-M3 ubuntu linux]]

Banana Pi M3 is a super charged single board computer with an Octa-core processor and 2GB of RAM. Along side the elite processing unit, it features Gigabit Ethernet, 2 USB, SATA, WiFi, Bluetooth, and HDMI connection. It can run on a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

*Read more about : [[Banana Pi BPI-M3]]

===Key Features===
* Octa-core 1.8GHz Powerful CPU
* 2 GB LPDDR3 memory
* 8 GB eMMC storage
* WiFi & Bluetooth onboard

=Development For Android=
===Load your first image on M3===

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

1.You could download latest image from our forum.
Ex: http://wiki.banana-pi.org/Banana_Pi_BPI-M3#Android_5.1.1_V5

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

===Load your image on M3 EMMC===
1.The only different with sd card burning is the image burning mode item choice

[[Image:M3_Android_Emmc_Burning.png | 600px]]

2.After succeed to burn image to SD, then plug SD card in your M3

3.Press power button, device will copy image to EMMC automatically

[[Image:M3_Android_Emmc_Copy.png]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===How to buld M3 Bsp code===
* Prepare a PC which runs ubuntu
* Install Docker-ce on your PC，https://docs.docker.com/install/linux/docker-ce/ubuntu/#install-docker-ce (Install Docker Environment)
* After install Docker, execute "docker pull sinovoip/bpi-build:ubuntu12.04", to pull image (Pull Docker Image)
* Then you pulled image, execute "docker run --privileged -d -p 2222:22 -v /media:/media sinovoip/bpi-build:ubuntu12.04" (Create A Port To Login Docker Image)
* "ssh -p 2222 root@127.0.0.1 #default passwd is root" (Login In Docker Image)
* Execute "git clone https://github.com/BPI-SINOVOIP/BPI-M3-bsp.git" on your ubuntu terminal (Git Clone M3 Bsp Code)
* Execute "./build.sh" to build M3 bsp code (Build M3 Bsp Code)
* After built, open a new terminal, you could copy the compile files out of docker image by executing "docker cp <your container id>:<your project path> <your pc path>"

[[Image:docker_operate.png]]

=Development For Linux=
Let's get start to develop on BPI-M3, see amazing things happen.
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M3

[[Image:M3_console_interface.png | 600px]]

===Load your first image on M3===
1.You could download latest image from our forum
* Here is the example link: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-release-raspbian-jessie-8-0-2018-5-28-v1-1/5847

2.Install bpi-tools on your system. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into M3, and press power button setup M3

===Load your first image on M3 EMMC===
* Run your M3 with TF card
* Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
* Plug your USB disk in M3
* After M3 recognise USB disk, execute "bpi-copy xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to install image on EMMC
* Then power off M3, take TF card out, power on M3

===Update your image===
For example, update your image to support new emmc5.1

* execute “bpi-tools”, to update your bpi tools;
* execute “bpi-update -c bpi-m3.conf”, to download new driver to update your image
* execute “file *.tgz”, to check download files’ type is compressed data
* execute “bpi-bootsel”, you will see the bootloader path, “/usr/lib/u-boot/bananapi/bpi-m3/BPI_M3_720P.img.gz”
* execute “bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m3/BPI_M3_720P.img.gz”, to update your bootloader
* reboot

===Make your own image===
====Make one raspbian image====
* Prepare a SD card which have installed Raspbian system
* Boot your SD card with M3, after M3 finish starting, copy your files and config your Raspbian, then poweroff M3
* Plug your SD card in Linux PC, "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-m3.conf -c raspbian-jessie-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

==Advanced Development==
===Install Docker===
You could try armbian to install docker, here is the image: https://dl.armbian.com/bananapim3/Debian_stretch_dev.7z (Here Thanks for the armbian community)

Download this image to your ubuntu PC (I am using ubuntu PC), then decompress it

* 7z x Debian_stretch_xxx.img
* bpi-copy Debian_stretch_xxx.img /dev/sd< drive letter >

username: root, password: 1234

Here are steps to install docker:

* vim /etc/apt/sources.list

* add this source：“deb http://http.debian.net/debian jessie-backports main”

* apt-get update

* apt-get install docker.io

To have a test, if docker has installed in your image.

* sudo docker run --rm hello-world

===SATA===
1. Mount SATA on M3
* After insert sata interface, execute "fdisk -l"
* Then "mount /dev/sdx /mnt/xxx"
[[Image:M3_Sata.png]]

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===OTG===
1. On M3 console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up
[[Image:M2P_ADBD.png]]

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M3 and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M3 OTG
* If yes, we could execute "adb shell" to connect M3 by adb now
[[Image:M2P_ADBD_Shell.png]]

===LCD 5" & LCD 7"===
* Execute "bpi-bootsel", you'll see a list of boot files
* Find "BPI_M3_LCD7.img.gz"
* Then execute "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-M3/BPI_M3_LCD7.img.gz"
[[Image:M3_bootsel_lcd7.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M3 console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M3_Gmac_test.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:

[[Image:M3_bluetooth.png]]

===WiFi on M3===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640(The left one) camara and HDF8865(The right one).

[[Image:ov5640_camara.png]]
[[Image:ov8865_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview

====Shell====
'''Ov5640'''
* We also have built-in command in "/usr/local/bin" to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

'''Ov8865'''
* "/test_ov8865.sh"

===IR function===
* Execute "getevent"
* Use your IR device to send information to M3
[[Image:M3_IR.png]]

===BPI-Tools===
====Install Bpi-tools====
* Execute "curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - "

====Update Bpi-tools====
* Execute "bpi-tools"
[[Image: Bpi-tools.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===GPU===
* Execute "glmark2-es" to start OpenGL test
* glmark2 Score: 258
[[Image:M3_GPU_Test.png | 320px]]

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

==FAQ==

Getting Started with M3

2023-03-20T01:26:18Z

Czj: /* Load your first image on M3 */

[[zh:快速上手香蕉派 BPI-M3]]
=Introduction=
==BPI-M3==
[[File:Banana_pi_BPI-M3_1.jpg|thumb|Overview: [[Banana Pi BPI-M3]]]]
[[File:M3_respbian.png|thumb|Overview: BPI-M3 respbian linux]]
[[File:BPI-m3_debian.jpg|thumb|Overview: BPI-M3 debian linux]]
[[File:Bpi-m3_ubutnu.jpg|thumb|Overview: BPI-M3 ubuntu linux]]

Banana Pi M3 is a super charged single board computer with an Octa-core processor and 2GB of RAM. Along side the elite processing unit, it features Gigabit Ethernet, 2 USB, SATA, WiFi, Bluetooth, and HDMI connection. It can run on a variety of operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.

*Read more about : [[Banana Pi BPI-M3]]

===Key Features===
* Octa-core 1.8GHz Powerful CPU
* 2 GB LPDDR3 memory
* 8 GB eMMC storage
* WiFi & Bluetooth onboard

=Development For Android=
===Load your first image on M3===

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

1.You could download latest image from our forum.
Ex: http://wiki.banana-pi.org/Banana_Pi_BPI-M3#Android_5.1.1_V5

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

===Load your image on M3 EMMC===
1.The only different with sd card burning is the image burning mode item choice

[[Image:M3_Android_Emmc_Burning.png | 600px]]

2.After succeed to burn image to SD, then plug SD card in your M3

3.Press power button, device will copy image to EMMC automatically

[[Image:M3_Android_Emmc_Copy.png]]

* Download PhoenixCard: https://pan.baidu.com/s/18Fo_JhYY02gmxtFw2Ps3rQ

===How to buld M3 Bsp code===
* Prepare a PC which runs ubuntu
* Install Docker-ce on your PC，https://docs.docker.com/install/linux/docker-ce/ubuntu/#install-docker-ce (Install Docker Environment)
* After install Docker, execute "docker pull sinovoip/bpi-build:ubuntu12.04", to pull image (Pull Docker Image)
* Then you pulled image, execute "docker run --privileged -d -p 2222:22 -v /media:/media sinovoip/bpi-build:ubuntu12.04" (Create A Port To Login Docker Image)
* "ssh -p 2222 root@127.0.0.1 #default passwd is root" (Login In Docker Image)
* Execute "git clone https://github.com/BPI-SINOVOIP/BPI-M3-bsp.git" on your ubuntu terminal (Git Clone M3 Bsp Code)
* Execute "./build.sh" to build M3 bsp code (Build M3 Bsp Code)
* After built, open a new terminal, you could copy the compile files out of docker image by executing "docker cp <your container id>:<your project path> <your pc path>"

[[Image:docker_operate.png]]

=Development For Linux=
Let's get start to develop on BPI-M3, see amazing things happen.
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M3

[[Image:M3_console_interface.png | 600px]]

===Load your first image on M3===
1.You could download latest image from our forum
* Here is the example link: http://forum.banana-pi.org/t/banana-pi-bpi-m3-new-image-release-raspbian-jessie-8-0-2018-5-28-v1-1/5847

2.Install bpi-tools on your system. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into M3, and press power button setup M3

===Load your first image on M3 EMMC===
* Run your M3 with TF card
* Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
* Plug your USB disk in M3
* After M3 recognise USB disk, execute "bpi-copy xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to install image on EMMC
* Then power off M3, take TF card out, power on M3

===Update your image===
For example, update your image to support new emmc5.1

* execute “bpi-tools”, to update your bpi tools;
* execute “bpi-update -c bpi-m3.conf”, to download new driver to update your image
* execute “file *.tgz”, to check download files’ type is compressed data
* execute “bpi-bootsel”, you will see the bootloader path, “/usr/lib/u-boot/bananapi/bpi-m3/BPI_M3_720P.img.gz”
* execute “bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m3/BPI_M3_720P.img.gz”, to update your bootloader
* reboot

===Make your own image===
====Make one raspbian image====
* Prepare a SD card which have installed Raspbian system
* Boot your SD card with M3, after M3 finish starting, copy your files and config your Raspbian, then poweroff M3
* Plug your SD card in Linux PC, "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-m3.conf -c raspbian-jessie-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

==Advanced Development==
===Install Docker===
You could try armbian to install docker, here is the image: https://dl.armbian.com/bananapim3/Debian_stretch_dev.7z (Here Thanks for the armbian community)

Download this image to your ubuntu PC (I am using ubuntu PC), then decompress it

* 7z x Debian_stretch_xxx.img
* bpi-copy Debian_stretch_xxx.img /dev/sd< drive letter >

username: root, password: 1234

Here are steps to install docker:

* vim /etc/apt/sources.list

* add this source：“deb http://http.debian.net/debian jessie-backports main”

* apt-get update

* apt-get install docker.io

To have a test, if docker has installed in your image.

* sudo docker run --rm hello-world

===SATA===
1. Mount SATA on M3
* After insert sata interface, execute "fdisk -l"
* Then "mount /dev/sdx /mnt/xxx"
[[Image:M3_Sata.png]]

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===OTG===
1. On M3 console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up
[[Image:M2P_ADBD.png]]

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M3 and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M3 OTG
* If yes, we could execute "adb shell" to connect M3 by adb now
[[Image:M2P_ADBD_Shell.png]]

===LCD 5" & LCD 7"===
* Execute "bpi-bootsel", you'll see a list of boot files
* Find "BPI_M3_LCD7.img.gz"
* Then execute "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-M3/BPI_M3_LCD7.img.gz"
[[Image:M3_bootsel_lcd7.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M3 console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M3_Gmac_test.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:

[[Image:M3_bluetooth.png]]

===WiFi on M3===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640(The left one) camara and HDF8865(The right one).

[[Image:ov5640_camara.png]]
[[Image:ov8865_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview

====Shell====
'''Ov5640'''
* We also have built-in command in "/usr/local/bin" to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

'''Ov8865'''
* "/test_ov8865.sh"

===IR function===
* Execute "getevent"
* Use your IR device to send information to M3
[[Image:M3_IR.png]]

===BPI-Tools===
====Install Bpi-tools====
* Execute "curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - "

====Update Bpi-tools====
* Execute "bpi-tools"
[[Image: Bpi-tools.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===GPU===
* Execute "glmark2-es" to start OpenGL test
* glmark2 Score: 258
[[Image:M3_GPU_Test.png | 320px]]

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

==FAQ==

Getting Started with M2 Ultra & Berry

2023-03-20T01:19:17Z

Czj: /* Android */

[[zh:快速上手香蕉派 BPI-M2 Ultra / BPI-M2 Berry]]
=Introduction=
==BPI-M2U==
[[File:Banana_pi_BPI-M2_Ultra_4.JPG|thumb|Overview [[Banana Pi BPI-M2U ]]]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|Overview [[Banana Pi BPI-M2 Berry]]]]
[[File:M2p_respbian.png|thumb|Overview: BPI-M2U respbian linux]]

Banana Pi BPI-M2 Ultra is a quad-core mini single board computer built with Allwinner R40 SoC. It features 2GB of RAM and 8GB eMMC. It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 2 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2U]]

===Key Features===
* Quad Core ARM Cortex A7 CPU R40
* 2GB DDR3 SDRAM
* 8 GB eMMC storage
* WiFi (AP6212) & Bluetooth onboard
* SATA Interface

==BPI-M2 Berry==
Banana Pi BPI-M2 Berry is a quad-core mini single board computer built with Allwinner V40 SoC. It features 1GB of RAM . It also has onboard WiFi and BT. On the ports side, the BPI-M2 Ultra has 4 USB A 2.0 ports, 1 USB OTG port, 1 HDMI port, 1 audio jack, a DC power port, and last but not least, a SATA port..

*Read more about : [[Banana Pi BPI-M2 Berry]]

===Key Features===
* Quad Core ARM Cortex A7 CPU V40.
* 1GB DDR3 SDRAM.
* WiFi (AP6212) & Bluetooth onboard.
* SATA Interface

=Development=
Let's get start to develop on BPI-M2U, see amazing things happen.
==Basic Development==
===Linux===
* Prepare 8G/above TF card, USB-Serial interface, PC with Windows System
* Using your USB-Serial Connect debug console on M2P

1.You could download the latest image from our forum.
* Here is an example image link: http://forum.banana-pi.org/t/banana-pi-bpi-m2u-berry-new-image-release-raspbian-jessie-8-0-2018-5-24/5812.

2.Put the TF card into a TF-USB adapter and plug it to your PC USB interface.

3.Download the flashing tools "BalenaEtcher" and start it.

4.Click "Flash from file" to select your image file.(.img or .zip)

5.Click "Select target" to choose your USB device.

6.Start to flash and wait for burning completely.

[[Image:Etcher.jpg | 600px]]

===Android===
1.You could download latest image from our forum.

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===Load your first image on M2U EMMC===
1.Bootup your M2U with Micro SD card
2.Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
3.Plug your USB disk in M2U
4.Mount the USB disk and flash the image file to eMMC

* bpi-tools
curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools|sudo -E bash
mount /dev/sda1 /mnt
cd /mnt
bpi-copy xxx-sd-emmc-xxx.img.zip /dev/mmcblk0

* dd command
mount /dev/sda1 /mnt
cd /mnt
unzip -p xxx-sd-emmc-xxx.img.zip |pv| dd of=/dev/mmcblk0 bs=10M status=noxfer

5.Then power off M2U, take TF card out, power on M2U

==Advanced Development==
===How to build uboot & kernel===
====Install tools====
* apt-get udpate
* apt-get install gcc-arm-linux-gnueabihf u-boot-tools
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
====Clone code====
* git clone: https://github.com/BPI-SINOVOIP/BPI-M2U-bsp.git
* ./build.sh
===SATA===
1. Mount SATA on M2U

[[Image:M2U_Sata.png]]

* After insert sata interface, execute "fdisk -l"
[[Image:M2U_Sata_fdisk_l.png]]

* Then "mount /dev/sdx /mnt/xxx"

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===OTG===
1. On M2U console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up
[[Image:M2P_ADBD.png]]

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2U and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2U OTG
* If yes, we could execute "adb shell" to connect M2U by adb now
[[Image:M2P_ADBD_Shell.png]]

===LCD 5" & LCD 7"===
* Execute "bpi-bootsel", you'll see a list of boot files
* Find "BPI_M2U_LCD7.img.gz"
* Then execute "bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m2u/BPI_M2U_LCD7.img.gz"
[[Image:M2U_bootsel_lcd7.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M2U console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M2U_Gmac_test.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:

[[Image:M2U_bluetooth.png]]

===WiFi on M2U===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
====Shell====
* We also have built-in command in "/usr/local/bin" to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===IR function===
* Execute "getevent"
* Use your IR device to send information to M2U

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

===Install Qt5.7 & Qtcreator===
1.Prepare a 32Gb TF card

2.Use GParted to resize root point '/' as 32Gb

3.apt-get install libxcb*

4.download qt5.7

5.make & make install

6.apt-get install qtcreator

7.Config qtcreator

==FAQ==

=Reference Link=

http://www.banana-pi.org/m2plus.html

http://forum.banana-pi.org/

Getting Started with M2M

2023-03-20T01:18:45Z

Czj: /* Android */

[[zh:快速上手香蕉派 BPI-M2 Magic]]
=Introduction=
==BPI-M2M==
[[File:Banana_pi_bpi-m2_magic_5.JPG|thumb|Overview:[[Banana Pi BPI-M2M ]]]]
[[File:M2M_ubuntu.png|thumb|Overview: BPI-M2M ubuntu linux]]

Banana Pi M2M is another ARM SoC powered development board that offers great computing performance in an ultra portable form factor. It is a 51mm square with Allwinner A33 Quad-core A7 SoC and 512MB DDR3 RAM.

*Read more about : [[Banana Pi BPI-M2M]]

===Key Features===
* Quad Core ARM Cortex A7 CPU. R16
* 512MB DDR3 SDRAM
* WiFi (AP6212) & Bluetooth onboard

=Development=
==Android==
1.You could download latest image from our forum.

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

==Linux==
===Prepare===
:1. Prepare 8G/above TF card, USB-Serial cable.
:2. Connect USB-Serial to 40 pin header uart2 for kernel console debug.

:'''Note: three pin header uart0 beside usb port is not debug uart for bpi release images''' because SDcard and uart0 are multiplex pin and default bpi images support both SD and eMMC. If you want bootup with emmc only and enable uart0 as debug port without SDcard support, please refer to [http://wiki.banana-pi.org/Getting_Started_with_M2M#Enable_uart0_for_emmc_only_image_debug enable uart0 debug for emmc only image] section.

[[Image:M2M__debug_console.png | 240px]] [[Image:M2M__pin_define.png | 240px]]

:3. Install bpi-tools on your Linux PC, If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and download this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:4. Download [http://wiki.banana-pi.org/Banana_Pi_BPI-M2M#Linux_2 latest linux image], and confirm that the md5 checksum is correct.
:5. Defautl login: pi/bananapi or root/bananapi.

===Install Image to SDcard===
:1. Install image with bpi-tools on Linux, plug your sd card to your Linux PC
$ sudo bpi-copy xxx-bpi-m2m-xxx.img.zip /dev/sdX

:2. Install image with dd command on Linux, umount SDcard device /dev/sdX partitions if mounted automatically, Actually bpi-copy is the same as this dd command.

$ sudo apt-get install pv
$ sudo unzip -p xxx-bpi-m2m-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install bpi image with Etcher on Windows, Linux and MacOS
::[https://www.balena.io/etcher/ Balena Etcher] is an open source project by Balena, Flash OS images to SD cards & USB drives

===Install Image to EMMC===

:1. Prepare a SDcard with Linux image flashed and bootup the board with this SDcard.
:2. Copy emmc image to udisk, plugin the udisk to board and mount it.
:3. Install with bpi-tools command
$ sudo bpi-copy xxx-bpi-m2m-xxx.img.zip /dev/mmcblk1
:4. Or Install with dd command, umount mmcblk1p1 and mmcblk1p2 partition if mounted automatically, Actually bpi-copy is the same as this dd command
$ sudo apt-get install pv
$ sudo unzip -p xxxb-bpi-m2m-xxx.img.zip | pv | dd of=/dev/mmcblk1 bs=10M status=noxfer
:5. After flash complete, power off safely and eject the sdcard.

'''Note: If the emmc was flashed android image before, you must erase the boot partition of android before step 3 or step 4.'''

root@bpi-iot-ros-ai:/# echo 0 > /sys/block/mmcblk1/mmcblk1boot0/force_ro
root@bpi-iot-ros-ai:/# echo 0 > /sys/block/mmcblk1/mmcblk1boot1/force_ro
root@bpi-iot-ros-ai:/#
root@bpi-iot-ros-ai:/# dd if=/dev/zero of=/dev/mmcblk1boot0 bs=4096 count=1024
1024+0 records in
1024+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.421164 s, 10.0 MB/s
root@bpi-iot-ros-ai:/# dd if=/dev/zero of=/dev/mmcblk1boot1 bs=4096 count=1024
1024+0 records in
1024+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.428427 s, 9.8 MB/s

===Build Source Code ===
:1. Get the bsp source code

$ git clone https://github.com/BPI-SINOVOIP/BPI-M2M-bsp

:2. Build the bsp source code
::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M2M-bsp/blob/master/README.md README.md]

==Advance Development==

===Enable uart0 for emmc only image debug===
:1. Enable uart0 node and disable sdc0 node in sunxi-pack/sun8iw5p1/configs/BPI-M2M-LCD7/sys_config.fex.

--- a/sunxi-pack/sun8iw5p1/configs/BPI-M2M-LCD7/sys_config.fex
+++ b/sunxi-pack/sun8iw5p1/configs/BPI-M2M-LCD7/sys_config.fex
@@ -262,7 +262,7 @@ twi_sda = port:PE13<3><default><default><default>
;uart_type = 2:2 wire,4:4 wire,8:8 wire, full function
;----------------------------------------------------------------------------------
[uart0]
-uart_used = 0
+uart_used = 1
uart_port = 0
uart_type = 2
uart_tx = port:PF02<3><1><default><default>
@@ -803,7 +803,7 @@ led3_active_low = 1
; that supports SD3.0 cards and eMMC4.4+ flashes
;-------------------------------------------------------------------------------
[mmc0_para]
-sdc_used = 1
+sdc_used = 0
sdc_detmode = 3
sdc_buswidth = 4
sdc_d1 = port:PF00<2><1><2><default>

:2. Build the bsp source code.
:3. Copy the bootloader file SD/bpi-m2m/100MB/BPI-M2M-LCD7-8k.img.gz to udisk. bpi also provide a [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FImages%2FBPI-M2M%2FUbuntu16.04%2FBPI-M2M-LCD7-eMMC-only-uart0-debug-8k.img.gz prebuild bootloader] for this requirement.
:4. Bootup the m2m board from emmc, plugin the udisk and mount it.
:5. Flash the bootloader to emmc
$ sudo bpi-bootsel BPI-M2M-LCD7-8k.img.gz /dev/mmcblk0
:or
$ sudo gunzip -c BPI-M2M-LCD7-8k.img.gz | dd of=/dev/mmcblk0 bs=1024 seek=8
$ sync
$ sudo umount /dev/sda1

:6. Mout boot partition and set kernel debug console in uEnv.txt
$ sudo mount -t vfat /dev/mmcblk0p1 /mnt
: Change "console=ttyS2,115200" to "console=ttyS0,115200" in /mnt/bananapi/bpi-m2m/linux/lcd7/uEnv.txt
$ sudo umount /dev/mmcblk0p1

:7. Safely poweroff the board and connect debug uart to uart0 three pin header.

===Audio Path===
:1. 2-pin HP header output audio path

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''2-pin HP header output audio path'''
|-
|Number id|| Ctl_name || value
|-
| 1|| headphone volume|| 0-63
|-
| 104|| AIF1IN0L Mux|| AIF1_DA0L
|-
| 103|| AIF1IN0R Mux|| AIF1_DA0R
|-
| 100|| DACL Mixer AIF1DA0L Switch|| 1
|-
| 96|| DACR Mixer AIF1DA0R Switch|| 1
|-
| 78|| HP_R Mux|| DACR HPR Switch
|-
| 77|| HP_L Mux|| DACL HPL Switch
|-
| 105|| Headphone Switch|| 1
|}

:2. Mic 1 input audio path

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Mic 1 input audio path'''
|-
|Number id|| Ctl_name || value
|-
| 56|| AIF1OUT0L Mux|| AIF1_AD0L
|-
| 55|| AIF1OUT0R Mux|| AIF1_AD0R
|-
| 51|| AIF1 AD0L Mixer ADCL Switch|| 1
|-
| 47|| AIF1 AD0R Mixer ADCR Switch|| 1
|-
| 24|| ADCR Mux|| ADC
|-
| 25|| ADCL Mux|| ADC
|-
| 34|| LEFT ADC input Mixer MIC1 boost Switch|| 1
|-
| 27|| RIGHT ADC input Mixer MIC1 boost Switch|| 1
|-
| 4|| MIC1 boost amplifier gain|| 0-7
|}

:3.Alsa configuration file /var/lib/alsa/alsa.state.bpi-m2m already enable 2-pin HP output and Mic 1 input audio path, and restore by /var/lib/bananapi/bpi-autorun.d/S10-audio-bpi-m2m.sh after system bootup.

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:
[[Image:M2M_BT_bluetoothctl.png]]

===WiFi Client===
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
$ sudo su
# killall wpa_supplicant
# wpa_passphrase <ssid> <passphrase> > /etc/wpa_supplicant/wpa_supplicant.conf
# ifconfig wlan0 up
# iwlist wlan0 scan
# wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
# dhclient wlan0

There are some other command line ways, please google for them.

2. Use UI interface to setup WiFi Client

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview

====Shell====
* We also have built-in command in /usr/local/bin to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi.GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"
[[Image: WringPi_1602_LCD_m2m.png]]

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"
[[Image: WringPi_LED_Martix_m2m.png]]

Getting Started with M2P

2023-03-20T01:18:06Z

Czj: /* Development For Android */

[[zh:快速上手香蕉派 BPI-M2+]]
=Introduction=
[[File:Banana_pi_BPI-M2+_2.jpg|thumb|Overview: [[Banana Pi BPI-M2+ ]]]]
[[File:M2p_ubunu.jpg|thumb|Overview: BPI-M2+ Ubuntu linux]]
[[File:M2p_debian.jpg|thumb|Overview:BPI-M2+ Debian linux]]
[[File:Rasbian.jpg|thumb|Overview:BPI-M2+ Rasbian linux]]

Banana Pi M2+ is mini size development board that offers great computing performance in an ultra portable form factor.It is a 65mm*65mm fantastic mini size board with Allwinner H series chips. It comes with different versions but share the same interfaces.

*Read more about : [[Banana Pi BPI-M2+]]
*Burn image : [[Quick Start Banana pi SBC]]

==BPI-M2+ H3==
===Key Features===
* Quad-core 1.2GHz Cortex-A7 H3
* 1GB DDR3
* 8GB eMMC onboard
* WiFi and BlueTooth onboard
* 10/100/1000Mbps Ethernet Port

=Development For Android=
===Load your first image on M2P===

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

1.You could download latest image from our forum.
Ex: http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-image-android7-0-release-2018-6-30/6147

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

* Here is the example of M3

[[Image:M3_Android_Burning.png]]

===Load your image on M2P EMMC===
1.The only different with sd card burning is the image burning mode item choice

* Here is the example of M3

[[Image:M3_Android_Emmc_Burning.png]]

2.After succeed to burn image to SD, then plug SD card in your M2P

3.Press power button, device will copy image to EMMC automatically

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

=Development For Linux=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M2P

===Load your first image on M2P===
1.You could download latest image from our forum
* Here is the example forum thread link: http://forum.banana-pi.org/t/banana-pi-bpi-m2p-new-image-release-ubuntu-16-04-v1-1/5719

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into M2P, and press power button setup M2P.

5.Login user/password: pi/bananapi or root/bananapi.

===Load your first image on M2P EMMC===
* Run your M2P with TF card
* Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
* Plug your USB disk in M2P
* After M2P recognise USB disk, execute "bpi-copy xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to install image on EMMC
* Then power off M2P, take TF card out, power on M2P with EMMC

===Update your image===
For example, update your image to support new emmc5.1

* execute “bpi-tools”, to update your bpi tools;
* execute “bpi-update -c bpi-m2p.conf”, to download new driver to update your image
* execute “file *.tgz”, to check download files’ type is compressed data
* execute “bpi-bootsel”, you will see the bootloader path, “/usr/lib/u-boot/bananapi/bpi-m2p/BPI_M2P_720P.img.gz”
* execute “bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m2p/BPI_M2P_720P.img.gz”, to update your bootloader
* reboot

==Advanced Development==

===How to build uboot & kernel===
====Install tools====
* apt-get udpate
* apt-get install gcc-arm-linux-gnueabihf u-boot-tools
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
====Clone code====
* git clone: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp.git
* ./build.sh

===How to create an image ===
* Prepare a SD card which have installed system(Ubuntu/Raspbian/..)
* Boot your SD card with M2P, after M2P finish starting, copy your files and config your system, then poweroff M2P. [If you don't want to config your system, you can skip this step]
* Plug your SD card in PC(which is running Linux), "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-m2p.conf -c ubuntu-mate-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

===GPIO Control===
* To access a GPIO pin you first need to export it with
echo XX > /sys/class/gpio/export
* with XX being the number of the desired pin. To obtain the correct number you have to calculate it from the pin name (like PH18)
(position of letter in alphabet - 1) * 32 + pin number
for PH18 this would be ( 8 - 1) * 32 + 18 = 224 + 18 = 242 (since 'h' is the 8th letter)
* echo "out/in" > /sys/class/gpio/gpio*NUMBER*/direction
* echo "0/1" > /sys/class/gpio/gpio*NUMBER*/value

===OTG===
1. On M2P console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2P and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2P OTG
* If yes, we could execute "adb shell" to connect M2P by adb now

===GMAC===
* Use iperf3 to test gmac

[[Image:M2P_GMAC.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:
[[Image:M2P_BT_bluetoothctl.png]]

[[Image:M2P_BT.png]]

===WiFi on M2P===

Driver code:

*https://github.com/BPI-SINOVOIP/BPI_WiFi_Firmware

====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Change Logo===
1.Download M2P bsp code

* Execute command “git clone https://github.com/BPI-SINOVOIP/BPI-M2P-bsp”

* After you cloned project, execute command “cd BPI-M2P-bsp”

2.Change to your boot logo

* Prepare a ".bmp" picture, here I rotate 180°, as follows :

[[Image:M2P_CL_1.png]]

* Change your picture name as "bootlogo.bmp"
* put your picture to "sunxi-pack/chips/sun8iw7p1/configs/BPI-M2P-xxxP/"
Here I replaced “bootlogo.bmp” which is under
“sunxi-pack/chips/sun8iw7p1/configs/BPI-M2P-720P/” as an example：

[[Image:M2P_CL_2.png]]

3.Build your code

* "./build.sh BPI-M2P-720P"
* choose 1

[[Image:M2P_CL_3.png]]

* After you built the project, you will see “SD” directory

[[Image:M2P_CL_4.png]]

4.Install a raspbian image on your SD card

5.Plug your SD card into your Ubuntu PC

(1) check your SD card was recognised as /dev/sdxx, as you can see, mine sd card was recognised as /dev/sde

[[Image:M2P_CL_5.png]]

6.Then “cd SD/bpi-m2p/100MB”

7.Execute command “bpi-bootsel BPI-M2P-720P.img.gz /dev/sde”

[[Image:M2P_CL_6.png]]

8.Insert your updated SD card to board, and power on, you will see:

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
[[Image:guvcview_ov5640.png]]
====Shell====
* We also have built-in command in /usr/local/bin to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===IR function===
* Execute "getevent"
* Use your IR device to send information to M2P
[[Image:IR_getevent.png]]

===BPI-Tools===
====Install Bpi-tools====
* Execute "curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - "

====Update Bpi-tools====
* Execute "bpi-tools"
[[Image: Bpi-tools.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi.GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"
[[Image: WringPi_1602_LCD.png]]

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"
[[Image: WringPi_0.96_OLED.png]]

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"
[[Image: WringPi_LED_Martix.png]]

==FAQ==

=Reference Link=

http://www.banana-pi.org/m2plus.html

http://forum.banana-pi.org/

Getting Started with M2P

2023-03-20T01:17:42Z

Czj: /* Load your image on M2P EMMC */

[[zh:快速上手香蕉派 BPI-M2+]]
=Introduction=
[[File:Banana_pi_BPI-M2+_2.jpg|thumb|Overview: [[Banana Pi BPI-M2+ ]]]]
[[File:M2p_ubunu.jpg|thumb|Overview: BPI-M2+ Ubuntu linux]]
[[File:M2p_debian.jpg|thumb|Overview:BPI-M2+ Debian linux]]
[[File:Rasbian.jpg|thumb|Overview:BPI-M2+ Rasbian linux]]

Banana Pi M2+ is mini size development board that offers great computing performance in an ultra portable form factor.It is a 65mm*65mm fantastic mini size board with Allwinner H series chips. It comes with different versions but share the same interfaces.

*Read more about : [[Banana Pi BPI-M2+]]
*Burn image : [[Quick Start Banana pi SBC]]

==BPI-M2+ H3==
===Key Features===
* Quad-core 1.2GHz Cortex-A7 H3
* 1GB DDR3
* 8GB eMMC onboard
* WiFi and BlueTooth onboard
* 10/100/1000Mbps Ethernet Port

=Development For Android=
===Load your first image on M2P===
1.You could download latest image from our forum.
Ex: http://forum.banana-pi.org/t/bananapi-bpi-m2p-h3-new-image-android7-0-release-2018-6-30/6147

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

* Here is the example of M3

[[Image:M3_Android_Burning.png]]

===Load your image on M2P EMMC===
1.The only different with sd card burning is the image burning mode item choice

* Here is the example of M3

[[Image:M3_Android_Emmc_Burning.png]]

2.After succeed to burn image to SD, then plug SD card in your M2P

3.Press power button, device will copy image to EMMC automatically

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

=Development For Linux=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M2P

===Load your first image on M2P===
1.You could download latest image from our forum
* Here is the example forum thread link: http://forum.banana-pi.org/t/banana-pi-bpi-m2p-new-image-release-ubuntu-16-04-v1-1/5719

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into M2P, and press power button setup M2P.

5.Login user/password: pi/bananapi or root/bananapi.

===Load your first image on M2P EMMC===
* Run your M2P with TF card
* Copy "xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to your USB disk
* Plug your USB disk in M2P
* After M2P recognise USB disk, execute "bpi-copy xxx-sd-emmc-xxx.img.zip / xxx-sd-emmc-xxx.img" to install image on EMMC
* Then power off M2P, take TF card out, power on M2P with EMMC

===Update your image===
For example, update your image to support new emmc5.1

* execute “bpi-tools”, to update your bpi tools;
* execute “bpi-update -c bpi-m2p.conf”, to download new driver to update your image
* execute “file *.tgz”, to check download files’ type is compressed data
* execute “bpi-bootsel”, you will see the bootloader path, “/usr/lib/u-boot/bananapi/bpi-m2p/BPI_M2P_720P.img.gz”
* execute “bpi-bootsel /usr/lib/u-boot/bananapi/bpi-m2p/BPI_M2P_720P.img.gz”, to update your bootloader
* reboot

==Advanced Development==

===How to build uboot & kernel===
====Install tools====
* apt-get udpate
* apt-get install gcc-arm-linux-gnueabihf u-boot-tools
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
====Clone code====
* git clone: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp.git
* ./build.sh

===How to create an image ===
* Prepare a SD card which have installed system(Ubuntu/Raspbian/..)
* Boot your SD card with M2P, after M2P finish starting, copy your files and config your system, then poweroff M2P. [If you don't want to config your system, you can skip this step]
* Plug your SD card in PC(which is running Linux), "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-m2p.conf -c ubuntu-mate-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

===GPIO Control===
* To access a GPIO pin you first need to export it with
echo XX > /sys/class/gpio/export
* with XX being the number of the desired pin. To obtain the correct number you have to calculate it from the pin name (like PH18)
(position of letter in alphabet - 1) * 32 + pin number
for PH18 this would be ( 8 - 1) * 32 + 18 = 224 + 18 = 242 (since 'h' is the 8th letter)
* echo "out/in" > /sys/class/gpio/gpio*NUMBER*/direction
* echo "0/1" > /sys/class/gpio/gpio*NUMBER*/value

===OTG===
1. On M2P console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2P and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2P OTG
* If yes, we could execute "adb shell" to connect M2P by adb now

===GMAC===
* Use iperf3 to test gmac

[[Image:M2P_GMAC.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:
[[Image:M2P_BT_bluetoothctl.png]]

[[Image:M2P_BT.png]]

===WiFi on M2P===

Driver code:

*https://github.com/BPI-SINOVOIP/BPI_WiFi_Firmware

====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Change Logo===
1.Download M2P bsp code

* Execute command “git clone https://github.com/BPI-SINOVOIP/BPI-M2P-bsp”

* After you cloned project, execute command “cd BPI-M2P-bsp”

2.Change to your boot logo

* Prepare a ".bmp" picture, here I rotate 180°, as follows :

[[Image:M2P_CL_1.png]]

* Change your picture name as "bootlogo.bmp"
* put your picture to "sunxi-pack/chips/sun8iw7p1/configs/BPI-M2P-xxxP/"
Here I replaced “bootlogo.bmp” which is under
“sunxi-pack/chips/sun8iw7p1/configs/BPI-M2P-720P/” as an example：

[[Image:M2P_CL_2.png]]

3.Build your code

* "./build.sh BPI-M2P-720P"
* choose 1

[[Image:M2P_CL_3.png]]

* After you built the project, you will see “SD” directory

[[Image:M2P_CL_4.png]]

4.Install a raspbian image on your SD card

5.Plug your SD card into your Ubuntu PC

(1) check your SD card was recognised as /dev/sdxx, as you can see, mine sd card was recognised as /dev/sde

[[Image:M2P_CL_5.png]]

6.Then “cd SD/bpi-m2p/100MB”

7.Execute command “bpi-bootsel BPI-M2P-720P.img.gz /dev/sde”

[[Image:M2P_CL_6.png]]

8.Insert your updated SD card to board, and power on, you will see:

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
[[Image:guvcview_ov5640.png]]
====Shell====
* We also have built-in command in /usr/local/bin to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===IR function===
* Execute "getevent"
* Use your IR device to send information to M2P
[[Image:IR_getevent.png]]

===BPI-Tools===
====Install Bpi-tools====
* Execute "curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - "

====Update Bpi-tools====
* Execute "bpi-tools"
[[Image: Bpi-tools.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi.GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"
[[Image: WringPi_1602_LCD.png]]

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"
[[Image: WringPi_0.96_OLED.png]]

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"
[[Image: WringPi_LED_Martix.png]]

==FAQ==

=Reference Link=

http://www.banana-pi.org/m2plus.html

http://forum.banana-pi.org/

Getting Started with M2 Zero

2023-03-20T01:15:06Z

Czj: /* Load your first Android image on M1 */

[[zh:快速上手香蕉派 BPI-M2 Zero]]
=Introduction=
[[File:BPI-M2_zero_11.JPG|thumb|Overview [[Banana Pi BPI-M2 ZERO]]]]
[[File:M2Zero_raspbian.png|thumb|Overview: BPI-M2Z raspbian]]
[[File:BPI-M2_zero_android_4.4.JPG|thumb|Android 4.4]]
[[File:BPI-M2_zero_ubuntu.JPG|thumb|Ubuntu Linux]]

*Read more about : [[Banana Pi BPI-ZERO]]

==BPI-M2 Zero==

Banana Pi M2 Zero is an ultra compact single board computer measures only 60mm*30mm. It uses quad-core Cortex A7 allwinner H2+ processor, with 512MB RAM memory. It's ideal for light-weight systems with some space-limited applications. Like other members of Banana Pi, it supports both linux and android operating system.

===Key Features===
* Quad Core ARM Cortex A7 CPU H2+
* 512MB SDRAM.
* WiFi (AP6212) & Bluetooth onboard.
* Mini HDMI.

=Development=
==Basic Development==
===Load your first Android image on M2 Zero===
1.You could download latest image from our forum.

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M2 Zero

[[Image:Debug_console_wire.png]]

[[Image:M2_Zero_debug_console.png]]

===Install Linux Image on M2 Zero===
Download [http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO#Linux latest Linux image], default login user/password is pi/bananapi or root/bananapi.

Install Image to SDcard on Linux PC with bpi-tools
:1. Install bpi-tools on your system
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash
:If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.

:2. Insert your SDcard into your PC
$ bpi-copy xxx.img /dev/sdx

Install Image to SDcard with Ether on Windows, Linux and MacOS
:[https://www.balena.io/etcher/ Balena Etcher] is an open source project by Balena, Flash OS images to SD cards & USB drives

Install Image to EMMC with SD Ubuntu
:1.Prepare a sd which is installed ubuntu image and bootup with sdcard
:2.Copy emmc image to udisk, plug in board, then mount udisk.
:3.After mount udisk, use command "bpi-copy xxx-emmc-xxx.img" to install image on Emmc.
:4.After success install, power off the board, eject the sdcard and poweron with emmc boot.

===Update your image===
:1. Get the m2 zero bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M2P-bsp-4.4

:2. Build the source code according to the README.md, and update the packages to the sdcard with bpi image flashed.
==Advanced Development==

===How to create an image ===
* Prepare a SD card which have installed system(Ubuntu/Raspbian/..)
* Boot your SD card with M2 Zero, after M2 Zero finish starting, copy your files and config your system, then poweroff M2 Zero. [If you don't want to config your system, you can skip this step]
* Plug your SD card in PC(which is running Linux), "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-m2z.conf -c ubuntu-mate-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

===OTG===
1. On M2 Zero console:
* Execute "./adbd.sh", then execute "ps -ax | grep adbd" to see if adbd is set up

2. On PC terminal:
* If adbd was succeed to set up, insert OTG-USB interface to M2 Zero and PC(with Ubuntu system)
* Execute "adb devices" to see if PC has recognised M2 ZeroP OTG
* If yes, we could execute "adb shell" to connect M2 Zero by adb now

===USB Ethernet===
* Prepare a USB to OTG wire, usb ethernet adapter

[[Image:M2Zero_usb_network_wire.png]]

* Use iperf3 to test network
[[Image:M2Zero_network.png]]

===Bluetooth===
* Use bluetoothctl tool to operate BT
* Execute "bluetoothctl"
* If you don't know how to use bluetoothctl, type "help", you will see more commands
* Execute these commands:
[[Image:M2Zero_bluetooth.png]]

===WiFi Client===
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===Camara function===
We use HDF5640 camara.

[[Image:ov5640_camara.png]]
====Guvcview====
* Use your UI interface to operate camara
* Applications -> Sound & Video -> guvcview
====Shell====
* We also have built-in command in /usr/local/bin to test camara
* "./test_ov5640_image_mode.sh" to test picture taking function
* "./cameratest.sh" to test video recording function

===Display===
====How to change display resolution====
For Example： we change M2Z HDMI display 1080P.

1. First, mount /dev/mmcblk0p1 /mnt, then enter to /mnt/bananapi/bpi-m2z/linux, find "sys_config.fex";

2. "vim sys_config.fex", change "screen0_output_mode = 5" to "screen0_output_mode = 10"

[[Image: display_output.png]]

3. After save changed, use "fex2bin" command to transfer sys_config.fex to bin file, "fex2bin sys_config.fex script.bin ", reboot.

parameters meaning：

[[Image: display_mode.png]]

===BPI-Tools===
====Install Bpi-tools====
* Execute "curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - "

====Update Bpi-tools====
* Execute "bpi-tools"
[[Image: Bpi-tools.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WiringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====How to Update WiringPi====
* Execute "bpi-update -c pkglist.conf"
[[Image: Update_Pkglist.png]]

* Execute "bpi-update -c bpi-pkg-bpi-wiringpi.conf"
[[Image: Update_WringPi.png]]

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====0.96 Inch OLED Display====
* Execute "/usr/local/bin/bpi_test_52pi.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

Getting Started with M1P

2023-03-20T01:13:17Z

Czj: /* Load your first image on M1+ */

[[zh:快速上手香蕉派 BPI-M1+]]
=Introduction=
==BPI-M1P==
[[File:Banana_pi_BPI-M1+_1.jpg|thumb|Overview [[Banana Pi BPI-M1+ ]]]]
[[File:M1P_ubuntu.png|thumb|Overview: BPI-M1P ubuntu linux]]

The Banana Pi M1+ features onboard WiFi g/b/n. The board supports all classic projects and even more because of the onboard WIFi chip. Like its sibling, it can run operating systems including Android, Lubuntu, Ubuntu, Debian, and Raspbian.
The Banana Pi M1+ is our upgraded M1 board. We feel like the onboard WiFi adds a lot more features to the board and makes it more convient for users to set up their linx desktop or router projects.

*Read more about : [[Banana Pi BPI-M1+]]

===Key Features===
* Dual-core 1.0GHz CPU
* 1 GB DDR3 memeory
* Mali-400 MP2 with Open GL ES 2.0/1.1
* WiFi onbaord

=Development=
Let's get start to develop on BPI-M1P, see amazing things happen.
==Linux==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with windows System
* Using your USB-Serial Connect debug console on M1P
===Load the linux image on M1+===
1.Download the latest image from the forum.

2.Put the TF card into a card reader and plug it to your PC USB interface.

3.Download the flashing tools "BalenaEtcher" and start it.

4.Click "Flash from file" to select your image file.(.img or .zip)

5.Click "Select target" to choose your USB device.

6.Start to flash and wait for a moment.

[[Image:Etcher.jpg | 600px]]

==Android==
===Load your first image on M1+===
1.You could download latest image from our forum.
Ex:

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

==Advanced Development==
===SATA===
1. Mount SATA on M1P
* After insert sata interface, execute "fdisk -l"
* Then "mount /dev/sdx /mnt/xxx"
[[Image:M1P_Sata.png]]

2. If you meet some errors when you mount SATA, try these following commands:

* "fdisk /dev/sdx" to create new partition , set your partition numbers and size, after created partitions, input "wq" to save and quit.
* "mkfs.ext2 /dev/sdx" to format the SATA
* "mount /dev/sdx /mnt/xxx"

3. After you success to insert SATA, we could input following commands to test SATA interface:
* "time dd if=/dev/xxx of=/dev/null bs=1M count=1000" to test read speed
* "time dd if=/dev/zero of=/dev/sdx bs=1M count=1000" to test write speed
[[Image:Sata_test.png]]

===Touch screen===

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On M1P console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:M1P_Gmac_test.png]]

===WiFi on M1P===
====WiFi Client====
'''You have two ways to setup WiFi Client'''

1. Use commands to setup WiFi client
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

2. Use UI interface to setup WiFi Client

===Clear boot===
* git clone https://github.com/BPI-SINOVOIP/BPI-files/tree/master/SD/100MB
* bpi-bootsel BPI-cleanboot-8k.img.gz /dev/sdX

===IR function===
* Execute "getevent"
* Use your IR device to send information to M1P
[[Image:M1P_IR.png]]

===RPi.GPIO===
====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi,GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./bpi_test_g40.py" to test RPi.GPIO

[[Image: RPi_GPIO.png]]

===WringPi===
* GitHub: https://github.com/BPI-SINOVOIP/BPI-WiringPi2.git
* We also have built-in test command in "/usr/local/bin"

====RGB 1602 LCD====
* Execute "/usr/local/bin/bpi_test_lcd1602.sh"

====8x8 RGB LED Martix====
* Firstly you need a GPIO Extend Board for 8x8 LED Martix
[[Image: WringPi_LED_Martix_Extend_Board.png]]

* Execute "/usr/local/bin/bpi_test_gpio40.sh"

===File System===
* read only system change to read & write mode: "mount -o remount,rw /"

===Install QT===
* sudo apt-get install build-essential
* sudo apt-get install libgl1-mesa-dev
* sudo apt-get install libglu1-mesa-dev
* sudo apt-get install freeglut3-dev
* sudo apt-get install cmake
* sudo apt-get install qt5-default qtcreator

===A20 CAN Bus===

In order to port [https://sourceforge.net/projects/can4linux/ can4linux] to the BananaPi, the CAN module description is needed from the A20 hardware manual. can4linux is a character-driver-based Linux driver used already on desktop PCs and embedded platforms like Freescale FlexCAN (the i.MX series of micro controllers) or Xiliny Zynq.

There is a more detailed document about CAN on the A20 at: https://dl.linux-sunxi.org/A20/CAN%20Bus1.pdf

This is a tutorial for using CAN BUS on bananapi with bananian 15-01

Thank selqcir share this example:

*Download and install "bananian-1501.img" into 8 GB SDCard.
*Expand the root file system using "bananian-config"
*Install missing package:
apt-get install git
apt-get update
apt-get upgrade
reboot
*Get last bananian available, and continu to install missing package:
git clone https://github.com/Bananian/linux-bananapi
apt-get install build-essential u-boot-tools uboot-mkimage
apt-get install libusb-1.0-0 libusb-1.0-0-dev git wget fakeroot kernel-package zlib1g-dev libncurses5-dev
apt-get install subversion
*Build kernel:
cd linux-bananapi
make menuconfig
*Exit without saving when menu appears
zcat /proc/config.gz > /root/linux-bananapi/.config
make uImage modules
make INSTALL_MOD_PATH=output modules_install
*At this step, kernel should be compiled and "Module.symvers" should be available
*Then rename modules and firmware provide by Bananian, and replace by the new one.
mv /lib/modules /lib/modules.old
mv /lib/firmware /lib/firmware.old
mv /root/linux-bananapi/output/lib/modules /lib/modules
mv /root/linux-bananapi/output/lib/firmware /lib/firmware
*Same for uImage:
mount /dev/mmcblk0p1 /mnt
cd /mnt
mv uImage uImage.old
mv /root/linux-bananapi/arch/arm/boot/uImage /mnt
reboot
*Create link for further build:
cd /lib/modules/3.4.104/
ln -s /root/linux-bananapi build
cd ~
*Get Can4Linux and build it:
svn checkout https://svn.code.sf.net/p/can4linux/code/trunk can4linux-code
cd /root/can4linux-code/can4linux/
make TARGET=BANANAPI
*Install module for each startup of the board:
insmod can4linux.ko
cp can4linux.ko /lib/modules/3.4.104/kernel/net/can/
depmod -A -v
modprobe -v can4linux
echo "" >> /etc/modules ; echo "can4linux" >> /etc/modules
reboot
*Build CAN example
apt-get install swig
apt-get install python-dev
cd can4linux-code/can4linux-examples/
*Update CAN speed and device in file "pyCan-example.py"
# setting the device number
device = 0
defaultBaudrate = '250'
*Connect CAN transceiver and CAN bus, and check with for example:
python pyCan-example.py

That's all

With this method, kernel version is "Linux bananapi 3.4.104" instead of "Linux bananapi 3.4.104+", because i was unable to find same sources than Bananian 15-01 , but CAN bus work !

==FAQ==

Getting Started with M1

2023-03-20T01:11:39Z

Czj: /* Load your first image on M1 */

[[zh:快速上手香蕉派 BPI-M1]]
=Introduction=
==BPI-M1==
[[File:Banana_pi_BPI-M1_1.jpg|thumb|Overview [[Banana Pi BPI-M1]]]]
[[File:Banana_pi_BPI-M1_2.jpg|thumb|Overview]]
[[File:BPI-M1_3d.jpg|thumb|BPI-M1 3D ]]

The Banana Pi M1 is our first product in our goal of creating an open source devlopment board community. With a Banana Pi, we want you to explore and experience the world of DIY projects and portable computing. We welcome all companies, DIYers, and tech loving people within our community! Together, we can make a difference, we can discover our passions, inspire others, and build a practical project

*Read more about : [[Banana Pi BPI-M1]]

===Key Features===
* Dual-core 1.0GHz CPU
* 1 GB DDR3 memeory
* Mali-400 MP2 with Open GL ES 2.0/1.1

=Development For Armbian=
===Basic requirements===

x86_64 or aarch64 machine with at least 2GB of memory and ~35GB of disk space for a virtual machine, container or bare metal installation
Ubuntu Jammy 22.04.x amd64 or aarch64 for native building or any Docker capable amd64 / aarch64 Linux for containerised

apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh

===Latest images===

https://www.armbian.com/bananapi/

=Development For Android=
===Load your first image on M1===
1.You could download latest image from our forum.
Ex:

2.Put your TF card into a TF-USB adapter, and then plug adapter in your Windows PC usb interface.

3.Prepare your image, and download image burning tools PhoenixCard.exe.

4.Use "PhoenixCard.exe" to burn android image to TF card.

[[Image:M3_Android_Burning.png | 600px]]

* Download PhoenixCard: https://pan.baidu.com/s/1-fjvPqtG_zewVzqnXf1AHw?pwd=eid9

===How to buld M1 Bsp code===
* Prepare a PC which runs ubuntu
* Install Docker-ce on your PC，https://docs.docker.com/install/linux/docker-ce/ubuntu/#install-docker-ce
* After install Docker, execute "docker pull sinovoip/bpi-build-android:a20_01", to pull image
* Then you pulled image, execute "docker run --privileged -d -p 2223:22 -v /media:/media sinovoip/bpi-build-android:a20_01"
* "ssh -p 2223 root@127.0.0.1 #default passwd is root"
* Execute "git clone https://github.com/BPI-SINOVOIP/BPI-M1-bsp.git" on your ubuntu terminal
* Execute "./build.sh" to build M1 bsp code
* After built, open a new terminal, execute "docker cp xxxxx(your container id):xxxxx(your project path) xxxxx(your pc path)"

[[Image:docker_operate.png]]

=Development For Linux=
===Load the linux image on M1===
1.Download the latest image from the forum.

2.Put the TF card into a card reader and plug it to your PC USB interface.

3.Download the flashing tools "BalenaEtcher" and start it.

4.Click "Flash from file" to select your image file.(.img or .zip)

5.Click "Select target" to choose your USB device.

6.Start to flash and wait for a moment.

[[Image:Etcher.jpg | 600px]]

Let's get start to develop on BPI-M1, see amazing things happen.
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, PC with Ubuntu System
* Using your USB-Serial Connect debug console on M1

[[Image:Debug_console_wire.png]]

[[Image:M1_uart_pins.png | 600px]]

[[Image:M1_console_interface.png | 600px]]

===Load your first image on M1===
1.You could download latest image from our forum
* Here is the example link:

2.Install bpi-tools on your system. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card.

4.After step 3, then you can insert your TF card into M1, and press power button setup M1

===Update your image===
* execute “bpi-tools”, to update your bpi tools;
* execute “bpi-update -c bpi-m1.conf”, to download new driver to update your image
* execute “file *.tgz”, to check download files’ type is compressed data
* execute “bpi-bootsel”, you will see the bootloader path, “/usr/lib/u-boot/bananapi/u-boot-2018.01/u-boot-2018.01-bpi-m1-8k.img.gz”
* execute “bpi-bootsel /usr/lib/u-boot/bananapi/u-boot-2018.01/u-boot-2018.01-bpi-m1-8k.img.gz”, to update your bootloader
* reboot

Banana Pi BPI-R3

2023-03-07T08:18:33Z

Czj: /* FAQ */

[[zh:香蕉派 BPI-R3]]
=Summary=
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-R3_3.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-R3_with_PoE.jpg|thumb|[[Banana Pi BPI-R3]] with PoE function support]]
[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]
[[File:BPI-R64_3.JPG|thumb|[[Banana Pi BPI-R64]] with MediaTek MT7622]]
[[File:BPI-R2_3.JPG|thumb|[[Banana Pi BPI-R2]] with MTK MT7623N chip design]]
[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTK1296 chip design]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] with allwinner A20 chip design]]
[[File:Bpi-r3_Metal_case.jpg|thumb|[[Banana Pi BPI-R3 ]] Metal case ]]

==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi6 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi6 connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6 has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Application direction==
*. Internet service Router
*. Wireless Router
*. Wireless Repeater
*. Home security Gateway
*. Home Automation
*. Nas device
*. Network and communication applications

==Key Features==
*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interfact
*. 26 PIN GPIO

==Getting Start==
*[[Getting Started with BPI-R3]]

=Hardware=
==Hardware interface==
[[File:BPI-R3_interface_750.jpg]]

==Jumper setting==
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Jumper Setting of Banana pi BPI-R3'''
|-
| Jumper Setting || SW1 || SW2|| SW5 || SW6
|-
| SPIM-NoR || Low || Low|| Low || X
|-
| SPIM-Nand || High || Low|| High || X
|-
| eMMC || Low || High|| High || Low
|-
| SD card || High || High|| X || High
|-
|}

==Hardware spec==

{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-R3'''
|-
| CPU ||MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
|-
| SDRAM || 2 GB DDR4
|-
| On board Storage || MicroSD $TF$ card,8GB eMMC onboard
|-
| GPIO || 26 Pin GPIO,some of which can be used for specific functions including UART, I2C, SPI, PWM, I2S.
|-
| On board Network || 5 Port 10/100/1000Mbps Ethernet
|-
| SFP || 2 SFP 2.5GbE
|-
| Wifi || Wifi 6 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
|-
| mini PCIE||Mini PCIe via USB
|-
|M.2 interface ||M.2 KEY-M PCIe inerface
|-
| USB || 1 USB 3.0 host ,2 USB interface with slot.
|-
| Buttons || Reset button,WPS botton, boot switch
|-
| Leds || Power status Led and RJ45 Led
|-
| DC Power || 12V/2A with DC in
|-
| Sizes || 100.5x148mm same as [[Banana Pi BPI-R64]] and [[Banana Pi BPI-R2]]
|-
| Weight || 200g
|-
|}

=Resources=
==Source code==
https://github.com/BPI-SINOVOIP/BPI-R3-OPENWRT-V21.02.3

Notes:
Baidu link: https://pan.baidu.com/s/1JSQ7wJTCeK4JqWR_XB-LLQ?pwd=6vdb (Pincode: 6vdb)
Google link:https://drive.google.com/file/d/13nQMfM0_XTyWcILhNxv_9E4TIvb65RI0/view?usp=sharing

==Documents==
*BPI-R3 DXF file : https://drive.google.com/file/d/1bc5mCtJlnPi84q7VZYaQkZhRUU4HUfUd/view?usp=sharing
*BPI-R3 schematic diagram : https://drive.google.com/file/d/1mxKb8CBbnzfNSd_4esmcX_NovxaXjEb8/view?usp=sharing
*MT7986A_Datasheet_1.15 : https://drive.google.com/file/d/1t_nuPTeoAcFb1dmEe4kJVlLWdHcAA6OB/view?usp=sharing
*MT7986A_Reference_Manual_for_BPI-R3 : https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing
*[Tutorial] Build, customize and use MediaTek open-source U-Boot and ATF : https://forum.banana-pi.org/t/tutorial-build-customize-and-use-mediatek-open-source-u-boot-and-atf/13785
*BPI-R3 OpenSource Routerboard how to burn and test imagehttps://www.youtube.com/watch?v=Xaf_SC7fPDM
*BPI-R3 CE,FCC,RoHS certificate : https://banana-pi.org/en/bpi-honor/
*Banana Pi BPI-R3 Review: Details, Pricing, & Features : https://androidpimp.com/embedded/banana-pi-bpi-r3-router-board/?fbclid=IwAR1G4cEco5iULwKG-C-n8MIiWOWZMhPborqmCzS2d3KIHx-eNQS-54lZnps
*Update OpenWrt to 22.03.3 SNAPSHOT:https://forum.banana-pi.org/t/bananapi-bpi-r3-update-openwrt-to-22-03-3-snapshot/14984

=Release image=
==OpenWRT==
*2022-06-01udptae BPI-R3 OpenWRT 21.02 linux kernel 5.4, wifi 6 2.4G and 5G working fine support nand flash ,SD card ,eMMC flash boot. for BPI-R3 production version hardware
::Google drive :https://drive.google.com/file/d/18_xst-diDdCg7CeSum1M5FDbbo31jFJq/view?usp=drivesdk
::Baidu link: https://pan.baidu.com/s/1idqU1-bB4XD1LTGDAJxRGA?pwd=chez Pincode: chez
::Discuss on forum : https://forum.banana-pi.org/t/banana-pi-bpi-r3-openwrt-image/13236

*2022-09-28 udptae BPI-R3 OpenWRT 21.02 linux kernel 5.4, wifi 6 2.4G and 5G working fine support nand flash ,SD card ,eMMC flash boot, support EC25 LTE 4G
Modules for BPI-R3 production version hardware
::Google drive: https://drive.google.com/file/d/1oNcnIl8bDla9pPWUd-TFPXXphsCMsJt0/view?usp=sharing
::Baidu link: https://pan.baidu.com/s/1v4sKfAuax3AfHNtp_2RP_g?pwd=mebq (Pincode: mebq)

==Debian==

*[BPI-R3] Debian Bullseye Image, this image is share by Frank:
::https://forum.banana-pi.org/t/bpi-r3-debian-bullseye-image/14541

* 2022-12-18-debian-11-bullseye-lite-bpi-r3-5.15-sd-emmc.img, Kernel 5.15.77
:: Baidu Cloud: https://pan.baidu.com/s/195HeMXjK-rmCEZTnYBCndA?pwd=8888 (pincode: 8888)
:: Google Drive:https://drive.google.com/file/d/1NRR1hKsv6vE1bHOyRjcCGiHgmgaRxt72/view?usp=share_link

* 2022-12-18-debian-10-buster-lite-bpi-r3-5.15-sd-emmc.img, Kernel 5.15.77
:: Baidu Cloud: https://pan.baidu.com/s/1_OGb8ZMF4pWIbaKJ0z2JsA?pwd=8888 (pincode: 8888)
:: Google Drive: https://drive.google.com/file/d/1Q9ZSCZ8_ZI6o5SG4_iOn-mQUaci6Qfrt/view?usp=share_link

==Ubuntu==
* 2022-12-18-ubuntu-22.04-server-bpi-r3-aarch64-sd-emmc.img
:: Baidu Cloud: https://pan.baidu.com/s/1PajBEeFkgzgBdmJa5KpHpA?pwd=8888 (pincode: 8888)
:: Google Drive:https://drive.google.com/file/d/1m9TFmnICj45b61evvmz9ja0g7kH641SG/view?usp=share_link

=FAQ=
===Failed to save the configuration===
:: Enter "mtd erase /dev/mtd10"

Banana Pi BPI-R64

2023-02-27T01:51:47Z

Czj: /* FAQ */

[[zh:香蕉派_BPI-R64]]

=Summary=
[[File:BPI-R64_3.JPG|thumb|[[Banana Pi BPI-R64]] with MT7622]]
[[File:BPI-R64_case_1.jpg|thumb|[[Banana Pi BPI-R64]] Metal [[Case]]]]

[[File:BPI-R2_3.JPG|thumb|[[Banana Pi BPI-R2]] with MTK MT7623N chip design]]
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]

[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTK1296 chip design]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] with allwinner A20 chip design]]
[[File:BPI-R64_4.JPG|thumb|BPI-R64 with BPI-7402 POE function support]]
[[File:Banana_Pi_BPI-R64_1.jpg|thumb|Overview：banana Pi BPI-R64]]

[[File:BPI-7402_IEEE_802.3at_PoE_module_2.jpg|thumb|[[BPI-7402 IEEE 802.3at PoE module]]]]
[[File:MTK_MT7615_1.JPG|thumb|[[BPI-MT7615 802.11 ac wifi 4x4 dual-band module]]]]
[[File:5G_gateway_2.jpg|thumb|BPI:4.0 [[Successful case]] 5G Converged communication gateway]]
[[File:BPI-4G 5.JPG|thumb|4G with USB [[4G module via USB]]]]
[[File:BPI-R64_4g_1.JPG|thumb|[[5G + 4G LTE+Wifi AC+Gigabit Multiplex aggregate route]]]]
[[File:BPI-R64_case.JPG|thumb|BPI-R64 case]]

==Introduction==
The Banana Pi R64 is a router based development board, which can run on a variety of open source operating systems including OpenWrt,Linux. It has 4 Gigabit LAN ports, 1 Gigabit WAN, and AC wifi AP function.
use 64 bit chip design

[[File:Banana_Pi_BPI-R64.png]]

'''Note: this board doesn't have HDMI interface'''

==MTK MT7622==

Highly integrated 4x4 802.11n and Bluetooth 5.0 platform with dedicated Network Accelerator
[https://www.mediatek.com/products/homeNetworking/mt7622 MediaTek MT7622] is the world’s first with 4x4n 802.11n/Bluetooth 5.0 system-on-chip designed and built for premium networking devices across several applications including routers/repeaters, home automation gateways, wireless audio, and wireless storage. The highly versatile chipset provides a single platform for popular 4X4 dual-band and tri-band routers/repeaters, providing maximum flexibility for manufacturers looking to build top-tier networking devices. The platform pairs high performance and extensively integrated functionality with a cost-effective approach.

The MT7622 contains MediaTek’s Adaptive Network technology that allows for easy setup, network self-healing, roaming, band steering, Smart quality of service, advanced security and more. For audio and voice control applications, essential audio interfaces such as I2S, TDM and S/PDIF are included. And for Home Automation Gateways there is a rich array of slow I/O in addition to the integrated Wi-Fi, Bluetooth and Zigbee co-existence.

Powered by a 64-bit dual-core ARM Cortex-A53 processor clocked at 1.35GHz, the MT7622 provides a host of advanced connectivity options like SGMII/RGMII, PCIe, and USB, and 4X4 802.11n FEM integration. Extending the platform with 802.11ac to meet additional markets is simply done via MT7615 SoC.

The MT7622 introduces several best-in-class features such as Bluetooth 5.0 and a dedicated Network Accelerator engine with the MediaTek Wi-Fi Warp Accelerator, storage accelerator (SATA 3.0/eSATA Gen2) and HNAT HQoS calculations are offloaded from the CPU, lowering overall power-use and freeing up resources to avoid any potential slow-downs.

The advantage of the MediaTek Wi-Fi Warp Accelerator is two-fold. Firstly it connects the Gigabit+ class 802.11ac networking through to the Gigabit switch/WAN connection via multi-Gigabit internal pathways, ensuring no bottleneck. Secondly, its specialized design not only offloads the CPU from many-user throughput and QoS calculations, it does so at lower power. The result is the MediaTek Wi-Fi Warp Accelerator maintains a sustained high-performance when even supporting multiple, simultaneous heavy users.

Integrated Bluetooth allows for a direct, local wireless connection via App for easy configuration of the router/Wi-Fi settings. The latest Bluetooth 5.0 quadruples range and doubles speed versus previous 4.x technologies, allowing new and innovative possibilities.

==Key Features==

* MediaTek MT7622,1.35GHZ 64 bit dual-core ARM Cortex-A53
* 1G DDR3 SDRAM
* Mini PCIE interface support 4G module
* built-in 4x4n 802.11n/Bluetooth 5.0 system-on-chip
* MTK7615 4x4ac wifi (option)
* support 1 SATA interface
* MicroSD slot supports up to 256GB expansion
* 8G eMMC flash (option 16/32/64G)
* 5 port 10/100/1000 Mb Ethernet port
* (1) USB 3.0
* Slow I/O:ADC, Audio Amplifier, GPIO, I2C, I2S, IR, PMIC I/F, PWM, RTC, SPI, UART
* POE function support

==Getting Start==

Read more for development :[[Getting Started with R64]]

Frank wiki : http://fw-web.de/dokuwiki/doku.php?id=en:bpi-r64:start

=Hardware Revision=
==Hardware interface==

[[File:BPI-R64_interface.JPG]]

the inner and outer diameter of the power plug adapter datasheet:https://drive.google.com/file/d/1k3AWmYOs2XE7lnRxCyytZu0Vpq_Bzcu_/view?usp=sharing

[[File:Dc090_size.png]]

==Hardware spec==
{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''HardWare Specification of Banana pi BPI-R64'''
|-
| CPU ||MediaTek MT7622,1.35GHZ 64 bit dual-core ARM Cortex-A53
|-
| SDRAM || 1 GB DDR3
|-
| SATA || support 1 SATA interface
|-
| GPIO || 40 Pins Header, 28×GPIO, some of which can be used for specific functions including UART, I2C, SPI, PWM, I2S.
|-
| On board Network || 5 10/100/1000Mbps Ethernet
|-
| Wifi || built-in 4x4n 802.11n (800Mbps) sysem-on-chip and MTK7615 4x4ac wifi Module (1733Mbps) (option)
|-
| Bluetooth || Bluetooth 5.0 system-on-chip
|-
| On board Storage || MicroSD $TF$ card,8GB eMMC onboard
|-
| mini PCIE||1 mini pcie interface for 4G
|-
| USB || 1 USB 3.0 host
|-
| Buttons || Reset button
|-
| Leds || Power status Led and RJ45 Led
|-
| IR || PIN define with GPIO
|-
| DC Power || 12V/2A with DC in
|-
| POE || support POE module interface,can add POE module
|-
| Sizes || 148 mm × 100.5mm same as [[Banana Pi BPI-R3]] and [[Banana Pi BPI-R2]]
|-
| Weight || 100g
|-
|}

==PoE support ==

we design PoE function for BPI-R64 ,so easy to add PoE module to support PoE function,PoE modue can support IEEE 802.3bt PoE standard ,Max support 12V/3A to power BPI-R64

[[File:BPI-R64_POE.jpg]]

more PoE module spec

[[BPI-7402 IEEE 802.3at PoE module]]

==4G support==

1, use pcie interface standard module ,and use SIM card slot onboard

::[[File:4g_onboard.jpg]]

2,use 4G extend module via USB port

*USB 4G module : http://wiki.banana-pi.org/4G_module_via_USB

==BPI-MT7615 802.11 ac wifi 4x4 dual-band==

we have design a MT7615 802.11 ac wifi module ,can use on BPI-R64

MT7615 is a highly integrated Wi-Fi single chip which support 1733 Mbps PHY rate,It fully compies with IEEE 802.11ac and IEEE802.11 a/b/n standards,offering feature-rich wireless connecivity at high standards,and delivering reliable,cost-effective throughput from and extended distance.

[[BPI-MT7615 802.11 ac wifi 4x4 dual-band module]]

[[BPI-R64 + MT7615 function test]]

==BPI-R64 GPIO Pin define==

[[Image:R64_gpio_40.jpg]]

=Resources=
==Source code==
*Banana Pi BPI-R64 (MT7622) openwrt (Kernel 4.19) : https://github.com/BPI-SINOVOIP/BPI-R64-openwrt
*BPI-R64 Linux BSP(kernel 5.4):https://github.com/BPI-SINOVOIP/BPI-R64-bsp-5.4
*BPI-R64 Linux BSP(kernel 4.19):https://github.com/BPI-SINOVOIP/BPI-R64-bsp-4.19
*BPI-R64 Linux BSP(kernel 4.4) : https://github.com/BPI-SINOVOIP/BPI-R64-bsp
*frank github(kernel 5.4): https://github.com/frank-w/BPI-R2-4.14/tree/5.4-r64-dsa
* OpenWRT: https://github.com/openwrt/openwrt/tree/master/target/linux/mediatek/mt7622

==Documents==
*Because of the Google security update some of the old links will not work if the images you want to use cannot be downloaded from the [https://drive.google.com/drive/folders/0B_YnvHgh2rwjVjNyS2pheEtWQlk?resourcekey=0-U4TI84zIBdId7bHHjf2qKA new link bpi-image Files]
*All banana pi [https://drive.google.com/drive/folders/0B4PAo2nW2Kfndjh6SW9MS2xKSWs?resourcekey=0-qXGFXKmd7AVy0S81OXM1RA&usp=sharing docement(SCH file,DXF file,and doc)]
*BPI-R64 schematic diagram
::google https://drive.google.com/file/d/1QzKmIwgSNbCIXQbqLsTUELJCEPik3VGr/view?usp=sharing
::baidu cloud link: https://pan.baidu.com/s/18MEJpr5OTYmySZoyk3bO5Q pincode: amqt
* BPI-R64 DXF file for case deign : https://drive.google.com/file/d/1_YNsdQ9Cv7FVOGrqd6GP0Tu5u2cjLwTA/view?usp=sharing
* BPI-R64 DXF file and the parts used for the assembly datasheet: https://drive.google.com/file/d/1LK5HkP4AfE8xNLJMRHvc7JgexfkDBUAF/view?usp=sharing
* 3D printed case for Banana PI R-64. Link https://www.thingiverse.com/thing:4261948
* BPI-R64 3D design file update with SolidWorks :http://forum.banana-pi.org/t/bpi-r64-3d-design-file-with-solidworks/10910
* MTK 7622 chip : https://www.mediatek.com/products/homeNetworking/mt7622
* MTK MT7622A_Datasheet_for_BananaPi_Only : https://drive.google.com/file/d/1DVEv3bovA8cPti3Ln7d9lDBjMCGFSE5m/view?usp=sharing
* MT7622 Reference Manual for Develope Board(BPi) : https://drive.google.com/file/d/1cW8KQmmVpwDGmBd48KNQes9CRn7FEgBb/view?usp=sharing
*MT7531 switch chip datasheet: https://drive.google.com/file/d/1aVdQz3rbKWjkvdga8-LQ-VFXjmHR8yf9/view?usp=sharing
*Banana Pi BPI-R64 debian Linux boot demo and bootlog:http://forum.banana-pi.org/t/banana-pi-bpi-r64-debian-linux-boot-demo-and-bootlog/8155
*Banana Pi BPI-R64 passed AWS Greengrass : https://devices.amazonaws.com/detail/a3G0h000000OvObEAK/Banana-Pi-R64
*Bpi-r64 quick start (boot from eMMC):http://forum.banana-pi.org/t/bpi-r64-quick-start-boot-from-emmc/9809
*Banana Pi BPI-R64 CE,FCC,RoHS Certification : http://forum.banana-pi.org/t/banana-pi-bpi-r64-open-source-router-board-ce-fcc-rohs-certification/10094
*Patchwork/Mailinglist there was a DSA-driver for mt7531 released : https://patchwork.kernel.org/project/linux-mediatek/list/?submitter=189635
*MTK chip mailline Linux effort :https://mtk.bcnfs.org/doku.php?id=linux_mainline_effort
*BPI-R64 current u-boot support：http://forum.banana-pi.org/t/bpi-r64-current-u-boot-support/10077
*New netfilter flow table based HNAT:http://forum.banana-pi.org/t/new-netfilter-flow-table-based-hnat/12049
*[Tutorial] Build, customize and use MediaTek open-source U-Boot and ATF : https://forum.banana-pi.org/t/tutorial-build-customize-and-use-mediatek-open-source-u-boot-and-atf/13785

== Amazon AWS Greengrass==

Banana Pi BPI-R64 passed Amazon AWS Greengrass:https://devices.amazonaws.com/detail/a3G0h000000OvObEAK/Banana-Pi-BPI-R64

=Release=

*Download and setup separate ATF image for booting directly into kernel or u-boot
::https://forum.banana-pi.org/t/bpi-r64-download-and-setup-separate-atf-image-for-booting-directly-into-kernel-or-u-boot/12806

==OpenWRT & LEDE==
*Banana Pi BPI-R64 19.07.7 OpenWRT Router image 2021-05-01
::google driver:https://drive.google.com/file/d/1YHSU8BHG-k0EcHNp0-F73Xlpiqq1ho4v/view?usp=sharing
::baidu link : https://pan.baidu.com/s/1RxtvekBOxP0UtNSzx5mpEg Pincode: fthx
::source code on github:https://github.com/BPI-SINOVOIP/BPI-R64-openwrt.git
::discuss on forum :http://forum.banana-pi.org/t/banana-pi-bpi-r64-19-07-7-openwrt-router-image-2021-05-01/12209

* Custom OpenWrt build for Banana Pi R64:
::http://forum.banana-pi.org/t/bpi-r64-custom-openwrt-build-for-banana-pi-r64/10973

*BPI-R64 new image : LEDE17 (OpenWRT) image Kernel:4.4.177 2020-04-09
::google driver ： https://drive.google.com/drive/folders/1EK6fkGivZB3OmY38W8gN4rFAsnInMlNl
::baidu cloud : https://pan.baidu.com/s/1UR-Uli2chQ5tO9VCl5Yz6A Pincode：j00s
::Boot media: SD Card & eMMC ,two image
::MD5: 21a6d89979d473cde59f7d61f3
::discuss on forum: http://forum.banana-pi.org/t/bpi-r64-new-image-lede17-openwrt-image-kernel-4-4-177-2020-04-09/10924

*Mainline OpenWRT image
::https://drive.google.com/drive/folders/1LQaxUAWPh6Q3QbLEIxN3JP3soIDEPzGD
::discuss on forum : http://forum.banana-pi.org/t/r64-mainline-openwrt-image/11415

==Ubuntu ==
*2021-6-16 update BPI-R64 Ubuntu Server 21.04 image
::Baidu link: https://pan.baidu.com/s/1nEfneNrFND1dfDLBAekdsg Pincode: dfvv
::Google link : https://drive.google.com/file/d/1ieF-qTyt8LDJiaGqr0uCL4QmAxJZpjhH/view?usp=drivesdk

*2020-05-08 updae ,Ubuntu 18.04 with kernel 5.4.0
::donload link : https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-R64%2FUbuntu18.04&mode=list
::discuss on forum : http://forum.banana-pi.org/t/bpi-r64-new-image-debian10-and-ubuntu18-04-linux-kernel-5-4-0-2020-05-08/11106

*2019-08-23 update,Ubuntu Server 16.04,This release is for banana pi R64 board, and it is based on kernel 4.19.
::Fetures Map:
::Google Drive : https://drive.google.com/open?id=1zrOSS2QJPirSwoK5yJFx10SiOtxRjXPt
::Baidu Drive : https://pan.baidu.com/s/1iOtk-OnC9yNTMzdhSeOCJA（PinCode：ew9c）
::MD5 : 79fc190def54140dd9bf12b73e263bd0
::username : root/pi ; password : bananapi
::Forum Pthread:http://forum.banana-pi.org/t/bpi-r64-ubuntu-16-04-aarch64-linux-lite-debian-10-buster-lite-demo-images-release-2019-08-23/9759
*2020-12-22 Ubuntu 18.04 with kernel 5.4.0
::download link : https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FImages%2FBPI-R64%2FUbuntu18.04%2F2020-12-20-ubuntu-18.04.3-bpi-r64-5.4-sd-emmc.img.zip
::supports 4G Module(EC20)
::username : root/pi ; password : bananapi

==Debian==
*[BPI-R64] debian buster with new bootchain and linux 5.10,frank share this image
::http://forum.banana-pi.org/t/bpi-r64-debian-buster-with-new-bootchain-and-linux-5-10/11850

*2020-05-08 updae ,Debian10 with kernel 5.4.0
::download link :　https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/?p=%2FImages%2FBPI-R64%2FDebian10&mode=list
::discuss on forum : http://forum.banana-pi.org/t/bpi-r64-new-image-debian10-and-ubuntu18-04-linux-kernel-5-4-0-2020-05-08/11106

*2019-08-23 update,Debian 10 buster lite,This release is for banana pi R64 board, and it is based on Debian 10 Buster Lite Operation system with kernel 4.19.
::Fetures Map:
::Google Drive : https://drive.google.com/open?id=1p4WImHkItdSYGRV5jtMdfYHm5PD4dl-q
::Baidu Drive : https://pan.baidu.com/s/1hVQj-1_rYc74QQ1Z4WoaiQ （PinCode：g1j5）
::MD5 : fa3f6a7f7a4bcf2c5a8072301cf8c268
::username : root/pi ; password : bananapi
::Forum Pthread:http://forum.banana-pi.org/t/bpi-r64-ubuntu-16-04-aarch64-linux-lite-debian-10-buster-lite-demo-images-release-2019-08-23/9759

*2018-12-11 update This release is for banana pi R64 board which is based on Mtk 7622, Debian 8 AARCH64 is based on kernel 4.4.92
::Features Map: http://wiki.banana-pi.org/Getting_Started_with_R64
::Google Drive : https://drive.google.com/open?id=1Xnz327Mm24WoVwAsj4yPPek09bP3yv7P
::Baidu Drive : https://pan.baidu.com/s/1AdCM9lTuWP9oXiOE2qGsDw
::md5sum : 4b43980375c3f9692c1f0585ca6b541a
::discuss on forum:http://forum.banana-pi.org/t/banana-pi-bpi-r64-new-image-debian-8-11-aarch64-release-2018-12-11/7447

==AArch64 Linux==

*2019-08-23 update,AArch64 Linux lite,This release is for banana pi R64 board, and it is based on kernel 4.19.
::Fetures Map:
::Google Drive : https://drive.google.com/open?id=1x7_Iu1D9jJGvAExdNZGDVGuv7CbDp4ep
::Baidu Drive : https://pan.baidu.com/s/15X6XtRuab08_N2T0vgoVOQ （PinCode：j4f7）
::MD5 :ed579320359fdc471eeaf37f98d5874d
::username : root/pi ; password : bananapi
::Forum Pthread:http://forum.banana-pi.org/t/bpi-r64-ubuntu-16-04-aarch64-linux-lite-debian-10-buster-lite-demo-images-release-2019-08-23/9759

=FAQ=
*easy to buy sample: [https://pt.aliexpress.com/store/group/R64-Board/302756_516275551.html?spm=2114.12010608.0.0.408a18d6rdUraV BPI official Aliexpress shop]
===TTL Voltage===
:: The debug-uart TTL is tolerant to 3.3V.

Getting Started with R2

2023-02-27T01:51:24Z

Czj: /* FAQ */

[[zh:快速上手香蕉派 BPI-R2]]

='''Introduction'''=
[[File:BPI-R2_3.JPG|thumb|Overview [[Banana Pi BPI-R2]]]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] Allwinner A20]]

[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]
[[File:BPI-R64_3.JPG|thumb|[[Banana Pi BPI-R64]] MTK MT7622]]
[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTD1296 chip design]]
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]

The Banana Pi R2 is a router based development board, which can run on a variety of open source operating systems including OpenWrt, Android, and Bananian. It has 4 Gigabit LAN ports, 1 Gigabit WAN, and 300Mbs wireless N capabilities.

Read more: [[Banana Pi BPI-R2]]

==Key Features==

* MediaTek MT7623N, Quad-core ARM Cortex-A7
* Mali 450 MP4 GPU
* 2G DDR3 SDRAM
* 1x Mini PCIE interface
* 2x SATA interface
* 4x Gigabit LAN 1x Gigabit WAN

==Hardware==
==BPI-R2 SATA interface==
BPI-R2 support 2 sata interface and onboard power port.

[[File:BPI-R2_SATA.jpg]]

you can use sata line connect your hardisk on BPI-R2.

*Test a SAMSUNG SSD DISK, the Read/Write performance are below:

::Read from disk: 230MB/s $command: dd if=/dev/sda of=/dev/zero bs=1M count=10240$

:: Write to disk: 192MB/s $command: dd if=/dev/zero of=/dev/sda bs=1M count=1024 oflag=direct$

*Note:

::if you use 3.5 big hardisk ,you may need power with outside power. on board power maybe can not support enough current

='''Development'''=
Let's get start to develop on BPI-R2, see amazing things happen.
==Basic Development==
===Prepare to develop===
* Prepare 16G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on R2

[[Image:R2_debug_console.png|240px]]

* BananaPi R2 - Debug-UART ：http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:debug-uart

===Load your first image on R2===
1.You could download latest image from our forum
* Here is the example image link: http://forum.banana-pi.org/t/bpi-r2-new-image-release-ubuntu-16-04-v1-3-2018-3-30/5293

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R2, and press power button for around 10s to setup R2

====Update Your Ubuntu On SD Card====
1. Clone Bsp project from Github
* Execute "git clone git@github.com:BPI-SINOVOIP/BPI-R2-bsp.git"

2. Execute "./build.sh", to build your own uboot and kernel.
[[Image:R2_build_sh.png]]

3. After finish built, Execute "cd SD", plug your Ubuntu TFcard in PC.

4. Execute "bpi-update -c bpi-r2.conf -d /dev/sdX", to update the compiled kernel to your TFcard.

====Ubuntu On Emmc====
1. If you want to install Ubuntu on EMMC, follow these steps：
* Burn an image to sd card, and set up R64 with sd card.
* Copy the image which name contains "xxx-emmc-xxx" to U disk.
* mount U disk to R64, then use bpi-copy to burn image to Emmc.

bpi-copy <XXX.img.zip>

* XXX.img.zip is ubuntu image we can get it from http://www.banana-pi.org/r2-download.html
* power off
* remove SD & power on

====OpenWrt On SD & Emmc Steps====
1. Clone OpenWrt project from Github.
* Execute "git clone https://github.com/garywangcn/bpi-r2_lede.git"

2. You need to have installed gcc, binutils, bzip2, flex, python, perl, make, find, grep, diff, unzip, gawk, getopt, subversion, libz-dev and libc headers.

3. Run "./scripts/feeds update -a" to get all the latest package definitions defined in feeds.conf / feeds.conf.default respectively and "./scripts/feeds install -a" to install symlinks of all of them into package/feeds/.

4. Use "make menuconfig" to configure your image.
* Choose "Target System" to config as "MediaTek Ralink ARM"
* Choose "Boot Loaders" to config as "u-boot-bpi_r2"

5. Execute "make -j1 V=s" to build your own OpenWrt image.

6. After built, we have two ways to install image.
(1) Plug your TFcard in Ubuntu PC, and enter to "build_dir/target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-mediatek_32/",
you will find two images:
* mtk-bpi-r2-EMMC.img
* mtk-bpi-r2-SD.img
(2) Write image to TF card, execute "dd if=mtk-bpi-r2-SD.img of=/dev/sdX"

(3) If you want to install image to EMMC, We need another system which is running on SD card to program EMMC image to EMMC, please follow below steps to do:
* Copy EMMC image to a running system which is from SD card
* Program EMMC image to User Data Area of EMMC: dd if=mtk-bpi-r2-EMMC.img of=/dev/mmcblk0 (assume /dev/mmcblk0 is for EMMC)
* Unlock EMMC boot0 block: echo 0 > /sys/block/mmcblk0boot0/force_ro
* Program preloader to EMMC boot0 block: dd if=mtk-bpi-r2-EMMC.img of=/dev/mmcblk0boot0 bs=1M count=1
* Change the Partition configurion of EMMC is 48h: reboot the system which is running SD, and enter the U-boot command line, run command emmc pconf 48 (for this steps, we can change partition configuration in userspace by using mmc-utils,see more information in BPI-R2 OpenWrt(LEDE) Souce code : 2018-04-11)
* Power off, remove SD card, and then power on R2 board

7. This step is for upgrade, if you don't want to install image after you built, you could use runtime upgrade.
* Copy "bin/targets/mediatek/32/lede-mediatek-32-bananapi,bpi-r2-sysupgrade.tar" to R2 board which is running OpenWrt system(no matter where(SD or EMMC) it boots from), and then run command "sysupgrade lede-mediatek-32-bananapi,bpi-r2-sysupgrade.tar" to update both kernel and rootfs.

* 1,Banana Pi R2 install openWRT: https://www.cnblogs.com/topbin/p/8794152.html
* 2,Banana Pi R2 Openwrt Network port configuration analysis : https://www.cnblogs.com/topbin/p/9518279.html
* 3,Banana Pi R2 developing a simple router based on Openwrt : https://www.cnblogs.com/topbin/p/9519881.html
* 4,Banana Pi R2 Openwrt Luci : https://www.cnblogs.com/topbin/p/9519875.html

=== Network-Configuration===
*Network-Configuration : http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start

==Advanced Development==
===GPIO===
====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 233

[[Image:R2_gpio_base.png]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 255（22+233） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio255/direction
* echo 1 > /sys/class/gpio/gpio255/value

====PWM Control====
* echo x >/sys/class/pwm/pwmchip0/export
* echo 200000 >/sys/class/pwm/pwmchip0/pwmx/period
* echo 100000 >/sys/class/pwm/pwmchip0/pwmx/duty_cycle
* echo 1 >/sys/class/pwm/pwmchip0/pwmx/enable

More about GPIO : http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:gpio

====Install RPi.GPIO====
* Execute "git clone https://github.com/BPI-SINOVOIP/RPi.GPIO"
* after clone the repo, cd RPi.GPIO
* Execute "sudo apt-get update"
* Execute "sudo apt-get install python-dev python3-dev"
* Execute "sudo python setup.py install" or "sudo python3 setup.py install" to install the module

====Using RPi.GPIO====
* cd /usr/local/bin
* Execute "./g40.py" to test RPi.GPIO

===Develop 4G module with R2===
Gets more info from here:

[[Using 4G module with BananaPi]]

===WiFi and Ap mode on R2 Ubuntu===
====STA====
* wmt_loader (ignore errors)
* stp_uart_launcher -p /etc/firmware &
* ip link set wlan0 up
* iw dev wlan0 scan | grep SSID
* vim /etc/wpasupplicant/wpa_supplicant.conf
network={
ssid="ssid"
psk="password"
priority=1
}
* wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
* dhclient wlan0

====AP mode====
* wmt_loader (ignore errors)
* stp_uart_launcher -p /etc/firmware &
* echo A >/dev/wmtWifi
* create your hostapd.conf: "vim /etc/hostapd/hostapd.conf "

interface=ap0
bridge=br0
ssid=test_r2
driver=nl80211
country_code=US
hw_mode=b
channel=1
max_num_sta=5
wpa=2
auth_algs=1
rsn_pairwise=CCMP
wpa_key_mgmt=WPA-PSK
wpa_passphrase=ledetest
logger_stdout=-1
logger_stdout_level=2

* According to your network interface(can search internet) to config ap0:
my network interface which can search internet is wan, and ip is 192.168.30.102, so I config ap0 as follows:

“ifconfig ap0 192.168.30.188 netmask 255.255.255.0”

* Run hostapd : “hostapd -d /etc/hostapd/hostapd.conf”
* Config dhcp file : “vim /etc/dhcp/dhcpd.conf”

subnet 192.168.30.0 netmask 255.255.255.0 {
range 192.168.30.2 192.168.30.250;
option domain-name-servers 8.8.8.8;
option routers 192.168.30.1; }

* Config dhcp of ap0, then the devices which connect ap0 could get IP: "dhcpd ap0 -pf /var/run/dhcpd.pid "
* And a bridge
* brctl addbr br0
* brctl addif br0 ap0
* brctl addif br wan
* Config br0 : “ifconfig br0 192.168.30.180 netmask 255.255.255.0”
* Add br0 gw as : “route add -net default netmask 255.255.255.0 gw 192.168.30.1 dev br0”

====Ap Mode FAQ====
If you meet problem like this：

[[Image:A64_ap_1.png]]

Then, you could solve by following command：
* nmcli radio wifi off
[[Image:A64_ap_2.png]]
* rfkill unblock 1
* rfkill unblock 2
* ifconfig ap0 up
* hostapd -d hostapd.conf
[[Image:A64_ap_3.png]]

===WiFi and Ap mode on R2 Openwrt===
====AP mode====
1. Make a bash script
* vim setup.sh
#!/bin/ash
wmt_loader &
sheep 3
stp_uart_launcher -p /etc/firmware &
sleep 5
echo A > /dev/wmtWifi &
sleep 5
hostapd -d hostapd.conf
2. Create your hostapd.conf
* vim hostapd.conf
interface=ap0
bridge=br-lan
ssid=BPI_R2
driver=nl80211
country_code=CN
hw_mode=g
channel=1
max_num_sta=5
wpa=2
auth_algs=1
rsn_pairwise=CCMP
wpa_key_mgmt=WPA-PSK
wpa_passphrase=ledetest
logger_stdout=-1
logger_stdout_level=2

3. Make it run
* ./setup.sh

4. Add it to starting progress
* vim /etc/rc.local
cd /root/
sleep 6
./setup.sh &

5. If your Ap is not stable, please limit the speed, here I limit download speed as 8Mbit/s, upload as 4Mbit/s
* tc qdisc add dev ap0 root handle 1: htb default 11
* tc class add dev ap0 parent 1:1 classid 1:2 htb rate 8Mbit ceil 4Mbit prio 2

===Make your own image===
* Prepare a SD card which have installed Ubuntu system
* Boot your SD card with R2, after R2 finish starting, copy your files and config your Ubuntu, then poweroff R2
* Plug your SD card in Linux PC, "cd /media", then "ln -s <your account> pi"
* Execute "bpi-migrate -c bpi-r2.conf -c ubuntu-mate-from-sd.conf -d /dev/sdx"
* Then you could get your own image now

==FAQ==
*1.Banana Pi BPI-R2 Razberry board OpenHab2
::https://community.openhab.org/t/banana-pi-bpi-r2-razberry-board-openhab2-help/37222/8

===TTL Voltage===
:: The debug-uart TTL is tolerant to 3.3V.

='''Reference Link'''=

http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:start

http://www.banana-pi.org/r2.html

http://forum.banana-pi.org/

Getting Started with BPI-R3

2023-02-27T01:50:12Z

Czj: /* TTL */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.
'''
'''UART_TX0 is the Boot Strapping PIN and must be kept low during power-on.'''

[[File:Strapping.png|720px]]

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing
===TTL Voltage===
:: The debug-uart TTL is tolerant to 3.3V.

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with BPI-R3

2023-02-27T01:49:29Z

Czj: /* FAQ */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.
'''
'''UART_TX0 is the Boot Strapping PIN and must be kept low during power-on.'''

[[File:Strapping.png|720px]]

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing
===TTL===
:: The debug-uart TTL is tolerant to 3.3V.

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with R64

2023-02-20T09:48:36Z

Czj: /* How to burn image to onboard eMMC */

[[zh:快速上手香蕉派 BPI-R64]]
=Introduction=
[[File:Banana_Pi_BPI-R64_1.jpg|thumb|Overview：[[Banana Pi BPI-R64]]]]
[[File:BPI-R64_case_1.jpg|thumb|[[Banana Pi BPI-R64]] Metal Jacket]]
[[File:BPI-R64_PoE.JPG|thumb|BPI-R64 with BPI-7402 POE function support]]
[[File:BPI-7402_IEEE_802.3at_PoE_module_1.jpg|thumb|[[BPI-7402 IEEE 802.3at PoE module]]]]
[[File:5G_gateway_2.jpg|thumb|BPI:4.0 [[Successful case]] 5G Converged communication gateway]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] Allwinner A20]]
[[File:BPI-R2_3.JPG|thumb|[[Banana Pi BPI-R2]] with MTK MT7623N chip design]]
[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]
[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTD1296 chip design]]
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]
The Banana Pi R64 is a router based development board, which can run on a variety of open source operating systems including OpenWrt,Linux. It has 4 Gigabit LAN ports, 1 Gigabit WAN, and AC wifi AP function. use 64 bit chip design.
Read more: [[Banana Pi BPI-R64]]

==Key Features==

* MediaTek MT7622,1.35GHZ 64 bit dual-core ARM Cortex-A53
* 1G DDR3 SDRAM
* Mini PCIE interface support 4G module
* Built-in 4x4n 802.11n/Bluetooth 5.0 system-on-chip
* MTK7615 4x4ac wifi on board
* Support 1 SATA interface
* MicroSD slot supports up to 256GB expansion
* 8G eMMC flash (option 16/32/64G)
* 5 port 10/100/1000 Mb Ethernet port
* 1 Port USB 3.0
* Slow I/O:ADC, Audio Amplifier, GPIO, I2C, I2S, IR, PMIC I/F, PWM, RTC, SPI, UART
* POE function support

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on R64

[[Image:R64_debug_console.jpg|320px]]

===How to burn image to SD card===
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R64, and press power button to setup R64

====How to burn image to onboard eMMC====
Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) for example, the steps are below:
Note: You can download the .bin file from github: https://github.com/BPI-SINOVOIP/BPI-R64-openwrt/tree/master/staging_dir/target-aarch64_cortex-a53_musl/image

1. Insert the flashed SD card and power on to start the board.(the image on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy eMMC bootable OpenWrt image(mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to eMMC:
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img of=/dev/mmcblk0
* dd if=mtk-bpi-r64-preloader-emmc.bin of=/dev/mmcblk0boot0
* mmc bootpart enable 1 1 /dev/mmcblk0

5. Shutdown, remove SD card and USB disk, and restart the board from eMMC.

=== Network-Configuration===
*Network-Configuration : http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start

==Advanced Development==
===GPIO===
====40 Pins Definition====

[[Image:R64_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 409

[[Image:R64_gpio_base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 431（22+409） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio431/direction
* echo 1 > /sys/class/gpio/gpio431/value

====PWM Control====
* echo x >/sys/class/pwm/pwmchip0/export
* echo 200000 >/sys/class/pwm/pwmchip0/pwmx/period
* echo 100000 >/sys/class/pwm/pwmchip0/pwmx/duty_cycle
* echo 1 >/sys/class/pwm/pwmchip0/pwmx/enable

====SPI touch panel====
SPI Panel module:

2.4" Touch Screen TFT LCD with SPI Interface, 240x320 (ILI9341 + ADS7843/XPT2046/HR2046)

SPI Panel <–> BPIR64

T_DO, T_DIN, T_CLK <–> SPIC_0: MOSI / MISO / CLK
T_CS <–> SPI-CE0
T_IRQ <–> IO-37
SDO, SCK, SDI <–> SPIC_1: MOSI / MISO / CLK
LED <–> PIN-31
DC <–> PIN-11
RESET <–> PIN-13
CS <–> SPI-CE1
GND <–> GND-9
VCC <–> 3.3V-1

DTS Modification:

/ {
backlight: backlight {
compatible = "gpio-backlight";
gpios = <&pio 82 GPIO_ACTIVE_HIGH>; //PIN31 IO-31 : GPIO82
default-on;
};
};

&pio {
spic0_pins: spic0-pins {
mux {
function = "spi";
groups = "spic0_0";
};
};

spic1_pins: spic1-pins {
mux {
function = "spi";
groups = "spic1_0";
};
};
}

&spi0 {
pinctrl-names = "default";
pinctrl-0 = <&spic0_pins>;
status = "okay";
touch@0 {
reg = <0>; //CE0
compatible = "ti,ads7843";
interrupt-parent = <&pio>;
interrupts = <86 0>; //PIN37: IO-37 == GPIO86
pendown-gpio = <&pio 86 0>;
spi-max-frequency = <1000000>;
vcc-supply = <&reg_3p3v>;
wakeup-source;
};
};

&spi1 {
pinctrl-names = "default";
pinctrl-0 = <&spic1_pins>;
status = "okay";
display@0{
compatible = "ilitek,ili9341";
reg = <0>; //CE0
spi-max-frequency = <32000000>;
dc-gpios = <&pio 51 GPIO_ACTIVE_HIGH>; //PIN11 UART1-TXD : GPIO51
reset-gpios = <&pio 52 GPIO_ACTIVE_HIGH>; //PIN13 UART1-RXD : GPIO52
backlight = <&backlight>;
};
};

Kernel config:

+CONFIG_FB_TFT_ILI9341
+CONFIG_FB_TFT
+CONFIG_FB
+CONFIG_BACKLIGHT_LCD_SUPPORT
+CONFIG_BACKLIGHT_CLASS_DEVICE
+CONFIG_BACKLIGHT_GPIO
+CONFIG_INPUT
+CONFIG_INPUT_TOUCHSCREEN
+CONFIG_TOUCHSCREEN_ADS7846

Application:

{| class="wikitable"
|-
| Package ||+ Description || Source
|-
| fbv || framebuffer image viewer || https://github.com/godspeed1989/fbv
|-
| input-event-daemon || input-event-daemon with touchTEST event || https://github.com/SAM33/input-event-daemon
|-
|}

input-event-daemon config that show image by touch area:
(I don't know why are the coordinates so strange, but the result of my actual touch and
print out that it is like this)

[Global]
listen = /dev/input/event0
listen = /dev/input/event1
[TouchTEST]
340,400,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/bpi_608x429.jpg -s 1
340,2260,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/openwrt_449x449.png -s 1

Banana Pi BPI-R64 SPI touch panel test: https://www.youtube.com/watch?v=ikag-D_TI0g&feature=youtu.be

===Sata===
* '''If you want to use Sata interface on R64, you need to give GPIO90 low level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 0 > /sys/class/gpio/gpio499/value

*Test a TOSHIBA HDD DISK, the Read/Write performance are below:

::Read from disk: 50MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 38MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_hdd_sata_test.jpg]]

*Test a SAMSUNG SSD DISK, the Read/Write performance are below:

::Read from disk: 360MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 200MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_ssd_sata_test.jpg]]

===PCIe===
* '''If you want to use PCIe interface on R64, you need to give GPIO90 high level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 1 > /sys/class/gpio/gpio499/value

* PCIe supports EC-25 4G module.
[[Image:R64_pcie_test_1.jpg]]

[[Image:R64_pcie_test_2.jpg]]

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On R64 console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:R64_Gmac_test.jpg]]

===BT & BLE on R64===
'''R64 BT Architectural'''

[[Image:R64_BT_Arch.jpg]]

* BLE on R64
* Input Command "btmw-test", you will enter to "btmw_test_cli" command line

[[Image:R64_BT_cli.jpg]]

* Here are some example commands：
** MW_GAP name 7622_BT /*rename bt device*/
** MW_GAP info /*check local BT device info*/
** MW_GATTC scan /* start ble scan*/
** MW_GATTC stop_scan /* stop ble scan*/

===R64 LAN Function===
* LAN eth interface is eth2, use "ifconfig eth2 up" to enable it.
* Config the ip, "ifconfig eth2 192.168.1.1".
[[Image:R64_Lan_test_1.jpg]]

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd eth2".
[[Image:R64_Lan_test_3.jpg]]

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

===Ap mode on R64===
* Find "mt_wifi.ko" and insmod it.
** insmod ./lib/modules/4.4.92-BPI-R64-Kernel/extra/mt_wifi.ko

* Then you will see ra0 and rai0.
[[Image:R64_wifi_test_1.jpg]]

* ra0 is MT7622 2.4G wifi
* rai0 is MT7615 5G wifi

====2.4G WiFi====
* Use "ifconfig ra0 up" to enable it.
* Config the ip, "ifconfig ra0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd ra0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

====5G WiFi====
* Use "ifconfig rai0 up" to enable it.
* Config the ip, "ifconfig rai0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd rai0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

==FAQ==
*MT7622 Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/open?id=1UhaIM9ork1O9cNO-t6ENMVVamB75AThV
::BaiDu Drive：https://pan.baidu.com/s/1KduFT2MUvMs2FhOF4A8kQQ

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with R64

2023-02-20T09:45:48Z

Czj: /* How to burn image to onboard eMMC */

[[zh:快速上手香蕉派 BPI-R64]]
=Introduction=
[[File:Banana_Pi_BPI-R64_1.jpg|thumb|Overview：[[Banana Pi BPI-R64]]]]
[[File:BPI-R64_case_1.jpg|thumb|[[Banana Pi BPI-R64]] Metal Jacket]]
[[File:BPI-R64_PoE.JPG|thumb|BPI-R64 with BPI-7402 POE function support]]
[[File:BPI-7402_IEEE_802.3at_PoE_module_1.jpg|thumb|[[BPI-7402 IEEE 802.3at PoE module]]]]
[[File:5G_gateway_2.jpg|thumb|BPI:4.0 [[Successful case]] 5G Converged communication gateway]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] Allwinner A20]]
[[File:BPI-R2_3.JPG|thumb|[[Banana Pi BPI-R2]] with MTK MT7623N chip design]]
[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]
[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTD1296 chip design]]
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]
The Banana Pi R64 is a router based development board, which can run on a variety of open source operating systems including OpenWrt,Linux. It has 4 Gigabit LAN ports, 1 Gigabit WAN, and AC wifi AP function. use 64 bit chip design.
Read more: [[Banana Pi BPI-R64]]

==Key Features==

* MediaTek MT7622,1.35GHZ 64 bit dual-core ARM Cortex-A53
* 1G DDR3 SDRAM
* Mini PCIE interface support 4G module
* Built-in 4x4n 802.11n/Bluetooth 5.0 system-on-chip
* MTK7615 4x4ac wifi on board
* Support 1 SATA interface
* MicroSD slot supports up to 256GB expansion
* 8G eMMC flash (option 16/32/64G)
* 5 port 10/100/1000 Mb Ethernet port
* 1 Port USB 3.0
* Slow I/O:ADC, Audio Amplifier, GPIO, I2C, I2S, IR, PMIC I/F, PWM, RTC, SPI, UART
* POE function support

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on R64

[[Image:R64_debug_console.jpg|320px]]

===How to burn image to SD card===
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R64, and press power button to setup R64

====How to burn image to onboard eMMC====
Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy eMMC bootable OpenWrt image(mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.
You can download the .bin file from github: https://github.com/BPI-SINOVOIP/BPI-R64-openwrt/tree/master/staging_dir/target-aarch64_cortex-a53_musl/image

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to eMMC:
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img of=/dev/mmcblk0
* dd if=mtk-bpi-r64-preloader-emmc.bin of=/dev/mmcblk0boot0
* mmc bootpart enable 1 1 /dev/mmcblk0

5. Shutdown, remove SD card and USB disk, and restart the board from eMMC.

=== Network-Configuration===
*Network-Configuration : http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start

==Advanced Development==
===GPIO===
====40 Pins Definition====

[[Image:R64_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 409

[[Image:R64_gpio_base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 431（22+409） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio431/direction
* echo 1 > /sys/class/gpio/gpio431/value

====PWM Control====
* echo x >/sys/class/pwm/pwmchip0/export
* echo 200000 >/sys/class/pwm/pwmchip0/pwmx/period
* echo 100000 >/sys/class/pwm/pwmchip0/pwmx/duty_cycle
* echo 1 >/sys/class/pwm/pwmchip0/pwmx/enable

====SPI touch panel====
SPI Panel module:

2.4" Touch Screen TFT LCD with SPI Interface, 240x320 (ILI9341 + ADS7843/XPT2046/HR2046)

SPI Panel <–> BPIR64

T_DO, T_DIN, T_CLK <–> SPIC_0: MOSI / MISO / CLK
T_CS <–> SPI-CE0
T_IRQ <–> IO-37
SDO, SCK, SDI <–> SPIC_1: MOSI / MISO / CLK
LED <–> PIN-31
DC <–> PIN-11
RESET <–> PIN-13
CS <–> SPI-CE1
GND <–> GND-9
VCC <–> 3.3V-1

DTS Modification:

/ {
backlight: backlight {
compatible = "gpio-backlight";
gpios = <&pio 82 GPIO_ACTIVE_HIGH>; //PIN31 IO-31 : GPIO82
default-on;
};
};

&pio {
spic0_pins: spic0-pins {
mux {
function = "spi";
groups = "spic0_0";
};
};

spic1_pins: spic1-pins {
mux {
function = "spi";
groups = "spic1_0";
};
};
}

&spi0 {
pinctrl-names = "default";
pinctrl-0 = <&spic0_pins>;
status = "okay";
touch@0 {
reg = <0>; //CE0
compatible = "ti,ads7843";
interrupt-parent = <&pio>;
interrupts = <86 0>; //PIN37: IO-37 == GPIO86
pendown-gpio = <&pio 86 0>;
spi-max-frequency = <1000000>;
vcc-supply = <&reg_3p3v>;
wakeup-source;
};
};

&spi1 {
pinctrl-names = "default";
pinctrl-0 = <&spic1_pins>;
status = "okay";
display@0{
compatible = "ilitek,ili9341";
reg = <0>; //CE0
spi-max-frequency = <32000000>;
dc-gpios = <&pio 51 GPIO_ACTIVE_HIGH>; //PIN11 UART1-TXD : GPIO51
reset-gpios = <&pio 52 GPIO_ACTIVE_HIGH>; //PIN13 UART1-RXD : GPIO52
backlight = <&backlight>;
};
};

Kernel config:

+CONFIG_FB_TFT_ILI9341
+CONFIG_FB_TFT
+CONFIG_FB
+CONFIG_BACKLIGHT_LCD_SUPPORT
+CONFIG_BACKLIGHT_CLASS_DEVICE
+CONFIG_BACKLIGHT_GPIO
+CONFIG_INPUT
+CONFIG_INPUT_TOUCHSCREEN
+CONFIG_TOUCHSCREEN_ADS7846

Application:

{| class="wikitable"
|-
| Package ||+ Description || Source
|-
| fbv || framebuffer image viewer || https://github.com/godspeed1989/fbv
|-
| input-event-daemon || input-event-daemon with touchTEST event || https://github.com/SAM33/input-event-daemon
|-
|}

input-event-daemon config that show image by touch area:
(I don't know why are the coordinates so strange, but the result of my actual touch and
print out that it is like this)

[Global]
listen = /dev/input/event0
listen = /dev/input/event1
[TouchTEST]
340,400,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/bpi_608x429.jpg -s 1
340,2260,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/openwrt_449x449.png -s 1

Banana Pi BPI-R64 SPI touch panel test: https://www.youtube.com/watch?v=ikag-D_TI0g&feature=youtu.be

===Sata===
* '''If you want to use Sata interface on R64, you need to give GPIO90 low level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 0 > /sys/class/gpio/gpio499/value

*Test a TOSHIBA HDD DISK, the Read/Write performance are below:

::Read from disk: 50MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 38MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_hdd_sata_test.jpg]]

*Test a SAMSUNG SSD DISK, the Read/Write performance are below:

::Read from disk: 360MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 200MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_ssd_sata_test.jpg]]

===PCIe===
* '''If you want to use PCIe interface on R64, you need to give GPIO90 high level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 1 > /sys/class/gpio/gpio499/value

* PCIe supports EC-25 4G module.
[[Image:R64_pcie_test_1.jpg]]

[[Image:R64_pcie_test_2.jpg]]

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On R64 console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:R64_Gmac_test.jpg]]

===BT & BLE on R64===
'''R64 BT Architectural'''

[[Image:R64_BT_Arch.jpg]]

* BLE on R64
* Input Command "btmw-test", you will enter to "btmw_test_cli" command line

[[Image:R64_BT_cli.jpg]]

* Here are some example commands：
** MW_GAP name 7622_BT /*rename bt device*/
** MW_GAP info /*check local BT device info*/
** MW_GATTC scan /* start ble scan*/
** MW_GATTC stop_scan /* stop ble scan*/

===R64 LAN Function===
* LAN eth interface is eth2, use "ifconfig eth2 up" to enable it.
* Config the ip, "ifconfig eth2 192.168.1.1".
[[Image:R64_Lan_test_1.jpg]]

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd eth2".
[[Image:R64_Lan_test_3.jpg]]

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

===Ap mode on R64===
* Find "mt_wifi.ko" and insmod it.
** insmod ./lib/modules/4.4.92-BPI-R64-Kernel/extra/mt_wifi.ko

* Then you will see ra0 and rai0.
[[Image:R64_wifi_test_1.jpg]]

* ra0 is MT7622 2.4G wifi
* rai0 is MT7615 5G wifi

====2.4G WiFi====
* Use "ifconfig ra0 up" to enable it.
* Config the ip, "ifconfig ra0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd ra0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

====5G WiFi====
* Use "ifconfig rai0 up" to enable it.
* Config the ip, "ifconfig rai0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd rai0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

==FAQ==
*MT7622 Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/open?id=1UhaIM9ork1O9cNO-t6ENMVVamB75AThV
::BaiDu Drive：https://pan.baidu.com/s/1KduFT2MUvMs2FhOF4A8kQQ

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with R64

2023-02-20T09:45:18Z

Czj: /* How to burn image to onboard eMMC */

[[zh:快速上手香蕉派 BPI-R64]]
=Introduction=
[[File:Banana_Pi_BPI-R64_1.jpg|thumb|Overview：[[Banana Pi BPI-R64]]]]
[[File:BPI-R64_case_1.jpg|thumb|[[Banana Pi BPI-R64]] Metal Jacket]]
[[File:BPI-R64_PoE.JPG|thumb|BPI-R64 with BPI-7402 POE function support]]
[[File:BPI-7402_IEEE_802.3at_PoE_module_1.jpg|thumb|[[BPI-7402 IEEE 802.3at PoE module]]]]
[[File:5G_gateway_2.jpg|thumb|BPI:4.0 [[Successful case]] 5G Converged communication gateway]]
[[File:Banana_pi_BPI-R1_1.JPG|thumb|[[Banana Pi BPI-R1]] Allwinner A20]]
[[File:BPI-R2_3.JPG|thumb|[[Banana Pi BPI-R2]] with MTK MT7623N chip design]]
[[File:Banana_Pi_BPI-R2_Pro_1_750.jpg|thumb|[[Banana Pi BPI-R2 Pro]] Rockchip RK3568 design]]
[[File:O2A0500.jpg|thumb|[[Banana Pi BPI-W2]] with Realtek RTD1296 chip design]]
[[File:Banana_Pi_BPI-R3_Router_2.jpg|thumb|[[Banana Pi BPI-R3]] with MediaTek MT7986(Filogic 830)]]
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]
The Banana Pi R64 is a router based development board, which can run on a variety of open source operating systems including OpenWrt,Linux. It has 4 Gigabit LAN ports, 1 Gigabit WAN, and AC wifi AP function. use 64 bit chip design.
Read more: [[Banana Pi BPI-R64]]

==Key Features==

* MediaTek MT7622,1.35GHZ 64 bit dual-core ARM Cortex-A53
* 1G DDR3 SDRAM
* Mini PCIE interface support 4G module
* Built-in 4x4n 802.11n/Bluetooth 5.0 system-on-chip
* MTK7615 4x4ac wifi on board
* Support 1 SATA interface
* MicroSD slot supports up to 256GB expansion
* 8G eMMC flash (option 16/32/64G)
* 5 port 10/100/1000 Mb Ethernet port
* 1 Port USB 3.0
* Slow I/O:ADC, Audio Amplifier, GPIO, I2C, I2S, IR, PMIC I/F, PWM, RTC, SPI, UART
* POE function support

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on R64

[[Image:R64_debug_console.jpg|320px]]

===How to burn image to SD card===
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R64, and press power button to setup R64

====How to burn image to onboard eMMC====
Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy eMMC bootable OpenWrt image(mtk-bpi-r64-preloader-emmc.bin,2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.
You can download the .bin file from github: https://github.com/BPI-SINOVOIP/BPI-R64-openwrt/tree/master/staging_dir/target-aarch64_cortex-a53_musl/image
3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to eMMC:
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=2020-04-09-OpenWRT-mtk-bpi-r64-EMMC.img of=/dev/mmcblk0
* dd if=mtk-bpi-r64-preloader-emmc.bin of=/dev/mmcblk0boot0
* mmc bootpart enable 1 1 /dev/mmcblk0

5. Shutdown, remove SD card and USB disk, and restart the board from eMMC.

=== Network-Configuration===
*Network-Configuration : http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start

==Advanced Development==
===GPIO===
====40 Pins Definition====

[[Image:R64_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 409

[[Image:R64_gpio_base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 431（22+409） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio431/direction
* echo 1 > /sys/class/gpio/gpio431/value

====PWM Control====
* echo x >/sys/class/pwm/pwmchip0/export
* echo 200000 >/sys/class/pwm/pwmchip0/pwmx/period
* echo 100000 >/sys/class/pwm/pwmchip0/pwmx/duty_cycle
* echo 1 >/sys/class/pwm/pwmchip0/pwmx/enable

====SPI touch panel====
SPI Panel module:

2.4" Touch Screen TFT LCD with SPI Interface, 240x320 (ILI9341 + ADS7843/XPT2046/HR2046)

SPI Panel <–> BPIR64

T_DO, T_DIN, T_CLK <–> SPIC_0: MOSI / MISO / CLK
T_CS <–> SPI-CE0
T_IRQ <–> IO-37
SDO, SCK, SDI <–> SPIC_1: MOSI / MISO / CLK
LED <–> PIN-31
DC <–> PIN-11
RESET <–> PIN-13
CS <–> SPI-CE1
GND <–> GND-9
VCC <–> 3.3V-1

DTS Modification:

/ {
backlight: backlight {
compatible = "gpio-backlight";
gpios = <&pio 82 GPIO_ACTIVE_HIGH>; //PIN31 IO-31 : GPIO82
default-on;
};
};

&pio {
spic0_pins: spic0-pins {
mux {
function = "spi";
groups = "spic0_0";
};
};

spic1_pins: spic1-pins {
mux {
function = "spi";
groups = "spic1_0";
};
};
}

&spi0 {
pinctrl-names = "default";
pinctrl-0 = <&spic0_pins>;
status = "okay";
touch@0 {
reg = <0>; //CE0
compatible = "ti,ads7843";
interrupt-parent = <&pio>;
interrupts = <86 0>; //PIN37: IO-37 == GPIO86
pendown-gpio = <&pio 86 0>;
spi-max-frequency = <1000000>;
vcc-supply = <&reg_3p3v>;
wakeup-source;
};
};

&spi1 {
pinctrl-names = "default";
pinctrl-0 = <&spic1_pins>;
status = "okay";
display@0{
compatible = "ilitek,ili9341";
reg = <0>; //CE0
spi-max-frequency = <32000000>;
dc-gpios = <&pio 51 GPIO_ACTIVE_HIGH>; //PIN11 UART1-TXD : GPIO51
reset-gpios = <&pio 52 GPIO_ACTIVE_HIGH>; //PIN13 UART1-RXD : GPIO52
backlight = <&backlight>;
};
};

Kernel config:

+CONFIG_FB_TFT_ILI9341
+CONFIG_FB_TFT
+CONFIG_FB
+CONFIG_BACKLIGHT_LCD_SUPPORT
+CONFIG_BACKLIGHT_CLASS_DEVICE
+CONFIG_BACKLIGHT_GPIO
+CONFIG_INPUT
+CONFIG_INPUT_TOUCHSCREEN
+CONFIG_TOUCHSCREEN_ADS7846

Application:

{| class="wikitable"
|-
| Package ||+ Description || Source
|-
| fbv || framebuffer image viewer || https://github.com/godspeed1989/fbv
|-
| input-event-daemon || input-event-daemon with touchTEST event || https://github.com/SAM33/input-event-daemon
|-
|}

input-event-daemon config that show image by touch area:
(I don't know why are the coordinates so strange, but the result of my actual touch and
print out that it is like this)

[Global]
listen = /dev/input/event0
listen = /dev/input/event1
[TouchTEST]
340,400,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/bpi_608x429.jpg -s 1
340,2260,3440,1860 = cat /dev/zero > /dev/fb0; fbv -f /root/openwrt_449x449.png -s 1

Banana Pi BPI-R64 SPI touch panel test: https://www.youtube.com/watch?v=ikag-D_TI0g&feature=youtu.be

===Sata===
* '''If you want to use Sata interface on R64, you need to give GPIO90 low level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 0 > /sys/class/gpio/gpio499/value

*Test a TOSHIBA HDD DISK, the Read/Write performance are below:

::Read from disk: 50MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 38MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_hdd_sata_test.jpg]]

*Test a SAMSUNG SSD DISK, the Read/Write performance are below:

::Read from disk: 360MB/s command: dd if=/dev/sda of=/dev/null bs=1M count=1024

::Write to disk: 200MB/s command: dd if=/dev/zero of=/dev/sda bs=1M count=1024
[[Image:R64_ssd_sata_test.jpg]]

===PCIe===
* '''If you want to use PCIe interface on R64, you need to give GPIO90 high level'''
** echo 499 > /sys/class/gpio/export
** echo out > /sys/class/gpio/gpio499/direction
** echo 1 > /sys/class/gpio/gpio499/value

* PCIe supports EC-25 4G module.
[[Image:R64_pcie_test_1.jpg]]

[[Image:R64_pcie_test_2.jpg]]

===GMAC===
Use iperf3 to test gmac

1. On PC Terminal:
* Execute "iperf3 -s"

2. On R64 console:
* TCP test: "iperf3 -c serverIP"
* UDP test: "iperf3 -u -c serverIP"
[[Image:R64_Gmac_test.jpg]]

===BT & BLE on R64===
'''R64 BT Architectural'''

[[Image:R64_BT_Arch.jpg]]

* BLE on R64
* Input Command "btmw-test", you will enter to "btmw_test_cli" command line

[[Image:R64_BT_cli.jpg]]

* Here are some example commands：
** MW_GAP name 7622_BT /*rename bt device*/
** MW_GAP info /*check local BT device info*/
** MW_GATTC scan /* start ble scan*/
** MW_GATTC stop_scan /* stop ble scan*/

===R64 LAN Function===
* LAN eth interface is eth2, use "ifconfig eth2 up" to enable it.
* Config the ip, "ifconfig eth2 192.168.1.1".
[[Image:R64_Lan_test_1.jpg]]

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd eth2".
[[Image:R64_Lan_test_3.jpg]]

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

===Ap mode on R64===
* Find "mt_wifi.ko" and insmod it.
** insmod ./lib/modules/4.4.92-BPI-R64-Kernel/extra/mt_wifi.ko

* Then you will see ra0 and rai0.
[[Image:R64_wifi_test_1.jpg]]

* ra0 is MT7622 2.4G wifi
* rai0 is MT7615 5G wifi

====2.4G WiFi====
* Use "ifconfig ra0 up" to enable it.
* Config the ip, "ifconfig ra0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd ra0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

====5G WiFi====
* Use "ifconfig rai0 up" to enable it.
* Config the ip, "ifconfig rai0 192.168.1.1".

* Config your dhcp server, "vim /etc/dhcp/dhcpd.conf", add these configurations.
[[Image:R64_Lan_test_2.jpg]]

* Start dhcp server, "dhcpd rai0".

* then config iptables and set package forward.
** Add "net.ipv4.ip_forward=1" to "/etc/sysctl.conf"
** "/sbin/sysctl -p" to make forward work
** "iptables -t nat -A POSTROUTING -s 192.168.1.1/24 -o eth3 -j MASQUERADE"

==FAQ==
*MT7622 Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/open?id=1UhaIM9ork1O9cNO-t6ENMVVamB75AThV
::BaiDu Drive：https://pan.baidu.com/s/1KduFT2MUvMs2FhOF4A8kQQ

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with CM4

2023-02-17T09:53:44Z

Czj: /* Wifi client */

=Introduction=
BananaPi BPI-CM4 new design with Amlogic A311D Quad core ARM Cortex-A73 and dual core ARM Cortex-A53 CPU ,ARM G52 MP4(6EE) GPU,NPU for AI at 5.0 TOPS, support Camera and MIPI-CSI interface ,HDMI output,2 Gigabit port . 4G RAM and 16 GB eMMC flash.

[[Banana Pi BPI-CM4]]

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via type-c, only support windows.
:2. Download the latest [https://wiki.banana-pi.org/Banana_Pi_BPI-CM4#Android android image], and confirm that the md5 checksum is correct.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m2s_android_install_1.png]]

:2. Short the usb boot test point on the main board, plugin type-c usb cable to PC or press the RST button if power adapter already connected, about two seconds later, the board will enter usb download mode and be identified correctly by PC. You can also enter usb download mode with adb command "adb reboot update" or console command "reboot update" if a bootable android already flashed, make sure typec usb connected to PC before doing this.
:[[File:cm4_usb_download.jpg]]
:[[File:m2s_android_install_3.png]]
:[[File:m2s_android_install_2.png]]

:3. Click the Start button of the download tool and wait for upgrade complete.

:[[File:m2s_android_install_4.png]]

:4. After Burning successfull, Unplug the type-c usb and connect to power supply adaptor to startup.

:[[File:m2s_android_install_5.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ https://github.com/BPI-SINOVOIP/BPI-A311D-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-A311D-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi CM4 DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi CM4 DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c1|| enable i2c 1
|-
| 3|| i2c2|| enable i2c 2
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m2s:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m2s:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m2s:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m2s_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/bananapi/bananapi_m2s/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c1 i2c2 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/bananapi/bananapi_m2s/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm64/boot/dts/amlogic/overlay/bananapi_m2s/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===Switch Mipi Panel===
:The default android release image only support one mipi panel because hw has no detect logic for different panel at boot, so [800x1280 bpi panel] enabled as default, but you can change to [1200x1920 bpi panel] as defualt in Settings->Panel Output

:[[File:m2s_panel_switch.png]]

===Panel Rotation===
The two 10" mipi panels are all portrait hw display, so the default android release image is portrait mode, but you can rotate it to 90/180/270 in two ways.

:1. UI Rotation in Settings->Display->Screen rotation
:[[File:m2s-rotation.png]]

:2. SurfaceFlinger rotation, need [https://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Build_Android_Source_Code modify android source code and build]
:Change the default sf rotation property
diff --git a/device/bananapi/bananapi_m2s/bananapi_m2s.mk b/device/bananapi/bananapi_m2s/bananapi_m2s.mk
index 1f51703..d592a44 100644
--- a/device/bananapi/bananapi_m2s/bananapi_m2s.mk
+++ b/device/bananapi/bananapi_m2s/bananapi_m2s.mk
@@ -579,6 +579,6 @@ PRODUCT_PROPERTY_OVERRIDES += \
else
PRODUCT_PROPERTY_OVERRIDES += \
ro.sf.lcd_density=213 \
- ro.sf.primary_display_orientation=0
+ ro.sf.primary_display_orientation=90
endif

:Change the touch panel rotation in dts
diff --git a/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts b/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
index 4a698b0..3d41b63 100755
--- a/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
+++ b/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
@@ -876,8 +876,8 @@
reg = <0x5d>;
reset-gpio = <&gpio GPIOA_6 GPIO_ACTIVE_HIGH>;
irq-gpio = <&gpio GPIOA_5 GPIO_ACTIVE_HIGH>;
- rotation = <4>; /* sf_rotation 0 */
- //rotation = <0>; /* sf_rotation 90*/
+ //rotation = <4>; /* sf_rotation 0 */
+ rotation = <0>; /* sf_rotation 90*/
//rotation = <5>; /* sf_rotation 180 */
//rotation = <3>; /* sf_rotation 270 */

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 16bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Flogo_create_tools%2Fm2s_android_bootlogo_tool.zip m2s_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m2s_android_bootlogo_tool.zip
$ cd m2s_android_bootlogo_tool/
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_secondary.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_secondary.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m2s_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M2S#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [https://wiki.banana-pi.org/Banana_Pi_BPI-CM4#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-cm4-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install the linux image in udisk with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-cm4-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_M2S#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-cm4-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

:4. Install with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-cm4-xxx.img.zip /dev/mmcblk0

:5. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M2S-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/khadas-g12b-v2015.01-m2s u-boot] the [https://github.com/Dangku/amlogic-linux/tree/khadas-g12b-4.9.y-m2s kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp/tree/master/aml-pack/g12b/bpi-m2s/linux BPI-M2S-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/overlays/
hifi_pcm5122.dtbo pdmmic.dtbo sdio.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_c-beeper.dtbo spi0.dtbo waveshare_tft35c_lcd.dtbo
i2c2.dtbo pwm_cd-c.dtbo spi0_flash.dtbo wifi_bt_rtl8822cs.dtbo
i2s.dtbo pwm_cd.dtbo uart1_cts_rts.dtbo i2smic.dtbo pwm_ef.dtbo
uart1.dtbo os08a10.dtbo pwm_ef-f.dtbo uart2.dtbo

:2. Update the overlays env in vfat /boot/env.txt to enable what you want.

# Device Tree Overlays
# uart1 -- Enable UART1 (uart_A, GPIO Header PIN8 & PIN10)
# pwm_c -- Enable PWM_C (GPIO Header PIN7)
# i2c2 -- Enable i2c2 (GPIO Header PIN3 & PIN5)
# spi0 -- Enable SPI0 (GPIO Header PIN19 & PIN21 & PIN23 & PIN24)
overlays="i2c2 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===Enable Camera===
:The linux release image is camera disabled default, according to the following configuration, it can be enabled by yourself.

:1. Update the [https://wiki.banana-pi.org/Getting_Started_with_BPI-CM4#DTB_overlay dtb overlays] env in /boot/env.txt to enable camera dtbo.

overlays="os08a10"

:2. Add camera modules to /etc/modules
iv009_isp_iq
iv009_isp_lens
iv009_isp_sensor
iv009_isp

:3. Create and add camera modules options to /etc/modprobe.d/os08a10.conf
#choose camera calibration parameters
options iv009_isp_iq cali_name=0
#choose isp register sequence
options iv009_isp_sensor isp_seq_num=0

:4. Enable camera isp systemd service
$ sudo systemctl enable camera_isp_3a_server.service

:Camera device is /dev/video0 after reboot.

===Switch Mipi Panel===
:The default linux release image only support one mipi panel because hw has no detect logic for different panel at boot, so 800x1280 bpi panel enabled as default, but you can change to [1200x1920 bpi panel] as defualt in /boot/lcd_env.txt
# Mipi panel type
# Symbol | Resolution
# ----------------------+-------------
# "lcd_0" | 10" 800x1280 panel
# "lcd_1" | 10" 1200x1920 panel
panel_type=lcd_0

:'''Note''': Dual display is not work on linux, so disconnect hdmi cable when mipi used.

===Panel Rotation===
:The two 10" mipi panels are all portrait hw display, so the default release image is portrait mode, but you can rotate it to 90/180/270.

:For Desktop image, create a xorg configuration file /usr/share/X11/xorg.conf.d/10-fbdev-rotate.conf with contents:

Section "Device"
Identifier "Configured Video Device"
# Rotate off
# Option "Rotate" "off"
# Rotate Right / clockwise, 90 degrees
Option "Rotate" "CW"
# Rotate upside down, 180 degrees
# Option "Rotate" "UD"
# Rotate counter clockwise, 270 degrees
# Option "Rotate" "CCW"

EndSection

Section "InputClass"
Identifier "Coordinate Transformation Matrix"
MatchIsTouchscreen "on"
MatchProduct "goodix-ts"
MatchDevicePath "/dev/input/event0"
MatchDriver "libinput"
# Rotate Right / clockwise, 90 degrees
Option "CalibrationMatrix" "0 1 0 -1 0 1 0 0 1"
# Rotate upside down, 180 degrees
# Option "CalibrationMatrix" "-1 0 1 0 -1 1 0 0 1"
# otate counter clockwise, 270 degrees
# Option "CalibrationMatrix" "0 -1 1 1 0 0 0 0 1"

EndSection

:For Server image, you can change the framebuffer rotation in two ways:

:1. Sysfs dynamically change.

echo 0 > /sys/class/graphics/fbcon/rotate //origin 0 degree
echo 1 > /sys/class/graphics/fbcon/rotate //90 degree
echo 2 > /sys/class/graphics/fbcon/rotate //180 degree
echo 3 > /sys/class/graphics/fbcon/rotate //270 degree

:2. Boot Configuration change.
:change the fb_rotate env in /boot/env.txt

# Framebuffer Rotate
# 0 - origin 0 degree
# 1 - 90 degree
# 2 - 180 degree
# 3 - 270 degree
fb_rotate=0

===Enable Wifi and BT===
:CM4 has onboard wifi/bt RTL8822CS, and is not enabled in default image, you can enable it with the following procedure.

:1. Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:2. Install bluetooth packages for server images
$ sudo apt update
$ sudo apt install bluez rfkill
$ bluetoothctl

:3. Reboot system

===Wifi client===
$ ip link set wlan0 up
// if "RTNETLINK answers: Operation not possible due to RF-kill" occurs, enter "rfkill unblock wifi" and try set wlan0 up again.
$ iw dev wlan0 scan | grep SSID
$ vim /etc/wpa_supplicant/wpa_supplicant.conf

network={
ssid="" //device name
psk="" //password
priority=1
}

$ wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -B
$ dhclient wlan0

===WiringPi===
: Note: This WiringPi only support set 26pins gpio to output, input, pwm or software pwm, for io functions as i2c, spi, ..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/Dangku/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 26pins status.
[[File:cm4_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/Dangku/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/blinkall.c blinkall], blink all pin header gpios, no extend board.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/lcd-bpi.c lcd1602-pi], [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/52pi-bpi.c 52pi-bpi], [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/matrixled-bpi.c matrixled-bpi], [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/berryclip-bpi.c berryclip-bpi], [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get Install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get Install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. copy the target file to /boot/firmware/ or /boot/ directory.

===EC20 LTE 4G Module===
:1. AT test
:After the module is connected and Linux OS bootup. several ttyUSB* device files are created in the directory /dev. For EC20, /dev/ttyUSB2 is the AT port.

:2. Connect Network via qmi_wwan on Ubuntu Desktop

:Click edit connections in network manager menu
:[[File:ec20_desktop_0.png]]

:Add a new mobile broadband connection
:[[File:ec20_desktop_1.png]]

:Choose qmi channel device
::When the qmi_wwan_q driver has been installed in the module, a network device and a QMI channel are created. The network device is named as wwanX and the QMI channel is /dev/cdc-wdmX. The network device is used for data transmission, and QMI channel is used for QMI message interaction
:[[File:ec20_desktop_2.png]]

:Choose carrier provider's country region
:[[File:ec20_desktop_3.png]]

:Choose carrier provider.
:[[File:ec20_desktop_4.png]]
:[[File:ec20_desktop_5.png]]
:Set connection name, carrier connection username/password and APN if needed.
:[[File:ec20_desktop_6.png]]

:Setup finished, now you can connect it.
:[[File:ec20_desktop_7.png]]

:3. Connect Network via pppd on Ubuntu&Debian Server

:Install pppd
$ sudo apt install ipppd

:Change AT device, username and password to your local carrier in /etc/ppp/peers/quectel-ppp
:[[File:ec20_server_pppd_uname.png]]

:Change APN to your local carrier in /etc/ppp/peers/quectel-chat-connect
:[[File:ec20_server_pppd_apn.png]]

: Two ways command to start pppd, you can check the process of PPP calling setup log [https://github.com/Dangku/readme/blob/master/cm4/ec20_pppd.log here].
# pppd call quectel-ppp &
::or
# quectel-pppd.sh /dev/ttyUSB2 <apn> <username> <password>

:Terminate pppd process:
# quectel-ppp-kill

:4. Connect Network via qmi_wwan on Ubuntu&Debian Server

:[quectel-CM] is a connection manager program for you to set up data connection manually. You can check the process of qmi_wwan calling setup log [https://github.com/Dangku/readme/blob/master/cm4/ec20_qmiwwan.log here].

# quectel-CM &

:Terminate quectel-CM process:

# killall quectel-CM

===Boot Linux from SSD===
:A311d soc rom and [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp BPI-M2S-bsp] uboot are both not support nvme boot, so the only way for booting linux from SSD is create a bootable sdcard or emmc with bootloader and boot partition flashed, then load rootfs from SSD. After bootup, everything will run from SSD. You need a minipcie to nvme adapter board because bananapi cm4io has a minipcie slot onboard.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_CM4#Install_Image_to_SDcard flash the CM4 Linux image to sdcard or emmc] for bootable and also flash it to the nvme ssd for loading rootfs.
:2. Bootup the CM4 board with [https://wiki.banana-pi.org/Getting_Started_with_CM4#Boot_Sequence sdcard or emmc], modify /boot/boot.ini to load rootfs from nvme partition for kernel.
diff a/boot/boot.ini b/boot/boot.ini
index 2222e79..c485067 100755
--- a/boot/boot.ini
+++ b/boot/boot.ini
@@ -20,6 +20,8 @@ fi;

if test "${devtype}" = "usb"; then setenv rootfsdev "/dev/sda2"; fi

+# force set root=/dev/nvme0n1p2
+setenv rootfsdev "/dev/nvme0n1p2"
+
# Load env.txt
fatload ${devtype} ${devno}:1 ${env_loadaddr} env.txt
env import -t ${env_loadaddr} ${filesize};
:3. Reboot the system, kernel will load rootfs from nvme ssd.
:[[File:cm4_ssd_rootfs.png]]

:4. Test performance
:You can verify the performance of your SSD on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and nvme ssd (Samsung 970EVOPlus)
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Nvme SSD Test Result
|-
| HDParm || Disk Read || 60.67 MB/s || 148.80 MB/s || 351.29 MB/s
|-
| HDParm || Cached Disk Read || 56.71 MB/s || 141.02 MB/s || 347.03 MB/s
|-
| DD || Disk Write || 14 MB/s || 51.0 MB/s || 244 MB/s
|-
| FIO || 4k random read || 2176 IOPS (8704 KB/s) || 8438 IOPS (33753 KB/s) || 101386 IOPS (405544 KB/s)
|-
| FIO || 4k random write || 932 IOPS (3729 KB/s) || 10876 IOPS (43505 KB/s) || 43206 IOPS (172827 KB/s)
|-
| IOZone || 4k read || 8586 KB/s || 20311 KB/s || 119475 KB/s
|-
| IOZone || 4k write || 2385 KB/s || 19016 KB/s || 90619 KB/s
|-
| IOZone || 4k random read || 6734 KB/s || 20807 KB/s || 51517 KB/s
|-
| IOZone || 4k random write || 3737 KB/s || 22731 KB/s || 95139 KB/s
|-
| || || Score: 1076 || Score: 5446 || Score: 24550
|}

===Disable SDcard UHS mode===
:Add disableuhs option to kernel bootargs in /boot/env.txt to disable sdcard uhs capability

# User kernel args
# Add customer kernel args here
user_kernel_args=pci=pcie_bus_safe disableuhs

==Other Development==

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the type-c usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m2s:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m2s_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m2s_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
2453 bytes read in 3 ms (797.9 KiB/s)
## Executing script at 03080000
Starting boot.ini...
reading env.txt
3483 bytes read in 7 ms (485.4 KiB/s)
HDMI: Autodetect: 1080p60hz
reading Image.gz
10924573 bytes read in 611 ms (17.1 MiB/s)
reading bananapi_m2s.dtb
88054 bytes read in 12 ms (7 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/wifi_bt_rtl8822cs.dtbo
729 bytes read in 6 ms (118.2 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m2s# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A '''extreme situation''' is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions

Getting Started with CM4

2023-02-17T09:50:02Z

Czj: /* Enable Wifi and BT */

=Introduction=
BananaPi BPI-CM4 new design with Amlogic A311D Quad core ARM Cortex-A73 and dual core ARM Cortex-A53 CPU ,ARM G52 MP4(6EE) GPU,NPU for AI at 5.0 TOPS, support Camera and MIPI-CSI interface ,HDMI output,2 Gigabit port . 4G RAM and 16 GB eMMC flash.

[[Banana Pi BPI-CM4]]

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via type-c, only support windows.
:2. Download the latest [https://wiki.banana-pi.org/Banana_Pi_BPI-CM4#Android android image], and confirm that the md5 checksum is correct.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m2s_android_install_1.png]]

:2. Short the usb boot test point on the main board, plugin type-c usb cable to PC or press the RST button if power adapter already connected, about two seconds later, the board will enter usb download mode and be identified correctly by PC. You can also enter usb download mode with adb command "adb reboot update" or console command "reboot update" if a bootable android already flashed, make sure typec usb connected to PC before doing this.
:[[File:cm4_usb_download.jpg]]
:[[File:m2s_android_install_3.png]]
:[[File:m2s_android_install_2.png]]

:3. Click the Start button of the download tool and wait for upgrade complete.

:[[File:m2s_android_install_4.png]]

:4. After Burning successfull, Unplug the type-c usb and connect to power supply adaptor to startup.

:[[File:m2s_android_install_5.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ https://github.com/BPI-SINOVOIP/BPI-A311D-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-A311D-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi CM4 DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi CM4 DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c1|| enable i2c 1
|-
| 3|| i2c2|| enable i2c 2
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m2s:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m2s:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m2s:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m2s_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/bananapi/bananapi_m2s/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c1 i2c2 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/bananapi/bananapi_m2s/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm64/boot/dts/amlogic/overlay/bananapi_m2s/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===Switch Mipi Panel===
:The default android release image only support one mipi panel because hw has no detect logic for different panel at boot, so [800x1280 bpi panel] enabled as default, but you can change to [1200x1920 bpi panel] as defualt in Settings->Panel Output

:[[File:m2s_panel_switch.png]]

===Panel Rotation===
The two 10" mipi panels are all portrait hw display, so the default android release image is portrait mode, but you can rotate it to 90/180/270 in two ways.

:1. UI Rotation in Settings->Display->Screen rotation
:[[File:m2s-rotation.png]]

:2. SurfaceFlinger rotation, need [https://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Build_Android_Source_Code modify android source code and build]
:Change the default sf rotation property
diff --git a/device/bananapi/bananapi_m2s/bananapi_m2s.mk b/device/bananapi/bananapi_m2s/bananapi_m2s.mk
index 1f51703..d592a44 100644
--- a/device/bananapi/bananapi_m2s/bananapi_m2s.mk
+++ b/device/bananapi/bananapi_m2s/bananapi_m2s.mk
@@ -579,6 +579,6 @@ PRODUCT_PROPERTY_OVERRIDES += \
else
PRODUCT_PROPERTY_OVERRIDES += \
ro.sf.lcd_density=213 \
- ro.sf.primary_display_orientation=0
+ ro.sf.primary_display_orientation=90
endif

:Change the touch panel rotation in dts
diff --git a/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts b/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
index 4a698b0..3d41b63 100755
--- a/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
+++ b/common/arch/arm64/boot/dts/amlogic/bananapi_m2s.dts
@@ -876,8 +876,8 @@
reg = <0x5d>;
reset-gpio = <&gpio GPIOA_6 GPIO_ACTIVE_HIGH>;
irq-gpio = <&gpio GPIOA_5 GPIO_ACTIVE_HIGH>;
- rotation = <4>; /* sf_rotation 0 */
- //rotation = <0>; /* sf_rotation 90*/
+ //rotation = <4>; /* sf_rotation 0 */
+ rotation = <0>; /* sf_rotation 90*/
//rotation = <5>; /* sf_rotation 180 */
//rotation = <3>; /* sf_rotation 270 */

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 16bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Flogo_create_tools%2Fm2s_android_bootlogo_tool.zip m2s_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m2s_android_bootlogo_tool.zip
$ cd m2s_android_bootlogo_tool/
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_secondary.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_secondary.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m2s_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M2S#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [https://wiki.banana-pi.org/Banana_Pi_BPI-CM4#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-cm4-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install the linux image in udisk with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-cm4-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_M2S#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-cm4-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

:4. Install with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-cm4-xxx.img.zip /dev/mmcblk0

:5. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M2S-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/khadas-g12b-v2015.01-m2s u-boot] the [https://github.com/Dangku/amlogic-linux/tree/khadas-g12b-4.9.y-m2s kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp/tree/master/aml-pack/g12b/bpi-m2s/linux BPI-M2S-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/overlays/
hifi_pcm5122.dtbo pdmmic.dtbo sdio.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_c-beeper.dtbo spi0.dtbo waveshare_tft35c_lcd.dtbo
i2c2.dtbo pwm_cd-c.dtbo spi0_flash.dtbo wifi_bt_rtl8822cs.dtbo
i2s.dtbo pwm_cd.dtbo uart1_cts_rts.dtbo i2smic.dtbo pwm_ef.dtbo
uart1.dtbo os08a10.dtbo pwm_ef-f.dtbo uart2.dtbo

:2. Update the overlays env in vfat /boot/env.txt to enable what you want.

# Device Tree Overlays
# uart1 -- Enable UART1 (uart_A, GPIO Header PIN8 & PIN10)
# pwm_c -- Enable PWM_C (GPIO Header PIN7)
# i2c2 -- Enable i2c2 (GPIO Header PIN3 & PIN5)
# spi0 -- Enable SPI0 (GPIO Header PIN19 & PIN21 & PIN23 & PIN24)
overlays="i2c2 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===Enable Camera===
:The linux release image is camera disabled default, according to the following configuration, it can be enabled by yourself.

:1. Update the [https://wiki.banana-pi.org/Getting_Started_with_BPI-CM4#DTB_overlay dtb overlays] env in /boot/env.txt to enable camera dtbo.

overlays="os08a10"

:2. Add camera modules to /etc/modules
iv009_isp_iq
iv009_isp_lens
iv009_isp_sensor
iv009_isp

:3. Create and add camera modules options to /etc/modprobe.d/os08a10.conf
#choose camera calibration parameters
options iv009_isp_iq cali_name=0
#choose isp register sequence
options iv009_isp_sensor isp_seq_num=0

:4. Enable camera isp systemd service
$ sudo systemctl enable camera_isp_3a_server.service

:Camera device is /dev/video0 after reboot.

===Switch Mipi Panel===
:The default linux release image only support one mipi panel because hw has no detect logic for different panel at boot, so 800x1280 bpi panel enabled as default, but you can change to [1200x1920 bpi panel] as defualt in /boot/lcd_env.txt
# Mipi panel type
# Symbol | Resolution
# ----------------------+-------------
# "lcd_0" | 10" 800x1280 panel
# "lcd_1" | 10" 1200x1920 panel
panel_type=lcd_0

:'''Note''': Dual display is not work on linux, so disconnect hdmi cable when mipi used.

===Panel Rotation===
:The two 10" mipi panels are all portrait hw display, so the default release image is portrait mode, but you can rotate it to 90/180/270.

:For Desktop image, create a xorg configuration file /usr/share/X11/xorg.conf.d/10-fbdev-rotate.conf with contents:

Section "Device"
Identifier "Configured Video Device"
# Rotate off
# Option "Rotate" "off"
# Rotate Right / clockwise, 90 degrees
Option "Rotate" "CW"
# Rotate upside down, 180 degrees
# Option "Rotate" "UD"
# Rotate counter clockwise, 270 degrees
# Option "Rotate" "CCW"

EndSection

Section "InputClass"
Identifier "Coordinate Transformation Matrix"
MatchIsTouchscreen "on"
MatchProduct "goodix-ts"
MatchDevicePath "/dev/input/event0"
MatchDriver "libinput"
# Rotate Right / clockwise, 90 degrees
Option "CalibrationMatrix" "0 1 0 -1 0 1 0 0 1"
# Rotate upside down, 180 degrees
# Option "CalibrationMatrix" "-1 0 1 0 -1 1 0 0 1"
# otate counter clockwise, 270 degrees
# Option "CalibrationMatrix" "0 -1 1 1 0 0 0 0 1"

EndSection

:For Server image, you can change the framebuffer rotation in two ways:

:1. Sysfs dynamically change.

echo 0 > /sys/class/graphics/fbcon/rotate //origin 0 degree
echo 1 > /sys/class/graphics/fbcon/rotate //90 degree
echo 2 > /sys/class/graphics/fbcon/rotate //180 degree
echo 3 > /sys/class/graphics/fbcon/rotate //270 degree

:2. Boot Configuration change.
:change the fb_rotate env in /boot/env.txt

# Framebuffer Rotate
# 0 - origin 0 degree
# 1 - 90 degree
# 2 - 180 degree
# 3 - 270 degree
fb_rotate=0

===Enable Wifi and BT===
:CM4 has onboard wifi/bt RTL8822CS, and is not enabled in default image, you can enable it with the following procedure.

:1. Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:2. Install bluetooth packages for server images
$ sudo apt update
$ sudo apt install bluez rfkill
$ bluetoothctl

:3. Reboot system

===Wifi client===
$ ip link set wlan0 up
$ iw dev wlan0 scan | grep SSID
$ vim /etc/wpa_supplicant/wpa_supplicant.conf

network={
ssid="" //device name
psk="" //password
priority=1
}

$ wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -B
$ dhclient wlan0

===WiringPi===
: Note: This WiringPi only support set 26pins gpio to output, input, pwm or software pwm, for io functions as i2c, spi, ..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/Dangku/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 26pins status.
[[File:cm4_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/Dangku/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/blinkall.c blinkall], blink all pin header gpios, no extend board.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/lcd-bpi.c lcd1602-pi], [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/52pi-bpi.c 52pi-bpi], [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/matrixled-bpi.c matrixled-bpi], [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:[https://github.com/Dangku/amlogic-wiringPi/blob/master/examples/berryclip-bpi.c berryclip-bpi], [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get Install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get Install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. copy the target file to /boot/firmware/ or /boot/ directory.

===EC20 LTE 4G Module===
:1. AT test
:After the module is connected and Linux OS bootup. several ttyUSB* device files are created in the directory /dev. For EC20, /dev/ttyUSB2 is the AT port.

:2. Connect Network via qmi_wwan on Ubuntu Desktop

:Click edit connections in network manager menu
:[[File:ec20_desktop_0.png]]

:Add a new mobile broadband connection
:[[File:ec20_desktop_1.png]]

:Choose qmi channel device
::When the qmi_wwan_q driver has been installed in the module, a network device and a QMI channel are created. The network device is named as wwanX and the QMI channel is /dev/cdc-wdmX. The network device is used for data transmission, and QMI channel is used for QMI message interaction
:[[File:ec20_desktop_2.png]]

:Choose carrier provider's country region
:[[File:ec20_desktop_3.png]]

:Choose carrier provider.
:[[File:ec20_desktop_4.png]]
:[[File:ec20_desktop_5.png]]
:Set connection name, carrier connection username/password and APN if needed.
:[[File:ec20_desktop_6.png]]

:Setup finished, now you can connect it.
:[[File:ec20_desktop_7.png]]

:3. Connect Network via pppd on Ubuntu&Debian Server

:Install pppd
$ sudo apt install ipppd

:Change AT device, username and password to your local carrier in /etc/ppp/peers/quectel-ppp
:[[File:ec20_server_pppd_uname.png]]

:Change APN to your local carrier in /etc/ppp/peers/quectel-chat-connect
:[[File:ec20_server_pppd_apn.png]]

: Two ways command to start pppd, you can check the process of PPP calling setup log [https://github.com/Dangku/readme/blob/master/cm4/ec20_pppd.log here].
# pppd call quectel-ppp &
::or
# quectel-pppd.sh /dev/ttyUSB2 <apn> <username> <password>

:Terminate pppd process:
# quectel-ppp-kill

:4. Connect Network via qmi_wwan on Ubuntu&Debian Server

:[quectel-CM] is a connection manager program for you to set up data connection manually. You can check the process of qmi_wwan calling setup log [https://github.com/Dangku/readme/blob/master/cm4/ec20_qmiwwan.log here].

# quectel-CM &

:Terminate quectel-CM process:

# killall quectel-CM

===Boot Linux from SSD===
:A311d soc rom and [https://github.com/BPI-SINOVOIP/BPI-M2S-bsp BPI-M2S-bsp] uboot are both not support nvme boot, so the only way for booting linux from SSD is create a bootable sdcard or emmc with bootloader and boot partition flashed, then load rootfs from SSD. After bootup, everything will run from SSD. You need a minipcie to nvme adapter board because bananapi cm4io has a minipcie slot onboard.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_CM4#Install_Image_to_SDcard flash the CM4 Linux image to sdcard or emmc] for bootable and also flash it to the nvme ssd for loading rootfs.
:2. Bootup the CM4 board with [https://wiki.banana-pi.org/Getting_Started_with_CM4#Boot_Sequence sdcard or emmc], modify /boot/boot.ini to load rootfs from nvme partition for kernel.
diff a/boot/boot.ini b/boot/boot.ini
index 2222e79..c485067 100755
--- a/boot/boot.ini
+++ b/boot/boot.ini
@@ -20,6 +20,8 @@ fi;

if test "${devtype}" = "usb"; then setenv rootfsdev "/dev/sda2"; fi

+# force set root=/dev/nvme0n1p2
+setenv rootfsdev "/dev/nvme0n1p2"
+
# Load env.txt
fatload ${devtype} ${devno}:1 ${env_loadaddr} env.txt
env import -t ${env_loadaddr} ${filesize};
:3. Reboot the system, kernel will load rootfs from nvme ssd.
:[[File:cm4_ssd_rootfs.png]]

:4. Test performance
:You can verify the performance of your SSD on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and nvme ssd (Samsung 970EVOPlus)
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Nvme SSD Test Result
|-
| HDParm || Disk Read || 60.67 MB/s || 148.80 MB/s || 351.29 MB/s
|-
| HDParm || Cached Disk Read || 56.71 MB/s || 141.02 MB/s || 347.03 MB/s
|-
| DD || Disk Write || 14 MB/s || 51.0 MB/s || 244 MB/s
|-
| FIO || 4k random read || 2176 IOPS (8704 KB/s) || 8438 IOPS (33753 KB/s) || 101386 IOPS (405544 KB/s)
|-
| FIO || 4k random write || 932 IOPS (3729 KB/s) || 10876 IOPS (43505 KB/s) || 43206 IOPS (172827 KB/s)
|-
| IOZone || 4k read || 8586 KB/s || 20311 KB/s || 119475 KB/s
|-
| IOZone || 4k write || 2385 KB/s || 19016 KB/s || 90619 KB/s
|-
| IOZone || 4k random read || 6734 KB/s || 20807 KB/s || 51517 KB/s
|-
| IOZone || 4k random write || 3737 KB/s || 22731 KB/s || 95139 KB/s
|-
| || || Score: 1076 || Score: 5446 || Score: 24550
|}

===Disable SDcard UHS mode===
:Add disableuhs option to kernel bootargs in /boot/env.txt to disable sdcard uhs capability

# User kernel args
# Add customer kernel args here
user_kernel_args=pci=pcie_bus_safe disableuhs

==Other Development==

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the type-c usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m2s:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m2s_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m2s_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M2S#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
2453 bytes read in 3 ms (797.9 KiB/s)
## Executing script at 03080000
Starting boot.ini...
reading env.txt
3483 bytes read in 7 ms (485.4 KiB/s)
HDMI: Autodetect: 1080p60hz
reading Image.gz
10924573 bytes read in 611 ms (17.1 MiB/s)
reading bananapi_m2s.dtb
88054 bytes read in 12 ms (7 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/wifi_bt_rtl8822cs.dtbo
729 bytes read in 6 ms (118.2 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m2s# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A '''extreme situation''' is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions

Getting Started with BPI-R3

2023-02-08T08:52:32Z

Czj: /* Wifi & Serial cable */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.
'''
'''UART_TX0 is the Boot Strapping PIN and must be kept low during power-on.'''

[[File:Strapping.png|720px]]

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with BPI-R3

2023-02-03T01:22:20Z

Czj: /* Wifi & Serial cable */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.
[[Image:Strapping.png|720px]]

UART_TX0 is the Boot Strapping PIN and must be kept low during power-on.

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with BPI-R3

2023-02-03T01:22:04Z

Czj: /* Wifi & Serial cable */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.
[[Image:Strapping.png|720px]]
UART_TX0 is the Boot Strapping PIN and must be kept low during power-on

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing

='''Reference Link'''=

http://forum.banana-pi.org/

Getting Started with BPI-R3

2023-02-03T01:19:38Z

Czj: /* Wifi & Serial cable */

[[zh:快速上手香蕉派 BPI-R3]]
==Introduction==
[[File:Banana_pi_751.jpg]]

Banana Pi BPI-R3 Router board with MediaTek MT7986(Filogic 830) quad core ARM A53 + MT7531A chip design ,2G DDR RAM ,8G eMMC flash onboard,It is a very high performance open source router development board,support Wi-Fi 6/6E 2.4G wifi use MT7975N and 5G wifi use MT7975P, support 2 SFP 2.5GbE port, and 5 GbE network port.

==MediaTek MT7986(Filogic 830)==

The MT7986(Filogic 830) integrates four Arm Cortex-A53 cores up to 2GHz with up to 18,000 DMIPs of processing power and 6Gbps of dual 4x4 Wi-Fi 6/6E connectivity. It has two 2.5g Ethernet interfaces and serial peripheral interfaces (SPI). Filogic 830‘s built-in hardware acceleration engine enables fast and reliable Wi-Fi offloading and wireless network connection. In addition, the chip supports Mediatek FastPath™ technology, which is suitable for games, AR/VR and other low-latency applications.

Wi-fi 6E has many advantages over its predecessors, including lower latency, larger bandwidth capacity and faster transmission rates. Wireless network devices supporting the 6GHz band mainly use 160MHz wide channel and 6GHz uncongested bandwidth to provide multigigabit transmission and low-latency wi-fi connection, providing reliable wireless network for streaming media, games, AR/VR and other applications.

==Key Features==

*. MediaTek MT7986(Filogic 830) Quad core ARM Cortex A53+MT7531 chip design
*. Wifi 6/6E 4x4 2.4G Wifi(MT7975N) +4x4 5G Wifi(MT7975P)
*. 2G DDR RAM
*. 8G eMMC flash
*. 2 SFP 2.5GbE
*. 5 GbE network port
*. POE support (optional)
*. Mini PCIe via USB
*. M.2 KEY-E PCIe inerface
*. Mciro SD card interface
*. 26 PIN GPIO

=Development=
==Basic Development==
===Prepare to develop===
* Prepare 8G/above TF card, USB-Serial interface, Ubuntu System
* Using your USB-Serial Connect debug console on BPI-R3

[[Image:R3_debug_console.jpg|320px]]

* R3 bootstrap and device select Jumper Setting
[[Image:BPI-R3-Jumper.png|320px]]

Note: SW1-A and SW1-B is for boot strap selecting;
SW1-C is that SPI-Nand or SPI-Nor Device is connected to CPU's SPI bus;
SW1-D is that SD Card or EMMC device is connected tp CPU's EMMC bus.

* Examples:
All Jumper is High.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

All Jumper is Low.
[[Image:BPI-R3-Jumper-ALL-Low.png|320px]]

===How to burn image to SD card===
A. Note: burn image to SD card on linux computer
1.You could download latest image from our forum
* Here is the example image link:

2.Install bpi-tools on your Ubuntu. If you can't access this URL or any other problems, please go to [https://github.com/BPI-SINOVOIP/bpi-tools bpi-tools repo] and install this tools manually.
* apt-get install pv
* curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

3.After you download the image, insert your TF card into your Ubuntu
* Execute "bpi-copy xxx.img /dev/sdx" to install image on your TF card

4.After step 3, then you can insert your TF card into R3, and press power button to setup R3
B. Note: burn image to SD card on windows computer
1. Download the tools from the website: https://sourceforge.net/projects/win32diskimager/
2. Install the tools into Windows computer.
3. flash image into SD card.

C. Change Boot Jumper to boot from SD, Enable SD Card Device.
[[Image:BPI-R3-Jumper-ALL-High.png|320px]]

====How to burn image to onboard eMMC====
Note: because SD card and EMMC device share one SOC's interface, you need flash one SD image firstly, then R3 boot from SD card, then flash nand image into Nand, then change boot strap to boot from nand, you need flash EMMC image into EMMC. Finally you change bootstrap to boot from EMMC.

Before burning image to eMMC, please prepare a SD card with flashed bootable image and a USB disk. Let's take OpenWrt image (mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img, mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) for example, the steps are below:

1. Insert the flashed SD card and power on to start the board.(the image "mtk-bpi-r3-SD-WAN1-SFP1-20220619-single-image.img" on the SD card can be OpenWrt or other linux OS like ubuntu...)

2. Copy Nand bootable and EMMC boot OpenWrt image(mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin, bl2_emmc.img, mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img) to USB disk, if the image is compressed please uncompress it before copying to USB disk.

3. Plug in USB disk to the board, and mount the USB to /mnt or other directory as follows: (you can skip mounting if it is mounted automatically)
* mount -t vfat /dev/sda1 /mnt
* change your directory to the mounting point, here is : cd /mnt

4. Execute following command to enable and copy image to nand flash:
* mtd erase /dev/mtd0
* dd if=mtk-bpi-r3-NAND-WAN1-SFP1-20220619-single-image.bin of=/dev/mtdblock0

5. Shutdown, remove SD card, and change bootstrap to boot from nand flash and change SD/EMMC switch jumper to EMMC, restart the board from Nand Flash.
Note: Enable EMMC device, boot strap is from nand
[[Image:BPI-R3-Jumper-Flash-EMMC.png|320px]]

6. repeat step 3, mount u-disk to /mnt, Execute following command to enable and copy image to EMMC device:
* mount -t vfat /dev/sda1 /mnt
* echo 0 > /sys/block/mmcblk0boot0/force_ro
* dd if=bl2_emmc.img of=/dev/mmcblk0boot0
* dd if=mtk-bpi-r3-EMMC-WAN1-SFP1-20220619-single-image.img of=/dev/mmcblk0
* mmc bootpart enable 1 1 /dev/mmcblk0

7. power off R3 board, remove u-disk driver, change bootstrap to boot from emmc device.
Note: Enable EMMC device, boot strap is from EMMC.
[[Image:BPI-R3-Jumper-Boot-EMMC.png|320px]]

=== Network-Configuration===
*Network-Configuration refer to: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start
*Network Interface: eth1, lan0 is for WAN; lan4, rax0, lan2, lan5, ra0, lan3, lan1 is for LAN, ra0 is for 2.4G wireless, rax0 is for 5G wireless.

[[Image:BPI-R3_network_interface.jpg|640px]]

root@OpenWrt:/# ifconfig

br-lan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
inet6 addr: fd63:8bea:d5ce::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

br-wan Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8538 (8.3 KiB)

eth0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
inet6 addr: fe80::eca1:57ff:fe81:ca19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4408 (4.3 KiB)
Interrupt:124

eth1 Link encap:Ethernet HWaddr 4A:BB:84:B4:5D:3F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8674 (8.4 KiB)
Interrupt:124

lan0 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan1 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan2 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan3 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan4 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lan5 Link encap:Ethernet HWaddr EE:A1:57:81:CA:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2418 (2.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368 (4.2 KiB) TX bytes:4368 (4.2 KiB)

ra0 Link encap:Ethernet HWaddr 00:0C:43:26:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6

rax0 Link encap:Ethernet HWaddr 02:0C:43:36:60:38
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@OpenWrt:/# brctl show br-wan

bridge name bridge id STP enabled interfaces
br-wan 7fff.eea15781ca19 no lan0, eth1

root@OpenWrt:/# brctl show br-lan

bridge name bridge id STP enabled interfaces
br-lan 7fff.eea15781ca19 no lan4, rax0, lan2, lan5, ra0, lan3, lan1

root@OpenWrt:/#

==Advanced Development==
===GPIO===
====26 Pins Definition====

[[Image:R3_gpio_40.jpg]]

====GPIO Control====
* echo xxx > /sys/class/gpio/export
* echo in/out > /sys/class/gpio/gpioxxx/direction
* echo 0/1 > /sys/class/gpio/gpioxxx/value

Check the base gpio, you could see mine is 411

[[Image:BPI-R3-GPIO-Base.jpg]]

For example: if you want to change gpio 22 as out highlevel, you need input commands like this：

* echo 433（22+411） > /sys/class/gpio/export
* echo out > /sys/class/gpio/gpio433/direction
* echo 1 > /sys/class/gpio/gpio433/value

===FAN===

[[Image:FAN.png]]

* R317 for 5V FAN and R318 for 12V FAN.
* CN23 supports PWM control while CN22 does not support.

====PWM FAN Control====
* echo 0 > /sys/class/pwm/pwmchip0/export
* echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
* echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
* echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity
* echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

===miniPCIe slot===
currently, miniPCIe slot only support one USB 4G module, example: EC25
when you insert one EC25 module, you may check it.

[[Image:BPI-R3-miniPCIe-Slot-EC25.jpg]]

===SFP===
After high and low temperature test, the following modules are suppoted by BPI-R3:

[[Image:SFP.png]]

===4G&5G===
* BPI-R3 supports 4G LTE EC25.
* If you want to use 5G on BPI-R3:
1. Insert 5G dongle into USB3.0.
2. Connect RG200U-CN to mini PCIe, connect SoC through USB2.0(speed limited).
3. Make an RG200U-CN LGA adapter board and insert it into M.2 KEY M.
Note: The availability of 4G/5G depends on the local carrier frequency band.

===Ap mode on BPI-R3===

* ra0 is MT7986a 2.4G wifi
* rax0 is MT7986a 5G wifi

===Wifi & Serial cable===
UART_TX0 is the Boot Strapping PIN and must be kept low during power-on
[[Image:Strapping.png]]
* '''If the chip type of serial cable is pl2303, the driver fails to load the firmware apparently and thus the wifi can't work.'''
* '''Other types including cp2102,ch340 and FDTI are all available, serial cable vlotage must be 3.3v LVTTL standard.

==FAQ==
*MT7986a Reference Manual for Develope Board(BPi)
::Google Drive：https://drive.google.com/file/d/1biSJmxnIpNzQroYDg9mtPtSTAv4i0DFf/view?usp=sharing

='''Reference Link'''=

http://forum.banana-pi.org/

File:Strapping.png

2023-02-03T01:17:03Z

Czj:

Getting Started with M5/M2Pro

2023-01-31T01:11:36Z

Czj: /* Install Image to EMMC */

=Introduction=
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]]]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_1.JPG|thumb|Amlogic S905X3 Processor]]
[[File:Banana_Pi_BPI-M5_2.jpg|thumb|Amlogic S905X3 Processor]]

Banana Pi M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port, IR Reciver, Audio Jack, 1 HDMI Out and USB type-c power supply.

Banana Pi M2Pro is the same SOC with M5, but different board layout. 2GB LPDDR4 and 16G eMMC flash, 2 USB 3.0 port,1GbE LAN port, rtl8821cu usb wifi/bt onboard, IR Reciver, 1 HDMI Out, 1 MicroUSB port, DC power supply.

=specifications=

*SoC – Amlogic S905X3 quad-core Cortex-A55 processor @ up to 2.0 GHz with
*Mali-G31 MP2 GPU @ 650Mhz
*System Memory – 4GB LPDDR4
*Storage – 16GB eMMC flash (option up to 64GB), MicroSD slot up to 2TB
*Video Output – HDMI 2.1 up to 4Kp60 with HDR, CEC, EDID
*Audio – 3.5mm audio jack, digital HDMI audio
*Connectivity – Gigabit Ethernet
*USB – 4x USB 3.0 ports via VL817 hub controller, 1x USB-C port (for power only?)
*Expansion – 40-pin Raspberry Pi header with 28x GPIO, UART, I2C, SPI, PWM, and power signal (+5V, +3.3V, GND).
*Debugging – 3-pin debug header
*Misc – Reset, Power, and U-boot button; power and activity LED’s; IR receiver
*Power Supply – 5V @3A via USB Type-C port
*Dimensions – 92x60mm (Not the same as Raspberry Pi PCB size, but they probably included the connectors during measurement)
*Weight – 48grams

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug. M2pro is used Micro-usb port for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].
:4. In Android SDcard is mmc0, emmc is mmc1, but in Linux SDcard is mmc1, emmc is mmc0.

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via USB type-c on M5 and Micro-usb on M2pro, only support windows.
:2. Download the latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2 android image], and confirm that the md5 checksum is correct.
:3. M5 and M2pro are compatiable with same android image.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m5_android_install_1.png]]

:2. M5/M2pro board disconnect power, press and hold SW4 button beside 40pin header, plugin type-c usb cable(microUSB on m2pro) to PC

:[[File:m5_android_install_2.png]]

:3. Click the Start button and wait for upgrade complete.

:[[File:m5_android_install_3.png]]

:4. After Burning successfull, Unplug the usb and connect to power supply adaptor to startup.

:[[File:m5_android_install_4.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ git clone https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi M5/M2Pro DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M5/M2pro DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c2|| enable i2c 2
|-
| 3|| i2c3|| enable i2c 3
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m5:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m5:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m5:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m5_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/amlogic/bananapi_m5/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c2 i2c3 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/amlogic/bananapi_m5/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm/boot/dts/amlogic/overlay/bananapi_m5/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===IR Remote Control Custom===
:Before starting this work, some android basic concepts and knowledge need to be known.

:*Linux kernel input key event.
:*Android keycode.
:*Linux keycode map to android keycode.
:*Android Adb function work on your PC

:1. pull the remote files from device
# adb pull /vendor/etc/remote.cfg
# adb pull /vendor/etc/remote.tab

:2. modify remote.cfg to enable remote debug message
:[[File:remotecfg.png]]

:push remote.cfg back

# adb root
# adb remount
# adb push remote.cfg /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.cfg
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000

:3. Get the remote keycode
:Press your remote key one by one and then print the dmesg to get the remote custom_code and each remote key code.

# adb shell dmesg | grep framecode=
:[[File:keycode.png]]

:custom_code = 0xfe01
:keycode = 0x00, 0x01, 0x09, 0x02, 0x0a, 0x05, 0x04 0x06, 0x03, 0x0b, 0x40, 0x48, 0x44

:4. Modify remote.tab to map the scancode to android keycode
:[[File:remotetab.png]]

:push remote.tab and test each key whether works

# adb root
# adb remount
# adb push remote.tab1 /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.tab
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -t /vendor/etc/remote.tab -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000
tabdir = /vendor/etc/remote.tab
custom_name = nec-test
fn_key_scancode = 0xffff
cursor_left_scancode = 0xffff
cursor_right_scancode = 0xffff
cursor_up_scancode = 0xffff
cursor_down_scancode = 0xffff
cursor_ok_scancode = 0xffff
custom_code = 0xfe01
release_delay = 80
map_size = 13
key[0] = 0x74
key[1] = 0x1008b
key[2] = 0x90066
key[3] = 0x20069
key[4] = 0xa006a
key[5] = 0x50067
key[6] = 0x4006c
key[7] = 0x6001c
key[8] = 0x30072
key[9] = 0xb0073
key[10] = 0x40009e
key[11] = 0x4800a4
key[12] = 0x440071

:5. Reboot the board

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. M5 and M2pro are compatiable with same Linux image.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install image with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_BPI-M5/M2Pro#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. There are two ways to install the linux image to board.
3.1 Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

3.2 Install the linux image in udisk with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/mmcblk0

:4. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M5-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M5-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/odroidg12-v2015.01-c4-m5 u-boot] the [https://github.com/Dangku/amlogic-linux/tree/odroidg12-4.9.y-c4-m5 kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M5-bsp BPI-M5-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/firmware/overlays/
custom_ir.dtbo pwm_b-backlight.dtbo spi0.dtbo
ds3231.dtbo pwm_c-beeper.dtbo uart1_cts_rts.dtbo
hifi_pcm5102a.dtbo pwm_cd-c.dtbo uart1.dtbo
hifi_pcm5122.dtbo pwm_cd.dtbo uart2.dtbo
i2c0.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_ef-f.dtbo waveshare_tft35c_lcd.dtbo
pwm_ab.dtbo sdio.dtbo waveshare_tft35c_rtp.dtbo

:2. Update the overlays env in vfat /boot/firmware/boot.ini to enable what you want. Default i2c0, spi0 and uart1 enabled.

# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "i2c0 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===WiringPi===
: Note: This WiringPi only support set 40pin gpio to output, input or software pwm, for io functions as i2c, spi, pwm..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/BPI-SINOVOIP/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m5_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/BPI-SINOVOIP/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-bpi, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:52pi-bpi, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled-bpi, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip-bpi, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Boot Linux from USB drive===

:S905x3 is not support usb boot in soc rom, so the only way for booting linux from usb drive is create a bootable sdcard or emmc with bootloader flashed, then load boot and rootfs from usb drive. After bootup, everything will run from usb drive.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash the M5/M2Pro Linux image to sdcard or emmc] for bootable and also flash it to the usb drive for loading boot and rootfs.
:2. Bootup the M5/M2pro board with [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Boot_Sequence sdcard or emmc], copy /boot/boot.ini to /boot/boot.ini.org so that bootloader load boot.ini fail and then try to load it from usb drive boot partition.
:3. Reboot the system, bootscript and rootfs will load from usb drive.
:[[File:m5_boot_from_usb.png]]

:4. Test performance
:You can verify the performance of your usb drive on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and usb drive
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Usb Drive Test Result
|-
| HDParm || Disk Read || 67.91 MB/s || 156.64 MB/s || 253.40 MB/s
|-
| HDParm || Cached Disk Read || 57.39 MB/s || 126.53 MB/s || 253.52 MB/s
|-
| DD || Disk Write || 13.0 MB/s || 48.8 MB/s || 149 MB/s
|-
| FIO || 4k random read || 2456 IOPS (9826 KB/s) || 9701 IOPS (38806 KB/s) || 5474 IOPS (21897 KB/s)
|-
| FIO || 4k random write || 938 IOPS (3753 KB/s) || 12888 IOPS (51554 KB/s) || 6980 IOPS (27920 KB/s)
|-
| IOZone || 4k read || 10615 KB/s || 29568 KB/s || 23770 KB/s
|-
| IOZone || 4k write || 4276 KB/s || 33585 KB/s || 18598 KB/s
|-
| IOZone || 4k random read || 8661 KB/s || 29637 KB/s || 19982 KB/s
|-
| IOZone || 4k random write || 4795 KB/s || 38177 KB/s || 22134 KB/s
|-
| || || Score: 1300 || Score: 7811 || Score: 5879
|}

==Other Development==

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp
:3. copy the target file to BPI-BOOT partition of linux image
$ cp boot-logo.bmp.gz /media/xxx/BPI-BOOT/

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 24bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Flogo_create_tools%2Fm5_android_bootlogo_tool.zip m5_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m5_android_bootlogo_tool.zip
$ cd m5_android_bootlogo_tool/
$ cp -a logo_img_files logo //logo_img_files is the origin bootlogo resource in android source and copy from <android-source-dir>/devices/amlogic/bananapi_m5/log_img_files
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_X3.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_X3.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m5_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the download usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m5:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m5_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
5699 bytes read in 3 ms (1.8 MiB/s)
## Executing script at 01b00000
...
reading Image.gz
9143358 bytes read in 510 ms (17.1 MiB/s)
reading meson64_bananapi_m5.dtb
70850 bytes read in 8 ms (8.4 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/i2c0.dtbo
223 bytes read in 6 ms (36.1 KiB/s)
reading overlays/spi0.dtbo
516 bytes read in 6 ms (84 KiB/s)
reading overlays/uart1.dtbo
225 bytes read in 5 ms (43.9 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A extreme situation is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Wifi/BT support===

:1. Android test and support.
rtl8723bu wifi/bt(usb)
rtl8188eu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]
rtl8814au wifi(usb), please get the [https://github.com/aircrack-ng/rtl8814au aircrack-ng] driver and install.

:'''How to enable Android Wifi/BT'''

:USB type: Plug-in the usb dongle to usb host port and reboot the system, After bootup, you can enable or disable wifi and bluetooth in Settings app.
:SDIO/UART type: Connect the hardware module to 40pin header correctly and [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Android_DTB_overlay configure the Android DTB overlay] to enable it.

:'''Note''': Android is not support that ethernet and wifi are both connected at the same time, Ethernet have a higher prioprity than wifi, it means wifi can't connect network if ethernet already connected, and wifi will drop connection if ethernet cable plugin.

:2. Linux test and support.
rtl8188eu wifi(usb)
rtl8192eu wifi(usb)
rtl8723bu wifi/bt(usb)
rtl8811au wifi(usb)
rtl8812au wifi(usb)
rtl8812bu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]

:'''How to enable Linux Wifi'''

:Wifi module drivers are already prebuild in the release images.

:USB type: Plug-in the usb dongle to usb host port and driver will be loaded automatically.
:SDIO/UART type:
::1). Connect the hardware module to 40pin header correctly.
::2). Configure the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#DTB_overlay dtb overlay]
# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "wifi_bt_rtl8822cs"
::3). Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:'''How to enable Linux Bluetooth'''

::1). Please download [https://github.com/Dangku/m5-rtk-linux-bt-driver rtk-linux-bt-driver] source code, build and install usb or uart rtk linux bluetooth drivers/firmwares to your image.
::2). For USB type, plug-in the usb dongle to usb host port and driver will be loaded automatically.
::3). For UART type, Configure the dtb overlay as the same as wifi before install the bluetooth drivers/firmwares. hci_uart driver will be loaded when rtk-hciuart.service start.

===Linux Server Image Network Configuration===

:[https://netplan.io Netplan]

:'''Linux Wifi STA mode'''

:A sample wifi sta mode netplan configuration file, 01-wlan0-sta.yaml
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: true
access-points:
"bananapi":
password: "123456789"

:'''Linux Wifi AP mode'''

:1. Prepare the setup the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Wifi.2FBT_support wifi adater] correctly.

:2. Get the wifi adapter Band, Frequencies, Channel, HT Capability, VHT Capability or other properties
$ iw list

:3. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Network-Manager.

:Install NetworkManager because ap is only supported with NetworkManager renderer
$ sudo apt install network-manager

:A sample 2.4G wifi ap mode netplan configuration file, 01-wlan0-ap-2.4g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 2.4GHz
channel: 6
auth:
key-management: psk
password: "123456789"

:A sample 5G wifi ap mode netplan configuration file, 01-wlan0-ap-5g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 5GHz
channel: 36
auth:
key-management: psk
password: "123456789"

:4. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Hostapd.

:1). Create a netplan configuration file, 01-wlan0-ap-hostapd.yaml
network:
version: 2
renderer: networkd
ethernets:
wlan0:
dhcp4: no
addresses:
- 192.168.11.1/24

:2). Install hostapd
$ sudo apt install hostapd

:Create hostapd configuration file /etc/hostapd/hostapd.conf, for example
interface=wlan0
ssid=bananapi

driver=nl80211

auth_algs=1
wpa=2
wpa_passphrase=123456789
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

#bridge=br0
beacon_int=500
#SSID not hidden
ignore_broadcast_ssid=0

hw_mode=a
channel=36
max_num_sta=8

### IEEE 802.11n
ieee80211n=1
#require_vht=0
ht_capab=[HT20][HT40+][SHORT-GI-20][SHORT-GI-40][SHORT-GI-80][DSSS_CCK-40]

### IEEE 802.11ac
ieee80211ac=1
#require_vht=0
#vht_capab=[MAX-MPDU-3895][SHORT-GI-80][SU-BEAMFORMEE]
#vht_oper_chwidth=1
#vht_oper_centr_freq_seg0_idx=42

### WMM
wmm_enabled=1

:3). To support 80MHz channel width you need load driver with '''rtw_vht_enable=2''' option, Or you can create /etc/modprobe.d/8822cs.conf with content
options 88x2cs rtw_vht_enable=2

:4). Install and configure dhcp server service, use isc-dhcp-server for example

$ sudo apt install isc-dhcp-server

:Configure dhcp server interface in /etc/default/isc-dhcp-server
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="wlan0"

:Configure dhcp subnet and dns in /etc/dhcp/dhcpd.conf
...
option domain-name "example.org";
option domain-name-servers 8.8.8.8, 114.114.114.114;
...
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
subnet 192.168.11.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.11.1 192.168.11.100;
option broadcast-address 192.168.11.255;
option routers 192.168.11.1;
}

:5). Start Service
$ sudo hostapd /etc/hostapd/hostapd.conf -B
$ sudo systemctl restart isc-dhcp-server

:6). Routing configuration.
sysctl net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -s 192.168.11.0/24 -o eth0 -j MASQUERADE

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions

Getting Started with M5/M2Pro

2023-01-31T01:10:12Z

Czj: /* Install Image to EMMC */

=Introduction=
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]]]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_1.JPG|thumb|Amlogic S905X3 Processor]]
[[File:Banana_Pi_BPI-M5_2.jpg|thumb|Amlogic S905X3 Processor]]

Banana Pi M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port, IR Reciver, Audio Jack, 1 HDMI Out and USB type-c power supply.

Banana Pi M2Pro is the same SOC with M5, but different board layout. 2GB LPDDR4 and 16G eMMC flash, 2 USB 3.0 port,1GbE LAN port, rtl8821cu usb wifi/bt onboard, IR Reciver, 1 HDMI Out, 1 MicroUSB port, DC power supply.

=specifications=

*SoC – Amlogic S905X3 quad-core Cortex-A55 processor @ up to 2.0 GHz with
*Mali-G31 MP2 GPU @ 650Mhz
*System Memory – 4GB LPDDR4
*Storage – 16GB eMMC flash (option up to 64GB), MicroSD slot up to 2TB
*Video Output – HDMI 2.1 up to 4Kp60 with HDR, CEC, EDID
*Audio – 3.5mm audio jack, digital HDMI audio
*Connectivity – Gigabit Ethernet
*USB – 4x USB 3.0 ports via VL817 hub controller, 1x USB-C port (for power only?)
*Expansion – 40-pin Raspberry Pi header with 28x GPIO, UART, I2C, SPI, PWM, and power signal (+5V, +3.3V, GND).
*Debugging – 3-pin debug header
*Misc – Reset, Power, and U-boot button; power and activity LED’s; IR receiver
*Power Supply – 5V @3A via USB Type-C port
*Dimensions – 92x60mm (Not the same as Raspberry Pi PCB size, but they probably included the connectors during measurement)
*Weight – 48grams

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug. M2pro is used Micro-usb port for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].
:4. In Android SDcard is mmc0, emmc is mmc1, but in Linux SDcard is mmc1, emmc is mmc0.

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via USB type-c on M5 and Micro-usb on M2pro, only support windows.
:2. Download the latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2 android image], and confirm that the md5 checksum is correct.
:3. M5 and M2pro are compatiable with same android image.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m5_android_install_1.png]]

:2. M5/M2pro board disconnect power, press and hold SW4 button beside 40pin header, plugin type-c usb cable(microUSB on m2pro) to PC

:[[File:m5_android_install_2.png]]

:3. Click the Start button and wait for upgrade complete.

:[[File:m5_android_install_3.png]]

:4. After Burning successfull, Unplug the usb and connect to power supply adaptor to startup.

:[[File:m5_android_install_4.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ git clone https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi M5/M2Pro DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M5/M2pro DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c2|| enable i2c 2
|-
| 3|| i2c3|| enable i2c 3
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m5:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m5:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m5:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m5_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/amlogic/bananapi_m5/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c2 i2c3 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/amlogic/bananapi_m5/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm/boot/dts/amlogic/overlay/bananapi_m5/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===IR Remote Control Custom===
:Before starting this work, some android basic concepts and knowledge need to be known.

:*Linux kernel input key event.
:*Android keycode.
:*Linux keycode map to android keycode.
:*Android Adb function work on your PC

:1. pull the remote files from device
# adb pull /vendor/etc/remote.cfg
# adb pull /vendor/etc/remote.tab

:2. modify remote.cfg to enable remote debug message
:[[File:remotecfg.png]]

:push remote.cfg back

# adb root
# adb remount
# adb push remote.cfg /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.cfg
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000

:3. Get the remote keycode
:Press your remote key one by one and then print the dmesg to get the remote custom_code and each remote key code.

# adb shell dmesg | grep framecode=
:[[File:keycode.png]]

:custom_code = 0xfe01
:keycode = 0x00, 0x01, 0x09, 0x02, 0x0a, 0x05, 0x04 0x06, 0x03, 0x0b, 0x40, 0x48, 0x44

:4. Modify remote.tab to map the scancode to android keycode
:[[File:remotetab.png]]

:push remote.tab and test each key whether works

# adb root
# adb remount
# adb push remote.tab1 /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.tab
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -t /vendor/etc/remote.tab -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000
tabdir = /vendor/etc/remote.tab
custom_name = nec-test
fn_key_scancode = 0xffff
cursor_left_scancode = 0xffff
cursor_right_scancode = 0xffff
cursor_up_scancode = 0xffff
cursor_down_scancode = 0xffff
cursor_ok_scancode = 0xffff
custom_code = 0xfe01
release_delay = 80
map_size = 13
key[0] = 0x74
key[1] = 0x1008b
key[2] = 0x90066
key[3] = 0x20069
key[4] = 0xa006a
key[5] = 0x50067
key[6] = 0x4006c
key[7] = 0x6001c
key[8] = 0x30072
key[9] = 0xb0073
key[10] = 0x40009e
key[11] = 0x4800a4
key[12] = 0x440071

:5. Reboot the board

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. M5 and M2pro are compatiable with same Linux image.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install image with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_BPI-M5/M2Pro#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. There are two ways to install the linux image to board
3.1. Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

3.2. Install the linux image in udisk with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/mmcblk0

:4. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M5-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M5-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/odroidg12-v2015.01-c4-m5 u-boot] the [https://github.com/Dangku/amlogic-linux/tree/odroidg12-4.9.y-c4-m5 kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M5-bsp BPI-M5-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/firmware/overlays/
custom_ir.dtbo pwm_b-backlight.dtbo spi0.dtbo
ds3231.dtbo pwm_c-beeper.dtbo uart1_cts_rts.dtbo
hifi_pcm5102a.dtbo pwm_cd-c.dtbo uart1.dtbo
hifi_pcm5122.dtbo pwm_cd.dtbo uart2.dtbo
i2c0.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_ef-f.dtbo waveshare_tft35c_lcd.dtbo
pwm_ab.dtbo sdio.dtbo waveshare_tft35c_rtp.dtbo

:2. Update the overlays env in vfat /boot/firmware/boot.ini to enable what you want. Default i2c0, spi0 and uart1 enabled.

# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "i2c0 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===WiringPi===
: Note: This WiringPi only support set 40pin gpio to output, input or software pwm, for io functions as i2c, spi, pwm..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/BPI-SINOVOIP/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m5_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/BPI-SINOVOIP/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-bpi, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:52pi-bpi, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled-bpi, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip-bpi, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Boot Linux from USB drive===

:S905x3 is not support usb boot in soc rom, so the only way for booting linux from usb drive is create a bootable sdcard or emmc with bootloader flashed, then load boot and rootfs from usb drive. After bootup, everything will run from usb drive.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash the M5/M2Pro Linux image to sdcard or emmc] for bootable and also flash it to the usb drive for loading boot and rootfs.
:2. Bootup the M5/M2pro board with [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Boot_Sequence sdcard or emmc], copy /boot/boot.ini to /boot/boot.ini.org so that bootloader load boot.ini fail and then try to load it from usb drive boot partition.
:3. Reboot the system, bootscript and rootfs will load from usb drive.
:[[File:m5_boot_from_usb.png]]

:4. Test performance
:You can verify the performance of your usb drive on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and usb drive
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Usb Drive Test Result
|-
| HDParm || Disk Read || 67.91 MB/s || 156.64 MB/s || 253.40 MB/s
|-
| HDParm || Cached Disk Read || 57.39 MB/s || 126.53 MB/s || 253.52 MB/s
|-
| DD || Disk Write || 13.0 MB/s || 48.8 MB/s || 149 MB/s
|-
| FIO || 4k random read || 2456 IOPS (9826 KB/s) || 9701 IOPS (38806 KB/s) || 5474 IOPS (21897 KB/s)
|-
| FIO || 4k random write || 938 IOPS (3753 KB/s) || 12888 IOPS (51554 KB/s) || 6980 IOPS (27920 KB/s)
|-
| IOZone || 4k read || 10615 KB/s || 29568 KB/s || 23770 KB/s
|-
| IOZone || 4k write || 4276 KB/s || 33585 KB/s || 18598 KB/s
|-
| IOZone || 4k random read || 8661 KB/s || 29637 KB/s || 19982 KB/s
|-
| IOZone || 4k random write || 4795 KB/s || 38177 KB/s || 22134 KB/s
|-
| || || Score: 1300 || Score: 7811 || Score: 5879
|}

==Other Development==

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp
:3. copy the target file to BPI-BOOT partition of linux image
$ cp boot-logo.bmp.gz /media/xxx/BPI-BOOT/

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 24bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Flogo_create_tools%2Fm5_android_bootlogo_tool.zip m5_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m5_android_bootlogo_tool.zip
$ cd m5_android_bootlogo_tool/
$ cp -a logo_img_files logo //logo_img_files is the origin bootlogo resource in android source and copy from <android-source-dir>/devices/amlogic/bananapi_m5/log_img_files
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_X3.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_X3.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m5_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the download usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m5:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m5_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
5699 bytes read in 3 ms (1.8 MiB/s)
## Executing script at 01b00000
...
reading Image.gz
9143358 bytes read in 510 ms (17.1 MiB/s)
reading meson64_bananapi_m5.dtb
70850 bytes read in 8 ms (8.4 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/i2c0.dtbo
223 bytes read in 6 ms (36.1 KiB/s)
reading overlays/spi0.dtbo
516 bytes read in 6 ms (84 KiB/s)
reading overlays/uart1.dtbo
225 bytes read in 5 ms (43.9 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A extreme situation is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Wifi/BT support===

:1. Android test and support.
rtl8723bu wifi/bt(usb)
rtl8188eu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]
rtl8814au wifi(usb), please get the [https://github.com/aircrack-ng/rtl8814au aircrack-ng] driver and install.

:'''How to enable Android Wifi/BT'''

:USB type: Plug-in the usb dongle to usb host port and reboot the system, After bootup, you can enable or disable wifi and bluetooth in Settings app.
:SDIO/UART type: Connect the hardware module to 40pin header correctly and [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Android_DTB_overlay configure the Android DTB overlay] to enable it.

:'''Note''': Android is not support that ethernet and wifi are both connected at the same time, Ethernet have a higher prioprity than wifi, it means wifi can't connect network if ethernet already connected, and wifi will drop connection if ethernet cable plugin.

:2. Linux test and support.
rtl8188eu wifi(usb)
rtl8192eu wifi(usb)
rtl8723bu wifi/bt(usb)
rtl8811au wifi(usb)
rtl8812au wifi(usb)
rtl8812bu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]

:'''How to enable Linux Wifi'''

:Wifi module drivers are already prebuild in the release images.

:USB type: Plug-in the usb dongle to usb host port and driver will be loaded automatically.
:SDIO/UART type:
::1). Connect the hardware module to 40pin header correctly.
::2). Configure the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#DTB_overlay dtb overlay]
# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "wifi_bt_rtl8822cs"
::3). Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:'''How to enable Linux Bluetooth'''

::1). Please download [https://github.com/Dangku/m5-rtk-linux-bt-driver rtk-linux-bt-driver] source code, build and install usb or uart rtk linux bluetooth drivers/firmwares to your image.
::2). For USB type, plug-in the usb dongle to usb host port and driver will be loaded automatically.
::3). For UART type, Configure the dtb overlay as the same as wifi before install the bluetooth drivers/firmwares. hci_uart driver will be loaded when rtk-hciuart.service start.

===Linux Server Image Network Configuration===

:[https://netplan.io Netplan]

:'''Linux Wifi STA mode'''

:A sample wifi sta mode netplan configuration file, 01-wlan0-sta.yaml
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: true
access-points:
"bananapi":
password: "123456789"

:'''Linux Wifi AP mode'''

:1. Prepare the setup the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Wifi.2FBT_support wifi adater] correctly.

:2. Get the wifi adapter Band, Frequencies, Channel, HT Capability, VHT Capability or other properties
$ iw list

:3. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Network-Manager.

:Install NetworkManager because ap is only supported with NetworkManager renderer
$ sudo apt install network-manager

:A sample 2.4G wifi ap mode netplan configuration file, 01-wlan0-ap-2.4g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 2.4GHz
channel: 6
auth:
key-management: psk
password: "123456789"

:A sample 5G wifi ap mode netplan configuration file, 01-wlan0-ap-5g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 5GHz
channel: 36
auth:
key-management: psk
password: "123456789"

:4. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Hostapd.

:1). Create a netplan configuration file, 01-wlan0-ap-hostapd.yaml
network:
version: 2
renderer: networkd
ethernets:
wlan0:
dhcp4: no
addresses:
- 192.168.11.1/24

:2). Install hostapd
$ sudo apt install hostapd

:Create hostapd configuration file /etc/hostapd/hostapd.conf, for example
interface=wlan0
ssid=bananapi

driver=nl80211

auth_algs=1
wpa=2
wpa_passphrase=123456789
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

#bridge=br0
beacon_int=500
#SSID not hidden
ignore_broadcast_ssid=0

hw_mode=a
channel=36
max_num_sta=8

### IEEE 802.11n
ieee80211n=1
#require_vht=0
ht_capab=[HT20][HT40+][SHORT-GI-20][SHORT-GI-40][SHORT-GI-80][DSSS_CCK-40]

### IEEE 802.11ac
ieee80211ac=1
#require_vht=0
#vht_capab=[MAX-MPDU-3895][SHORT-GI-80][SU-BEAMFORMEE]
#vht_oper_chwidth=1
#vht_oper_centr_freq_seg0_idx=42

### WMM
wmm_enabled=1

:3). To support 80MHz channel width you need load driver with '''rtw_vht_enable=2''' option, Or you can create /etc/modprobe.d/8822cs.conf with content
options 88x2cs rtw_vht_enable=2

:4). Install and configure dhcp server service, use isc-dhcp-server for example

$ sudo apt install isc-dhcp-server

:Configure dhcp server interface in /etc/default/isc-dhcp-server
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="wlan0"

:Configure dhcp subnet and dns in /etc/dhcp/dhcpd.conf
...
option domain-name "example.org";
option domain-name-servers 8.8.8.8, 114.114.114.114;
...
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
subnet 192.168.11.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.11.1 192.168.11.100;
option broadcast-address 192.168.11.255;
option routers 192.168.11.1;
}

:5). Start Service
$ sudo hostapd /etc/hostapd/hostapd.conf -B
$ sudo systemctl restart isc-dhcp-server

:6). Routing configuration.
sysctl net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -s 192.168.11.0/24 -o eth0 -j MASQUERADE

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions

Getting Started with M5/M2Pro

2023-01-31T01:07:22Z

Czj: /* WiringPi2-Python */

=Introduction=
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]]]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_1.JPG|thumb|Amlogic S905X3 Processor]]
[[File:Banana_Pi_BPI-M5_2.jpg|thumb|Amlogic S905X3 Processor]]

Banana Pi M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port, IR Reciver, Audio Jack, 1 HDMI Out and USB type-c power supply.

Banana Pi M2Pro is the same SOC with M5, but different board layout. 2GB LPDDR4 and 16G eMMC flash, 2 USB 3.0 port,1GbE LAN port, rtl8821cu usb wifi/bt onboard, IR Reciver, 1 HDMI Out, 1 MicroUSB port, DC power supply.

=specifications=

*SoC – Amlogic S905X3 quad-core Cortex-A55 processor @ up to 2.0 GHz with
*Mali-G31 MP2 GPU @ 650Mhz
*System Memory – 4GB LPDDR4
*Storage – 16GB eMMC flash (option up to 64GB), MicroSD slot up to 2TB
*Video Output – HDMI 2.1 up to 4Kp60 with HDR, CEC, EDID
*Audio – 3.5mm audio jack, digital HDMI audio
*Connectivity – Gigabit Ethernet
*USB – 4x USB 3.0 ports via VL817 hub controller, 1x USB-C port (for power only?)
*Expansion – 40-pin Raspberry Pi header with 28x GPIO, UART, I2C, SPI, PWM, and power signal (+5V, +3.3V, GND).
*Debugging – 3-pin debug header
*Misc – Reset, Power, and U-boot button; power and activity LED’s; IR receiver
*Power Supply – 5V @3A via USB Type-C port
*Dimensions – 92x60mm (Not the same as Raspberry Pi PCB size, but they probably included the connectors during measurement)
*Weight – 48grams

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug. M2pro is used Micro-usb port for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].
:4. In Android SDcard is mmc0, emmc is mmc1, but in Linux SDcard is mmc1, emmc is mmc0.

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via USB type-c on M5 and Micro-usb on M2pro, only support windows.
:2. Download the latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2 android image], and confirm that the md5 checksum is correct.
:3. M5 and M2pro are compatiable with same android image.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m5_android_install_1.png]]

:2. M5/M2pro board disconnect power, press and hold SW4 button beside 40pin header, plugin type-c usb cable(microUSB on m2pro) to PC

:[[File:m5_android_install_2.png]]

:3. Click the Start button and wait for upgrade complete.

:[[File:m5_android_install_3.png]]

:4. After Burning successfull, Unplug the usb and connect to power supply adaptor to startup.

:[[File:m5_android_install_4.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ git clone https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi M5/M2Pro DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M5/M2pro DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c2|| enable i2c 2
|-
| 3|| i2c3|| enable i2c 3
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m5:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m5:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m5:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m5_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/amlogic/bananapi_m5/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c2 i2c3 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/amlogic/bananapi_m5/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm/boot/dts/amlogic/overlay/bananapi_m5/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===IR Remote Control Custom===
:Before starting this work, some android basic concepts and knowledge need to be known.

:*Linux kernel input key event.
:*Android keycode.
:*Linux keycode map to android keycode.
:*Android Adb function work on your PC

:1. pull the remote files from device
# adb pull /vendor/etc/remote.cfg
# adb pull /vendor/etc/remote.tab

:2. modify remote.cfg to enable remote debug message
:[[File:remotecfg.png]]

:push remote.cfg back

# adb root
# adb remount
# adb push remote.cfg /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.cfg
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000

:3. Get the remote keycode
:Press your remote key one by one and then print the dmesg to get the remote custom_code and each remote key code.

# adb shell dmesg | grep framecode=
:[[File:keycode.png]]

:custom_code = 0xfe01
:keycode = 0x00, 0x01, 0x09, 0x02, 0x0a, 0x05, 0x04 0x06, 0x03, 0x0b, 0x40, 0x48, 0x44

:4. Modify remote.tab to map the scancode to android keycode
:[[File:remotetab.png]]

:push remote.tab and test each key whether works

# adb root
# adb remount
# adb push remote.tab1 /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.tab
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -t /vendor/etc/remote.tab -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000
tabdir = /vendor/etc/remote.tab
custom_name = nec-test
fn_key_scancode = 0xffff
cursor_left_scancode = 0xffff
cursor_right_scancode = 0xffff
cursor_up_scancode = 0xffff
cursor_down_scancode = 0xffff
cursor_ok_scancode = 0xffff
custom_code = 0xfe01
release_delay = 80
map_size = 13
key[0] = 0x74
key[1] = 0x1008b
key[2] = 0x90066
key[3] = 0x20069
key[4] = 0xa006a
key[5] = 0x50067
key[6] = 0x4006c
key[7] = 0x6001c
key[8] = 0x30072
key[9] = 0xb0073
key[10] = 0x40009e
key[11] = 0x4800a4
key[12] = 0x440071

:5. Reboot the board

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. M5 and M2pro are compatiable with same Linux image.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install image with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_BPI-M5/M2Pro#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

:4. Install the linux image in udisk with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/mmcblk0

:5. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M5-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M5-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/odroidg12-v2015.01-c4-m5 u-boot] the [https://github.com/Dangku/amlogic-linux/tree/odroidg12-4.9.y-c4-m5 kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M5-bsp BPI-M5-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/firmware/overlays/
custom_ir.dtbo pwm_b-backlight.dtbo spi0.dtbo
ds3231.dtbo pwm_c-beeper.dtbo uart1_cts_rts.dtbo
hifi_pcm5102a.dtbo pwm_cd-c.dtbo uart1.dtbo
hifi_pcm5122.dtbo pwm_cd.dtbo uart2.dtbo
i2c0.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_ef-f.dtbo waveshare_tft35c_lcd.dtbo
pwm_ab.dtbo sdio.dtbo waveshare_tft35c_rtp.dtbo

:2. Update the overlays env in vfat /boot/firmware/boot.ini to enable what you want. Default i2c0, spi0 and uart1 enabled.

# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "i2c0 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===WiringPi===
: Note: This WiringPi only support set 40pin gpio to output, input or software pwm, for io functions as i2c, spi, pwm..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/BPI-SINOVOIP/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m5_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/BPI-SINOVOIP/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-bpi, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:52pi-bpi, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled-bpi, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip-bpi, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Boot Linux from USB drive===

:S905x3 is not support usb boot in soc rom, so the only way for booting linux from usb drive is create a bootable sdcard or emmc with bootloader flashed, then load boot and rootfs from usb drive. After bootup, everything will run from usb drive.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash the M5/M2Pro Linux image to sdcard or emmc] for bootable and also flash it to the usb drive for loading boot and rootfs.
:2. Bootup the M5/M2pro board with [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Boot_Sequence sdcard or emmc], copy /boot/boot.ini to /boot/boot.ini.org so that bootloader load boot.ini fail and then try to load it from usb drive boot partition.
:3. Reboot the system, bootscript and rootfs will load from usb drive.
:[[File:m5_boot_from_usb.png]]

:4. Test performance
:You can verify the performance of your usb drive on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and usb drive
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Usb Drive Test Result
|-
| HDParm || Disk Read || 67.91 MB/s || 156.64 MB/s || 253.40 MB/s
|-
| HDParm || Cached Disk Read || 57.39 MB/s || 126.53 MB/s || 253.52 MB/s
|-
| DD || Disk Write || 13.0 MB/s || 48.8 MB/s || 149 MB/s
|-
| FIO || 4k random read || 2456 IOPS (9826 KB/s) || 9701 IOPS (38806 KB/s) || 5474 IOPS (21897 KB/s)
|-
| FIO || 4k random write || 938 IOPS (3753 KB/s) || 12888 IOPS (51554 KB/s) || 6980 IOPS (27920 KB/s)
|-
| IOZone || 4k read || 10615 KB/s || 29568 KB/s || 23770 KB/s
|-
| IOZone || 4k write || 4276 KB/s || 33585 KB/s || 18598 KB/s
|-
| IOZone || 4k random read || 8661 KB/s || 29637 KB/s || 19982 KB/s
|-
| IOZone || 4k random write || 4795 KB/s || 38177 KB/s || 22134 KB/s
|-
| || || Score: 1300 || Score: 7811 || Score: 5879
|}

==Other Development==

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp
:3. copy the target file to BPI-BOOT partition of linux image
$ cp boot-logo.bmp.gz /media/xxx/BPI-BOOT/

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 24bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Flogo_create_tools%2Fm5_android_bootlogo_tool.zip m5_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m5_android_bootlogo_tool.zip
$ cd m5_android_bootlogo_tool/
$ cp -a logo_img_files logo //logo_img_files is the origin bootlogo resource in android source and copy from <android-source-dir>/devices/amlogic/bananapi_m5/log_img_files
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_X3.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_X3.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m5_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the download usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m5:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m5_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
5699 bytes read in 3 ms (1.8 MiB/s)
## Executing script at 01b00000
...
reading Image.gz
9143358 bytes read in 510 ms (17.1 MiB/s)
reading meson64_bananapi_m5.dtb
70850 bytes read in 8 ms (8.4 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/i2c0.dtbo
223 bytes read in 6 ms (36.1 KiB/s)
reading overlays/spi0.dtbo
516 bytes read in 6 ms (84 KiB/s)
reading overlays/uart1.dtbo
225 bytes read in 5 ms (43.9 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A extreme situation is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Wifi/BT support===

:1. Android test and support.
rtl8723bu wifi/bt(usb)
rtl8188eu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]
rtl8814au wifi(usb), please get the [https://github.com/aircrack-ng/rtl8814au aircrack-ng] driver and install.

:'''How to enable Android Wifi/BT'''

:USB type: Plug-in the usb dongle to usb host port and reboot the system, After bootup, you can enable or disable wifi and bluetooth in Settings app.
:SDIO/UART type: Connect the hardware module to 40pin header correctly and [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Android_DTB_overlay configure the Android DTB overlay] to enable it.

:'''Note''': Android is not support that ethernet and wifi are both connected at the same time, Ethernet have a higher prioprity than wifi, it means wifi can't connect network if ethernet already connected, and wifi will drop connection if ethernet cable plugin.

:2. Linux test and support.
rtl8188eu wifi(usb)
rtl8192eu wifi(usb)
rtl8723bu wifi/bt(usb)
rtl8811au wifi(usb)
rtl8812au wifi(usb)
rtl8812bu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]

:'''How to enable Linux Wifi'''

:Wifi module drivers are already prebuild in the release images.

:USB type: Plug-in the usb dongle to usb host port and driver will be loaded automatically.
:SDIO/UART type:
::1). Connect the hardware module to 40pin header correctly.
::2). Configure the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#DTB_overlay dtb overlay]
# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "wifi_bt_rtl8822cs"
::3). Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:'''How to enable Linux Bluetooth'''

::1). Please download [https://github.com/Dangku/m5-rtk-linux-bt-driver rtk-linux-bt-driver] source code, build and install usb or uart rtk linux bluetooth drivers/firmwares to your image.
::2). For USB type, plug-in the usb dongle to usb host port and driver will be loaded automatically.
::3). For UART type, Configure the dtb overlay as the same as wifi before install the bluetooth drivers/firmwares. hci_uart driver will be loaded when rtk-hciuart.service start.

===Linux Server Image Network Configuration===

:[https://netplan.io Netplan]

:'''Linux Wifi STA mode'''

:A sample wifi sta mode netplan configuration file, 01-wlan0-sta.yaml
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: true
access-points:
"bananapi":
password: "123456789"

:'''Linux Wifi AP mode'''

:1. Prepare the setup the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Wifi.2FBT_support wifi adater] correctly.

:2. Get the wifi adapter Band, Frequencies, Channel, HT Capability, VHT Capability or other properties
$ iw list

:3. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Network-Manager.

:Install NetworkManager because ap is only supported with NetworkManager renderer
$ sudo apt install network-manager

:A sample 2.4G wifi ap mode netplan configuration file, 01-wlan0-ap-2.4g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 2.4GHz
channel: 6
auth:
key-management: psk
password: "123456789"

:A sample 5G wifi ap mode netplan configuration file, 01-wlan0-ap-5g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 5GHz
channel: 36
auth:
key-management: psk
password: "123456789"

:4. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Hostapd.

:1). Create a netplan configuration file, 01-wlan0-ap-hostapd.yaml
network:
version: 2
renderer: networkd
ethernets:
wlan0:
dhcp4: no
addresses:
- 192.168.11.1/24

:2). Install hostapd
$ sudo apt install hostapd

:Create hostapd configuration file /etc/hostapd/hostapd.conf, for example
interface=wlan0
ssid=bananapi

driver=nl80211

auth_algs=1
wpa=2
wpa_passphrase=123456789
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

#bridge=br0
beacon_int=500
#SSID not hidden
ignore_broadcast_ssid=0

hw_mode=a
channel=36
max_num_sta=8

### IEEE 802.11n
ieee80211n=1
#require_vht=0
ht_capab=[HT20][HT40+][SHORT-GI-20][SHORT-GI-40][SHORT-GI-80][DSSS_CCK-40]

### IEEE 802.11ac
ieee80211ac=1
#require_vht=0
#vht_capab=[MAX-MPDU-3895][SHORT-GI-80][SU-BEAMFORMEE]
#vht_oper_chwidth=1
#vht_oper_centr_freq_seg0_idx=42

### WMM
wmm_enabled=1

:3). To support 80MHz channel width you need load driver with '''rtw_vht_enable=2''' option, Or you can create /etc/modprobe.d/8822cs.conf with content
options 88x2cs rtw_vht_enable=2

:4). Install and configure dhcp server service, use isc-dhcp-server for example

$ sudo apt install isc-dhcp-server

:Configure dhcp server interface in /etc/default/isc-dhcp-server
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="wlan0"

:Configure dhcp subnet and dns in /etc/dhcp/dhcpd.conf
...
option domain-name "example.org";
option domain-name-servers 8.8.8.8, 114.114.114.114;
...
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
subnet 192.168.11.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.11.1 192.168.11.100;
option broadcast-address 192.168.11.255;
option routers 192.168.11.1;
}

:5). Start Service
$ sudo hostapd /etc/hostapd/hostapd.conf -B
$ sudo systemctl restart isc-dhcp-server

:6). Routing configuration.
sysctl net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -s 192.168.11.0/24 -o eth0 -j MASQUERADE

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions

Getting Started with M5/M2Pro

2023-01-31T01:07:15Z

Czj: /* RPi.GPIO */

=Introduction=
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]]]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_1.JPG|thumb|Amlogic S905X3 Processor]]
[[File:Banana_Pi_BPI-M5_2.jpg|thumb|Amlogic S905X3 Processor]]

Banana Pi M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port, IR Reciver, Audio Jack, 1 HDMI Out and USB type-c power supply.

Banana Pi M2Pro is the same SOC with M5, but different board layout. 2GB LPDDR4 and 16G eMMC flash, 2 USB 3.0 port,1GbE LAN port, rtl8821cu usb wifi/bt onboard, IR Reciver, 1 HDMI Out, 1 MicroUSB port, DC power supply.

=specifications=

*SoC – Amlogic S905X3 quad-core Cortex-A55 processor @ up to 2.0 GHz with
*Mali-G31 MP2 GPU @ 650Mhz
*System Memory – 4GB LPDDR4
*Storage – 16GB eMMC flash (option up to 64GB), MicroSD slot up to 2TB
*Video Output – HDMI 2.1 up to 4Kp60 with HDR, CEC, EDID
*Audio – 3.5mm audio jack, digital HDMI audio
*Connectivity – Gigabit Ethernet
*USB – 4x USB 3.0 ports via VL817 hub controller, 1x USB-C port (for power only?)
*Expansion – 40-pin Raspberry Pi header with 28x GPIO, UART, I2C, SPI, PWM, and power signal (+5V, +3.3V, GND).
*Debugging – 3-pin debug header
*Misc – Reset, Power, and U-boot button; power and activity LED’s; IR receiver
*Power Supply – 5V @3A via USB Type-C port
*Dimensions – 92x60mm (Not the same as Raspberry Pi PCB size, but they probably included the connectors during measurement)
*Weight – 48grams

=development=

==Prepare==
:1. Prepare a usb-serial cable, a 5V/3A adaptor type-c power supply. The serial cable is used for console debug and type-c cable is used for android image download and ADB debug. M2pro is used Micro-usb port for android image download and ADB debug.
:2. Prepare a SDcard at least 8GB for linux development, android only support emmc boot.
:3. The SOC rom first boot media is emmc, so board can't bootup from SDcard if the emmc is bootable with any image flashed, more info please refer to board [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence].
:4. In Android SDcard is mmc0, emmc is mmc1, but in Linux SDcard is mmc1, emmc is mmc0.

==Android==
===Prepare===

:1. Download and install the [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Fimage_download_tools%2Faml_usb_burning_tool_V2_setup_v2.2.3.3.zip AML Usb Burning Tool] for android image download via USB type-c on M5 and Micro-usb on M2pro, only support windows.
:2. Download the latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2 android image], and confirm that the md5 checksum is correct.
:3. M5 and M2pro are compatiable with same android image.

===Install Image with Usb Burning Tool===

:1. Open USB_Burning_Tool.exe, select menu File->Import image, choose the android image file aml_upgrade_package.img.

:[[File:m5_android_install_1.png]]

:2. M5/M2pro board disconnect power, press and hold SW4 button beside 40pin header, plugin type-c usb cable(microUSB on m2pro) to PC

:[[File:m5_android_install_2.png]]

:3. Click the Start button and wait for upgrade complete.

:[[File:m5_android_install_3.png]]

:4. After Burning successfull, Unplug the usb and connect to power supply adaptor to startup.

:[[File:m5_android_install_4.png]]

:5. Click the Stop button to cancel the upgrade process and close the USB Buring Tool.

===Install Image with Aml Flash Tool===
:[https://github.com/Dangku/aml-flash-tool aml-flash-tool] is a linux platform opensource image flash util for Amlogic android.

$ ./flash-tool.sh --img=/path/to/aml_upgrade_package.img --parts=all --wipe --soc=g12a --reset=y

:[[File:m5_linux_flash.PNG]]

===Build Android Source Code===
:1. Get Android 9.0 source code

$ git clone https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9

:2. Build the Android 9.0 Source code

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-S905X3-Android9/blob/master/README.md README.md]

===Android DTB overlay===

:Bananapi M5/M2Pro DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M5/M2pro DTBO idx value table'''
|-
|idx value|| device tree overlay || description
|-
| 0|| android_p_overlay|| default dtbo, no use
|-
| 1|| wifi_bt_rtl8822cs|| enable bpi rtl8822cs wifi/bt module
|-
| 2|| i2c2|| enable i2c 2
|-
| 3|| i2c3|| enable i2c 3
|-
| 4|| sdio|| enable sdio
|-
| 5|| uart1|| enable 2 pins uart 1
|-
| 6|| uart1_cts_rts|| enable 4 pins uart 1
|-
| 7|| uart2|| enable 2 pins uart 2
|-
| 8|| hifi_pcm5122|| enable i2s [https://shumeipai.nxez.com/hifidac-hat-for-raspberry-pi pcm5122 HiFi DAC]
|}

:'''How to apply a new dtbo'''

:1. ADB command via sysfs

root@dangku-desktop:/tmp# adb root
restarting adbd as root
root@dangku-desktop:/tmp# adb remount
remount succeeded
root@dangku-desktop:/tmp# adb shell
bananapi_m5:/ # echo dtbo > /sys/class/unifykeys/name
bananapi_m5:/ # echo "1" > /sys/class/unifykeys/write
bananapi_m5:/ # reboot

:2. Uart console command via sysfs

console:/ $
console:/ $ su
console:/ # echo dtbo > /sys/class/unifykeys/name
[ 115.702781@0] unifykey: name_store() 1302, name dtbo, 4
[ 115.702856@0] unifykey: name_store() 1311
console:/ #
console:/ # echo "1" > /sys/class/unifykeys/write
[ 129.262659@0] unifykey: write_store() is a string
[ 129.262733@0] unifykey: dtbo, 1, 1
[ 129.265312@0] unifykey: amlkey_write 393
[ 129.292347@1] emmc_key_write:149, write ok
console:/ #
console:/ # reboot

:3. Settings App(To-Do)

:Check the bootup uart debug message and confirm which dtbo is loaded actually, here "1" means set idx=1 to apply wifi_bt_rtl8822cs dtbo.

load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb detected
find 2 dtbos
dtbos to be applied: 1
Apply dtbo 1

:Unifykeys is stored in a specific emmc part, "Normal erase" selected in USB_Burning_Tool will not erase this data for next update, you must select "Erase all" if you want the default dtbo idx to be applied after image download.

:[[File:m5_android_erase_all.png]]

:'''Build Android image with a specific DTBO default'''.

:1. Default build-in overlays are defined in device/amlogic/bananapi_m5/Kernel.mk, you can add a new overlay dtbo here.
DTBO_DEVICETREE := android_p_overlay wifi_bt_rtl8822cs i2c2 i2c3 sdio uart1 uart1_cts_rts uart2 hifi_pcm5122

:2. Default apply DTBO idx is defined in device/amlogic/bananapi_m5/BoardConfig.mk, you can change the idx value to set which overlay dtbo will be applied default.
BOARD_KERNEL_CMDLINE += androidboot.dtbo_idx=0

:3. DTS files are in common/arch/arm/boot/dts/amlogic/overlay/bananapi_m5/

:More info about android device tree overlays, please refer to [https://source.android.com/devices/architecture/dto google android offical site]

===Install OpenGapps===

:1. Download install package from [https://opengapps.org/ OpenGapps], Android release image is arm/android 9.0 variant.

[[File:opengapps.PNG]]

:2. Download [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fapps%2Fdevice_id_v1.3.2.apk device_id.apk].
:3. Copy the OpenGapp package to a udisk or sdcard root directory.
:4. Create a txt file named '''factory_update_param.aml''' in udisk or sdcard root directory with the following android recovery parameter content, and replace the file name with the actual downloaded package.
::udisk:
--wipe_cache
--update_package=/udisk/open_gapps-arm-9.0-pico-20210327.zip

::sdcard:
--wipe_cache
--update_package=/sdcard/open_gapps-arm-9.0-pico-20210327.zip

:5. Plugin the udisk or sdcard to the board and poweron.

:6.OpenGapps install and certify.
:<youtube>fXOKmWfpqF8</youtube>
:watch this video on [https://www.bilibili.com/video/BV13y4y1s77i/ bilibili]

===IR Remote Control Custom===
:Before starting this work, some android basic concepts and knowledge need to be known.

:*Linux kernel input key event.
:*Android keycode.
:*Linux keycode map to android keycode.
:*Android Adb function work on your PC

:1. pull the remote files from device
# adb pull /vendor/etc/remote.cfg
# adb pull /vendor/etc/remote.tab

:2. modify remote.cfg to enable remote debug message
:[[File:remotecfg.png]]

:push remote.cfg back

# adb root
# adb remount
# adb push remote.cfg /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.cfg
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000

:3. Get the remote keycode
:Press your remote key one by one and then print the dmesg to get the remote custom_code and each remote key code.

# adb shell dmesg | grep framecode=
:[[File:keycode.png]]

:custom_code = 0xfe01
:keycode = 0x00, 0x01, 0x09, 0x02, 0x0a, 0x05, 0x04 0x06, 0x03, 0x0b, 0x40, 0x48, 0x44

:4. Modify remote.tab to map the scancode to android keycode
:[[File:remotetab.png]]

:push remote.tab and test each key whether works

# adb root
# adb remount
# adb push remote.tab1 /vendor/etc/
# adb shell
m5_mbox:/ # chmod 644 /vendor/etc/remote.tab
m5_mbox:/ # remotecfg -c /vendor/etc/remote.cfg -t /vendor/etc/remote.tab -d
cfgdir = /vendor/etc/remote.cfg
work_mode = 1
repeat_enable = 0
debug_enable = 1
max_frame_time = 1000
tabdir = /vendor/etc/remote.tab
custom_name = nec-test
fn_key_scancode = 0xffff
cursor_left_scancode = 0xffff
cursor_right_scancode = 0xffff
cursor_up_scancode = 0xffff
cursor_down_scancode = 0xffff
cursor_ok_scancode = 0xffff
custom_code = 0xfe01
release_delay = 80
map_size = 13
key[0] = 0x74
key[1] = 0x1008b
key[2] = 0x90066
key[3] = 0x20069
key[4] = 0xa006a
key[5] = 0x50067
key[6] = 0x4006c
key[7] = 0x6001c
key[8] = 0x30072
key[9] = 0xb0073
key[10] = 0x40009e
key[11] = 0x4800a4
key[12] = 0x440071

:5. Reboot the board

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, but you should read the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Boot_Sequence boot sequence] at first.

:2. M5 and M2pro are compatiable with same Linux image.

:2. Make sure bootable EMMC is formatted if you want bootup from SDcard, more info refer to [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_EMMC_for_SDcard_Bootup Erase EMMC for SDcard Bootup]

:3. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:4. Install bpi-tools on your Linux PC(if [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash image] with other tools, ignore this step). If you can't access this URL or any other install problem, please go to [https://github.com/bpi-sinovoip/bpi-tools bpi-tools] source repo, download and install this tools manually.
$ apt-get install pv
$ curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash

:5. Download Linux latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux Linux Image], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

===Install Image to SDcard===
:1. Install Image with Etcher on Windows, Linux and MacOS.
::[https://balena.io/etcher Balena Etcher] is an opensource GUI flash tool by Balena, Flash OS images to SDcard or USB drive

:[[File:m2s_linux_flash.png]]

:2. Install Image with dd command on Linux, umount SDcard device /dev/sdX partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:3. Install image with bpi-tools on Linux, plug SDcard to Linux PC and run
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/sdX

===Install Image to EMMC===
:1. Prepare a [https://wiki.banana-pi.org/Getting_Started_with_BPI-M5/M2Pro#Install_Image_to_SDcard SDcard with Linux image] flashed and bootup board with this SDcard.

:2. Copy Linux image to udisk, plug the udisk to board and mount it.

:3. Install with dd command, umount mmcblk0p1 and mmcblk0p2 partition if mounted automatically. Actually bpi-copy is the same as this dd command.
$ sudo apt-get install pv unzip
$ sudo unzip -p xxx-bpi-m5-xxx.img.zip | pv | dd of=/dev/mmcblk0 bs=10M status=noxfer

:4. Install the linux image in udisk with bpi-tools command
$ sudo apt-get install pv unzip
$ sudo bpi-copy xxx-bpi-m5-xxx.img.zip /dev/mmcblk0

:5. After download complete, power off safely and eject the SDcard.

===Build Linux Source Code===
:1. Get the Linux bsp source code
$ git clone https://github.com/BPI-SINOVOIP/BPI-M5-bsp
:2. Build the bsp source code

::Please read the source code [https://github.com/BPI-SINOVOIP/BPI-M5-bsp/blob/master/README.md README.md]

:3. If you want build uboot and kernel separately, please download the [https://github.com/Dangku/amlogic-u-boot/tree/odroidg12-v2015.01-c4-m5 u-boot] the [https://github.com/Dangku/amlogic-linux/tree/odroidg12-4.9.y-c4-m5 kernel] only, get the toolchains, boot script and other configuration files from [https://github.com/BPI-SINOVOIP/BPI-M5-bsp BPI-M5-bsp]

===DTB overlay===
:1. DTB overlay is used for 40pin gpios multi-function configuration and install in vfat boot partition, you can check the mount point with mount command.
root@bananapi:~# ls /boot/firmware/overlays/
custom_ir.dtbo pwm_b-backlight.dtbo spi0.dtbo
ds3231.dtbo pwm_c-beeper.dtbo uart1_cts_rts.dtbo
hifi_pcm5102a.dtbo pwm_cd-c.dtbo uart1.dtbo
hifi_pcm5122.dtbo pwm_cd.dtbo uart2.dtbo
i2c0.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c1.dtbo pwm_ef-f.dtbo waveshare_tft35c_lcd.dtbo
pwm_ab.dtbo sdio.dtbo waveshare_tft35c_rtp.dtbo

:2. Update the overlays env in vfat /boot/firmware/boot.ini to enable what you want. Default i2c0, spi0 and uart1 enabled.

# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "i2c0 spi0 uart1"

:3. Must be restart the board for overlay dtb loaded.

===WiringPi===
: Note: This WiringPi only support set 40pin gpio to output, input or software pwm, for io functions as i2c, spi, pwm..., you must enable dtb overlay in boot.ini

:1. Build and install wiringPi
$ git clone https://github.com/BPI-SINOVOIP/amlogic-wiringPi
$ cd amlogic-wiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m5_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/BPI-SINOVOIP/amlogic-wiringPi/tree/master/examples amlogic-wiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-bpi, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:52pi-bpi, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled-bpi, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip-bpi, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install
$ sudo apt-get install build-essential python python-dev python-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO-Amlogic.git
$ cd RPi.GPIO-Amlogic
$ sudo python setup.py clean --all
$ sudo python setup.py build install

===WiringPi2-Python===

: Build and install
$ sudo apt-get Install python python-dev python-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi2-Python-Amlogic.git
$ cd WiringPi2-Python-Amlogic
$ sudo python setup.py install

===Boot Linux from USB drive===

:S905x3 is not support usb boot in soc rom, so the only way for booting linux from usb drive is create a bootable sdcard or emmc with bootloader flashed, then load boot and rootfs from usb drive. After bootup, everything will run from usb drive.

:1. The simple way is [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Install_Image_to_SDcard flash the M5/M2Pro Linux image to sdcard or emmc] for bootable and also flash it to the usb drive for loading boot and rootfs.
:2. Bootup the M5/M2pro board with [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Boot_Sequence sdcard or emmc], copy /boot/boot.ini to /boot/boot.ini.org so that bootloader load boot.ini fail and then try to load it from usb drive boot partition.
:3. Reboot the system, bootscript and rootfs will load from usb drive.
:[[File:m5_boot_from_usb.png]]

:4. Test performance
:You can verify the performance of your usb drive on Pi Benchmarks using the following command:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

:Test results for sd, emmc and usb drive
:{| class="wikitable"
|-
| Category || Test || Sdcard Test Result || Emmc Test Result || Usb Drive Test Result
|-
| HDParm || Disk Read || 67.91 MB/s || 156.64 MB/s || 253.40 MB/s
|-
| HDParm || Cached Disk Read || 57.39 MB/s || 126.53 MB/s || 253.52 MB/s
|-
| DD || Disk Write || 13.0 MB/s || 48.8 MB/s || 149 MB/s
|-
| FIO || 4k random read || 2456 IOPS (9826 KB/s) || 9701 IOPS (38806 KB/s) || 5474 IOPS (21897 KB/s)
|-
| FIO || 4k random write || 938 IOPS (3753 KB/s) || 12888 IOPS (51554 KB/s) || 6980 IOPS (27920 KB/s)
|-
| IOZone || 4k read || 10615 KB/s || 29568 KB/s || 23770 KB/s
|-
| IOZone || 4k write || 4276 KB/s || 33585 KB/s || 18598 KB/s
|-
| IOZone || 4k random read || 8661 KB/s || 29637 KB/s || 19982 KB/s
|-
| IOZone || 4k random write || 4795 KB/s || 38177 KB/s || 22134 KB/s
|-
| || || Score: 1300 || Score: 7811 || Score: 5879
|}

==Other Development==

===Custom Linux Boot Logo===
:Linux uboot limit boot logo fb size to 1080p60hz/1920x1080 default, so oversize resolution will not be supported by default image, but you can modify uboot source code to support it.

:1. Prepare a 24bit bmp file and named boot-logo.bmp
:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp
:3. copy the target file to BPI-BOOT partition of linux image
$ cp boot-logo.bmp.gz /media/xxx/BPI-BOOT/

===Custom Android Boot Logo===
:Android bootloader limit boot logo fb display size is 1080p60hz/1920x1080 default, and android kernel dtb partition table limit boot logo partition size to 16MB default .

:1. Prepare a 24bit bmp file and named boot-logo.bmp

:2. Compress the bmp file to boot-logo.bmp.gz
$ gzip boot-logo.bmp

:3. Download [https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FTools%2Flogo_create_tools%2Fm5_android_bootlogo_tool.zip m5_android_bootlogo_tool.zip]

:4. Extract this tool
$ unzip m5_android_bootlogo_tool.zip
$ cd m5_android_bootlogo_tool/
$ cp -a logo_img_files logo //logo_img_files is the origin bootlogo resource in android source and copy from <android-source-dir>/devices/amlogic/bananapi_m5/log_img_files
$ ls -l logo/
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup.bmp
-rwxr--r-- 1 dangku dangku 525054 Sep 25 16:54 bootup_X3.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_bar.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_error.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_fail.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_logo.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_success.bmp
-rwxr--r-- 1 dangku dangku 184 May 19 2020 upgrade_unfocus.bmp
-rwxr--r-- 1 dangku dangku 180072 May 19 2020 upgrade_upgrading.bmp

:5. Copy the boot-logo.bmp.gz
$ cp boot-logo.bmp.gz logo/bootup.bmp
$ cp boot-logo.bmp.gz logo/bootup_X3.bmp

:6. Create target logo.img with img pack tool, the binary and related libs of m5_android_bootlogo_tool are copy from <android-source-dir>/out/host/linux-x86
$ ./logo_img_packer -r logo logo.img

:7. Flash boot logo with fastboot
$ adb root
$ adb remount
$ adb reboot fastboot
:Wait few seconds and check whether fastboot connected
$ fastboot device
1234567890 fastboot
$ fastboot flashing unlock_critical
$ fastboot flashing unlock
$ fastboot flash logo logo.img
$ fastboot reboot

===Boot Sequence===

:[[File:m5_linux_boot_squence.png]]

:Check bootloader loaded from SDcard or EMMC at the beginning of the console debug messages

:1. Rom load bootloader from SDcard (Linux log example)
...

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
'''Load FIP HDR DDR from SD''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

...

:2. Rom load bootloader from EMMC(Android Log example)

...

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
board id: 1
'''Load FIP HDR DDR from eMMC''', src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000

...

===Erase EMMC for SDcard Bootup===
:There are four possible scenarios should be pay attention to, EMMC already flashed Android image, EMMC already flashed Linux image, boot process hangup in BL2 and EMMC empty.

:1. Bootable EMMC with Android image flashed

::a). Using usb burning tool, unplug the download usb cable while the download process at '''7% formatting'''

::[[File:m5_android_format.png]]

::b). Using Android Fastboot tool, make sure the adb/fastboot tools is work on your PC before doing this.

root@dangku-desktop:/tmp# '''adb root'''
adbd is already running as root
root@dangku-desktop:/tmp# '''adb remount'''
remount succeeded
root@dangku-desktop:/tmp# '''adb shell'''
bananapi_m5:/ # '''reboot fastboot'''
::Wait a few seconds for board reboot to fastboot mode
root@dangku-desktop:/tmp# '''fastboot devices'''
1234567890 fastboot
root@dangku-desktop:/tmp# '''fastboot flashing unlock_critical'''
...
OKAY [ 0.044s]
finished. total time: 0.044s
root@dangku-desktop:/tmp# '''fastboot flashing unlock'''
...
OKAY [ 0.047s]
finished. total time: 0.047s
root@dangku-desktop:/tmp# '''fastboot erase bootloader'''
erasing 'bootloader'...
OKAY [ 0.059s]
finished. total time: 0.059s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot0'''
erasing 'bootloader-boot0'...
OKAY [ 0.036s]
finished. total time: 0.036s
root@dangku-desktop:/tmp# '''fastboot erase bootloader-boot1'''
erasing 'bootloader-boot1'...
OKAY [ 0.035s]
finished. total time: 0.035s

::c). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5_v1#'''amlmmc erase 1'''
emmckey_is_protected(): protect
start = 0,end = 57343
start = 221184,end = 30535679
Erasing blocks 0 to 8192 @ boot0
start = 0,end = 8191
Erasing blocks 0 to 8192 @ boot1
start = 0,end = 8191
bananapi_m5_v1#'''reset'''
resetting ...
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK;

::These two ways actually erase the bootloader part of EMMC android, After bootup from SDcard Linux, You'd better [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command].

::d). The simplest way is insert the SDcard with Linux image flashed before power on, the Android bootloader will check boot.ini file whether exist in SDcard vfat partition, so that the SDcard Linux will bootup. After bootup, you can [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Erase_Emmc_Android_by_dd_command format the whole EMMC by dd command] and then flash the Linux image to EMMC.

...
BPI: try boot from sdcard
reading boot.ini
5699 bytes read in 3 ms (1.8 MiB/s)
## Executing script at 01b00000
...
reading Image.gz
9143358 bytes read in 510 ms (17.1 MiB/s)
reading meson64_bananapi_m5.dtb
70850 bytes read in 8 ms (8.4 MiB/s)
reading uInitrd
11704481 bytes read in 655 ms (17 MiB/s)
reading overlays/i2c0.dtbo
223 bytes read in 6 ms (36.1 KiB/s)
reading overlays/spi0.dtbo
516 bytes read in 6 ms (84 KiB/s)
reading overlays/uart1.dtbo
225 bytes read in 5 ms (43.9 KiB/s)

:2. Bootable EMMC with Linux image flashed

::a). Using uboot command, connect a debug console cable and press ESC while power on to enter uboot command line

bananapi_m5# mmc erase 0 1000

::b). Linux u-boot also check boot.ini file whether exist in SDcard vfat partition so that the SDcard Linux will bootup. After bootup, you can format the whole EMMC by dd command or flash the Linux image directly to EMMC.

:3. A extreme situation is bootloader or uboot corrupted, Rom load it from EMMC but hangup in u-boot or BL2, for example the boot process will hangup in BL2 of EMMC if dram init failed, The only way is format the EMMC with usb burning tool, or download the Android image completely and then try other ways to erase EMMC or flash Linux image to EMMC.

:4. Rom will try to load bootloader from SDcard directly if EMMC is empty.

===Erase Emmc Android by dd command===
:If the board is flashed android before, the whole emmc must be erased by these commands if you want bootup it with SDcard Linux image.
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot0 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0boot1 bs=1M status=noxfer
$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M status=noxfer
$ sync

===Wifi/BT support===

:1. Android test and support.
rtl8723bu wifi/bt(usb)
rtl8188eu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]
rtl8814au wifi(usb), please get the [https://github.com/aircrack-ng/rtl8814au aircrack-ng] driver and install.

:'''How to enable Android Wifi/BT'''

:USB type: Plug-in the usb dongle to usb host port and reboot the system, After bootup, you can enable or disable wifi and bluetooth in Settings app.
:SDIO/UART type: Connect the hardware module to 40pin header correctly and [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Android_DTB_overlay configure the Android DTB overlay] to enable it.

:'''Note''': Android is not support that ethernet and wifi are both connected at the same time, Ethernet have a higher prioprity than wifi, it means wifi can't connect network if ethernet already connected, and wifi will drop connection if ethernet cable plugin.

:2. Linux test and support.
rtl8188eu wifi(usb)
rtl8192eu wifi(usb)
rtl8723bu wifi/bt(usb)
rtl8811au wifi(usb)
rtl8812au wifi(usb)
rtl8812bu wifi(usb)
[http://forum.banana-pi.org/t/banana-pi-wifi-bt-4-2-expansion-board-standard-usb-interface/12162 rtl8821cu wifi/bt(usb)]
[http://forum.banana-pi.org/t/bpi-m5-wifi-bt-board-sdio-interface-802-11-a-b-g-n-ac-2t2r-wifi-and-bluectooch-5-0/11846 rtl8822cs wifi/bt(sdio/uart)]

:'''How to enable Linux Wifi'''

:Wifi module drivers are already prebuild in the release images.

:USB type: Plug-in the usb dongle to usb host port and driver will be loaded automatically.
:SDIO/UART type:
::1). Connect the hardware module to 40pin header correctly.
::2). Configure the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#DTB_overlay dtb overlay]
# Overlays to load
# Example combinations:
# spi0 i2c0 i2c1 uart0
# hktft32
# hktft35
setenv overlays "wifi_bt_rtl8822cs"
::3). Add the wifi module name to /etc/modules for loaded automatically next boot.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
88x2cs

:'''How to enable Linux Bluetooth'''

::1). Please download [https://github.com/Dangku/m5-rtk-linux-bt-driver rtk-linux-bt-driver] source code, build and install usb or uart rtk linux bluetooth drivers/firmwares to your image.
::2). For USB type, plug-in the usb dongle to usb host port and driver will be loaded automatically.
::3). For UART type, Configure the dtb overlay as the same as wifi before install the bluetooth drivers/firmwares. hci_uart driver will be loaded when rtk-hciuart.service start.

===Linux Server Image Network Configuration===

:[https://netplan.io Netplan]

:'''Linux Wifi STA mode'''

:A sample wifi sta mode netplan configuration file, 01-wlan0-sta.yaml
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: true
access-points:
"bananapi":
password: "123456789"

:'''Linux Wifi AP mode'''

:1. Prepare the setup the [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Wifi.2FBT_support wifi adater] correctly.

:2. Get the wifi adapter Band, Frequencies, Channel, HT Capability, VHT Capability or other properties
$ iw list

:3. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Network-Manager.

:Install NetworkManager because ap is only supported with NetworkManager renderer
$ sudo apt install network-manager

:A sample 2.4G wifi ap mode netplan configuration file, 01-wlan0-ap-2.4g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 2.4GHz
channel: 6
auth:
key-management: psk
password: "123456789"

:A sample 5G wifi ap mode netplan configuration file, 01-wlan0-ap-5g.yaml
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
dhcp4: no
access-points:
"bananapi":
mode: ap
band: 5GHz
channel: 36
auth:
key-management: psk
password: "123456789"

:4. Manage wifi access point mode with [http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux_Server_Image_Network_Configuration Netplan] and Hostapd.

:1). Create a netplan configuration file, 01-wlan0-ap-hostapd.yaml
network:
version: 2
renderer: networkd
ethernets:
wlan0:
dhcp4: no
addresses:
- 192.168.11.1/24

:2). Install hostapd
$ sudo apt install hostapd

:Create hostapd configuration file /etc/hostapd/hostapd.conf, for example
interface=wlan0
ssid=bananapi

driver=nl80211

auth_algs=1
wpa=2
wpa_passphrase=123456789
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

#bridge=br0
beacon_int=500
#SSID not hidden
ignore_broadcast_ssid=0

hw_mode=a
channel=36
max_num_sta=8

### IEEE 802.11n
ieee80211n=1
#require_vht=0
ht_capab=[HT20][HT40+][SHORT-GI-20][SHORT-GI-40][SHORT-GI-80][DSSS_CCK-40]

### IEEE 802.11ac
ieee80211ac=1
#require_vht=0
#vht_capab=[MAX-MPDU-3895][SHORT-GI-80][SU-BEAMFORMEE]
#vht_oper_chwidth=1
#vht_oper_centr_freq_seg0_idx=42

### WMM
wmm_enabled=1

:3). To support 80MHz channel width you need load driver with '''rtw_vht_enable=2''' option, Or you can create /etc/modprobe.d/8822cs.conf with content
options 88x2cs rtw_vht_enable=2

:4). Install and configure dhcp server service, use isc-dhcp-server for example

$ sudo apt install isc-dhcp-server

:Configure dhcp server interface in /etc/default/isc-dhcp-server
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="wlan0"

:Configure dhcp subnet and dns in /etc/dhcp/dhcpd.conf
...
option domain-name "example.org";
option domain-name-servers 8.8.8.8, 114.114.114.114;
...
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
subnet 192.168.11.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.11.1 192.168.11.100;
option broadcast-address 192.168.11.255;
option routers 192.168.11.1;
}

:5). Start Service
$ sudo hostapd /etc/hostapd/hostapd.conf -B
$ sudo systemctl restart isc-dhcp-server

:6). Routing configuration.
sysctl net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -s 192.168.11.0/24 -o eth0 -j MASQUERADE

===Cloud-init&Snap===
:Cloud-init and Snap service are enabled default, you can disable or remove them.

:1. disable or remove cloud-init
$ sudo touch /etc/cloud/cloud-init.disabled
:or
$ sudo apt purge cloud-init

:2. disable or remove snap
$ sudo apt purge snapd

===Enable rc-local===
:The systemd service rc-local.service already exists in release image, but there is no [Install] part in the unit file. As a result, Systemd is unable to enable it. First, we must update the file.

$ sudo nano /lib/systemd/system/rc-local.service

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target
Alias=rc-local.service

:Create /etc/rc.local file.

sudo nano /etc/rc.local

#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

:Add executable permission to /etc/rc.local

$ sudo chmod +x /etc/rc.local

:Enable rc-local.service and reboot

$ sudo systemctl enable rc-local.service
$ sudo reboot

===Enable sudo for Debian===
:The release Debian image do not install sudo default, with "su -" command, user can change to root. If you like sudo, you can install it.

$ su -
Password:(enter bananapi)

# apt install sudo
# adduser pi sudo

: Then please do logout and login again

===Install Docker Engine===
:Install Docker Engine on Ubuntu 20.04 Server

:1. Set up the repository

:Update the apt package index and install packages to allow apt to use a repository over HTTPS:
$ sudo apt-get update
$ sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

:Add Docker’s official GPG key:
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

:Set up the stable repository
$ echo \
"deb [arch=arm64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

:2. Install Docker Engine
$ sudo apt-get update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

:3. Verify the Docker Engine is installed correctly by running the hello-world image.
$ sudo docker run hello-world

:[[File:docker-test.png]]

Install docker with a simple command

$ curl -sSL get.docker.com | sudo sh

[https://docs.docker.com/engine/install/ Install Docker Engine] on other Linux distributions