Pstorage functional with deactivated softdevice?

[Nobody13]

Preface: I am developing a software working with different radio protocols (enhanced shockburst, bluetooth,...). Therefore I implemented uart commands for switching radio protocols.

This means I have to switch softdevice very often on and off. If radio chip is configured for enhanced shockburst and I want to save data in flash, I have to put radio module offline, start softdevice, save data to flash, stop softdevice and reconfigure chip for shockbust.

Is there a way for using pstorage functions without active softdevice, so I must not switching softdevice off and on?

Remarks: Softdevice does not want active hardware configurations (like radio module). If softdevce will be startet with active radio module for example, softdevice will throw an error which causes a reset.

Switching to pstorage without softdevice or pstorage raw isn't really an option because run time manager gots cracy and wants to install serveral packages like DFU.

[Jørgen Holmefjord]

Hi,

I'm not sure I understand your last comment. pstorage_nosd is for use without softdevice, it is not possible to use the normal pstorage without softdevice.

You might need to modify the libraries a bit if you want to use pstorage both with and without softdevice, to make sure you use the softdevice-safe pstorage functions when softdevice is enabled and nosd functions when it is disabled.

Could you explain the errors you are getting when switching to pstorage_nosd in more details?

Best regards,

Jørgen

[Nobody13]

Yes pstorage_nosd is for use without softdevice. But if I select this package dialog "Manage Run-Time Environment" gets angry and returns message "Component conflicts with other selected components and has unresolved dependencies".

Package pstorage_nosd conflicts with package softdevice_present, which I need for several other packages. If I deselect package softdevice_present new conflicts with s110, app_util will be generated. If I deselect app_util new conflicts with app_fifo, app_scheduler, app_timer will be generated.

I my opinion packages are coupled too strong avoiding easy package change.

And I cannot remove softdevice s100 because sometimes I need to switch to blueooth protocol.

It drives me crazy...

:->