@Lazar-Demin : Thanks a lot. It took us some time to finalize this dev :-). Correct: The MicroSD only is accessed by the display controller. However, over serial commands from the Omega to the display controller, you can interact with the display itself. I'm pretty fond of this, as just dumping some serial commands really is easy. I therefore have two MicroSD slots on the board. One is reserved for the display controller and only accessed by it. The second one is connected to the Omega2S+ and serves as memory extension. If this can be an interesting solution for you, don't hesitate E-mailing me. I'll send you a proto board. Best, MK

seem i found a problem - it's abattery If we don't se on chip model and return from m41t81s to m41t80 in dts all worked fine RTC and watchdog(but watchodg has only on 81s)

@Modest-Polykarpovich I tried but the device did not appear in /dev/ echo rtc_m41t80 0x68 > /sys/class/i2c-dev/i2c-0/device/new_device dmesg show [ 152.302693] i2c i2c-0: new_device: Instantiated device rtc_m41t80 at 0x68 root@Omega-61B6:/# lsmod | grep 41t8 rtc_m41t80 8704 0 root@Omega-61B6:/# i2cdump -y -f -r 0-6 0 0x68 c 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 00 ff ff 7f 07 3f 1f ...????

@crispyoz said in Project "liburtc" the library to operate external RTC devices: Not sure where I would buy old Russian diodes here on Australia though You can try 1N34A that's Germanium Diode too and say us result.

@Modest-Polykarpovich It is not a question of what you consider acceptable. I was simply suggesting a solution to your problem. If Omega does not suit your application you are free to change to a more suitable device, but you'll need make sure it is not OpenWrt based because you'll probably strike a similar issue, if not with this kmod but some other. Either way, I'll get a good night's sleep

@Mark-Fisher IIRC, the standard RTC package implements an init script which will read the data from the RTC device on boot and set the clock accordingly. On shutdown it updates the RTC device with the current clock value. In between those states, if a network connection is established, the Omega will query NTP servers and sync the clock with that. So, as long as you build your firmware with the requisite packages (the one with the driver for your RTC device and the standard RTC package together with any dependencies either require) and ensure that the RTC device is accessible during boot up, your needs should be accommodated.

@unique1984 said in DS 1307 RTC Simple Bash Client: echo -e "<date> Show the date [YYYYMMDDHHMMSS] from RTC" sir, can you help me it's not working for me? I got the output is i am using isl12026 datasheet instead of your address value place i used 0x20 is this currect? REGCONTROL=$(i2cget -y 0 0x20 0x07) YEAR=$(i2cget -y 0 0x20 0x06) MONTH=$(i2cget -y 0 0x20 0x05) DATE=$(i2cget -y 0 0x20 0x04) DAYOFWEEK=$(i2cget -y 0 0x20 0x03) # day of week 1-7 monday-sunday HOUR=$(i2cget -y 0 0x20 0x02) MINUTE=$(i2cget -y 0 0x20 0x01) SECOND=$(i2cget -y 0 0x20 0x00) i got the below output. can u please help me solve this problem. 2000-00-00 00:00:00

@Arshad-Alam What do you get when you run i2cdetect -y 0 It should give you a list of devices and their addresses like so: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Identify the ones you know are connected and the one you cannot identify will be the RTC. If you are thinking the Omega has an RTC built in, then you are mistaken. You would need to hook one up to the i2c bus to be able to use one.

The PCF8574 break-out board, is an 8 port GPIO extension. So i cannot read the I2C bus with above program... I need more inputs on the Omega2, so i was hoping to solve it this way. I tried the One-Wire system before, but also no luck (device not recognised)...

@Paul-Cousins Hi, I'm having the same error, could you please send me your code? I'd really appreciate it, thanks