What are the conditions that produce an MPSL ASSERT 112, 2105 ?

Hello, anyone.

On a NRF52840DK, modified to match my target. Using nrf SDK v2.1.0.

I have bluetooth (config for firmware upgrade by BT) advertize smp, have connection and notifs seemingly working

I am having a MPSL ASSERT 112, 2105 as soon as the fw upgrade starts.

What are the conditions that produce an MPSL ASSERT 112, 2105 ?

I know that it fundamentally has to do with conflicting configurations that I am fighting with for eons now.

Could you please publish the exhaustive list of MPSL ASSERT x,y. We would gain some dev time.

Parents
  • Hi Laurent,

    I don't have the exhaustive list either, unfortunately. I've asked the MPSL team and will get back to you when I know more.

    Could you please publish the exhaustive list of MPSL ASSERT x,y. We would gain some dev time.

    I understand that this would be useful, but as far as I know there are no plans to publish this. Still, I've passed on your request!

    Best regards,

    Raoul

  • Hi Laurent,

    I heard back from our MPSL team:

    Regarding the list of MPSL asserts: We don't have such a list internally, and also these assert codes can be different for each new NCS release. Also, each assert can have many different reasons so unfortunately I don't think there is convenient way to share such a list with customers, it will be basically unusable.

    Regarding the issue itself, they are asking for some clarification:

    1) Is the customer disabling interrupts in their application for some reason?
    2) Is the customer writing to flash or is he doing some other time-consuming operations?
    3) Can they share their prj.conf files to check if they have the correct settings?

    Could you expand on this, and also share your config files?

    I know that it fundamentally has to do with conflicting configurations that I am fighting with for eons now.

    Are you suspecting some kconfig options in particular?

    Thanks.

    Best regards,

    Raoul

Reply
  • Hi Laurent,

    I heard back from our MPSL team:

    Regarding the list of MPSL asserts: We don't have such a list internally, and also these assert codes can be different for each new NCS release. Also, each assert can have many different reasons so unfortunately I don't think there is convenient way to share such a list with customers, it will be basically unusable.

    Regarding the issue itself, they are asking for some clarification:

    1) Is the customer disabling interrupts in their application for some reason?
    2) Is the customer writing to flash or is he doing some other time-consuming operations?
    3) Can they share their prj.conf files to check if they have the correct settings?

    Could you expand on this, and also share your config files?

    I know that it fundamentally has to do with conflicting configurations that I am fighting with for eons now.

    Are you suspecting some kconfig options in particular?

    Thanks.

    Best regards,

    Raoul

Children
Related