I have no concrete proposal but it really sounds like a common RTC interface would be needed here – if it doesn’t exist already. I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio:. I have tried I2C tools from U-boot, probing and reading from specific device – no results. Hello Tim, this is the entry for I2C in my device tree. Linux has booted, and now shows [ 1.
|Date Added:||6 November 2014|
|File Size:||22.78 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I2C Help Pic 18f with RTC DS1339
I am relatively new to Linux, so any help would be much appreciated. If so, the easiest one to try is the rtc. I have no concrete proposal but it really sounds like a common RTC interface would be needed here – if it doesn’t exist already. And scan is finished instantly.
If the “invalid argument” error only occurs the first time you use the RTC then I think you are going to have to go through a commissioning process that sets the clock. Agreed, although I would go one step further.
CONFIG_SENSORS_DS1337: Dallas Semiconductor DS1337 and DS1339 Real Time Clock
Anyway, exporting that function shouldn’t hurt: Can’t say more unfortunately, as I never had to use a RTC myself. It’s here if you want to cherry-pick d1339 and build your own kernel: I have tried I2C tools from U-boot, probing and reading from specific device – no results. A line similar to this:.
I2C tools returns following:. Do you know what means this part of the. I did generate new device tree, but left the old pre-loader, which caused all the problems. I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio: So, to sum up: I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio:.
In the command list you should see a line that looks like this:. I’m using the very latest raspbian stretch, used rpi-update to get the latest kernel: You are expecting it to declare that 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.
Lniux Tue, Linud 10, at Here are some facts and tryouts:. I submitted a small patch to the driver to enable this when the “wakeup-source” property is specified along with “m41t62”. If so, the module will be called ds There are some ARM platforms where we can only get the time via ntpdate, and this is also satisfactory.
Then you can write the time in seconds to that file and the alarm interrupt will occur at that time. No such file or directory Does anyone knows where could be the problem.
LKML: Alexandre Belloni: Re: [PATCH] rtc: ds fix ds wakealarm support
Thank you again for your time and help! This driver can also be built as a module.
Document the fact that ds driver works also with DS real-time clock chip. Then I manually de-asserted it, and got good values in registers. So adding new compatible driver name did load the driver now.
A Gossamer Threads company. Hold down a key during boot from power-up or reset, and at the u-boot prompt enter help to see if there are I2C tools built-in. I2C tools returns following: 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: