<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Dec 24, 2016, at 10:24 AM, Alan Cudmore <<a href="mailto:alan.cudmore@gmail.com" class="">alan.cudmore@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Scott,<div class="">The raspberry pi BSP uses the newer Linux I2C API, which is used in a few BSPs. </div><div class="">I have been able to use the I2C API for a few devices on the Pi, and I have been slowly working on trying to support the sense hat. </div><div class="">I have a sense hat display driver in the “dpi-drivers” branch of my RKI project:</div><div class=""><a href="https://github.com/alanc98/rki/tree/rpi-drivers" class="">https://github.com/alanc98/rki/tree/rpi-drivers</a></div><div class=""><br class=""></div><div class="">Sense hat display driver in action here:</div><div class=""><a href="https://www.youtube.com/watch?v=cHYxj6aW4jI" class="">https://www.youtube.com/watch?v=cHYxj6aW4jI</a></div><div class=""><br class=""></div><div class="">The code to drive that demo is here:</div><div class=""><a href="https://github.com/alanc98/rki/blob/rpi-drivers/sensehatdisplay_cmd.c" class="">https://github.com/alanc98/rki/blob/rpi-drivers/sensehatdisplay_cmd.c</a></div><div class=""><br class=""></div><div class="">The project is setup so you can add and test drivers without adding them to the RTEMS tree. </div><div class=""><br class=""></div><div class="">The sense hat display driver does bring out a bug ( maybe a race condition ? ) in the I2C Pi BSP code. I had to add a delay in the Pi I2C support code to make the sense hat display work correctly. I can’t seem to locate that patch right now, I’ll have to find it. </div><div class=""><br class=""></div><div class="">I was starting to work on the HTS221 Temp/Humidity driver next. </div><div class="">It would be great to get someone else helping with the rest of the drivers. </div><div class=""><br class=""></div><div class="">I was also trying to test the SPI support, but I have been unable to get a driver for my simple SPI device to work. ( works on Arduino and Pi/Linux ). I think we need to convert the SPI support in the Pi BSP to the new SPI framework anyway, so it’s worth revisiting the SPI implementation. </div><div class=""><br class=""></div><div class="">Alan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 23, 2016, at 11:14 PM, Scott Zemerick <<a href="mailto:scott@zemericks.com" class="">scott@zemericks.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Is anyone currently using i2c with the raspberrypi2 - and more specifically the SenseHat? The i2c bsp code looks mostly complete, but I am confused as to which i2c API functions to call, with some concern that the i2c bsp support isn't complete. A quick comparison of the pi i2c code with the spi code shows some design differences, with the latter looking more complete. I plan on digging more into the pi bsp, but I would like to know the current state and if anyone has a basic example of pi i2c. Thanks! </div>
_______________________________________________<br class="">users mailing list<br class=""><a href="mailto:users@rtems.org" class="">users@rtems.org</a><br class=""><a href="http://lists.rtems.org/mailman/listinfo/users" class="">http://lists.rtems.org/mailman/listinfo/users</a></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>