Jump to content

Search the Community

Showing results for tags 'nanopim4'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

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. I downloaded the latest Armbian 22.08 image for the NanoPi M4V2 (https://armbian.chi.auroradev.org/dl/nanopim4v2/archive/Armbian_22.08.8_Nanopim4v2_jammy_current_5.15.75.img.xz), flashed it to an sd card and tried to boot my NanoPi M4 (non-V2 board). It crashes every time with the attached log. I have tried 4 different power supplies, so I don't think that's the issue. I tried the Bullseye CLI image and it fails in the same way. The Sid server image works fine. Any ideas? Thanks, Ben
  2. Hi, I own a nanopi m4 v1, I know there is no more armbian support neither maintainer for this board but I still enjoy "the other supported variants" which work very good for my needs. Until now, I only used armbian on sdcards for my system, but today I tried to install it of my emmc module. Maybe I did somethig stupid, I tried to install the bullseye current cli version from https://www.armbian.com/nanopi-m4/ on my emmc module via armbian-install. So all process of installation was ok (boot on sdcard then armbian-install => erase / format / install on emmc ...), I choose to boot from emmc too (maybe it was a mistake). => After the installation I put off the sdcard (to let only the emmc on the board), then plugin power to boot, but nothing happen (only red light on boot). From then my board cannot boot anymore, I have only the red light on, no more green light. I try to flash back sdcard again with a lot of differents images (armbian, legacy versions, friendly elec versions), without any success. I try with differents sdcards (who worked before), with or without the emmc module plug, nothing worked. I try too to boot on usb but same result. So I think the option I choose in armbian-install to boot on emmc maybe change the boot mode of my board ? Maybe is some eeprom on the board with some kind of boot order which was flash by armbian-install and explains the problem ? Have anyone have that kind of problem ? Some ideas to unbrick my board ? Thank you P.S. : My emmc module is ok too, I had friendlycore installed on it and I boot it more earlier today. I don't have emmc usb reader, so I cannot flash the emmc for now (I used the board for that).
  3. I simply can not figure out why UART4 at GPIO1 header with the pins 19 (TX) and 21 (RX) not working at all. I see that here (ttyS2) is running an agetty but there is no serial activity at any baudrate (9600, 115200). Please help me.
  4. Hi all, I have a nanopi m4 with following installation - Armbian_22.05.4_Nanopim4v2_jammy_current_5.15.48_xfce_desktop. I am looking for someone who has retroarch installed on armbian and fully working, and what the key steps are. Im asking because: 1) I tried installing by command line, which installs retroarch to a location with no cores. An issue with rk3399 cores is that there are none to download and must be built seperately (Is there a way to update a file so that cores can be downloaded through the application?) 2) In an attempt to build retroarch + cores, i downloaded and built libretro, which took probably 12+ hours. This resulted in a seperate installation, with cores not in the correct directory, and many cores uninstallable eg mame2010, ppsspp. I hope someone can assist - I want to find a use for my nanopi m4 but having difficulty with retro games - Rcade is buggy, lakka does not work well, batocera does not work well, TwisterOS does not boot after selecting correct .dtb etc. I have built linux and android on many boards but this one is troublesome. Thanks for reading
  5. Myy

    Mainline VPU

    So, I tried to adapt @Kwiboo and @jernej patches on my 5.6 branch, but this made the kernel fail to boot for no visible reason. Since I were able to boot it without the VPU patches, I'm convinced that it's their readaptation that broke something. The patches applied are here : https://github.com/Miouyouyou/RockMyy64 If someone wants to play with them and determine which one break the boot process.
  6. mindee

    NanoPI M4

    NanoPi-M4 will be cheaper and same form factor as RPI 3.
  7. My nanopi m4b has been showing slowness problems that I believe to be caused by the ethernet, I access a site inside it that has a camera stream and sometimes it is slow, and now the connection via ethernet completely stopped working, I looked for something in the logs but I didn't find anything that could indicate the problem, I can access my site over wifi
  8. i found a running task on friendlyelec desktop called "pwm fan" But i found no more informations how to connect a pwm fan to the Nanopi M4 Which pins are needed to connect ? Can i use a normal 5V Fan or is a special Fan needed ? Anyone aware of this ?
  9. I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64 while others uInitrd -> uInitrd-5.10.35-rockchip64 dtb -> dtb-5.10.35-rockchip64 The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard. It works fine afterward but I wondered if there is the right way to fix this issue for good. Thank you,
  10. I am trying to get a camera going on the Nanopi-m4 (I have tried another board as well with similar results). The sensor is setup in the device tree correctly and gets probed on boot. However there are some issues when loading rkisp1. [ 5.645127] rkisp1 ff920000.isp1: Adding to iommu group 5 [ 5.645695] rkisp1 ff920000.isp1: Failed to get clk 'clk_isp': -2 [ 5.645814] rkisp1: probe of ff920000.isp1 failed with error -2 My understanding with Failed to get is because it is either being used by another resource or was not defined correctly. Below are my entries in the device tree for the isp. I am using `isp1` in this case, I am assuming as well that `ispl` is locked to `csi1` where my camera is located. isp1: isp1@ff920000 { compatible = "rockchip,rk3399-cif-isp"; reg = <0x0 0xff920000 0x0 0x4000>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; clocks = <&cru SCLK_ISP1>, <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "isp", "aclk", "hclk"; iommus = <&isp1_mmu>; phys = <&mipi_dsi1>; phy-names = "dphy"; power-domains = <&power RK3399_PD_ISP1>; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; #address-cells = <1>; #size-cells = <0>; }; }; }; isp1_mmu: iommu@ff924000 { compatible = "rockchip,iommu"; reg = <0x0 0xff924000 0x0 0x100>, <0x0 0xff925000 0x0 0x100>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; interrupt-names = "isp1_mmu"; clocks = <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "aclk", "iface"; #iommu-cells = <0>; power-domains = <&power RK3399_PD_ISP1>; rockchip,disable-mmu-reset; }; &isp1_mmu { status = "okay"; }; &isp1 { status = "okay"; ports { port@0 { mipi_in_ucam1a: endpoint@0 { reg = <0>; remote-endpoint = <&ucam_out1a>; data-lanes = <1 2>; }; }; }; }; Currently I am disabling unused devices in order to make sure that this isn't related to some conflict. Any help or references would be great. I am still in the process of getting an understanding of rkisp.
  11. I'm getting burst "VOP vblank IRQ stuck for 10 ms" error messages in dmesg and wondering what it means and if anything to improve/fix. I'm using Nanopi m4 $ uname -a Linux nanopim4 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux kern :err : [Sat Mar 13 22:20:13 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:09 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:11 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:18 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:21 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms
  12. Hi all, This has confused me! I have an old copy Armbian_20.02.7_Nanopim4_buster_current_5.4.28_desktop.7z which works fine. Any SD cards I put it on using Balena Etcher works. Any of the latest versions simply won't boot. The only difference appears to be the XZ file format. I extracted one of the later ones using 7Zip and then Etcher to flash and as expected it mad no difference at all. Has something been done to the V1 firmware from the V2 that doesn't work or firmwares containing the wrong naming etc? Help!
  13. Hi, Just bought the SATA HAT and before I get started, I see in the OS Support that Lubuntu and Friendly Core is supported. Does this Exclude Armbian ? I'm not overwhelmed with FriendlyCore . Thank sin advance
  14. Board: Nanopi M4 with 4GB OS: Armbian_5.65_Nanopim4_Debian_stretch_default_4.4.162 Boot from SD, rootfs on an external HDD 8TB (WD MyBook). I attached another external HDD (Toshiba 2TB). I have been trying rsync -avh from the Toshiba one to the main MyBook one. It ran for under a minute before reporting files were vanished and exited with errors. It appeared the / is gone. nothing return from ls. Hard-reboot, fsck ran, everything's back to normal. I've been trying rsync with nice -n 20 as well as --bwlimit 10, 1MB. Nothing helped. stress test the board for 10 minutes, (stress -c 4 -m 4 -d 4 -i 4). All looks good. Any help's appreciated. Thanks, Jerry
  15. Hi, I was trying to load below Armbian images into NanoPi M4 (just M4, neither M4B nor M4V2). They are able to be loaded in the first place, but when I reboot the board by typing "reboot" command in the terminal, I can only see black screen showing on the monitor, no led flashing on the board even, and the board never boots up again. If I unplug the power cable and plug back again, it boots as expected. Is there any way I can reboot the board remotely? Armbian_20.08.1_Nanopim4_buster_current_5.8.6_desktop.img.xz Armbian_20.08.1_Nanopim4_buster_current_5.8.6.img.xz Armbian_20.08.1_Nanopim4_bionic_current_5.8.6.img.xz Armbian_20.08.1_Nanopim4_focal_current_5.8.6.img.xz As these are in the recommended image list for M4, do we have images with kernel version greater than 5 you guys would recommend? Thanks, Jason
  16. Hi, I noticed that on my board I didn't have notification with MOTD when updates were available and I think that I've found the culprit: In the file /usr/lib/armbian/armbian-apt-updates of the package linux-buster-root-legacy-nanopim4_20.08.17_arm64.deb, this line stop the script to go further : # give up if packages are broken [[ ! $(dpkg -l | grep ^..r) ]] && exit 0 If I remove the ! then it works (because the script, in fact, gives up if packages are not broken )
  17. I have a serious problem as I mentioned in a title Currently I'm using Armbian on my NanoPi M4 and very satisfied its functionality But when I try to use usb3 device (especially camera from ZWO campany, ZWO ASI 178) with it, it doesn't recognize it as USB3 device but USB2 by checking the data transfer speed with "lsusb -t" Then, once I unplug the cable and plug it to the pi again, that device is recognized as USB3 and the data transfer speed becomes much higher. I need to get USB3's fast data transfer as soon as the board gets booted, without unplugging cables since now it's not that easy to access to the board and cable. I tried usb reset command like echo -n "1-2.1" > /sys/bus/usb/drivers/usb/unbind but this doesn't change anything I suppose somehow I can simulate this unplugging processing with some commands and get USB3 connection. Hope anyone knows about this issue Thank you
  18. Hi, I'm using NanoPi M4 $ uname -a Linux nanopim4 4.4.213-rk3399 #3 SMP Mon Oct 5 15:53:54 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux and wondering if I can upgrade the linux kernel to 5.8.x without reinstalling other things. I tried armbian-config -> System -> Other All available options are those 4.4.213-rk3399 with different Armbian versions 20.08.x. I'm currently on 20.08.9 Appreciated any step, pointer Thank you
  19. I am testing a Nano-Pi M4 with 4GB of RAM, with the heat sink and fans installed ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.4.162-rk3399, docker CE and BOINC / seti@home, installed. I am using 7 Raspberry-Pi 3B+ boards as nodes. I would like to implement and test boinc-client-docker, (https://github.com/BOINC/boinc-client-docker). I am new at this and running into overheating issues, (temps over 70C as reported by htop), when all 6 cores are maxed out at 100%. I can keep the board slightly below 70C if I add multiple fans pointed at the heat sink, however I would like a better solution. I was wondering if setting the max frequency of the cores to a slightly lower level would resolve this issue. 2x Cortex-A72 at up to 2.0GHz, 4x Cortex-A53 @ up to 1.5GHz cores 1 through 4 will run at 1.49x and cores 5 & 6 will run at 1.99x they all idle at 600 MHz with a resting temp of 32C Would setting thee max frequencies to 1.48 and 1.8 help resolve this issue? What would be the best method of testing this? The results of cat /etc/default/cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=600000 MAX_SPEED=2016000 GOVERNOR=ondemand
  20. Hi, I would like to know if it is possible to switch from the current branch to the legacy one as I've read that the board will be much more stable with the older kernel ? I've installed my NanopiM4 last march, and I've experienced some random freezes of my board after some time (can take weeks). It seems that one of my solutions would be to use the legacy kernel as it is much more stable - information I got by reading the forums (something I haven't done before because I'm stupid and was in a hurry...). Is it possible to downgrade only the kernel at all ? Here are the packages that (I think) I have to replace : linux-buster-root-current-nanopim4/buster,now 20.08.3 arm64 [installed] linux-dtb-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-headers-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-image-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-u-boot-nanopim4-current/buster,now 20.08.1 arm64 [installed] With those packages, then : linux-buster-root-legacy-nanopim4 - armbian tweaks for buster on nanopim4 (legacy branch) linux-dtb-legacy-rockchip64 - linux dtb, version 4.4.213-rockchip64 linux-headers-legacy-rockchip64 - linux kernel headers for 4.4.213-rockchip64 on arm64 linux-image-legacy-rockchip64 - linux kernel, version 4.4.213-rockchip64 linux-u-boot-nanopim4-legacy - uboot loader 2020.07 Will that be enough or are more packages needed without screwing my install ? Should I use apt-get or do I have to use the armbian-config tool instead ? Is there an order to respect ?
  21. Have anyone tried to use USB connected monitor with NanoPi? I'm thinking about buying one but not sure it can work with it or, if some change has to be done to NanoPi , I would like to know about it.
  22. Hi, I'm currently working to enable SPI on NanoPi M4 but it is not working... I have edited main DT to the following one and now /dev/spidev0.0 appears. But when I checked spi with this tool:https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c I only got the result below and no matrix appears... spi mode: 0x0 bits per word: 8 max speed: 500000 Hz (500 KHz) Here is what dmesg | grep spi returns I have checked the output from the proper GPIO with oscilloscope but found nothing. almost spent couple weeks on this Anyone had the same issue or knows what to do here?
  23. Hi all, anyone here ever used a Khadas Tone Board on a Nanopi M4 ? I've just bought one but can't get any sound out of it. What I'm trying to achieve is run Logitech media server in conjunction with squeezelite using the Khadas as my DAC. LMS and Squeezelite both installed and run without errors BUT ! there is no sound. How can I make the Khadas the default output device ? Edit I have it working now you have to edit /etc/defaults/squeezelite and tell it what card to use SL_SOUNDCARD="hw:CARD=Control,DEV=0"
  24. Hi everyone, I'm trying to get 4k output from my NanoPi M4. I have tried (using a Steamlink HDMI cable) directly connected to my TV (to eliminate my receiver as a point of failure/bugs) to get something to output to the screen in 4k. I haven't succeeded. What information I've gathered so far: There are two "vops" a big and little, and the little one is not designed to, and cannot output 4k (there was a patch hacking that into vopl but I never dared test it and can't find it now). There was this change setting the maximum resolution to 4k in a file/subdirectory I cannot find in recent kernels anymore: https://patchwork.ozlabs.org/project/uboot/patch/20200402114125.2501-6-jagan@amarulasolutions.com/ Any LibreElec/Kodi build (Joern-P, @Kwiboo, @balbes150, @@lex) didn't seem to give me any 4K output options, on kernel 4.4 or 5.x. The EDID returned from my TV contains the 4k modes (but seems to not be able to handle them correctly): Section "Monitor" Identifier "LG TV" ModelName "LG TV" VendorName "GSM" # Monitor Manufactured week 1 of 2015 # EDID version 1.3 # Digital Display DisplaySize 1600 900 Gamma 2.20 Option "DPMS" "false" Horizsync 30-83 VertRefresh 58-62 # Maximum pixel clock is 160MHz #Not giving standard mode: 640x480, 60Hz #Not giving standard mode: 800x600, 60Hz #Not giving standard mode: 1024x768, 60Hz #Not giving standard mode: 1152x864, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Extension block found. Parsing... #WARNING: I may have missed a mode (CEA mode 93) #WARNING: I may have missed a mode (CEA mode 94) #WARNING: I may have missed a mode (CEA mode 95) #WARNING: I may have missed a mode (CEA mode 98) #WARNING: I may have missed a mode (CEA mode 99) #WARNING: I may have missed a mode (CEA mode 100) Modeline "Mode 16" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace Modeline "Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 1" 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline "Mode 6" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline "Mode 7" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 9" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 11" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 12" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 13" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 14" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 15" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline "Mode 17" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Option "PreferredMode" "Mode 16" EndSection CEA mode 93-95 and 98-100 are all 4k output modes, see the table listing them on Wikipedia. My question is then, what am I missing and how do I get 4k output from my NanoPi M4? Thanks for any input!
  25. Hi all, I'd just like to share a problem I experienced and what solved after a bit of Googling. Basically, I have Nextcloud installed on my Nanopi M4 (v1) with Armbian: $ uname -a Linux nanopim4 4.4.192-rk3399 When I sync files from my Android phone via local wifi, often the transfers were just failed. Not always but usually, it's when a directory contains lot of large files. After a bit of Googling and came across this: https://unix.stackexchange.com/questions/494290/nanopi-m4-rk3399-apache2-ssl-large-download-hangs/495378#495378 It works. The problem's solved after: ethtool -K eth0 rx off tx off and put the command in /etc/network/if-up.d/ethtool Just wondering if anyone knows the root cause and have better solution than disabling things. Thanks,
×
×
  • Create New...