[jira] [Commented] (MYNEWT-664) coredownload newtmgr command should indicate core size in first response

[ASF subversion and git services (JIRA)]

[ 
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] [Updated] (MYNEWT-756) mpstats (on nrf51) hangs indefinately

[Jacob (JIRA)]

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

Jacob updated MYNEWT-756:
-

switched to nrf51dk pca10031 which i guess in an nrf51422 qfac using
nrf51dk bsp

core Commit a6c5103e6b709423cf9380e9d2e57004bafb2ca9

i can strip sysfg all the way down to here and it always just hangs

Jacobs-MacBook-Air:chippd3 jacobrosenthal$ newt target show bleprph-nrf51dk
targets/bleprph-nrf51dk
app=@apache-mynewt-core/apps/bleprph
bsp=@apache-mynewt-core/hw/bsp/nrf51dk
build_profile=optimized
syscfg=BLE_LL_CFG_FEAT_LE_ENCRYPTION=0:BLE_SM_LEGACY=0:BLE_SM_SC=0
Jacobs-MacBook-Air:chippd3 jacobrosenthal$


and it just hangs like ive seen on nrf51dk-16kbram bsps

if i turn logs back on

Jacobs-MacBook-Air:chippd3 jacobrosenthal$ newt target show bleprph-nrf51dk
targets/bleprph-nrf51dk
app=@apache-mynewt-core/apps/bleprph
bsp=@apache-mynewt-core/hw/bsp/nrf51dk
build_profile=optimized

syscfg=BLE_LL_CFG_FEAT_LE_ENCRYPTION=0:BLE_SM_LEGACY=0:BLE_SM_SC=0:CONSOLE_COMPAT=1:CONSOLE_ECHO=0:CONSOLE_INPUT=0:CONSOLE_MAX_INPUT_LEN=0:CONSOLE_RTT=1:CONSOLE_UART=0:LOG_LEVEL=0
Jacobs-MacBook-Air:chippd3 jacobrosenthal$



Jacobs-MacBook-Air:node-newtmgr jacobrosenthal$ GODEBUG=cgocheck=0 newtmgr
mpstats -cnimble_bleprph -ldebug -t
2017/06/06 21:01:19 [DEBUG] BLE Connection devaddr:[]
2017/06/06 21:01:19 [DEBUG] State:PoweredOn
2017/06/06 21:01:19 [DEBUG] scanning...
2017/06/06 21:01:19 [DEBUG] Peripheral Discovered: , Address:[0 0 0 0 0 0]
Address Type:0
2017/06/06 21:01:19 [DEBUG] Peripheral Discovered: , Address:[0 0 0 0 0 0]
Address Type:0
2017/06/06 21:01:20 Unhandled event: xpc.Dict{"kCBMsgId":53,
"kCBMsgArgs":xpc.Dict{"kCBMsgArgDeviceUUID":xpc.UUID{0x2f, 0xd, 0xcb, 0x60,
0xf, 0x3e, 0x47, 0x52, 0xb7, 0x74, 0x13, 0x29, 0x3a, 0x3, 0xd4, 0xd0},
"kCBMsgArgATTMTU":104}}
2017/06/06 21:01:20 [DEBUG] Peripheral Connected
2017/06/06 21:01:20 [DEBUG] Newtmgr Service Found
2017/06/06 21:01:20 [DEBUG] Newtmgr Characteristic Found
2017/06/06 21:01:20 [DEBUG] Writing newtmgr request &{Op:0 Flags:0 Len:0
Group:0 Seq:0 Id:3 Data:[]}
2017/06/06 21:01:20 [DEBUG] Serializing request &{Op:0 Flags:0 Len:0
Group:0 Seq:0 Id:3 Data:[]} into buffer [0 0 0 0 0 0 0 3]
2017/06/06 21:01:20 [DEBUG] Tx packet dump:
  00 00 00 00 00 00 00 03   ||

