This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
Magic Byte Error #311
Comments
The error is correct, the firmware binary (the file you give the flasher) should always start with the bytecode |
I'm an idiot. I was trying to upload the .Yaml. Figured ish how to use the CLI, but now getting a similar error: Invalid head of packet (0x1B) This was using esphomeyaml bedroom.yaml wizard
|
Changed to a different Ubuntu machine and it worked. Problem solved |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Getting this error:
Using 'COM3' as serial port.
Connecting....
Detecting chip type... ESP32
Connecting....
Chip Info:
Uploading stub...
Running stub...
Stub running...
Unexpected error: The firmware binary is invalid (magic byte=65, should be E9)
Tried with 3 of those
https://www.aliexpress.com/item/ESP32-Development-Board-WiFi-Bluetooth-Ultra-Low-Power-Consumption-Dual-Cores-ESP-32-ESP-32S-Board/32801337284.html
All give the same error: Unexpected error: The firmware binary is invalid (magic byte=65, should be E9)
Please provide details about your environment.
--> Windows with EshopmeFlasher, Yaml file generated on Docker
Please provide details about which ESP you're using.
-->
this one https://www.aliexpress.com/item/ESP32-Development-Board-WiFi-Bluetooth-Ultra-Low-Power-Consumption-Dual-Cores-ESP-32-ESP-32S-Board/32801337284.html
Description of problem:
GEtting Unexpected error: The firmware binary is invalid (magic byte=65, should be E9)
while trying to flash
Problem-relevant YAML-configuration entries:
Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: