Re: Assert failed in ble_ll_hci.c:999

It is a bug in our stack. We are going to fix it soon so you should see an email that discusses the issue and fix. Thanks for catching this! Will > On Jul 7, 2016, at 6:37 PM, Simon Ratner wrote: > > So, the assert being where it is, would your bet be on a controller bug, a >

Re: Assert failed in ble_ll_hci.c:999

On Thu, Jul 07, 2016 at 06:37:46PM -0700, Simon Ratner wrote: > So, the assert being where it is, would your bet be on a controller bug, a > host bug, or the app corrupting os memory in some way? (I've certainly done > my fair share of the latter ;) Hi Simon, It looks like this is caused by a

Re: Assert failed in ble_ll_hci.c:999

So, the assert being where it is, would your bet be on a controller bug, a host bug, or the app corrupting os memory in some way? (I've certainly done my fair share of the latter ;) On Thu, Jul 7, 2016 at 6:06 PM, will sanfilippo wrote: > There are a few of them actually.

Re: Assert failed in ble_ll_hci.c:999

There are a few of them actually. Note that we returned an error code when the block being freed was not part of the memory pool or either the block or pool is NULL. There was some debate on whether to return an error in the latter two cases, but not any debate about the former. What does

Re: Shell prompt for mynewt

+1 I want to know when console is ready for input. > On Jul 6, 2016, at 10:05 AM, David G. Simmons wrote: > > > So I don’t know if anyone else wanted this, but the lack of a shell prompt > when connected to mynewt was sort of driving me nuts. I’ve been on a command > line