My apologies, I should have done a better job stating my problem.
I’m perfectly fine with using TinyCLR alpha. In fact I specifically installed a TinyCLR just two days ago to try it out. Mainly because it works with VS 2017.
I’ve tried communicating with the device using software I2C and it works but with glitches. The problem with software I2C is that it only supports clock frequency of 100 KHz at the moment, but device requires 400 KHz (hardware mode) and this causing some interesting fluctuations in the temperature readings
My question is regarding the fact that before version 0.5 DeviceInformation.FindAll had an implementation:
but starting from version 0.5 the implementation was replaced with “NotSupportedException”:
This was done intentionally and it was documented in the release notes. What I was not able to find in the release notes is a correct/recommended way of initializing the I2C channel now.
Just want to make sure I’m doing everything by the book, before claiming that there is bug in TinyCLR OS