Skip to content

Need images for ESP32-S2 series without the internal USB CDC #890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
josesimoes opened this issue Nov 18, 2021 · 9 comments · Fixed by nanoframework/nf-interpreter#3053
Closed

Comments

@josesimoes
Copy link
Member

Details about Problem

Target: ESP32-S2

Description

All current images for ESP32-S2 are using the internal USB CDC for Wire Protocol.
Several modules out there have an external serial-USB chip instead. Need to figure out a common pattern for the UART pins so we can offer an image that fits those.
Example: https://www.olimex.com/Products/IoT/ESP32-S2/ESP32-S2-DevKit-Lipo/open-source-hardware

@hneel
Copy link

hneel commented Feb 23, 2022

Does this apply to the Wemos S2 Mini too?
I can't get a connection with this device

C:\>nanoff --serialport COM12 --target ESP32_PSRAM_REV0 --update
.NET nanoFramework Firmware Flasher v2.0.30+937d96cbf5
Copyright (C) 2019 .NET Foundation and nanoFramework project contributors


Using COM12 @ 1500000 baud to connect to ESP32.
Reading details from chip...
Error E4000: Error executing esptool command. (esptool.py v3.2
Serial port COM12
Connecting...
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting...

Traceback (most recent call last):
  File "esptool.py", line 377, in detect_chip
struct.error: unpack requires a buffer of 16 bytes

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "esptool.py", line 5143, in <module>
  File "esptool.py", line 5136, in _main
  File "esptool.py", line 4541, in main
  File "esptool.py", line 121, in get_default_connected_device
  File "esptool.py", line 388, in detect_chip
  File "esptool.py", line 663, in connect
  File "esptool.py", line 616, in _connect_attempt
  File "serial\serialutil.py", line 594, in inWaiting
  File "serial\serialwin32.py", line 259, in in_waiting
serial.serialutil.SerialException: ClearCommError failed (PermissionError(13, 'The device does not recognize the command.', None, 22))
[3356] Failed to execute script 'esptool' due to unhandled exception!
)

@josesimoes
Copy link
Member Author

josesimoes commented Mar 2, 2022

@hneel I've check the Wemos S2 Mini schematic and it's using the embedded USB CDC port, so this issue does not apply to that hardware.

Instead of the above, try this command line: nanoff --serialport COM12 --platform esp32 --update --preview.

@hneel
Copy link

hneel commented Mar 2, 2022

Hi, thanks for your reply. But unfortunatly it doesn't work. Whatever I try, I always get this error.
(I've also tried a 2nd device. it didn't make any differrence)

@josesimoes
Copy link
Member Author

@hneel can you go over to our Discord to discuss about this? If yes, please ping me there, about this.

@josesimoes
Copy link
Member Author

josesimoes commented Mar 8, 2022

For reference, here's an official module using an external USB-Serial bridge chip .
And another one here.

@FrankBakkerNl
Copy link

As discussed on Discord this board seems to have the same issue
http://www.lilygo.cn/prod_view.aspx?typeid=50033&id=1321&fid=t3:50033:3

@networkfusion
Copy link
Member

@AdrianSoundy Is this now fixed?

@AdrianSoundy
Copy link
Member

I haven't looked at this one but it is straight forward.
We currently have 2 firmware for S2

  • Kaluga with Uart for wire protocol & screen ILI9341
  • Feather_S2 with USB CDC for wire protocol

The Kaluga should work for all devices with just UART

Probably best to create 2 new firmware and retire these one.
ESP32_S2_UART
ESP32_S2_USB
Both with generic screen drivers

What do you think ?
@josesimoes @networkfusion

@josesimoes
Copy link
Member Author

I'm OK with that option. Will you tackle that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants