Debugger Disconnection Problem

⚠️
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//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
6 posts / 0 new
Last post
MarkDsylva_2277
Offline
Last seen:1 month 4 weeks ago
加入:2019-06-19 04:20
Debugger Disconnection Problem

Hello Dialog Team,

I am working on a custom made board for a project. I am using the DA14585-00ATDEVKT-P Development Kit - Pro for debugging and OTP. When I try to detect the DA14585 on my board using Keil, its detecting the device correctly. But when I start the debug session, I am getting 'Cannot Access Target' error and occasionally 'Cannot Access Memory' error and the debugging session fails. I have a doubt regarding how can debugging fail if keil is able to detect the chip.

Please note:

  • I am using the blinky project in the SDK folder and its working properly on the daughter board with DA14585 which is attached to the development kit.
  • I am removing the daughter board and I am using wire jumpers when I am working on my custom board

Regards,

Mark

Device:
PM_Dialog
Offline
Last seen:15 hours 29 min ago
工作人员
加入:2018-02-08 11:03
Hi Mark,

Hi Mark,

Can you please indicate if you have burnt the OTP? If yes, keep in mind that OTP stands for One Time Programmable, thus you can’t erase and re-write the OTP multiple times. Additionally, If the application flags are burned and the JTAG enable flag is Disabled in the OPT Header then the device becomes inaccessible which mean that you will not have access to JTAG. Please navigate into the Options for target > Debug > J-Link/J-Trace Cortex Settings and make sure that the SN and the SWD IDCODE are appeared in the window and press OK.

Thanks, PM_Dialog

MarkDsylva_2277
Offline
Last seen:1 month 4 weeks ago
加入:2019-06-19 04:20
Hi PM_Dialog,

Hi PM_Dialog,

I didnt do any OTP on the chip. I tried navigating to target > Debug > J-Link/J-Trace Cortex Settings. When I selected JTAG it doesnt show any IDCODE but SN code is visible. But when I select SW both codes are visible.

Regards,

Mark

MHv_Dialog
Offline
Last seen:1 month 1 day ago
工作人员
加入:2013-12-06 15:10
Hi Mark,

Hi Mark,

I suspect that your J-Link connection wires are too long. Could you please try to shorten the wires from the devkit to your board - 2-3inches max. Also, make sure that your ground wire is short (J5-2). Please also try to provide the supply from the devkit (J5-23).

The symptoms you observe could also be a result of building the project for the wrong target (not very likely - but for completeness). Please see the new SDK6"Getting Started" guide有关如何选择职业per SmartBond device in Keil (section 3.1).

/MHv

MarkDsylva_2277
Offline
Last seen:1 month 4 weeks ago
加入:2019-06-19 04:20
Hi MHv_Dialog,

Hi MHv_Dialog,

The J-link connection wires length are below 2-3 inches. The supply is also given through the dev kit.

I have also checked the target name and sdk. Everything is correct. But the debugging disconnection problem still persists. Please guide on how to solve this issue.

Regards,

Mark

MHv_Dialog
Offline
Last seen:1 month 1 day ago
工作人员
加入:2013-12-06 15:10
Hi Mark,

Hi Mark,

Please make sure that your connections matches those of thePrototype Bring-up Guide. Follow the instructions in this guide, and please also use the empty_peripheral_template guide as described in that tutorial.

/MHv