2017/06/06 21:01:20 [DEBUG] Write BLE Packet:buf:: len::8
2017/06/06 21:01:20 [DEBUG] Read BLE
Packet:buf::l?brcfmpools?fmsys_1?fblksiz$enblks

enfree cmi?wble_hci_ram_evt_hi_pool?fblksizHenblkse len::101
2017/06/06 21:01:20 [DEBUG] Rx packet dump:
  01 00 02 6c 00 00 00 03  bf 62 72 63 00 66 6d 70
 |...l.brc.fmp|
0010  6f 6f 6c 73 bf 66 6d 73  79 73 5f 31 bf 66 62 6c
 |ools.fmsys_1.fbl|
0020  6b 73 69 7a 19 01 24 65  6e 62 6c 6b 73 0c 65 6e
 |ksiz..$enblks.en|
0030  66 72 65 65 09 63 6d 69  6e 08 ff 77 62 6c 65 5f
 |free.cmin..wble_|
0040  68 63 69 5f 72 61 6d 5f  65 76 74 5f 68 69 5f 70
 |hci_ram_evt_hi_p|
0050  6f 6f 6c bf 66 62 6c 6b  73 69 7a 18 48 65 6e 62
 |ool.fblksiz.Henb|
0060  6c 6b 73 02 65|lks.e|

2017/06/06 21:01:20 [DEBUG] Deserialized response &{Op:1 Flags:0 Len:620
Group:0 Seq:0 Id:3 Data:[191 98 114 99 0 102 109 112 111 111 108 115 191
102 109 115 121 115 95 49 191 102 98 108 107 115 105 122 25 1 36 101 110 98
108 107 115 12 101 110 102 114 101 101 9 99 109 105 110 8 255 119 98 108
101 95 104 99 105 95 114 97 109 95 101 118 116 95 104 105 95 112 111 111
108 191 102 98 108 107 115 105 122 24 72 101 110 98 108 107 115 2 101]}
2017/06/06 21:01:20 [DEBUG] Read BLE
Packet:buf::nfreecmin?wble_hci_ram_evt_lo_pool?fblksizHenblkenfrecmi?rble_hs_hci_ev_pool?fblksizenblks
 len::101
2017/06/06 21:01:20 [DEBUG] Rx packet dump:
  6e 66 72 65 65 02 63 6d  69 6e 00 ff 77 62 6c 65
 |nfree.cmin..wble|
0010  5f 68 63 69 5f 72 61 6d  5f 65 76 74 5f 6c 6f 5f
 |_hci_ram_evt_lo_|
0020  70 6f 6f 6c bf 66 62 6c  6b 73 69 7a 18 48 65 6e
 |pool.fblksiz.Hen|
0030  62 6c 6b 73 08 65 6e 66  72 65 65 08 63 6d 69 6e
 |blks.enfree.cmin|
0040  08 ff 72 62 6c 65 5f 68  73 5f 68 63 69 5f 65 76
 |..rble_hs_hci_ev|
0050  5f 70 6f 6f 6c bf 66 62  6c 6b 73 69 7a 10 65 6e
 |_pool.fblksiz.en|
0060  62 6c 6b 73 0a|blks.|

2017/06/06 21:01:20 [DEBUG] Read BLE Packet:buf::enfree
cmin 
?pble_hs_conn_pool?fblksizTenblksenfreecmin?sble_l2cap_chan_pool?fblksizenblksenfr
len::101
2017/06/06 21:01:20 [DEBUG] Rx packet dump:
  65 6e 66 72 65 65 0a 63  6d 69 6e 09 ff 70 62 6c
 |enfree.cmin..pbl|
0010  65 5f 68 73 5f 63 6f 6e  6e 5f 70 6f 6f 6c bf 66
 |e_hs_conn_pool.f|
0020  62 6c 6b 73 69 7a 18 54  65 6e 62 6c 6b 73 01 65
 |blksiz.Tenblks.e|
0030  6e 66 72 65 65 00 63 6d  69 6e 00 ff 73 62 6c 65
 |nfree.cmin..sble|
