"idf.py -p /dev/ttyUSB0 monitor" Doesn't Work as Advertised with SparkFun Thing Plus - ESP32 WROOM

Development Boards ESP32
1

Apologies if this topic might already have been addressed, but I couldn’t find it in either SparkFun’s or Espressif’s user forums.

The serial comm monitor included with the ESP32 IDF (“idf.py -p /dev/ttyUSB0 monitor”) shows that the “Hello World” repeating-loop example builds, flashes and runs properly. I am able to stop the monitor with the “Ctlr+]” key press in PuTTY and the “Disconnect Terminal Connection” button in Eclipse. So far so good, as documented in https://docs.espressif.com/projects/esp … nitor.html.

However, the other “Ctrl+” key presses don’t cause anything to happen. That is, “Ctrl+T” doesn’t provide escape to the other commands, nor does “Ctrl+X” terminate the monitor. I observe this using both PuTTY and Eclipse terminal windows.

This seems strange. If “idf.py -p /dev/ttyUSB0 flash” is able to reset the Thing, get it to listen to its USB interface and make download happen, why can’t the monitor similarly interrupt the processing loop to examine and report internal Thing state?

Comments? Ideas?

Configuration:

SparkFun Thing Plus - ESP32 WROOM, version WRL-15663, connected to host via USB2.0

Unbuntu 20.04.1 LTS —> OS: Linux, v.5.4.0-42-generic, x86_64 / gtk 3.24.20, WebKit 2.28.4

ESP-IDF v4.3-dev-771-gc77c4ccf6

Eclipse IDE for C/C++ Developers (includes Incubating components), Version: 2020-06 (4.16.0), Build id: 20200615-1200

ESP-IDF Eclipse Plugin, version: 1.1.1.202006040612

Java version 11.0.8

2

MY MISTAKE! The monitor does work. I picked a poor example that obscured its function. The ESP32 IDF’s “hello world” example scrolls by so quickly that there is no time to see the response to the “Ctrl+T Ctrl+whatever” key presses. The “blink” example set to use GPIO13 (which flashes a blue L.E.D. on the Thing) runs slowly enough to allow human reaction. Sorry for the false alarm.