Search the Community

Hello guys, i'm trying to connect that ili9341 display with my m2 zero but it wont work. My armbian Version: Armbian_23-02-0-trunk_Bananapim2zero_lunar_edge_6.1.11_xfce_desktop The display has a pinout that matches with the raspberry pi, so also the banana pi m2 zero would do the job, since it has the same pinout like the raspberry pi has. It uses 26 pins to connect to the banana pi m2 zero gpio output pins. 3 buttons and a touch panel are available but i only want to use the lcd for now. I edited the armbianEnv.txt to open the spi port and added my overlay tft.dts to /boot/overlay-user but i cant get a picture on the screen, Its just glowing white. Am I missing something? Are my gpios numbers in the overlay correct? do i have to install additional software? I would be very happy for tips or help! My armbianEnv.txt : verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=39f6ab06-e14f-4885-8454-717c5405f006 rootfstype=ext4 overlays=cpu-clock-1.2GHz-1.3v spi-spidev param_spidev_spi_bus=0 user_overlays=tft usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u My overlay tft.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragmen@0 { target = <&pio>; __overlay__ { display_pins: display_pins { pins = "PC0", "PC3"; function = "gpio_out"; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; display: display@0 { compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&display_pins>; spi-max-frequency = <16000000>; rotation= <270>; bgr; fps = <10>; buswidth = <8>; height = <240>; width = <320>; reset-gpios = <&pio 0 25 0>; /* GPIOA 6 */ dc-gpios = <&pio 0 24 0>; /* GPIOA 3 */ debug = <3>; }; }; }; __overrides__ { rotation = <&display>, "rotation:0"; fps = <&display>, "fps:0"; debug = <&display>, "debug:0"; }; };

Hello, im trying to map the i2c-2 to some GPIO ports and have to rewrite the device-tree on armbian 22.04. I'm failing miserably and have no idea how-to do it. I managed to compile the i2c-gpio.ko kernel module as it is not part of the armbian 5.15.89-sunxi kernel. However, here i'm stuck and cant manage to make it happen. On RPi it was simple adding an overlay to config.txt: dtoverlay=i2c-gpio,bus=2,i2c_gpio_sda=27,i2c_gpio_scl=17 /boot/overlays/i2c-gpio.dtbo I'm trying to replicate that for Armbian, here is my dts file: // Overlay for i2c_gpio bitbanging host bus. /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/"; __overlay__ { i2c_gpio: i2c@2 { reg = <0>; compatible = "i2c-gpio"; gpios = <&pio 17 0 /* sda */ &pio 27 0 /* scl */ >; i2c-gpio,delay-us = <2>; #address-cells = <1>; #size-cells = <0>; }; }; }; fragment@1 { target-path = "/aliases"; __overlay__ { i2c_gpio = "/i2c@2"; }; }; fragment@2 { target-path = "/__symbols__"; __overlay__ { i2c_gpio = "/i2c@2"; }; }; __overrides__ { i2c_gpio_sda = <&i2c_gpio>,"gpios:4"; i2c_gpio_scl = <&i2c_gpio>,"gpios:16"; i2c_gpio_delay_us = <&i2c_gpio>,"i2c-gpio,delay-us:0"; bus = <&i2c_gpio>, "reg:0"; }; }; What am I doing wrong?

Hi All, I am trying to enable HID gadget on Banana Pi M2 Zero with latest Armbian OS for it. I followed the instructions in following link,but no luck: Switch USB port from OTG to HOST mode I get modprobe: ERROR: could not insert 'g_hid': No such device when I enter modprobe g_hid. I appreciate any help. Thanks

I don’t own banana pi but I’m thinking of buying it for the project we’re going to do. I have raspberry pi zero but mediapipe is not working. Can I install this library on m2 zero? I would be glad if you help. Thank you.

I don't own banana pi but I'm thinking of buying it for the project we're going to do. I have raspberry pi zero but mediapipe is not working. I'm thinking of doing image manipulation and this is the most important library in my code. That's why I'm trying to do a detailed research because my budget is limited. Thank you for your help 💯

