I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio:. Thank you again for your time and help! Probably, they are init values for the RTC, but I couldn’t find any documentation about that: In the command list you should see a line that looks like this:. If hwclock at the linux prompt works, your I2C bus is working. I have played around with u-boot, and noticed that I2C was held in reset.
|Date Added:||3 January 2017|
|File Size:||63.61 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
No such file or directory. 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 ds13339 corrupted.
I am having troubles with I2C driver. Board index All times are UTC. Linux has booted, and now shows [ 1. Actually, I have tried to add another driver file ds13339 in device tree.
Do you have the devices listed in the tree on your board: And scan is finished instantly. Then you can write the time in seconds to that file and the alarm interrupt will occur at that time.
[PATCH] ds1337 driver works also with ds1339 chip [Linux 2.6.13]
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 ds13399.
In the command list you should see a line that looks like this:. All I2C registers were set to 0. Those with an ack get listed. I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio:.
How to configure the Linux kernel/drivers/i2c/chips | How To Wiki | FANDOM powered by Wikia
During boot U-boot reports I2C: Make sure the pre-loader is generated with the output from your design, and that your BSEL pins are pointing to the ds1393 place to get it.
On Wed, May 04, at Hello Tim, this is the entry for I2C in my device tree. Is there an entry in your device tree for the I2C, with the proper compatible string? Select all hwclock -r hwclock: 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.
[PATCH] ds driver works also with ds chip [Linux ] – Linux Kernels
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.
Select all date Thu Jan 1 Perhaps the driver in 4. Adding a new RTC to i2c-rtc-overlay. There are some ARM platforms where we can only get the time via ntpdate, and this is also satisfactory. And regarding kernel version, I have been running 4.
I’m using the very latest raspbian stretch, used rpi-update to get the latest kernel: 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 dss1339 external PHY through gpio: On Tue, May 10, at 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 lniux that sets the clock.
It’s here if you want to cherry-pick it and build your own kernel: Invalid argument hwclock -w hwclock -r Wed Dec 31 Here are some facts and tryouts: And weird thing is that RTC line is just before this: