RE: Details of Known Issues (DRGN-10613)

Elfving — Wed, 04 Dec 2024 09:10:30 GMT

Hello again, I've now heard from the relevant team.

[quote user=""]What specifically happens when a memory access fault occurs?
[/quote]

nrf_fault_handler_t callback provided to sd_softdevice_enable will be called with id=NRF_FAULT_ID_APP_MEMACC. How to handle faults is up to the application.

[quote user=""]

What is the intent of this change and what impact will it have, including side effects?

[/quote]

This will cause the MWU handler to not be masked by the critical section, and thus be run at the correct time. We are not aware about any side-effects of the workaround.

[quote user=""]

If it has no impact, why is it not included in the released source?

[/quote]

The issue was discovered too late to include it to the major 7.0.0 release. It was not prioritized for minor releases mainly because workaround deemed to be enough.

[quote user=""]Also, Is it correct to assume that the information in the release notes is inherited from the previous version for each release?
Do I only need to check the most recent release notes, or do I need to check all release notes?[/quote]

Yes, it's enough to check "Limitations" and "Known Issues" sections in the most recent release notes only.

Regards,

Elfving

RE: Details of Known Issues (DRGN-10613)

Elfving — Tue, 03 Dec 2024 14:41:38 GMT

Hi,

I believe this previous case might answer some of your questions. It is also a bit strange to me why the fix wasn't added in the source code, though for the question on why it isn't added these days I guess one reason is that nRF5 SDK isn't as actively maintained anymore. For that reason I would also recommend you to switch to NCS.

For the rest of the questions, I've forwarded them to the relevant team, I'll let you know once I hear from them.

Regards,

Elfving