Issues with using JLink on custom DA14580 board

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
6 posts / 0 new
Last post
tsgowtham
Offline
Last seen: 10 months 3 weeks ago
Joined: 2020-05-04 12:39
Issues with using JLink on custom DA14580 board

Hi,

I have 2 custom DA14580 boards and am facing an issue while trying to debug with Keil. When I go to the debug settings and press scan, initially it detecct to show the cortex m0. But then after few seconds it would not detect it. Currently, it's unable to detect the m0 even for a short duration. 

The debugger gives 2.8V at the DA14580's VBAT. 

Any methods on how I could debug this issue or what could cause this?

Thanks

Keywords: 
Device: 
PM_Dialog
Offline
Last seen: 15 hours 8 min ago
Staff
Joined: 2018-02-08 11:03
Hi tsgowtham,

Hi tsgowtham,

Could you please share more inputs for your setup? Are you using any of Dialog development board for the JTAG or you have an external JTAG interface? In the Keil, if you navigate to Options for target > Debug > Settings, are you able to detect your device? Is should be similar with the attached screenshots.

Thanks, PM_Dialog

Attachment: 
tsgowtham
Offline
Last seen: 10 months 3 weeks ago
Joined: 2020-05-04 12:39
Hi PM_Dialog,

Hi PM_Dialog,

I have an external JTAG interface, pretty sure the issue is not with this external interface.

The board has 1 mm pads onto which I have soldered some wires, which I have connected to the external JTAG interface. I have verified the working of the wires with a continuity test from the soldered pads to the external interface using a multimeter. Also, I'm using only the VBAT, GND, SWDIO and SWCLK pads. I'm not using the VPP or the reset pads.

I should have been a bit more clear by what I meant when I said the "m0 was not detected". I checked the same path to the debugger settings which you have mentioned. The "ARM CoreSight" was initially getting detected for a few seconds and then would disappear i.e. the SW Device box is blank. Now, when I tried it again, it doesn't detect it even once.

This has happened with 2 boards. 

PM_Dialog
Offline
Last seen: 15 hours 8 min ago
Staff
Joined: 2018-02-08 11:03
Hi tsgowtham,

Hi tsgowtham,

So, if I understood correctly this happens only in 2 custom boards. Can you replicate it in any other of your boards? Are you using the J-Link Lite? Do you have any of our development boards?

Thanks, PM_Dialog

tsgowtham
Offline
Last seen: 10 months 3 weeks ago
Joined: 2020-05-04 12:39
Hi,

Hi,

I have only 2 of these boards and will not be able to get anymore for the time being. I was actually using the JLink on a nRF52 devkit. I've used method before to debug, so I'm sure it's not a issue with the nRF52 devkit. I currently do not have a DA14580 devkit, but will be getting one soon.

 

PM_Dialog
Offline
Last seen: 15 hours 8 min ago
Staff
Joined: 2018-02-08 11:03
Hi tsgowtham,

Hi tsgowtham,

Here we can provide support only for Dialog products. You can program your custom board by using our development kit – I assume that you have ordered the Pro-DK. This can be done either via UART or the JTAG interface. Below are the required connections for each interface.

JTAG interface, the required connections are:

 J4 - Pin 1 (VBAT_580) - > Vcc of the custom board.

 J4 - Pin 25 (TMS) - > SWDIO pin of custom board.

 J4 - Pin 27 (TCK) - > SW_CLK pin of custom board.

 TP2 -> to the Vpp of the custom board (if OTP needs to be programmed).

 J4 - Pin 2 (GND) - > to the ground of the custom board.

UART interface, the required connections are:

J4 - UTX - > on the RX pin of the custom board.

J4 - URX - > on the TX pin of the custom board.

J4 - RST - > to the RST pin of the custom board.

J4 - VBAT_580 - > to the Vcc of the custom board.

 TP2 -> to the Vpp of the custom board (if OTP needs to be programmed).

Thanks, PM_Dialog