http://lpccs-docs.dialog-semiconductor.com/um-b-090-da1469x_getting_started/07_Your%20First%20DA1469x%20Application%20%E2%80%93%20Advertising%20Demo/Your%20First%20DA1469x%20Application%20%E2%80%93%20Advertising%20Demo.html#build-调试qspi配置中的建议步骤1：我使用调试qspi构建配置构建二进制文件
步骤2：我使用run->；外部工具->；program_qspi_jtag并获得以下输出。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。编程图像cli_编程器1.26版权所有（c）2015-2019对话框半导体引导加载程序文件未指定，使用内部uartboot.bin然后它将永远挂起
方法2:
然后我尝试使用直接受以下启发的命令行工具：SDK_10.0.4.66.2/doc/html/cli_programmer.html
我找不到任何关于GDB服务器的文档仪表（是否有我找不到的文件？）但是我从SmartSnippets调用中获取了参数并按如下方式启动了gdbserver:
GDB服务器输出：
JLink_Linux_V644i_x86_64//JLinkGDBServer-if-swd-device Cortex-M33-endian little-speed 8000-port 2331-swort 2332-telnetport-vd-ir-localhostonly 1-log JLink.log-singlerun-strict-timeout 0-nogui-rtos GDBServer/RTOSPlugin_FreeRTOS SEGGER J-Link GDB Server V6.44i命令行版本JLinkARM.dll V6.44i（dll于2019年5月17日17:37:26编译）命令行：-if swd-device Cortex-M33-endian little-speed 8000-port 2331-swoport 2332-telnetport 2333-vd-ir-localhostonly 1-log jlink.log-singlerun-strict-timeout 0-nogui-rtos GDBServer/RTOSPlugin FreeRTOS------GDB服务器启动设置------GDBInit文件：无GDB服务器侦听端口：2331 SWO原始输出侦听端口：2332 Te终端I/O端口：2333接受远程连接：仅本地主机生成日志文件：on验证下载：on Init regs on启动：on静默模式：off单次运行模式：on Target连接超时：0 ms------J-Link相关设置------J-Link主机接口：USB J-Link脚本：none J-Link设置文件：none------目标相关设置------Target设备：Cortex-M33目标接口：SWD目标接口速度：8000kHz目标端：很少连接到J-Link…J-Link已连接。固件：J-Link OB-SAM3U128 V3编译2019年1月7日14:06:26硬件：V3.00序列号：483051972检查目标电压…目标电压：3.30 V侦听连接到目标的TCP/IP端口2331…连接到t目标正在雷竞技电竞平台等待GDB连接…连接到127.0.0.1收到的监视器命令：clrbp收到的监视器命令：重置0 Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Received monitor command: sleep 10 Sleep 10ms Received monitor command: halt Halting target CPU... ...Target halted (PC = 0x0000076C) Received monitor command: memU32 0x20010000 = 0xdeadbeef Writing 0xDEADBEEF @ address 0x20010000 Received monitor command: memU32 0x20010004 = 0xdeadbeef Writing 0xDEADBEEF @ address 0x20010004 Received monitor command: memU32 0x20010008 = 0xdeadbeef Writing 0xDEADBEEF @ address 0x20010008 Received monitor command: memU32 0x2001000c = 0xdead10cc Writing 0xDEAD10CC @ address 0x2001000C Downloading 4 bytes @ address 0x100C0050 - Verify failed Received monitor command: sleep 100 Sleep 100ms Received monitor command: reset 0 Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Received monitor command: sleep 1 Sleep 1ms Received monitor command: halt Halting target CPU... ...Target halted (PC = 0x200010CA) Downloading 2 bytes @ address 0x50000024 - Verified OK Received monitor command: loadbin /tmp/cli_programmer_IDqXYy, 0x00000000 Loading binary file [/tmp/cli_programmer_IDqXYy] ... Downloading 30484 bytes @ address 0x00000000 - Verified OK Binary file loaded successfully (30484 bytes downloaded) Received monitor command: reset 0 Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Received monitor command: go Starting target CPU... Received monitor command: reset 0 Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Received monitor command: halt Halting target CPU... ...Target halted (PC = 0x0000076C) Downloading 1 bytes @ address 0x00000218 - Verified OK Performing single step... ...Target halted (Vector catch, PC = 0x0000076E) Starting target CPU...
cli_programmer output:
SDK_10.0.4.66.2/binaries$ ./cli_programmer gdbserver 0x0 ../projects/dk_apps/demos/pxp_reporter/DA1469x-00-Debug_QSPI/pxp_reporter.bin cli_programmer 1.26 Copyright (c) 2015-2019 Dialog Semiconductor bootloader file not specified, using internal uartboot.bin Uploading boot loader/application executable... Executable uploaded.
Then it hangs forever