0040  5f 6c 32 63 61 70 5f 63  68 61 6e 5f 70 6f 6f 6c
 |_l2cap_chan_pool|
0050  bf 66 62 6c 6b 73 69 7a 

[jira] [Updated] (MYNEWT-756) mpstats (on nrf51) hangs indefinately

[Jacob (JIRA)]

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

Jacob updated MYNEWT-756:
-

Maybe my device is weird. Ive got 2 new shipping now.

On Tue, Jun 6, 2017 at 3:24 PM, Christopher Collins (JIRA) 



> mpstats (on nrf51) hangs indefinately
> -
>
> Key: MYNEWT-756
> URL: https://issues.apache.org/jira/browse/MYNEWT-756
> Project: Mynewt
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: Newt
>Reporter: Jacob
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> I believe core is failing before sending the last packet, as neither newtmgr 
> or node-newtmgr receives that packet.
> Jacobs-MacBook-Air:newtmgr jacobrosenthal$ GODEBUG=cgocheck=0 newtmgr mpstats 
> -cnimble_bleprph -t -ldebug
> 2017/05/11 22:28:46 [DEBUG] BLE Connection devaddr:[]
> 2017/05/11 22:28:46 [DEBUG] State:PoweredOn
> 2017/05/11 22:28:46 [DEBUG] scanning...
> 2017/05/11 22:28:46 [DEBUG] Peripheral Discovered: , Address:[0 0 0 0 0 0] 
> Address Type:0
> 2017/05/11 22:28:47 Unhandled event: xpc.Dict{"kCBMsgId":53, 
> "kCBMsgArgs":xpc.Dict{"kCBMsgArgDeviceUUID":xpc.UUID{0x2f, 0xd, 0xcb, 0x60, 
> 0xf, 0x3e, 0x47, 0x52, 0xb7, 0x74, 0x13, 0x29, 0x3a, 0x3, 0xd4, 0xd0}, 
> "kCBMsgArgATTMTU":104}}
> 2017/05/11 22:28:47 [DEBUG] Peripheral Connected
> 2017/05/11 22:28:47 [DEBUG] Newtmgr Service Found 
> 2017/05/11 22:28:47 [DEBUG] Newtmgr Characteristic Found
> 2017/05/11 22:28:47 [DEBUG] Writing newtmgr request &{Op:0 Flags:0 Len:0 
> Group:0 Seq:0 Id:3 Data:[]}
> 2017/05/11 22:28:47 [DEBUG] Serializing request &{Op:0 Flags:0 Len:0 Group:0 
> Seq:0 Id:3 Data:[]} into buffer [0 0 0 0 0 0 0 3]
> 2017/05/11 22:28:47 [DEBUG] Tx packet dump:
>   00 00 00 00 00 00 00 03   ||
> 2017/05/11 22:28:47 [DEBUG] Write BLE Packet:buf:: len::8
> 2017/05/11 22:28:47 [DEBUG] Read BLE 
> Packet:buf::l?brcfmpools?fmsys_1?fblksiz$enblks
>   
>   enfreecmin?wble_hci_ram_evt_hi_pool?fblksizHenblkse len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   01 00 02 6c 00 00 00 03  bf 62 72 63 00 66 6d 70  |...l.brc.fmp|
> 0010  6f 6f 6c 73 bf 66 6d 73  79 73 5f 31 bf 66 62 6c  |ools.fmsys_1.fbl|
> 0020  6b 73 69 7a 19 01 24 65  6e 62 6c 6b 73 0c 65 6e  |ksiz..$enblks.en|
> 0030  66 72 65 65 09 63 6d 69  6e 00 ff 77 62 6c 65 5f  |free.cmin..wble_|
> 0040  68 63 69 5f 72 61 6d 5f  65 76 74 5f 68 69 5f 70  |hci_ram_evt_hi_p|
> 0050  6f 6f 6c bf 66 62 6c 6b  73 69 7a 18 48 65 6e 62  |ool.fblksiz.Henb|
> 0060  6c 6b 73 02 65|lks.e|
> 2017/05/11 22:28:47 [DEBUG] Deserialized response &{Op:1 Flags:0 Len:620 
> Group:0 Seq:0 Id:3 Data:[191 98 114 99 0 102 109 112 111 111 108 115 191 102 
> 109 115 121 115 95 49 191 102 98 108 107 115 105 122 25 1 36 101 110 98 108 
> 107 115 12 101 110 102 114 101 101 9 99 109 105 110 0 255 119 98 108 101 95 
> 104 99 105 95 114 97 109 95 101 118 116 95 104 105 95 112 111 111 108 191 102 
> 98 108 107 115 105 122 24 72 101 110 98 108 107 115 2 101]}
> 2017/05/11 22:28:47 [DEBUG] Read BLE 
> Packet:buf::nfreecmin?wble_hci_ram_evt_lo_pool?fblksizHenblkenfrecmi?rble_hs_hci_ev_pool?fblksizenblks
>  len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   6e 66 72 65 65 02 63 6d  69 6e 00 ff 77 62 6c 65  |nfree.cmin..wble|
> 0010  5f 68 63 69 5f 72 61 6d  5f 65 76 74 5f 6c 6f 5f  |_hci_ram_evt_lo_|
> 0020  70 6f 6f 6c bf 66 62 6c  6b 73 69 7a 18 48 65 6e  |pool.fblksiz.Hen|
> 0030  62 6c 6b 73 08 65 6e 66  72 65 65 08 63 6d 69 6e  |blks.enfree.cmin|
> 0040  08 ff 72 62 6c 65 5f 68  73 5f 68 63 69 5f 65 76  |..rble_hs_hci_ev|
> 0050  5f 70 6f 6f 6c bf 66 62  6c 6b 73 69 7a 10 65 6e  |_pool.fblksiz.en|
> 0060  62 6c 6b 73 0a|blks.|
> 2017/05/11 22:28:47 [DEBUG] Read BLE Packet:buf::enfree
> cmin  
> ?pble_hs_conn_pool?fblksizTenblksenfreecmin?sble_l2cap_chan_pool?fblksizenblksenfr
>  len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   65 6e 66 72 65 65 0a 63  6d 69 6e 09 ff 70 62 6c  |enfree.cmin..pbl|
> 0010  65 5f 68 73 5f 63 6f 6e  6e 5f 70 6f 6f 6c bf 66  |e_hs_conn_pool.f|
> 0020  62 6c 6b 73 69 7a 18 54  65 6e 62 6c 6b 73 01 65  |blksiz.Tenblks.e|
> 0030  6e 66 72 65 65 00 63 6d  69 6e 00 ff 73 62 6c 65  |nfree.cmin..sble|
> 0040  5f 6c 32 63 61 70 5f 63  68 61 6e 5f 70 6f 6f 6c  |_l2cap_chan_pool|
> 0050  bf 66 62 6c 6b 73 69 7a  18 1c 65 6e 62 6c 6b 73  |.fblksiz..enblks|
> 0060  03 65 6e 66 72|.enfr|
> 2017/05/11 22:28:47 [DEBUG] Read BLE 
> 

