Re: Subscription Request and Question.

Well those are bad news I guess. Tim, sorry to be so persisten with this but again, if neither Android nor iOS allow you to specify your own keys, how can you use pre-shared keys? If I understood correctly, I can install a unique key on each device at manufacture and keep a copy of it in the

Re: NRF52dk ADC

You should still be able to access a ref to the branch even if it was deleted. For git, deleting a branch is more like shoving the clutter in the closet than throwing it in the trash. try 'git branch -a' to see if it's visible on the remote... and if nothing else, 'git checkout 0c0f3e1' because

Re: Subscription Request and Question.

On 2 December 2016 at 17:09, Christopher Collins wrote: > Sorry if I missed this earlier in the thread, but will iOS really let > you use an external key for BLE encryption? Just based on my limited > experience with CoreBluetooth, I wouldn't expect this functionality to >

Re: NRF52dk ADC

Sadly my fork does not have that branch any longer ... If anyone DOES happen to have a copy of it, and could send me the relevant main.c file for reference, I'd greatly appreciate it! Best regards, dg > On Dec 2, 2016, at 12:43 PM, Christopher Collins wrote: > > On Fri,

Re: NRF52dk ADC

On Fri, Dec 02, 2016 at 09:30:04AM -0800, will sanfilippo wrote: > There is a branch called “sterly_refactor” that we used when we were > refactoring bsp and other code. There is ADC code in there. If you > checkout that branch you can go to the apps directory and look for the > sblinky app. In

Re: NRF52dk ADC

There is a branch called “sterly_refactor” that we used when we were refactoring bsp and other code. There is ADC code in there. If you checkout that branch you can go to the apps directory and look for the sblinky app. In that main.c (which is where I said this stuff shouldnt be but that was

Re: NRF52dk ADC

Do you have some functioning code you could share? I'm really just using this sensor https://www.adafruit.com/products/1786 and reading an analog voltage from it anyway. dg > On Dec 2, 2016, at 12:06 PM, will sanfilippo wrote: > >

Re: NRF52dk ADC

Just to chime in here. Not sure what your interrupt issue without looking at it in more detail, but there is a reason you dont want to do the init in main and you want to do it in the bsp: you now have processor specific code in your application. If you want your driver or application to be

Re: Subscription Request and Question.

Hi Rodrigo, On Fri, Dec 02, 2016 at 12:30:12PM +0100, Rodrigo Lorenzo Leal wrote: > OK so pre shared key is my best option I guess. > > What I don't understand is, if is possible to have pre-shared key, that is > accesible through the cloud, why I cannot generate a key on the cloud and > access

Re: Subscription Request and Question.

On Fri, Dec 02, 2016 at 10:59:13AM +, Tim Hutt wrote: [...] > (there are supposed to be native Channel-Oriented Connections coming but I > wouldn't hold my breath). Just a small clarification: connection-oriented channels were already added in bluetooth 4.1. However, Nimble doesn't support

Re: [newtmgr] Delete/overwrite image in slot 1

Hi Kevin, On Fri, Dec 02, 2016 at 09:51:25AM +0100, Kevin Townsend wrote: > Is there a means with newtmgr today to delete an image in bank 1, for > example if you uploaded an image there incorrectly? There is no way to delete the image in slot 0. This is an instance of a more general rule:

Newbie & running into an error during setup

Hi everyone, Newbie here, and looking forward to learning more about Mynewt! I'm going through installing and setting up Mynewt on Ubuntu 16.04 (inside a VM on a macbook) using the Docker method. The issue I'm running into is: newt install -v apache-mynewt-core Downloading repository

Re: Subscription Request and Question.

OK so pre shared key is my best option I guess. What I don't understand is, if is possible to have pre-shared key, that is accesible through the cloud, why I cannot generate a key on the cloud and access it doing a request, from both the app and the device (through GPRS). Maybe is not a OOB

Re: Subscription Request and Question.

On 2 Dec 2016 10:52 a.m., "Rodrigo Lorenzo Leal" wrote: > > Tim. > > Thanks for the reply! So there's no way for the BLE library on iOS and > Android to get the key from an external source? (like a server request) and > use that? Correct. > Also, how does an in house

Re: Subscription Request and Question.

Tim. Thanks for the reply! So there's no way for the BLE library on iOS and Android to get the key from an external source? (like a server request) and use that? I'm more experienced on the firmware/peripheral side than in the app one (I just did some minor test projects on Android). Also, how

Re: Subscription Request and Question.

Yes I know it is only against the pairing phase (I did say that in my previous email), but as Rodrigo said you can (apparently) force re-pairing so that is a small comfort. And I have read the spec and as far as I can tell, Francisco Corella is correct: 'LE Secure Connections' in BLE 4.2 uses the

Re: Subscription Request and Question.

Rodrigo, GPRS will allow you to avoid MitM, but you'll still have to do your own crypto unfortunately because OOB isn't supported on iOS or Android. Also you might want to check if GPRS itself is secure! I expect it probably isn't but you may not care about that depending on your paranoia level.

Re: Subscription Request and Question.

Hi guys! This is actually a problem we will need to solve in the product I'm currently developing at my company. In our case, we have a peripheral with no screen or I/O capabilities that connects to an app via BLE. As I understand it (and mike explained very well in his videos), once the key

[newtmgr] Delete/overwrite image in slot 1

Is there a means with newtmgr today to delete an image in bank 1, for example if you uploaded an image there incorrectly? Assuming the following situation: Images: slot=0 version: 0.3.0 bootable: true flags: active hash: 7494da56ead5fe83a0e26ad72fdf1bc8a4d1d6b01b1712e4e1bf4437218f4d8b