Click to access Hershberger_QEX_11_14.pdf

Photo #1

Bluetooth 5 CW Keyer.

Power not shown

Arduino Files: https://github.com/bobh/nimBLE-discrete-xfer/tree/main/nimbleDiscrete

Dave Graham’s: ESP32 Based CW Filter and Signal Display

https://1drv.ms/u/s!AhrXOA_g9S-oZ_6-DLVcz7n359g?e=3zAgA1

Bluetooth 5 is transferring CW with no latency or jitter.

Adding In-Circuit debugging to the ESP32-C3 Dev Kit.

Using an old USB cable/breakout I had lying around. You’ll probably want to use USB-C. 😉

Attach nothing to the Dev Kit USB connector.

Also, I use a lot of power and grounds.

Link: https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/api-guides/usb-serial-jtag-console.html

Debugging (at a break point) in VSCode on Ubuntu.

NOTES:

> The ESP32-C3 is said to be the successor to the ESP-8266. And like the 8266 is limited in Programmable IO compared with the ESP-32. This USB method of In-Circuit debugging uses two processor PIO pins instead of the four pins needed for JTAG debugging–freeing up two pins for general use.

> In the processor’s low power modes, the USB interface is powered down and USB debugging is not possible. If you need to debug while in one of the two low power modes, you should use the JTAG interface.

> Visual Studio Code operates at the source code level and is able to use this method of debugging to set breakpoints, examine variables and the stack, single-step high level source code and flash the device. But VSCode has no knowledge of the processor details (e.g. CPU internal registers, memory configuration–access and format). As a result single-stepping through assembly code while examining CPU registers, flags and memory is not possible.
But the detailed knowledge gained while single-stepping assembly code would be an advantage in learning the ESP32-C3’s risc-v architecture. VSCode teamed with PlatformIO could provide this capability and I have filed an issue to that purpose on PlatformIO’s github. https://github.com/platformio/platform-espressif32/issues/651