On Wed, Sep 2, 2020 at 12:41 AM Niresh <nireshshara...@gmail.com> wrote: > > Hi, > You are right, I've done a little experiment to confirm the same. > > Test #1: Made both system and RTC time synchronized with 2020-09-02 09:00:30 > and then rebooted , both time syncs. > > Test #2: Made RTC time delay with an hour by using command hwclock --set > --date "09/02/20 08:00:30 "and system time 2020-09-02 09:00:30 and then > rebooted. Now, the system time is not sync with RTC,it remains unchanged > 2020-09-02 09:00:30 > > Test #3: Made RTC time advance with an hour by using command hwclock --set > --date "09/02/20 10:00:30 "and system time 2020-09-02 09:00:30 and then > rebooted. Now, the system time is sync with RTC, that's with 2020-09-02 > 10:00:30 > > Could you please tell me starts from which version of kernel > "BB-I2C2-RTC-DS3231.dtbo" device tree works. I will tell you why, I was > using arm-linux-gnueabihf-gcc-4.9 to compile my application code in the > 4.4.30-ti-r64 kernel, and it compiled and ran perfectly. Now the same > application code gives me an error message with compiler > arm-linux-gnueabihf-gcc-8 in the new image 4.19.94-ti-r42. > > Like I said before, I am not a linux guy and the developer, who coded this > and has left the organisation, cautioned me to stick with 4.4.30-ti-r64 > kernel for stable operation of application code. Please advise which version > is good to go and how to overcome this issue.
Can you share the actual "error message"? Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgMqVpXgg6qJ1fgtkCbJCY2f8OtcDfVEYbYW3CWbFA0rw%40mail.gmail.com.
