common BSP API,

Hi, I was chatting with Will about this offline; there’s no header file describing API exported by BSPs. This includes function prototypes like os_bsp_init() (currently declared in libs/os), bsp_imgr_current_slot() (currently declared individually on every BSP’s bsp/bsp.h), bsp_flash_dev()

Re: core files, memory to include

It would be quite a bit of work for a very specialized feature :) Modifying BSP’s array of memory regions should be easy enough to do in the cases where peripheral memory is wanted, IMHO. > On May 17, 2016, at 1:31 PM, will sanfilippo wrote: > > Sounds good. I see if you have

Re: core files, memory to include

Hi Will, I was going to collect all the SRAM to start with. Once all is working, and the size of the core becomes an issue, then start cutting down. There’s nothing stopping you from collecting peripheral register state, as long as the registers are memory mapped. Just need to tell coredump

Re: Trouble running bleprh example

Hi Chris, - I am using LightBlue on my iPhone. I have also tried the nRF MCP app as well with the same result. - Yes, the LightBlue does not show the device when you tell it to re-scan. - I also tried commenting out the data-length extension, but that did not seem to change

Re: Trouble running bleprh example

On Mon, May 16, 2016 at 09:29:37PM -0700, James Howarth wrote: > Hi Chris, > > Thanks. I'm getting closer. > > Using the 'LightBlue Explorer' app: > >- I can see the nimble-bleprh device >- nim-bleprh appears to be advertising no services. >- When I try and connect to the nRF52,