Remove ITM from NRF52_DK and DELTA_DFBM_NQ620 targets

The NRF52_DK and DELTA_DFBM_NQ620 have the SWO pin (p0_18) mapped to
LED2. This means that on startup LED2 turns on after the ITM is
initialized which is confusing. Since most users want LED2 usage
instead of SWO we remove the ITM for these targets.

The nRF52 readme is updated to instruct users how to get SWO support
if they need it.
pull/9767/head
RFulchiero 2019-02-19 15:20:36 -06:00
parent 400fd82972
commit 5fb5a4a414
2 changed files with 14 additions and 2 deletions

View File

@ -153,6 +153,16 @@ The assert handler is defined in mbed-os/features/FEATURE_BLE/targets/TARGET_NOR
* It is not possible to do an asynchronous write from flash and receive non-asynchronously at the same time since the non-asynchronous receive buffer is being used as the temporary transmission buffer.
* The driver will flush the DMA buffer after a configurable timeout. During this process the UART will be halted and therefor unable to receive data. Hardware flow control should be enabled to avoid missing any data during this window.
#### Serial Wire Output (SWO)
On the nRF52832 pin 18 (p18 or p0_18) is the SWO pin and a GPIO pin. On the nRF52_DK and DELTA_DFBM_NQ620 targets p18 is also mapped to LED2, so the ITM has been removed from these targets to avoid contention. If you need SWO capability instead of LED2, add the ITM through ```mbed_app.json```:
```
"target_overrides": {
"*": {
"target.device_has_add": ["ITM"]
}
}
```
## SoftDevice

View File

@ -6791,7 +6791,8 @@
"device_name": "nRF52832_xxAA",
"macros_add": [
"WSF_MAX_HANDLERS=10"
]
],
"device_has_remove": ["ITM"]
},
"SDT52832B": {
"inherits": ["MCU_NRF52832"],
@ -6835,7 +6836,8 @@
"supported_form_factors": ["ARDUINO"],
"inherits": ["MCU_NRF52832"],
"release_versions": ["5"],
"device_name": "nRF52832_xxAA"
"device_name": "nRF52832_xxAA",
"device_has_remove": ["ITM"]
},
"MCU_NRF52840": {
"inherits": ["Target"],