Jump to content

Search the Community

Showing results for tags 'orangepilite2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • 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
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Skype


Github


Location


Interests

  1. Hi, I am unable to build any images for orangepi SOCs specifically orangepilite, orangepilite2 and one plus. Always returned error halfeway. Following is a sample of log when I compile image for orange pi lite. Please me some guidance on how to resolve this. My steps: run sudo compile.sh -- "Do no tchnage the kernel..." --> "orangepilite"--> either current or legacy --> either "buster" -->"Image with console inter..." -->"Standard image with ..."compilation.log
  2. Can someone please add support for the onboard microphone to armbian for the Lite2?! It is missing in armbian-config, there is no h6-analog-codec.dtbo in /boot/dtb/allwinner/overlay The microphone is wired up the same way as on the other h6 boards. Thank you very much!
  3. There is a patched version that enables noscan=1 , but the one I'm using seems like it hasn't been patched. When there is no AP's around HT40 kicks in ok without noscan=1. With noscan=1 and AP's are around hostapd won't even start in HT20 mode. Any help? root@orangepilite2:~# modinfo 88x2bu|grep version: version: v5.8.7.1_35809.20191129_COEX20191120-7777 srcversion: 43C721C4A870A632EBDE0B5 parm: rtw_chip_version:int root@orangepilite2:~# uname -a && hostapd -v Linux orangepilite2 5.4.43-sunxi64 #20.05.2 SMP Tue Jun 2 17:20:17 CEST 2020 aarch64 GNU/Linux hostapd v2.9 User space daemon for IEEE 802.11 AP management, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator Copyright (c) 2002-2019, Jouni Malinen <j@w1.fi> and contributors
  4. Hi! I use this board since jun/2019 with Armbian 5.90 and kernel 5.1.15 (all OK except HDMI audio). In these 6 months tried to update kernel image few times, 5.2.x some months ago and now 5.5.0, but not more 1920x1080 support, the maximum is 1280x1024. Xrandr not show as supported mode anymore, whats happen? This is related to u-boot? I think can not read EDID, because no monitor model name is shown. Another question is, now in 5.5.x I can see HDMI audio device, but still can't listen, what left to be developed?
  5. In an effort to enable Bluetooth on the OrangePi (Lite2 | 3) I am stuck at enabling UART1 via overlay. According to the schematics, the AP6255 is connected via UART1 (PG6-PG9) to the H6 SoC but not defined in the dtb. Since there is a dtbo which looks promising at /boot/dtb/allwinner/overlay/sun50i-h6-uart1.dtbo I tried adding an overlay to /boot/armbianEnv.txt - manually and via armbian-config. Both did not work out. In addition, I also tried adding uart1 to the dtb, without success. What am I missing?
  6. Is there way to configure sound over hdmi? Display is working ok (configuration for 1366x768 and 1920x1080 was made manually), but there is no sound.
  7. Linux orangepilite2 5.9.8-sunxi64 #ifb SMP Fri Nov 20 20:38:13 EST 2020 aarch64 aarch64 aarch64 GNU/Linux After trying to load batman-adv module i get the error Segmentation fault. This is the dmesg output of the error that occurs: [ 952.114742] Unable to handle kernel paging request at virtual address ffff800026beb000 [ 952.122734] Mem abort info: [ 952.125603] ESR = 0x96000006 [ 952.128674] EC = 0x25: DABT (current EL), IL = 32 bits [ 952.134042] SET = 0, FnV = 0 [ 952.137123] EA = 0, S1PTW = 0 [ 952.140328] Data abort info: [ 952.143261] ISV = 0, ISS = 0x00000006 [ 952.147150] CM = 0, WnR = 0 [ 952.150165] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041308000 [ 952.156920] [ffff800026beb000] pgd=0000000077fff003, p4d=0000000077fff003, pud=0000000077ffe003, pmd=0000000000000000 [ 952.167593] Internal error: Oops: 96000006 [#1] SMP [ 952.172482] Modules linked in: batman_adv(OE+) fuse algif_hash algif_skcipher af_alg bnep bridge r8152 88x2bu(OE) snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec hci_uart btqca btrtl btsdio btbcm brcmfmac btintel bluetooth brcmutil cfg80211 ecdh_generic rfkill ecc sunxi_cedrus(C) videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common videodev panfrost gpu_sched sun8i_ce mc crypto_engine display_connector cpufreq_dt uas i2c_mv64xxx [ 952.213199] CPU: 2 PID: 3177 Comm: modprobe Tainted: G C OE 5.9.8-sunxi64 #ifb [ 952.221463] Hardware name: OrangePi Lite2 (DT) [ 952.225911] pstate: 40000005 (nZcv daif -PAN -UAO BTYPE=--) [ 952.231530] pc : batadv_hard_if_event+0x220/0x7a8 [batman_adv] [ 952.237393] lr : batadv_hard_if_event+0x20c/0x7a8 [batman_adv] [ 952.243225] sp : ffff80001150ba50 [ 952.246540] x29: ffff80001150ba50 x28: ffff80001150bdc0 [ 952.251854] x27: 0000000000000100 x26: ffff8000100e38c8 [ 952.257167] x25: 0000000000000003 x24: 0000000000000000 [ 952.262479] x23: ffff800011495048 x22: 0000000000000001 [ 952.267792] x21: 0000000000000000 x20: ffff0000348f5000 [ 952.273105] x19: 0000000000000005 x18: 0000000000000000 [ 952.278418] x17: 0000000000000000 x16: 0000000000000000 [ 952.283730] x15: 0000005138b2fcae x14: 000000000000015b [ 952.289044] x13: 0000000000000130 x12: 0000000000000000 [ 952.294355] x11: 0000000000000000 x10: 0000000000000001 [ 952.299667] x9 : 000000000000015e x8 : ffff000037d962c0 [ 952.304979] x7 : ffff000034c65d80 x6 : 0000000000000000 [ 952.310291] x5 : ffff800010ff62c0 x4 : ffff80000939c888 [ 952.315604] x3 : ffff0000348f5000 x2 : 0000000000000000 [ 952.320917] x1 : ffff800026beb000 x0 : ffff800026beb000 [ 952.326230] Call trace: [ 952.328723] batadv_hard_if_event+0x220/0x7a8 [batman_adv] [ 952.334219] call_netdevice_register_net_notifiers+0x58/0x108 [ 952.339963] register_netdevice_notifier+0x94/0x130 [ 952.344846] batadv_init+0xf4/0x130 [batman_adv] [ 952.349459] do_one_initcall+0x54/0x1b8 [ 952.353290] do_init_module+0x54/0x200 [ 952.357032] load_module+0x1f88/0x2550 [ 952.360775] __do_sys_finit_module+0xb4/0x120 [ 952.365125] __arm64_sys_finit_module+0x20/0x30 [ 952.369650] el0_svc_common.constprop.0+0x6c/0x168 [ 952.374433] do_el0_svc+0x24/0x90 [ 952.377743] el0_sync_handler+0x90/0x198 [ 952.381659] el0_sync+0x158/0x180 [ 952.384974] Code: 54fff6c1 d538d081 f9425e80 8b010000 (885f7c03) [ 952.391061] ---[ end trace 468e2b20acac28b8 ]---
  8. Hi, I just wanted to report this bug. Latest Armbian Buster images for OPi Lite 2 don't work. When they're booted up, it takes 30 seconds for the device to freeze completely. The screen, keyboard, network, everything is frozen after less than a minute. I downgraded to a release from a month ago and it boots up correctly.
  9. Hello I have Opi lite 2 + 28byj-48 driver and step motor, and I want to play around, but can't find RPi.GPIO for OPi lite 2, how can I make it work ? I find pretty good example with raspberry pi http://www.raspberryproject.pl/en/automation/28byj-48-stepper-motor-raspberry-pi/ , I rearranged GPIOs to fit my board but I have error: File "testy.py", line 4, in <module> import RPi.GPIO as GPIO ModuleNotFoundError: No module named 'RPi' Welcome to ARMBIAN 5.67.181116 nightly Ubuntu 18.04.1 LTS 4.19.2-sunxi64
  10. I bought an orange pi lite 2 and I would like to use it with the ADC MCP3008 but when executing the code in python using the spidev library, it always returns the value of 1023 and when I disconnect the ADC it keeps showing the same value, it is as if there was no communication , The ADC is not the one with the problem since I tried it with an arduino mega and it works perfectly, it is in the orange pi lite 2 where it does not work. the connections are: VDD=3.3V VREF=3.3V AGND=GND CLK= (PC00) SPIO_CLK DOUT=(PC03) MISO DINT=(PC02) MOSI CS = (PC05) SPI0_CS0 DGND= GND import spidev import time spi = spidev.SpiDev() spi.open(0, 0) def read() adc = spi.xfer2([1,8<<4,0]) data = ((adc[1] & 3) << 8) + adc[2] return data while True: print(====================) print(read()) time.sleep(0.5) The only thing that returns is 1023 always if I have the spidev0.0 my armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h6 rootdev=UUID=07e078d5-15c7-4e03-8ec7-edf62ab350ed rootfstype=ext4 overlays=spi-spidev w1-gpio param_spidev_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u check the connection more than once, I don't know if the pins of MOSI, MISO, CLK and CS0; They are well configured with the ADC, I support myself for the connection with the following image. I speak Spanish, so I used google translator, therefore I apologize if I do not explain myself well.
  11. Linux orangepilite2 5.4.43-sunxi64 #20.05.2 SMP Tue Jun 2 17:20:17 CEST 2020 aarch64 GNU/Linux I have managed by accident to get full USB3 speed on orange pi lite 2. I have bought a USB3 hub: "Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub" , I have no idea which chip it has, it is in an aluminum case and looks like the one on the attached picture but black. By attaching atleast two usb devices in the hub USB3 somehow gets into full speed mode, one of them has to be USB2 device. I have managed to get with all devices I have ATM about 2000Gbs including iperf in both directions with rtl8153, hdparm -t on two usb2 memory sticks and one usb3 hard disk that got around 130MBs read. All devices were pumping speed test at once. If there is a USB3 speed test I could do without attaching any usb3 devices I would like to try it to see how fast can it go.
  12. Hi all, Recently i have purchased an orange pi lite2 board(H6) for codec audio streaming.I would like to establish the interface between Orange pi Lite 2 (H6) and AC108(codec board) for audio recording.I have downloaded Android source code and start making changes in Fex file, but couldn't get any luck. I am confusing in which I2S driver need to be used for H6 to communicate with codec (AC108). I am totally new to orange pi boards. so, please clarify following doubts... 1).which i2s driver needs to be map with codec(AC108) driver? 2).what all changes are required in Fex file? 3).How to set sysclk, clkdiv, fmt ? Please clarify above doubts. regards akash.
  13. Hello, can anyone share his hostapd.conf where he managed to get HT40 "width: 40 MHz" running on orange pi lite 2 while it is in AP mode ?
  14. Hi I would like to know whether I can use orange pi lite 2 image on orange pi one plus. I tried it but eth0 is not visible. Is there a way to tweak it? The reason is I want to create an image with various packages installed. So that i do not need to maintain 2 sd images since both are H6. Tq
  15. Dear community, Im trying to get an USB gadget via OTG running on Linux (OrangePI Lite 2). As OPI Lite 2 doesn't support 'USB-UART/Gadget mode' like OPI Zero, I just modify the build config and rebuild kernel by myself as steps shown below. 1. I change the mode of USB from host to otg in the: https://github.com/armbian/build/blob/master/patch/kernel/sunxi-current/board-h6-orangepi-lite2-fix-missing-all.patch 2. I add MODULES_CURRENT="g_serial" & SERIALCON="ttyS0,ttyGS0" to build/config/boards/orangepilite2.conf file. 3. I rebuild the kernel and flashed the new image to sdcard. Unfortunately, I find it doesn't work, the WIN10 does find a USB device but cannot recognize it. In win10 device manager, it shows "Unknown USB Device (Device Descriptor Request Failed)" I was wondering if anyone tried 'USB-UART/Gadget mode' in OPI Lite2, could you help give some suggestions? Here is some messages when I tried debug this issue: root@orangepilite2:~# cat /etc/modules g_serial root@orangepilite2:~# dmesg | grep gadget [ 5.955959] g_serial gadget: Gadget Serial v2.4 [ 5.955967] g_serial gadget: g_serial ready root@orangepilite2:~# ls /sys/bus/platform/devices/sunxi_usb_udc/ ls: cannot access '/sys/bus/platform/devices/sunxi_usb_udc/': No such file or directory root@orangepilite2:~# ll /sys/kernel/config/usb_gadget/ total 0 root@orangepilite2:~# ls /sys/class/udc musb-hdrc.5.auto root@orangepilite2:~# ls /dev/tty* /dev/tty /dev/tty2 /dev/tty31 /dev/tty43 /dev/tty55 /dev/ttyGS0 /dev/tty0 /dev/tty20 /dev/tty32 /dev/tty44 /dev/tty56 /dev/ttyS0 /dev/tty1 /dev/tty21 /dev/tty33 /dev/tty45 /dev/tty57 /dev/ttyS2 /dev/tty10 /dev/tty22 /dev/tty34 /dev/tty46 /dev/tty58 /dev/ttyS3 /dev/tty11 /dev/tty23 /dev/tty35 /dev/tty47 /dev/tty59 /dev/ttyS4 /dev/tty12 /dev/tty24 /dev/tty36 /dev/tty48 /dev/tty6 /dev/ttyS5 /dev/tty13 /dev/tty25 /dev/tty37 /dev/tty49 /dev/tty60 /dev/ttyS6 /dev/tty14 /dev/tty26 /dev/tty38 /dev/tty5 /dev/tty61 /dev/ttyS7 /dev/tty15 /dev/tty27 /dev/tty39 /dev/tty50 /dev/tty62 /dev/tty16 /dev/tty28 /dev/tty4 /dev/tty51 /dev/tty63 /dev/tty17 /dev/tty29 /dev/tty40 /dev/tty52 /dev/tty7 /dev/tty18 /dev/tty3 /dev/tty41 /dev/tty53 /dev/tty8 /dev/tty19 /dev/tty30 /dev/tty42 /dev/tty54 /dev/tty9
  16. Hello, I am trying to use g_serial but it does not work. I'm using fresh install of armbian (Armbian_5.38_Orangepilite_Debian_stretch_next_4.14.14.7z), with apt-get update/apt-get upgrade/armbianconfig Install headers. Linux orangepilite 4.14.15-sunxi #28 SMP Mon Jan 29 07:24:48 CET 2018 armv7l GNU/Linux This is the overlay I use to enable OTG: sudo /usr/sbin/armbian-add-overlay usbotg.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "otg"; status = "okay"; }; }; }; After rebooting OPi there are several errors like this in syslog musb_g_ep0_irq 712: SetupEnd came in a wrong ep0stage out/status The other computer is running Ubuntu 16.04 LTS I use small USB hub (full speed only) between my PC and OPi lite but if I make direct connection the errors are same. If I unplug and plug USB cable between OrangePi Lite and my computer (or if I plug the cable after OPi boots) I get same errors. I got same errors when trying with .g_ether usb 7-2.1: new full-speed USB device number 4 using uhci_hcd usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: new full-speed USB device number 5 using uhci_hcd usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: new full-speed USB device number 6 using uhci_hcd usb 7-2.1: device not accepting address 6, error -71 usb 7-2.1: new full-speed USB device number 7 using uhci_hcd usb 7-2.1: device not accepting address 7, error -71 usb 7-2-port1: unable to enumerate USB device The result of sudo armbianmonitor -u is here http://ix.io/Fcb Regards
  17. Hello Armbian team, I must start by thanking you for the effort you put into Armbian and making it possible for us to get the best of our boards. Your work is appreciated! The problem that I have been facing is that my OPI lite 2 functions correctly when it boots, but after a while I see a couple of sunxi-mmc errors in the logs and the filesystem becomes inaccessible and the board unusable. The log entries look like this: [ 750.827959] sunxi-mmc 4020000.mmc: data error, sending stop command [ 751.824422] sunxi-mmc 4020000.mmc: send stop command failed I cannot pinpoint the source of the problem as multiple issues seem to play a role in the behaviour. The board seems to overheat quite quickly (in 10 mins while sitting idle) before the errors start to occur What I have tried and observed: I have tried multiple images (debian and ubuntu) and all led to the same problem The overheating problem means that the temperatures get 75°C without any real load on the CPU It seems that the IO problems with accessing the SD start when the board is at about 62°C Celsius The overheating seems to me to be related to network activity - as it seemed to me, that the board did not overheat that dramatically when not connected to my wireless network, but I need the WIFI connection so I kept it on. Here are the logs generated when using a the current debian buster image by 'armbianmonitor -u' http://ix.io/2lhb I can see multiple pin errors when booting the board in the logs reported by sun50i-h6-pinctrl, and sunxi-mmc probably related to port 192? I would appreciate any help or hints how to narrow down the problem or solve it if possible ;-) Best regards, robert
  18. firmware version: Armbian_20.02.1_Orangepilite2_bionic_current_5.4.20.img ================= cmd log [dengzy@opl2 ~]$ sudo modprobe sunxi-cir [dengzy@opl2 ~]$ lsmod | grep cir 2:sunxi_cir 16384 0 3:rc_core 45056 1 sunxi_cir [dengzy@opl2 ~]$ ls /dev/input/ by-path event0 mice [dengzy@opl2 ~]$ evtest No device specified, trying to scan all of /dev/input/event* Not running as root, no devices may be available. Available devices: /dev/input/event0: axp20x-pek Select the device event number [0-0]: ^C [dengzy@opl2 ~]$ ================= Also no new log in dmesg when I excute modprobe, looks like sunxi-cir.ko failed to probe (dtb file not been modified) I also tried install lirc in armbian-config, it will create a uinput device, but still, when I use evtest to test my remote controler, nothing happend. Any help to make my controller work will be greatly appreciated!
  19. I cannot get the screen to rotate 90 or 270 degrees. Inverting it works like it should, but not "sideways". uname -a: Linux orangepilite2 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 GNU/Linux xrandr --version: xrandr program version 1.5.0 xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 /etc/X11/xorg.conf.d/01-armbian-defaults.conf: Section "Monitor" Identifier "Monitor0" Option "DPMS" "false" Option "Rotate" "right" EndSection Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection Screen is in "normal" orientation regardless of the rotate right option in the xorg conf. xrandr -o inverted works like it should and is noted in the xrandr output. Similarly with "normal". "right" and "left" however, do nothing. Or more precisely, they turn the display black for 1-2 seconds and then it returns to "normal" and displays the normal xrandr output, no "right" or "left" after resolution. echo <number> sudo tee /sys/class/graphics/fbcon/rotate_all works perfectly for all rotations on the console however. But of course it does not rotate X. EDIT: xrandr --output HDMI-1 --mode 848x480 works perfectly and sets the resolution like it should. xrandr --output HDMI-1 --mode 848x480 --rotate right does not. It blanks the display for 2 seconds, resets rotation to normal and resolution to 1024x7688, regardless of what they were before.
  20. Hi, I have two OrangePi Lite running side by side. After working fine for about 8 months both started to experience same issue with wireless: The board works randomly for few hours or few days and then looses wireless connection. When this happens reboot does not help as then issue occurs immediately after the boot. Unplugging and replugging power source resolves that for a while and then happens again I suspect it may not be related to a hardware issue or wireless hotspot, as I have at least 3 other clients that continue to work fine. Searching for it on the internet brought this issue with Raspberry Pi: https://github.com/raspberrypi/linux/issues/1988. Raspberry uses different wireless chipset either. All that makes me think this may be an issue in the kernel itself Any ideas or thoughts? Workaround also appreciated Thanks
  21. Is it normal? Why Couldn't get bank PG regulator U-Boot SPL 2019.10-armbian (Feb 17 2020 - 08:31:10 +0100) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):572fcdd-dirty NOTICE: BL31: Built : 08:31:00, Feb 17 2020 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc07ef00, model: OrangePi Lite 2 INFO: ARM GICv2 driver initialized INFO: PMIC: Probing AXP805 on I2C INFO: PMIC: aldo1 voltage: 3.300V INFO: PMIC: aldo3 voltage: 3.300V INFO: PMIC: bldo1 voltage: 1.800V INFO: PMIC: bldo2 voltage: 1.800V INFO: PMIC: bldo3 voltage: 1.800V INFO: PMIC: cldo1 voltage: 3.300V INFO: PMIC: dcdcd voltage: 0.960V INFO: PMIC: dcdce voltage: 1.200V INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.10-armbian (Feb 17 2020 - 08:31:10 +0100) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi Lite 2 DRAM: 1 GiB MMC: mmc@4020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3033 bytes read in 6 ms (493.2 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 291 bytes read in 5 ms (56.6 KiB/s) 32785 bytes read in 14 ms (2.2 MiB/s) 4161 bytes read in 15 ms (270.5 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 44000000 7655747 bytes read in 775 ms (9.4 MiB/s) 15687688 bytes read in 1579 ms (9.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7655683 Bytes = 7.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 498b2000, end 49fff103 ... OK Loading Device Tree to 0000000049841000, end 00000000498b1fff ... OK Starting kernel ... [ 2.297662] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.304821] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 198 [ 2.311791] sun50i-h6-pinctrl 300b000.pinctrl: pin-198 (5000400.serial) status -517 [ 2.319453] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 198 (PG6) from group PG6 on device 300b000.pinctrl [ 2.330321] dw-apb-uart 5000400.serial: Error applying setting, reverse things back [ 2.541572] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.548826] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 192 [ 2.555873] sun50i-h6-pinctrl 300b000.pinctrl: pin-192 (4021000.mmc) status -517 [ 2.563357] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 192 (PG0) from group PG0 on device 300b000.pinctrl [ 2.574353] sunxi-mmc 4021000.mmc: Error applying setting, reverse things back [ 2.582052] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator [ 2.589282] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 70 [ 2.596240] sun50i-h6-pinctrl 300b000.pinctrl: pin-70 (300b000.pinctrl:70) status -517 [ 2.604594] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.611819] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 198 [ 2.618865] sun50i-h6-pinctrl 300b000.pinctrl: pin-198 (5000400.serial) status -517 [ 2.626612] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 198 (PG6) from group PG6 on device 300b000.pinctrl [ 2.637601] dw-apb-uart 5000400.serial: Error applying setting, reverse things back [ 2.647257] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.654501] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 192 [ 2.661550] sun50i-h6-pinctrl 300b000.pinctrl: pin-192 (4021000.mmc) status -517 [ 2.669035] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 192 (PG0) from group PG0 on device 300b000.pinctrl [ 2.680023] sunxi-mmc 4021000.mmc: Error applying setting, reverse things back [ 2.687515] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator [ 2.694750] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 70 [ 2.701718] sun50i-h6-pinctrl 300b000.pinctrl: pin-70 (300b000.pinctrl:70) status -517 [ 2.710085] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.717319] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 198 [ 2.724368] sun50i-h6-pinctrl 300b000.pinctrl: pin-198 (5000400.serial) status -517 [ 2.732120] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 198 (PG6) from group PG6 on device 300b000.pinctrl [ 2.743111] dw-apb-uart 5000400.serial: Error applying setting, reverse things back [ 2.752766] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 2.760001] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 192 [ 2.767060] sun50i-h6-pinctrl 300b000.pinctrl: pin-192 (4021000.mmc) status -517 [ 2.774548] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 192 (PG0) from group PG0 on device 300b000.pinctrl [ 2.785544] sunxi-mmc 4021000.mmc: Error applying setting, reverse things back [ 3.075680] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator [ 3.083006] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 70 [ 3.090009] sun50i-h6-pinctrl 300b000.pinctrl: pin-70 (300b000.pinctrl:70) status -517 [ 3.098672] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 3.105942] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 198 [ 3.113041] sun50i-h6-pinctrl 300b000.pinctrl: pin-198 (5000400.serial) status -517 [ 3.120854] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 198 (PG6) from group PG6 on device 300b000.pinctrl [ 3.131907] dw-apb-uart 5000400.serial: Error applying setting, reverse things back [ 3.142360] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 3.149644] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 192 [ 3.156704] sun50i-h6-pinctrl 300b000.pinctrl: pin-192 (4021000.mmc) status -517 [ 3.164198] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 192 (PG0) from group PG0 on device 300b000.pinctrl [ 3.175201] sunxi-mmc 4021000.mmc: Error applying setting, reverse things back [ 3.184840] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator [ 3.192143] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 70 [ 3.199107] sun50i-h6-pinctrl 300b000.pinctrl: pin-70 (300b000.pinctrl:70) status -517 [ 3.199593] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 3.214352] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 198 [ 3.214358] sun50i-h6-pinctrl 300b000.pinctrl: pin-198 (5000400.serial) status -517 [ 3.229144] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 198 (PG6) from group PG6 on device 300b000.pinctrl [ 3.229150] dw-apb-uart 5000400.serial: Error applying setting, reverse things back [ 3.250438] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PG regulator [ 3.257692] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 192 [ 3.257699] sun50i-h6-pinctrl 300b000.pinctrl: pin-192 (4021000.mmc) status -517 [ 3.257706] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 192 (PG0) from group PG0 on device 300b000.pinctrl [ 3.272233] sunxi-mmc 4021000.mmc: Error applying setting, reverse things back Armbian 20.02.1 Buster ttyS0 orangepilite2 login:
  22. Thank you for bringing USB3 to life on the lite2 again!
  23. Hello everyone, I've got an orange pi pite 2, I install in my sd card armbian, it start but when I login and create a new account and reboot, I see termianl and not the desktop of armbian, If i reboot it ask me again to login, but I can'f see the terminal.... PLEASE HELP....... THANKS
  24. The problem I have an USB endoscope camera that works fine with my Orange Pi lite's normal USB port. However I need both USB port for other devices, so I want to connect this same USB camera, which was orginally marketed as USB otg camera for android phones, using Opi lite's micro usb otg connector. What have I tried - In armbian-config menu, I have enabled usbhost0. I believe this overlay is for the usb otg port, but just to be sure I also enabled usbhost1, usbhost2 and usbhost3. - Using dtc I decompiled sun8i-h3-orangepi-lite.dtb into sun8i-h3-orangepi-lite.dtc. - In this dtc file, I looked up musb, and changed status = "disabled" to "okay", and added dr_mode = "host", like this usb@01c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x6 0x20>; resets = <0x6 0x11>; interrupts = <0x0 0x47 0x4>; interrupt-names = "mc"; phys = <0x18 0x0>; phy-names = "usb"; extcon = <0x18 0x0>; status = "okay"; linux,phandle = <0x47>; phandle = <0x47>; dr_mode = "host" }; - Again with dtc, I compiled the dts to dtb file which replaced the old one (I've made backup). - After reboot, this seemed to have done something root@orangepilite:~$ dmesg |grep musb [ 4.086014] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 4.086025] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 9 [ 4.086290] usb usb9: Manufacturer: Linux 4.14.78-sunxi musb-hcd [ 4.086295] usb usb9: SerialNumber: musb-hdrc.1.auto However, when I connect the camera to the usb otg port, it doesn't work. The LED's on the camera doesn't turn on (so there is probably no power coming from the port, also there are no video devices on /dev/. How do I connect my camera to the micro usb port on Orange pi lite?
  25. Hi i have a problem trying to load the drivers of this camera, could you help me? Issue: mobprobe: FATAL: Module ov5647 not found in directory /lib/modules/4.14.84-sunix Board: Orange Pi Lite Camera sensor: OV5647 fisheye OS: Ubuntu - Armbian 5.65
×
×
  • Create New...