[jira] [Commented] (MYNEWT-787) serial boot loader - newtmgr buffer overruns
[ https://issues.apache.org/jira/browse/MYNEWT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054949#comment-16054949 ] ASF subversion and git services commented on MYNEWT-787: Commit 09408a3fa9d24d5f7bb2436867e247b48e3b58ae in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=09408a3 ] MYNEWT-787 serial boot loader - nmp buf overruns The serial boot loader fails to process some newtmgr commands: 1. The image list response is too large for the outgoing buffer. 2. The "new" newtmgr sends large image chunks in its image upload requests. These chunks are too large for the serial boot loader's input buffer. The fixes are as follows: 1. Increase the outgoing buffer size from 48 to 80. 2. Increase the incoming buffer size from 128 to 512. 3. Return an error rather than overrun the output buffer. > serial boot loader - newtmgr buffer overruns > > > Key: MYNEWT-787 > URL: https://issues.apache.org/jira/browse/MYNEWT-787 > Project: Mynewt > Issue Type: New Feature > 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/340) > The serial boot loader fails to process some newtmgr commands: > 1. The image list response is too large for the outgoing buffer. > 2. The "new" newtmgr sends large image chunks in its image upload requests. > These chunks are too large for the serial boot loader's input buffer. > The fixes are as follows: > 1. Increase the outgoing buffer size from 48 to 80. > 2. Increase the incoming buffer size from 128 to 512. > 3. Return an error rather than overrun the output buffer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052364#comment-16052364 ] ASF subversion and git services commented on MYNEWT-750: Commit 9572c52fa2a0c67b6a2a15ec3dca4501fd24a29b in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=9572c52 ] MYNEWT-750 BLE Host - Persist SC flag for bonds. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052365#comment-16052365 ] ASF subversion and git services commented on MYNEWT-750: Commit 6e380728c1382e679e2c6967e6820dfc4f48b116 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6e38072 ] MYNEWT-750 - Authenticated flag incorrect. We would persist the authenticated flag if either peer supported authentication. We should only persist it if both support it. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052363#comment-16052363 ] ASF subversion and git services commented on MYNEWT-750: Commit cb7782d7b4f322799510d293a23a65061244f6c8 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=cb7782d ] MYNEWT-750 Fix some coding style issues. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052366#comment-16052366 ] ASF subversion and git services commented on MYNEWT-750: Commit b6d96411b6af18360c5a8fc4f8d31d473b99118a in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=b6d9641 ] MYNEWT-750 BLE Host - Ignore pair from bonded peer If a device is already bonded, ;he host should not allow the same device to pair again. Currently, the host blindly proceeds with the pairing operation. This should not be allowed because the second peer could be an imposter masquerading as the original. New behavior in such a scenario: 1. Host notifies application of the duplicate pairing attempt via the gap event callback. The callback specifies a new event code (BLE_GAP_EVENT_REPEAT_PAIRING) that specifically indicates a duplicate pairing attempt. 2. The gap event callback returns an error code indicating which of the following behaviors to perform: a. Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting bond. The stack will verify the bond has been deleted and continue the pairing procedure. If the bond is still present, this event will be reported again. b. Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently ignore the pairing request. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052367#comment-16052367 ] ASF subversion and git services commented on MYNEWT-750: Commit 729c34e4e2f692a9c5fc4a8d4024b91eff856358 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=729c34e ] MYNEWT-750 Fix build when SM disabled. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052368#comment-16052368 ] ASF subversion and git services commented on MYNEWT-750: Commit 79fcf1d2a81d3487f237d696c69d6a904bb94ec5 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=79fcf1d ] MYNEWT-750 Handle repeat pairing in e.g. apps. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > If a device is already bonded, the host should not allow the same device to > pair again. Currently, the host blindly proceeds with the pairing operation. > This should not be allowed because the second peer could be an imposter > masquerading as the original. > I propose the following behavior in such a scenario: > # Host notifies application of the duplicate pairing attempt via the gap > event callback. The callback would specify a new event code that > specifically indicates a duplicate pairing attempt. > # The gap event callback would return an error code indicating which of the > following behaviors to perform: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050020#comment-16050020 ] ASF subversion and git services commented on MYNEWT-768: Commit 4ce6e7c3c1340add8ceea46b477e4301b8762d6c in incubator-mynewt-newtmgr's branch refs/heads/master from [~cwanda] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=4ce6e7c ] MYNEWT-768 help text for newtmgr image erase command. Added more help text to explain when an image can be erased and matches documentation. > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > 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 *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050021#comment-16050021 ] ASF subversion and git services commented on MYNEWT-768: Commit 041577f608f74abf9f4b6580c0b1692d1fa3ca94 in incubator-mynewt-newtmgr's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=041577f ] Merge pull request #2 from cwanda/image_erase_help MYNEWT-768 help text for newtmgr image erase command. > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > 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 *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-529) i2c bus scanner
[
https://issues.apache.org/jira/browse/MYNEWT-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048588#comment-16048588
]
ASF subversion and git services commented on MYNEWT-529:
Commit 1839134dc34a9797d1f50733351e3d32a96fcea0 in incubator-mynewt-core's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1839134 ]
MYNEWT-529 - move i2c_scan to a separate package.
> i2c bus scanner
> ---
>
> Key: MYNEWT-529
> URL: https://issues.apache.org/jira/browse/MYNEWT-529
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: HAL
>Reporter: Marko Kiiskila
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Bring in Kevin's i2c bus scanner, probably in form of separate package.
> test/i2c_tools maybe?
> static int
> shell_i2cscan_cmd(int argc, char **argv)
> {
>uint8_t addr;
>int32_t timeout = OS_TICKS_PER_SEC / 10;
>uint8_t dev_count = 0;
>console_printf("Scanning I2C bus 0\n"
> " 0 1 2 3 4 5 6 7 8 9 a b c de f\n"
> "00: ");
>/* Scan all valid I2C addresses (0x03..0x77) */
>for (addr = 0x08; addr < 0x78; addr++) {
>int rc = hal_i2c_master_probe(0, addr, timeout);
>/* Print addr header every 16 bytes */
>if (!(addr % 16)) {
> console_printf("\n%02x: ", addr);
>}
>/* Display the addr if a response was received */
>if (!rc) {
>console_printf("%02x ", addr);
>dev_count++;
>} else {
>console_printf("-- ");
>}
>}
>console_printf("\nFound %u devices on I2C bus 0\n", dev_count);
>return 0;
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-699) recreate linker files which show how to build olimex bsp to run from RAM
[ https://issues.apache.org/jira/browse/MYNEWT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048575#comment-16048575 ] ASF subversion and git services commented on MYNEWT-699: Commit 6a896c0cd2127a9b4def97f940fdaadf53d23445 in incubator-mynewt-core's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6a896c0 ] MYNEWT-699; re-add sample linker scripts to Olimex BSP. > recreate linker files which show how to build olimex bsp to run from RAM > > > Key: MYNEWT-699 > URL: https://issues.apache.org/jira/browse/MYNEWT-699 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > I removed them as unused, without realizing that our tutorials talk refer > them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-699) recreate linker files which show how to build olimex bsp to run from RAM
[ https://issues.apache.org/jira/browse/MYNEWT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048576#comment-16048576 ] ASF subversion and git services commented on MYNEWT-699: Commit 596c007dc79bd64c721bc4d2a945024eba08c4f0 in incubator-mynewt-core's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=596c007 ] Merge pull request #334 from mkiiskila/olimex_xtra_ld MYNEWT-699; re-add sample linker scripts to Olimex BSP. > recreate linker files which show how to build olimex bsp to run from RAM > > > Key: MYNEWT-699 > URL: https://issues.apache.org/jira/browse/MYNEWT-699 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > I removed them as unused, without realizing that our tutorials talk refer > them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048469#comment-16048469 ] ASF subversion and git services commented on MYNEWT-780: Commit 3e044fc39584b91d48114d9132bbad0eb106592f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3e044fc ] Merge pull request #331 from vrahane/MYNEWT-780 MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048464#comment-16048464 ] ASF subversion and git services commented on MYNEWT-779: Commit 6d63e997396ad92dee3e03fb49cdb98196ef2c78 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6d63e99 ] Merge pull request #332 from vrahane/MYNEWT-779 MYNEWT-779 tcs34725 driver: remove os_time_delay() > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048465#comment-16048465 ] ASF subversion and git services commented on MYNEWT-779: Commit 6d63e997396ad92dee3e03fb49cdb98196ef2c78 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6d63e99 ] Merge pull request #332 from vrahane/MYNEWT-779 MYNEWT-779 tcs34725 driver: remove os_time_delay() > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048466#comment-16048466 ] ASF subversion and git services commented on MYNEWT-780: Commit 43c2103373045cd0bac1e597cfbdf66d2c4ec1d3 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=43c2103 ] MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048467#comment-16048467 ] ASF subversion and git services commented on MYNEWT-780: Commit 08c184989ce45aa34d1316a259517c8252ca3a3a in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=08c1849 ] MYNEWT-780 TCS34725 exposing address cfg for shell > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048468#comment-16048468 ] ASF subversion and git services commented on MYNEWT-780: Commit 3e044fc39584b91d48114d9132bbad0eb106592f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3e044fc ] Merge pull request #331 from vrahane/MYNEWT-780 MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048463#comment-16048463 ] ASF subversion and git services commented on MYNEWT-779: Commit fdd2557773886fb9002c3f125a5dd9a14982623d in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=fdd2557 ] MYNEWT-779 tcs34725 driver: remove os_time_delay() - Removing os_time_delay() from driver and moving it to shell for using it with shell. - Sensor framework polling timer should be used for reading instead of os_time_delay(). > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048375#comment-16048375
]
ASF subversion and git services commented on MYNEWT-720:
Commit cd248f806a8a1325caea1f55c2d8f5314035 in incubator-mynewt-newt's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=cd248f8 ]
Merge pull request #68 from mkiiskila/re-sign
MYNEWT-720; add 'newt resign-image' command.
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048374#comment-16048374
]
ASF subversion and git services commented on MYNEWT-720:
Commit 25b3864b689cb1101dc280c9fc7a1a6c64df8a25 in incubator-mynewt-newt's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=25b3864 ]
MYNEWT-720; add 'newt resign-image' command.
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048277#comment-16048277 ] ASF subversion and git services commented on MYNEWT-681: Commit 618f56a734808a7931f0626d9a8e401bd5cfc518 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=618f56a ] Merge pull request #318 from vrahane/MYNEWT-681 MYNEWT-681 rb-nano2 remove flash write protection in download scripts > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048276#comment-16048276 ] ASF subversion and git services commented on MYNEWT-681: Commit 618f56a734808a7931f0626d9a8e401bd5cfc518 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=618f56a ] Merge pull request #318 from vrahane/MYNEWT-681 MYNEWT-681 rb-nano2 remove flash write protection in download scripts > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048274#comment-16048274 ] ASF subversion and git services commented on MYNEWT-681: Commit 3a0fd9da5541ee381e2b672375a8775475902d7c in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3a0fd9d ] MYNEWT-681 openocd script remove unused file > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048278#comment-16048278 ] ASF subversion and git services commented on MYNEWT-781: Commit 17060baba1c59df0d83b395c4c629a41a1a8c4b1 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=17060ba ] MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048280#comment-16048280 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048275#comment-16048275 ] ASF subversion and git services commented on MYNEWT-681: Commit d59f281f45e69855ea3630d65b6b2df55af54bf4 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d59f281 ] MYNEWT-681 openocd script fix wrong indentation > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048281#comment-16048281 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048221#comment-16048221 ] ASF subversion and git services commented on MYNEWT-777: Commit 9379a3d62513a53288f07bb91e7897a82ae1846f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=9379a3d ] Merge pull request #325 from vrahane/MYNEWT-777 MYNEWT-777 SensorAPI: Use util/parse pkg instead of using sensor_shell_stol() > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048219#comment-16048219 ] ASF subversion and git services commented on MYNEWT-777: Commit b3dfb7c6729c092e4ea528fe1ca55ed5b829b8fc in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=b3dfb7c ] MYNEWT-777 SensorAPI: Use util/parse pkg - Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-752) Error in setting the "permanent" flag upon confirm with hash during image upgrade
[ https://issues.apache.org/jira/browse/MYNEWT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048185#comment-16048185 ] ASF subversion and git services commented on MYNEWT-752: Commit 572cfa1c3473d4a42cc726944b176b2a5c485692 in incubator-mynewt-core's branch refs/heads/master from ccollins476ad [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=572cfa1 ] Merge pull request #313 from ccollins476ad/img-test-perm MYNEWT-752 Allow confirm of tentative slot. > Error in setting the "permanent" flag upon confirm with hash during image > upgrade > - > > Key: MYNEWT-752 > URL: https://issues.apache.org/jira/browse/MYNEWT-752 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > This is an issue seen during image upgrade. When doing a "confirm" with a > hash, newtmgr always marks the "permanent" flag for Slot 1 image to "true", > irrespective of which image the hash matches. > This works fine when we skip the "test" step during image upgrade and we > issue a "confirm" with a hash of the new image in Slot 1. > However, if we do the "test" step (when the new image is swapped into Slot > 0), and we then do a "confirm" with a hash of the new image and reboot, the > device marks the old image in Slot 1 as "permanent" and swaps it back to Slot > 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047278#comment-16047278 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047277#comment-16047277 ] ASF subversion and git services commented on MYNEWT-781: Commit 17060baba1c59df0d83b395c4c629a41a1a8c4b1 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=17060ba ] MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047279#comment-16047279 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-778) newt - "newt run" fails for native targets
[ https://issues.apache.org/jira/browse/MYNEWT-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047189#comment-16047189 ] ASF subversion and git services commented on MYNEWT-778: Commit 911007a63756cc64592f4b6e47f08a151cc59a3d in incubator-mynewt-newt's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=911007a ] Merge pull request #67 from ccollins476ad/sim-version MYNEWT-778 newt - "newt run" fails for native tgts > newt - "newt run" fails for native targets > -- > > Key: MYNEWT-778 > URL: https://issues.apache.org/jira/browse/MYNEWT-778 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > This issue seems to have been introduced by MYNEWT-694. > If the user runs "newt run" without specifying a version number, newt prompts > the user for a version number and uses it to build an image. This behavior > is correct most of the time, but it is incorrect for sim targets. Sim > targets use plain elf files, not image files, so newt shouldn't prompt the > user for a version number in this case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-778) newt - "newt run" fails for native targets
[ https://issues.apache.org/jira/browse/MYNEWT-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047188#comment-16047188 ] ASF subversion and git services commented on MYNEWT-778: Commit 228ca75c865dcb3cd04a64217b77fea046ccd053 in incubator-mynewt-newt's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=228ca75 ] MYNEWT-778 newt - "newt run" fails for native tgts > newt - "newt run" fails for native targets > -- > > Key: MYNEWT-778 > URL: https://issues.apache.org/jira/browse/MYNEWT-778 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > This issue seems to have been introduced by MYNEWT-694. > If the user runs "newt run" without specifying a version number, newt prompts > the user for a version number and uses it to build an image. This behavior > is correct most of the time, but it is incorrect for sim targets. Sim > targets use plain elf files, not image files, so newt shouldn't prompt the > user for a version number in this case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047106#comment-16047106 ] ASF subversion and git services commented on MYNEWT-681: Commit d59f281f45e69855ea3630d65b6b2df55af54bf4 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d59f281 ] MYNEWT-681 openocd script fix wrong indentation > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047105#comment-16047105 ] ASF subversion and git services commented on MYNEWT-681: Commit 03d311c3e5c6a0f0634791cc45b97b26da88a128 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=03d311c ] MYNEWT-681 remove flash write protection - Add EXTRA_GDB_CMDS variable which would go to the GDB_CMD_FILE in the openocd script. - removing write protection in download script by setting the write protection bits in the BPROT config registers. Also, setting the DISABLEINDEBUG register - Using CFG_POST_INIT instead of EXTRA_GDB_CMDS since openocd can handle writing registers and it's a good idea to use openocd rather than using gdb to disabel write protection > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-774) Intermittent serial errors in newtmgr messages on Arduino Zero
[ https://issues.apache.org/jira/browse/MYNEWT-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043486#comment-16043486 ] ASF subversion and git services commented on MYNEWT-774: Commit ee14e32eb54f3b93b6d632ad64ae57d26fbfbf2d in incubator-mynewt-core's branch refs/heads/master from ccollins476ad [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=ee14e32 ] Merge pull request #323 from ccollins476ad/shell-max-events MYNEWT-774 Serial errors in newtmgr messages > Intermittent serial errors in newtmgr messages on Arduino Zero > -- > > Key: MYNEWT-774 > URL: https://issues.apache.org/jira/browse/MYNEWT-774 > 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/323) > Using the nmgr_shell transport (newtmgr over shell), some incoming commands > get dropped. The problem seems to be caused by an exhaustion of shell events. > By default, the shell only allocates a single event. > The sequence looks like this: > # Client sends newtmgr command to device. > # Console passes newtmgr command to shell. > # Shell allocates the only event and fills it with the data. > # Shell processes event, hands data to newtmgr code. > # Newtmgr processes command and sends response. > # Client sees response and sends follow-up command. > # Console passes newtmgr command to shell. > # Shell has no events left; drops incoming command. > # Initial event gets freed. > By changing the default event count from 1 to 2, we ensure there is always a > spare event available. Since we will never send the second response before > freeing the first event, two events is sufficient. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-775) Crash due to unaligned accesses during CoAP parsing.
[ https://issues.apache.org/jira/browse/MYNEWT-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043482#comment-16043482 ] ASF subversion and git services commented on MYNEWT-775: Commit 2b23934335b25cde92ebb80a9330210aa662ab05 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=2b23934 ] MYNEWT-775 Crash; unaligned accesses: CoAP parsing > Crash due to unaligned accesses during CoAP parsing. > > > Key: MYNEWT-775 > URL: https://issues.apache.org/jira/browse/MYNEWT-775 > 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/322) > Some code assumes that an mbuf's om_data pointer is suitably aligned for > struct pointer access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-775) Crash due to unaligned accesses during CoAP parsing.
[ https://issues.apache.org/jira/browse/MYNEWT-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043483#comment-16043483 ] ASF subversion and git services commented on MYNEWT-775: Commit 258625bdc299d414d6ad4283b0e30e9dacdd62d8 in incubator-mynewt-core's branch refs/heads/master from ccollins476ad [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=258625b ] Merge pull request #322 from ccollins476ad/coap-unaligned MYNEWT-775 Crash; unaligned accesses: CoAP parsing > Crash due to unaligned accesses during CoAP parsing. > > > Key: MYNEWT-775 > URL: https://issues.apache.org/jira/browse/MYNEWT-775 > 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/322) > Some code assumes that an mbuf's om_data pointer is suitably aligned for > struct pointer access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-738) Fix Parameter arrays in events and elsewhere
[ https://issues.apache.org/jira/browse/MYNEWT-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043301#comment-16043301 ] ASF subversion and git services commented on MYNEWT-738: Commit f0ca77a427f0aca30400b71a21f3206471a878fa in incubator-mynewt-core's branch refs/heads/master from [~janc] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f0ca77a ] Merge pull request #311 from wes3/myn738 MYNEWT-738: Fix parameter arrays > Fix Parameter arrays in events and elsewhere > > > Key: MYNEWT-738 > URL: https://issues.apache.org/jira/browse/MYNEWT-738 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Affects Versions: v1_0_0_rel >Reporter: William San Filippo >Assignee: William San Filippo > Fix For: v1_1_0_rel > > > It appears that for some events and possible commands that the specification > was interpreted incorrectly. Multiple parameter arrays are treated in the > following manner: > Arrayed parameters are specified using the following notation: ParameterA[i]. > If more than one set of arrayed parameters are specified (e.g. ParameterA[i], > ParameterB[i]), then the order of the parameters are as follows: > ParameterA[0], ParameterB[0], ParameterA[1], ParameterB[1], ParameterA[2], > ParameterB[2], … ParameterA[n], ParameterB[n] > Need to go through the controller and host code to fix all places where this > is incorrect. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-738) Fix Parameter arrays in events and elsewhere
[ https://issues.apache.org/jira/browse/MYNEWT-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043300#comment-16043300 ] ASF subversion and git services commented on MYNEWT-738: Commit c921fd5c652fad3505d598f14f53441d4be32566 in incubator-mynewt-core's branch refs/heads/master from [~wes3] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c921fd5 ] MYNEWT-738: Fix parameter arrays This code change fixes our incorrect interpretation of the BLE specification regarding parameter arrays when parsing advertising reports. > Fix Parameter arrays in events and elsewhere > > > Key: MYNEWT-738 > URL: https://issues.apache.org/jira/browse/MYNEWT-738 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Affects Versions: v1_0_0_rel >Reporter: William San Filippo >Assignee: William San Filippo > Fix For: v1_1_0_rel > > > It appears that for some events and possible commands that the specification > was interpreted incorrectly. Multiple parameter arrays are treated in the > following manner: > Arrayed parameters are specified using the following notation: ParameterA[i]. > If more than one set of arrayed parameters are specified (e.g. ParameterA[i], > ParameterB[i]), then the order of the parameters are as follows: > ParameterA[0], ParameterB[0], ParameterA[1], ParameterB[1], ParameterA[2], > ParameterB[2], … ParameterA[n], ParameterB[n] > Need to go through the controller and host code to fix all places where this > is incorrect. -- 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=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] [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] [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] [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)
[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=16039971#comment-16039971 ] ASF subversion and git services commented on MYNEWT-664: Commit b88eb9cfdbfc539dbdded17a3f1cf604497a9c6c in incubator-mynewt-newtmgr's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=b88eb9c ] 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-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=16039822#comment-16039822 ] ASF subversion and git services commented on MYNEWT-664: Commit 27990a44e7ca28e2f9edd8fba62658af5737b555 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=27990a4 ] Merge pull request #312 from ccollins476ad/coredownload-len 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-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=16039821#comment-16039821 ] ASF subversion and git services commented on MYNEWT-664: Commit 4d0ab7febe7b13861f77d4a7048345866d4a634a in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=4d0ab7f ] 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-772) BLE Host - Initial set-event-mask specifies reserved bits
[
https://issues.apache.org/jira/browse/MYNEWT-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039710#comment-16039710
]
ASF subversion and git services commented on MYNEWT-772:
Commit a56d659361fc25ac75fca399ac89838cc5847b74 in incubator-mynewt-core's
branch refs/heads/master from [~ccollins476]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=a56d659 ]
MYNEWT-772 BLE Host - Rsrvd bits in set-event-mask
The host intends to enable the following events at start up:
/**
* Enable the following events:
* 0x0001 Inquiry Complete Event
* 0x0002 Inquiry Result Event
* 0x0004 Connection Complete Event
* 0x0008 Connection Request Event
* 0x0010 Disconnection Complete Event
* 0x0020 Authentication Complete Event
* 0x0040 Remote Name Request Complete Event
* 0x0080 Encryption Change Event
* 0x0100 Change Connection Link Key Complete Event
* 0x0200 Master Link Key Complete Event
* 0x0400 Read Remote Supported Features Complete Event
* 0x0800 Read Remote Version Information Complete Event
* 0x1000 QoS Setup Complete Event
* 0x2000 Reserved
* 0x4000 Reserved
* 0x8000 Hardware Error Event
* 0x0001 Flush Occurred Event
* 0x0002 Role Change Event
* 0x0004 Reserved
* 0x0008 Mode Change Event
* 0x0010 Return Link Keys Event
* 0x0020 PIN Code Request Event
* 0x0040 Link Key Request Event
* 0x0080 Link Key Notification Event
* 0x0100 Loopback Command Event
* 0x0200 Data Buffer Overflow Event
* 0x0400 Max Slots Change Event
* 0x0800 Read Clock Offset Complete Event
* 0x1000 Connection Packet Type Changed Event
* 0x2000 QoS Violation Event
* 0x4000 Page Scan Mode Change Event [deprecated]
* 0x8000 Page Scan Repetition Mode Change Event
* 0x0001 Flow Specification Complete Event
* 0x0002 Inquiry Result with RSSI Event
* 0x0004 Read Remote Extended Features Complete Event
* 0x0800 Synchronous Connection Complete Event
* 0x1000 Synchronous Connection Changed Event
* 0x8000 Encryption Key Refresh Complete Event
* 0x2000 LE Meta-Event
*/
It does this by setting the following bit mask: 0x20009fff. This
mask is incorrect; it should be: 0x20009807
> BLE Host - Initial set-event-mask specifies reserved bits
> -
>
> Key: MYNEWT-772
> URL: https://issues.apache.org/jira/browse/MYNEWT-772
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Nimble
>Reporter: Christopher Collins
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> (Pull request: https://github.com/apache/incubator-mynewt-core/pull/307)
> The host intends to enable the following events at start up:
> {noformat}
> /**
> * Enable the following events:
> * 0x0001 Inquiry Complete Event
> * 0x0002 Inquiry Result Event
> * 0x0004 Connection Complete Event
> * 0x0008 Connection Request Event
> * 0x0010 Disconnection Complete Event
> * 0x0020 Authentication Complete Event
> * 0x0040 Remote Name Request Complete Event
> * 0x0080 Encryption Change Event
> * 0x0100 Change Connection Link Key Complete Event
> * 0x0200 Master Link Key Complete Event
> * 0x0400 Read Remote Supported Features Complete Event
> * 0x0800 Read Remote Version Information Complete Event
> * 0x1000 QoS Setup Complete Event
> * 0x2000 Reserved
> * 0x4000 Reserved
> * 0x8000 Hardware Error Event
> * 0x0001 Flush Occurred Event
> * 0x0002 Role Change Event
> * 0x0004 Reserved
> * 0x0008 Mode Change Event
> * 0x0010 Return Link Keys Event
> * 0x0020 PIN Code Request Event
> *
[jira] [Commented] (MYNEWT-773) Implement oic_serial in "new" newtmgr
[ https://issues.apache.org/jira/browse/MYNEWT-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039626#comment-16039626 ] ASF subversion and git services commented on MYNEWT-773: Commit 39b246447b08393bd35eed16492ee08d3b48ead7 in incubator-mynewt-newtmgr's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=39b2464 ] MYNEWT-773 Implement oic_serial in "new" newtmgr > Implement oic_serial in "new" newtmgr > - > > Key: MYNEWT-773 > URL: https://issues.apache.org/jira/browse/MYNEWT-773 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newtmgr >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The old newtmgr > (https://github.com/apache/incubator-mynewt-newt/tree/master/newtmgr) > supports OMP (newtmgr over CoAP) over serial. > The new newtmgr > (https://github.com/apache/incubator-mynewt-newtmgr/tree/master/newtmgr) > lacks this feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039397#comment-16039397 ] ASF subversion and git services commented on MYNEWT-543: Commit b37d8bf275159d2c959cc55d8179328f40d28dec in incubator-mynewt-newt's branch refs/heads/master from [~cwanda] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=b37d8bf ] MYNEWT-640 Added newt target amend command. The newt target amend command allows the user to add, change, delete values for multi-value target variables without overwriting existing values. This addresses the concern raised in MYNEWT-543. The amend command uses the same format as newt target set. The variables that can have values appended are: syscfg, cflags, aflags, and lfags. It supports a -d flag to delete values. > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=16039396#comment-16039396
]
ASF subversion and git services commented on MYNEWT-640:
Commit b37d8bf275159d2c959cc55d8179328f40d28dec in incubator-mynewt-newt's
branch refs/heads/master from [~cwanda]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=b37d8bf ]
MYNEWT-640 Added newt target amend command.
The newt target amend command allows the user to add, change, delete values
for multi-value target variables without overwriting existing values. This
addresses the concern raised in MYNEWT-543.
The amend command uses the same format as newt target set. The variables that
can have values appended are: syscfg, cflags, aflags, and lfags. It supports a
-d flag to delete values.
> 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] [Commented] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
[ https://issues.apache.org/jira/browse/MYNEWT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039368#comment-16039368 ] ASF subversion and git services commented on MYNEWT-694: Commit 9634cbe1e9012fc620d8f2e8f3a076ec493c536e in incubator-mynewt-newt's branch refs/heads/master from [~cwanda] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=9634cbe ] MYNEWT-694 newt run cmd prompts user for version If the target is not a bootloader and the user did not provide a version number, prompt the user to enter a version or use the default value 0. > newt run command should query user for version number instead of skipping > create image step > --- > > Key: MYNEWT-694 > URL: https://issues.apache.org/jira/browse/MYNEWT-694 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > The *newt run* command currently skips the create image step if the user does > not provide a version number for the command. It would be useful to have the > command query the user for a version number and to let the user know that the > command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash
[ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030368#comment-16030368 ] ASF subversion and git services commented on MYNEWT-583: Commit e66a00721fb4df0a348fe4b462095f0a95cc1950 in incubator-mynewt-newt's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=e66a007 ] This closes #55. Merge remote-tracking branch 'mkiiskila/mynewt_583_2' * mkiiskila/mynewt_583_2: MYNEWT-583; repo.go - call vers.String() explicitly when printing version number. MYNEWT-583; newt - allow use of specific tag/repository revision. > Allow project.yml to specify a commit hash > -- > > Key: MYNEWT-583 > URL: https://issues.apache.org/jira/browse/MYNEWT-583 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > Would be great if one could lock down a specific mynewt-core commit hash in > project.yml, in addition to tags. Currently, one tags are supported, but when > using develop/latest it is more useful to test against a fixed known state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash
[ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030367#comment-16030367 ] ASF subversion and git services commented on MYNEWT-583: Commit f43066ccd50620d23b752b4f2887427d1c8ce3da in incubator-mynewt-newt's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=f43066c ] MYNEWT-583; repo.go - call vers.String() explicitly when printing version number. > Allow project.yml to specify a commit hash > -- > > Key: MYNEWT-583 > URL: https://issues.apache.org/jira/browse/MYNEWT-583 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > Would be great if one could lock down a specific mynewt-core commit hash in > project.yml, in addition to tags. Currently, one tags are supported, but when > using develop/latest it is more useful to test against a fixed known state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash
[ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030366#comment-16030366 ] ASF subversion and git services commented on MYNEWT-583: Commit d33755a5bd8dacdd7f79dc32f45420d8a7960a68 in incubator-mynewt-newt's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=d33755a ] MYNEWT-583; newt - allow use of specific tag/repository revision. > Allow project.yml to specify a commit hash > -- > > Key: MYNEWT-583 > URL: https://issues.apache.org/jira/browse/MYNEWT-583 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > Would be great if one could lock down a specific mynewt-core commit hash in > project.yml, in addition to tags. Currently, one tags are supported, but when > using develop/latest it is more useful to test against a fixed known state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash
[ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030369#comment-16030369 ] ASF subversion and git services commented on MYNEWT-583: Commit e66a00721fb4df0a348fe4b462095f0a95cc1950 in incubator-mynewt-newt's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=e66a007 ] This closes #55. Merge remote-tracking branch 'mkiiskila/mynewt_583_2' * mkiiskila/mynewt_583_2: MYNEWT-583; repo.go - call vers.String() explicitly when printing version number. MYNEWT-583; newt - allow use of specific tag/repository revision. > Allow project.yml to specify a commit hash > -- > > Key: MYNEWT-583 > URL: https://issues.apache.org/jira/browse/MYNEWT-583 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > Would be great if one could lock down a specific mynewt-core commit hash in > project.yml, in addition to tags. Currently, one tags are supported, but when > using develop/latest it is more useful to test against a fixed known state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-759) Change BLE-over-CoAP UUID from 128-bit to 16-bit
[ https://issues.apache.org/jira/browse/MYNEWT-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021746#comment-16021746 ] ASF subversion and git services commented on MYNEWT-759: Commit 3531ce6d6282ebc6587d9641f651f54f7420f1e4 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3531ce6 ] MYNEWT-759 Change BLE-over-CoAP UUID 128 --> 16 The plan is to reserve a 16-bit UUID with the Bluetooth SIG. In the meantime, we will use the (arbitrarilly chosen) UUID 0x9923. > Change BLE-over-CoAP UUID from 128-bit to 16-bit > > > Key: MYNEWT-759 > URL: https://issues.apache.org/jira/browse/MYNEWT-759 > Project: Mynewt > Issue Type: Improvement >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The plan is to reserve a 16-bit UUID with the Bluetooth SIG. In the > meantime, we will use the (arbitrarilly chosen) UUID 0x9923. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-707) Add API to retrieve public and static random addresses from chip specific locations
[ https://issues.apache.org/jira/browse/MYNEWT-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018617#comment-16018617 ] ASF subversion and git services commented on MYNEWT-707: Commit ee0f350e01b5239521f1d1338f062b8c62f3c9e0 in incubator-mynewt-core's branch refs/heads/bsnbranch from [~wes3] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=ee0f350 ] MYNEWT-707: Add API to retrieve public and random static address Please read the Jira ticket for more information on how to use these API. The controller now calls ble_hw_get_public_addr() and will use that address for its public address. The global device address has not been hidden yet since some apps rely on the ability to modify it. > Add API to retrieve public and static random addresses from chip specific > locations > --- > > Key: MYNEWT-707 > URL: https://issues.apache.org/jira/browse/MYNEWT-707 > Project: Mynewt > Issue Type: New Feature > Components: Nimble >Affects Versions: v1_0_0_rel >Reporter: William San Filippo >Assignee: William San Filippo > Fix For: v1_1_0_rel > > > This ticket will add API to retrieve a public address and random static > address from "chip specific" locations. Here are the API and how they will > work for the nordic chips, which are currently the only supported BLE chips. > This ticket does not address storing/retrieving these values from flash or > configuration areas. > 1) The ble_hw_get_public_addr function will do the following: > * If the user has overridden the default public address (the syscfg variable) > with a non-zero public address, that address will be returned by this > function. > * If the default public address in the syscfg is all zero, the code will read > FICR and check if the device address type in the FICR is public. If so, it > means the nordic chip was factory programmed with a public address and this > will be used. > * If both of the above checks fail, the code will read UICR[0] and UICR[1] to > see if a public address has been programmed into the UICR. We are doing this > to make it easy for folks to program their development kits with public > addresses so they do not have to hardcode them. UICR[0] will contain the > least significant 4 bytes of the device address. UICR[1] will contain the > most significant two bytes. The upper 16 bits of this word should be set to > 0. The API will presume that this is a valid public device address as long as > the upper 16-bits of this 32-bit word are all zero. We will also check to see > if this is a valid public address (see below). If both UICR[0] and UICR[1] > are zero, this will not be considered a valid public address. > 2) The ble_hw_get_static_addr() will do the following: > * Read the FICR to see if there is a random address in the FICR. This is the > default programming of the nrf51dk and nrf52dk. Unless you have them program > a public device address in the FICR, it will have a random address. > * If the chip does not have a random address the API returns -1. > * If the chip has a random address the upper two bits will be set to 1 (which > denotes random static address). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016694#comment-16016694 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016698#comment-16016698 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016692#comment-16016692 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016691#comment-16016691 ] ASF subversion and git services commented on MYNEWT-754: Commit c24413e1106042015a693713305f046845169a2e in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c24413e ] MYNEWT-754 BLE Host - Support deleting of CCCDs. > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016685#comment-16016685 ] ASF subversion and git services commented on MYNEWT-754: Commit 02f60846684b0f51dbfe050795b144e0f8b35641 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=02f6084 ] MYNEWT-754 BLE host - addrcmp ignores padding. A straight memcmp of the ble_addr_t struct won't always work, particularly if one of the structs is allocated on the stack. The contents of the padding bytes are indeterminate, and could cause a false negative. > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016688#comment-16016688 ] ASF subversion and git services commented on MYNEWT-754: Commit 507773fdcd1aff62db51fe1f8afdf7b0014e4099 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=507773f ] MYNEWT-754 BLE Host - Add some missing consts. > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016699#comment-16016699 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016690#comment-16016690 ] ASF subversion and git services commented on MYNEWT-754: Commit fd6da967a98574e0593508217b1eca8c26f97ac5 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=fd6da96 ] MYNEWT-754 BLE Host - Basic store util unit tests. > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016687#comment-16016687 ] ASF subversion and git services commented on MYNEWT-754: Commit 7ad98820d8c7692e3c39d66c7b736ca7df3c1cb0 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=7ad9882 ] MYNEWT-754 BLE Host - Store mgmt API additions /** * Deletes all entries from the store that match the specified key. * * @param type The type of store entry to delete. * @param key Entries matching this key get deleted. * * @return 0 on success; * Other nonzero on error. */ int ble_store_util_delete_all(int type, const union ble_store_key *key) /** * Retrieves the set of peer addresses for which a bond has been * established. * * @param out_peer_id_addrs On success, the set of bonded peer * addresses gets written here. * @param out_num_peers On success, the number of bonds gets * written here. * @param max_peers The capacity of the destination buffer. * * @return 0 on success; * BLE_HS_ENOMEM if the destination buffer * is too small; * Other nonzero on error. */ int ble_store_util_bonded_peers(ble_addr_t *out_peer_id_addrs, int *out_num_peers, int max_peers) /** * Deletes all entries from the store that are attached to the specified * peer address. This function deletes security entries and CCCD * records. * * @param peer_id_addr Entries with this peer address get * deleted. * * @return 0 on success; * Other nonzero on error. */ int ble_store_util_delete_peer(const ble_addr_t *peer_id_addr) > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016686#comment-16016686 ] ASF subversion and git services commented on MYNEWT-754: Commit c542807fb3af50962d55bb669ae7f149cb208150 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c542807 ] MYNEWT-754 BLE Host - iterate: return err on fail > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016696#comment-16016696 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016693#comment-16016693 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016684#comment-16016684 ] ASF subversion and git services commented on MYNEWT-754: Commit f0a1ea83726a488734c7ad957ef7c2ac956a42b4 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f0a1ea8 ] MYNEWT-754 BLE host - Store cb can abort iterate. > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016695#comment-16016695 ] ASF subversion and git services commented on MYNEWT-754: Commit c7d7a0ebf294af93ff298f244863645be3d01c12 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c7d7a0e ] This closes #277. Merge branch 'key-overflow' * key-overflow: MYNEWT-754 BLE Host - Support deleting of CCCDs. MYNEWT-754 BLE Host - Basic store util unit tests. MYNEWT-754 BLE Host - Add some missing consts. MYNEWT-754 BLE Host - Store mgmt API additions MYNEWT-754 BLE Host - iterate: return err on fail MYNEWT-754 BLE host - addrcmp ignores padding. MYNEWT-754 BLE host - Store cb can abort iterate. MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-754) BLE Host - Store management API additions
[ https://issues.apache.org/jira/browse/MYNEWT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016683#comment-16016683 ] ASF subversion and git services commented on MYNEWT-754: Commit c2654f308cb21b41653583b951fcdcd85bb17f4e in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c2654f3 ] MYNEWT-754 BLE Host - cfgable RAM store capacity > BLE Host - Store management API additions > - > > Key: MYNEWT-754 > URL: https://issues.apache.org/jira/browse/MYNEWT-754 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The store API supports all the necessary operations: read, write, and delete. > However, some convenience functions are sorely lacking: > * Retrieve list of bonded peers > * Delete bond -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash
[ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016613#comment-16016613 ] ASF subversion and git services commented on MYNEWT-583: Commit 26b618f3df44c01a721ec59df3120f1ed758e06e in incubator-mynewt-newt's branch refs/heads/master from [~marko] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=26b618f ] MYNEWT-583; newt - allow use of specific tag/repository revision. > Allow project.yml to specify a commit hash > -- > > Key: MYNEWT-583 > URL: https://issues.apache.org/jira/browse/MYNEWT-583 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Simon Ratner >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > Would be great if one could lock down a specific mynewt-core commit hash in > project.yml, in addition to tags. Currently, one tags are supported, but when > using develop/latest it is more useful to test against a fixed known state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-748) SensorAPI: Add BME280 support to mynewt along with pressure, temperature and humidity support
[ https://issues.apache.org/jira/browse/MYNEWT-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013813#comment-16013813 ] ASF subversion and git services commented on MYNEWT-748: Commit f2a8e66af0947699269814ff13fa562fc27323d5 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f2a8e66 ] MYNEWT-748 SensorAPI: Add BME280 support - Make OIC observe rate configurable - Use the OIC observe rate as the LED blink rate in the app > SensorAPI: Add BME280 support to mynewt along with pressure, temperature and > humidity support > - > > Key: MYNEWT-748 > URL: https://issues.apache.org/jira/browse/MYNEWT-748 > Project: Mynewt > Issue Type: New Feature >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Add SPI driver for BME280 along with pressure, temperature and humidity > support in SensorAPI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-748) SensorAPI: Add BME280 support to mynewt along with pressure, temperature and humidity support
[ https://issues.apache.org/jira/browse/MYNEWT-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013812#comment-16013812 ] ASF subversion and git services commented on MYNEWT-748: Commit 1dc1635810bd5b0eea1c3faed1675d9139e2a32d in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1dc1635 ] MYNEWT-748 SensorAPI: Add BME280 support SensorAPI support for pressure, temperature and humidity - Add temperature, pressure, humidity support - change temperature handling for bno055 - fix bugs with register values > SensorAPI: Add BME280 support to mynewt along with pressure, temperature and > humidity support > - > > Key: MYNEWT-748 > URL: https://issues.apache.org/jira/browse/MYNEWT-748 > Project: Mynewt > Issue Type: New Feature >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Add SPI driver for BME280 along with pressure, temperature and humidity > support in SensorAPI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
