I2C works fine. I've written a library, shared object, and some C# wrapper code to call the so. All works great for me.trainboy wrote:I totally agree. I to have been in computers since I was 20 years of age, I am now 60, and thought "I'll have a piece of that Pi action" but everything I try has had a stumbling block. As a example (1) - What's so big about Cross Compiling on a Windows platform? I can Cross compile for Atmel ATmega devices on a PC. I can Cross Complile for PIC 18F devices on a PC. Where is the problem? I need a Gcc complier that works on a PC with the associated header files for the Pi environment, and I will transfer the resultant Object file to the Pi and run it. I do not want to load Linux into my PC. I do not need a 2nd occurance of windows in a split screen environment PC. I do not need to have Debian Vs Raspian issues. I am only creating a file that will run on an Arm Cpu.
Example (2) - I want to use I2C bus and program it in 'C' - what a palaver!!! I can see the signals SDA & SCL on a 'scope if I use i2cdetect -y 1 (I have a Rev2 Pi) but will it work from a C program - no it will not.
Check this out: http://www.skpang.co.uk/blog/archives/575
And this: http://binerry.de/post/27128825416/rasp ... uino-slave
Edit: Here is the link to the relevant C code for the i2c-arduino project: https://github.com/binerry/RaspberryPi/ ... 2c-arduino
In that c file you will find the code you need to make an i2c call.
Finally, if you want me to send you the code for my library (based on the links above) send me a PM and I'll get you the source. I'll be adding a repo on github soon, but I don't want to push it up until I finish the documentation.