Can't program and connect to ESP32-S3 TinyS3 AP / run esp32-s3-devkitc-1-n32r8v

[ajlennon]

PROBLEM DESCRIPTION

I am trying to boot the development release binaries on ESP32 S3 boards. I've tried two boards

• esp32-s3-devkitc-1-n32r8v
• tinys3

They program but then seem to fail in slightly different ways.

With the TinyS3 I see Tasmota boot and it says the webserver is running in AP mode. I do see the AP on my phone/laptop but cannot connect to it (I've tried forgetting the AP and various clients to connect).

I also see a "QPC: Reset" in the CDC serial log

rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)                                                                                                                
Saved PC:0x42102d2e                                                                                                                                                          
SPIWP:0xee                                                                                                                                                                   
mode:DOUT, clock div:1                                                                                                                                                       
load:0x3fce3808,len:0x128                                                                                                                                                    
load:0x403c9700,len:0xba4                                                                                                                                                    
load:0x403cc700,len:0x275c                                                                                                                                                   
SHA-256 comparison failed:                                                                                                                                                   
Calculated: 6cc03bfca557e3754e59bc9ad33adf6a93f7a61de42da4d84cf4b736cd6b6b37                                                                                                 
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff                                                                                                   
Attempting to boot anyway...                                                                                                                                                 
entry 0x403c98c0                                                                                                                                                             
                                                                                                                                                                             
00:00:00.001 CMD: Using USB CDC                                                                                                                                              
00:00:00.001 HDW: ESP32-S3 (PSRAM)                                                                                                                                           
00:00:00.011 UFS: FlashFS mounted with 4404 kB free                                                                                                                          
00:00:00.026 CFG: Loaded from File, Count 6                                                                                                                                  
00:00:00.032 QPC: Count 1                                                                                                                                                    
00:00:00.060 BRY: Berry initialized, RAM used=4041 bytes                                                                                                                     
00:00:00.067 Project tasmota - Tasmota Version 12.2.0.6(tasmota)-2_0_5_3(2022-12-06T08:40:06)                                                                                
00:00:00.219 WIF: WifiManager active for 3 minutes                                                                                                                           
00:00:00.890 HTP: Web server active on tasmota-4F4994-2452 with IP address 192.168.4.1                                                                                       
00:00:06.953 QPC: Reset           
00:09:58.951 APP: Serial logging disabled  

I've googled around and tried a range of different esptool.py programming settings I've seen but nothing seems to help

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Read the Contributing Guide and Policy and the Code of Conduct
• Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• Device used (e.g., Sonoff Basic): _____ TinyS3
• [ X Tasmota binary firmware version number used: _____ Development tasmota32s3cdc.factory.bin
  • Pre-compiled
  • Self-compiled
• Flashing tools used: _____ esptool.py v4.4
• Provide the output of command: Backlog Template; Module; GPIO 255:

  Configuration output here:

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

• Provide the output of this command: Status 0:

  STATUS 0 output here:

• Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

Program esp32-s3-devkitc-1-n32r8v or TinyS3

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

Tasmota to boot, connect to AP

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[ajlennon]

As if by magic after going through all that as soon as I posted this issue I figured out a workaround

With the TinyS3 the issue is that I needed to reset the board using the reset button after I power it up.

Very unsure why this should be!

NB. This is replicable

• Every time I plug in the USC-C connector the AP can be seen on my phone but I can never connect. When I try to connect the AP seems to go away

• If instead I power then push the reset button I can then connect to the AP and can get the board on my WiFI network and access it.

Most odd. Have dropped back to look at the esp32-s3-devkitc-1-n32r8v now as we get different errors with that

[barbudor]

In many case a hardware reset (or sometime power cycling) is generally recommended after flashing
When flashing dev boards such as Nodemcu, mini-D1 etc that are using external usb/serial bridge, the board embeds a logic to trigger the reset pin at the end of the flashing.
When flashing through CDC, the reset cannot occur

[ajlennon]

Yes but the thing here is if I power cycle without the reset button press then I'll fail to connect again 🤦‍♀️

[barbudor]

Sorry I missed you exact details

When you power through usb c, you mean connected to a phone or PC?
Did you tried powering with a charger?
May be there is some impact of CDC that systematically place the chip in programming mode

[ajlennon]

So with TinyS3 and CDC development image this morning I can't seem to connect to it whatever I do (laptop, resetting, charger). Will keep banging away at this...

[sfromis]

While I do not have the TinyS3 (from Unexpected Maker, I assume), I'm not seeing such trouble with his larger ProS3 board, using the tasmota32s3cdc.factory.bin image.

I do know of a risk of certain "ideas" seen from some mobile device creators can cause trouble connecting to an AP without Internet access, but this should not depend on you doing extra resets.

[Jason2866]

The reset behaviour is not under software control. It is the hardware design how it is integrated. The S3 is different here to the other ESP32 MCUs.

[sfromis]

One potential risk factor could be the "power supply situation". Depending on how much is powered up, and what power is actually available at that time, operation just might be affected. A following reset would have "less risk" after the broader power situation was stabilized.

Not saying that this is cause, just pointing out that things are often more complex than simplistic digital ideas about things being either fully ON or completely OFF.