[
https://issues.apache.org/jira/browse/MYNEWT-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048613#comment-16048613
]
Vipul Rahane edited comment on MYNEWT-782 at 6/14/17 6:12 AM:
--------------------------------------------------------------
This might be a case of clock stretching as I encountered the same with BNO055.
I have a ticket open for it:
https://issues.apache.org/jira/browse/MYNEWT-631.
Linking it to this ticket to give more context. There is also a capture
attached to the ticket.
was (Author: vrahane):
This might be case of clock stretching as I encountered the same with BNO055. I
have a tickets opened for it:
https://issues.apache.org/jira/browse/MYNEWT-631.
Linking it to this ticket to give more context. There is also a capture
attached to the ticket.
> Atmel SAMD21 i2c probing
> ------------------------
>
> Key: MYNEWT-782
> URL: https://issues.apache.org/jira/browse/MYNEWT-782
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Reporter: Marko Kiiskila
>
> I have 2 test i2c devices. I can do 'i2c_scan' on either, but will discover
> the device only once.
> On subsequent runs the device does not report being present. Should
> investigate if this is because a) the device itself refuses to respond or b)
> hal i2c driver on SAMD21 is faulty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
