Hi Ram, On Thu, Mar 15, 2018 at 12:07:55PM +0530, Sriram V wrote: > Hi, > > I have the following doubts on NimBle: > > The document says 32+ concurrent connections, multiple connections in > simultaneous central and peripheral roles. Does that mean the "device > running Nimble" can connect to 32 different other devices like phones?
Yes, with one caveat: each of the 32 centrals needs to be sufficiently cooperative in choosing connection parameters ( http://www.novelbits.io/ble-connection-intervals/). My knowledge of the BLE link layer is pretty limited, so someone more informed may need to chime in. Your app might need to request different connection parameters from the centrals (using http://mynewt.apache.org/latest/network/ble/ble_hs/ble_gap/functions/ble_gap_update_params/). Of course, you will also need to build the Mynewt image device with a configuration suitable for 32 concurrent connections (e.g., NIMBLE_MAX_CONNECTIONS=32, etc.). > Also, I wanted to check if the stack provides firmware upgrade > capability and if so, can you provide an example on how it is being > done. The newtmgr tool (http://mynewt.apache.org/latest/newtmgr/overview/) is used to upgrade Mynewt devices. Newtmgr is a command line tool, but I believe there are other client libraries available (node.js, android?). I don't see any examples of image upgrades, but there is some information here, under the "Image Upgrade" heading: http://mynewt.apache.org/latest/os/modules/split/split/ > Can we upgrade multiple devices (having Nimble) at the same time using > a single device/phone supporting BT? It probably not the most helpful answer, but: yes, as long as the phone can handle it. You can certainly perform multiple simultaneous upgrades from a computer using the newtmgr tool. That said, I have a feeling you will get better overall throughput if you limit yourself to one upgrade at a time. Chris
