Hi,
I've done multiple designs with the DA14531 using a different debugger / programmer (DA14531 EVK). However, this time I need 1.8V capability and my existing debugger won't do that. So I got a segger J-Link Base debugger / programmer and the 6-pin adapter for tag connect: https://www.segger.com/products/debug…needle-adapter/
My main problem is being able to detect the device (from Keil MDK). See attached error message. See attached relevant schematic for my board.
Nothing else is connected to RST (I have disconnected CHG-STOP connection to another part of the circuit - it was not the problem). I have also ohm'd out the connections between the j-link base debugger 20-pin header and the DA14531 MOD pins SWDIO, SWCLK, RST, and VTREF. So, there is no wiring mistake, pin connections are correct.
There is nothing else connected to SWDIO.
There is a level translator input (A) connected to SWDCLK (see schematic), but I can't see how that would make a difference. I can try and disconnect it if you think it would be useful.
I have scoped the signals SWDIO, SWDCLK and RST while DA14531 is connected. I see some valid-looking data at SWDIO, but nothing at SWDCLK other than constant 0.36V (same as RST, nothing but 0.36V). To me it looks like j-link base assumes RST is active low, but DA14531 is active high (and pulled down internally with 25kOhm). This is why the orange light is lit.
When I disconnect DA14531 and scope the signals SWDIO, SWDCLK and RST at the J-link 20pin header, the signal RST will go low and just before that there is some valid looking data on SWDIO and clocks on SWDCLK. I feel like the issue has to do with RST (active high vs active low).
One time I did get a connection using segger commander and it looked like this:
DLL version V6.40, compiled Oct 26 2018 15:06:02
Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Sep 22 2022 14:53:28
Hardware version: V11.00
S/N: 51025885
License(s): GDB
VTref=1.806V
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: CORTEX-M0
Type '?' for selection dialog
Device>connect CORTEX-M0
Please specify target interface:
J) JTAG (Default)
S) SWD
F) FINE
I) ICSP
C) C2
T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "CORTEX-M0+" selected.
Connecting to target via SWD
Found SW-DP with ID 0x0BC11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770031)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB008 SCS
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB00B FPB
Cortex-M0 identified.But I can't seem to get a connection anymore through commander, and certainly have never got connection through keil. Any ideas what could be the issue here? I've been stuck for days
Thank you!
Erik