The UART (Port 2) gets garbled after bt_enable(). This issue does not occur if actively Debugging using Segger.
The issue is also reproducible upon a settings_save_one() call. But the UART shell behavior is restored if NRF_POWER->TASKS_CONSTLAT is set to 1.
For the bt_enable() test step, though, the CONSTLATSTAT is set back to 0 constantly so the UART shell remains unrecoverable.
```
4:22:29.4657|[00:?0:11.650,9200m<inf>sys: Event 0x01
14:22:29.4[0?0:11.650,980??1;33m<wrn> led: sequ? 1 in ??ogress, queueing 3
14:22:29.4?--- 24?sages dropped ---
14:22:29.4988|??[00:00:11.?2] nf>?sdc_hci_driv?SoftDevoce Controll?ild??sion:
14:22:29.5002| ? ? c7 53 7d bc 06 ?f7 c0 b3 3a?28 8e 56 1e d7S}..... .:>(?
14:22:29.5024| ? ? a0 be 9 ? ? |....
14:22:29.5038--- 5 me???s dred ---
14:22:29.5200|[00:00??653,648] <?f> b?i_c? HW Platform: N??dic SemicondReceived kdp CRC
bad packet crc 0x1a0681f != 0x30282072
?essadropped ---
14:22:29.5545|00:00:??3,6?[0m<in bt_hci_co?rmwareStandard Blth c???oller (0x00) Version.32083 Build5153724
14:22:29.5572|-- mes???s dropp?d ---
14:22:29.5741|m[00:00:11.?53,9?<inf> bt_h??_coro Iress. p mu@ call ??ings?d()
14:22:29.5743|uart:~$ 8x8-- 4ssagdropped ---
14:22:29.5911|?00:11.653,927] m<in?le:???tooitialized
```
