Fix vector table relocation for NRF52

[marcuschangarm]

Description

The vector table relocation sequence depends on:

1. Whether the SoftDevice is present.
2. The Application is a bootloader or not.

If the SoftDevice is present and the application is a bootloader
the MBR must be initialized to trap SoftDevice service calls
before setting the new vector table address.

The SCB->VTOR must be set to point at the MBR as well.

If the SoftDevice is not present the SCB->VTOR can point at the
new vector table directly.

Pull request type

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

[marcuschangarm]

@c1728p9

As we discussed. The MBR does not trap SoftDevice service calls if the UICR bootloader address is set hence the extra check.

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : SUCCESS

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

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : FAILURE

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

[0xc0170]

We should wait for nrf52 flash fix and restart CI right away then

[marcuschangarm]

/morph build

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[marcuschangarm]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : FAILURE

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

[mbed-ci]

Test : FAILURE

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

[marcuschangarm]

/morph test

[mbed-ci]

Test : SUCCESS

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

[adbridge]

@c1728p9 Could you please review this PR asap. Thanks

[theotherjimmy]

Depends on prior NRF52 stuff, going to 5.9.0-rc1