I2C not working on Pi 3

[Senna-chan]

This code works on my Pi 2 but not the new Pi 3
The code and the libs for the project is on my github account

pi@Natsukipi:~/monodevelop/BattleBotServer/BattleBotServer/bin/Debug $ sudo mono BattleBotServer.exe

Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type initializer for BattleBotServer.Helpers ---> System.NotSupportedException: Connector pintout Unknown is not supported
  at Raspberry.IO.InterIntegratedCircuit.I2cDriver.GetBscBase (ProcessorPin sdaPin, ProcessorPin sclPin) [0x00000] in <filename unknown>:0
  at Raspberry.IO.InterIntegratedCircuit.I2cDriver..ctor (ProcessorPin sdaPin, ProcessorPin sclPin) [0x00000] in <filename unknown>:0
  at BattleBotServer.Helpers..cctor () [0x00000] in <filename unknown>:0
  --- End of inner exception stack trace ---
  at BattleBotServer.LogWriter.get_Instance () [0x00000] in <filename unknown>:0
  at BattleBotServer.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for BattleBotServer.Helpers ---> System.NotSupportedException: Connector pintout Unknown is not supported
  at Raspberry.IO.InterIntegratedCircuit.I2cDriver.GetBscBase (ProcessorPin sdaPin, ProcessorPin sclPin) [0x00000] in <filename unknown>:0
  at Raspberry.IO.InterIntegratedCircuit.I2cDriver..ctor (ProcessorPin sdaPin, ProcessorPin sclPin) [0x00000] in <filename unknown>:0
  at BattleBotServer.Helpers..cctor () [0x00000] in <filename unknown>:0
  --- End of inner exception stack trace ---
  at BattleBotServer.LogWriter.get_Instance () [0x00000] in <filename unknown>:0
  at BattleBotServer.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0

[OddmarDam]

Any news on this ? I also have a RPI 3 that i would like to use instead of my RPI 2.

[msanchez71]

Is this project still active? I would like to know when this issue with Pi 3 might be looked at.

Thank you in advance

[jyksnw]

Looks like a new PinMapping needs to be defined. It is my understanding that the RPI 3 GPIO is supposed to be backwards compatible with RPI 2. If this is the case than it should just be a matter of defining the RPI 3 and using the RPI 2 PinMappings. I don't own a RPI 3 so I am not able to test this otherwise I would do the work. If someone has a RPI 3 and wants to give it a shot look at the PinMapping.cs located in Raspberry.IO.GeneralPurpose

[OddmarDam]

I have a RPI 3. I suppose it's the BoardRevision i am looking for ?!

On Fri, May 20, 2016 at 8:06 PM, Jason Snow notifications@github.com
wrote:

Looks like a new PinMapping needs to be defined. It is my understanding
that the RPI 3 GPIO is supposed to be backwards compatible with RPI 2. If
this is the case than it should just be a matter of defining the RPI 3 and
using the RPI 2 PinMappings. I don't own a RPI 3 so I am not able to test
this otherwise I would do the work. If someone has a RPI 3 and wants to
give it a shot look at the PinMapping.cs located in
Raspberry.IO.GeneralPurpose

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#56 (comment)

[jyksnw]

I just had a deeper look at this. Looks like PinMapping has already been updated to account for RPI 2 and RPI 3, however GpioConnectionSettings.cs had not. I added a HACK into GpioConnectionSettings.cs that might potentially fix the RPI 3 I2C issue. This isn't a long term fix, so if someone can test it and get back to me I will gladly work on a more permanent solution.

You can find the fix/hack in my fork of raspberry-sharp-io. Be sure to checkout the rpi3_i2c branch after cloning the fork.

[OddmarDam]

Here is what i get when i test the I2C on a RPI3::

Unhandled Exception:
System.NotSupportedException: Connector pintout Unknown is not supported
at Raspberry.IO.InterIntegratedCircuit.I2cDriver.GetBscBase (ProcessorPin
sdaPin, ProcessorPin sclPin) <0x74a5e610 + 0x001f4> in :0
at Raspberry.IO.InterIntegratedCircuit.I2cDriver..ctor (ProcessorPin
sdaPin, ProcessorPin sclPin) <0x74a5e268 + 0x0005b> in :0
at Test.Components.Ssd1306.MainClass.Main (System.String[] args)
<0x76abdf50 + 0x00047> in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NotSupportedException: Connector
pintout Unknown is not supported
at Raspberry.IO.InterIntegratedCircuit.I2cDriver.GetBscBase (ProcessorPin
sdaPin, ProcessorPin sclPin) <0x74a5e610 + 0x001f4> in :0
at Raspberry.IO.InterIntegratedCircuit.I2cDriver..ctor (ProcessorPin
sdaPin, ProcessorPin sclPin) <0x74a5e268 + 0x0005b> in :0
at Test.Components.Ssd1306.MainClass.Main (System.String[] args)
<0x76abdf50 + 0x00047> in :0

