Jump to content

Search the Community

Showing results for tags 'orangepiplus'.

  • 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
    • Orange Pi 5
  • 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 have Orange Pi Plus 2 running Ubuntu Bionic with Armbian Linux 4.19.62-sunxi and I would like to upgrade it to recent Armbian build based on Ubuntu Linux Server and move OS to SSD connected to one of USB ports. I tried to use Armbian_22.08.2_Orangepiplus_jammy_current_5.15.69.img.xz but it does not connect to both HDMI and network. I tried unofficial command line interface images from product page and weekly released unsupported community builds. Behavior of all these builds is the same - no output to HDMI, no network connection. Finaly I found that recent image for Orange Pi Plus / Plus 2 which boots is Armbian_22.08.1_Orangepiplus_jammy_current_5.15.63.img.xz. I was able to boot from this image and transfer OS to SSD but running "apt update" and "apt upgrade" breaks something in operating system even if Kernel is "frozen" using armbian-config utility. After upgrade OS does not recognize usb-to-serial adapter CH341 connected to one of USB ports. Amout of loaded Kernel modules essentially decrease: orangepiplus:~:# lsmod Module Size Used by pwrseq_simple 16384 1 sy8106a_regulator 16384 0 gpio_keys 20480 0 uas 24576 1 realtek 24576 1 orangepiplus:~:# Attempt to load module using modprobe fails: orangepiplus:~:# modprobe usbserial vendor=1a86 product=7523 modprobe: FATAL: Module usbserial not found in directory /lib/modules/5.15.63-sunxi orangepiplus:~:# It looks like kernel modules were upgraded by running "apt update" and "apt upgrade" although Kernel was "frozen" using armbian-config utility. There is no 5.15.63-sunxi folder in /lib/modules: orangepiplus:~:# ls -la /lib/modules/ total 12 drwxr-xr-x 3 root root 4096 Nov 14 21:04 . drwxr-xr-x 76 root root 4096 Nov 14 20:31 .. drwxr-xr-x 3 root root 4096 Nov 14 20:31 5.15.74-sunxi orangepiplus:~:# Adding sym link to upgraded modules does not help. Load module fails due to exec format error: orangepiplus:~:# ln -s /lib/modules/5.15.74-sunxi /lib/modules/5.15.63-sunxi orangepiplus:~:# ls -la /lib/modules/ total 12 drwxr-xr-x 3 root root 4096 Nov 14 20:45 . drwxr-xr-x 76 root root 4096 Nov 14 20:31 .. lrwxrwxrwx 1 root root 26 Nov 14 20:45 5.15.63-sunxi -> /lib/modules/5.15.74-sunxi drwxr-xr-x 3 root root 4096 Nov 14 20:31 5.15.74-sunxi orangepiplus:~:# orangepiplus:~:# modprobe usbserial vendor=1a86 product=7523 modprobe: ERROR: could not insert 'usbserial': Exec format error orangepiplus:~:# All modules in /lib/modules before and after running "apt update" and "apt upgrade" are compressed and have extension ".xz". It looks like upgraded Kernel has no ability to load compressed modules. I understand that Orange Pi Plus / Plus 2 is not supported anymore but is it possible to check if Kernels newer then 5.15.63 were compiled with "CONFIG_MODULE_COMPRESS=y" and "CONFIG_MODULE_COMPRESS_XZ=y"? Thanks, Sergey
  2. Hi. I need the serial number of the CPU of the orange Pi boards. I see it is in the file /proc/cpuinfo I need another place that is not file based as the cpuinfo file can be spoofed. Is there a way to read it directly from a register?
  3. If I convert rootfs to btrfs do I need to rebuild /boot/initrd.img-5.4.20-sunxi. E.g. is it enough to convert ext4 to btrfs on another PC and replace rootfstype=ext4 by rootfstype=btrfs in /boot/armbianEnv.txt? Armbian 2020.02.1 mainline with default kernel, orange pi plus I need a compression because OPI+ supports cards up to 32 Gb only. Thanks in advance.
  4. I was updating some images and thought the Orange Pi + had been retired ... but there was no Support Ended note. I see a lot of other Plus versions of Orange pi boards listed, but not the plain Orange Pi +. Seems easy to miss ;] A little searching found the Orange Pi + is supported https://www.armbian.com/orange-pi-plus/ Am I just missing the link in Downloads? The only way I've been able to get to the page is by direct url or a duckduckgo search https://duckduckgo.com/?q="orange+pi+plus"+armbian&t=raspberrypi&ia=web
  5. Hey, i hope this has not been answered already but i could not find it. I also hope this is the right place to report it. The orange pi + does not appear in the list of devices https://www.armbian.com/download/?tx_maker=xunlong but there is a download page for it you can reach by the search. https://www.armbian.com/orange-pi-plus/ i assume its a bug in the web page?
  6. After upgrade to latest kernel (4.19.38) my device only boots into maintenance mode. System is on emmc and no problems before. I started armbian-config and switched back to previous kernel, but it doesn't boot system. Even with all USB devices disconnected it didn't start (as i see there are some usb errors in log), file system seems to be clean, just didn't start system in normal mode.... Any advice? Thx Update: OK, solved, after installing latest updates within maintenance mode its ok again....
  7. Is the build for Orangepi Plus the same for Orangepi Plus 2? When I download for OPI Plus 2 I get the following file: Armbian_5.65_Orangepiplus_Debian_stretch_next_4.14.78 but it will not start
  8. Hi, I've been using armbian in combination with openmediavault for the last years to access my files on an 1TB HDD. Today I wanted to upgrade the drive to a 3 TB one, but it just shows a capacity 746GB. Is there a size limit on the GL830 for harddrives or why isn't the real capacity showing up? fdisk-l: Disk /dev/sda: 746.5 GiB, 801569724416 bytes, 1565565868 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Thanks in advance Regards, Joshua
  9. Hi, I have an Opi+2 board and I want to overclock it. Assuming that I have a proper cooling, how can I do that? I want to overclock it to 1.6Ghz.
  10. I made tests with Orange Pi 2+ to install Armbian to eMMC. But I have no idea why it takes 30 minutes to install. I assume write speed of eMMC to be 5MB/s (ok maybe it is even faster) and Armbian on SD card is about 2.1GB, so it should take ~7 minutes to copy files, plus some more minutes to finish final touches, let's say 15 minutes together. But why it takes more than 30 minutes? Is there any possibility how to reduce this time? P.S. When I am burning armbian img to SD card, in 5 minutes I am ready to go and boot the system.
  11. --- ENGLISH --- Hello, Is there a kernel 4.9+ with the usable sata port, for an Orange PI plus 2 ? I looked HERE but I can not recover an old version with functional SATA port. Thanks for your help. Marc --- ORIGINAL --- Bonjour, Est ce qu'il existe un kernel 4.9+ avec le port sata utilisable, pour un Orange PI plus 2 ? j'ai regardé ICI mais je ne parviens pas à récupérer une ancienne version avec port SATA fonctionnel Merci pour votre aide. Marc
  12. Hello My system is installed on the internal eMMC. After a system update my OPi will not boot anymore. Perhaps anyone can help. Thx.. Gesendet von meinem WAS-LX1A mit Tapatalk
  13. Ozebe

    VLC Issue

    Hello guys, I am having problems with vlc, the video is running out of proportion and it is all over the interface, ie, even minimizing vlc the video is still being shown, I tried to change the codecs but I did not have a satisfactory result, because only the VDPAU works without lags Help me please, sorry for bad English.
  14. Hello there I am looking to prepare kernel headers on orange pi plus to install mali drivers kernel version 4.14.68-sunxi Release Bionic Command : cd /usr/src/linux-headers-4.14.68-sunxi && sudo make scripts -j4 Result: scripts/Makefile.build:155: recipe for target 'scripts/mod/devicetable-offsets.s' failed make[2]: *** [scripts/mod/devicetable-offsets.s] Error 1 scripts/Makefile.build:587: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 Makefile:569: recipe for target 'scripts' failed make: *** [scripts] Error 2 I have tried everything here is the detailed debugging info make scripts -j4 -d Any help would be appreciated
  15. Hi, I recently reinstalled an orange pi 2+ with Armbian Stretch mainline kernel 4: root@ted1090-7:~# uname -a Linux ted1090-7 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux I also installed it on EMMC (this way, with this u-boot-sunxi-with-spl.bin). Now this orange pi crashes every couple of days (sometimes with a couple of hours). This orange pi use to run with Armbian legacy 3.x kernel on EMMC without any issue: pi@ted1090-6 ~ $ uname -a Linux ted1090-6 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l GNU/Linux Exactly the same applications are installed (dump1090 and dump1090-tools). The applications do run okay until the orange pi crashes. I have several more orange pi's 2 +, running exactly the same software on the Armbian legacy 3.x kernel installed on EMMC without any issue. I would like to know why my orange pi crashes with the Armbian Stretch mainline kernel 4? I monitored the files systems and searched the log files for a reason, but I didn't find a cause. Does anyone know why I pi crashes? Here is my system info: http://ix.io/1lxa root@ted1090-7:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/1lxa Kind regards!
  16. First : i downloaded both Armbian versions for "Orange Pi+ 2" but reported link file names where different from those that actually download : a) link says https://dl.armbian.com/orangepiplus/Ubuntu_xenial_default_desktop.7z, but download file is Armbian_5.38_Orangepiplus_Ubuntu_xenial_default_3.4.113_desktop.7z b) 2nd link says https://dl.armbian.com/orangepiplus/Debian_stretch_next.7z, but download is Armbian_5.38_Orangepiplus_Debian_stretch_next_4.14.14.7z Second : after download i extracted both with : 7z e filename.7z then i run etcher 1.4.4 cli : ./etcher -d /dev/sdd filename.img -y , result sdcard writed, then i inserted sdcard and boot it . I never had a hdmi signal and green led still blinking in both images i tried . Thanks in advance for any help Panos
  17. Hi Did a fresh install of Armbian_5.38_Orangepiplus_Debian_stretch_next_4.14.14.img on a Orange Pi Plus. Efter reboot, I did a apt-get update and apt-get upgrade, then rebooted... For some reason, wlna0 is no longer listed. I can do a "ifconfig wlan0 up", which brings up the interface - but so far I have had no success in configuring the wlan0 interface, neither by armbian-config nor nmtui I have even tried to edit /etc/network/interfaces and add: allow-hotplug wlan0 auto wlan0 iface wlan0 inet dhcp wpa-ssid "RG47C" wpa-psk "Secret!!!" but I am still not able to get it up and running. After a reboot, wlan0 is down again (and apparently unable to connect to any wireless networks). /var/log/messages states: Aug 2 18:57:40 3d-am8l NetworkManager[4187]: <info> [1533236260.7447] device (wlan0): driver supports Access Point (AP) mode Aug 2 18:57:40 3d-am8l NetworkManager[4187]: <info> [1533236260.7508] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3) Aug 2 18:57:40 3d-am8l NetworkManager[4187]: <warn> [1533236260.7530] Error: failed to open /run/network/ifstate Aug 2 18:57:40 3d-am8l NetworkManager[4187]: <info> [1533236260.7820] manager: startup complete Any help is appreciated. Regards /B
  18. I've formatted the opi+2 card I have using recovery and now I get ping screen. I use a 1280x1024 screen with a DVI converter. I tried the HDMI cable using a 1080p TV and it worked without issues. I also tried "h3disp -m 33 -d" "h3dsip -m 1024x768 -d" "h3disp -m 33" and so on. None of them worked. Here is a system output (used armbianmonitor -u) http://ix.io/1iWN !! I noticed this output when used dmesg command: [DISP] disp_ioctl,line:1584:para err in disp_ioctl, cmd = 0x0,screen id = 65536
  19. Hi, I have a Opi+2 board which has an Armbian system installed in its emmc. Now I want to format its Emmc and reinstall Armbian but the problem is I don't have a proper SD card. So I need to do it without an SD card. I have a running system on it, so I can reach the working system. Is there a way of formating it while its running? For example a command does the same thing with "dd if=armbian.img of="/dev/mmcblk1"" (which won't work while there is a system working, its just an example) (mmcblk1 = working system, emmc)
  20. Hello, I am trying to boot Armbian on a stock Orange Pi Plus 2 which has stock Android installed to its eMMC. I perform the following steps: 1. Download the Armbian Stretch mainline kernel 4.14.y (https://dl.armbian.com/orangepiplus/Debian_stretch_next.7z). 2. Unzip the archive uzing p7zip (on Arch Linux, using "7z e Armbian_5.38_Orangepiplus_Debian_stretch_next_4.14.14.7z"). 3. Verify that the sha256sum of Armbian_5.38_Orangepiplus_Debian_stretch_next_4.14.14.img is 7ac1896ca4ea8f518d41d23ee07b05aedd1db23fbbeab2056865ae5a3c45e5c9. 4. Burn the image with Etcher to a brand new and genuine Samsung Evo Plus 32 GB. (It was used for writing a couple of older Armbian versions today, but to no avail). 5. Insert the SD card in the Orange Pi Plus 2's SD card slot. 6. Plug in Ethernet and UART debug. 7. Power on with a tested 5V, 2A power supply and no unnecessary USB devices connected to the Pi. 8. The power-on green LED on the board is steadily lit, the green LED on the Ethernet port flashes quickly. The CPU is warm to the touch, but kernel doesn't boot properly. 9. No DHCP entries for new devices pop up in the router table. Here is the UART output: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) 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 3708 bytes read in 212 ms (16.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 152 bytes read in 172 ms (0 Bytes/s) 5070044 bytes read in 520 ms (9.3 MiB/s) 6968976 bytes read in 626 ms (10.6 MiB/s) Found mainline kernel configuration 33781 bytes read in 1019 ms (32.2 KiB/s) 4179 bytes read in 708 ms (4.9 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5069980 Bytes = 4.8 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 49b2a000, end 49fffc9c ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49ab9000, end 49b29fff ... OK Starting kernel ... After waiting for around 5 minutes, I tried to power cycle the board. The result was identical. I can boot up the stock Android from the eMMC successfully. Nicely work also a Debian and Raspbian official images. Nevertheless, they cannot access the eMMC so that I can install Armbian on it. I tried a few different versions of Armbian on the same and on an older but tested 4GB microSD card: Armbian_5.25_Orangepiplus_Debian_jessie_default_3.4.113.img. The board does not boot properly: U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:04:04) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.01-armbian (Feb 02 2017 - 03:04:04 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 6944 bytes read in 156 ms (43 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2652 bytes read in 192 ms (12.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 123 bytes read in 132 ms (0 Bytes/s) 3789961 bytes read in 591 ms (6.1 MiB/s) 4754648 bytes read in 687 ms (6.6 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 36128 bytes read in 514 ms (68.4 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3789897 Bytes = 3.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 2048MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]! I also tried to mount the eMMC directly under Arch Linux using FEL using https://github.com/zador-blood-stained/fel-mass-storage. This did not work properly and I saw no devices using fdisk -l: U-Boot SPL 2016.09-armbian-fel-mass-storage-dirty (Sep 28 2016 - 12:21:11) DRAM: 2048 MiB Trying to boot from FEL U-Boot 2016.09-armbian-fel-mass-storage-dirty (Sep 28 2016 - 12:21:11 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 2 GiB Using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 (FEL boot) ## Executing script at 43100000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2229486 Bytes = 2.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 2048MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2004620! ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]! What am I doing wrong? Thank you in advance! Kind regards, Nikolay
  21. Hi, is WoL supported on orange pi? I have orange pi pc+ and ethtool shows letter d next to Supports Wake-on , cant turn it on. Maybe I need to compile module with support?
  22. I've tried to downgrade the kernel with the armbian-config tool, but now the opi+2 hangs while booting from emmc. I can boot via sd card, but i dont know how to fix the problem - please help.
  23. I am trying to switch legacy kernel to "next". I did it successfully with armbian-config for OrangePiPC (obviously Armbian was installed on SD card). Once I attempted to do the same with Orange Pi Plus and system installed onto internal EMMC then after reboot... nothing. I am wondering also if the issue is related to platform or the fact that Armbian was installed on EMMC. I have connected TTL2USB and following is the result (seems to be indefinite loop): U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 141 ms (25.4 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 21 bytes read in 161 ms (0 Bytes/s) MMC: no card present mmc_init: -123, time 2 ** Bad device mmc 0 ** 4578312 bytes read in 446 ms (9.8 MiB/s) 6972808 bytes read in 526 ms (12.6 MiB/s) Found mainline kernel configuration 33781 bytes read in 473 ms (69.3 KiB/s) 401 bytes read in 137 ms (2 KiB/s) Applying user provided DT overlay ds1307.dtbo ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4578248 Bytes = 4.4 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 49ba2000, end 49fffbc8 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49b31000, end 49ba1fff ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 44.940355] reboot: Restarting system U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device
  24. When 40pin female-female cable connected to my Orange Pi Plus 2 GPIO voltage on pin1 decreasing from 3.3v to ~ 1.6v WAIDW?
  25. Hi there, I am new here, and new to Armbian I have a Orange Pi Plus2 and I am trying to make a project to present Spotify as an iPod over USB, so that it can be used in vehicles / docks that support iPod connectivity via USB Some of this work has already been done here on the iPod USB gadget driver side https://github.com/oandrew/ipod-gadget Using the standard premade armbian builds I cannot compile the source code as the headers are missing. Therefore I compiled Armbian from source using INSTALL-HEADERS=yes, mainline Jessie. As there is no option for the Orange Pi Plus2 board, I used the Orange Pi plus config instead. The image boots, but the USB OTG appears disabled. dmesg | grep "musb" shows nothing. I played around with the device tree a bit sun8i-h3-orangepi-plus.dtb using the following: usb@01c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x2 0x20>; resets = <0x2 0x11>; interrupts = <0x0 0x47 0x4>; interrupt-names = "mc"; phys = <0x12 0x0>; phy-names = "usb"; extcon = <0x12 0x0>; status = "okay"; # changed linux,phandle = <0x39>; phandle = <0x39>; dr_mode = "otg"; # added }; I found this info from here: https://vjordan.info/log/fpga/nanopi-neo-usb-otg-with-armbian-mainline-4x-kernel.html After a reboot this seems to enable the OTG which was previously failed, and the ipod gadget loads, but when connecting to a PC nothing happens. [ 4.406064] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 4.406073] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 9 [ 4.406276] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002 [ 4.406283] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.406288] usb usb9: Product: MUSB HDRC host driver [ 4.406294] usb usb9: Manufacturer: Linux 4.14.36-sunxi musb-hcd [ 4.406299] usb usb9: SerialNumber: musb-hdrc.1.auto ............................................... [ 207.167207] g_ipod gadget: = ipod_config_ptp_bind() [ 207.167377] ipod-gadget-hid: alloc_chrdev_region dev: 242 0 [ 207.167391] ipod-gadget-hid: ipod_hid_alloc() [ 207.167608] g_ipod gadget: = ipod_config_bind() [ 207.167614] g_ipod gadget: = ipod_audio_bind() [ 207.173180] g_ipod gadget: = ipod_hid_bind(), deactivs=1 [ 207.173201] g_ipod gadget: g_ipod ready I also tried the sun8i-h3-orangepi-plus-2e.dtb as suggested on this page http://linux-sunxi.org/Xunlong_Orange_Pi_Plus_2 but no difference. I think it might have something to do with vbus - but its going overhead a little I appreciate the iPod gadget might be complicating things, so if someone could help me out with just getting something simpler working I would be very appreciative. Thanks Daniel
×
×
  • Create New...