英文:
ESP-IDF monitor outputting garbage symbols
问题
I have an ESP32-WROVER devkit which I've been using on and off for a few hobby projects.
我有一个ESP32-WROVER开发套件，我一直在偶尔使用它进行一些业余项目。
I've got an IDF clone and am using VSCode with the ESP-IDF extension.
我有一个IDF克隆版本，并且在VSCode中使用ESP-IDF扩展。
Today, I suddenly started getting garbage symbols on the monitor, which I was relying on to debug.
今天，突然间我开始在监视器上看到垃圾符号，我原本依赖它来进行调试。
Naturally, I assume it's a UART issue, but I'm uncertain where to go to check the setup.
自然而然，我认为这是一个UART问题，但我不确定应该去哪里检查设置。
I am quite unfamiliar with the settings.
我对这些设置不太熟悉。
I'm using git, so I tried to see if any of the sdkconfig.defaults changed like CONFIG_ESP_CONSOLE_UART_BAUDRATE.
我使用git，所以我尝试查看是否有任何sdkconfig.defaults文件的更改，比如CONFIG_ESP_CONSOLE_UART_BAUDRATE。
My assumption is that something changed in the IDF setup.
我猜测IDF设置中有些东西发生了变化。
(edit):
Solved.
I used Termite to connect to the COM port at 115200 baud, and the output was sensible. After some puzzling around, I found that the VScode ESP-IDF extension controls the monitor baud rate if you're using the command palette. Under Settings > Extensions > ESP-IDF > Idf : Monitor Baud Rate
I'm still confused as to how this setting was changed without my input, it literally happened overnight. Oh well...
已解决。
我使用Termite连接到COM端口，波特率为115200，输出结果是合理的。在经过一番研究后，我发现如果你使用命令面板，VScode ESP-IDF扩展可以控制监视器的波特率。在“设置”>“扩展”>“ESP-IDF”>“Idf : Monitor Baud Rate”下。
我仍然对这个设置如何在没有我的输入的情况下发生改变感到困惑，它真的是在一夜之间发生的。嗯，无所谓了...
英文:
I have an ESP32-WROVER devkit which I've been using on and off for a few hobby projects.
I've got an IDF clone and am using VSCode with the ESP-IDF extension.
Today, I suddenly started getting garbage symbols on the monitor, which I was relying on to debug.
Looks like so:
xx�xx��������x������x�����xx�x�xx�x�������x�x�x��x��x���xxxx����������������������������x�����x�x���x��x���x��xx��xxxx�x��x�xx��xxx�xxxx�xx�x�x��x���x�����x��xxx�xx�xx�xxxx��xx�x�xx�x�x�xx�xx��x�x�x�x
Naturally, I assume it's a UART issue, but I'm uncertain where to go to check the setup.
I am quite unfamiliar with the settings.
I'm using git, so I tried to see if any of the sdkconfig.defaults changed like CONFIG_ESP_CONSOLE_UART_BAUDRATE.
My assumtion is that something changed in the IDF setup.
(edit):
Solved.
I used Termite to connect to the COM port at 115200 baud, and the output was sensible. After some puzzling around, I found that the VScode ESP-IDF extension controls the monitor baud rate if you're using the command palette. Under Settings > Extensions > ESP-IDF > Idf : Monitor Baud Rate
I'm still confused as to how this setting was changed without my input, it literally happened over-night. Oh well...
答案1
得分: 2
我认为vscode扩展版本v1.6.2导致了这个错误。它最近发布并且可能自动更新了。它忽略了关于监视波特率的所有设置，并将其覆盖为460800。
降级到先前的版本应该可以解决这个问题。
打开espressif扩展页面。如果您点击卸载旁边的箭头，您将看到"安装另一个版本"，选择v1.6.1。
英文:
I think vscode extension version v1.6.2 causes this error. It released recently and probably auto updated.
It ignores all settings about monitor baudrate and override it to 460800.
Downgrade to previous version should fix this issue.
Open espressif extension page. You will see "install another version" if you click arrow next to uninstall. choose v1.6.1
答案2
得分: 1
"对于 v1.6.2，我必须在 settings.json 中添加 'idf.monitorBaudRate': '115200'，然后重新构建项目。然后监视器再次正常工作。"
英文:
For v1.6.2 I had to add "idf.monitorBaudRate": "115200", in settings.json and then rebuild the project. Then the monitor worked fine again.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论