Re: [Gumstix-users] i2c Gumstix to Robostix timeout

[theorifice <ale...@ut...>]

I am also getting this problem very frequently and have yet to figure any
sort of solution.  I have found that even rapid subsequent calls to
'i2c-load 0x0b Info' can cripple the i2c.  Unloading and Reloading the i2c
modules sometimes works, but often I need to do a hard restart.  

I'm attaching an image with the output of a scope on the i2c SDA and SCLK
lines for a transaction between the Verdex and the Robostix.   The clock
looks majorly distorted with very slow rise and fall times although this
maybe because I am scoping from the pinouts on the robostix board rather
than from wherever the i2c lines are on the Robostix.  I've scoped i2c
transactions between the verdex and other devices and the clock looks
nominal.

The driver seems to really get stuck though and I've even tried resetting
registers using pxaregs to no avail.

I'd love to figure this problem out!


sburden wrote:
> 
> Hello Dave,
> 
> 
> Dave Hylands wrote:
>> 
>> Hi Sam,
>> 
>> Hmmm. I don't see anywhere in the i2c subsystem where that error is
>> returned.
>> 
>> In fact, there are hardly any drivers at all which return that
>> particular error code, since it's normally associated with socket
>> stuff.
>> 
>> It's possible that there is a case of errno not being set properly.
>> Try setting errno to 0 before the call, and see if you still get that.
>> 
> 
> I #include'd <errno.h> and set errno = 0; before each call to any of the
> i2c commands defined in i2c-api.h, and I still get that `connection
> refused' error (#111); it's actually the one I get most frequently, now.
> 
> Does it sound like I properly reset the errno variable?  If so, any ideas
> about why that might be the error I'm receiving?
> 
> - Sam
> 
http://www.nabble.com/file/p17614098/DSC06897.jpeg 
-- 
View this message in context: http://www.nabble.com/i2c-Gumstix-to-Robostix-timeout-tp17115455p17614098.html
Sent from the Gumstix mailing list archive at Nabble.com.