Well, I had the right i2c address, but was calling the wrong function when initializing the dbs_rx board. I called the c++ equivalent of the following Python code:
self._u._write_io(self._which,0x0001,0x0001)
instead of
self._u._write_oe(self._which,0x0001,0x0001)
So I typoed and put "io" instead of "oe" which resulted in the bad bad behavior. Duh. Sorry for the false alarm, and thanks Eric and Matt for your help!
Eric Blossom <[EMAIL PROTECTED]> wrote:
On Sun, Oct 22, 2006 at 10:31:31PM -0700, David Caruth wrote:
> Hi All.
>
> I have searched this forum for i2c errors and dbs problems, but have
> not found anything like my problem. I'm sure I have the correct i2c
> address set as well. Any suggestions? Please don't suggest that I
> just use the python script... :)
My guess is that you are using the wrong i2c addresses. Many data
sheets conflate the 7-bit i2c address with the 8-bit byte that
contains the 7-bit i2c address in the top 7-bits and r/w bit in the
low bit of that byte. When our code is talking about an i2c address,
we _really_ mean i2c address, not the i2c address shifted one way or
the other.
Eric
Stay in the know. Pulse on the new Yahoo.com. Check it out.
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