On Sun, May 22, 2016 at 7:00 PM, Jason Snow notifications@github.com
wrote:

I just had a deeper look at this. Looks like PinMapping has already been
updated to account for RPI 2 and RPI 3, however GpioConnectionSettings.cs
had not. I added a HACK into GpioConnectionSettings.cs that might
potentially fix the RPI 3 I2C issue. This isn't a long term fix, so if
someone can test it and get back to me I will gladly work on a more
permanent solution.

You can find the fix/hack in my fork of raspberry-sharp-io
https://github.com/jyksnw/raspberry-sharp-io/tree/rpi3_i2c. Be sure to
checkout the rpi3_i2c branch after cloning the fork.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#56 (comment)

[msanchez71]

jyksnw,

I would be happy to send you a RPi 3 if you would like. just let me know and we can work out the logistics. I will also do some more testing this week as I get a chance.

Thanks...

[jyksnw]

@OddmarDam thanks for posting back. Assuming that the error was caused while using my rpi3_i2c branch; The error "System.NotSupportedException: Connector
pintout Unknown is not supported" might indicate that the ConfigurationManager isn't able find the gpioConfiguration, at least that is my assumption. I would need a RPi 3 to trace down the root cause of the error and potentially fix it.

@msanchez71 Thank you so much for the offer. I have been wanting a reason to pull the trigger to get myself a RPi 3 so maybe now is a good time. I wouldn't want to put you out of your RPi 3 while I tried to troubleshoot and this I2C issue.

[jyksnw]

I have been trying to re-situatiate myself with this project this evening as it has been about a years since I contributed to it. I have found that It has also been about a year since there has been any major contribution to this library. With the RPi 2 and RPi 3 having support for Windows 10 IoT I almost hate to suggest that one looks there for a more stable and viable C# based solution. Looks like they have the drivers for the I2C stuff in Win 10 IoT. Have a look at Windows 10 IoT and their GitHub. I did pull in the two pending Pull Requests into my fork and I will try to keep working on this project as my time permits, but I can't make any promises.

[psymonwhite]

I've been using the Windows 10 IoT for a while now, and although it works well enough, it's worth pointing out that it is not a full .Net implementation.

Many of the basic system libraries are missing and you have to look up the Windows Universal Platform way to do things.

I went over to this because the implementation is much smoother and the remote debugging is very easy to setup.

[OddmarDam]

I also tried the Windows iot but found a lot of the "old" ways are different. TCPClient is not there, last time i checked.
So please keep up the good work :)

[jyksnw]

Thanks for the feedback on Windows 10 IoT. I will gladly keep working on this, I don't have write privileges to this repository so I am going to focus on implementing any fixes on my fork of the project.

[Senna-chan]

After a long time I decided to respond to this thread. Yes Raspberry-sharp-io isn't updated for a long time. You can get I2C working on a Pi3 by hacking a bit in some classes but because of some unknown reason it is really buggy and unstable and I just remade my program in Python.
I couldn't(and wouldn't) use Windows 10 IoT because the network support is not that good(Can't even run ASP) and the whole coding of it is not what I'm used to.
I hope the devs of Raspberry-Sharp-IO are gonna update the code because it was really usefull. But till that time the choice for you guys could be either ditch Raspbian and use Windows 10 IoT or ditch .NET and try to use Python.

R.I.P. Pi 3. You served me well till a power addon board caused a malfunction.

I will keep this open so that people can post fixes here

[ebezine]

Hi,
Sorry for the late reply, the project is a bit frozen currently due to high pressure at work. Unfortunately I still haven't bought a Raspberry Pi 3 hence I'm not able to test.

As far as I understand the issue, RPi 3 pinout is not correctly detected in GpioConnectionSettings. I just had a look and it seem that RPi 2 is not handled (although it might be compatible with RPI B+ ?)

I'll try to buy a RPi 3 soon in order to make some tests and fix this issue.

Thanks for your support... and patience !

[ebezine]

Actually Pinout detection is made in Raspberry.Board (i.e in Raspberry.System assembly)