Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12 Jun 2013 10:58 AM by  Andrew Bowser
SOMxM37xx-10 PMIC communication problem... Remove R36
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Andrew Bowser
New Member
New Member
Posts:


--
11 Jun 2013 10:07 AM
    These are the two modules I am using:

    SOMAM3703-10-2780HFCR
    SOMDM3730-10-1782JFIR

    I have several of both and every single board is showing this issue. I first noticed the issue when trying to access and update the real time clock. When using the 'hwclock' linux command I would either get a terminal lock-up, a false good but no update or interrupt is issued, or the error message "select() to /dev/rtc to wait for clock tick timed out". The issue actually spans further than this in that all communication between the processor and the TPS65950 power management chip is this flakey.

    After a long battle of making sure this wasn't an issue with my custom baseboard or my coworkers custom software and then another long battle of trying to find any issue with the SOM board I finally stumbled upon the error. It seems to be a simple human error ("I must've put a decimal point in the wrong place or something!") and the fix is equally simple. The resistor pack R36 is 470 ohm and should be 4.7k ohm. Simple as that. The two I2C lines that control the power management are held with too strong of a pullup to allow communication. Just remove the resistor pack or replace with an equivalent 4.7k ohm package. I have removed R36 on all of my modules and they all are in working order now with a fully functional real time clock.

    I hope this saves someone else the trouble I went through tracking down this error.
    products_apps@logicpd.com
    New Member
    New Member
    Posts:


    --
    12 Jun 2013 09:56 AM
    Bowser,
    Sorry to hear about your issues. That R-pack value is a direct recommendation from TI for the OMAP3530 that we kept on the transition to AM/DM37xx. They are necessary because those I2C buses run at 3.2 MHz. Did you see similar problems on our baseboard, or only yours? I am unsure why you have two cards with that problem while no one else has had issues with PMIC communications.
    Andrew Bowser
    New Member
    New Member
    Posts:


    --
    12 Jun 2013 10:58 AM
    I supposed the difference is that I am using 400 kHz for both of those busses. These two I2C busses do not connect to either baseboard.

    All of the TI designs that I have seen use 4.7k pull-ups for all the I2C busses. This includes the OMAP3 EVM and the Beagleboard.
    You are not authorized to post a reply.