Re: How to change the CPU time frequency of mynewt and nimble stack

Hello: This issue should now be fixed in the latest development branch. Note that this is not working on the nrf51 platforms but since you were using nrf52 it should work. Let me know if you see any issues with it. > On Jan 8, 2017, at 6:20 PM, WangJiacheng wrote:

Re: air_quality app

I think it should be '/include/pkgname/pgkname.h' for the include files. Here's an example I have locally with 'tsl2561' as the root folder where this command was run: $ tree -L 3 . ├── include │ └── tsl2561 │ └── tsl2561.h ├── pkg.yml ├── src │ ├── tsl2561.c │ ├── tsl2561_priv.h │

air_quality app

I'm working through the air_quality tutorial, and am encountering some problems that I'm not sure the root of. I've created the proper files: ls -R libs/my_driver/senseair/ total 4 0 drwxr-xr-x 3 dsimmons staff 102 Jan 9 16:42 include 4 -rw-r--r-- 1 dsimmons staff 869 Jan 9 16:51

Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, On Sun, Jan 08, 2017 at 01:04:54PM -0700, Jacob Rosenthal wrote: > On Mon, Jan 2, 2017 at 2:46 PM, Christopher Collins > wrote: > > > Do you know how big your loader is currently? > > > Well, could be anything based on how much Im trying to strip from the >

Re: crypto libraries

Hi, > On Jan 9, 2017, at 5:30 AM, Szymon Janc wrote: > > Hi, > > Currently there are 2 crypto libraries in mynewt sourcetree - TinyCrypt and > mbedTLS. TinyCrypt is used only by Bluetooth LE Secure Connections and > bootutils. > > From a very brief look it seems

Re: How to change the CPU time frequency of mynewt and nimble stack

You should be able to do exactly what you tried to do; that was one of the intents with os_cputime. Hopefully I will have an answer soon regarding why this does not work. Regarding timers: The nimble stack on the nrf52 currently uses Timer 0 for cputime (and thus for the controller BLE

Re: BLE certification of the Nimble stack

Hi, On 4 January 2017 at 18:22, Klaus Hagen wrote: > Hi, > > Is or will released Nimble stack versions be Bluetooth SIG qualified in the > future? Or are companies integrating the Nimble stack supposed to get their > own qualification done? You always have to

crypto libraries

Hi, Currently there are 2 crypto libraries in mynewt sourcetree - TinyCrypt and mbedTLS. TinyCrypt is used only by Bluetooth LE Secure Connections and bootutils. >From a very brief look it seems that mbetTLS provides necessary EC and DH API. Also TinyCrypt seems to be in quite old version