Jump to content

Search the Community

Showing results for tags 'odroidc2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • 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


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. I’m running an Odroid C2 and trying to drive a 14.9" 1280x390 60hz LCD marquis display. On a Pi I can change the boot config files to the following and the display works like a champ. [HDMI:1] hdmi_group=2 hdmi_mode=87 hdmi_timings=1280 0 8 128 64 390 0 1 3 24 0 0 0 67 0 42009500 8 On the Odroid running Armbian 22.11 Jammy XFCE I tried changing: /boot/armbianEnv.txt adding display_autodetect=false hdmimode=1280x390p60hz I had no joy with this change, it did not modify the display output. I love how fast and light Odroid is with Armbian, it is really snappy, but I need some help stretching out this display. Any help pointing me in the right direction would be greatly appreciated, I already threw you $5 to take a look @Igor https://paypal.com/donate/?hosted_button_id=A2AM5NWLVENF2&source=url
  2. boa noite gostaria de pedir ajuda estou tentando instalar o armbian em placa amlogic s805 e gostaria do arquivo u-boot já pesquisei no forum no site desde já agradeço não obteve sucesso
  3. I've tried a few images of the latest builds. None of them start. Odroid starts to power the screen and I see blinking lights, but screen goes dark and it seems to cycle like this. I use USB power for it and a powered hub (so basically no power output to USB dongles, etc.)
  4. Odroid C2 never starting after a soft reboot (reboot command). I have the same problem which other user is having with the Odroid C4 With the last kernel I have 5.10.102-meson64 the Odroid C2 never boots again after the "reboot" command, I need to unplug and plug again the power suply. Thanks and best regards, David
  5. I have a Waveshare 3.5inch RPi LCD (A): https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(A) Does somebody have this kind of LCD running on a Odroid C2? Is there a step by step? Because the Waveshare or Odroid Wiki is over my head 😟
  6. Hi. I want to use CAN interface on ODROID C2 board. I use external CAN-bus controller like MCP2515 via SPI interface. So, i need to enable SPI and CAN-bus peripherals and in kernel. So, could someone explain me how to do that? I know about device tree, but don`t know what to do. Just give me some guide links about device tree management, any examples, etc.
  7. Hello Guys, i am running an Odroid C2 with the latest Armbian based on debian Bullseye. As disk i am using an 8GB emmc flash drive. For longlive reasons i am thinking about to reduce the read or more important the write access to that drive. I know, that every SD card and also every EMMC flash drive got a certain amount of write access and then its dead... So i am ask you what can i do to reduce read/write: - move logs to external usb? - activate ZRAM? - disable cache...? - tmpfs? I am just at the beginning of this, so kindly let me know if you guys have some well know hints. Thanks JM
  8. I have just downloaded desktop Armbian 22.08 Jammy XFCE on my Odroid-C2 and it works fine on a 1080p monitor. I need it to work on a different monitor though so I have added the following lines to /boot/armbianEnv.txt display_autodetect=false hdmimode=1680x1050p60hz and added hdmitx=forcergb in the bootargs (which I copy/pasted from /boot/boot.cmd) but it has no effect. My monitor works with these parameters on Hardkernels Ubuntu 18.04 image. What else do I need to do?
  9. I use DietPi on my Odroid C2. I post here because the developer mentioned that the DietPi image is based on the Armbian kernel and he suggested posting here. When I attach the R5 to a USB port of my Odroid C2 it is not recognized. lsusb and dmesg do not show it. On my Ubuntu 22.04 PC it does show up. Looked around and finally found an old post on this forum that mentions a bug with the C2 in recognizing USB devices. The mentioned workaround is to add a second USB device and reboot the device. I added an USB drive and both are now recognized, initialized and working after a reboot. (When removing one of the devices it again doesn’t stick after a reboot.) I can not find more information on this. It seems this problem isn't solved? Regards, Joost
  10. Hi there, I've an odroid C2 device used for home automation and running armbian (uname -a) : Linux odroidc2 4.19.69-meson64 which is running stable with no problem. Yesterday, I've downloaded a fresh image of latest armbian for odroid C2, named Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img.xz. Put it on a new SD card and booted. It booted correctly but I've NO network. The LAN chip doesnt work at all, altough it appear in the device list I've theses entries in dmesg: [ 2.217600] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found [ 2.217611] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found [ 2.217694] meson8b-dwmac c9410000.ethernet: PTP uses main clock [ 2.218292] random: fast init done [ 2.218418] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 2.218426] meson8b-dwmac c9410000.ethernet: DWMAC1000 [ 2.218431] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported [ 2.218435] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported [ 2.218439] meson8b-dwmac c9410000.ethernet: COE Type 2 [ 2.218443] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported [ 2.218446] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported [ 2.218538] meson8b-dwmac c9410000.ethernet: Normal descriptors [ 2.218543] meson8b-dwmac c9410000.ethernet: Ring mode enabled [ 2.218547] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer ... [ 10.568311] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.568329] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.615619] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.615634] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.716190] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.716207] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.735509] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.735535] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) the first message I see when I boot (while plug in the power) is: Net: Could not get PHY for ethernet@c9410000: addr -1 No ethernet found The device is working with older armbian version but not the latest ? Could anyone look at it because the image available for download seem's broken and should not be distributed like this. I've reverted back to my old image (that's why I don't have the full log) and lost my week end on it, trying to sort it out without success. Could this be related to the .dtb ?? Thanks you
  11. I would like to permanently change at start up the UART permissions of /dev/ttyAML0 to give user, read write permissions always. I can do this with the usual "chmod" command but this gets reset after every boot and sometimes also during normal operations. Can somebody direct me to how this can be done please? xuraax
  12. I have an C2 and an old VU7 (800x480p60hz) https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-c2 that I was hoping to use for a mini kiosk. Was able to run the older Hard Kernel supplied images with the uboot boot.ini updates suggested above to change disable auto detect, fix the resolution, and set to DVI rather than HDMI mode. When I loaded the latest Focal image from Armbian when I have the screen switched on then the kernel faults and reboots. ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7b06a000, end 7bf49d63 ... OK Loading Device Tree to 000000007aff8000, end 000000007b069fff ... OK Starting kernel ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59543 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton I assume all I should need to do is update the /boot/boot.cmd, run `mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr` and the boot.scr should be updated. Also set: setenv disable_vu7 "false" But that variable isn't being used anywhere in the boot.cmd so I don't think it is being applied.
  13. This week we discontinued the default 3.x kernel for the Odroid C2, and are working on the 4.18/4.19 kernels. A few odds and ends have come up, the biggest one appears to be the gpio-hog in the C2 device tree somehow not working, causing the USB hub on the board to never be powered on. root@odroidc2:/sys/class/gpio# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-392 ( |mdio-reset ) out hi gpio-407 ( |reset ) out hi gpio-422 ( |cd ) in lo gpio-465 ( |TFLASH_VDD ) out hi gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks: gpio-500 ( |TF_IO ) out lo gpio-501 ( |usb-hub-reset ) out hi gpio-502 ( |USB_OTG_PWR ) out hi gpio-510 ( |c2:blue:alive ) out lo The hog claims it is there, but I get no power to the port. The other is the HDMI output becoming extremely fussy about the sort of monitor it's been given. [update] On the NanoPi K2 I actually get a crash on boot with my HDMI --> DVI adapter monitor. With both monitors, if plugged in after boot, desktop displays (on C2 only the pure HDMI monitor will display at all), but a fault occurs: FYI @Neil Armstrong
  14. according to here 5.13 is latest kernel https://www.armbian.com/odroid-c2/ but when I issue: sudo apt-get update && sudo apt-get dist-upgrade -y I'm still on 5.10....
  15. Hi , i buiild a SPDIF connector like shown here: https://forum.odroid.com/viewtopic.php?t=21477 it uses the J7 SPDIF output which is connected to HDMI. On coreelec i can clearly see a HDMI soundcard output with aplay -L , i dont see that on armbian.... Is odroid c2 spdif output on armbian working ? why do i not see this soundcard that f.e. libreelec is showing ( i have 2 odroid c2s , one is running coreelec in my living room with HDMI connector working) im using a little older armbian distro since the latest has ethernet issues on C2 (im using 20.11 , kernel 5.9.10 debian edition ) regards, Simon
  16. Hello all! I have an ODROID-C2 that I am trying to use with a GPS connected over UART for timing purposes, which requires the use of pps. Based on my searching and reading in this forum, I have determined that for my OS and kernel (Focal, 5.9.14) I should be able to do so by adding overlay=pps-gpio to armbianEnv.txt. What is not clear to me, however, is how to specify which pin to use! In this thread I see windysea said: But I don't know how to use this information! I have found no documentation on param_pps_*, and my attempts at guessing based on information from other threads and resources have failed to work so far. I have been fiddling with this for a few days to no avail now, so any assistance would be greatly appreciated. Regards, John
  17. as described in: https://gitlab.freedesktop.org/mesa/mesa/issues/2377 it's possible to use meson HW video codec now, but in the URL, not very clear, does any one know how to use it?
  18. Hi, I'm getting a random packet loss on the ethernet connection. When pinging, about 6-8% pings are lost, the ssh connection sometimes freezes for a moment. Things I've tried so far: Disabled NetworkManager, added eth0 in /etc/network/interfaces with a static ip4 address Disabled EEE for eth0 Replaced ethernet cable Plugged into different switch None of them made something better. My C1 & C4 with the same Armbian Buster version/release don't have this issue. How to investigate deeper in this issue?
  19. I recently bought a 64 GB eMMC module (chip on orange board) from Ordoid/Hardkernel but u-boot does not recognize the eMMC. What I did: installed the official Armbian_20.11.10_Odroidc2_focal_current_5.9.14.img.xz with Etcher on SD card booted successfully from SD card, eMMC is accessible from within Armbian/Ubuntu executed nand-sata-install to transfer the system to eMMC, which completed without error messages shutdown the system, removed SDcard and restarted it The serial console displayed the following: U-Boot 2020.10-armbian (Jan 05 2021 - 01:40:47 +0100) odroid-c2 Model: Hardkernel ODROID-C2 SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! Card did not respond to voltage select! MMC Device 2 not found no mmc device at slot 2 starting USB... Bus usb@c9100000: USB DWC2 scanning bus usb@c9100000 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found and then tried to boot via network. I then flashed the eMMC with the official Odroid image ubuntu-20.04-3.16-minimal-odroid-c2-20200617.img.xz and the system booted up successfully, so the eMMC module is working fine. Next step was to try the nightly build (Armbian_21.02.0-trunk.80_Odroidc2_focal_current_5.10.10_gnome_desktop.img.xz, with Etcher flashed on SD, then nand-sata-install) and again the eMMC as not visible in u-boot so the system did not come up. Therefore I set up an Armbian build environment and first tried to use this promising patch for u-boot https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/5ccd5d2cc98224108ae9fb09593a862c9caa5e80 but it seemed not to be suficient. I then replaced the provided u-boot v2020.10 with the new v2021.01 version and after replacing the kernel and uboot packages with the self compiled ones the eMMC was recognised by u-boot and the system boots from the orange 64GB eMMC module. U-Boot 2021.01-armbian (Feb 01 2021 - 11:57:23 +0100) odroid-c2 Model: Hardkernel ODROID-C2 SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 7136 bytes read in 1 ms (6.8 MiB/s) ## Executing script at 08000000 161 bytes read in 1 ms (157.2 KiB/s) 15703885 bytes read in 342 ms (43.8 MiB/s) 25461248 bytes read in 556 ms (43.7 MiB/s) 38868 bytes read in 2 ms (18.5 MiB/s) 232 bytes read in 1 ms (226.6 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) The "Card did not respond to voltage select" message is from the missing SD card Therefore I kindly ask to upgrade the u-boot of Odroid C2 to version 2021.01 in the next release.
  20. A few weeks ago, after a firmware-upgrade my C2 bricked. It's blue led didn't flash any more and no serial console was available. Since I had everything setup just right I wanted to recover it using these steps here: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot Off course I replaced the packages with the ones for the C2. Specifically: https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-dtb-current-meson64_20.11.3_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-image-current-meson64_20.11.3_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-buster-root-current-odroidc2/linux-buster-root-current-odroidc2_20.11.6_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/a/armbian-firmware/armbian-firmware_20.11.3_all.deb After following all the steps, I don't seem to have an uInitrd. I don't know if that would help booting up again, but from the symlinks section it's the only file missing after following all the steps: Does anybody know what went wrong or guide me towards the right steps to recover my C2?
  21. 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
  22. I tried Armbian_20.11.0-trunk.32_Odroidc2_focal_current_5.9.8.img and Armbian_20.11.0-trunk.32_Odroidc2_buster_current_5.9.8.img and both will not boot after apt upgrade. Armbian_20.08.22_Odroidc2_focal_current_5.9.6.img will not come up after sudo reboot and has to be power cycled. I believe the latter has been a persistent issue.
  23. With my OPi Zero, I noticed that at random times the ethernet connection somehow gets disabled. The only way to recover is by power cycling. I use the device as Pi-Hole (so when ethernet gets disconnected, I don't have internet anymore), print server and UniFi controller. I decided to swap it for my Odroid C2. Odd enough the C2 has the same issue. Maybe someone can help me with this? When powercycled, the Odroid with the latest Armbian (installed two days ago) is all up and running fine. It can connect to the internet, I can SSH into it. The ethernet led is flashing orange, so the gigabit connection is available. However, at rondom times the ethernet leds are both disabled. At this point, the C2 is still alive, but there's no way to access it without power cycling. I've tried removing the ethernet cable and connecting it again, hoping Armbian would recognize the connection - what happens in this case is that the green led will flash a few times (100Mbit) but the device is still offline. I've added some information from the log here before rebooting. This information keeps repeating in the log files... Hopefully someone can guide my as how to get the connection stable.
  24. Dear community, unfortunately, "armbianmonitor -u" doesn't give me a link anymore, and I'm not sure if uploading works at all. So I cant provide the information As our deployment date approaches, we try to finalize our Armbian system for North Pacific seafloor... and found some unexpected problems (problems seem alwas to be unexpected): The TigerVNC has two problems on Armbian, and it would be great if you could verify that issues and maybe problem some helpful ideas: (1) TigerVNC (tigervnc-common/stable,now 1.9.0) needs the following workaround to start at all: LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.so.1 vncserver :1 -localhost no Seems to be libunwind8 related, and is ugly, but not the main problem. (2) TigerVNC can be started by crontab "@reboot", but fails to open a desktop. There are messages about dbus problems, the display closes afterwards. I use Armbian NEXT, with Debian Buster, and kernel is locked to 4.19.90 (due to the various troubles with the new kernel, which seems to be optimzed for video playback but not stable operation). Any help is appreciated, and if you need more information, please let me know. So far, Michael
  25. Hi all, as a small status update on the seafloor business, here are some pictures of the new Odroid C2 based instruments which will be deployed in September/October in the northers Pacific. Ten modules with different functionality will be deployed, all based on a standard setup of Odroid C2, TRB3sc FPGA based TDC DAQ system, one PADIWA preamp, and a modded mdedia converter serving as a fully configurable mini switch. One of the modules carries several Hamamatsu mini spectrometers, as well as a camera, to observe bioluminescence. Another module is targeting at muon tracking with SiPM based readout: I have some more picture of the more "fancy" PMT based modules, but don't want to flood this forum now with too many pictures. To all of you: thanks for the support you gave us over the last year, and the discussions on specific topics! Deployment pictures will follow once the modules are in place on the seafloor, 2600m deep in the Pacific (and operational, hopefully, this time we just have a GbE fiber, no serial port...) See you, Michael
  • Create New...