Fix SWI conflict in SoftDevice for NRF52 series

[marcuschangarm]

Description

SWI channels reserved for the SoftDevice were incorrectly defined leading to conflicts in the serial implementation. New serial driver only uses one SWI channel instead of four.

Pull request type

[x] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[0xc0170]

At least one user confirmed that this fixes the issue

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2555
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7453/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[NeilMacMullen]

This seems to address the issue I was seeing in #7219 (comment) so is a significant improvement.

However, there still appears to be an issue with SPI. I'm still trying to pin this down but it appears that on one of the spi buses I am using, it's not possible to read data.

[mbed-ci]

Test : SUCCESS

Build number : 2312
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7453/2312

[marcuschangarm]

@NeilMacMullen

However, there still appears to be an issue with SPI. I'm still trying to pin this down but it appears that on one of the spi buses I am using, it's not possible to read data.

Is this a new issue or do you have an open github issue for it?

[NeilMacMullen]

@marcuschangarm It's 'new' in the sense that I only discovered it after overcoming the initial problems and it doesn't currently have its own issue id. I don't think it was caused by this fix and may have been present on master for some time, I only mentioned it here in case some variation of this fix might be relevant to SPI as well. Probably best if I raise a separate ticket for it.

[marcuschangarm]

I only mentioned it here in case some variation of this fix might be relevant to SPI as well.

I don't recall any direct dependencies between SPI and UART/BLE.

[cmonr]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2205
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7453/

[cmonr]

@NeilMacMullen If there isn't already an issue open, please go ahead and open one. We can track problems better when they're in a GitHub issues instead of comments in PRs.

Bringing this in since the PR appears to address its initial problem scope.

[AGlass0fMilk]

Resolves #7440