Uploader: | Gurisar |
Date Added: | 13 June 2008 |
File Size: | 35.14 Mb |
Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
Downloads: | 2427 |
Price: | Free* [*Free Regsitration Required] |

I am relatively new to Linux, so any help would be much appreciated. And weird thing is that RTC line is just before this: I am having troubles with I2C driver.
[PATCH] ds1337 driver works also with ds1339 chip
I have tried I2C tools from U-boot, probing and reading from specific device - no results. 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: 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 rs1339.
Hello Tim, this is the entry for I2C in my device tree. Can't say more unfortunately, as I never had to use a RTC myself. On Wed, May 04, at Linux has booted, and now shows [ 1. Board index All times are UTC. Then I manually de-asserted it, and got lihux values in registers.
How to configure the Linux kernel/drivers/i2c/chips
On Tue, May 10, at Anyway, exporting that function shouldn't hurt: I have played around with u-boot, and noticed that I2C was held in reset. There are some ARM platforms where we can only get the time via ntpdate, and this is also satisfactory.
Here are some facts and tryouts: Here are some facts and tryouts:. Select all hwclock -r hwclock: Do you know what means this part of the. A line similar to this:. In device tree it is says designware-i2c. 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:.
Mailing List Archive GT. Does anyone knows where could be the problem.
Adding a new RTC to - Raspberry Pi Forums
In the command list you should see a line that looks like this: If instead ds3139 is occurring every boot then that suggests that either the RTC isn't holding its value no battery backup or that the content is being corrupted. Therefore RTC drivers are usualy compiled in kernel.
And regarding kernel version, I have been running 4. But it's in linux-next and Linus has pulled it into his tree, so should be out soon. I'm using the very latest raspbian stretch, used rpi-update to get the latest kernel: And scan is finished instantly.
You can check the driver source in the kernel tree and see.
Linux source code: drivers/i2c/chips/dsc (v) - Bootlin
In the command list you should see a line that looks like this:. All I2C registers were set to 0.

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.
Make sure the pre-loader is generated with the output from your design, and that your BSEL pins are pointing to the right place to get it.
Comments
Post a Comment