[jira] [Resolved] (MYNEWT-661) BLE Host - SC:yes, lgcy:no - device never responds to pairing rsp.

[Christopher Collins (JIRA)]

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

Christopher Collins resolved MYNEWT-661.

Resolution: Fixed

Thanks, Łukasz.  It looks good.

{noformat}
007743 compat> b sec start conn=1
008183 module: 0, command: b
008184 [ts=63937440ssb, mod=4 level=0] looking up peer sec; peer_addr_type=0 
peer_addr=0x34 0x22 0x00 0x99 0x99 0x99
008187 [ts=63960876ssb, mod=4 level=0] host tx hci data; handle=1 length=11
008189 [ts=63976500ssb, mod=4 level=0] ble_hs_hci_acl_tx(): 0x01 0x00 0x0b 0x00 
0x07 0x00 0x06 0x00 0x01 0x03 0x00 0x09 0x10 0x07 0x07
008193 [ts=64007812ssb, mod=4 level=0] ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0018 
len=0
008195 [ts=64023436ssb, mod=4 level=0] 0x18 0x20 0x00
008196 [ts=64031248ssb, mod=4 level=0] Command complete: cmd_pkts=1 ogf=0x8 
ocf=0x18 status=0 rand=0xc213c8492ede7859
008199 [ts=64054684ssb, mod=4 level=0] ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0018 
len=0
008202 [ts=64078120ssb, mod=4 level=0] 0x18 0x20 0x00
008203 [ts=64085932ssb, mod=4 level=0] Command complete: cmd_pkts=1 ogf=0x8 
ocf=0x18 status=0 rand=0x07be2ac5aa1e6e57
008206 compat> Number of Completed Packets: num_handles=1
008210 [ts=64140616ssb, mod=4 level=0] handle:1 pkts:1
008215 [ts=64179676ssb, mod=4 level=0] ble_hs_hci_evt_acl_process(): 
conn_handle=1 pb=2 len=11 data=0x07 0x00 0x06 0x00 0x02 0x03 0x00 0x01 0x10 
0x07 0x07
008219 [ts=64210924ssb, mod=4 level=0] rxed sm command: pair rsp; conn=1 
io_cap=3 oob_data_flag=0 authreq=0x01 mac_enc_key_size=16 init_key_dist=7 
resp_key_dist=7
008223 [ts=64242172ssb, mod=4 level=0] host tx hci data; handle=1 length=6
008225 [ts=64257796ssb, mod=4 level=0] ble_hs_hci_acl_tx(): 0x01 0x00 0x06 0x00 
0x02 0x00 0x06 0x00 0x05 0x03
008228 encryption change event; status=1027 handle=1 our_ota_addr_type=0 
our_ota_addr=0a:45:00:11:22:33 our_id_addr_type=0 our_id_addr=0a:45:00:11:22:33 
peer_ota_addr_type=0 peer_ota_addr=99:99:99:00:22:34 peer_id_addr_type=0 
peer_id_addr=99:99:99:00:22:34 conn_itvl=40 conn_latency=0 
supervision_timeout=256 encrypted=0 authenticated=0 bonded=0
008241 [ts=64382788ssb, mod=4 level=0] Number of Completed Packets: 
num_handles=1
008243 [ts=64398412ssb, mod=4 level=0] handle:1 pkts:1
{noformat}

