Go to advanced search

by The Stick
Wed Apr 01, 2015 2:00 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: Problems bit-banging an I2C Slave
Replies: 4
Views: 1387

Re: Problems bit-banging an I2C Slave

Yup, that was indeed it. Now to just figure out why the slave is getting nothing but 0x01 from the master... Master creates a char* that equals... " Here, have some text. This is but a sample of my power." ...and then sets the first char to 57, indicating the length of the message. This shows up as ...
by The Stick
Tue Mar 31, 2015 9:10 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: Problems bit-banging an I2C Slave
Replies: 4
Views: 1387

Re: Problems bit-banging an I2C Slave

Hi rst, I've been looking through your code a whole lot trying to get mine to work. I'd say that it's pretty much done, except for the fact that the data and/or clock pins seem to not be paying the bus any attention. I've set BCM 18 and BCM 19 (physical pins 12 and 35) to 7 (via setting 0x20200000 +...
by The Stick
Fri Mar 27, 2015 1:57 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: Problems bit-banging an I2C Slave
Replies: 4
Views: 1387

Problems bit-banging an I2C Slave

I have a Pi B+ on which I'm trying to bit-bash an I2C Slave in C / C++ (code's pretty much C despite the fact I'm using g++ and .cpp files), utilizing GPIO 18 as my Clock and GPIO 17 as my Data. I'm utilizing the BCM2835 C library from Mike M . My code is a little less featured that a true Slave, if...
by The Stick
Sat Jan 05, 2013 10:55 pm
Forum: General discussion
Topic: RS and Allied Update #6
Replies: 324
Views: 52470

Re: RS and Allied Update #6

Now, I know this isn't the BEST place to be posting this, but it's the closest I can figure. I've had an order through Allied Electronics (Yes, I know, not RS Components, the company who seems to be dominating this thread), initially ordered Sept 30, 2012. I then received an email from AE Nov 26, 20...

Go to advanced search