Jump to content

Search the Community

Showing results for tags 'nanopik1plus'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 10 results

  1. Hello! I found that on NanoPi K1 Plus there is issues with both of integrated audio adapter (H3 Audio Codec) and HDMI Audio (allwinner-hdmi 1c22800.i2s-i2s-hifi) 1. With H3 Audio Codec I getting only silence, altrought there is short click on starting and end of playback. "Stereo" mode was chosen in pavucontrol for this audio adapter. 2. With allwinner-hdmi audio playback is working, but left and right channels is swapped. Like above "Stereo" mode was chosen in pavucontrol for this audio adapter. Tests was performed from Mate desktop installed on top of Armbian 20.05.4 with Linux 5.4.45-sunxi64. "speaker-test -t wav -c 2" command was used for testing. To make sure that PulseAudio will route audio from speaker-test to right audio adapter I used pavucontrol to disable all other audio adapters besides the one I currently test. I wonder if anyone else experiencing same issues with this board? Should I report allwinner-hdmi channels issue or H3 Audio Codec issue to kernel bugzilla or some Armbian-specific patches is involved in enabling audio adapters on this board?
  2. I am trying to start snap multipass on the device nanopi k1 plus, getting the following error: root@nanopik1plus:~/testSnap# multipass start launch failed: Internal error: qemu-system-x86_64 failed getting vmstate (Process returned exit code: 1) with output: qemu-system-aarch64: -nographic: No machine specified, and there is no default Use -machine help to list supported machines
  3. I'm trying to make working 3.5" 320*480 TFT SPI display with touch screen on NanoPi K1 Plus with Armbian 20.05.2 (kernel 5.4.43). For now it works, but the touchscreen has issues. In empty `startx` session cursor works for few minutes and then hangs, restarting `startx` make it working again for a while. If I try to run x session with chrome, the cursor hangs immediately. openbox-session & chromium --no-first-run --disable --disable-translate --disable-infobars --disable-suggestions-service --disable-save-password-bubble --start-maximized --kiosk --disable-session-crashed-bubble Any ideas how to fix it? Screen image Configuration steps: 1. Enable 2 spi 2. Screen and touchpanel dts, based on https://github.com/adafruit/adafruit-rpi-fbtft/blob/master/dts/overlays/rpi/piscreen-overlay.dts 3. Install software apt-get install xserver-xorg xorg xserver-xorg-legacy xinit xinput openbox chromium
  4. As title says, how to install image on eMMC on this board? My board works fine on TF card with every image FriendlyElec, DietPi and you here provide, but i haven't managed to make it boot from eMMC. On official Wiki there are some misleading. For Ubuntu they say to select image from eflasher and burn it on TF card. Eflasher folder has two images. Which one? Although i tried both. Anyway, if i burn boot image on TF card, should eMMC stays empty or to burn on it, say, root image? Or to burn root image on TF? I had a few attempts but no luck. Obviously. On Android, they say to insert TF card into PC and burn image on eMMC? LOL. Again should i burn anything on eMMC? If so, should i burn it as product or startup? Damn, too many options... Second question. There are two Armbian images, bionic and stretch. What is the difference? Both works fine, but they are server kind of images. Is there a plan to make a desktop variant?
  5. I'm trying to get TFTP support into U-Boot but it insists that 'no ethernet found'. I've added a couple of nodes to the device tree such that it has 'status = "okay" and mac-address = [00 00 00 00 00 00]; I've also added a top level alias in sun50i-h5-nanopi-k1-plus.dts (as added by @martinayotte following this thread) as below. Not sure if the U-Boot config needs changing in any way but the network components are certainly being built. Any thoughts most welcome. AATIA. aliases { serial0 = &uart0; ethernet0 = &emac; }; U-Boot dump of the loaded DTB on running system follows: => bdinfo arch_number = 0x00000000 boot_params = 0x40000100 DRAM bank = 0x00000000 -> start = 0x40000000 -> size = 0x80000000 baudrate = 115200 bps TLB addr = 0xBFFF0000 relocaddr = 0xBDF4B000 reloc off = 0x73F4B000 irq_sp = 0xB9F27590 sp start = 0xB9F27590 Early malloc usage: 2d8 / 400 fdt_blob = 00000000b9f275a8 => fdt addr 00000000b9f275a8 => fdt print ethernet0 ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x0000000e>; reg = <0x01c30000 0x00010000>; interrupts = <0x00000000 0x00000052 0x00000004>; interrupt-names = "macirq"; resets = <0x00000005 0x0000000c>; reset-names = "stmmaceth"; clocks = <0x00000005 0x0000001b>; clock-names = "stmmaceth"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; status = "okay"; mac-address = [00 00 00 00 00 00]; mdio { #address-cells = <0x00000001>; #size-cells = <0x00000000>; compatible = "snps,dwmac-mdio"; phandle = <0x0000000f>; }; mdio-mux { compatible = "allwinner,sun8i-h3-mdio-mux"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; mdio-parent-bus = <0x0000000f>; mdio@1 { compatible = "allwinner,sun8i-h3-mdio-internal"; reg = <0x00000001>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x00000001>; clocks = <0x00000005 0x00000043>; resets = <0x00000005 0x00000027>; }; }; mdio@2 { reg = <0x00000002>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; }; }; };
  6. Working from the documentation here: https://docs.armbian.com/Developer-Guide_FEL-boot/#what-is-felnfs-boot. Not much luck so far with an FA NanoPi K1 Plus. Please see below for details. TIA.
  7. I've tried to the best of my abilities, but it seems that the current Bionic image does not support the K1 Plus wifi? Is that correct? In armbian-config there is no option to setup wireless and I cannot get the board to recognise a wlan0 device by changing the interfaces configurtation.. Is there some trick?
  8. I am a new owner of Nanopi K1 plus. Can someone tell me how to install a desktop version of my device?
  9. My NanoPi K1 Plus is using at the moment ARMBIAN 5.47 stable Debian GNU/Linux 9 (stretch) 4.14.51-sunxi64 ( https://dl.armbian.com/nanopik1plus/archive/Armbian_5.47_Nanopik1plus_Debian_stretch_next_4.14.51.7z ) In the archive at https://dl.armbian.com/nanopik1plus/archive/ is also https://dl.armbian.com/nanopik1plus/archive/Armbian_5.53_Nanopik1plus_Debian_stretch_next_4.17.9.7z Is 4.17.9 also stable? And if YES is there a simple way to update without reinstalling? I did try apt update apt upgrade and apt dist-upgrade but no 4.17.9 avail. Nightly is at https://dl.armbian.com/nanopik1plus/nightly/Armbian_5.46.180622_Nanopik1plus_Debian_stretch_dev_4.17.2.7z (but I didnt want to switch ti nightly via armbian-config)
  10. who tried to install ? who was able to install on eMMC ?
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines