[jira] [Updated] (MYNEWT-631) SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro

2017-06-13 Thread Vipul Rahane (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYNEWT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vipul Rahane updated MYNEWT-631:

Component/s: drivers

> SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro
> -
>
> Key: MYNEWT-631
> URL: https://issues.apache.org/jira/browse/MYNEWT-631
> Project: Mynewt
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: drivers
>Affects Versions: v1_0_0_beta2
>Reporter: Vipul Rahane
>Assignee: Vipul Rahane
>Priority: Minor
> Attachments: bno055_capture.png
>
>
> While trying out different sensors with the SensorsAPI, a bug was found with 
> the Arduino Zero Pro/M0 Pro. BNO055 does not work with it. Attaching the 
> timing capture while reading the CHIP_ID of the sensor.
> Most probably this is due to clock stretching, this can be observed in the 
> capture. The sensor works fine with nRF52DK.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (MYNEWT-631) SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro

2017-03-21 Thread Vipul Rahane (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYNEWT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vipul Rahane updated MYNEWT-631:

Summary: SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro  
(was: BNO055 Sensor not working with Arduino M0/Zero Pro)

> SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro
> -
>
> Key: MYNEWT-631
> URL: https://issues.apache.org/jira/browse/MYNEWT-631
> Project: Mynewt
>  Issue Type: Bug
>Affects Versions: v1_0_0_beta2
>Reporter: Vipul Rahane
>Assignee: Vipul Rahane
>Priority: Minor
> Attachments: bno055_capture.png
>
>
> While trying out different sensors with the SensorsAPI, a bug was found with 
> the Arduino Zero Pro/M0 Pro. BNO055 does not work with it. Attaching the 
> timing capture while reading the CHIP_ID of the sensor.
> Most probably this is due to clock stretching, this can be observed in the 
> capture. The sensor works fine with nRF52DK.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)