DS1339 LINUX DRIVER DOWNLOAD
In the command list you should see a line that looks like this: It’s here if you want to cherry-pick it and build your own kernel: I will try your other recommendations and let you know. I’m not sure if adding yet another driver specific header is a good idea. I did generate new device tree, but left the old pre-loader, which caused all the problems. You can check the driver source in the kernel tree and see. Maybe I need to enable something extra in I2C controller during boot?
|Date Added:||1 March 2004|
|File Size:||39.29 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Hello all, I am having troubles with I2C driver. A line similar to this:. In the meantime you posted reply with pre-loader issue, and after re-compiling the pre-loader, now I can see transmission on scope, as well as:.
It’s both conceptually wrong and actually unnecessary. Either way this is no longer a DT problem and you would be better off asking on a different forum – Interfacing or Advanced Users, perhaps.
I’m probably doing something wrong so any pointers would be nice You can check the driver source in the kernel tree and see. There are some ARM platforms where we can only get the time via ntpdate, and this is also satisfactory.
DS RTC has wrong time
This driver can also be built as a module. It will, however talk to the device if Da1339 use the i2c md or i2c mw commands.
Maybe I need to enable something extra in I2C controller during boot? If hwclock at the linux prompt works, your I2C bus is working. I submitted a small patch to the driver to enable this when the “wakeup-source” property is specified along with “m41t62”.
linux-kernel – Re: rtc-ds driver (especially for DS, DS)
Invalid argument hwclock -w hwclock -r Wed Dec 31 Those with an ack get listed. Then I ds1339 de-asserted it, and got good values in registers.
If instead it is occurring every boot then that suggests that either the RTC isn’t holding its value no battery backup or that the content is lknux corrupted.
The problem is that Linux is not loading the driver. I have no concrete proposal but it really sounds like a common RTC interface would be needed here – if it doesn’t exist already.
Perhaps the driver in 4. On Wed, May 04, at All I2C registers were set to 0. Anyway, exporting that function shouldn’t hurt: I will try your other recommendations and let you know.
CONFIG_SENSORS_DS1337: Dallas Semiconductor DS1337 and DS1339 Real Time Clock
Linux kernel is Linux 4. I have tried I2C tools from U-boot, probing and reading from specific device – no results.
Thank you again for your time and help! You are expecting it to declare ds1393 once we have an accurate time source to program the RTC, which is a much higher level operation – it just doesn’t fit the DT model.
In the meantime you posted reply with d1339 issue, and after re-compiling the pre-loader, now I can see transmission on scope, as well as: I2C tools returns following: I am having troubles with I2C driver. A Gossamer Threads company. Document the fact that ds driver works also with DS real-time clock chip. Linux has booted, and now shows [ 1. Here are some facts and tryouts:.