[jira] [Commented] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042058#comment-16042058 ] ASF subversion and git services commented on MYNEWT-649: Commit ba90f55894aba22391aebc52710fc95029752aea in incubator-mynewt-newt's branch refs/heads/master from [~cwanda] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=ba90f55 ] MYNEWT-649 Validate target variable target set command. Valid variables are: aflags, app, build_profile, bsp, cflags, lflags, loader, syscfg > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042059#comment-16042059 ] ASF subversion and git services commented on MYNEWT-649: Commit c14fb5e79fdb1a617e50e2475ae82de6478d0e19 in incubator-mynewt-newt's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=c14fb5e ] This closes #65. Merge remote-tracking branch 'cwanda/mynewt-649' * cwanda/mynewt-649: Add space between required and optional variable setting in usage output. MYNEWT-649 Validate target variable target set command. Valid variables are: aflags, app, build_profile, bsp, cflags, lflags, loader, syscfg > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-760) Switch testbench app over to CoAP (from plain NMP)
[ https://issues.apache.org/jira/browse/MYNEWT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042048#comment-16042048 ] ASF subversion and git services commented on MYNEWT-760: Commit bac13ef1af5436f3a0a025bbb4e161bc2b87e2bb in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=bac13ef ] MYNEWT-760 testbench: plain NMP --> OMP (CoAP). Fix build for non-BLE devices. > Switch testbench app over to CoAP (from plain NMP) > -- > > Key: MYNEWT-760 > URL: https://issues.apache.org/jira/browse/MYNEWT-760 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-770. Resolution: Fixed > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042041#comment-16042041 ] ASF subversion and git services commented on MYNEWT-770: Commit 20ef27fc9226300028e5065fb819ec6edf24209d in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=20ef27f ] This closes #306. Merge remote-tracking branch 'ccollins476ad/nosig-armv7' * ccollins476ad/nosig-armv7: native-*: Remove obsolete CONSOLE_UART definitions MYNEWT-770 Use sim package in native-mips BSP. MYNEWT-770 Use sim package in native-armv7 BSP. MYNEWT-770 Use sim package in native BSP. MYNEWT-770 Separate sim package. > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042039#comment-16042039 ] ASF subversion and git services commented on MYNEWT-770: Commit 20ef27fc9226300028e5065fb819ec6edf24209d in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=20ef27f ] This closes #306. Merge remote-tracking branch 'ccollins476ad/nosig-armv7' * ccollins476ad/nosig-armv7: native-*: Remove obsolete CONSOLE_UART definitions MYNEWT-770 Use sim package in native-mips BSP. MYNEWT-770 Use sim package in native-armv7 BSP. MYNEWT-770 Use sim package in native BSP. MYNEWT-770 Separate sim package. > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042038#comment-16042038 ] ASF subversion and git services commented on MYNEWT-770: Commit 5f41b4a731a381661db43982860f10ae3731cd86 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=5f41b4a ] MYNEWT-770 Use sim package in native-armv7 BSP. > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042037#comment-16042037 ] ASF subversion and git services commented on MYNEWT-770: Commit 9ddccbb4fd96eece2c7356cdd9980c3cd592870a in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=9ddccbb ] MYNEWT-770 Separate sim package. > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
[ https://issues.apache.org/jira/browse/MYNEWT-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042040#comment-16042040 ] ASF subversion and git services commented on MYNEWT-770: Commit 20ef27fc9226300028e5065fb819ec6edf24209d in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=20ef27f ] This closes #306. Merge remote-tracking branch 'ccollins476ad/nosig-armv7' * ccollins476ad/nosig-armv7: native-*: Remove obsolete CONSOLE_UART definitions MYNEWT-770 Use sim package in native-mips BSP. MYNEWT-770 Use sim package in native-armv7 BSP. MYNEWT-770 Use sim package in native BSP. MYNEWT-770 Separate sim package. > Sim - Share sig/no-sig implementation for all sim architectures > --- > > Key: MYNEWT-770 > URL: https://issues.apache.org/jira/browse/MYNEWT-770 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/306) > In MYNEWT-745, sim was split into two implementations: > * signals > * no-signals > The above change was applied to the i386 version of sim, but not to the other > sim implementations (ARMv7 and MIPS). > This ticket is for extracting the signals and no-signals code into a > standalone package that can be used by all sim implementations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-760) Switch testbench app over to CoAP (from plain NMP)
[ https://issues.apache.org/jira/browse/MYNEWT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042030#comment-16042030 ] ASF subversion and git services commented on MYNEWT-760: Commit 34eb7044a7bce770cac59289e7120d06570a7a46 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=34eb704 ] This closes #309. Merge remote-tracking branch 'ccollins476ad/testbench-coap' * ccollins476ad/testbench-coap: MYNEWT-760 testbench: plain NMP --> OMP (CoAP). > Switch testbench app over to CoAP (from plain NMP) > -- > > Key: MYNEWT-760 > URL: https://issues.apache.org/jira/browse/MYNEWT-760 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-760) Switch testbench app over to CoAP (from plain NMP)
[ https://issues.apache.org/jira/browse/MYNEWT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042029#comment-16042029 ] ASF subversion and git services commented on MYNEWT-760: Commit f848af17c0e899b475e3cf20b5e46fbf87f18f63 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f848af1 ] MYNEWT-760 testbench: plain NMP --> OMP (CoAP). > Switch testbench app over to CoAP (from plain NMP) > -- > > Key: MYNEWT-760 > URL: https://issues.apache.org/jira/browse/MYNEWT-760 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-550) ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
[ https://issues.apache.org/jira/browse/MYNEWT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042023#comment-16042023 ] ASF subversion and git services commented on MYNEWT-550: Commit 314d7ab58e7a90b2db5c2fd2424ab8b62cf3b198 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=314d7ab ] MYNEWT-550 Add ble_gattc_indicate_custom() > ble_gattc_indicate_custom to parallel ble_gattc_notify_custom > - > > Key: MYNEWT-550 > URL: https://issues.apache.org/jira/browse/MYNEWT-550 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Affects Versions: v1_0_0_beta1, v1_0_0_beta2 >Reporter: Simon Ratner >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > Would be very handy to send arbitrary indications, and seems like an omission > since the corresponding notify api is there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-550) ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
[ https://issues.apache.org/jira/browse/MYNEWT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-550. Resolution: Fixed > ble_gattc_indicate_custom to parallel ble_gattc_notify_custom > - > > Key: MYNEWT-550 > URL: https://issues.apache.org/jira/browse/MYNEWT-550 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Affects Versions: v1_0_0_beta1, v1_0_0_beta2 >Reporter: Simon Ratner >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > Would be very handy to send arbitrary indications, and seems like an omission > since the corresponding notify api is there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-550) ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
[ https://issues.apache.org/jira/browse/MYNEWT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042022#comment-16042022 ] ASF subversion and git services commented on MYNEWT-550: Commit 7bf8bf314891b3ee0b08ce76d7a9ed28fa061d32 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=7bf8bf3 ] MYNEWT-550 Signal GAP event for custom notifies. Prior to this change, only "non-custom" notifications signalled a GAP event. This is not right; all outgoing notifications should be indicated to the application. > ble_gattc_indicate_custom to parallel ble_gattc_notify_custom > - > > Key: MYNEWT-550 > URL: https://issues.apache.org/jira/browse/MYNEWT-550 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Affects Versions: v1_0_0_beta1, v1_0_0_beta2 >Reporter: Simon Ratner >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > Would be very handy to send arbitrary indications, and seems like an omission > since the corresponding notify api is there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-550) ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
[
https://issues.apache.org/jira/browse/MYNEWT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042024#comment-16042024
]
ASF subversion and git services commented on MYNEWT-550:
Commit be089fcd5b36c6ae2e24c157be111ab47721a100 in incubator-mynewt-core's
branch refs/heads/master from [~ccollins476]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=be089fc ]
This closes #310.
Merge remote-tracking branch 'ccollins476ad/indicate-custom'
* ccollins476ad/indicate-custom:
Fix typo ("ACM" should be "ACL").
MYNEWT-550 Add ble_gattc_indicate_custom()
MYNEWT-550 Signal GAP event for custom notifies.
> ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
> -
>
> Key: MYNEWT-550
> URL: https://issues.apache.org/jira/browse/MYNEWT-550
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Nimble
>Affects Versions: v1_0_0_beta1, v1_0_0_beta2
>Reporter: Simon Ratner
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> Would be very handy to send arbitrary indications, and seems like an omission
> since the corresponding notify api is there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MYNEWT-550) ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
[
https://issues.apache.org/jira/browse/MYNEWT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042025#comment-16042025
]
ASF subversion and git services commented on MYNEWT-550:
Commit be089fcd5b36c6ae2e24c157be111ab47721a100 in incubator-mynewt-core's
branch refs/heads/master from [~ccollins476]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=be089fc ]
This closes #310.
Merge remote-tracking branch 'ccollins476ad/indicate-custom'
* ccollins476ad/indicate-custom:
Fix typo ("ACM" should be "ACL").
MYNEWT-550 Add ble_gattc_indicate_custom()
MYNEWT-550 Signal GAP event for custom notifies.
> ble_gattc_indicate_custom to parallel ble_gattc_notify_custom
> -
>
> Key: MYNEWT-550
> URL: https://issues.apache.org/jira/browse/MYNEWT-550
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Nimble
>Affects Versions: v1_0_0_beta1, v1_0_0_beta2
>Reporter: Simon Ratner
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> Would be very handy to send arbitrary indications, and seems like an omission
> since the corresponding notify api is there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (MYNEWT-739) sensor_test app: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-739. - Resolution: Fixed > sensor_test app: improvements > - > > Key: MYNEWT-739 > URL: https://issues.apache.org/jira/browse/MYNEWT-739 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: drivers > Environment: nRF52dk with Adafruit BNO055 sensor and Minicom >Reporter: Sheela >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > This ticket will take care of any improvements we want for the app: > 1. Built code from the tip to include Sensors. Connected Adafruit BNO055 via > I2C interface to nRF52dk. Modified Syscfg to "nrf52_sensor > syscfg=BNO055_I2CBUS=0:I2C_0=1" for the BNO055 sensor. > Using sensors_test, issued 'sensor list' command which yielded "sensor dev = > color0, type = 0x8000 " as result. > Noticed that in syscfg the "TCS34725_PRESENT" was also set to '1' by default > and 'sensor list' automatically shows only that sensor. > sensor list should show all the sensors that are configured. > In the app tcs34725_config() was failing which was causing the sensor list to > not get populated. > 2. Remove config, gpio toggle stats, gpio toggle logs from the app. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-744. - Resolution: Fixed > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-724) mynewt, build on ubuntu
[ https://issues.apache.org/jira/browse/MYNEWT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-724. --- Resolution: Fixed > mynewt, build on ubuntu > --- > > Key: MYNEWT-724 > URL: https://issues.apache.org/jira/browse/MYNEWT-724 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel > Environment: Linux Version: > lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 14.04.4 LTS > Release: 14.04 > Codename: trusty > Go version: > go version > go version go1.7 linux/386 >Reporter: Filipe >Assignee: Wanda Chiu >Priority: Minor > > when building the mynewt on ubuntu I have an error on go builder: > syscfg/syscfg.go:965: constant 4294967295 overflows int > Seems that the SYSCFG_INTERRUPT_PRIO_MAX is too big for the variable "int" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-640) Add an newt target "amend" feature to amend or delete target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu closed MYNEWT-640.
-
> Add an newt target "amend" feature to amend or delete target variable values
> -
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MYNEWT-761) 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" command
[ https://issues.apache.org/jira/browse/MYNEWT-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-761. - > 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" > command > --- > > Key: MYNEWT-761 > URL: https://issues.apache.org/jira/browse/MYNEWT-761 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > *newtmgr mpstats* and *newtmgr taskstats* commands have been changed to > *newtmgr mpstat* and *newtmgr taskstat* (singular instead of plural) post > 1.0. The command guide and tutorials need to be updated to use the new > version for 1.1 documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-763) Add documentation for newt target amend command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-763. - > Add documentation for newt target amend command > --- > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target amend* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-764) Update Doc for newt run command
[ https://issues.apache.org/jira/browse/MYNEWT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-764. - > Update Doc for newt run command > --- > > Key: MYNEWT-764 > URL: https://issues.apache.org/jira/browse/MYNEWT-764 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document that *newt run* command now queries the user for a version > (or use default 0) the version is not provided for an application target, > instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041430#comment-16041430 ] ASF subversion and git services commented on MYNEWT-744: Commit afd861b3f3f9d0bed22117e461db45aa70c796b6 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=afd861b ] Merge pull request #258 from vrahane/MYNEWT-744 MYNEWT-744 SensorAPI: improvements > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041429#comment-16041429 ] ASF subversion and git services commented on MYNEWT-744: Commit 14c9c7abac7db73563bf0eb5fb61c26aca4da287 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=14c9c7a ] MYNEWT-744 Sensor imp remove dead code in app > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041431#comment-16041431 ] ASF subversion and git services commented on MYNEWT-744: Commit afd861b3f3f9d0bed22117e461db45aa70c796b6 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=afd861b ] Merge pull request #258 from vrahane/MYNEWT-744 MYNEWT-744 SensorAPI: improvements > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041428#comment-16041428 ] ASF subversion and git services commented on MYNEWT-744: Commit dff99ac72513431e0b2ec283a73b6603bd93275f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=dff99ac ] MYNEWT-744 Sensor imp, OIC gyro > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041427#comment-16041427 ] ASF subversion and git services commented on MYNEWT-744: Commit 1437e4951a229e73cb830c838d5633b5fd5aae21 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1437e49 ] MYNEWT-744 remove unused code > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041426#comment-16041426 ] ASF subversion and git services commented on MYNEWT-744: Commit 1341ed45f2851e6f69c380ba53e284db954f7beb in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1341ed4 ] MYNEWT-744 Sensor imp gyroscope fix - Gyroscope data structure was not defined, hence the data was not seen > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041423#comment-16041423 ] ASF subversion and git services commented on MYNEWT-744: Commit 7ffb3408e9049498e1dee656e049a440da77e00a in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=7ffb340 ] MYNEWT-744 Sensor imp cfg, types and other changes - Add default cfg for the external sensors in the creator package so that all the sensors on the sensor device get initialized - Add a mask field to the sensor structure so that differentiating between supported Vs configured sensors is possible - Change the sensor_mgr_match_bytype() function to check w.r.t mask. - Adding config variable for mask for different drivers in their respective structures. - Adding an API to set the sensor types based on the mask. - Moving config_sensor() out of the app into the creator package and the bsp. Objective is to show how a developer would initialize and configure the sensor in the bsp which is normally the practice. - Changing sensor_shell command "list" to show only configured types. - sensor_shell cmd "type" shows supported types by the driver. > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041422#comment-16041422 ] ASF subversion and git services commented on MYNEWT-744: Commit d3e3cfc0f2a94bb8317607e1e29328841730544e in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d3e3cfc ] MYNEWT-744 Add missing comments and remove get itf > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041424#comment-16041424 ] ASF subversion and git services commented on MYNEWT-744: Commit b480aa4f124eab90a9f86642a511e22eebbb5773 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=b480aa4 ] MYNEWT-744 Sensor imp, change device name - Change device name in app to be sensy > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-664) coredownload newtmgr command should indicate core size in first response
[ https://issues.apache.org/jira/browse/MYNEWT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041321#comment-16041321 ] ASF subversion and git services commented on MYNEWT-664: Commit cab9dea5bb8fce60ac322a6cf5d3dec759ca4bf1 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=cab9dea ] MYNEWT-664 add length to coredownload rsp. > coredownload newtmgr command should indicate core size in first response > > > Key: MYNEWT-664 > URL: https://issues.apache.org/jira/browse/MYNEWT-664 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/312) > This would be analogous to the "image upload", "file upload", and "file > download" commands. Each of these indicate the total number of bytes in the > first packet. > This change involves a backwards compatible modification to the NMP protocol. > Compatibility is maintained because this change only requires the addition > of a new field, not the modification or removal of existing fields. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-689) CONSOLE_UART syscfg value
[ https://issues.apache.org/jira/browse/MYNEWT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041322#comment-16041322 ] ASF subversion and git services commented on MYNEWT-689: Commit 63214275a0aad5cdc857e83dd987adf705d6eafe in incubator-mynewt-core's branch refs/heads/master from [~wes3] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6321427 ] MYNEWT-689: Make CONSOLE_UART a syscfg variable. Update stm32f7discovery bsp. > CONSOLE_UART syscfg value > - > > Key: MYNEWT-689 > URL: https://issues.apache.org/jira/browse/MYNEWT-689 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: BSP >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: William San Filippo > Fix For: v1_1_0_rel > > > Currently CONSOLE_UART is hard-coded in bsp/bsp.h. > It would be better as a syscfg value, so that switching the console to UART1, > for example, didn't require modifying the bsp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
