-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Describe the bug
I flashes the ESP32 V3 with the following commands:
./esptool --after no_reset --chip esp32 --baud 115200 --port /dev/cu.usbserial-0001 write_flash --verify 0x10000 /Users/zodiac/Downloads/firmware.bin
Connecting....
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: fc:b4:67:f5:98:a0
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00010000 to 0x0010cfff...
Compressed 1032416 bytes to 652001...
Wrote 1032416 bytes (652001 compressed) at 0x00010000 in 57.7 seconds (effective 143.2 kbit/s)...
Hash of data verified.
./esptool --after hard_reset --chip esp32 --baud 115200 --port /dev/cu.usbserial-0001 write_flash 0x307000 /Users/zodiac/Downloads/littlefs.bin
Connecting....
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: fc:b4:67:f5:98:a0
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00307000 to 0x003f6fff...
Compressed 983040 bytes to 367008...
Wrote 983040 bytes (367008 compressed) at 0x00307000 in 33.4 seconds (effective 235.4 kbit/s)...
Hash of data verified.
But than nothing happened, the reboot has apparently no effect and I also can't see any wifi.
If till now not connected the CAN-bus module
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Heating System Model
If applicable.
Used Interface Module
If applicable.
Additional context
That' is the consol output:
[0;32mI (52) boot: ESP-IDF qa-test-v4.3.3-20220423 2nd stage bootloader�[0m
�[0;32mI (53) boot: compile time 11:11:52�[0m
�[0;32mI (53) boot: chip revision: 3�[0m
�[0;32mI (58) boot_comm: chip revision: 3, min. bootloader chip revision: 0�[0m
�[0;32mI (65) boot.esp32: SPI Speed : 40MHz�[0m
�[0;32mI (69) boot.esp32: SPI Mode : DIO�[0m
�[0;32mI (74) boot.esp32: SPI Flash Size : 4MB�[0m
�[0;32mI (78) boot: Enabling RNG early entropy source...�[0m
�[0;32mI (84) boot: Partition Table:�[0m
�[0;32mI (87) boot: ## Label Usage Type ST Offset Length�[0m
�[0;32mI (95) boot: 0 phy_init RF data 01 01 0000f000 00001000�[0m
�[0;32mI (102) boot: 1 otadata OTA data 01 00 00010000 00002000�[0m
�[0;32mI (110) boot: 2 nvs WiFi data 01 02 00012000 0000e000�[0m
�[0;32mI (117) boot: 3 at_customize unknown 40 00 00020000 000e0000�[0m
�[0;32mI (125) boot: 4 ota_0 OTA app 00 10 00100000 00180000�[0m
�[0;32mI (132) boot: 5 ota_1 OTA app 00 11 00280000 00180000�[0m
�[0;32mI (140) boot: End of partition table�[0m
�[0;31mE (144) boot: ota data partition invalid and no factory, will try all partitions�[0m
�[0;31mE (152) esp_image: image at 0x100000 has invalid magic byte (nothing flashed here?)�[0m
�[0;31mE (160) boot: OTA app partition slot 0 is not bootable�[0m
�[0;31mE (166) esp_image: image at 0x280000 has invalid magic byte (nothing flashed here?)�[0m
�[0;31mE (175) boot: OTA app partition slot 1 is not bootable�[0m
�[0;31mE (180) boot: No bootable app partitions in the partition table�[0m
ets Jul 29 2019 12:21:46