Help needed with --debug on ESP32-S3 #559
Replies: 2 comments 3 replies
-
|
Your board has a UART to USB bridge IC on it and it is connected to the rx and tx pins for the console on the esp32. this is what you need to be using for your serial connection to the ESP32. This should be your build command. There are 3 different types of connections that can be made from your computer to the ESP32. they are as follows. Serial Serial is a serial connection that communicates using a traditional serial type of IO. For this to work the board you have need to have a TTL to USB (Serial to USB) bridge IC. One of the 2 USB ports on your board is connected to that IC. The other USB port is for connecting the ESP32 to other serial devices, things like keyboards, mice, etc.. However it also handles the CDC and JTAG connections. MicroPython by default is setup to output over the CDC connection if the MCU supports it. The REPL can be output to both the CDC and the UART at the same time if you wanted to but it ends up being a waste of pins. Because your MCU has both connected you would want to output the REPL to UART which then leaves the other USB available for you to use if you wanted to connect a USB device. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Kevin, Using your suggested build configuration, mpremote started worked fine and the debug output was no longer spewing ten of thousands of lines of Your build config outputs both debug and REPL on UART. Before you replied, I did try something else: I commented out the line in the esp-idf that was generating that specific debug line from |
Beta Was this translation helpful? Give feedback.
-
|
depending on the kind of display you have attached and if it initialized any drivers for the display you could get a whole lot of messages for it. I would not be able to tell you exactly what was going on unless I was able to replicate the exact setup you are using to be able to test with. |
Beta Was this translation helpful? Give feedback.
-
|
This is before any drivers are initialised. This is immediately on boot. |
Beta Was this translation helpful? Give feedback.
-
|
I am sure that interrupts are used internally in micropython as well as in the serial connection whether it be CDC, JTAG or UART. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have built debug firmware with the following command line:
sd@SD-i9:~/lvmpy$ python3 make.py esp32 --enable-uart-repl=n --debug --flash-size=16 BOARD=ESP32_GENERIC_S3 BOARD_VARIANT=SPIRAM_OCT DISPLAY=st77916 INDEV=cst816sI added the
--enable-uart-repl=nbecause I could see the REPL prompt appearing in the debug output on the UART.I get my debug output on the UART USB port at 115,200 baud.
The board is a very generic one from Amazon and seems to run well without the --debug, even when overclocking the memory.
https://www.amazon.co.uk/dp/B0DFGFV3H5?th=1
If I try to use mpremote mount (in order to do my debugging), I get a timeout before it can connect.
If I wait several minutes, I can get a REPL with a basic terminal.
I wondered if the debug output was slowing down REPL interaction, so I turned off debug output using...
This silences all debug output on the UART.
But the REPL still does not behave, even with no debug output happening...
If, after silencing the debug output, I close my terminal and try to open the REPL port again, I can get various errors messages, including
access deniedand '**** Failed to open the serial port COM8 ****' (from within vscode) on the REPL com port. I cannot usempremote mounteither.Are there some pitfalls I need to be aware of in order to compile with --debug and get a functioning REPL?
Basically, I can get debug output, but am unable to execute any useful micropython code.
I am a bit stumped as to what to try next.
Here is the log of the firmware starting up. Once it has started, it continuously outputs
D (xxxxxx) intr_alloc: Connected src 38 to int 3 (cpu 1), where xxxxxx is a timestamp, until I setesp.osdebug(None)Beta Was this translation helpful? Give feedback.
All reactions