Hello Dialog, I have a very odd problem. I have had some new boards made and the pin connections for the programming
interface are the same as the IOTMSK kit. Specifically, all of the lines going to the 10 pin connector which connects to the
CIB板连接到相同的处理器引脚（DA14585），如IOTMSK套件的原理图所示。
我能够使用JTAG或UART在SmartSnippets Studio中进入SmartSnippets工具箱，然后
from within the toolbox program and load a compiled hex file using the Booter option into Sysram. This works as noted
using either the JTAG or UART ONLY options. So it looks like the Toolbox can at least load code into sysram of my
new boards using either JTAG or UART. Now the problem is that I have been using the Eclipse compiler to develop
code and when I try to run the Eclipse debugger with my new boards attached I would expect that Eclipse would just
program the sysram as it does for the IOTMSK board when starting the debugger, but it doesnt. The debugger crashes
使用此消息：
J-Link GDB服务器失败：无法连接到目标。请检查目标是否有动力，如果带有丝带电缆已正确插入
For more details, see the JLinkGDBServerCL.exe console.
这显然给我的印象是如此mething wrong with my connection but as noted it should be the same
as what is on the IOTMSK. I am out of ideas as to what might be causing this. Any ideas? Is there something I need
为准备这些新芯片以与Eclipse调试器接口？我难过。任何帮助都是
appreciated. Craig
Hi Craig Flanagan,
Apologies but I am a little bit confused with your question, so I need some clarifications in order to understand your issue. Are you using the DA14585 IoT Multi-Sensor hardware or you have designed a custom board based on our reference design? Did you follow the AN-B-064 document?
//www.wsdof.com/sites/default/files/an-b-064_da14585_iot_sensors_reference_application_with_eclipsegcc.pdf
Also, when using the SmartSnippets toolbox you are not able to download the firmware into the System-RAM, so I supposes that you burnt the SPI flash, is that correct?
Thanks, PM_Dialog
对不起，我不清楚，让我试着做得更好
1. I did follow the AN-B-064 in setting up the Eclipse IDE to work with my DA14585 IOTMSK board/kit. It works fine.
2.我可以使用DA14585 Iotmsk套件/板在Eclipse中编译和调试精细，我一直在使用此配置
现在几周没有问题。
3. I created a custom board. This custom board has a DA14585 processor and includes the equivalent 10 pin header as the
DA14585 IOTMSK kit/board and the same header connections to the processor (so I expected that it would work fine
使用Eclipse）。
4.当我从10个引脚带状电缆中卸下Iotmsk套件/板并将带状电缆连接到我的板，Eclipse调试器
不会加载，我收到以下错误：
J-Link GDB服务器失败：无法连接到目标。请检查目标是否有动力，如果带有丝带电缆已正确插入
For more details, see the JLinkGDBServerCL.exe console.
5. I suspected a hardware issue with my new board, so I checked all the pin connections and everything is fine. Further, I went into KEIL
(to test the custom board) and was able to load and debug the SMARTTAG application. I noted that the bluetooth communcations was
也从我的自定义板上工作到我的智能手机。因此，定制板硬件显然在keil中没有问题
environment.
6.以下是我的自定义板未能加载调试器后发布的jlink日志文件（我一直在查看但真的不知道如何解释）：
SEGGER J-Link GDB Server V6.14h LogFile
日志记录启动@ 2019-04-08 15:02
03-00000000-00-00000000-0023: -----GDB Server start settings-----
03-00000000-00-0000000000-0023：GDBINIT文件：无
03-00000000-00-00000000-0023: GDB Server Listening port: 2331
03-00000000-00-0000000000-0023：SWO原始输出聆听端口：2332
03-00000000-00-00000000-0023: Terminal I/O port: 2333
03-00000000-00-00000000-002D: Accept remote connection: localhost only
03-00000000-00-00000000-0021: Generate logfile: on
03-00000000-00-00000000-0021：验证下载：开
03-00000000-00-00000000-0021: Init regs on start: on
03-00000000-00-00000000-0022: Silent mode: off
03-0000000000-00-0000000000-0021：单次运行模式：ON
03-00000000-00-0000000000-0023：目标连接超时：0毫秒
03-00000000-00-00000002-0023: ------J-Link related settings------
03-00000000-00-00000002-0022: J-Link Host interface: USB
03-0000000000-00-00000002-0023：J-Link脚本：无
03-00000000-00-00000002-0023: J-Link settings file: none
03-00000000-00-00000002-0023: ------Target related settings------
03-0000000000-00-00000002-0028：目标设备：Cortex-M0
03-00000000-00-00000002-0022：目标接口：SWD
03-0000000000-00-00000002-0026：目标接口速度：8000kHz
03-0000000000-00-0000000002-0025：目标endian：很少
03-00000000-00-00000003-0017: Connecting to J-Link...
02-00000000-00-00000011-003D: Firmware: J-Link OB-SAM3U128 V3 compiled Jan 7 2019 14:06:26
02-00000000-00-00000011-000F：硬件：v3.00
02-00000000-00-00000011-000E: S/N: 483031254
02-0000000000-00-00000021-0052：功能：RDIWebSRV WebServer在本地端口19080上运行（0018ms，总计0018ms）
02-00000000-00-00000021-0033: T28CC 000:007 returns O.K. (0018ms, 0018ms total)
03-00000000-00-00000021-0014: J-Link is connected.
02 - 00000000 - 00 - 00000000 - 00 - b3: T28CC 000:026 JLINK_ExecCommand("device = Cortex-M0", ...). C:\Program Files (x86)\SEGGER\JLink_V614h\JLinkDevices.xml evaluated successfully. returns 0x00 (0191ms, 0209ms total)
02-00000000-00-00000214-006A: T28CC 000:218 JLINK_ExecCommand("SetFlashRewriteBehavior = 1", ...). returns 0x00 (0000ms, 0210ms total)
02-0000000000-00-00-00000214-0041：T28CC 000：218 JLink_GetFirmwarestring（...）（总计0210ms）
03-00000000-00-00000214-003D: Firmware: J-Link OB-SAM3U128 V3 compiled Jan 7 2019 14:06:26
02-0000000000-00-00-00000214-004F：T28CC 000：218 JLink_Gethardwareversion（）返回0x7530（0000ms，总计0210ms）
03-0000000000-00-00000214-000F：硬件：v3.00
03-0000000000-00-00000215-000E：S / N：483031254
03-00000000-00-00000215-000F：功能：RDI
02-00000000-00-00-00000215-0049：T28CC 000：219 JLink_Gethwstatus（...）返回0x00（0000ms，总计0210ms）
02-00000000-00-00-00000215-003C：T28CC 000：219 JLink_EnablyBPS（ON）（0000ms，总计0210ms）
03-0000000000-00-00000215-001A：检查目标电压...
03-00000000-00-00000216-0016: Target voltage: 3.30 V
03-0000000000-00-00000216-001D：聆听TCP / IP端口2331
03-00000000-00-00000216-0017: Connecting to target...
02-00000000-00-00000216-0035: T28CC 000:220 JLINK_ClrError() (0000ms, 0210ms total)
02-00000000-00-00000216-0049: T28CC 000:220 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0210ms total)
02-00000000-00-00000217-0055: T28CC 000:220 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0001ms, 0211ms total)
02-00000000-00-00-00000217-0039：T28CC 000：221 JLink_setspeed（8000）（0000ms，总计0211ms）
02-00000000-00-00000217-0044: T28CC 000:221 JLINK_GetSpeed() returns 0xA6B (0000ms, 0211ms total)
02-00000000-00-00000217-0077: T28CC 000:221 JLINK_SetResetType(JLINKARM_RESET_TYPE_NORMAL) returns JLINKARM_RESET_TYPE_NORMAL (0000ms, 0211ms total)
02-00000000-00-00000217-003B: T28CC 000:221 JLINK_SetResetDelay(0) (0000ms, 0211ms total)
02-00000000-00-00000217-0055: T28CC 000:221 JLINK_SetEndian(ARM_ENDIAN_LITTLE) returns 0x00 (0000ms, 0211ms total)
02-00000000-00-00000226-01FC: T28CC 000:221 JLINK_Connect() >0x10B TIF>Found SW-DP with ID 0x0BB11477 >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x30 TIF> >0x0D TIF> >0x28 TIF>No AP preselected. Assuming that AP[0] is the AHB-AP >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x30 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF>
02-00000000-00-00000234-01FA: >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF>
02-0000000000-00-00-0000024-01FA：> 0x21 tif >>>>>> 0x21 tif >>> 0x0d tif >>>> 0x21 tif >>>> 0x0d tif >> 0x21 tif >> 0x0d tif >>> 0x21 tif >> 0x0d tif >>> 0x21 tif >>>>> 0x21 tif >>>>> 0x0d tif >> 0x0d tif >>> 0x21 tif >> 0x0d tif >>>>>21 tif >> 0x0d tif >>>>>>>>>>>>>>>>>TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 0x0D TIF >> 0x21 TIF >>>>> 0x0d TIF >> 0x21 TIF >> 0x0x0d TIF >>>>>>>>>>>>> 0x0D TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
02-00000000-00-00000252-01FA: >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF>
02-0000000000-00-00000261-01FA：> 0x21 TIF >>>> 0x0D TIF >>>>> 0x0D TIF >> 0x21 TIF >>> 0x0D TIF >>>>> 0x21 TIF >> 0x0D TIF >>> 0x21 TIF >>>>>>>> 0x21 tif >>>>> 0x21 tif >>>>> 0x0d tif >> 0x0d tif >>> 0x21 tif >> 0x0d tif >>>>>21 tif >> 0x0d tif >>>>>>>>>>>>>>>>>TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 0x0D TIF >> 0x21 TIF >>>>> 0x0d TIF >> 0x21 TIF >> 0x0x0d TIF >>>>>>>>>>>>> 0x0D TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
02-0000000000-00-00-00000269-01FA：> 0x21 TIF >>>>>>>>>>>>>> 0x0D TIF >> 0x21 TIF >> 0x0D TIF >>>>> 0x21 TIF >> 0x0d TIF >>>>>>>>>>>>>>>>>> 0x21 tif >>>>> 0x21 tif >>>>> 0x0d tif >> 0x0d tif >>> 0x21 tif >> 0x0d tif >>>>>21 tif >> 0x0d tif >>>>>>>>>>>>>>>>>TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 0x0D TIF >> 0x21 TIF >>>>> 0x0d TIF >> 0x21 TIF >> 0x0x0d TIF >>>>>>>>>>>>> 0x0D TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
02-00000000-00-00000277-01FA: >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF>
02-00000000-00-00000285-01FA: >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF>
02-0000000000-00-00000293-01FA：> 0x21 TIF >>>>>>>>>>>>> 0x0D TIF >>>>> 0x21 TIF >> 0x0D TIF >>>> 0x21 TIF >> 0x0D TIF >> 0x21 TIF>> 0x0d TIF >>> 0x21 tif >>>>> 0x21 tif >>>>> 0x0d tif >> 0x0d tif >>> 0x21 tif >> 0x0d tif >>>>>21 tif >> 0x0d tif >>>>>>>>>>>>>>>>>TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 0x0D TIF >> 0x21 TIF >>>>> 0x0d TIF >> 0x21 TIF >> 0x0x0d TIF >>>>>>>>>>>>> 0x0D TIF >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
02-00000000-00-00000296-00EC: >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF>Could not power-up debug power domain. >0x0D TIF> >0x0D TIF> >0x0D TIF> >0x0D TIF> >0x0D TIF>
02-00000000-00-00000350-0109: ***** Error: DAP error while reading AHB-AP IDR. >0x10B TIF>Found SW-DP with ID 0x0BB11477 >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x30 TIF> >0x0D TIF> >0x28 TIF>No AP preselected. Assuming that AP[0] is the AHB-AP >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x30 TIF> >0x0D TIF>
02-0000000000-00-00-00000353-0113：> 0x28 tif >>>>>>> 0x21 tif >>>> 0x0d tif >>> 0x28 tif >>>> 0x0d tif >>> 0x30 tif> >> 0x0d tif >> 0x28 tif >> 0x0d tif>> 0x30 tif >>>>>> 0x tif >>>> 0x21 tif >>>>> 0x0d tif >>>>>21 tif> AP-IDR：0x00030003，类型：自定义AP（未知）返回0xFFFFFEFB（0136ms，总计0.136ms，0347ms，总计0347ms）
03-00000000-00-00000353-002A: ERROR: DAP error while reading AHB-AP IDR.
03-00000000-00-00000353-0023：错误：无法连接到目标。
03-00000000-00-00000353-0035：目标连接失败。GDBSERVER将关闭......
03-0000000000-00-00000365-0037：恢复目标状态和关闭J-Link连接...
02-00000000-00-00000365-0041: T28CC 000:369 JLINK_IsOpen() returns 0x01 (0000ms, 0347ms total)
02-00000000-00-0000000365-0058：T28CC 000：369 JLink_ExecCommand（“Clrallbps”，......）。返回0x00（总计000ms，0347ms）
03-0000000000-00-00000398-0010：关闭...
7. At this point, given that my custom board works in the KEIL IDE but wont work in Eclipse per the attached log file, I am baffled. Any thoughts would be helpful.
克雷格
PROBLEM SOLVED (I BELIEVE)
I suspected a download speed issue. So within Eclipse I selected "run" then "debug configurations" then in the left
面板双击GDB Segger J-Link调试，然后在右侧选择Debugger选项卡然后设置
the initial speed to something less than the 8k it is set to. I selected 1000 khz. Now recompile and debug and
调试器不会再次为您提供错误消息....
Hi Craig Flanagan,
So, you figured your issue out, didn’t you? Thanks for your indication! Do you need any other support on that?
Thanks. PM_Dialog
Im good thanks.