Banana Pi Wiki - User contributions [en]

Getting Started with M5/M2Pro

2024-07-25T08:06:54Z

Dangku: /* Linux Server Image Network Configuration */

=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('''3.3V,Baud: 115200'''), 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.
:5. User name/password: '''pi/bananapi''' ,'''root/bananapi'''.

==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

:or you can get the source code tar archive from [https://pan.baidu.com/s/1TmmR_075b49lPSt1Phq0ag?pwd=8888 Baidu Pan(pincode: 8888)] or [https://drive.google.com/drive/folders/1RuvazYcr46HKMvNBxSqQftdyWa0tK9f7?usp=share_link Google Drive]

: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. It’s recommended to use A1 rated cards, 8GB at least.

:3. M5 and M2pro are compatiable with same Linux image.

:4. 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]

:5. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:6. 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

:7. Download latest [http://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux Linux Image], and confirm that the md5 checksum is correct.

:8. Default login: pi/bananapi or root/bananapi

:9. The wiki guide is only for [https://wiki.banana-pi.org/Banana_Pi_BPI-M5#Linux bananapi 4.9 bsp ubuntu/debian images].

===Install Image to SDcard===
:1. Install Image with Balena 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 Balena Cli on Windows, Linux and MacOS.
:[https://github.com/balena-io/balena-cli Balena CLI] is a Command Line Interface for balenaCloud or openBalena. It can be used to flash linux image. Download the installer or standalone package from [https://github.com/balena-io/balena-cli/releases balena-io] and [https://github.com/balena-io/balena-cli/blob/master/INSTALL.md install] it correctly to your PC, then you can use the "[https://docs.balena.io/reference/balena-cli/#local-flash-image local flash]" command option of balena to flash a linux image to sdcard or usb drive.

$ sudo balena local flash path/to/xxx-bpi-m5-xxx.img.zip
$ sudo balena local flash path/to/xxx-bpi-m5-xxx.img.zip --drive /dev/sdX
$ sudo balena local flash path/to/xxx-bpi-m5-xxx.img.zip --drive /dev/sdX --yes

:3. 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

:4. 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/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/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, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential git
$ git clone https://github.com/Dangku/WiringPi
$ cd 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/Dangku/WiringPi/tree/master/examples WiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-adafruit, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:oled, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-pip python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

: Create and install wheel package
$ sudo python3 setup.py bdist_wheel
$ sudo pip3 install dist/RPi.GPIO-XXX.whl

: Install from git source directly without development
$ sudo pip3 install git+https://github.com/Dangku/RPi.GPIO.git

: If the package is already installed, it should be uninstalled before installing the new one, or installing the new one with --force-reinstall option.

===WiringPi-Python===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi-Python.git
$ cd WiringPi-Python
$ sudo python3 setup.py install

===Luma.Examples===
:[https://github.com/rm-hull/luma.examples luma.examples] use GPIO.BCM gpio mode default, so you should map 40pin header pins to bcm gpio number and connect the hardware correctly.

:1. build and install RPi.GPIO

$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

:you can change the bcmledpin variable in test/led.py to your hardware backlight gpio and run it to check RPi.GPIO works well.

$ sudo python3 test/led.py

:hardware backlight will repeat on and off

:2. luma.examples libs install

$ sudo usermod -a -G i2c,spi,gpio pi

:if group does not exist, the following command will create it:

$ sudo groupadd --system xxx

$ sudo apt-get install python3-dev python3-pip libfreetype6-dev libjpeg-dev build-essential
$ sudo apt-get install libsdl-dev libportmidi-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-image1.2-dev
$ git clone https://github.com/rm-hull/luma.examples.git
$ cd luma.examples

:install luma.core, luma.emulator, luma.lcd, luma.le-matrix, luma.oled pip libs, make sure this step without error or downloading interrupted, try again if get errors
$ sudo -H pip install -e .
:or
$ sudo -H pip3 install -e .

:for debian buster(python 3.7) which does not include /usr/bin/pip in package python3-pip, and will get the following errors when install luma packages with pip3

...
WARNING, No "Setup" File Exists, Running "buildconfig/config.py"
Using UNIX configuration...

/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
...

:install sdl2 related packages to fix this issue, then install luma libs again with pip3
$ sudo apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-mixer-dev libsdl2-image-dev
$ sudo -H pip3 install -e .

:check installed luma pip libs
$ pip3 list | grep luma

luma.core 2.4.0
luma.emulator 1.4.0
luma.lcd 2.10.0
luma.led-matrix 1.7.0
luma.oled 3.11.0

:3. examples test
:Enable i2c or spi [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#DTB_overlay overlays] before running test examples
$ cd examples
$ sudo python3 bounce.py --config ../conf/ili9341.conf

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M5/M2pro Tested HDMI LCD'''
|-
|panel || /boot/boot.ini
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd.htm Waveshare 3.5inch 480x320] || setenv display_autodetect "false"
setenv hdmimode "480x320p60hz"
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd-e.htm Waveshare 3.5inch 640x480] ||
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720]
|-
| [https://www.waveshare.com/5inch-hdmi-amoled.htm Waveshare 5inch 960x544] ||
|-
| [https://www.waveshare.com/5inch-hdmi-lcd-h.htm Waveshare 5inch 800x480] ||
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || setenv display_autodetect "false"
setenv hdmimode "1440x2560p60hz"
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-b.htm Waveshare 7inch 800x480] ||
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-c.htm Waveshare 7inch 1024x600] ||
|-
| [https://www.waveshare.com/7.9inch-HDMI-LCD.htm Waveshare 7.9inch 400x1280] ||
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || setenv display_autodetect "false"
setenv hdmimode "1536x2048p60hz"
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] ||
|-
| [https://www.waveshare.com/9inch-2560x1600-Monitor.htm Waveshare 9inch 2560x1600] || setenv display_autodetect "false"
setenv hdmimode "2560x1600p60hz"
|-
| [https://www.waveshare.com/10.1inch-HDMI-LCD-E.htm Waveshare 10.1inch 1024x600] ||
|-
| [https://www.waveshare.com/10.1inch-hdmi-lcd-b-with-case.htm Waveshare 10.1inch 1280x800] ||
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] ||
|-
| [https://www.waveshare.com/12.3inch-hdmi-lcd.htm Waveshare 12.3inch 1920x720] ||
|-
| [https://www.waveshare.com/13.3inch-HDMI-LCD-H.htm Waveshare 13.3inch 1920x1080] ||
|-
| [https://www.waveshare.com/15.6inch-hdmi-lcd-h-with-case.htm Waveshare 15.6inch 1920x1080] ||
|}

: backlight control

https://github.com/Dangku/Waveshare-USB-Brightness

===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/M2Pro#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/M2Pro#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

===Disable 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 root
Password:(enter bananapi)

# apt-get update
# apt-get 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

2024-07-25T08:06:18Z

Dangku: /* Linux Server Image Network Configuration */

Getting Started with M5/M2Pro

2024-07-25T08:05:46Z

Dangku: /* Linux Server Image Network Configuration */

Getting Started with M5/M2Pro

2024-07-25T08:04:47Z

Dangku: /* Linux Server Image Network Configuration */

Getting Started with M2S

2024-07-05T08:16:41Z

Dangku: /* WiringPi2-Python */

=Introduction=
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]
[[File:Banana_Pi_BPI-M2S_S922_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic S922x chip]]
[[File:Banana_Pi_BPI-M2S_with_poe.jpg|thumb|BPI-M2S with [[BPI-9600 IEEE 802.3af PoE module]]]]
[[File:Banana_Pi_BPI-M2S_with_wifi_and_BT_module.jpg|thumb|BPI-M2S with Wifi&BT module]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]] Amlogic S905x3 design]]

=specifications=

=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].
:4. Only A311D variant board have camera, mipi panel and npu support.

==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-M2S#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. Press and hold USB button on the board, plugin type-c usb cable to PC or press the RST button if power adapter already connected, about two seconds later, release the button, the board will be identified correctly.

:[[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

:or you can get the source code tar archive from [https://pan.baidu.com/s/1rANGEB-1MLPCBXqOR5aYCg?pwd=8888 BaiduPan(pincode: 8888)] or [https://drive.google.com/drive/folders/1INIABp_MbB5UcwfqujTngGLOZN7YGuWp?usp=share_link GoogleDrive]

: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 M2S DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M2S 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. It’s recommended to use A1 rated cards, 8GB at least.

:3. 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]

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. 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

:6. Download Linux latest [https://wiki.banana-pi.org/Banana_Pi_BPI-M2S#Linux Linux Image], and confirm that the md5 checksum is correct.

:7. Default login: pi/bananapi or root/bananapi

:8. The wiki guide is only for [https://wiki.banana-pi.org/Banana_Pi_BPI-M2S#Linux bananapi 4.9 bsp ubuntu/debian images].

===Install Image to SDcard===
:1. Install Image with Balena 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 Balena Cli on Windows, Linux and MacOS.
:[https://github.com/balena-io/balena-cli Balena CLI] is a Command Line Interface for balenaCloud or openBalena. It can be used to flash linux image. Download the installer or standalone package from [https://github.com/balena-io/balena-cli/releases balena-io] and [https://github.com/balena-io/balena-cli/blob/master/INSTALL.md install] it correctly to your PC, then you can use the "[https://docs.balena.io/reference/balena-cli/#local-flash-image local flash]" command option of balena to flash a linux image to sdcard or usb drive.

$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip
$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip --drive /dev/disk2
$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip --drive /dev/disk2 --yes

:3. 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-m2s-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:4. 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-m2s-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-m2s-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-m2s-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/
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
i2c1.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c2.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/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-M2S#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

===WiringPi===
: Note: This WiringPi only support set 40pin 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, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential git
$ git clone https://github.com/Dangku/WiringPi
$ cd WiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m2s_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/Dangku/WiringPi/tree/master/examples WiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-adafruit, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:oled, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-pip python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

: Create and install wheel package
$ sudo python3 setup.py bdist_wheel
$ sudo pip3 install dist/RPi.GPIO-XXX.whl

: Install from git source directly without development
$ sudo pip3 install git+https://github.com/Dangku/RPi.GPIO.git

: If the package is already installed, it should be uninstalled before installing the new one, or installing the new one with --force-reinstall option.

===WiringPi-Python===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi-Python.git
$ cd WiringPi-Python
$ sudo python3 setup.py install

===Luma.Examples===
:[https://github.com/rm-hull/luma.examples luma.examples] use GPIO.BCM gpio mode default, so you should map 40pin header pins to bcm gpio number and connect the hardware correctly.

:1. build and install RPi.GPIO
:build bananapi m2s RPi.GPIO with python3 instead of python because luma uses python3.

$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

:you can change the bcmledpin variable in test/led.py to your hardware backlight gpio and run it to check RPi.GPIO works well.

$ sudo python3 test/led.py

:hardware backlight will repeat on and off

:2. luma.examples libs install

$ sudo usermod -a -G i2c,spi,gpio pi

:if group does not exist, the following command will create it:

$ sudo groupadd --system xxx

$ sudo apt-get install python3-dev python3-pip libfreetype6-dev libjpeg-dev build-essential
$ sudo apt-get install libsdl-dev libportmidi-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-image1.2-dev
$ git clone https://github.com/rm-hull/luma.examples.git
$ cd luma.examples

:install luma.core, luma.emulator, luma.lcd, luma.le-matrix, luma.oled pip libs, make sure this step without error or downloading interrupted, try again if get errors
$ sudo -H pip install -e .
:or
$ sudo -H pip3 install -e .

:for debian buster(python 3.7) which does not include /usr/bin/pip in package python3-pip, and will get the following errors when install luma packages with pip3

...
WARNING, No "Setup" File Exists, Running "buildconfig/config.py"
Using UNIX configuration...

/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
...

:install sdl2 related packages to fix this issue, then install luma libs again with pip3
$ sudo apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-mixer-dev libsdl2-image-dev
$ sudo -H pip3 install -e .

:check installed luma pip libs
$ pip3 list | grep luma

luma.core 2.4.0
luma.emulator 1.4.0
luma.lcd 2.10.0
luma.led-matrix 1.7.0
luma.oled 3.11.0

:3. examples test
:Enable i2c or spi [https://wiki.banana-pi.org/Getting_Started_with_M2S#DTB_overlay overlays] before running test examples
$ cd examples
$ sudo python3 bounce.py --config ../conf/ili9341.conf

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M2S Tested HDMI LCD'''
|-
|panel || /boot/env.txt
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd.htm Waveshare 3.5inch 480x320] || hdmi_autodetect=no
hdmi=480x320p60hz
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd-e.htm Waveshare 3.5inch 640x480] ||
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720]
|-
| [https://www.waveshare.com/5inch-hdmi-lcd-h.htm Waveshare 5inch 800x480] ||
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || hdmi_autodetect=no
hdmi=1440x2560p60hz
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-b.htm Waveshare 7inch 800x480] ||
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-c.htm Waveshare 7inch 1024x600] ||
|-
| [https://www.waveshare.com/7.9inch-HDMI-LCD.htm Waveshare 7.9inch 400x1280] ||
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || hdmi_autodetect=no
hdmi=1536x2048p60hz
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] ||
|-
| [https://www.waveshare.com/9inch-2560x1600-Monitor.htm Waveshare 9inch 2560x1600] || hdmi_autodetect=no
hdmi=2560x1600p60hz
|-
| [https://www.waveshare.com/10.1inch-HDMI-LCD-E.htm Waveshare 10.1inch 1024x600] ||
|-
| [https://www.waveshare.com/10.1inch-hdmi-lcd-b-with-case.htm Waveshare 10.1inch 1280x800] ||
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] ||
|-
| [https://www.waveshare.com/13.3inch-HDMI-LCD-H.htm Waveshare 13.3inch 1920x1080] ||
|-
| [https://www.waveshare.com/15.6inch-hdmi-lcd-h-with-case.htm Waveshare 15.6inch 1920x1080] ||
|}

: backlight control

https://github.com/Dangku/Waveshare-USB-Brightness

===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.

==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

===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-M2S#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-M2S#DTB_overlay dtb overlay]
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.

===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 root
Password:(enter bananapi)

# apt-get update
# apt-get 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 M2S

2024-07-05T08:16:28Z

Dangku: /* WiringPi */

=Introduction=
[[File:Banana_Pi_BPI-M2S_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic A311D chip]]
[[File:Banana_Pi_BPI-M2S_S922_1.jpg|thumb|[[Banana Pi BPI-M2S]] Amlogic S922x chip]]
[[File:Banana_Pi_BPI-M2S_with_poe.jpg|thumb|BPI-M2S with [[BPI-9600 IEEE 802.3af PoE module]]]]
[[File:Banana_Pi_BPI-M2S_with_wifi_and_BT_module.jpg|thumb|BPI-M2S with Wifi&BT module]]
[[File:BPI-M2_Pro_2.jpg|thumb|[[Banana Pi BPI-M2 Pro]] S905x3 design]]
[[File:Banana_Pi_BPI-M5_4.JPG|thumb|[[Banana Pi BPI-M5]] Amlogic S905x3 design]]

=specifications=

=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].
:4. Only A311D variant board have camera, mipi panel and npu support.

==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-M2S#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. Press and hold USB button on the board, plugin type-c usb cable to PC or press the RST button if power adapter already connected, about two seconds later, release the button, the board will be identified correctly.

:[[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

:or you can get the source code tar archive from [https://pan.baidu.com/s/1rANGEB-1MLPCBXqOR5aYCg?pwd=8888 BaiduPan(pincode: 8888)] or [https://drive.google.com/drive/folders/1INIABp_MbB5UcwfqujTngGLOZN7YGuWp?usp=share_link GoogleDrive]

: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 M2S DTBO idx value table, default idx value is 0 in release image.

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M2S 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. It’s recommended to use A1 rated cards, 8GB at least.

:3. 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]

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. 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

:6. Download Linux latest [https://wiki.banana-pi.org/Banana_Pi_BPI-M2S#Linux Linux Image], and confirm that the md5 checksum is correct.

:7. Default login: pi/bananapi or root/bananapi

:8. The wiki guide is only for [https://wiki.banana-pi.org/Banana_Pi_BPI-M2S#Linux bananapi 4.9 bsp ubuntu/debian images].

===Install Image to SDcard===
:1. Install Image with Balena 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 Balena Cli on Windows, Linux and MacOS.
:[https://github.com/balena-io/balena-cli Balena CLI] is a Command Line Interface for balenaCloud or openBalena. It can be used to flash linux image. Download the installer or standalone package from [https://github.com/balena-io/balena-cli/releases balena-io] and [https://github.com/balena-io/balena-cli/blob/master/INSTALL.md install] it correctly to your PC, then you can use the "[https://docs.balena.io/reference/balena-cli/#local-flash-image local flash]" command option of balena to flash a linux image to sdcard or usb drive.

$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip
$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip --drive /dev/disk2
$ sudo balena local flash path/to/xxx-bpi-m2s-xxx.img.zip --drive /dev/disk2 --yes

:3. 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-m2s-xxx.img.zip | pv | dd of=/dev/sdX bs=10M status=noxfer

:4. 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-m2s-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-m2s-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-m2s-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/
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
i2c1.dtbo pwm_ef.dtbo waveshare_tft24_lcd.dtbo
i2c2.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/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-M2S#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

===WiringPi===
: Note: This WiringPi only support set 40pin 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, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential git
$ git clone https://github.com/Dangku/WiringPi
$ cd WiringPi
$ chmod a+x build
$ sudo ./build

:2. Run '''gpio readall''' to show all 40pins status.
[[File:m2s_wiringpi.png]]

:3. BPI GPIO Extend board and examples in [https://github.com/Dangku/WiringPi/tree/master/examples WiringPi/examples]

:blinkall, blink all pin header gpios, no extend board.
:lcd-adafruit, [http://wiki.banana-pi.org/BPI_LCD_1602_display_module BPI LCD 1602 display module] example.
:oled, [http://wiki.banana-pi.org/BPI_OLED_Display_Module BPI OLED Display Module] example.
:matrixled, [http://wiki.banana-pi.org/BPI_RGB_LED_Matrix_Expansion_Module BPI RGB LED Matrix Expansion Module] example.
:berryclip, [http://wiki.banana-pi.org/BPI_BerryClip_Module BPI BerryClip Module]

===RPi.GPIO===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-pip python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

: Create and install wheel package
$ sudo python3 setup.py bdist_wheel
$ sudo pip3 install dist/RPi.GPIO-XXX.whl

: Install from git source directly without development
$ sudo pip3 install git+https://github.com/Dangku/RPi.GPIO.git

: If the package is already installed, it should be uninstalled before installing the new one, or installing the new one with --force-reinstall option.

===WiringPi2-Python===

: Build and install, for debian, you must [https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Enable_sudo_for_Debian install sudo] before build
$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools swig git
$ git clone --recursive https://github.com/Dangku/WiringPi-Python.git
$ cd WiringPi-Python
$ sudo python3 setup.py install

===Luma.Examples===
:[https://github.com/rm-hull/luma.examples luma.examples] use GPIO.BCM gpio mode default, so you should map 40pin header pins to bcm gpio number and connect the hardware correctly.

:1. build and install RPi.GPIO
:build bananapi m2s RPi.GPIO with python3 instead of python because luma uses python3.

$ sudo apt-get update
$ sudo apt-get install build-essential python3 python3-dev python3-setuptools git
$ git clone https://github.com/Dangku/RPi.GPIO.git
$ cd RPi.GPIO
$ sudo python3 setup.py clean --all
$ sudo python3 setup.py install

:you can change the bcmledpin variable in test/led.py to your hardware backlight gpio and run it to check RPi.GPIO works well.

$ sudo python3 test/led.py

:hardware backlight will repeat on and off

:2. luma.examples libs install

$ sudo usermod -a -G i2c,spi,gpio pi

:if group does not exist, the following command will create it:

$ sudo groupadd --system xxx

$ sudo apt-get install python3-dev python3-pip libfreetype6-dev libjpeg-dev build-essential
$ sudo apt-get install libsdl-dev libportmidi-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-image1.2-dev
$ git clone https://github.com/rm-hull/luma.examples.git
$ cd luma.examples

:install luma.core, luma.emulator, luma.lcd, luma.le-matrix, luma.oled pip libs, make sure this step without error or downloading interrupted, try again if get errors
$ sudo -H pip install -e .
:or
$ sudo -H pip3 install -e .

:for debian buster(python 3.7) which does not include /usr/bin/pip in package python3-pip, and will get the following errors when install luma packages with pip3

...
WARNING, No "Setup" File Exists, Running "buildconfig/config.py"
Using UNIX configuration...

/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
...

:install sdl2 related packages to fix this issue, then install luma libs again with pip3
$ sudo apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-mixer-dev libsdl2-image-dev
$ sudo -H pip3 install -e .

:check installed luma pip libs
$ pip3 list | grep luma

luma.core 2.4.0
luma.emulator 1.4.0
luma.lcd 2.10.0
luma.led-matrix 1.7.0
luma.oled 3.11.0

:3. examples test
:Enable i2c or spi [https://wiki.banana-pi.org/Getting_Started_with_M2S#DTB_overlay overlays] before running test examples
$ cd examples
$ sudo python3 bounce.py --config ../conf/ili9341.conf

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M2S Tested HDMI LCD'''
|-
|panel || /boot/env.txt
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd.htm Waveshare 3.5inch 480x320] || hdmi_autodetect=no
hdmi=480x320p60hz
|-
| [https://www.waveshare.com/3.5inch-hdmi-lcd-e.htm Waveshare 3.5inch 640x480] ||
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720]
|-
| [https://www.waveshare.com/5inch-hdmi-lcd-h.htm Waveshare 5inch 800x480] ||
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || hdmi_autodetect=no
hdmi=1440x2560p60hz
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-b.htm Waveshare 7inch 800x480] ||
|-
| [https://www.waveshare.com/7inch-hdmi-lcd-c.htm Waveshare 7inch 1024x600] ||
|-
| [https://www.waveshare.com/7.9inch-HDMI-LCD.htm Waveshare 7.9inch 400x1280] ||
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || hdmi_autodetect=no
hdmi=1536x2048p60hz
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] ||
|-
| [https://www.waveshare.com/9inch-2560x1600-Monitor.htm Waveshare 9inch 2560x1600] || hdmi_autodetect=no
hdmi=2560x1600p60hz
|-
| [https://www.waveshare.com/10.1inch-HDMI-LCD-E.htm Waveshare 10.1inch 1024x600] ||
|-
| [https://www.waveshare.com/10.1inch-hdmi-lcd-b-with-case.htm Waveshare 10.1inch 1280x800] ||
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] ||
|-
| [https://www.waveshare.com/13.3inch-HDMI-LCD-H.htm Waveshare 13.3inch 1920x1080] ||
|-
| [https://www.waveshare.com/15.6inch-hdmi-lcd-h-with-case.htm Waveshare 15.6inch 1920x1080] ||
|}

: backlight control

https://github.com/Dangku/Waveshare-USB-Brightness

===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.

==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

===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-M2S#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-M2S#DTB_overlay dtb overlay]
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.

===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 root
Password:(enter bananapi)

# apt-get update
# apt-get 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

2024-04-30T04:38:11Z

2024-04-30T03:04:18Z

Dangku: /* Custom Logo */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===
:Change boot logo and bootanimation by adb command

:1. Boot logo

:Prepare a 24bit bootlogo.bmp file, resolution limited to 1280x720, then push it to android by adb
$ adb root
$ adb remount
$ adb push bootlogo.bmp /Reserve0/
$ adb reboot

:2. Bootanimation logo

:Create a folder named media, put bootanimation.zip to it and push to android by adb
$ mkdir media
$ cp bootanimation.zip media/
$ adb root
$ adb remount
$ adb push media /system/
$ adb reboot

:Change boot logo and bootanimation by building android source code

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===
:Install Play Store with Magisk, it's not recommended.

:1. Download the latest [https://magiskmanager.com/ Magisk app]
:2. Download [https://sourceforge.net/projects/litegapps/files/litegapps/arm/31/lite/v2.5/ LiteGapps arm package]
:4. Copy Magisk apk file and LiteGapps zip package to SDcard and plugin it to the board.
:5. Follow the process in the video to Install Google Play store.

:<youtube>pMKBVcJhsx4</youtube>

:Another way, you can build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

: The default audio output channel is hdmi, switch it to jack output in Settings->Sound->Audio output channel

:[[File:m4b_audio_switch.jpg]]

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M4 Berry Tested HDMI LCD'''
|-
|panel || Test Video
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720] || https://youtu.be/CRcjx6_29rA
|-
| [https://www.waveshare.com/5inch-hdmi-amoled.htm Waveshare 5inch 960x544] || https://youtu.be/0wZ3lWQQTkQ
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || https://youtu.be/z9gTHa3i8Ag
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || https://youtu.be/Qjwo4vVBQmo
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] || https://youtu.be/SP9-HGrY6-M
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] || https://youtu.be/WA1yBGcYZds
|-
| [https://www.waveshare.com/12.3inch-hdmi-lcd.htm Waveshare 12.3inch 1920x720] || https://youtu.be/OJfqtHlgDvk
|}

Banana Pi BPI-M5

2024-03-15T02:45:23Z

Dangku: /* Armbian */

[[zh:香蕉派_BPI-M5]]
=BPI-M5 Introduction=
[[File:Banana_Pi_BPI-M5_1.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: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 64-bit 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 64-bit 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|| 85x56 mm, 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:https://drive.google.com/drive/folders/1RuvazYcr46HKMvNBxSqQftdyWa0tK9f7?usp=share_link

===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/
*BPI-M5 How to install Ubuntu server on external USB-disk:https://forum.banana-pi.org/t/bpi-m5-howto-install-ubuntu-server-on-external-usb-disk/15259
*Install Armbian, OctoPrint and Klipper on the emmc of a Banana pi M5 - Linux and windows : https://www.youtube.com/watch?v=q5I6pzWCTrg
*CoreELEC for Banana Pi BPI-M2 Pro and BPI-M5:https://wiki.coreelec.org/coreelec:bpi
*U-Boot for BananaPi BPI-M2-PRO (S905X3):https://u-boot.readthedocs.io/en/latest/board/amlogic/bananapi-m2pro.html
*How to flash Armbian to the eMMc of the Banana-Pi BPi-M5:https://uglyscale.press/2023/08/31/how-to-flash-armbian-to-emmc-of-banana-pi-bpi-m5/

=System image=

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

*2023-03-01 release, tablet variant image
: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 release, box variant image
: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

==Linux==
:[http://wiki.banana-pi.org/Getting_Started_with_BPI-M5#Linux How to flash Linux Image]
===Ubuntu===
*2023-08-30-ubuntu-20.04-server-bpi-m5-m2pro-aarch64-sd-emmc.img
:Baidu Cloud: https://pan.baidu.com/s/16nAyyW0IfTJqoYat2Qfcag?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1y3i9uUgzmp03r9zzeuJkNszPZNl7D0OR?usp=sharing

*2023-08-30-ubuntu-20.04-mate-desktop-bpi-m5-m2pro-aarch64-sd-emmc.img
:Baidu Cloud: https://pan.baidu.com/s/1UgfUDdNE-SQHka64mrNAYw?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1RMX8F1PMLO-UcPPJL4QwYvdPVhk-a_c_?usp=sharing

===Debian===
*2023-08-30-debian-10-buster-xfce-bpi-m5-m2pro-aarch64-sd-emmc.img
:Baidu Cloud: https://pan.baidu.com/s/15XHAZKDFqJLA3BH1b9Slqw?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1EDXxJs23xV5Je91ZhfPYDvBubhhmJN1n?usp=sharing

*2023-08-30-debian-10-buster-bpi-m5-m2pro-aarch64-sd-emmc.img
:Baidu Cloud: https://pan.baidu.com/s/1tFUbyPbrTJ5UGgM05w2k6A?pwd=8888 (pincode:8888)
:Google Drive:https://drive.google.com/drive/folders/1Y-GuZYovWRgBvt0z7FLnIuBJufVFflvv?usp=sharing

==Third part image==

===Raspbian===
*BPI-M5 BPI-M2 Pro new image:Raspbian image, 2023-05-03 update,please choose the right image
:Google driver: https://drive.google.com/drive/folders/1Rvr1l3LhnVcss0FD0_bAm3Jbi84vZBkT
:Baidu Cloud : https://pan.baidu.com/s/1T2DT3ruTRvRdFgIUrR1obg?pwd=8888 (pincode：8888)
*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/1VoiHH0IMU5iZRRdGg1-SpSu8pmwnjkmX
:Baidu Cloud: https://pan.baidu.com/s/1Y1S05nGQDOP8Pxu9eE6k_Q?pwd=8888
: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-13, 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

*Armbian legacy build with bananapi kernel 4.9

===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

==How to install Ubuntu Server 20.04 to M5 EMMC==
[[How to install Ubuntu Server 20.04 to M5 EMMC]]

=Easy to buy=

*SINOVOIP Aliexpress shop: https://www.aliexpress.us/item/3256801685527943.html?
*Bipai Aliexpress shop: https://www.aliexpress.us/item/3256803496172400.html
*Taobao Shop: https://item.taobao.com/item.htm?spm=a1z10.1-c-s.w4004-25059194388.8.13c23a90voeqk3&id=636199832159

*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

Getting Started with BPI-M4 Zero

2024-01-26T10:32:37Z

Dangku: /* Install Play Store */

[[zh:快速上手_BPI-M4_Zero]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Zero#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-zero_android_1.jpg]]
:[[File:m4-zero_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Zero while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-zero_android_3.jpg]]

:3. Download

:[[File:m4-zero_android_4.jpg]]

:4. Download finish

:[[File:m4-zero_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:Install Play Store with Magisk, it's not recommended.

:1. Download the latest [https://magiskmanager.com/ Magisk app]
:2. Download [https://sourceforge.net/projects/litegapps/files/litegapps/arm/31/lite/v2.5/ LiteGapps arm package]
:4. Copy Magisk apk file and LiteGapps zip package to SDcard and plugin it to the board.
:5. Follow the process in the video to Install Google Play store.

:<youtube>pMKBVcJhsx4</youtube>

:Another way, you can build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Zero#Linux | Linux Image]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Zero#Linux | bananapi 4.9 bsp ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

:1. Make sure that the Linux image has been burned into an SD card and started normally.

:2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

:3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

::[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

:4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface, an HDMI cable, and a mini HDMI to HDMI adapter.
:3. Use an HDMI cable and a mini HDMI to HDMI adapter to connect the monitor and BPI-M4 Zero, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Zero UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Zero, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Zero on the router management interface, or use the following command on the BPI-M4 Zero UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Zero is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Zero user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Zero in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Zero in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4zero:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Zero board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Zero.If it is a USB disk with a type-A plug, you also need a type-A to type-C adapter.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Zero Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, use an HDMI cable and a mini HDMI to HDMI adapter to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4zero:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4zero:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Zero in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

Getting Started with BPI-M4 Berry

2024-01-26T10:31:39Z

Dangku: /* Install Play Store */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===
:Install Play Store with Magisk, it's not recommended.

:1. Download the latest [https://magiskmanager.com/ Magisk app]
:2. Download [https://sourceforge.net/projects/litegapps/files/litegapps/arm/31/lite/v2.5/ LiteGapps arm package]
:4. Copy Magisk apk file and LiteGapps zip package to SDcard and plugin it to the board.
:5. Follow the process in the video to Install Google Play store.

:<youtube>pMKBVcJhsx4</youtube>

:Another way, you can build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

: The default audio output channel is hdmi, switch it to jack output in Settings->Sound->Audio output channel

:[[File:m4b_audio_switch.jpg]]

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M4 Berry Tested HDMI LCD'''
|-
|panel || Test Video
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720] || https://youtu.be/CRcjx6_29rA
|-
| [https://www.waveshare.com/5inch-hdmi-amoled.htm Waveshare 5inch 960x544] || https://youtu.be/0wZ3lWQQTkQ
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || https://youtu.be/z9gTHa3i8Ag
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || https://youtu.be/Qjwo4vVBQmo
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] || https://youtu.be/SP9-HGrY6-M
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] || https://youtu.be/WA1yBGcYZds
|-
| [https://www.waveshare.com/12.3inch-hdmi-lcd.htm Waveshare 12.3inch 1920x720] || https://youtu.be/OJfqtHlgDvk
|}

Getting Started with BPI-M4 Berry

2024-01-26T10:27:57Z

Dangku: /* Install Play Store */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:1. Download the latest [https://magiskmanager.com/ Magisk app]
:2. Download [https://sourceforge.net/projects/litegapps/files/litegapps/arm/31/lite/v2.5/ LiteGapps arm package]
:4. Copy Magisk apk file and LiteGapps zip package to SDcard and plugin it to the board.
:5. Follow the process in the video to Install Google Play store.

:<youtube>pMKBVcJhsx4</youtube>

:Another way, you can build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

: The default audio output channel is hdmi, switch it to jack output in Settings->Sound->Audio output channel

:[[File:m4b_audio_switch.jpg]]

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M4 Berry Tested HDMI LCD'''
|-
|panel || Test Video
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720] || https://youtu.be/CRcjx6_29rA
|-
| [https://www.waveshare.com/5inch-hdmi-amoled.htm Waveshare 5inch 960x544] || https://youtu.be/0wZ3lWQQTkQ
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || https://youtu.be/z9gTHa3i8Ag
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || https://youtu.be/Qjwo4vVBQmo
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] || https://youtu.be/SP9-HGrY6-M
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] || https://youtu.be/WA1yBGcYZds
|-
| [https://www.waveshare.com/12.3inch-hdmi-lcd.htm Waveshare 12.3inch 1920x720] || https://youtu.be/OJfqtHlgDvk
|}

Getting Started with BPI-M4 Berry

2024-01-26T10:25:48Z

Dangku: /* Install Play Store */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:1. Download the latest [https://magiskmanager.com/ Magisk app]
:2. Download [https://sourceforge.net/projects/litegapps/files/litegapps/arm/31/lite/v2.5/ LiteGapps arm package]
:4. Copy download apps and package to SDcard and plugin it to Bananapi R2pro.
:5. Follow the process in the video to Install Google Play store.

:<youtube>pMKBVcJhsx4</youtube>

:Another way, you can build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

: The default audio output channel is hdmi, switch it to jack output in Settings->Sound->Audio output channel

:[[File:m4b_audio_switch.jpg]]

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

===HDMI LCD===

:{| class="wikitable"
|-
| style="background: PaleTurquoise; color: black" colspan="4"| '''Bananapi M4 Berry Tested HDMI LCD'''
|-
|panel || Test Video
|-
| [https://www.waveshare.com/4inch-hdmi-lcd-c.htm Waveshare 4inch 720x720] || https://youtu.be/CRcjx6_29rA
|-
| [https://www.waveshare.com/5inch-hdmi-amoled.htm Waveshare 5inch 960x544] || https://youtu.be/0wZ3lWQQTkQ
|-
| [https://www.waveshare.com/5.5inch-1440x2560-lcd.htm Waveshare 5.5inch 1440x2560] || https://youtu.be/z9gTHa3i8Ag
|-
| [https://www.waveshare.com/8inch-1536x2048-LCD.htm Waveshare 8inch 1536x2048] || https://youtu.be/Qjwo4vVBQmo
|-
| [https://www.waveshare.com/8.8inch-Side-Monitor.htm Waveshare 8.8inch 480x1920] || https://youtu.be/SP9-HGrY6-M
|-
| [https://www.waveshare.com/11.9inch-HDMI-LCD.htm Waveshare 11.9inch 320x1480] || https://youtu.be/WA1yBGcYZds
|-
| [https://www.waveshare.com/12.3inch-hdmi-lcd.htm Waveshare 12.3inch 1920x720] || https://youtu.be/OJfqtHlgDvk
|}

Getting Started with BPI-M4 Zero

2024-01-22T03:52:52Z

Dangku: /* Install Image with USB tool */

[[zh:快速上手_BPI-M4_Zero]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Zero#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-zero_android_1.jpg]]
:[[File:m4-zero_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Zero while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-zero_android_3.jpg]]

:3. Download

:[[File:m4-zero_android_4.jpg]]

:4. Download finish

:[[File:m4-zero_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:Build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Zero#Linux | Linux Image]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Zero#Linux | bananapi 4.9 bsp ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

:1. Make sure that the Linux image has been burned into an SD card and started normally.

:2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

:3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

::[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
::[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

:4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface, an HDMI cable, and a mini HDMI to HDMI adapter.
:3. Use an HDMI cable and a mini HDMI to HDMI adapter to connect the monitor and BPI-M4 Zero, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Zero UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Zero, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Zero on the router management interface, or use the following command on the BPI-M4 Zero UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Zero is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Zero user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Zero in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Zero in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4zero:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Zero board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Zero.If it is a USB disk with a type-A plug, you also need a type-A to type-C adapter.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Zero Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, use an HDMI cable and a mini HDMI to HDMI adapter to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4zero:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4zero:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Zero in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

File:M4b audio switch.jpg

2024-01-22T03:37:31Z

Dangku:

Getting Started with BPI-M4 Berry

2024-01-22T03:36:34Z

Dangku: /* Switch Audio Output */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:Build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

: The default audio output channel is hdmi, switch it to jack output in Settings->Sound->Audio output channel

:[[File:m4b_audio_switch.jpg]]

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

Getting Started with BPI-M4 Berry

2024-01-22T03:33:11Z

Dangku: /* Install Play Store */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:Build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

===Switch Audio Output===

:

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

Getting Started with BPI-M4 Berry

2024-01-22T03:11:22Z

Dangku: /* Custom Logo */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

===Install Play Store===

:Build the android source code with OpenGApps google play include.

:1. Apply this patch to source code.
diff --git a/device/softwinner/apollo/common/opengapps/config.mk
b/device/softwinner/apollo/common/opengapps/config.mk
index 4c2a7f3..c7ff30e 100644
--- a/device/softwinner/apollo/common/opengapps/config.mk
+++ b/device/softwinner/apollo/common/opengapps/config.mk
@@ -1,4 +1,4 @@
-BOARD_BUILD_OPENGAPPS := false
+BOARD_BUILD_OPENGAPPS := true

ifeq ($(BOARD_BUILD_OPENGAPPS), true)
GAPPS_VARIANT := pico

:3. Create /vendor/opengapps folder

:4. Download [https://github.com/opengapps/aosp_build OpenGApps aosp_build] project to /vendor/opengapps/build

:5. Create /vendor/opengapps/sources folder, download [https://gitlab.opengapps.org/opengapps OpenGApps projects] to /vendor/opengapps/sources/

:6. Build the source code and flash image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

Getting Started with BPI-M4 Berry

2024-01-22T03:03:19Z

Dangku: /* Custom IR */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

Getting Started with BPI-M4 Berry

2024-01-22T03:03:04Z

Dangku: /* Build Android Source Code */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====

Getting Started with BPI-M4 Berry

2024-01-22T03:02:22Z

Dangku: /* Custom IR */

[[zh:快速上手_BPI-M4_Berry]]
[[File:Banana_Pi_BPI-M4_Berry_1.jpg|thumb|[[Banana Pi BPI-M4 Berry]] H618 design]]
[[File:Banana_pi_BPI-M2_Berry_5.JPG|thumb|[[Banana Pi BPI-M2 Berry]] A40i-H 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|[[Banana Pi BPI-M5]] with S905x3 design]]

=Development=

==Android==
===Prepare===

:1. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | Android image]].

:2. Download and Install [https://download.banana-pi.dev/d/ca025d76afd448aabc63/files/?p=%2FTools%2Fimage_download_tools%2Fphoenixsuit_V1.1.0_20150325.rar Allwinner Image Download Tools], PhoenixSuit is for window.

:3. Type-C cable, 5V power supply.

===Install Image with USB tool===

:1. Open PhoenixSuit, click the Firmware icon to switching to firmware download panel, then click Image button and choose the Android Image file.

:[[File:m4-berry_android_1.jpg]]
:[[File:m4-berry_android_2.jpg]]

:2. Press and hold the SW2 button on M4 Berry while connecting to the computer using type-c, popup a warning dialog.Press Yes.

:[[File:m4-berry_android_3.jpg]]

:3. Download

:[[File:m4-berry_android_4.jpg]]

:4. Download finish

:[[File:m4-berry_android_5.jpg]]

===Custom IR===
:Wiki images support NEC protocol default.

:1. Execute getevent -l | grep MSC_SCAN in the serial port or adb shell, then press the corresponding button on the remote control to obtain the device ID and scancode.

:[[File:m4b_custom_ir_1.jpg]]

:The MSC_SCAN data is 32 bits.
:Bits [31:24] represent the key press status, where 0 indicates release, and 1 indicates press.
:Bits [23:8] represent the device ID. Use this ID to generate a keylayout file named customer_ir_xxxx.kl. For example, in this case, it would be customer_ir_fe01.kl.
:Bits [7:0] represent the scancode.

:2. Based on the results of step one, create a new file named customer_ir_xxxx.kl with the following content:

:[[File:m4b_custom_ir_2.jpg]]

:Map the scancodes in the second column to Android keycodes.

:3. Use the adb command to push customer_ir_xxxx.kl to the system.

$ adb root
$ adb remount
$ adb push customer_ir_xxxx.kl /system/usr/keylayout/
$ adb reboot

:For source code porting, put the customer_ir_xxxx.kl to vendor/w/common/hardware/input/multi_ir/keylayout/ directory and build the source code.

===Build Android Source Code===

:Please read the source code [https://github.com/BPI-SINOVOIP/BPI-H618-Android12/blob/master/README.md README.md]

===Custom Logo===

:1. Boot logo

:Rename the logo file to bootlogo.bmp and put it in longan/device/config/chips/h618/boot-resource/boot-resource/ directory.

:2. Bootanimation logo

:Put bootanimation.zip to device/softwinner/apollo/common/media/bootanimation/ directory.

:3. Launcher logo for Box variant image

:Create a 270x110, 32 bit depth, png image and rename it to aw_logo.png, put it in vendor/aw/common/package/TVLauncher/res/drawable-xhdpi/ directory.

:Then build the source code and flash the image to your board.

==Linux==
===Prepare===
:1. Linux image support SDcard or EMMC bootup, and will boot from the SD card first.

:2. It’s recommended to use A1 rated cards, 8GB at least.

:3. Make sure bootable EMMC is formatted if you want bootup from SDcard.

:4. Make sure SDcard is formatted without Linux image flashed if you want bootup from EMMC and use Sdcard as storage.

:5. Download latest [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]], and confirm that the md5 checksum is correct.

:6. Default login: pi/bananapi or root/bananapi

:7. The wiki guide is only for [[Banana_Pi_BPI-M4_Berry#System_image | bananapi ubuntu/debian images]].

:8. USB-Serial (3.3V). Baud: 115200.

===Install Image to SDcard===
:1. Install Image with Balena 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]]

===Install Image to eMMC===

1. Make sure that the Linux image has been burned into an SD card and started normally.

2. Enter the following command in the terminal:
<pre>
sudo bananapi-config
</pre>

3. By default, select the first item continuously and press the Enter key to install the Linux system image on the eMMC.

:[[File:Bpi_m4_berry_mobaxterm_12.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_13.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_14.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_15.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_16.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_17.jpg]]
:[[File:Bpi_m4_berry_mobaxterm_18.jpg]]

4. The last step is to shut down the computer. At this time, disconnect the power supply, remove the SD card, and power on again to boot from eMMC.

===Erase eMMC===

1. Make sure the Linux image has been burned into an SD card and insert the SD card. By default it will boot from the SD card.

2. Enter the command lsblk in the terminal to list the block device information in the system, such as hard disks, partitions, disks, etc.

<pre>
pi@bpi-m4berry:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 7.4G 0 disk
└─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd
/
mmcblk1 179:32 0 7.3G 0 disk
└─mmcblk1p1 179:33 0 7.3G 0 part
mmcblk1boot0 179:64 0 4M 1 disk
mmcblk1boot1 179:96 0 4M 1 disk
zram0 252:0 0 993.2M 0 disk [SWAP]
zram1 252:1 0 50M 0 disk /var/log
zram2 252:2 0 0B 0 disk
</pre>

3. mmcblk0 is the SD card and mmcblk1 is the eMMC. Enter the following command in the terminal to erase the eMMC. This process takes several minutes and is irreversible. Be careful to back up important data.
<pre>
sudo dd if=/dev/zero of=/dev/mmcblk1
</pre>

===Ubuntu Desktop===

:1. Using the Ubuntu desktop version system image, you can get a graphical operation interface.
:2. You need to prepare a monitor with an HDMI interface and an HDMI cable.
:3. Use an HDMI cable to connect the monitor and BPI-M4 Berry, switch the monitor input interface to the corresponding HDMI interface, power on, and wait a moment to see the desktop.

[[File:Bpi_m4_berry_ubuntu_1.jpg]]

===Debug UART===
:1. Prepare a 3.3v USB to TTL module.
:2. Use the USB to TTL module to connect the PC USB port and the Debug UART port on the board.
:3. Open a serial terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:4. Taking mobaxterm as an example, after setting the serial port number and 115200 baud rate, you can open the BPI-M4 Berry UART terminal.

[[File:bpi_m4_berry_mobaxterm_1.jpg]]

[[File:bpi_m4_berry_mobaxterm_2.jpg]]

===SSH===
:1. Prepare a network cable and a router.
:2. Use a network cable to connect the LAN port of the router to the BPI-M4 Berry, and also connect the PC to another LAN port.
:3. Check the IP address of BPI-M4 Berry on the router management interface, or use the following command on the BPI-M4 Berry UART terminal to check the IP address.
ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::3e1f:688f:81ab:d8b7 prefixlen 64 scopeid 0x20<link>
ether 02:00:54:a0:d6:a6 txqueuelen 1000 (Ethernet)
RX packets 553 bytes 92549 (92.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 329 bytes 26023 (26.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
:4. Open an SSH terminal software on the PC, such as [https://mobaxterm.mobatek.net/ mobaxterm] or [https://www.putty.org/ putty].
:5. Taking mobaxterm as an example, fill in the obtained IP address, such as 192.168.3.10 above, in the IP address column and 22 in the Port port.

[[File:bpi_m4_berry_mobaxterm_3.jpg]]

:6. Open the SSH terminal and enter the login username/password: pi/bananapi or root/bananapi. There will be no prompt when entering the password. Please enter it normally and press Enter when finished.

[[File:bpi_m4_berry_mobaxterm_4.jpg]]

===NoMachine Remote Desktop===
:1. Make sure BPI-M4 Berry is connected to the Internet and use the following command to download the nomachine DEB installation package in the system.

wget https://download.nomachine.com/download/8.9/Arm/nomachine_8.9.1_1_arm64.deb

:2. Or open [https://downloads.nomachine.com/download/?id=117&distro=ARM NoMachine for ARM - arm64 download page] in a PC browser, download the DEB installation package, and then copy it to BPI-M4 Berry user directory through SSH or USB disk.

:3. After the download is completed, install it through the following command. Note that the file name is based on the actual downloaded file name.

sudo dpkg -i nomachine_8.9.1_1_arm64.deb

:4. PC side also needs to download and install NoMachine. [https://download.nomachine.com NoMachine download page] Select the installation package suitable for the PC operating system, download it locally and complete the installation.

:5. Pay attention to keeping the PC and BPI-M4 Berry in the same LAN. You can try SSH connection first to ensure normal communication within the LAN.

:6. Open NoMachine on the PC, click the Add button, enter the IP address of BPI-M4 Berry in the Host bar in the window after the jump, and then click the Add button.
[[File:Bpi_m4_berry_nomachine_1.jpg]]

:7. Click the recognized port icon, enter the username/password in the new window that pops up, and then click the OK button.
[[File:Bpi_m4_berry_nomachine_2.jpg]]
[[File:Bpi_m4_berry_nomachine_3.jpg]]

:8. After completing the subsequent settings, you can see the desktop.
[[File:Bpi_m4_berry_nomachine_4.jpg]]

:9. If no device is connected to the HDMI interface, the NoMachine remote desktop will display a black screen. It is recommended to keep the HDMI connection or connect an HDMI decoy device.

===WiFi===
: Use the nmcli command to scan WiFi hotspots, connect to hotspots, and create AP hotspots.

nmcli device #List devices
nmcli device wifi list # List available wifi access points, list can be omitted
nmcli device wifi connect [SSID] password [PASSWORD] # Connect to the hotspot mySSID. After the connection is successful, the configuration file will be automatically generated. If you want to connect again in the future, you can use the nmcli connection up [SSID] command.
nmcli device disconnect [device name] # Disconnect wifi, use the wifi device name displayed in the nmcli device command
nmcli device wifi hotspot con-name [NAME] ifname [device name] ssid [SSID] password [PASSWORD] # Create AP hotspot

nmcli connection show #List network connection configuration
nmcli connection down [NAME] # Deactivate a connection
nmcli connection up [NAME] # Activate a connection
nmcli connection delete [SSID] #Delete a configuration and no longer save information and automatically connect

nmcli radio wifi off # Turn off wifi
nmcli radio wifi on # Turn on wifi

:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli.html nmcli command reference document]
:* [https://developer-old.gnome.org/NetworkManager/unstable/nmcli-examples.html nmcli command reference examples]

===Set static IP, DNS===
:1. To set a static IP, you need to maintain the connection first. If you want to set an Ethernet static IP, you must first maintain the Ethernet connection; if you want to set a wireless network static IP, you must first maintain a connection to a WIFI.
:2. If the upper-level router has assigned the IP address you want to set to other devices, please change it to an idle IP, or ask other devices to give up the IP.
:3. Use the nmcli connection show command to display all connections, for example:
pi@bpi-m4berry:~$ nmcli connection show
NAME UUID TYPE DEVICE
TP-LINK_5G_7747 e4a49726-adf1-44d7-a621-0e3af96cc390 wifi wlx2cc3e6acd5d7
Wired connection 1 612eda94-55dc-3c85-b05e-f16c41775b4e ethernet --
:4. Use the nmcli connection show [NAME] command to display all the properties of a specific connection, such as:
nmcli connection show TP-LINK_5G_7747 #If you want to see Ethernet, change to Wired connection 1

#Only list three common items
ipv4.dns: 192.168.3.1 #The default is the gateway address
ipv4.addresses: 192.168.3.10/24 #The default is the IP address assigned by the router DHCP
ipv4.gateway: 192.168.3.1 #Gateway address, the default is the IP address of the router

:5.Set static IP:
nmcli connection modify TP-LINK_5G_7747 ipv4.addresses 192.168.3.2
:6.Set DNS:
nmcli connection modify TP-LINK_5G_7747 ipv4.dns 8.8.8.8 #Google DNS
:7.Reset:
reboot
:8. After restarting, check whether the modification is successful:
ifconfig
nmcli connection show TP-LINK_5G_7747

===Network time synchronization===
:Chrony is an open source free Network Time Protocol NTP client and server software. It allows the computer to keep the system clock synchronized with the clock server (NTP), thus allowing your computer to maintain accurate time. Chrony can also be used as a server software to provide time synchronization services for other computers.

timedatectl set-ntp false #Disable NTP-based network time synchronization

sudo apt install chrony #Install chrony
systemctl start chrony #Start chrony
systemctl enable chrony
systemctl status chrony
systemctl restart chrony #Restart service

timedatectl status #View time synchronization status
timedatectl list-timezones #View time zone list
timedatectl set-timezone Asia/Shanghai #Modify time zone
timedatectl set-ntp true #Enable NTP network time synchronization

date #View time
sudo hwclock -r #View hardware clock

:* [https://chrony-project.org/documentation.html Chrony reference documentation]

===View hardware temperature===
Enter the following command to view the temperature data returned by the sensor built into the chip on the BPI-M4 Berry board.
sensors

===Modify HDMI output resolution===
:When using the Ubuntu desktop operating system, you can find the Displays column in Settings and modify the resolution.

[[File:Bpi_m4_berry_ubuntu_2.jpg]]

===Use USB disk===
:1. Prepare a USB disk that has been partitioned normally and insert it into the USB interface of BPI-M4 Berry.
:2. In the Ubuntu desktop version, you can see that the USB disk has been recognized and can be opened in the file manager, or partition management can be performed through the GParted tool.

[[File:Bpi_m4_berry_ubuntu_3.jpg]]

:3. In the terminal, mount the USB disk to the local directory:
mkdir mnt #Create a separate directory in the ~/user directory for mounting for easy management
cat /proc/partitions | grep "sd*" #List partitions starting with sd
sudo mount /dev/sda1 ~/mnt/ #Mount /dev/sda1 to ~/mnt/
ls ~/mnt/ #After mounting, you can list the files in the USB disk
sudo umount -v /dev/sda1 #umount, then you can remove the USB disk

===Use Audio Devices===
: Prepare an audio file and copy it to the BPI-M4 Berry Ubuntu desktop system through a USB flash drive or SSH.
====HDMI audio====
:1. Prepare a monitor with HDMI audio input function, turn on the relevant functions in the monitor settings, and use an HDMI cable to connect the monitor.
:2. Set the output device to HDMI Audio in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_4.jpg]]
:3.Play audio.
[[File:Bpi_m4_berry_ubuntu_5.jpg]]

====3.5mm audio jack====
:1. Prepare a headset or other audio device that uses a 3.5mm plug, insert the plug into the 3.5mm jack of BPI-M4 Berry.
:2. Set the output device to Audio Codec in the Sound column of the settings.
[[File:Bpi_m4_berry_ubuntu_6.jpg]]
:3. Play audio.

====Terminal command to play audio files====
<pre>
aplay -l #List devices
aplay -D hw:0,0 [path] #Play the audio file of the specified path
</pre>

===Use Bluetooth===
:1. Open settings in the Ubuntu desktop and connect a Bluetooth device, such as a Bluetooth mouse or keyboard, in the Bluetooth bar.
[[File:Bpi_m4_berry_ubuntu_7.jpg]]
:2. The method to connect the Bluetooth device through the command line in the terminal is as follows:
<pre>
pi@bpi-m4berry:~$ sudo bluetoothctl #Open the Bluetooth device management tool
[sudo] password for pi:
Agent registered
[CHG] Controller 2C:C3:E6:AC:D5:D8 Pairable: yes
[bluetooth]# power on #Start the Bluetooth function, power off to turn it off
Changing power on succeeded
[bluetooth]# discoverable on #Allow this device to be discovered
Changing discoverable on succeeded
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discoverable: yes
[bluetooth]# pairable on #Allow device pairing
Changing pairable on succeeded
[bluetooth]# scan on #Start scanning
Discovery started
[CHG] Controller 2C:C3:E6:AC:D5:D8 Discovering: yes
[NEW] Device D4:C4:85:A5:C6:B1 Logitech Pebble #The MAC address and device name of a Bluetooth mouse
[CHG] Device D4:C4:85:A5:C6:B1 TxPower: 4
[bluetooth]# pair D4:C4:85:A5:C6:B1 #Pair the MAC address of the Bluetooth device you want to connect to
Attempting to pair with D4:C4:85:A5:C6:B1
[CHG] Device D4:C4:85:A5:C6:B1 Connected: yes
[DEL] Device A4:C1:38:9B:F6:FD SLPO20N20200059
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D4:C4:85:A5:C6:B1 UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D4:C4:85:A5:C6:B1 ServicesResolved: yes
[CHG] Device D4:C4:85:A5:C6:B1 Paired: yes
Pairing successful #pairing successfully
[CHG] Device D4:C4:85:A5:C6:B1 Modalias: usb:v046DpB021d0007
[bluetooth]# exit #Exit the Bluetooth device management tool
pi@bpi-m4berry:~$
</pre>

:[https://wiki.archlinux.org/title/bluetooth archlinux bluetooth reference document]

===Use IR Receiver===
:1. You need to prepare an infrared remote control using NEC format.
:2. Enter the following command in the terminal to start receiving infrared signals.
sudo ir-keytable -c -p NEC -t

Old keytable cleared
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
258.553895: lirc protocol(nec): scancode = 0x45
258.553926: event type EV_MSC(0x04): scancode = 0x45
258.553926: event type EV_SYN(0x00).
260.667648: lirc protocol(nec): scancode = 0x46
260.667671: event type EV_MSC(0x04): scancode = 0x46
260.667671: event type EV_SYN(0x00).
260.719552: lirc protocol(nec): scancode = 0x46 repeat
260.719568: event type EV_MSC(0x04): scancode = 0x46
260.719568: event type EV_SYN(0x00).
273.263728: lirc protocol(nec): scancode = 0x47
273.263753: event type EV_MSC(0x04): scancode = 0x47
273.263753: event type EV_SYN(0x00).
273.315591: lirc protocol(nec): scancode = 0x47 repeat
273.315608: event type EV_MSC(0x04): scancode = 0x47
273.315608: event type EV_SYN(0x00).

For other commands and specific application methods, please see [https://manpages.ubuntu.com/manpages/focal/en/man1/ir-keytable.1.html ir-keytable reference document]

===Transfer files===
====scp====
scp (secure copy) command in Linux system is used to copy file(s) between servers in a secure way.

The SCP command or secure copy allows the secure transferring of files between the local host and the remote host or between two remote hosts.

It uses the same authentication and security as it is used in the Secure Shell (SSH) protocol.

You can copy files from a Windows terminal to a Linux system on the same LAN. Just make sure the Open SSH client is turned on and can be viewed in Settings > Applications > Optional Features.

If you want to copy files from Windows systems to Linux systems, you also need to enable the Open SSH server.
:[[File:Bpi_m4_berry_mobaxterm_6.jpg]]

The scp command format is:

:<pre>scp [optionals] file_source file_target</pre>
::1.<nowiki>[optionals]</nowiki> is an optional parameter, such as -r, which can be used to copy the entire directory recursively.

::2.file_source The file or directory to be copied.

::3.file_target will copy the past path and rename it if a specific file name is entered at the end.

Take copying local files from a Windows system to a Linux system as an example. In the Windows terminal, enter:
:<pre>PS D:\temp\temp_4> scp ".\hello.txt" pi@192.168.3.12:"/home/pi/Downloads/"</pre>

You can also copy files in the Linux system to the local computer in the Windows terminal:
:<pre>PS D:\temp\temp_4> scp pi@192.168.3.12:"/home/pi/Downloads/hello.txt" "D:\temp\temp_4"</pre>
:: Where pi@192.168.3.12 is the user name in the Linux system and the IP address of the BPI-M4 Berry in the LAN.
:: Where <nowiki>:"/home/pi/Downloads/hello.txt"</nowiki> is the file path in the Linux system.
:: Where "D:\temp\temp_4" is the path in Windows system.

[https://www.geeksforgeeks.org/scp-command-in-linux-with-examples/ scp reference document]

====mobaxterm====
Files can be managed through a graphical interface using mobaxterm or other similar software.
:[https://mobaxterm.mobatek.net/download.html mobaxterm download]
:[https://download.mobatek.net/mobaxterm-on-linux.html mobaxterm-linux preview version]

As shown in the figure below, after establishing an SSH connection in mobaxterm, a file management window will appear on the left side of the interface, which supports copying and pasting by dragging and dropping files.
:[[File:Bpi_m4_berry_mobaxterm_7.jpg]]

===40 pin interface GPIO, I2C, UART, SPI, and PWM testing===
====GPIO====
Control the GPIO port to light up the LED light.

'''Set the high and low levels of GPIO'''

:[[File:M4_Berry_gpio.jpg]]

The following is a demonstration using 7 pin.

Insert the LED light and you can see that it is not lit up.

:[[File:M4_Berry_gpio_led_1.jpg]]

: 1.Execute
gpio mode 2 out
:to set it to output mode.

: 2.Execute
gpio write 2 1
:You can see that the LED light has been turned on.
:[[File:M4_Berry_gpio_led_2.jpg]]

: 3.Execute
gpio write 2 0
:You can see that the LED light has been turned off.
:[[File:M4_Berry_gpio_led_1.jpg]]

'''Set pull-up and pull-down resistors'''
: 1.Firstly, it is necessary to set the GPIO port to input mode
gpio mode 2 in

: 2.Then set the GPIO port as an pull-up resistor
gpio mode 2 up
:The LED light is lit up again
:[[File:M4_Berry_gpio_led_1.jpg]]

: 3.Finally, set the GPIO port to dropdown mode
gpio mode 2 down
:The LED light goes out again
:[[File:M4_Berry_gpio_led_2.jpg]]

====I2C====

According to the schematic diagram, the available i2cs are i2c3 and i2c4
:[[File:M4_Berry_gpio_i2c.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "pg-i2c3"and"pg-i2c4"
:[[File:M4_Berry_bananapi_config_i2c.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are i2c-3 and i2c-4 nodes.
pi@bpi-m4berry:~$ ls /dev/i2c-3
/dev/i2c-3
pi@bpi-m4berry:~$ ls /dev/i2c-4
/dev/i2c-4

: 8. Execute

cd /usr/src/wiringPi/examples/
gcc ./oled_demo.c -o oled -lwiringPi

: 9.Connect the i2c device to the pin of i2c3. Execute

sudo ./oled /dev/i2c-3

:[[File:M4_Berry_i2c_3_led.jpg]]

: 10.Connect the i2c device to the pin of i2c4. Execute

sudo ./oled /dev/i2c-4

:[[File:M4_Berry_i2c_4_led.jpg]]

====UART====
By reviewing the schematic, it can be found that the available uart are uart1 and uart5.
:[[File:M4_Berry_gpio_uart.png]]

: 1.Uart1 and Uart5 is closed by default and needs to be opened. Execute
sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.If you want to use uart1,select"pg-uart1".If you want to use uart5,select"ph-uart5"
:[[File:M4_Berry_bananapi_config_uart.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are ttyS5 nodes.
pi@bpi-m4berry:~$ ls /dev/ttyS5
/dev/ttyS5

: 8:Short circuit uart1 pin or uart5 and execute
gpio serial /dev/ttyS1
:[[File:M4_Berry_gpio_uart1.jpg]]
:[[File:M4_Berry_gpio_uart5.jpg]]

====SPI====
By reviewing the schematic, it can be found that the available spi is spi1.
:[[File:M4 Berry-sch-gpio-spi.png]]

: 1.Execute

sudo bananapi-config

: 2.Select "System"
:[[File:M4 Berry-bananapi-config-1.jpg]]

: 3.Select "Hardware"
:[[File:M4 Berry-bananapi-config-2.jpg]]

: 4.Use the keyboard directional keys to move, then use the spacebar to select.Select "spi1-cs1-spidev"
:[[File:M4 Berry-bananapi-config-spi.jpg]]

: 5.Select "Save", then select "Back"
:[[File:M4 Berry-bananapi-config-3.jpg]]

: 6.Finally, choose Reboot.
:[[File:M4 Berry-bananapi-config-4.jpg]]

: 7.After restarting, check if there are SPI nodes.
pi@bpi-m4berry:~$ ls /dev/spidev1.1
/dev/spidev1.1

: 8.Execute

sudo spidev_test -v -D /dev/spidev1.1

:[[File:M4 Berry-bananapi-config-spi-1.jpg]]

:It can be seen that TX and RX are different. So, we need to short-circuit MOSI and MISO and execute the command again.

:[[File:M4 Berry-bananapi-config-spi-2.jpg]]

====PWM====