[jira] [Created] (MYNEWT-770) Sim - Share sig/no-sig implementation for all sim architectures
Christopher Collins created MYNEWT-770: -- Summary: 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 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] [Updated] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-744: Description: - 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 changes the drivers to work with all the fixes mentioned above. was: 1. Changa data structure to SLIST instead of TAILQ so that it can get initialized statically. 2. Remove dummy functions in the bsp and add the sensor device initialization functions instead. 3. sensor_dev_create() should be moved out of hal_bsp.c. > 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 >
[jira] [Updated] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-744: Description: - 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. was: - 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()
[jira] [Assigned] (MYNEWT-756) mpstats (on nrf51) hangs indefinately
[
https://issues.apache.org/jira/browse/MYNEWT-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheela reassigned MYNEWT-756:
-
Assignee: Christopher Collins (was: Sterling Hughes)
> 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
>
> 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
> Packet:buf::eecmin?wble_l2cap_sig_proc_pool?fblksizenblksenfreecmin?xle_att_svr_prep_entry_pool?fblksiz
>
>
[jira] [Assigned] (MYNEWT-757) Inconsistent tags among newt, blinky, and core
[ https://issues.apache.org/jira/browse/MYNEWT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheela reassigned MYNEWT-757: - Assignee: Aditi Hilbert (was: Sterling Hughes) > Inconsistent tags among newt, blinky, and core > -- > > Key: MYNEWT-757 > URL: https://issues.apache.org/jira/browse/MYNEWT-757 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newt >Reporter: Christopher Collins >Assignee: Aditi Hilbert > Fix For: v1_1_0_rel > > > * "newt install" should download the corresponding version of blinky. > * Blinky's project.yml should specify the corresponding version of core. > Currently, the versions don't match up properly: > * In master: newt specifies blinky's develop tag > * In develop: blinky's project.yml specifies core's 1-latest tag. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (MYNEWT-758) BLE Host - OOB security for SC
[ https://issues.apache.org/jira/browse/MYNEWT-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheela reassigned MYNEWT-758: - Assignee: Szymon Janc > BLE Host - OOB security for SC > -- > > Key: MYNEWT-758 > URL: https://issues.apache.org/jira/browse/MYNEWT-758 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Szymon Janc > Fix For: v1_1_0_rel > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