About 6 months ago I started a music project with the Raspberry PI Zero 2W. The project is a module to generate weird and wonderful drone music/sounds (example here) Because of the fact that it's nearly impossible to got hold of the Raspberry PI Zero 2W, I want to "port" the project to an alternative and available board with the same footprint and pinout; the BPI M2 Zero would be perfect. I have quite a challenge though; See image: The exact setup below with an Raspberry PI Zero 2W (O/S: Bullseye 11) and the install procedure described here, runs absolutely fine --- but now I want this setup to run on the BPI M2 Zero (O/S: "Armbian_20.05.1_Bananapim2zero_buster_current_5.4.43_desktop" downloaded from here) I appreciate that the BPI M2 Zero has a different architecture - but I guess with the lack of support (compared to the Raspberry PI) I can't figure out how to get this setup running. Has anyone got experience getting the two boards "talking" ? I need the setup to be the same as I already have the PCBs produced you see. I haven't seen a Armbian version of Bullseye 11 ... but I don't think it's absolutely necessary to have the same O/S. I guess what matters is that the Audio's board install-script (curl https://get.pimoroni.com/phatdac | bash) is re-worked to run on the BPI M2 Zero. I am willing to offer a financial incentive for your time (ping me).

I'm using Banana Pi M2 Zero with Armbian Debian GNU/Linux 10 (Buster). Compiled the image myself with the latest source code using the armbin/build repository. I want to be able to do serial communication on pins 8 and 10. I'm looking for something to appear at /dev/ttyAMA0, so I can communicate with it. I saw some other forum posts which mentioned it'll happen on /dev/ttyS0 , however even that is not happening. The serial communication is working via FTDI (using the USB side connected to the Banana Pi), which indicates there is no problem with the other device. This is what the configuration looks like using "sudo minicom -s". +-----------------------------------------------------------------------+ | A - Serial Device : /dev/ttyS0 | | B - Lockfile Location : /var/lock | | C - Callin Program : | | D - Callout Program : | | E - Bps/Par/Bits : 115200 8N1 | | F - Hardware Flow Control : No | | G - Software Flow Control : No | | | | Change which setting? | +-----------------------------------------------------------------------+ | Screen and keyboard | | Save setup as dfl | | Save setup as.. | | Exit | | Exit from Minicom | +--------------------------+ I have enabled "uart1" using "sudo armbian-config -u" -> System -> Hardware. Connecting Rx, Tx on the pins 8 and 10 also does not show up in "dmesg" How do I go about debugging the issue or finding the root cause of the problem? Many thanks!

Hi, I am stuck integrating IR in my board banana pi m2 zero. Can anyone guide me to setup IR?

Hi, so without knowing what the swappiness actually is I changed the value from 100 to 512. Since then, I can't boot my Banana Pi M2 Zero. Shortly after that, I remembered again: swappiness is the percentage of how often to use swap and not the maximum amount of storage. Can I repair it inside uboot? Can I plug the sd card into my PC and edit the files there? Here is the log from the serial console. It's stuck forever after the last line. .............................................................. U-Boot SPL 2020.10-armbian (Nov 23 2020 - 15:48:18 +0100) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2020.10-armbian (Nov 23 2020 - 15:48:18 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Banana Pi BPI-M2-Zero DRAM: 512 MiB MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3967 bytes read in 4 ms (967.8 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 262 bytes read in 3 ms (85 KiB/s) 11504321 bytes read in 963 ms (11.4 MiB/s) 7793968 bytes read in 652 ms (11.4 MiB/s) Found mainline kernel configuration 33363 bytes read in 12 ms (2.7 MiB/s) 788 bytes read in 11 ms (69.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo 502 bytes read in 10 ms (48.8 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart1.dtbo 502 bytes read in 11 ms (43.9 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart3.dtbo 4185 bytes read in 11 ms (371.1 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11504257 Bytes = 11 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49507000, end 49fffa81 ... OK Loading Device Tree to 49496000, end 49506fff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Thanks

I got myself a Banana Pi M2 Zero (with H3 chip) and am running Armbian (Armbian_21.08.1_Bananapim2zero_buster_current_5.10.60) on it. I have enabled SPI by adding the spi-spidev dt overlay. Now I want to use both CS pins at the same time so that I can connect two devices. The spi-add-cs1 overlay doesn't change anything so I researched a bit and found this custom overlay. Unfortunately it didn't work too and there is still only a single spidev available. Is there any way to enable both of them at the same time?

Hi forum members, the apt utility in my bpi m2 zero can't find neither dnsutil nor bind9-dnsutil for bullseye, here the output: pi@fewo-relais:~$ sudo apt install bind9-dnsutils Paketlisten werden gelesen… Fehler! E: Encountered a section with no Package: header E: Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_binary-armhf_Packages E: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden. pi@fewo-relais:~$ pi@fewo-relais:~$ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapim2zero BOARD_NAME="Banana Pi M2 Zero" BOARDFAMILY=sun8i BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=735eff9 DISTRIBUTION_CODENAME=bullseye DISTRIBUTION_STATUS=csc VERSION=21.08.0-trunk LINUXFAMILY=sunxi ARCH=arm IMAGE_TYPE=user-built BOARD_TYPE=csc INITRD_ARCH=arm KERNEL_IMAGE_TYPE=Image BRANCH=current Can someone help how to update the repository to have also bind9-dnsutils included ? Regards wollik

Upgrading to the latest Armbian build 5.15.25 on the M2-Zero has caused the camera to stop working. I had a build from https://github.com/Qengineering/BananaPi-M2-Zero-OV5640, and ive seen my camera work with Gstreamer but i now need it to use the hardware encoding. So i used https://wvthoog.nl/nanopi-ov5640-camera/ to enable the Cedrus encoder, but upgrading the devices loses the camera and /video1. There is no /video1, or media1. Ive tried to edit the dts files, build and push them but no luck. Any advice here would be good. I know there are a few topics on here on this subject, but they are all slightly different issues because of the kernel used.

I cannot compile this module - https://github.com/uboborov/sunxi-cedar-mainline I get this: root@bananapim2zero:/usr/src/sunxi-cedar-mainline# make arch=ARM KERNEL_SOURCE=../linux-source-5.10.60-sunxi make -C ../linux-source-5.10.60-sunxi M=/usr/src/sunxi-cedar-mainline modules make[1]: Entering directory '/usr/src/linux-source-5.10.60-sunxi' MODPOST /usr/src/sunxi-cedar-mainline/Module.symvers ERROR: modpost: "arm_copy_to_user" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "arm_copy_from_user" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "kmem_cache_alloc_trace" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "arm_heavy_mb" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "__aeabi_unwind_cpp_pr1" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "_raw_spin_unlock_irqrestore" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "_raw_spin_lock_irqsave" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "__aeabi_unwind_cpp_pr0" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! ERROR: modpost: "__gnu_mcount_nc" [/usr/src/sunxi-cedar-mainline/cedar_ve.ko] undefined! make[2]: *** [scripts/Makefile.modpost:124: /usr/src/sunxi-cedar-mainline/Module.symvers] Error 1 make[2]: *** Deleting file '/usr/src/sunxi-cedar-mainline/Module.symvers' make[1]: *** [Makefile:1728: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-source-5.10.60-sunxi' make: *** [Makefile:18: default] Error 2 I've done: make scripts sudo make modules_prepare

I am trying to configure my Banana Pi M2 Zero to use UART to communicate with my 3D Printer. I used Armbian config to setup UART 3 (Pins 8 & 10). I can't seem to communicate over the port. How do I test and do I need to make other config changes? Thank you!

Hi All, I''m using a BPI M2 Zero, where a 100 MBit ethernet Interface is implemented on the board. Since I'm using DHCP for this interface, I found that the MAC Address of this eth0 interface changes on every boot. The MAC Address of the wlan0 interface is permanent and don't changes during boots. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Di 30. Jun xx:xx:xx CEST 2020 Debian GNU/Linux 10 (buster) 5.4.45-sunxi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 17:42:11 up 25 min, 2 users, load average: 0,00, 0,00, 0,05 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 8a:aa:ea:69:67:50 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:46:04 up 0 min, 2 users, load average: 2,48, 0,70, 0,24 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 5e:af:c0:93:75:72 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:47:07 up 0 min, 2 users, load average: 1,92, 0,44, 0,14 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 56:e7:62:af:35:55 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) 17:48:23 up 0 min, 2 users, load average: 1,69, 0,39, 0,13 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 96:57:7c:ed:85:e0 txqueuelen 1000 (Ethernet) wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether cc:b8:a8:a9:bc:8e txqueuelen 1000 (Ethernet) Is there a way to set the MAC address of the eth0 interface to a fix value ? Regards WolliK

Hey, I am using the Image from the Armbian Download site: Armbian_20.11.6_Bananapim2zero_bullseye_current_5.10.4 and I am trying to get SPI to work, enabled it using armbian-config and through editing the /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=034edbda-9395-4820-87a1-f3a83bad8a58 rootfstype=ext4 overlays=spi-spidev usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But after a reboot it does not show in /dev/ (what seems odd, i2c-0 shows in /dev/ even though it is not enabled in the armbianEnv.txt) As far as I understand it, the dts for h3 should be the same for h2+ ? I also found a file called "sun8i-h2-plus-bananapi-m2-zero.dtb" under /boot/dtb after some research I found out that this is a device tree binary (thats also why I cant read it) but I couldn't find any information on how to use it. Or how I could replace the spi-spidev.dtd with this h2 one. I also already tried the focal_current_5.10.4 Image same result. Thanks in advance Lukas

Greetings, Some time ago, I built armbian with kernel 5.4.51. I applied a patch to two dts files that allowed for the OV5640 camera to work. By "work", I mean /dev/video0 was present in the system and /dev/media0 was also present. I could set camera parameters with media-ctl pointing to /dev/media0. Now, I've updated, and using a legacy kernel, 5.4.65, I cannot reproduce this. I've applied the same dts changes, but upon booting this image /dev/media0 is missing. I've compared the two kernel configurations, and there are very minimal differences: # diff config-5.4.51-sunxi /boot/config-5.4.65-sunxi 3c3 < # Linux/arm 5.4.51 Kernel Configuration --- > # Linux/arm 5.4.65 Kernel Configuration 2116d2115 < # CONFIG_BLK_DEV_SR_VENDOR is not set 2644a2644 > # CONFIG_RTL8192EU is not set 3165a3166 > CONFIG_SPI_DYNAMIC=y likewise, comparing loaded modules shows me that on my 5.4.65 build ov5640 is not in use: Module Size Used by ov5640 28672 0 On my 5.4.51 build, it is in use. I'm not sure where to go from here.

Environment: (H2+) + linux-sunxi + ov5640 It can be registered by kernel ,but I can't capture any picture from camera . Here is my kernel demsg: ===================================================================================== # dmesg |grep VFE [ 1.720292] [VFE]cci probe start cci_sel = 0! [ 1.720328] [VFE]cci probe end cci_sel = 0! [ 1.720359] [VFE]cci_init end [ 1.720372] [VFE]Welcome to Video Front End driver [ 1.720514] [VFE_DEBUG]vfe_probe [ 1.720638] [VFE]pdev->id = 0 [ 1.720644] [VFE]dev->mipi_sel = 0 [ 1.720650] [VFE]dev->vip_sel = 0 [ 1.720655] [VFE]dev->isp_sel = 0 [ 1.720662] [VFE_DEBUG]fetch sys_config1 [ 1.720670] [VFE_DEBUG]dev->ccm_cfg[0] = d70a0508 [ 1.720678] [VFE_DEBUG]dev->ccm_cfg[1] = d70a0814 [ 1.720690] [VFE_DEBUG]vip0 vip_dev_qty=1 [ 1.720698] [VFE_DEBUG]vip0 vip_define_sensor_list=0 [ 1.720759] [VFE_DEBUG]fetch vip_dev0_flash_en from sys_config failed [ 1.720773] [VFE_DEBUG]fetch vip_dev0_flash_mode from sys_config failed [ 1.720785] [VFE_DEBUG]fetch vip_dev0_af_pwdn from sys_config failed [ 1.720803] [VFE_DEBUG]dev->ccm_cfg[0]->ccm = ov5640 [ 1.720812] [VFE_DEBUG]dev->ccm_cfg[0]->twi_id = 2 [ 1.720821] [VFE_DEBUG]dev->ccm_cfg[0]->i2c_addr = 78 [ 1.720828] [VFE_DEBUG]dev->ccm_cfg[0]->is_isp_used = 1 [ 1.720835] [VFE_DEBUG]dev->ccm_cfg[0]->is_bayer_raw = 1 [ 1.720843] [VFE_DEBUG]dev->ccm_cfg[0]->vflip = 0 [ 1.720850] [VFE_DEBUG]dev->ccm_cfg[0]->hflip = 0 [ 1.720858] [VFE_DEBUG]dev->ccm_cfg[0]->iovdd_str = [ 1.720865] [VFE_DEBUG]dev->ccm_cfg[0]->avdd_str = [ 1.720872] [VFE_DEBUG]dev->ccm_cfg[0]->dvdd_str = [ 1.720879] [VFE_DEBUG]dev->ccm_cfg[0]->afvdd_str = [ 1.720887] [VFE_DEBUG]dev->ccm_cfg[0]->act_used = 1 [ 1.720894] [VFE_DEBUG]dev->ccm_cfg[0]->act_name = ad5820_act [ 1.720902] [VFE_DEBUG]dev->ccm_cfg[0]->act_slave = 0x18 [ 1.726942] [VFE_WARN]vfe vpu clock is null [ 1.726950] [VFE_DEBUG]get io resource num = 3 [ 1.726958] [VFE_DEBUG]get resource, name = csi [ 1.726970] [VFE_DEBUG]dev->regs.csi_regs = f1cb0000 [ 1.726977] [VFE_DEBUG]get resource, name = isp [ 1.726986] [VFE_DEBUG]dev->regs.isp_regs = f1cb8000 [ 1.915506] [VFE_DEBUG]isp load paddr = 5890a000 [ 2.011208] [VFE_DEBUG]isp load dma_addr = 1890a000 [ 2.041942] [VFE_DEBUG]isp load addr = d890a000 [ 2.046967] [VFE_DEBUG]isp saved paddr = 5890b000 [ 2.052205] [VFE_DEBUG]isp saved dma_addr = 1890b000 [ 2.057710] [VFE_DEBUG]isp saved addr = d890b000 [ 2.062843] [VFE_DEBUG]get irq resource [ 2.067119] [VFE_DEBUG]clock resource [ 2.071223] [VFE_DEBUG]vfe core clk = 600000000 [ 2.076259] [VFE_DEBUG]get pin resource [ 2.087109] [VFE]..........................vfe clk open!....................... [ 2.095253] [VFE_DEBUG]vfe dphy clock is null [ 2.100104] [VFE_DEBUG]vfe mipi csi clock is null [ 2.109647] [VFE]vfe_init end [ 2.112973] [VFE]probe_work_handle start! [ 2.117425] [VFE_DEBUG]v4l2_device_register [ 2.130426] [VFE_DEBUG]v4l2 subdev register [ 2.188045] [VFE]v4l2 subdev register input_num = 0 [ 2.193475] [VFE]vfe sensor detect start! input_num = 0 [ 2.199280] [VFE_WARN]Camer detect "YUV" fmt is different from sys_config! [ 2.206924] [VFE_WARN]Apply detect fmt = 0 replace sys_config fmt = 1! [ 2.214300] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" ! [ 2.231983] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start! [ 2.307854] [VFE_DEBUG]ccm_cfg pt = d70a0508 [ 2.312611] [VFE_DEBUG]ccm_cfg->sd = (null) [ 2.317449] [VFE_DEBUG]module vflip = 0 hflip = 0 [ 2.322678] [VFE_DEBUG]module vflip_thumb = 0 hflip_thumb = 0 [ 2.329052] [VFE_DEBUG]module is_isp_used = 1 is_bayer_raw= 0 [ 2.335444] [VFE_ERR]Error registering v4l2 subdevice No such device! [ 2.342605] [VFE_WARN]vfe sensor register check error at input_num = 0 [ 2.349853] [VFE_DEBUG]dev->ccm_cfg[0] = d70a0508 [ 2.355092] [VFE_DEBUG]dev->ccm_cfg[0]->sd = (null) [ 2.360710] [VFE_DEBUG]dev->ccm_cfg[0]->power.iovdd = (null) [ 2.367186] [VFE_DEBUG]dev->ccm_cfg[0]->power.avdd = (null) [ 2.373575] [VFE_DEBUG]dev->ccm_cfg[0]->power.dvdd = (null) [ 2.379949] [VFE_DEBUG]dev->ccm_cfg[0]->power.afvdd = (null) [ 2.386813] [VFE]V4L2 device registered as video2 [ 2.392083] [VFE]..........................vfe clk close!....................... [ 2.400332] [VFE_DEBUG]vfe dphy clock is null [ 2.405166] [VFE_DEBUG]vfe mipi csi clock is null [ 2.410397] [VFE]probe_work_handle end! =============================================================================================== But there are many error when I capture picture from camera. =============================================================================================== # fswebcam -d /dev/video2 --no-banner -r 320x240 capture.jpg --- Opening /dev/video2... [ 1805.085820] [VFE]vfe_open Trying source module v4l2...[ 1805.091463] [VFE]..........................vfe clk open!....................... [ 1805.102490] [VFE_DEBUG]vfe dphy clock is null [ 1805.107797] [VFE_DEBUG]vfe mipi csi clock is null [ 1805.113473] [VFE_DEBUG]tasklet init ! [ 1805.117708] [VFE]vfe_open ok [ 1805.121105] [VFE_ERR]input index(0) > dev->dev_qty(1)-1 invalid!, device_valid_flag[0] = 0 /dev/video2 opened. No [ 1805.130706] [VFE]vfe_close input was specified, using the f[ 1805.136267] [VFE]vfe select input flag = 0, s_input have not be used . irst. Unable to query [ 1805.146328] [VFE]..........................vfe clk close!....................... input 0. VIDIOC_ENUMIN[ 1805.157302] [VFE_DEBUG]vfe dphy clock is null PUT: Invalid argument [ 1805.164902] [VFE_DEBUG]vfe mipi csi clock is null [ 1805.172467] [VFE]vfe_close end ================================================================================================= How can I fix it ?

Hello, I have a GPIO pin that is high when starting the board. I am trying to force it low. Taking a look at gpio readall +-----+-----+---------+------+---+---Pi ?---+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 12 | 8 | SDA.1 | ALT5 | 0 | 3 || 4 | | | 5v | | | | 11 | 9 | SCL.1 | ALT5 | 0 | 5 || 6 | | | 0v | | | | 6 | 7 | GPIO. 7 | ALT3 | 0 | 7 || 8 | 0 | ALT3 | TxD | 15 | 13 | | | | 0v | | | 9 || 10 | 0 | ALT3 | RxD | 16 | 14 | | 1 | 0 | GPIO. 0 | ALT3 | 0 | 11 || 12 | 0 | ALT3 | GPIO. 1 | 1 | 16 | | 0 | 2 | GPIO. 2 | ALT3 | 0 | 13 || 14 | | | 0v | | | | 3 | 3 | GPIO. 3 | ALT3 | 0 | 15 || 16 | 0 | ALT3 | GPIO. 4 | 4 | 15 | | | | 3.3v | | | 17 || 18 | 0 | ALT3 | GPIO. 5 | 5 | 68 | | 64 | 12 | MOSI | ALT3 | 0 | 19 || 20 | | | 0v | | | | 65 | 13 | MISO | ALT3 | 0 | 21 || 22 | 0 | ALT3 | GPIO. 6 | 6 | 2 | | 66 | 14 | SCLK | ALT3 | 0 | 23 || 24 | 0 | ALT3 | CE0 | 10 | 67 | | | | 0v | | | 25 || 26 | 0 | ALT3 | CE1 | 11 | 71 | | 19 | 30 | SDA.0 | ALT3 | 0 | 27 || 28 | 0 | ALT3 | SCL.0 | 31 | 18 | | 7 | 21 | GPIO.21 | OUT | 1 | 29 || 30 | | | 0v | | | | 8 | 22 | GPIO.22 | ALT3 | 0 | 31 || 32 | 0 | ALT3 | GPIO.26 | 26 | 354 | | 9 | 23 | GPIO.23 | ALT3 | 0 | 33 || 34 | | | 0v | | | | 10 | 24 | GPIO.24 | ALT3 | 0 | 35 || 36 | 0 | ALT3 | GPIO.27 | 27 | 356 | | 17 | 25 | GPIO.25 | ALT3 | 0 | 37 || 38 | 0 | ALT3 | GPIO.28 | 28 | 21 | | | | 0v | | | 39 || 40 | 0 | ALT3 | GPIO.29 | 29 | 20 | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+---Pi ?---+---+------+---------+-----+-----+ it can be seen the following line is active: +-----+-----+---------+------+---+---Pi ?---+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | 7 | 21 | GPIO.21 | OUT | 1 | 29 || 30 | | | 0v | | | I've tried to force it off, but doesn't seem to work: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { poweroff_pins:poweroff_pins { allwinner,pins = "PA7"; allwinner,function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { poweroff: poweroff { compatible = "gpio-poweroff"; gpios = <&pio 0 7 1>; }; }; }; }; Is this the wrong approach? Thanks!

Greetings, I've been building an image for a banana pi m2-zero. I noticed during the build that the following DTS is chosen: sun8i-h3-orangepi-zero-plus2.dt There is a sun8i-h2-plus-bananapi-m2-zero.dts in the same directory, that I think would be more relevant. How can I choose this DTS instead?

Ok, so, first of all, I am a complete noob. I bought Banana Pi thinking that it is similar to Raspberry Pi's architecture but it's obviously not. I bought a 240x240 Waveshare 1.3 inch hat and I was wondering how to get it working on my Banana Pi Zero (H2+). On Raspberry Pi I can use Juj's fbcp-ili9341 driver but it's probably not compatible with Armbian, right? How do I go about it? Also, it would be nice to know how to detect buttons (that are on the hat) and convert them to key strokes. Thanks!

hello dear all on banana pi - i have connected all the wires but: no signal on screen what can i do now - plz advice update: found an very very interesting thread: see https://www.raspberrypi.org/forums/viewtopic.php?t=34061 presume, you have installed your selected OS on SD card. Boot sector of the SD card is normally accessible from Windows, so you can edit file config.txt. What you maybe need? Add into config.txt this line: Code: Select all hdmi_force_hotplug=1 well - this can be a good hint.. what do you say - btw. How to edit this line!? btw found some additonal texts: https://raspberrypi.stackexchange.com/questions/2169/how-do-i-force-the-raspberry-pi-to-turn-on-hdmi Add these two lines to /boot/config.txt and reboot Raspbmc: hdmi_force_hotplug=1 hdmi_drive=2 hdmi_force_hotplug=1 sets the Raspbmc to use HDMI mode even if no HDMI monitor is detected. hdmi_drive=2 sets the Raspbmc to normal HDMI mode (Sound will be sent if supported and enabled). Without this line, the Raspbmc would switch to DVI (with no audio) mode by default. config.txt is read by the GPU so it will work on every distro. There's two ways to do it. In older Pi installs, use the fb0 framebuffer when you want to display stuff on the HDMI/TV display, for example: FRAMEBUFFER=/dev/fb0 startx will use the HDMI/TV framebuffer for X windows instead of the PiTFT On Jessie Pi installs, run sudo nano /usr/share/X11/xorg.conf.d/99-fbdev.conf to edit the configuration file and make sure it contains: Copy Code Section "Device" Identifier "display" Driver "fbdev" Option "fbdev" "/dev/fb0" EndSection change the Option "fbdev" "/dev/fb0" line to Option "fbdev" "/dev/fb1" if you want the xdisplay on the PiTFT or fb1 to fb0 for HDMI output. Update: If don't see the code above in the file, then simply copy and paste what is shown in this answer at the bottom of that file. If you can't find 99-fbdev.conf file in that folder, then there is probably another file with different name like 10-evdev.conf in the same folder which you will have to modify to make it work as described above.

Hi all, I just downloaded the Armbian(5.36 xenial-next)-based image for BPI M2 Zero, that comes with kernel 4.14.3-sunxi. I'm looking for kernel headers for this kernel, but I can't find it in armbian's repo. Could you help me to retrive them? Thank you!