Re: Clarification on ble_gattc_*_by_uuid calls

On Mon, Jun 27, 2016 at 04:13:09PM -0700, Simon Ratner wrote: > Hi Chris, > > One quick clarification question: after receiving a callback with any > error status, do you guarantee that the callback will never be called > again (including with a NULL svc param)? Hi Simon, Yes, that is the

Re: split image design

Im on to how to implement this in newt. Here are my thoughts for review. I am not that familiar with Go or with Newt code, so I’m thinking the most important thing is to get this to work and then figure out how to re-architect this in newt to be “nice”. Here are roughly the steps I will take.

Re: More Serial Issues

Thanks for chiming in Marko and sorry I didnt respond sooner David. For some reason I didnt see any of the latter emails; I was not ignoring you. Well, technically, I guess I was, but it was not intentional :-) > On Jun 27, 2016, at 1:15 PM, David G. Simmons wrote: > > >>

Re: More Serial Issues

> On Jun 27, 2016, at 3:52 PM, marko kiiskila wrote: > > >> On Jun 27, 2016, at 12:19 PM, David G. Simmons wrote: >> >>> >>> On Jun 27, 2016, at 1:30 PM, will sanfilippo >> > wrote: >>> >>> By default we do

Re: More Serial Issues

> On Jun 27, 2016, at 12:19 PM, David G. Simmons wrote: > >> >> On Jun 27, 2016, at 1:30 PM, will sanfilippo > > wrote: >> >> By default we do not enable flow control so those lines shouldnt do anything. >> >> As Kevin states,

Re: More Serial Issues

> On Jun 27, 2016, at 1:30 PM, will sanfilippo wrote: > > By default we do not enable flow control so those lines shouldnt do anything. > > As Kevin states, you hook up RTS to CTS, CTS to RTS, TXD to RXD and RXD to > TXD (if that makes sense). Hopefully the cabling you are

Re: More Serial Issues

By default we do not enable flow control so those lines shouldnt do anything. As Kevin states, you hook up RTS to CTS, CTS to RTS, TXD to RXD and RXD to TXD (if that makes sense). Hopefully the cabling you are using is labeled so it is easy to determine which wires are what (txd from computer

Re: More Serial Issues

On 27/06/16 19:05, David G. Simmons wrote: Will, Thanks! One issue was certainly that I was using the PDK instead of the DK, I’ll add that to the documentation as there was no mention of this. And while I have been known, in the past, to get TX and RX backwards, that is not the case here.

Re: More Serial Issues

Will, Thanks! One issue was certainly that I was using the PDK instead of the DK, I’ll add that to the documentation as there was no mention of this. And while I have been known, in the past, to get TX and RX backwards, that is not the case here. That being said, I’m still getting nothing,

Re: More Serial Issues

David: I am not sure if this is the issue but it could be you are using the nrf52pdk bsp as opposed to the nrf52dk bsp. The PCA version on top of the board will tell you which one you should be using. The pdk is 10036 and the dk is 10040. If you turn the board over you will see that pins

More Serial Issues

Me again … So I gave up on serial to the STM32F3Discovery board (for now) and moved on to the NRF52 board that I just got. Started working through the tutorial http://mynewt.apache.org/os/tutorials/bletiny_project/ and, of course, found