(we get an authreq error now.)

> BLE Host - SC:yes, lgcy:no - device never responds to pairing rsp.
> --
>
> Key: MYNEWT-661
> URL: https://issues.apache.org/jira/browse/MYNEWT-661
> 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
>
>
> Configure device A with the following settings:
> {noformat}
> BLE_SM_LEGACY: 0
> BLE_SM_SC: 1
> {noformat}
> Configure device B with the opposite settings:
> {noformat}
> BLE_SM_LEGACY: 1
> BLE_SM_SC: 0
> {noformat}
> # Connect the two devices.
> # Device A initiates pairing.
> The result is: device A never responds to B's paring response.  Instead, it 
> does nothing and allows the pairing procedure to time out.



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

[jira] [Commented] (MYNEWT-752) Error in setting the "permanent" flag upon confirm with hash during image upgrade

[Christopher Collins (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039890#comment-16039890
 ] 

Christopher Collins commented on MYNEWT-752:


(Pull request: https://github.com/apache/incubator-mynewt-core/pull/313)

h3. Before fix:
{noformat}
[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image test 
5ff2addc0fb7bde71fd03dd161834e61ded2041652c37196f180b12091c2ff55
Images:
 slot=0
version: 0.0.0
bootable: true
flags: active confirmed
hash: bd42be9757549d4209ce873ab68f7cd290a9c494398d39af6b5702ec66aafb7d
 slot=1
version: 2.2.2.2
bootable: true
flags: pending
hash: 5ff2addc0fb7bde71fd03dd161834e61ded2041652c37196f180b12091c2ff55
Split status: N/A (0)
{noformat}

(reset device)

{noformat}
[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image list
Images:
 slot=0
version: 2.2.2.2
bootable: true
flags: active
hash: 5ff2addc0fb7bde71fd03dd161834e61ded2041652c37196f180b12091c2ff55
 slot=1
version: 0.0.0
bootable: true
flags: confirmed
hash: bd42be9757549d4209ce873ab68f7cd290a9c494398d39af6b5702ec66aafb7d
Split status: N/A (0)

[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image confirm 
5ff2addc0fb7bde71fd03dd161834e61ded2041652c37196f180b12091c2ff55
Images:
 slot=0
version: 2.2.2.2
bootable: true
flags: active confirmed
hash: 5ff2addc0fb7bde71fd03dd161834e61ded2041652c37196f180b12091c2ff55
 slot=1
version: 0.0.0
bootable: true
flags: pending permanent
hash: bd42be9757549d4209ce873ab68f7cd290a9c494398d39af6b5702ec66aafb7d
Split status: N/A (0)
{noformat}

h3. After fix:
{noformat}
[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image test 
817b16111d40151345566e73a2a2f999fd2efd65d43a1a98cdccd991ee0be775
Images:
 slot=0
version: 0.0.0
bootable: true
flags: active confirmed
hash: 1c71f96bcff94e6f2307f9b28bd0249fa73f0bb0819a99ee5bacc4db4e2179e3
 slot=1
version: 2.2.2.2
bootable: true
flags: pending
hash: 817b16111d40151345566e73a2a2f999fd2efd65d43a1a98cdccd991ee0be775
Split status: N/A (0)
{noformat}

(reset device)

{noformat}
[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image list
Images:
 slot=0
version: 2.2.2.2
bootable: true
flags: active
hash: 817b16111d40151345566e73a2a2f999fd2efd65d43a1a98cdccd991ee0be775
 slot=1
version: 0.0.0
bootable: true
flags: confirmed
hash: 1c71f96bcff94e6f2307f9b28bd0249fa73f0bb0819a99ee5bacc4db4e2179e3
Split status: N/A (0)

[ccollins@ccollins-mac:~/repos/mynewt/core]$ newtmgr -c ble-nimble-bleprph 
--name nimble-bleprph image confirm 
817b16111d40151345566e73a2a2f999fd2efd65d43a1a98cdccd991ee0be775
Images:
 slot=0
version: 2.2.2.2
bootable: true
flags: active confirmed
hash: 817b16111d40151345566e73a2a2f999fd2efd65d43a1a98cdccd991ee0be775
 slot=1
version: 0.0.0
bootable: true
flags:
hash: 1c71f96bcff94e6f2307f9b28bd0249fa73f0bb0819a99ee5bacc4db4e2179e3
Split status: N/A (0)
{noformat}

> 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.3.15#6346)

[jira] [Commented] (MYNEWT-664) coredownload newtmgr command should indicate core size in first response

[ASF subversion and git services (JIRA)]

[ 
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

[ASF subversion and git services (JIRA)]

[ 
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] [Resolved] (MYNEWT-772) BLE Host - Initial set-event-mask specifies reserved bits

[Christopher Collins (JIRA)]

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

Christopher Collins resolved MYNEWT-772.

Resolution: Fixed

> 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
>  * 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
>  */
> {noformat}
> It does this by setting the following bit mask: {{0x20009fff}}.  This 
> mask is incorrect; it should be: {{0x20009807}}.



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

[jira] [Commented] (MYNEWT-772) BLE Host - Initial set-event-mask specifies reserved bits

[ASF subversion and git services (JIRA)]

[ 
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] [Updated] (MYNEWT-664) coredownload newtmgr command should indicate core size in first response

[Christopher Collins (JIRA)]

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

Christopher Collins updated MYNEWT-664:
---
Description: 
(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.

  was:
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.


> 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] [Resolved] (MYNEWT-773) Implement oic_serial in "new" newtmgr

[Christopher Collins (JIRA)]

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

Christopher Collins resolved MYNEWT-773.

Resolution: Fixed

> 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-773) Implement oic_serial in "new" newtmgr

[ASF subversion and git services (JIRA)]

[ 
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-756) mpstats (on nrf51) hangs indefinately

[Christopher Collins (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039502#comment-16039502
 ] 

Christopher Collins commented on MYNEWT-756:


Thanks, Jacob.  When I try with those msys settings (8 / 149), the device does 
not hang and I always receive the NOMEM response.  Here is my target:

{noformat}
targets/bleprph-nrf51dk
app=apps/bleprph
bsp=hw/bsp/nrf51dk
build_profile=optimized

syscfg=BLE_LL_CFG_FEAT_LE_ENCRYPTION=0:BLE_PUBLIC_DEV_ADDR=(uint8_t[6]){0x1c, 
0x22, 0x00, 0x99, 0x99, 
0x99}:BLE_SM_LEGACY=0:BLE_SM_SC=0:LOG_LEVEL=0:MSYS_1_BLOCK_COUNT=8:MSYS_1_BLOCK_SIZE=149
{noformat}

Could you please paste your target so I can try with your settings?

> mpstats (on nrf51) hangs indefinately
> -
>
> Key: MYNEWT-756
> URL: https://issues.apache.org/jira/browse/MYNEWT-756
> Project: Mynewt
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: Newt
>Reporter: Jacob
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> I believe core is failing before sending the last packet, as neither newtmgr 
> or node-newtmgr receives that packet.
> Jacobs-MacBook-Air:newtmgr jacobrosenthal$ GODEBUG=cgocheck=0 newtmgr mpstats 
> -cnimble_bleprph -t -ldebug
> 2017/05/11 22:28:46 [DEBUG] BLE Connection devaddr:[]
> 2017/05/11 22:28:46 [DEBUG] State:PoweredOn
> 2017/05/11 22:28:46 [DEBUG] scanning...
> 2017/05/11 22:28:46 [DEBUG] Peripheral Discovered: , Address:[0 0 0 0 0 0] 
> Address Type:0
> 2017/05/11 22:28:47 Unhandled event: xpc.Dict{"kCBMsgId":53, 
> "kCBMsgArgs":xpc.Dict{"kCBMsgArgDeviceUUID":xpc.UUID{0x2f, 0xd, 0xcb, 0x60, 
> 0xf, 0x3e, 0x47, 0x52, 0xb7, 0x74, 0x13, 0x29, 0x3a, 0x3, 0xd4, 0xd0}, 
> "kCBMsgArgATTMTU":104}}
> 2017/05/11 22:28:47 [DEBUG] Peripheral Connected
> 2017/05/11 22:28:47 [DEBUG] Newtmgr Service Found 
> 2017/05/11 22:28:47 [DEBUG] Newtmgr Characteristic Found
> 2017/05/11 22:28:47 [DEBUG] Writing newtmgr request &{Op:0 Flags:0 Len:0 
> Group:0 Seq:0 Id:3 Data:[]}
> 2017/05/11 22:28:47 [DEBUG] Serializing request &{Op:0 Flags:0 Len:0 Group:0 
> Seq:0 Id:3 Data:[]} into buffer [0 0 0 0 0 0 0 3]
> 2017/05/11 22:28:47 [DEBUG] Tx packet dump:
>   00 00 00 00 00 00 00 03   ||
> 2017/05/11 22:28:47 [DEBUG] Write BLE Packet:buf:: len::8
> 2017/05/11 22:28:47 [DEBUG] Read BLE 
> Packet:buf::l?brcfmpools?fmsys_1?fblksiz$enblks
>   
>   enfreecmin?wble_hci_ram_evt_hi_pool?fblksizHenblkse len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   01 00 02 6c 00 00 00 03  bf 62 72 63 00 66 6d 70  |...l.brc.fmp|
> 0010  6f 6f 6c 73 bf 66 6d 73  79 73 5f 31 bf 66 62 6c  |ools.fmsys_1.fbl|
> 0020  6b 73 69 7a 19 01 24 65  6e 62 6c 6b 73 0c 65 6e  |ksiz..$enblks.en|
> 0030  66 72 65 65 09 63 6d 69  6e 00 ff 77 62 6c 65 5f  |free.cmin..wble_|
> 0040  68 63 69 5f 72 61 6d 5f  65 76 74 5f 68 69 5f 70  |hci_ram_evt_hi_p|
> 0050  6f 6f 6c bf 66 62 6c 6b  73 69 7a 18 48 65 6e 62  |ool.fblksiz.Henb|
> 0060  6c 6b 73 02 65|lks.e|
> 2017/05/11 22:28:47 [DEBUG] Deserialized response &{Op:1 Flags:0 Len:620 
> Group:0 Seq:0 Id:3 Data:[191 98 114 99 0 102 109 112 111 111 108 115 191 102 
> 109 115 121 115 95 49 191 102 98 108 107 115 105 122 25 1 36 101 110 98 108 
> 107 115 12 101 110 102 114 101 101 9 99 109 105 110 0 255 119 98 108 101 95 
> 104 99 105 95 114 97 109 95 101 118 116 95 104 105 95 112 111 111 108 191 102 
> 98 108 107 115 105 122 24 72 101 110 98 108 107 115 2 101]}
> 2017/05/11 22:28:47 [DEBUG] Read BLE 
> Packet:buf::nfreecmin?wble_hci_ram_evt_lo_pool?fblksizHenblkenfrecmi?rble_hs_hci_ev_pool?fblksizenblks
>  len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   6e 66 72 65 65 02 63 6d  69 6e 00 ff 77 62 6c 65  |nfree.cmin..wble|
> 0010  5f 68 63 69 5f 72 61 6d  5f 65 76 74 5f 6c 6f 5f  |_hci_ram_evt_lo_|
> 0020  70 6f 6f 6c bf 66 62 6c  6b 73 69 7a 18 48 65 6e  |pool.fblksiz.Hen|
> 0030  62 6c 6b 73 08 65 6e 66  72 65 65 08 63 6d 69 6e  |blks.enfree.cmin|
> 0040  08 ff 72 62 6c 65 5f 68  73 5f 68 63 69 5f 65 76  |..rble_hs_hci_ev|
> 0050  5f 70 6f 6f 6c bf 66 62  6c 6b 73 69 7a 10 65 6e  |_pool.fblksiz.en|
> 0060  62 6c 6b 73 0a|blks.|
> 2017/05/11 22:28:47 [DEBUG] Read BLE Packet:buf::enfree
> cmin  
> ?pble_hs_conn_pool?fblksizTenblksenfreecmin?sble_l2cap_chan_pool?fblksizenblksenfr
>  len::101
> 2017/05/11 22:28:47 [DEBUG] Rx packet dump:
>   65 6e 66 72 65 65 0a 63  6d 69 6e 09 ff 70 62 6c  |enfree.cmin..pbl|
> 0010  65 5f 68 73 5f 63 6f 6e  6e 5f 70 6f 6f 6c bf 66  |e_hs_conn_pool.f|
> 0020  62 6c 6b 73 69 7a 18 54  65 6e 62 6c 6b 

[jira] [Commented] (MYNEWT-543) setting sys cfg values via newt erases old settings

[ASF subversion and git services (JIRA)]

[ 
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

[ASF subversion and git services (JIRA)]

[ 
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

[ASF subversion and git services (JIRA)]

[ 
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] [Created] (MYNEWT-773) Implement oic_serial in "new" newtmgr

[Christopher Collins (JIRA)]

Christopher Collins created MYNEWT-773:
--

 Summary: 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)