Then I manually de-asserted it, and got good values in registers. Hello all, I am having troubles with I2C driver. All I2C registers were set to 0. Therefore RTC drivers are usualy compiled in kernel. There is no reason why it can’t be initialised during the normal driver initialisation – which is how we do it on a number of ARM platforms. Agreed, although I would go one step further. I’m probably doing something wrong so any pointers would be nice
|Date Added:||20 January 2016|
|File Size:||23.96 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Do you know what means this part of the. On Tue, May 10, at There are some ARM platforms where we can only get the time via ntpdate, and this is also satisfactory. And weird thing is that RTC line is just before this: Actually, I have tried to add another driver file name in device tree.
P1010 & I2C RTC DS1339
Anyway, exporting that function shouldn’t hurt: Maybe I need to enable something extra in I2C controller during boot? Hold down a key during boot from power-up or reset, and at the u-boot prompt d1339 help to see if there are I2C tools built-in. Is there an entry in your device tree for the I2C, with the proper compatible string?
Hello all, I am having troubles with I2C driver. I am relatively new to Linux, so any help would be much appreciated. There is no reason why it can’t be initialised during the normal driver initialisation – which is how we do it on a number of ARM platforms.
It’s here if you want to cherry-pick it and build your own kernel: If instead it is occurring lihux boot then that suggests that either the RTC isn’t holding its value no battery backup or that the content is being corrupted.
But still after I2C probing there was nothing on oscilloscope. I’m using the very latest raspbian stretch, used rpi-update to get the latest kernel: So adding new compatible driver name did load the driver now. I’m not sure if adding yet another driver specific header is a good idea.
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:.
No such file or directory.
I2C Help Pic 18f with RTC DS | Microchip
Those with an ack get listed. Can’t say more unfortunately, as I never had to use a RTC myself. I2C tools returns following: Invalid argument hwclock -w hwclock -r Wed Dec 31 I have played around with u-boot, and noticed that I2C was held in reset. Here are some facts and tryouts: Linux has booted, and now shows [ 1. I will try your other recommendations and let you know.
The problem is that Linux is not vs1339 the driver. I2C tools returns following:. linuxx
LKML: Alexandre Belloni: Re: [PATCH] rtc: ds fix ds wakealarm support
In the command list you should see a line that looks like this: Does anyone knows where could be the problem. Here are some facts and tryouts:.
No such file or directory Does anyone knows where could vs1339 the problem. You can check the driver source in the kernel tree and see. I submitted a small patch to the driver to enable this when the “wakeup-source” property is specified along with “m41t62”. Mailing List Archive GT.