For emission testing, we need to be able to use some DTM commands (such as: transmitter test) inside our normal firmware.
The normal firmware uses the softdevice for BLE.
My idea is to use ble_dtm to enable transmitter test, when required.
Because our application usesTIMER1-TIMER4, and softdevice uses TIMER0, I'm having a resource problem with ble_dtm, which needs two timers.
I'm thinking to use the following aproach:
-disable the softdevice (so TIMER0 is free), just before calling dtm_init().
-configure dtm_init to use TIMER0
-comment all ANOMALY_172_TIMER usage (because I'm hoping our devices either won't suffer from anomaly 172, or if they do, it does not cause problems for a simple transmitter test)
My questions:
-Can ble_dtm be used with SOFTDEVICE_PRESENT (and softdevice disabled, after having been enabled before)
-Can ble_dtm safely use TIMER0 when the softdevice has been disabled? (after having been enabled before)
Or perhaps an alternative aproach; would it be possible to start a BLE transmitter test using the softdevice?
