ESP32 Forum

Hello there, I am completely new to this forum and ESP IDF and I am trying to understand the basics of IDF before I begin to work on a more sophisticated BLE project.

Some Configuration facts of my current setup:
IDE: VScode
OS: Windows 11
"idf.py --version" is v1.0.3
Component config -> ESP System Settings -> Channel for console output is "USB Serial/JTAG Controller"
baud: 115200
Component config -> Application Level Tracing -> Data Destination 2 is "USB_CDC" -- I feel my issue lies here, as in I do not think this is enabling "CDC on Boot" (not quite sure what that is)

(please do ask for more if needed, I am not exactly sure what is needed for this)

------------------------------------

What am I trying to accomplish (i.e. learn):
1. How to use UART for "uart_read_bytes" and "uart_write_bytes" in an echo-task type format
2. How to read user input using "fgets" or some other 'built in' function such as "getchar" (in such a format that the monitor "waits" for input), in a fashion similar to the console using "printf" to prompt user for data and then waiting for user input.

*those two things are not the same, but I feel that as long as I can do one of them, I can figure the other out on my own. My question here is focused on the first task and we can ignore second thing

-------------------------------------

Currently I tried following the UART echo example and came up with the following program:
I end up having the following issue (this is in the IDF monitor):
In addition, I have included an attachment of my circuit setup in case something is wrong there (to explain it, there is a simple LED hooked up on GPIO_NUM_2, and a random pin connector from pin number 9 to GND, which I read about being some sort of solution for something...)
My question: how do I make it so that I can begin writing (perhaps on PuTTY) and seeing the "ESP_LOGI" messages on the monitor? If anything here that I have given is misguided, please correct me and absolutely let me know if more information is needed, my entire methodology is wrong, or anything else of the sort.

Thank you so much for bearing with my nonsense!

Two things:
- You need a connection from GPIO9 to GND to force the chip into download mode. After you've successfully downloaded a program, you generally don't need it anymore (as ESP can put itself into download mode afterwards).
- This board uses the integrated USB-serial-JTAG device to talk to your PC, not an UART, so your channel for console output is correct. You're not using application level tracing, so you can ignore that. It does mean you don't need to install the UART driver; if you want you can install the USB-serial-JTAG driver instead.

Thank you so much for your response!

I actually ended up creating a solution to my problem so I will write it down for those of you who are reading this in the future needing help with how to read input on the ESP 32 C3 MINI:

In order to get this thing working, go to this link below:
https://docs.espressif.com/projects/esp ... /uart.html

Follow the steps for config, setting pins, and installing driver. After you do this, make sure that your console mode is changed from the default UART0 -> USB/JTAG "something something..."
After that, ensure you have the following item imported:
#include "driver/uart.h"

In addition to this, go ahead and add the following line inside of your CMakeList.txt (the one INSIDE the main file, not the one outside):
REQUIRES driver

^ (this require statement goes inside the parenthesis on a new line)

Now at this point you will have a configured ESP 32 for UART on whatever default pins the steps in the link showed you. A couple things you need to do to modify it all:

- change ".flow_ctrl" in the config to "UART_HW_FLOWCTRL_DISABLE" unless you need it

- remove ".rx_flow_ctrl_thresh"

- set UART_NUM to UART_NUM_0 or UART_NUM_1 (this goes for all of the parameters asking for uart_num)

- (this step is where I had issue) you need to modify the "uart_set_pin" with the following parameters:
- "uart_set_pin(UART_NUM_0, UART_PIN_NO_CHANGE, UART_PIN_NO_CHANGE, UART_PIN_NO_CHANGE, UART_PIN_NO_CHANGE)"
- by doing this, you are telling the board to use defaults, which will default to D+ and D- pins (on the USB) -- correct me please if my understanding on this part is wrong, would appreciate any feedback anywhere

- optionally you can remove the queue by doing the following:
- uart_driver_install(UART_NUM_0, uart_buffer_size, uart_buffer_size, 0, NULL, 0) <- you can also set the SECOND "uart_buffer_size" parameter to 0 if you don't need transmit

Now, in order to take in user input, I encourage you to figure this out on your own. However I am sure there are many of you that need a little nudge in the right direction, so I will link a couple cppreference functions that I ended up using in my final mock up of reading user input from the serial (I would learn how to use them if you don't know how, and then figure out how to implement them to take in user input):

https://en.cppreference.com/w/c/io/fgetc
https://en.cppreference.com/w/c/io/fgets




Now somebody is probably super lazy, so here is my solution in a nutshell: I read every character input (ignoring the garbage that IDF gives you when there was nothing input) and then compile them together into a full "msg" array

I hope that this helps someone, and good luck!