Re: Trouble running bleprh example

[James Howarth]

Hi Chris,
Is there a way to hook up to the device while it is running to see the debug 
messages?  So that I can diagnose some of these problems myself?
CheersJames






On Mon, May 16, 2016 at 12:38 PM -0700, "Christopher Collins" 
 wrote:










Hi James,

On Mon, May 16, 2016 at 10:49:10AM -0700, James Howarth wrote:
> Hi,
> 
> I am trying to get the bleprph example up and running on a Nordic nRF52
> PDK.  But I can't seem to see the device using the LightBlue app running on
> my iPhone.
[...]

Hi James,

I'm pretty sure I know what the problem is - the application task's
stack is overflowing right out the gate.  I'm afraid I have to take the
blame for this one; the default logging settings use a lot of stack, and
I don't often test with them. 

The fix is simple: increase the application stack size from 200 to 288
words.  You can do this by changing apps/bleprph/src/main.c as follows:

#define BLEPRPH_STACK_SIZE  (OS_STACK_ALIGN(288))

This change has already been made to the development branch, but it
didn't make it into the previous release.  Using the develop branch
instead of fixing the bug yourself is also an option; you can do so by
changing your project.yml as follows:

FROM:

repository.apache-mynewt-core:
type: github
vers: 0-latest
user: apache
repo: incubator-mynewt-core

TO:

repository.apache-mynewt-core:
type: github
vers: 0-dev
user: apache
repo: incubator-mynewt-core

(change the "vers" field).

Then upgrade your packages with "newt upgrade", e.g.,

[ccollins@iori:~/tmp/myproj]$ newt upgrade
apache-mynewt-core
Would you like to upgrade repository apache-mynewt-core from 0.7.9-none to 
0.0.0-none ? [Yn] y

Naturally, this branch is quite unstable!

Chris

core files, memory to include

[marko kiiskila]

Hi,

I’ve started implementing support for core dump generation.
Core would be generated on assert() and on unhandled
exceptions.
This would be placed somewhere on flash, and then you
can download it from target and use it together with the
built binary to look at system state at the time of the fault.

For the initial implementation, I was going to dump all the
RAM present in the system, and just assume that there
would be enough flash space to keep it.
The info about memory ranges could come from BSP(?) in 
form of an array.
I assume BSP would be the right owner for this data. Unless
there are countering opinions?

The 2nd rev of coredumping would then allow user to have
an option for smaller dump. This would not contain all
RAM,  but rather a subset. I was thinking of only including the
stack of the currently running task in it. Of course, this would be
for later.
—
M

Re: Trouble running bleprh example

[Christopher Collins]

Hi James,

On Mon, May 16, 2016 at 10:49:10AM -0700, James Howarth wrote:
> Hi,
> 
> I am trying to get the bleprph example up and running on a Nordic nRF52
> PDK.  But I can't seem to see the device using the LightBlue app running on
> my iPhone.
[...]

Hi James,

I'm pretty sure I know what the problem is - the application task's
stack is overflowing right out the gate.  I'm afraid I have to take the
blame for this one; the default logging settings use a lot of stack, and
I don't often test with them. 

The fix is simple: increase the application stack size from 200 to 288
words.  You can do this by changing apps/bleprph/src/main.c as follows:

#define BLEPRPH_STACK_SIZE  (OS_STACK_ALIGN(288))

This change has already been made to the development branch, but it
didn't make it into the previous release.  Using the develop branch
instead of fixing the bug yourself is also an option; you can do so by
changing your project.yml as follows:

FROM:

repository.apache-mynewt-core:
type: github
vers: 0-latest
user: apache
repo: incubator-mynewt-core

TO:

repository.apache-mynewt-core:
type: github
vers: 0-dev
user: apache
repo: incubator-mynewt-core

(change the "vers" field).

Then upgrade your packages with "newt upgrade", e.g.,

[ccollins@iori:~/tmp/myproj]$ newt upgrade
apache-mynewt-core
Would you like to upgrade repository apache-mynewt-core from 0.7.9-none to 
0.0.0-none ? [Yn] y

Naturally, this branch is quite unstable!

Chris

Trouble running bleprh example

[James Howarth]

Hi,

I am trying to get the bleprph example up and running on a Nordic nRF52
PDK.  But I can't seem to see the device using the LightBlue app running on
my iPhone.

Here's what I have done:

   - I copied the "repos/apache-mynewt-core/apps/bleprph" folder to apps/
   - I edited the pkg.deps: in apps/bleprph/pkg.yml to:

pkg.deps:
- "@apache-mynewt-core/libs/os"
- "@apache-mynewt-core/sys/log"
- "@apache-mynewt-core/net/nimble/controller"
- "@apache-mynewt-core/net/nimble/host"
- "@apache-mynewt-core/libs/console/full"
- "@apache-mynewt-core/libs/baselibc"



   - I set up the following targets:

targets/nrf52_boot
app=@apache-mynewt-core/apps/boot
bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
build_profile=optimized
targets/perph
app=apps/bleprph
bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
build_profile=debug


   - I then loaded the boot and perph images.
   - Power-cycled the board


Any suggestions are greatly appreciated.

Cheers
James