OK. thanks, I understand that much better. I totally forgot about
increasing the stack size..
Separately I figured out by commenting things out that
cbor_encode_text_stringz is what was crashing it, and increased the main
stack size. Which makes sense. Now Im back to what started this, with err 8.
> On Apr 19, 2017, at 4:33 PM, Jacob Rosenthal wrote:
>
> On Wed, Apr 19, 2017 at 11:19 AM, marko kiiskila wrote:
>
>> Just general comments, I hope I’m not saying things which are
>> too obvious.
>>
> More specific would be even better :) I dont
On Wed, Apr 19, 2017 at 04:33:05PM -0700, Jacob Rosenthal wrote:
> On Wed, Apr 19, 2017 at 11:19 AM, marko kiiskila wrote:
>
> > Just general comments, I hope I’m not saying things which are
> > too obvious.
> >
> More specific would be even better :) I dont think my gdb is up
On Wed, Apr 19, 2017 at 11:19 AM, marko kiiskila wrote:
> Just general comments, I hope I’m not saying things which are
> too obvious.
>
More specific would be even better :) I dont think my gdb is up to par
Either g_os_run_list or one of the task structures is getting
Just general comments, I hope I’m not saying things which are
too obvious.
Either g_os_run_list or one of the task structures is getting smashed.
As you know you tasks beforehand, you can walk through them manually
to figure which one it is.
Usually culprit is stack overflow, so once you find out
Anyone have thoughts on debugging the scheduler crash? That point gets hit
constantly, so breaking there is tough, break commands and logging also
appears to mess with bluetooth timing as I cant get a connect when I do
that.
On Mon, Apr 17, 2017 at 10:49 AM, Jacob Rosenthal
Hi Marko,
You're right, that looks eerily similar to what I'm seeing (MYNEWT-656
does). Yeah my next task it to upgrade to the latest OS version.
Thanks again,
Pritish
On Wed, Apr 19, 2017 at 10:21 AM, marko kiiskila wrote:
>
> > On Apr 19, 2017, at 10:06 AM, Pritish Gandhi
Hi, Will
It looks like I stepped on every possible rake while migrating to mynewt.
Here is what I have for now:
1. After enabling ble_phy_stats & ble_ll_stats I saw big values of
tx_late counters. This was the cause of "invisible" advertising packets:
just not tx'ed. As a workaround I
> On Apr 19, 2017, at 10:06 AM, Pritish Gandhi wrote:
>
> I'm sorry I forgot to give more details about my setup and architecture.
>
> I'm running this on an STM32F4Discovery EVB (so STM32F407VG). It can't be
> the issue with the controller stack, since I'm not using
I'm sorry I forgot to give more details about my setup and architecture.
I'm running this on an STM32F4Discovery EVB (so STM32F407VG). It can't be
the issue with the controller stack, since I'm not using the controller. In
my setup the STM32F4Discovery is driving an externally connected Broadcom
I for one am really looking forward to rtt as I dont have serial on several
off the shelf devices Im working with.
On Wed, Apr 19, 2017 at 1:16 AM, Łukasz Rymanowski <
lukasz.rymanow...@codecoup.pl> wrote:
> I suggest to create feature branch for that work in this case. I believe
> Michal will
Well, recently I've also get stack corruption: 80 dwords for BLE
controller's LL task was too low value. Increasing it to 128 works for me.
I'm in doubt, in theory this should be the common case, but de-facto
it's not. Possibly your exception is related to the case. Anyway, this
requires more
I suggest to create feature branch for that work in this case. I believe
Michal will fix support for newtmgr, but till then some of us could make
use of RTT and other cool stuff which will go on top (e.g. support for
btmon).
What do you think?
On 19 April 2017 at 00:23, marko kiiskila
13 matches
Mail list logo