Re: Issues with bleprph and blecent on nRF51822xxaa

On Fri, Feb 17, 2017 at 3:38 AM, will sanfilippo wrote: > Hello there Marcos: > > Indeed, some of the sample apps probably wont run in 16KB RAM. If a malloc > fails it should be pretty easy to debug as I would suspect most mallocs in > the code assert() if they cant get the

Re: Issues with bleprph and blecent on nRF51822xxaa

Hi there! On Fri, Feb 17, 2017 at 5:45 PM, marko kiiskila wrote: > > > You could try removing the memory areas which are marked as flash, and then > use > restore. > I.e. > delete mem 0 > delete mem 1 > mem 0 0x rw nocache > info mem > restore binary > > Depending on

Re: Issues with bleprph and blecent on nRF51822xxaa

> On Feb 16, 2017, at 8:19 PM, Marcos Scheeren wrote: > > Hi, Marko. > > On Tue, Feb 14, 2017 at 2:33 PM, marko kiiskila wrote: >> Hi, >> >> >> Quick peek to gdb sources tells me that the memory region is marked as >> flash, and comment says that

Re: Issues with bleprph and blecent on nRF51822xxaa

Hello there Marcos: Indeed, some of the sample apps probably wont run in 16KB RAM. If a malloc fails it should be pretty easy to debug as I would suspect most mallocs in the code assert() if they cant get the memory. Is there a specific app your want to run? > On Feb 16, 2017, at 8:19 PM,

Re: Issues with bleprph and blecent on nRF51822xxaa

Hi, Marko. On Tue, Feb 14, 2017 at 2:33 PM, marko kiiskila wrote: > Hi, > > > Quick peek to gdb sources tells me that the memory region is marked as > flash, and comment says that only allow writes during ‘load’ phase (which, > technically, I guess would be correct). Check the

Issues with bleprph and blecent on nRF51822xxaa

Hi, Last month I was having some issues loading the compiled code to the board without OpenOCD or JLink, just using GDB extended-remote mode, that seems to be solved now - Thanks Marko and Chris for the help! So, I edited the linker script to flash the board at address 0x0 (removed the header