This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ANCS minimum requirement

Hi,

I'm working on integrating ANCS on our existing and futur products. I started to port the Nordic SDK example (12.x) and it seems to work fine on nRF52, which will be fine for our futur product line that will probably based on it.

But I also try to port it on nRF51, because we have released products based on it. I can make a working implementation on the DK, but the SDK example for ANCS is too big (FLASH and RAM) to cohabit with our existing Firmware.

So my question is the following. On the ANCS SDK example, what are the minimum requirement for a working ANCS peripheral ?

I understand it need at least the Service and Characteristics. What about pairing and db_discovery ? Can this be simplified at some points ?

Any experience, link or feedback is welcome on this subject.

Note that I'm using SD130

Thanks

Parents
  • Hi Thierry,

    We do have the example in SDK v12.2 for nRF51 (inside PCA10028 folder). Could you simply use the example for nRF51 ?

    Which nRF51 chip variant you have on your product? You may have issue with the size of RAM since we made the example for the 32kB RAM variant. If it doesn't fit your chip, we will have to simplify the code.

  • I assume you also used MicroLIB so the 2kB of heap is not counted (you can remove 2kB heap manually also) I don't think it would be simpler to write your own discovery module as you focusing on just single ANCS service and know which handles exactly you want to discover and store.

    About the peer manager, maybe you can try to use device manager (removed from SDK v12) instead, it should use less RAM than peer manager. Or you can think of making your own module, simply store the bond information and get read it back when needed.

    How much RAM/flash still exceeded after all you've done ?

Reply
  • I assume you also used MicroLIB so the 2kB of heap is not counted (you can remove 2kB heap manually also) I don't think it would be simpler to write your own discovery module as you focusing on just single ANCS service and know which handles exactly you want to discover and store.

    About the peer manager, maybe you can try to use device manager (removed from SDK v12) instead, it should use less RAM than peer manager. Or you can think of making your own module, simply store the bond information and get read it back when needed.

    How much RAM/flash still exceeded after all you've done ?

Children
No Data
Related