在等待本机支持时，I2C发生了什么变化?值得麻烦还是应该等待? [英] Bit-banging I2C while waiting for native support? Worth the trouble or should we wait?

问题描述

是否有人试图在应用处理器上的软件中模拟I2C(即使用GPIO引脚的位敲打")?

如果有人已经做过，我们宁愿不花时间重新发明轮子.

此外，如果I2C的本地支持"不被采用，我们宁愿不浪费任何这样的周期.将在下一个软件版本中提供:)

Microsoft团队对此有何看法?

谢谢！
M

---

Manu

解决方案

FYI
https://www.element14.com/community/people/Workshopshed/blog/2018/11/23/azure-sphere-secure-iot-i2c-compass

我们发布了MT3620 Grove Shield.它使用UART-I2c桥接芯片.

http://wiki.seeedstudio.com/Grove_Starter_Kit_for_Azure_Sphere_MT3620_Development_Kit/

Has anyone tried to emulate I2C in software (i.e. "bit-banging" using GPIO pins) on the application processor?

We would rather not spend time reinventing the wheel if someone's done it already.

Also, we would rather not waste any such cycles if I2C "native support" were to become available in the next software release :)

Microsoft team, any perspective on this?

Thanks!
M

---

Manu

解决方案

FYI
https://www.element14.com/community/people/Workshopshed/blog/2018/11/23/azure-sphere-secure-iot-i2c-compass

We released MT3620 Grove Shield. It use UART-I2c bridge chip.

http://wiki.seeedstudio.com/Grove_Starter_Kit_for_Azure_Sphere_MT3620_Development_Kit/

这篇关于在等待本机支持时，I2C发生了什么变化?值得麻烦还是应该等待?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！