Problem installing Rtc shield (Hardkernell) on Openmediavault Erasmus

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Problem installing Rtc shield (Hardkernell) on Openmediavault Erasmus

      Hi all :)
      My Openmediavault nas is installed on a Odroid C2. Im trying to install the HardKernell RTC shield following this tutorial Link
      Running the second line (sudo fdtput -t s /boot/meson64_odroidc2.dtb /i2c@c1108500/pcf8563@51 status "okay") i have this error: FDT_ERR_NOTFOUND (see the picture below).
      Ubuntu users can solve this problem updating the kernell Link....but we are talking about Armbian...
      Someone can help me?
      Please...
      Images
      • 568e93cd50e0ff5720b7e0277f57e61b.jpg

        82.62 kB, 1,008×756, viewed 21 times
    • marcellom wrote:

      Im trying to install the HardKernell RTC shield following this tutorial
      This tutorial assumes Hardkernel's partition layout, legacy kernel and path naming which is different in our case and you end up trying to modify a file that doesn not exist: /boot/meson64_odroidc2.dtb

      I would do a


      Source Code

      1. find /boot -name "*.dtb"

      If you find a file that seems to match, back it up and try the modification again.

      Edit: I was wrong, didn't get the error message correctly.

      On a related note: I tried very hard to upgrade to latest mainline kernel on ODROID-C2 few weeks ago (4.13 IIRC) but failed. But in case I would've suceeded then the above tutorial/method can't work anyway since DT structures with 4.13 will differ from 3.14 for sure.

      So that's something I did not even thought about: compatibility to legacy kernel (that we're still using this 3.14 kernel is a shame since unmaintained since Aug, 2016 now).
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.

      The post was edited 1 time, last by tkaiser ().

    • marcellom wrote:

      It seems a hopeless case...
      I don't think so, it's just a different naming and partition scheme currently used on the OMV image so I would believe if you find the correct .dtb file (sorry, too lazy to boot my C2 just for this now) then you most probably already would succeed. Besides that for me NTP always did the job so I wonder why you need to connect a RTC?
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • marcellom wrote:

      .. the meson64_odroidc2.dtb file is in the boot directory in omv.
      You're right, I missed this before.

      Please try to use the dtc tool to convert .dtb to .dts then change this line from "disabled" to ok "okay" and convert back. After a reboot it might work.

      Source Code

      1. cd /boot
      2. cp -p meson64_odroidc2.dtb meson64_odroidc2.dtb.bak
      3. dtc -I dtb -O dts -o meson64_odroidc2.dts meson64_odroidc2.dtb
      4. nano meson64_odroidc2.dts
      5. dtc -I dts -O dtb -o meson64_odroidc2.dtb meson64_odroidc2.dts
      Not tested and if you corrupt meson64_odroidc2.dtb in any stage then the board might be bricked (and you need another Linux box with card reader to recover from this by moving meson64_odroidc2.dtb.bak to meson64_odroidc2.dtb). So do only proceed please if you know what you do :)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.

      The post was edited 1 time, last by tkaiser: Wrong wording, it must be "okay" and not "ok" ().

    • Hi :)I started from a fresh image last night (a custom img with my settings, shares etc etc), I've done this line code

      sudo apt install device-tree-compiler

      and after this

      1. cd /boot
      2. cp -p meson64_odroidc2.dtb meson64_odroidc2.dtb.bak
      3. dtc -I dtb -O dts -o meson64_odroidc2.dts meson64_odroidc2.dtb
      4. nano meson64_odroidc2.dts
      Was searching..but i cant' find this part of code in my meson64_odroidc2.dts......


      Source Code

      1. &i2c_a {
      2. status = "okay";
      3. /* Hardkernel I2C RTC */
      4. pcf8563: pcf8563@51 {
      5. status = "disabled";
      6. compatible = "nxp,pcf8563";
      7. reg = <0x51>;
      8. #clock-cells = <0>;
      9. };

      So...is possible that rtc driver is not installed...or i was drunk/blind?:)



      Maybe we are going in the right direction...
    • marcellom wrote:

      is possible that rtc driver is not installed
      No idea, that might be possible too. But now it's about DT and a decompiled .dtb might look different than the original .dts. So simply search for the string 'pcf8563@51' there and change disabled to okay.

      BTW: this is way too off-topic in an OMV forum since it's about getting a DT node enabled for an ARM board. Hardkernel forum would be a better place.
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • marcellom wrote:

      A staff member says "try in a different forum like armbian"..
      I can understand that's annoying but due to ODROID community being one of the two SBC vendor communities with an excellent support level you won't find users with some knowledge active somewhere else.

      Different idea if you don't suceed: if there's a Debian Jessie OS image available at Hardkernel forum/community for ODROID-C2 known to work with your RTC module then you can install OMV there by following the official guides (will then show a lot lower NAS performance of course)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.