Closed jacobrosenthal closed 8 years ago
FYI, if you are working with the latest yotta targets, you'll find that we print the size of available heap (on the console) at the end of the build. There is also a config option to switch to an S110 softdevice to allow freeing up ~2K of memory.
There is note explaining the "out-of-memory" issue in the readme of the example: https://github.com/ARMmbed/ble-examples/blob/master/BLE_EddystoneService/readme.md
heh sorry
startConfigService doesnt return, but If I directly call startBeaconService It appears to work fine. I dont have good debug support set up yet with softdevice (link to a guide at all?) But it looks like the dynamic allocations crash... if I remove some of first allocations I get a few more allocations down the chain so memory?
Im using a target that inherits from nordic-nrf51822-16k-gcc (its the old nordic pca10000 device) Has this been tested on 16k?