Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 175 subscribers
  • Views 221 views
  • Users 0 members are here
Related

How to use DS3231M PMOD

hai.bi

My ultimate goal is to use an RTC and I have bought DS3231M PMOD so I am going to try it on MicroZed.


I have gone through Vivado and configured I2C0 on 14-15 and exported according to the link http://microzed.org/content/problem-linaro-and-i2c-devices


I am wondering what to do in kernel config?  Since I am using the MIO, what do I need to do for the I2C hardware bus support?  Then what to do with the driver?  there is only DS3232 driver should I use it?


Then should I modify the device tree manually before build?


Regards,

  • 0

    I don't have a foolproof answer for you, but if it were me I would try the following:

    1. Modify the device tree manually as per the link you referenced, and see if you can achieve the same results.  Sounds like you set up your platform with the same I2C connection.

    2. There is an Ubuntu design for Zynq (Zedboard or Mini-ITX) that uses I2C devices.  You can check the kernel configuration in either design to see how the I2c drivers are connected, and how their device tree looks.  (Assuming 1 doesn't get you where you need to be).

    3. You may need to do some detective work on the kernel configuration by checking the .config file for I2C references.  Then you can search for those same references in the menuconfig tool and that will ensure when you change a setting, dependencies are also set.  If you know your way around the .config thoroughly, then it's ok to modify it by hand.  But I think in most cases you're better off using the tool.

    Hope that gets you going.  Let us know how you make out.

    Ron

  • 0

    This post on the Xilinx Community forums indicates one user found a problem with the Zynq PS (Processing System) I2C controller and solved his issue by moving to a PL (Programmable Logic) based AXI I2C controller: 

    http://forums.xilinx.com/t5/Embedded-Linux/Zedboard-Digilent-Pmod-Real-Time-Clock-cannot-detect/td-p/534271

     

    You will not be able to do that via the MIO based PMOD on the MicroZed but, if you do have access to PL based PMODs on a carrier card in your system, you might want to give his solution a try.

     

    -Gary

  • 0

    Thanks to all your comments.  I have reached a deeper level.  I am able to use i2cset 0 0x68 0xD0 to send out commands and see response on the scope.  And I am using the PMOD on the J5 so it's MIO. There was a glitch problem on the MIO i2C but I want to see it's working before I move on to a better eMIO.

    However, when I boot the board, there was no i2c activity (before I use i2cset manually).  The following was taken out of the output:

    i2c /dev entries driver
    cdns-i2c e00004000.i2c: 400 kHz mmio e00004000 irq 57
    ...
    /opt/pkg/.... drivers/rtc/hctosys.c: unable to open rtc device (rtc0)


    So I am thinking there has to be some configuration not right resulting in the Linux not accessing the i2c 0 correctly for rtc0.

  • 0

    I think I have made further:

    I am using the following command to link the rtc with the i2c:

    echo ds3232 0x68 > /sys/class/i2c-adapter/i2c-0/new_device

    Then I can see that the system instantiated device.  So I think it's working.  I was just I didn't know you have to do that under Linux command prompt.