Replies: 4 comments 4 replies
-
Hey @HausBJB! As stated in the issues template, we're using github issue to track work items, not anwesering questions. |
Beta Was this translation helpful? Give feedback.
-
OK thanks. @josesimoes But couldn't that also be a bug? Then I hope that someone can help me here |
Beta Was this translation helpful? Give feedback.
-
I have the same problem with an ESP WROOM 32. Flashing the Program succeeds in 1 out of 20 deployment tries. On the other tries I get the same "ERROR: failing to connect to device". I tried multiple targets (ESP32_REV0, ESP32_REV3 (and BLE versions), ESP32_WROOM_32). Don't know what I'm doing wrong. I checked the cable multiple times and tried with multiple ESPs from the same model. |
Beta Was this translation helpful? Give feedback.
-
@HausBJB Hello, I have the same problem as you. I have successfully solved this problem, but I don't know if this can help you. Wish you a happy life! |
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.
-
Target name(s)
ESP32_BLE_REV0
Firmware version
1.8.0.616
Was working before? On which version?
N/A
Device capabilities
nanoff --update --target ESP32_BLE_REV0 --serialport COM10
.NET nanoFramework Firmware Flasher v2.4.2+c4df2f6716
Copyright (C) 2019 .NET Foundation and nanoFramework project contributors
Using COM10 @ 1500000 baud to connect to ESP32.
Reading details from chip...
OK
Connected to:
ESP32 (ESP32-D0WDQ6 (revision 1))
Features WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Flash size 4MB unknown from TENX (manufacturer 0x94 device 0x16406)
PSRAM: undetermined
Crystal 40MHz
MAC C8:F0:9E:A3:18:E4
Trying to find ESP32_BLE_REV0 in stable repository...OK
Extracting ESP32_BLE_REV0-1.8.0.616.zip...OK
Updating to 1.8.0.616
Erasing flash...
OK
Flashing firmware...
Wrote 23856 bytes (15078 compressed) at 0x00001000 in 0.4 seconds (effective 477.1 kbit/s)...
Hash of data verified.
Wrote 1254352 bytes (823172 compressed) at 0x00010000 in 12.9 seconds (effective 778.9 kbit/s)...
Hash of data verified.
Wrote 3072 bytes (136 compressed) at 0x00008000 in 0.1 seconds (effective 305.0 kbit/s)...
Hash of data verified.
OK
Description
The firmware update worked wonderfully. VS 2022 also finds the device in the device explorer.
Unfortunately, all other things do not work.
First start:
17:28:25.755 [NanoDevices: checking device COM10 *** 2nd attempt ***]
17:28:25.779 [NanoDevices: checking device COM10 @ 921600]
17:28:29.478 [NanoDevices: valid device ESP32 @ COM10]
17:28:29.478 [NanoDevices: Serial device enumeration completed. Found 1 devices]
E.g. Ping works and I get the following message.
ESP32 @ COM10 is active running nanoCLR.
All other commands do not work e.g
Device capabilities report the following.
ESP32 @ COM10 is not responding, please reboot the device.
F5 =>
17:34:48.783 [Starting deployment transaction from v2022.2.0.48+5f8dab6e5f]
17:34:48.786 [Starting debug engine on nanoDevice]
17:34:48.812 [Connecting to debugger engine...]
17:34:53.200 [*** ERROR: failing to connect to device ***]
Ping
ESP32 @ COM10 is active running nanoCLR.
Device Capabilities
ESP32 @ COM10 is not responding, please reboot the device.
What am I doing wrong?
How to reproduce
No response
Expected behaviour
No response
Screenshots
Aditional information
No response
Beta Was this translation helpful? Give feedback.
All reactions