Power management on Direct Test Mode netcore

Hi,

DTM is an implementation based on the specification from the bluetooth core specification, and its purpose is to test the RF PHY.

It is not made to be optimized for runtime current consumption.

Could I ask why you're using DTM as a base to create a low-power application?

Kind regards,

Håkon

We are trying to test the radio of the nrf5340 chip in an evaluation set-up that will be embedded in a small, enclosed space with no possibility of adding wires to the design. There will be a battery in this set-up that can be charged wirelessly, but it would still be very helpful if we could reduce the power consumption while the device is not receiving or transmitting DTM packets.

We are trying to test the radio of the nrf5340 chip in an evaluation set-up that will be embedded in a small, enclosed space with no possibility of adding wires to the design. There will be a battery in this set-up that can be charged wirelessly, but it would still be very helpful if we could reduce the power consumption while the device is not receiving or transmitting DTM packets.

Hi,

DTM requires both physical access (its a 2-wire interface, essentially normal UART at 19k2 baud), and will also require that this is active at all times, thus causing a sleep current of approx. 700-900 uA (depends on clock configuration: https://infocenter.nordicsemi.com/topic/ps_nrf5340/chapters/current_consumption/doc/current_consumption.html?cp=3_0_0_3_3_0_20#unique_1916708250).

It really does sound like you do not want to base your application upon this firmware. As mentioned, the only use-case is to evaluate the RF PHY, not perform application related communication.

Kind regards,

Håkon