I2C2_SDA and I2C2_SCL pins 23,24 on the expansion port

[Mohan AY]

Hi

I am attempting I2C on expansion port (beagleboard C3).

I have similar setup mentioned in:
http://groups.google.com/group/beagleboard/browse_thread/thread/409c7fd9e49b27f9/ae3b72e1cafa3243?lnk=gst&q=i2c#ae3b72e1cafa3243

"On the beagleboard I connected to the i2c-2 pins on the expansion
connector (pin 1 for 1.8v, pin 23 for sdc, pin 24 for scl, pin 27 for
ground). For the I2C slave device, I connected to the i2c on the UART
header (pin 10 for ground, pin 14 for 5v, pin 12 for sda, pin 16 for
scl). "

The issue here is: After connecting I2C slave I don't see any change
in the logic analyzer.

Any cues?

Thanks!

[Gerald Coley]

What size are your pullup resistors on the SCL and SDA signals?

 

Gerald

 

--

You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

[Mohan AY]

Thank you for replaying. My apologies for the late reply.

SDA & SCL lines of expansion headers are connected to PIN 1 of
expansion header through 4.7 K resistors.

With above arrangement when we power on the beagleboard, 1.8V was
observed on I2C2 lines of expansion headers. However, without external
pullup resistors (as above) we were still getting the same 1.8V on
I2C2 lines.

Additional info:
-----------------
We ran a simple I2C test from user space, and got 'controller timed
out' error.

Thank you,
Mohan

On Dec 31 2009, 7:02 pm, Gerald Coley <ger...@beagleboard.org> wrote:
> What size are your pullup resistors on the SCL and SDA signals?
>
> Gerald
>

> On Thu, Dec 31, 2009 at 6:25 AM, Mohan AY <moha...@gmail.com> wrote:
> > Hi
>
> > I am attempting I2C on expansion port (beagleboard C3).
>
> > I have similar setup mentioned in:
>

> >http://groups.google.com/group/beagleboard/browse_thread/thread/409c7...

>
> > "On the beagleboard I connected to the i2c-2 pins on the expansion
> > connector (pin 1 for 1.8v, pin 23 for sdc, pin 24 for scl, pin 27 for
> > ground).  For the I2C slave device, I connected to the i2c on the UART
> > header (pin 10 for ground, pin 14 for 5v, pin 12 for sda, pin 16 for
> > scl). "
>
> > The issue here is: After connecting I2C slave I don't see any change
> > in the logic analyzer.
>
> > Any cues?
>
> > Thanks!
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>

[Mohan AY]

Would like to add one more important detail.

I am using Android on Beagleboard, followed all steps mentioned in:
http://free-electrons.com/blog/android-beagle/

I have seen posts where developers comment some feature is working for
them after some tweaking, etc. and since there are many beagleboard
ports, sometimes it becomes difficult to understand for which port the
feature is working.

Thank you,
Mohan

On Dec 31 2009, 7:02 pm, Gerald Coley <ger...@beagleboard.org> wrote:

> What size are your pullup resistors on the SCL and SDA signals?
>
> Gerald
>

> On Thu, Dec 31, 2009 at 6:25 AM, Mohan AY <moha...@gmail.com> wrote:
> > Hi
>
> > I am attempting I2C on expansion port (beagleboard C3).
>
> > I have similar setup mentioned in:
>

> >http://groups.google.com/group/beagleboard/browse_thread/thread/409c7...

>
> > "On the beagleboard I connected to the i2c-2 pins on the expansion
> > connector (pin 1 for 1.8v, pin 23 for sdc, pin 24 for scl, pin 27 for
> > ground).  For the I2C slave device, I connected to the i2c on the UART
> > header (pin 10 for ground, pin 14 for 5v, pin 12 for sda, pin 16 for
> > scl). "
>
> > The issue here is: After connecting I2C slave I don't see any change
> > in the logic analyzer.
>
> > Any cues?
>
> > Thanks!
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>

[Gerald Coley]

If you are getting a 1.8V level without the pullups, then you do not have the correct MUX settings on the I2C lines. They are most likley set to a GPIO mode. You need to set up the pin muxing to enable the I2C modes on those pins. I suggest you do a search on the discussion group for help on this issue. It has been discussed many times in the past.

 

http://beagleboard.org/discuss

 

Gerald

To unsubscribe from this group, send email to beagleboard...@googlegroups.com.

