Jump to content

Search the Community

Showing results for tags 'bananapim2zero'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. 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
  2. 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
  3. 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!
  4. 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
  5. 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.
  6. 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 ?
  7. 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!
  8. 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?
  9. 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!
  10. 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.
  11. 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!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines