-
Notifications
You must be signed in to change notification settings - Fork 140
Closed
Description
Checklist
- Checked the issue tracker for similar issues to ensure this is not a duplicate
- Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
- Tested with the latest version to ensure the issue hasn't been fixed
How often does this bug occurs?
always
Expected behavior
Remain connected and stub executing / esptool-js be functional.
Actual behavior (suspected bug)
After stub loads the device presents a Guru Meditation Error
Error logs or terminal output
esptool.js
Serial port WebSerial VendorID 0x1a86 ProductID 0x55d3
Connecting...Debug: using Classic Serial Reset
Debug: _connect_attempt default_reset
Debug: Sync connect attempt 0
Debug: Sync
Debug: Sync err Error: Invalid head of packet (0x74): Possible serial noise or corruption.
Debug: Error at sync Error: Invalid head of packet (0x74): Possible serial noise or corruption.
Debug: Sync connect attempt 1
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 2
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 3
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 4
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: _connect_attempt default_reset
Debug: Sync connect attempt 0
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 1
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 2
Debug: Sync
Debug: Sync err Error: No serial data received.
Debug: Error at sync Error: No serial data received.
Debug: Sync connect attempt 3
Debug: Sync
Debug: 538052359
Debug: Connect attempt successful.
Debug: Chip Magic f01d83
Detecting chip type... ESP32
Debug: Read efuse 1073061900
Debug: Read efuse 1073061900
Debug: Read efuse 1073061908
Debug: Read efuse 1073061900
Chip is ESP32-U4WDH (revision 3)
Debug: Read efuse 1073061900
Debug: Read efuse 1073061900
Debug: Read efuse 1073061904
Debug: Read efuse 1073061912
Features: Wi-Fi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
Debug: Read efuse 1073061892
Debug: Read efuse 1073061896
MAC: ec:c9:ff:8a:53:cc
Debug: Read efuse 1073061892
Debug: Read efuse 1073061896
Uploading stub...
Debug: mem_begin 3532 1 6144 400be000
Debug: check_command enter RAM download mode
Debug: check_command write to target RAM
Debug: mem_begin 156 1 6144 3ffdeba8
Debug: check_command enter RAM download mode
Debug: check_command write to target RAM
Running stub...
Debug: check_command leave RAM download mode
Error: Guru Meditation Error detected
// CONSOLE FROM BROWSER:
Error: Guru Meditation Error detected
at $48fa161544deddd5$export$86495b081fef8e52.detectPanicHandler (webserial.js:214:19)
at $48fa161544deddd5$export$86495b081fef8e52.read (webserial.js:255:30)
at async $6473b3df29822c68$export$b0f7a6c745790308.runStub (esploader.js:1038:41)
at async $6473b3df29822c68$export$b0f7a6c745790308.main (esploader.js:1076:9)
at async $382e02c9bbd5d50b$var$connectButton.onclick (index.ts:118:12)
Steps to reproduce the behavior
Connect Adafruit Mini Sparkle Motion (https://www.adafruit.com/product/6160)
Click connect after selecting any baud (or default)
Project release version
latest
System architecture
Intel/AMD 64-bit (modern PC, older Mac)
Operating system
MacOS
Operating system version
Sequoia 15.3
Shell
ZSH
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels