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

Product Groups

  • Misc
  • Support


  • Armbian
  • Armbian releases


  • Volunteering opportunities


  • Community Calendar


  • Official giveaways
  • Community giveaways


  • Members

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. 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
  2. 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
  3. --------Preamble------------ Tried Armbian on Opi pc, and fell in love with it! It feels like the O.S. for me! Tried to turn the c2 into the ultimate night stand alarm clock, with 7" screen, micro keyboard and tiny mouse, with speakers built in a customized re-purposed case running ubuntu for beside the bed . alarm-clock-applet is a favorite app on Rpi, works great, I live by it basically. but the c2 will not play audio with it, gstreamer-ugly download and then it works, but it whacks out the RTC. alarm works great on Opi with Armbian but no RTC. The RTC is a big part of the situation, experimentally powering with solar. All that time and money wasted on a great concept, this was the second attempt to find a use for the c2 other than a paper weight. I'm still a total newb.... --------------------------------- RTC on Odroid c2, Is it a similar process in Armbian? Is it a different repository? I have absolutely no idea what to do in armbian to make it work at least not with out some sort of example or at least a good path to start on, and searching produced no results, at least nothing understandable to me, But im really good at wrecking the linux O.S. when trying new things.... OS Requirements - Linux : Add the PCF8563 RTC driver c2 setup: n/a Enable RTC Shield odroid@odroid:~$ sudo apt install device-tree-compiler odroid@odroid:~$ sudo fdtput -t s /media/boot/meson64_odroidc2.dtb /i2c@c1108500/pcf8563@51 status "okay" odroid@odroid:~$ Now you have the RTC on ODROID-C2 running with the current date and time the next step is to make it load when the ODROID-C2 boots. Edit the modules file: odroid@odroid:~$ echo "aml_i2c"|sudo tee -a /etc/modules odroid@odroid:~$ cat /etc/modules aml_i2c odroid@odroid:~$ Add aml_i2c at the end of the file. Next you want to add the RTC on ODROID-C2 at boot by editing /etc/rc.local.odroid@odroid:~$ sudo nano /etc/rc.local if [ -f /aafirstboot ]; then /aafirstboot start ; fi hwclock -s exit 0 Reboot your ODROID-C2. --------------- I know the Rpi will do the job, but i have enough of them and dont want to get yet another untill the Rpi4..... If this wont work, is there an SBC with RTC option that works with Armbian? Thanx
  4. Hi, as the "huge eMMC" patch for Odroid C2 seems to work, I want to proceed now on PWM and SAR. I just installed a fresh system, and try to get both things working. Can someone give me a hint on which modules I need, and if some tweaking in device tree is needed? lsmod shows me that the SAR module seems to be present (meson_saradc), but I can't find the corresponding files on /sys/class/... Moreover, the meson_pwm.ko is present and can be modprobe'd, but I don't get any files unter /sys/class/pwm/ Any help is appreciated. Thanks in advance, Michael
  5. 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
  6. I used a stable Armbian Image (Armbian Stretch mainline kernel 4.18.y) for OdroidC2. The OS booted up normally but the USB hubs didn't detect the connected peripherals. The output of `lsusb` didn't show any of the connected peripherals. Thanks Sumit
  7. 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
  8. Hi all, I'm new to Linux and trying to set up a music server using my Odroid C2/Armbian/Cantata/MPD/HDMI sound. Got Armbian 5.60 (Stretch) 4.18.8 installed. Cantata sees the small test music library I set up on the C2 and appears to play tracks as the progress bar moves. I get no sound from the C2 connected HDMI monitor. (for initial testing only, i2s + DAC/Amp later). I tried the same set up using the Odroid Ubuntu/Mate desktop image a few days back and it worked straight out of the box. My suspicion is that the audio output settings in the mpd.conf are not correct (mpd 0.19.21). For HDMI sound output, does my version of Armbian use Pulse Audio or Alsa ? Could you give me some pointers as to what the audio output entries should be for MPD to give HDMI sound output?
  9. I think it would make sense to rename the forum section here from "Amlogic S905(x)" to "Amlogic". It would make much more sense for me to talk here for example about the Armbian port of the Odroid C0/C1/C1+ (Amlogic S805) then in any other forum section.
  10. Hi guys, some months ago I implemented an Odroid C2 as readout controller for a scientific instrument. Lot of people were kind and helped me with some problems with Armbian, especially eMMC and PWM. Today, finally, we managed to have our instrument (two strings with several Odroid C2 and other stuff) deployed. It is sitting now at 2628m depth in the Pacific Ocean, and will go operational the next days. Here we are... I think I can announce the deepest Odroid so far (cry loud if I'm wrong :) ) In the picture you just can see the Titanium housing with two glass covers attached to the string. Again, thanks for the fish :) Michael
  11. hi dear all i am MS student and want to make my own development board for S905. if i purchase components from market and make a pcb then is it work? any one can answer my question?
  12. Hi guys, I just recompiled my patches from old 2015 Uboot to the 2018 version, allowing setting the baud rate in Uboot (for accessing it by 9600 8N1), and saving envs in eMMC. First one works, I can switch easily baudrates now, but "saveenv" fails, spitting out a lot of error messages: => saveenv Saving Environment to EXT4... Card did not respond to voltage select! ** Bad device mmc 0 ** Failed (1) I also see that apparently the settings are being loaded from a wrong partition: U-Boot 2018.07-armbian (Oct 28 2018 - 10:43:58 +0100) odroid-c2 DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from EXT4... Card did not respond to voltage select! ** Bad device mmc 0 ** Failed (-5) In: serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Any ideas on that? Maybe eMMC disk layout changed? Any help is appreciated (if you need patches, I can post them here). Michael
  13. Hello, does anybody run above configuration successfully? If yes, what are the steps to make this happen? I did this: sudo apt install xorgxrdp xrdp But this is the result: xrdp (0.9.1-9+deb9u3) wird eingerichtet ... Generating 2048 bit rsa key... ssl_gen_key_xrdp1 ok saving to /etc/xrdp/rsakeys.ini Created symlink /etc/systemd/system/multi-user.target.wants/xrdp-sesman.service -> /lib/systemd/system/xrdp-sesman.service. Created symlink /etc/systemd/system/multi-user.target.wants/xrdp.service -> /lib/systemd/system/xrdp.service. A dependency job for xrdp.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript xrdp, action "start" failed. * xrdp.service - xrdp daemon Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:xrdp(8) man:xrdp.ini(5) Okt 25 17:19:24 oc2-e1 systemd[1]: Dependency failed for xrdp daemon. Okt 25 17:19:24 oc2-e1 systemd[1]: xrdp.service: Job xrdp.service/start failed with result 'dependency'. dpkg: Fehler beim Bearbeiten des Paketes xrdp (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zur?ck Trigger f?r systemd (232-25+deb9u4) werden verarbeitet ... Trigger f?r man-db ( werden verarbeitet ... xorgxrdp (0.9.1-9+deb9u3) wird eingerichtet ... Trigger f?r libc-bin (2.24-11+deb9u3) werden verarbeitet ... Fehler traten auf beim Bearbeiten von: xrdp E: Sub-process /usr/bin/dpkg returned an error code (1) Despite quite some time spent I have no glue, what 'dependency' might be missing. Appreciate any help. Hans
  14. Hi all am trying to make a router out of my odroid c2 using the mainline kernel but am trying to configure mini jumbo frames to support my PPPoE on a FTTP line but am getting errors from the kernel when attempting to enable the 1508MTU needed to support it. my question is do these adaptors support jumbo frames on any kernel or is it just the mainline kernel not supporting them.
  15. It seems the networking in Armbian 5.59 is messed up. It creates a eth0 adapter (disabled) and Wired network 1 adapter. You can delete these in nmtui, but they always return. I had the same issue with NanoPi Duo using mainline Stable. I can get it to work a bit using armbian-config, removing all interfaces and configuring IP, but it gets screwed up again. I cannot trust to run 5.59 headless because I have no way to get into the SBC without hooking video back up.
  16. Odroid C2: next and dev kernels do recognize USB hard-drives The stable kernel does. Kernel configuration issue?
  17. Is this https://forum.openmediavault.org/index.php/Thread/24299 a known issue with 5.60? In https://github.com/armbian/testings it's written that 'USB hot plugging' doesn't work which is something I'm fine with. But what does 'networking sometimes doesn't work' means exactly? @Igor since I've seen you submitted the test report. What does that mean wrt networking? Isn't the next branch meant as a 'stable' branch where basic functionality has to work flawlessly? Did networking work prior to 5.60 release?
  18. What would cause the following dialog to show up when running a binary? : No such file or directory When I run strace against the file I get the following for the execution command. execve("./spyserver", ["./spyserver"], [/* 20 vars */]) = -1 ENOENT (No such file or directory)
  19. Hi guys, After some time I get enough brave to do apt upgrade on my Odroid C2 (after month or two).. I updated following packages: Start-Date: 2018-08-07 11:09:56 Commandline: apt upgrade Install: html2text:arm64 (1.3.2a-18, automatic), debconf-utils:arm64 (1.5.56+deb8u1, automatic) Upgrade: ncurses-term:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), libtinfo5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), linux-dtb-odroidc2:arm64 (5.40, 5.54), libncurses5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), libncursesw5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), ncurses-bin:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), base-files:arm64 (8+deb8u10, 8+deb8u11), patch:arm64 (2.7.5-1, 2.7.5-1+deb8u1), libldap-2.4-2:arm64 (2.4.40+dfsg-1+deb8u3, 2.4.40+dfsg-1+deb8u4), linux-image-odroidc2:arm64 (5.40, 5.54), armbian-config:arm64 (5.40, 5.54), linux-u-boot-odroidc2-default:arm64 (5.40, 5.49), docker-ce:arm64 (18.05.0~ce~2.1.rc1-0~debian, 18.06.0~ce~2.1.rc1-0~debian), armbian-tools-jessie:arm64 (5.40, 5.44), tzdata:arm64 (2018d-0+deb8u1, 2018e-0+deb8u1), armbian-firmware:arm64 (5.40, 5.45), ncurses-base:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3) End-Date: 2018-08-07 11:10:45 After upgrade I am having freeze almost every 12 hours - not able to connect to the odroid via SSH (running headless) and I have to replug power (I am using official power adapter from Odroid via jack). Here is link to logs etc. any ideas what it could be? I will try to set up nmon or zabbix to monitor health of mem / cpu before crash.
  20. Hello armbian community, I am coming from the official Hardkernel minimal Ubuntu image to armbian (I need a newer kernel than the 3.16 in Hardkernel images). I'd like a headless setup, so I have downloaded and flashed what is inside Armbian_5.49_Odroidc2_Debian_stretch_next_4.17.3.7z. So far so good, the image boots to login prompt. However when I want to log in, the characters typed do not appear on the screen. I have tried several keyboards (one of them being the same keyboard I'm typing this post on so I know it works), both wired and wireless, connected directly or via a USB hub, still nothing. I've also tried flashing the desktop image from Armbian_5.49_Odroidc2_Debian_stretch_next_4.17.3_desktop.7z with the same result (a desktop does not come up, only CLI login, but that would not be an issue). I have also tried boot the C2, wait a few minutes and then just blindly type root<enter>1234<enter> - nothing happens. I went back to the Hardkernel image - all my keyboards work, no problem there. Any idea what to try or what could be wrong with my setup? Thank you!
  21. I run my ODROID C2 from eMMC, and after upgrading u-boot default to 5.38 booting no longer works. It looks like it cannot read the root partition and then reboots (and it will just keep rebooting). If I downgrade to u-boot 5.35 the system starts normally. This is the boot log from serial (first boot to start of the second): https://hastebin.com/raw/qajacahipe
  22. I have created a branch for amlogic device mainline u-boot, I have successfully booted le potato now, it took some small adjustments to support the 2015 boot script. Anyone wishing to try this use LIB_TAG="meson64-uboot" Next steps: use a proper boot script to take advantage of armbianEnv.txt and bring Le Potato to modernity. using C2 as pattern bring up mainline support for K2
  23. TL;DR: the following is a simple summary of the issue: Amlogic SoCs contain an own embedded microcontroller (Cortex-M3) used for controlling power and clocks A proprietary and closed source firmware is loaded on the M3 at boot. This stuff is contained in the bl30.bin blob we have to include This firmware controls the real clockspeeds, ignores what the cpufreq framework running in the Linux kernel wants and even reports back bogus clockspeeds (the kernel wants to set 1512 MHz, the M3 ignores this and sets 1416 MHz instead but the code returns faked 1512 MHz) Various tests showed that this is not related to thermal protection but just to $something we currently don't understand and out of our control Hardkernel are the only ones who managed to get a bl30.bin blob from Amlogic for their ODROID-C2 that does not cheat on us but honours the cpufreq framework, sets the wanted clockspeeds and also returns real and not faked cpufreq values. On all other Amlogic SBC situation is different Talking about 'not entirely honest' when it's about bold lies is funny It's some proprietary crap that controls DVFS on Amlogic SoCs (a bl30.bin BLOB loading some firmware on the embedded Cortex-M3 which controls DVFS/cpufreq on its own) and Hardkernel is the only vendor that got this BLOB from Amlogic in a way where the installation does not cheat on you. In case the BLOB does also DRAM initialization (most likely) it should be hard to exchange it between boards. https://forum.armbian.com/topic/2138-armbian-for-amlogic-s912/?do=findComment&comment=43338 (S912 and S905X are both known to cheat on the Linux kernel. The cpufreq values are all faked. Most probably this does also apply to all S905 devices except ODROID-C2 since Hardkernel managed to get a fixed BLOB from Amlogic)
  24. Odroid C2 Armbian 5.44 Ubuntu- Bionic XFCE 4.12/ - 1. system lost eth0 connection after 5 minutes work ( DHCP or Static number IP ) 2. sometimes not reboot properly - i have to unconnected from power
  25. Hi, with my Odroid C2 I experience a strange behaviour regarding Armbian Updates. Initially Armbian_5.38_Odroidc2_Debian_jessie_default_3.14.79 was installed, after installation I did an upgrade to Debian Stretch. Meanwhile a new Armbian version v5.44 / v5.45 with a newer Kernel is available for Odroid C2 devices. If I do "apt update" and "apt upgrade", a newer version isn't visible or would be installed? The system is stuck on v5.38 with Kernel 3.14.79: " Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 3.14.79-odroidc2 Linux lx 3.14.79-odroidc2 #14 SMP PREEMPT Thu Jan 25 05:46:07 CET 2018 aarch64 System load: 0.39 0.28 0.30 Up time: 1 day Memory usage: 19 % of 1975MB IP: 172.x.x.x CPU temp: 57°C Usage of /: 51% of 7.0G " When I do "dpkg -l | grep armbian", I see the following: " ii armbian-config 5.45 all Armbian configuration utility ii armbian-firmware-full 5.38 all Linux firmware-full ii armbian-tools-stretch 5.44 arm64 Armbian tools, Cubie bt utils ii hostapd 2:2.6-4~armbian5.38+1 arm64 IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator ii sunxi-tools 1.4.2-2~armbian5.38+1 arm64 tools for working with Allwinner (sunxi) ARM processors " Has anyone an idea, what happens here? Many thanks, Matt
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines