仅当我手动启动gdbserver时,VISUAL STUDIO 2019 ARM嵌入式调试才会启动

如何解决仅当我手动启动gdbserver时,VISUAL STUDIO 2019 ARM嵌入式调试才会启动

我很惊讶Microsoft的家伙如何在简单的事实中搞砸这一点。

    {
      "type": "cppdbg","name": "stlink-openOCD-GCEG-FW.elf","project": "C:\\Users\\Piotr\\git\\gPIMS-EG\\out\\build\\IoT-Debug\\GCEG-FW.elf","projectTarget": "","cwd": "C:\\Users\\Piotr\\git\\gPIMS-EG","program": "C:\\Users\\Piotr\\git\\gPIMS-EG\\out\\build\\IoT-Debug\\GCEG-FW.elf","MIMode": "gdb","externalConsole": true,"inheritEnvironments": [
        "gcc_arm"
      ],"miDebuggerPath": "C:\\Program Files (x86)\\Atollic\\TrueSTUDIO for STM32 9.3.0\\ARMTools\\bin\\arm-atollic-eabi-gdb.exe","setupCommands": [
        {
          "text": "-file-exec-and-symbols C:/Users/Piotr/git/gPIMS-EG/out/build/IoT-Debug/GCEG-FW.elf","description": "load file","ignoreFailures": false
        },{
          "text": "-interpreter-exec console \"monitor reset halt\"",{
          "text": "-target-download","description": "flash target","ignoreFailures": false
        }
      ],"visualizerFile": "","showDisplayString": true,"miDebuggerServerAddress": "localhost:3333","launchCompleteCommand": "None","debugServerPath": "C:\\openocd-0.10.0\\bin-x64\\openocd.exe","debugServerArgs": "-f board\\st_nucleo_l476rg.cfg","serverStarted": "stm32l4x.cpu: hardware has 6 breakpoints,4 watchpoints","filterStderr": true,"filterStdout": true
    }
  ]
}

在这种情况下,运行gdbserver(openOCD)-但将其设置为奇怪的模式。例如,它认为目标不支持监视命令。

enter image description here

删除"miDebuggerServerAddress": "localhost:3333",后,它将停止运行openOCD。对于实验,我可以手动启动它,并从CLI发送相同的MI命令,一切正常。

C:\openocd-0.10.0\bin-x64>"C:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.3.0\ARMTools\bin\arm-atollic-eabi-gdb.exe" --interpreter=mi
=thread-group-added,id="i1"
~"GNU gdb (GNU Tools for ARM Embedded Processors (Build 17.03)) 7.10.1.20160923-cvs\n"
~"Copyright (C) 2015 Free Software Foundation,Inc.\n"
~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY,to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
~"This GDB was configured as \"--host=i686-w64-mingw32 --target=arm-atollic-eabi\".\nType \"show configuration\" for configuration details."
~"\nFor bug reporting instructions,please see:\n"
~"<http://www.gnu.org/software/gdb/bugs/>.\n"
~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
~"For help,type \"help\".\n"
~"Type \"apropos word\" to search for commands related to \"word\".\n"
(gdb)
-target-select remote localhost:3333
=thread-group-started,id="i1",pid="42000"
=thread-created,id="1",group-id="i1"
~"0x08027f7c in ?? ()\n"
*stopped,frame={addr="0x08027f7c",func="??",args=[]},thread-id="1",stopped-threads="all"
^connected
(gdb)
-file-exec-and-symbols C:/Users/Piotr/git/gPIMS-EG/out/build/IoT-Debug/GCEG-FW.elf
^done
(gdb)
-interpreter-exec console "monitor reset halt"
@"Unable to match requested speed 500 kHz,using 480 kHz\n"
@"Unable to match requested speed 500 kHz,using 480 kHz\n"
@"adapter speed: 480 kHz\n"
@"target halted due to debug-request,current mode: Thread \n"
@"xPSR: 0x01000000 pc: 0x08027f7c msp: 0x20018000\n"
^done
(gdb)

谁能告诉我Microsoft在认为目标不支持监视命令的模式下执行gdb的操作。使用gdb表单命令行时,我什至无法重现此行为(我已经尝试了很多次)。当我手动启动openOCD时,具有如下所示配置的VS可以正常工作。

问题:在没有手动启动openOCD的情况下如何从VS对其进行调试?

    {
      "type": "cppdbg","setupCommands": [
        {
          "text": "-target-select remote localhost:3333","description": "connect to target",{
          "text": "-file-exec-and-symbols C:/Users/Piotr/git/gPIMS-EG/out/build/IoT-Debug/GCEG-FW.elf","filterStdout": true
    }
  ]
}

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-