Jump to content

Search the Community

Showing results for tags 'odroidc2'.

  • 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


  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. Greetings. I'm running a headless cluster of Odroid C2's (eMMC) using the latest Armbian buster minimal image with kernel 4.19.69-meson64. I'm encountering an issue where it takes a long time for SSH connection to be accepted (initially up to 30 min consistently). I get a connection refused. The issue seems to be due to the entropy pool becoming depleted during the early boot process which blocks SSH from starting while it refills the pool. The problem seems to be known and documented well here: https://daniel-lange.com/archives/152-Openssh-taking-minutes-to-become-available,-booting-takes-half-an-hour-...-because-your-server-waits-for-a-few-bytes-of-randomness.html As suggested I have installed installed haveged which brings the SSH startup from 30 mins to 10 mins after boot, which is an improvement, but still not good. Has anyone else experienced this issue? Any ideas?
  2. I started to play with lima(mesa mali drivers) on Odroid C2 with ubuntu 19.04 with kernel 5.3. rc6 with lima enabled I add latest mesa drivers from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers there are only arm64 packages But there is problem on amlogic platform with order of dri/card* as dri/card0 point to lima and dri/card1 point to mesa drm driver but most software don't have options to set it up and they expect drm driver on card0 so there is problem in weston 5 for example https://lists.freedesktop.org/archives/wayland-devel/2018-September/039446.html but weston 4 and 6(https://packages.debian.org/sid/weston) is working fine so what is working in my case I was able to start weston4 like weston --drm-device=card1 then weston-simple-egl then glmark2-wayland so good luck with lima and panfrost it will be nice to test panfrost on odroid xu4 It will be nice to have simple options to enable lima/panfrost on armbian what do you think? It should be metter of enabling LIMA in kernel configs and add install mesa from oibaf ppa I asked him about armhf build be he talk about small amount of users lima gitlab issues https://gitlab.freedesktop.org/lima/mesa/issues
  3. After some hours of compiling I got OpenCV 4.1.1 running on Armbian Buster 64-bit. The SBC is an Odroid-C2. Thank you for this great OS-image.
  4. Using a cable such as this one, can we expect Armbian on the C2 to consistently assign the same serial designation to each cable port? It would be nice but probably not? I found this question and this one but I'm not sure what would be the best approach for my application. I'd like to do it 'The Armbian Way' if there is one. How would you ensure that each hardware device is assigned the same port each time? Thanks .
  5. Hello, A GPS module ublox is connected to a odroid c2 board on GPIOX.12 and GPIOX.13 for the RX and TX and GPIOX.10 for the PPS. The board is running the stable kernel 4.19.42-meson64 from Armbian based on Debian stretch which was dist-upgraded to Debian buster. I am trying to get the /dev/pps0 entry using GPIOX.10 to finish the chrony setup but I cannot find the correct syntax in the DTS file. Any pointer or idea ? I try either of the gpios line below, none of them seems to be correct. pps { gpios = "< 0x1e 0x66 0x0 >"; #gpios = "<&gpiox 10 GPIO_ACTIVE_HIGH>"; #gpios = "< 0x66 >"; assert-falling-edge; compatible = "pps-gpio"; }; The file include/dt-bindings/gpio/gxbb.h#L122 in the Linux kernel tree show the value of GPIOX.10 is set to 102 (aka 0x66 in hexa). After reboot, the pps-gpio module is loaded and cannot find the GPS connected. # dmesg | grep -i pps [ 1.414780] pps_core: LinuxPPS API ver. 1 registered [ 1.414783] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 5.460824] OF: /pps: could not find phandle [ 5.460835] pps-gpio pps: failed to get GPIO from device tree [ 5.460849] pps-gpio: probe of pps failed with error -22 The previous pps-gpio kernel module had the option for the gpio_pin which seems a bit easier to use :-/ Thank you.
  6. Hello, Recently I have discovered bug in kernel or maybe iptables with using Huawei E3372h LTE Hi-Link USB dongle (or maybe other devices which exposes HTTP interfaces over cdc_ether). Odroid enters into kernel panic and reboot. I am using ARMBIAN 5.85 stable Debian GNU/Linux 9 (stretch) 4.19.42-meson64. kernel:[ 60.801868] Internal error: Oops: 96000004 [#1] PREEMPT SMP The steps to recreate the bug: 1) disable or remove NetworkManager, use only IPv4, 2) set network interfaces in /etc/network/interfaces source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet static address netmask allow-hotplug enxXXX iface enxXXX inet dhcp enxXXX - is example name of your E3372h (virtual?) ethernet interface. 3) check settings in /etc/sysctl.conf - you need have some routing capabilites on - mine is: kernel.printk = 3 4 1 3 net.ipv4.conf.default.rp_filter=1 net.ipv4.conf.all.rp_filter=1 net.ipv4.tcp_syncookies=1 net.ipv4.ip_forward=1 net.ipv4.conf.all.accept_redirects = 0 net.ipv6.conf.all.accept_redirects = 0 net.ipv4.conf.all.secure_redirects = 0 net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv6.conf.all.accept_source_route = 0 net.ipv6.conf.all.disable_ipv6=1 net.ipv4.icmp_echo_ignore_broadcasts=1 net.ipv4.icmp_echo_ignore_all=1 vm.swappiness=100 4) set iptables rules to forward packets between local eth0 and usb dongle ethernet: *nat :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o enxXXX -j MASQUERADE COMMIT *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] :interfaces - [0:0] :open - [0:0] -A INPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT -A INPUT -j interfaces -A INPUT -j open -A INPUT -j DROP -A FORWARD -i enxXXX -o eth0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o enxXXX -p tcp -m multiport --dports 80,443,9001,9111,3690 -j ACCEPT -A FORWARD -i eth0 -o enxXXX -p icmp -m icmp --icmp-type 8 -j ACCEPT -A FORWARD -j DROP -A OUTPUT -j ACCEPT -A interfaces -i lo -j ACCEPT COMMIT 5) connect to local eth0 other computer (set static IP to eg., netmask and gateway, 6) from other computer you should be able to ping E3372h eth interface:, 7) open web browser (I have Firefox) - enter address: 8) after 5-10 seconds kernel panic occurs 9) after reboot there is a green background on screen via HDMI (need to hard power off and on to start without green screen). I have attached two fotos: 1 - kernel oops messages; 2 - green screen. Has anyone had a similar problem?
  7. Hello, I using up to date Armbian Stretch with kernel 4.19.41-meson64 #5.85 SMP PREEMPT Wed May 8 12:40:37 CEST 2019 aarch64 GNU/Linux. Today about 2 minutes after system boot I have found this warning in kernel log: May 12 07:51:48 xxx kernel: WARNING: CPU: 1 PID: 0 at kernel/time/hrtimer.c:917 hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: Modules linked in: cdc_ether usbnet uas xt_tcpudp nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_conntrack iptable_filter ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_connt May 12 07:51:48 xxx kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.41-meson64 #5.85 May 12 07:51:48 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) May 12 07:51:48 xxx kernel: pstate: 20000085 (nzCv daIf -PAN -UAO) May 12 07:51:48 xxx kernel: pc : hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: lr : txdone_hrtimer+0xd0/0x108 May 12 07:51:48 xxx kernel: sp : ffff00000800be20 May 12 07:51:48 xxx kernel: x29: ffff00000800be20 x28: ffff80007ff8a580 May 12 07:51:48 xxx kernel: x27: ffff00000891a6d8 x26: 0000000000000001 May 12 07:51:48 xxx kernel: x25: 0000000000000000 x24: 0000000000000001 May 12 07:51:48 xxx kernel: x23: ffff8000710c4be8 x22: 00000000000000f8 May 12 07:51:48 xxx kernel: x21: ffff8000710c4bb8 x20: ffff8000710c4ac0 May 12 07:51:48 xxx kernel: x19: 00000000000f4240 x18: 0000000000000000 May 12 07:51:48 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 May 12 07:51:48 xxx kernel: x15: 000000000000029a x14: 0000000000000400 May 12 07:51:48 xxx kernel: x13: 0000000000000001 x12: 0000000000000001 May 12 07:51:48 xxx kernel: x11: 0000000000ad3d80 x10: 0000000000000040 May 12 07:51:48 xxx kernel: x9 : ffff000008e93418 x8 : ffff800071400248 May 12 07:51:48 xxx kernel: x7 : ffff800071400288 x6 : 00000000d138f0b4 May 12 07:51:48 xxx kernel: x5 : 0000000000000001 x4 : ffff8000710c4be8 May 12 07:51:48 xxx kernel: x3 : 0000002116b3f554 x2 : 00000000000f4240 May 12 07:51:48 xxx kernel: x1 : 0000002116b3f76a x0 : 0000000000000216 May 12 07:51:48 xxx kernel: Call trace: May 12 07:51:48 xxx kernel: hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: __hrtimer_run_queues+0x120/0x1b8 May 12 07:51:48 xxx kernel: hrtimer_interrupt+0xd4/0x250 May 12 07:51:48 xxx kernel: arch_timer_handler_phys+0x28/0x40 May 12 07:51:48 xxx kernel: handle_percpu_devid_irq+0x80/0x138 May 12 07:51:48 xxx kernel: generic_handle_irq+0x24/0x38 May 12 07:51:48 xxx kernel: __handle_domain_irq+0x5c/0xb0 May 12 07:51:48 xxx kernel: gic_handle_irq+0x58/0xa8 May 12 07:51:48 xxx kernel: el1_irq+0xb0/0x128 May 12 07:51:48 xxx kernel: arch_cpu_idle+0x10/0x18 May 12 07:51:48 xxx kernel: do_idle+0x1d4/0x298 May 12 07:51:48 xxx kernel: cpu_startup_entry+0x20/0x28 May 12 07:51:48 xxx kernel: secondary_start_kernel+0x194/0x1d0 May 12 07:51:48 xxx kernel: ---[ end trace dcd1d1f08e0ad792 ]--- When it happened I had one USB device connected to ODROID - E3372h LTE modem (and it was online). But system working normally after that. I've never had such warning before (with previous kernel - 4.19.20). Maybe it has something to do with the last Armbian kernel update?
  8. Hello, I using up to date Armbian Stretch with kernel 4.19.41-meson64 #5.85 SMP PREEMPT Wed May 8 12:40:37 CEST 2019 aarch64 GNU/Linux. I started using TP-Link TL-WN722N V1 USB WiFi dongle recently. Unfortunately Armbian has crashed and rebooted once during I using such USB dongle. I tried to reproduce this bug once more but I can't. I have installed firmware-atheros package for this USB dongle. Should I install armbian-firmware-full package instead of firmware-atheros? It could help? Log:
  9. Hi, I compiled some images for C2 yesterday (mainline 5.77, jessie), and had a nice console as usual. Today, the new images still have u-boot console, and give some information about kernel starting, but no login by console (USB serial) is possible. I tried to set "console=serial" in /boot/armbianEnv.txt, but that gives me an endless reboot loop. Were there some changes? Maybe in baudrate? I get u-boot messages at 115200 8N1 as expected.. Michael
  10. Hi, I use the new kernel with I2CA being used for controlling some U/I meters and sensors. There are three 1Wire masters included by overlay (and they work ): > ls /sys/bus/w1/devices/ > 22-000000214032 28-00000a09aa8d w1_bus_master2 > 28-00000a089919 w1_bus_master1 w1_bus_master3 I2C works also fine, all devices mounted so far are answering: > i2cdetect -y 0 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- 0c -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: 40 41 -- -- -- 45 -- 47 48 -- 4a -- -- 4d -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- 6c -- -- -- > 70: -- -- -- -- -- -- 76 -- Then I access the GPIO subsystem to initialize one pin for power control: #! /bin/sh echo 475 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio475/direction echo 0 > /sys/class/gpio/gpio475/value After that, I2C access is screwed up, and no normal access possible: > i2cdetect -y 0 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f > 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f > 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f > 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f > 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f > 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f > 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f > 70: 70 71 72 73 74 75 76 77 This is kind of a showstopper - anyone can help here? Seems that activating the GPIO subsystem is touching the I2C pins on J2, too. Michael
  11. Hi, I use the C2 connector J2 signals to control power distribution for several attaches devices. A n-channel MOSFET is driven by a GPIO signal, with pulldown (3k3) to ensure that the n-channel MOSFET is off, - as long as the GPIO pin is in tristate or input state. I considered this to be the case for all "normal" GPIO lines (except I2C and SPI). I see now that after powerup, at least GPIOX_5 is active and switches on my load until I can export the GPIOX_5 and drive it low. Does anyone know if the GPIO lines are driven actively after powerup / reset? And if so, can this behaviour be changed in U-boot or kernel environment? The philosophy of the whole business is to keep everything shutdown except the C2 and the fiber media converter, so in case of bad things happening we can start without being disturbed by some external hardware. Another issue seems to happen with the new kernel: I power the C2 by the J2 pins (+5V), with J1 removed. Old kernel was off after a "shutdown -h now", the current one is rebooting after this command. This happens only if powered by J2 pins, not when powered by the small power connector - tested with two C2 boards now. Any ideas on that? Thanks in advance, Michael
  12. Now checked on Odroid C2 an image 5.76 with MALI and a media script, by a technique with replacement of u-boot, as for K2. Everything works fine. After installing the script, the standard browser began to play video 1080 full screen without brakes. MPV is just as easy to handle any full-screen video. Bonus has an in-house sound via HDMI. There is one caveat when configuring - it is necessary to specify the correct DTB option in the file for Odroid C2 "/extlinux/extlinux conf". 1. Copy of the standard u-boot from the working SD card. dd if=/dev/mmcblkXXX of=u-boot_odroid_c2.img bs=1M count=4 2. Burn the image Armbian for TV Boxing on the SD card. 3. Replace u-boot on the recorded SD card dd if=u-boot_odroid_c2.img of=/dev/mmcblk0 conv=fsync bs=1 count=442 dd if=u-boot_odroid_c2.img of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1 4. edit "/extlinux/extlinux conf" p.s. By the way, LibreELEC with the new 5.1 kernel works just as well on Odroid C2.
  13. Hi, On an Odroid C2, I used to read IP camera stream with ffmpeg without HW decoding, as it was not available yet. After reading many threads on this forum, regarding hw decoding through ffmpeg, I decided to give a try....but without any success. First of all, I tried to decode the Sintel.2010.720p.mkv file, and it worked well. This is the command I used: ffmpeg -c:v h264_v4l2m2m -i Sintel.2010.720p.mkv -an -vf fps=1 -f image2 -strftime 1 "/dev/shm/cam1_%S.jpg" (This takes a snapshot every second from the video file) And I got this output: [h264_v4l2m2m @ 0xaaaab68e84f0] driver 'meson-vdec' on card 'Amlogic Video Decoder' [h264_v4l2m2m @ 0xaaaab68e84f0] Using device /dev/video0 [h264_v4l2m2m @ 0xaaaab68e84f0] driver 'meson-vdec' on card 'Amlogic Video Decoder' Stream mapping: Stream #0:0 -> #0:0 (h264 (h264_v4l2m2m) -> mjpeg (native)) Press [q] to stop, [?] for help [h264_v4l2m2m @ 0xaaaab68e84f0] output POLLERR [swscaler @ 0xaaaab691f000] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to '/dev/shm/cam1_%S.jpg': Metadata: encoder : Lavf57.83.100 Chapter #0:0: start 0.000000, end 103.125000 Metadata: title : Chapter 01 Chapter #0:1: start 103.125000, end 148.667000 Metadata: title : Chapter 02 Chapter #0:2: start 148.667000, end 349.792000 Metadata: title : Chapter 03 Chapter #0:3: start 349.792000, end 437.208000 Metadata: title : Chapter 04 Chapter #0:4: start 437.208000, end 472.075000 Metadata: title : Chapter 05 Chapter #0:5: start 472.075000, end 678.833000 Metadata: title : Chapter 06 Chapter #0:6: start 678.833000, end 744.083000 Metadata: title : Chapter 07 Chapter #0:7: start 744.083000, end 888.032000 Metadata: title : Chapter 08 Stream #0:0(eng): Video: mjpeg, yuvj420p(pc), 1280x544 [SAR 1:1 DAR 40:17], q=2-31, 200 kb/s, 1 fps, 1 tbn, 1 tbc Metadata: encoder : Lavc57.107.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1 frame= 53 fps=3.4 q=4.8 Lsize=N/A time=00:00:53.00 bitrate=N/A speed=3.44x After that successfull test, I tried this from a CCTV RTSP stream : ffmpeg -stimeout 5000000 -c:v h264_v4l2m2m -i rtsp:// -an -vf fps=1 -f image2 -strftime 1 "/dev/shm/cam1_%S.jpg" and I got this output: [h264 @ 0xaaaadbc04330] corrupted macroblock 16 36 (total_coeff=-1) [h264 @ 0xaaaadbc04330] error while decoding MB 16 36 [h264 @ 0xaaaadbc04330] concealing 753 DC, 753 AC, 753 MV errors in I frame Guessed Channel Layout for Input Stream #0.1 : mono Input #0, rtsp, from 'rtsp://': Metadata: title : 10 Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: h264 (Baseline), yuvj420p(pc, bt709, progressive), 1280x720, 2.08 tbr, 90k tbn, 180k tbc Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s [h264_v4l2m2m @ 0xaaaadbd68c70] driver 'meson-vdec' on card 'Amlogic Video Decoder' [h264_v4l2m2m @ 0xaaaadbd68c70] Using device /dev/video0 [h264_v4l2m2m @ 0xaaaadbd68c70] driver 'meson-vdec' on card 'Amlogic Video Decoder' Stream mapping: Stream #0:0 -> #0:0 (h264 (h264_v4l2m2m) -> mjpeg (native)) Press [q] to stop, [?] for help [h264_v4l2m2m @ 0xaaaadbd68c70] output POLLERR [swscaler @ 0xaaaadbc47f60] deprecated pixel format used, make sure you did set range correctly [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. Output #0, image2, to '/dev/shm/cam1_%S.jpg': Metadata: title : 10 encoder : Lavf57.83.100 Stream #0:0: Video: mjpeg, yuvj420p(pc), 1280x720, q=2-31, 200 kb/s, 1 fps, 1 tbn, 1 tbc Metadata: encoder : Lavc57.107.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1 [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. [Parsed_fps_0 @ 0xaaaadbc668a0] Discarding initial frame(s) with no timestamp. Last message repeated 1 times frame= 0 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.00 bitrate=N/A speed= 0x video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown Output file is empty, nothing was encoded (check -ss / -t / -frames parameters if used) I am using the regular ffmpeg, installed through apt install. (No compilation from source). I am using the latest armbian ubuntu stable version: 4.19.20-meson64 #5.75 SMP PREEMPT Fri Feb 8 10:08:40 CET 2019 aarch64 aarch64 aarch64 GNU/Linux Any sugestions for using HW decoding over a RTSP stream? Thx Fabian
  14. Hi everyone, I'm trying to use the serial port on pins 8+10 on an ODroid C2. My understanding is that this maps to /dev/ttyS1 by default, but whenever I try to use this serial port, or any of ttyS0, S1, S2, S3, I get the error "Input/output error". root@odroidc2:~# stty raw -crtscts 9600 < /dev/ttyS1 stty: 'standard input': Input/output error root@odroidc2:~# cat /dev/ttyS1 cat: /dev/ttyS1: Input/output error I have done a lot of searching on this forum and others, and it sounds like this could be something I need to enable in my device tree config, or some kind of overlay, but I'm very new to this and couldn't find anything specific on what to do. I had a look around in the /boot directory but couldn't find anything that might indicate that the UART was disabled. I would have thought this /dev/ttyS1 would be enabled by default, while /dev/ttyS2 is optional since it collides with some GPIO pins. I'm using the latest Armbian_5.75_Odroidc2_Debian_stretch_next_4.19.20 and have also had the same problem with the latest Ubuntu as well. Is there a trick to enabling the default UART included with the ODroid C2? Thanks!
  15. I have a 4-port USB 2.0 hub powered by a 5V 3.1A power supply that does not show up on my C2, with or without devices connected to it. I have the C2's USB OTG port disabled as I use a DC power supply. $ sudo lsusb Bus 001 Device 004: ID 1df7:3010 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg does not log the hub connecting/disconnecting. How do I troubleshoot this? armbianmonitor -u: http://ix.io/1DzS
  16. Hello, I have 16GB orange eMMC v0.4 module for Odroid C2. I have installed on it Armbian Debian Stretch Next (mainline kernel). When I run iozone I got read results that is slower than eMMC Hardkernel specs. root@odroidc2:~# iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Iozone: Performance Test of File I/O Version $Revision: 3.429 $ Compiled for 64 bit mode. Build: linux Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner, Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone, Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root, Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer, Vangel Bojaxhi, Ben England, Vikentsi Lapa. Run began: Sun Feb 10 03:49:18 2019 Include fsync in write timing O_DIRECT feature enabled Auto Mode File size set to 102400 kB Record Size 4 kB Record Size 16 kB Record Size 512 kB Record Size 1024 kB Record Size 16384 kB Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 32953 36184 23772 23774 23679 25934 102400 16 39075 44064 42145 42258 41967 43945 102400 512 40897 41149 80160 80028 79930 41461 102400 1024 41512 41928 82305 82300 82167 42205 102400 16384 41108 43502 86202 86228 86214 43877 On Hardkernel Ubuntu when I run iozone I have max ~50 MB/s write and ~133MB/s read, but on Armbian only max ~86 MB/s read. Why is that?
  17. lm-sensors can read temps fine - $ uname -a Linux Odroid-C2 4.19.20-meson64 #5.75 SMP PREEMPT Fri Feb 8 10:08:40 CET 2019 aarch64 GNU/Linux $ sensors -u scpi_sensors-isa-0000 Adapter: ISA adapter aml_thermal: temp1_input: 39.000 But htop displays 0 C -
  18. Hello, I have installed Armbian Debian Stretch Next (mainline kernel) on my Odroid C2 and updated to newest version(apt update & apt upgrade). Everything works fine except USB ports. I have USB LTE modem which is not recognized. I have tried "lsusb -v" but with this modem not works. But when I connect USB keyboard first then "lsusb -v" and next I connect LTE modem and type "lsusb -v" then it's works. I also tried connecting USB LTE modem before Odroid C2 boot but this workaround not working. Is there any workaround which not involving connecting more than one USB device? Maybe usb kernel modules (usbcore, ehci_hcd, ...) compiled as external modules will help find workaround?
  19. Well, no fancy introduction here, because this doesn't pretend to be a script for the general use, only for testers who want to try the current *very early* status of the media capabilities in the Armbian meson mainline kernel. Warning: It will replace your current kernel with a pre-compiled nightly 4.19.20. Instructions: Download, untar and run. If you need further instructions, then you are not ready for this script (again, it is very unpolished, not for general use). Download link: https://mega.nz/#!YvYUhayC!CI1fl52V4tV0G4oqUib4W-NlMpVSpLDp8kmo74g-V08 Things that you can try with this script, on a X session: Use a 1080p@30fps h264 video, and play it with "mpv -hwdec <filename>". You'll see in the logs that it is decoding through v4l-m2mcopy Install and run glmark2-es2 Use Chromium WebGL Play a 1080p@30fps video in YouTube in full-screen smoothly. I'm pretty sure it is not really using HW decoding as it claims (there is no initialization message in dmesg), but it's smooth for sure. Gstreamer is tested not to work, in some other forum I was told that Bionic version is not enough and I need to compile a newer one. Performance is not in any way good, but it is a starting point. Anyway, the first TO-DO is getting the mali module integrated into the kernel, so there is no need to compile it separately.
  20. I'm currently running Armbian 5.60 on an Odroid C2. Tried the new mainline kernel version (5.71) on the weekend and everything looked fine at first, but when I got to starting one of my docker containers, it failed. This container uses armhf binaries. Is there some way of enabling armhf support with the new mainline kernel builds of Armbian, or do I need a custom build now? I installed docker via armbian-config. As far as I can remember, I did not have to do anything special to get this working on the 3.x kernel build... Any pointers in the right direction would be appreciated. Thanks and best regards, Ulrich
  21. Hi, I've downloaded and successfully installed Armbian_5.47_Odroidc2_Debian_stretch_default_3.16.57 on an Odroid C2 (eMMC) : HDMI output is working fine. Then I ran: apt-get update then apt-get upgrade then I got a message saying that the kernel has been updated and that I need to reboot. After the reboot, I have no HDMI output anymore. SSH is available and board seems to be working fine. For information, after the update: uname -a Linux jeedom 3.16.57-odroidc2 #72 SMP PREEMPT Wed Sep 19 12:32:15 CEST 2018 aarch64 GNU/Linux Tried this without success. I've tested with other cable and screen, no success.
  22. Hi All, I'm tring to make Ocroid C2 working with PiSound shield. https://github.com/BlokasLabs/pisound/tree/master/pisound-module I've compiled the module, an I'm able to install it properly. I've changed the DTS in this way --- pisound-overlay.dts 2019-01-22 23:28:59.460427794 +0000 +++ pisound-overlay_odroid.dts 2019-01-23 01:48:20.198204778 +0000 @@ -20,10 +20,9 @@ /dts-v1/; /plugin/; -#include <dt-bindings/gpio/gpio.h> - +#include "/usr/src/linux-headers-4.19.15-meson64/include/dt-bindings/gpio/gpio.h" / { - compatible = "brcm,bcm2708"; + compatible = "amlogic,meson-gxbb"; fragment@0 { target = <&spi0>; I've followed guide line here https://docs.armbian.com/User-Guide_Allwinner_overlays/ https://wiki.odroid.com/odroid-c2/application_note/gpio/spi#c2 https://forum.armbian.com/topic/8353-use-gpio-on-c2-with-mainline-kernel/ but still getting trouble. Do you've any tips? It spi0 the proper target to use? Do I need to displable something in C2 dts? thanks Federico
  23. Hi there, after updating the kernel to the latest version, the odroid-c2 only boots if a keyboard is present. If I disconnect the keyboard (which is and was the normal situation), on next reboot, I get a message "Enter root password for maintenance or press CONTROL-D to continue". Obviously, I'd greatly appreciate being able to boot my Odroid without having to connect a keyboard all the time. Best, Bastian
  24. Hi - I'm running kernel 4.18.8-odroidc2 under stretch and I've installed linux-headers-next-odroidc2 linux-source-4.18.8-next-odroidc2 where the kernel image was linux-image-next-odroidc2 The system in general rocks - I was worried about not being able to use my RTL8812AU in the monitor mode - but it works! But I have 2 issues with 4.18.8-odroidc2, first the RTC PCF8563 module. The .config file includes the following entries CONFIG_RTC_DRV_PCF85363=m # CONFIG_RTC_DRV_PCF8563 is not set The Odroid C2 RTC shield is the one not set, namely, the PCF8563 See https://www.hardkernel.com/shop/rtc-shield/ Now if I try to build the loadable module make ARCH=arm64 scripts make ARCH=arm64 distclean the last command generates the following error scripts/Makefile.clean:15: drivers/gpu/drm/nouveau/Makefile: No such file or director and if I just type make ARCH=arm64 make[1]: *** No rule to make target 'arch/arm64/kernel/vdso/gettimeofday.S', needed by 'arch/arm64/kernel/vdso/gettimeofday.o'. Stop. So I have to punt. I must be doing something wrong. Any help would be greatly appreciated! -- Cinaed
  25. Hi, I am trying to get the official Hardkernel RTC board working. This board requires the driver module "rtc-pcf8563.ko" which is not included in the image by default. So I went through the kernel compiling tutorial, to add this module to my "own" kernel, and copy it over to my main system. First problem: the kernel version was different: main system is at version 4.18.8, while the module was compiled for 4.18.20. I could fix this by myself be defining the KERNELBRANCH='tag:v4.18.8'. Second problem: the "linux family" has changed. My main system is at Armbian version 5.60 for family "odroidc2". The driver module was compiled for "meson64". Until now, I could not fix this. So when I try to load this module, this fails with "Exec format error". So basically three questions come to my mind: What can I do to fix the problem with the different linux families by myself? Is there another way to compile just a single driver module for a specific kernel version for a specific board/linux family? Or is this just the way to go to compile "everything at once"? What about adding the driver module for the PCF8563 to the kernel by default? Greetings, Jojo
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines