No Serial Monitor output from Lilygo T-Display S3 board

Continuing the discussion from Serial Monitor Not Working On Esp32(SOLVED):

I'm using the Lilygo T-Display S3, and I've never managed to make the serial monitor work.
I print there a lot of stuff, but it never gets displayed...
I'm using the same baud rate between the code and the serial panel.
I've used while(!Serial); with no success.
What do I need to do? Using Arduino IDE 2.0.1 on Win10

The only thing I see on the serial monitor is:

load:0x3fce3808,len:0x43c
load:0x403c9700,len:0xbec
load:0x403cc700,len:0x2a3c
entry 0x403c98d8
E (448) ADC: adc1_lock_release(419): adc1 lock release called before acquire
E (448) ADC: adc1_lock_release(419): adc1 lock release called before acquire
E (448) ADC: adc1_lock_release(419): adc1 lock release called before acquire
E (448) ADC: adc1_lock_release(419): adc1 lock release called beESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x2b (SPI_FAST_FLASH_BOOT)
Saved PC:0x4037f904
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x43c
load:0x403c9700,len:0xbec
load:0x403cc700,len:0x2a3c
entry 0x403c98d8
E (448) ADC: adc1_lock_release(419): adc1 lock release called before acquire

Hi @fabryz

When I'm having trouble with serial output, I like to do a quick check with the most simple possible sketch. If this works, then I know the problem has something to do with my real sketch. If it doesn't work, then I know the problem is not related to my sketch code. It seems maybe a little silly, but it allows me to be sure I'm focusing my troubleshooting efforts in the right direction.

Try uploading this sketch to your Arduino board:

  1. Copy and paste this code as a new sketch in the Arduino IDE:
    void setup() {
      Serial.begin(9600);
    }
    
    void loop() {
      Serial.println("hello");
      delay(1000);
    }
    
  2. Upload the sketch to your Arduino board.
  3. Select Tools > Serial Monitor from the Arduino IDE menus to open the Serial Monitor view if it is not already open.
  4. Make sure the baud rate menu at the top right corner of the Serial Monitor panel is set to "9600".

Do you now see the word "hello" being printed in the Serial Monitor's output field once a second?

Hi @ptillisch yes, I also like to try with the simplest code and then evolve it, so I'm sure that I'm building above something that has already been tested and worked.

I've tried your simple code, but it doesn't print anything, the console is completely empty

Does the same problem occur if you try with the Arduino IDE 1.8.19 Serial Monitor?

The download links for Arduino IDE 1.8.19 are listed here:

https://www.arduino.cc/en/software#legacy-ide-18x

You will probably find the "Windows ZIP file" download the most convenient in this case where you only want to do a quick experiment. Just download that file, unzip the file to any convenient location, then run the arduino.exe file you find inside the unzipped folder. No installation is needed.

I already have the 1.8 installed, was just migrating to 2.x.
Will try that as soon as possible, I've actually never had console issues with arduinos, only with this esp32

Hi, I'm also try to us a Lilygo T-Display S3 and can't get anything out of the serial monitor...
I'm using Arduino IDE 1.8.13 on a iMac, and get good output from the other device I use (Uno, Nano, NodeMCU, etc.), but nothing from the S3.
I've followed this tread and tried the simple code with a few different port speeds, but nothing seems to help.
Not sure what to try next.

I'm having exactly the same problem with the Lilygo T-Display S3. Also Arduino 1.8.13 on a Mac. Can it have something todo with the USB-Serial Driver on the Mac ??

OK ...found it .. for the Lilygo T-display S3 you have to set USB CDC on Boot "Enable".

4 Likes

Your an absolute star... Not sure how that got disabled, as I'm sure I was getting the boot up info before... Anyway, Serial Monitor is now working!

"USB CDC on Boot" set to "Enable" works for me on Arduino IDE 1.8.19 :+1: :+1: :+1:

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.