We looked at doing this on an nRF51422 running S310 version 1. We never did it but we did get confirmation it was theoretically possible with some tricky linker work.
The issue is the soft device checks the return address of the code that calls into the soft device for reasonableness. If you are calling into the soft device from a region of RAM beyond the 16K boundary, the soft device will assume error and lock up.
So if you can structure your code and your linker such that no call into the soft device ever originates from beyond the 16K boundary, then in theory it should work. Or so we were told with the s310 version 1. Not sure if this works for your situation.
We looked at doing this on an nRF51422 running S310 version 1. We never did it but we did get confirmation it was theoretically possible with some tricky linker work.
The issue is the soft device checks the return address of the code that calls into the soft device for reasonableness. If you are calling into the soft device from a region of RAM beyond the 16K boundary, the soft device will assume error and lock up.
So if you can structure your code and your linker such that no call into the soft device ever originates from beyond the 16K boundary, then in theory it should work. Or so we were told with the s310 version 1. Not sure if this works for your situation.
