Custom board power measurment and programming configuration

RE: Custom board power measurment and programming configuration

Håkon Alseth — Wed, 26 Mar 2025 16:05:43 GMT

Hi,

It should not draw that much current. Try disconnecting pin-for-pin between the DK and custom-board to see if you can find the signal(s) that draw excessive current.

Kind regards,

Håkon

RE: Custom board power measurment and programming configuration

robsrick — Wed, 26 Mar 2025 15:55:46 GMT

I'm seeing about 5mA. So i gather from what you're saying the configuration in my diagram should be low power when debugging not active?

if that's the case i'll look elsewhere, maybe im getting some current leakage else where on the board.

RE: Custom board power measurment and programming configuration

Håkon Alseth — Wed, 26 Mar 2025 15:49:56 GMT

Hi,

How much added current are you seeing?

Could it be that you have a process that is continuously trying to connect to the debugger? An "nRF Terminal" instance in vscode?

Kind regards,

Håkon

RE: Custom board power measurment and programming configuration

robsrick — Wed, 26 Mar 2025 14:39:08 GMT

Hi Hakon

connected as in wired in not actively debugging.

regards

Robert

RE: Custom board power measurment and programming configuration

Håkon Alseth — Wed, 26 Mar 2025 14:27:15 GMT

Hi,

[quote user=""]Im noticing that when the debugger is connected (which is all the time in normal use) im drawing milliamps of extra power i think due to the debugger connection?[/quote]

Connected as in wired in, or connected as in used on the PC-side?

When a debug session is active, you will draw more current, as the debugger will force certain clock domains on, and you will see approx. 1.2 mA as your base sleep current.

Kind regards,

Håkon