That's a fairly large number. I was expecting some in the the couple hundreds of uA. I have multiple experiences of an enabled debug interface not being detected post production. This results in shorter then expected battery life. But I would think 3 mA would be easily detected. Additional thoughts?
At least after programming the consumption stays at 3mA.
If I only connect using SWDSelect in JLinkExe the consumption is 2.7mA.
Apparently this only sends the SWD switching sequence to power up the debug IF:
SEGGER J-Link Commander V6.40 (Compiled Oct 26 2018 15:06:29) DLL version V6.40, compiled Oct 26 2018 15:06:02
Connecting to J-Link via USB...O.K. Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41 Hardware version: V1.00 S/N: 682389160 VTref=3.300V
Type "connect" to establish a target connection, '?' for help J-Link>SWDSelect Select SWD by sending SWD switching sequence. Found SWD-DP with ID 0x2BA01477 J-Link>
