Soft Device Controller hard fault - NULL pointer dereference in library

RE: Soft Device Controller hard fault - NULL pointer dereference in library

sss — Sun, 01 May 2022 23:56:54 GMT

Thanks for clarifying, this helped significantly in narrowing the scope of our investigation.

We were calling sdc_support_ext_adv() with the peripheral library linked in - which should have yielded an error from the API, but didn't. In 1.9.1 or thereabouts, this appears to have been resolved and it will instead report NRF_EOPNOTSUPP as expected. Now we are using sdc_support_adv() with the peripheral library and everything is working as expected. Thanks for your help.

RE: Soft Device Controller hard fault - NULL pointer dereference in library

Susheel Nuguru — Fri, 22 Apr 2022 07:03:15 GMT

The symbol should be for ll_adv_prepare but we are not able to understand the full context of this due to the obfuscated call stack.

Are you using advertising extensions? and could you also give some code snippets on how you are initializing the advertising parameters?

RE: Soft Device Controller hard fault - NULL pointer dereference in library

Susheel Nuguru — Thu, 21 Apr 2022 10:08:53 GMT

I need to get access to the map file for the softdevice controller version to get more understanding on the symbol you mentioned. I will ask the softdevice team to help me with this. Will come back to you when I have more info.

RE: Soft Device Controller hard fault - NULL pointer dereference in library

sss — Thu, 21 Apr 2022 08:14:58 GMT

Hi there,

I'm limited in what I can share from a source perspective because of commercial sensitivity, but I will help where I can. We are using nrfxlib 1.9.0 and nrfx 1.8.0.

Is the map file something you can request from the team? The symbol remains as sym_PY5KUATPBYOYJBMP6H7AVRPSEO7BZX2JK524O6A across all of our builds.

RE: Soft Device Controller hard fault - NULL pointer dereference in library

Susheel Nuguru — Thu, 21 Apr 2022 07:58:59 GMT

Hi,

Unfortunately those symbols does not give any more information without the map file. Can you help us replicate this problem on our end?
Which Nordic Connect SDK version are you using?