[ghanashyam prabhu]

Hi Am Shyam, working with Mohan...

Adding the Pin Mux configuration details..

We have set the pin mux configuration to work in Mode0 (that is the
I2C mode),This has been set in the mux.h/ mux.c and beagle.h files as
mentioned in a lot of forums. So we tried this for configuring pin mux
in the kernel. Pin mux configuration is also changed during U-boot..
Alas.. we dont see anything change on the Logic analyzers for the I2C2
Pins. The I2C tools pops out a connection timed out error..

Can we read the OMAP pin configuration register for I2C2 SDA and SDC
on run time in linux command line shell .. if that is possible then we
can write/read to these registers on run time to check if they are
configured correctly?
Does nasm work for omap or any other assembly code specific to OMAP?

regards
Shyam

> > > > beagleboard...@googlegroups.com<beagleboard%2Bunsubscribe@googlegr oups.com>
> > <beagleboard%2Bunsu...@googlegroups.com<beagleboard%252Bunsubscribe@goo glegroups.com>

>
> >  > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/beagleboard?hl=en.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > beagleboard...@googlegroups.com<beagleboard%2Bunsubscribe@googlegr oups.com>

[Eric Fung]

I posted the info about the i2c-2 before. Please read this URL:
http://groups.google.com/group/beagleboard/browse_thread/thread/a6c42ef56c6a2da2/1608e6c0f0207a8d?lnk=raot&pli=1

To unsubscribe from this group, send email to beagleboard...@googlegroups.com.

[MAY]

Thank you for reply.

After going through many discussions in this group and documents from
beagleboard.org, ti.com, we made following changes to source, which
did not result in any success.

arch/arm/mach-omap2/board-omap3beagle.c
=============
omap3_beagle_i2c_init(): Enabled I2c bus 2
> omap_register_i2c_bus(2, 100, NULL, 0);

omap3_beagle_init():
> omap_cfg_reg(AE15_34XX_I2C2_SDA);
> omap_cfg_reg(AF15_34XX_I2C2_SCL);

arch/arm/mach-omap2/mux.c
============
Note: Tried different combinations w.r.t. PIN_INPUT, PULLUP, PULLDOWN,
etc.: However no change
> MUX_CFG_34XX("AF15_34XX_I2C2_SCL", 0x1be,
OMAP34XX_MUX_MODE0 | OMAP34XX_PIN_INPUT)
> MUX_CFG_34XX("AE15_34XX_I2C2_SDA", 0x1c0,
OMAP34XX_MUX_MODE0 | OMAP34XX_PIN_INPUT)

kernel/.config
==========
> CONFIG_OMAP_MUX=y

kernel/arch/arm/configs/omap3_beagle_defconfig
=============
> CONFIG_OMAP_MUX=y

Also, the peripheral used is 1.8v, hence no need for voltage
translation in this case.

Please let us know if the direction we are going is correct.

Thank you,
Mohan

On Jan 4, 1:55 am, Eric Fung <erickpf...@gmail.com> wrote:
> I posted the info about the i2c-2 before. Please read this URL:http://groups.google.com/group/beagleboard/browse_thread/thread/a6c42...

>
> On Sun, Jan 3, 2010 at 3:02 AM, ghanashyam prabhu <
>

> > > > > > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>
> > <beagleboard%2Bunsubscribe@googlegr oups.com>
> > > > <beagleboard%2Bunsu...@googlegroups.com<beagleboard%252Buns...@googlegroups.com>

> > <beagleboard%252Bunsubscribe@goo glegroups.com>
>
> > > >  > > .
> > > > > > For more options, visit this group at
> > > > > >http://groups.google.com/group/beagleboard?hl=en.
>
> > > > --
>
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Beagle Board" group.
> > > > To post to this group, send email to beagl...@googlegroups.com.
> > > > To unsubscribe from this group, send email to

> > > > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>

> > <beagleboard%2Bunsubscribe@googlegr oups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/beagleboard?hl=en.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>

[MAY]

Finally when tried with Angstrom, I2C on expansion port worked!
This linux port has all the changes built-in. Importantly, i2c tools
was already ported which helped quickly to verify the I2C
functionality. Thank you, Angstrom guys!

Our earlier attempt with 'Android on Beagleboard' needs to be reviewed
for I2C related changes.
May be on some other day.

Gerald & Eric,
Thank you for your timely comments & help.

Best Regards,
Mohan