Closed technicsdj closed 6 months ago
rstrouse
commented
6 months ago If this is a new onboard download the onboard file again and flash it again. It looks like the littlefs partition is corrupted. If you are using one of the espressif tools this can happen when the serial port write is corrupted. I would suggest you download the onboard file again and use the web.esphome.io website. Also please make sure you download the proper onboard file.
technicsdj
commented
6 months ago Hey, thanks for the idea. i have tested it but i have the same problem as with all flashers, that the bootled of the controller is only lit. the log shows the following errors:
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371
rstrouse
commented
6 months ago That tells me that either the flash chip is broken or you are not using the correct SomfyController.onboard.esp32xx.bin.zip file. The watchdog timer resetting like that is typically because the main bootloader cannot find the proper code to execute.
EDIT: Which ESP32 board do you have?
technicsdj
commented
6 months ago i am using the following microcontroller. https://www.az-delivery.de/en/products/esp32-developmentboard i can rule out that it is broken. i have tried a new one and i get the same errors. can you tell me which is the correct firmware?
rstrouse
commented
6 months ago Ok so download the zip file below and extract it to a directory on your computer.
Install button. Do not click the PREPARE FOR FIRST USE button.SomfyController.onboard.esp32.bin and press INSTALLWhen it finishes installing the binaries you should remove power from the board and reboot it. After it has completely booted you should see an ESPSomfy RTS access point in your wifi list.
technicsdj
commented
6 months ago thanks for the instructions, i get the same error that the index.html cannot be found.
the accesspoint is available and i can connect, but as i said i get the error message that the index.html cannot be found.
rstrouse
commented
6 months ago I decided to flash another device with onboard firmware and it worked just fine. What is the history with this board? Is it currently hooked up to the radio? If it is please remove the radio from all the pins. That way we can make sure there isn't a wiring issue with the radio.
If you look at the error above it is like the littlefs partition cannot be mounted.
technicsdj
commented
6 months ago there is no radio connected to the microcontroller. when the radio is connected, it cannot be flashed at all. i have now taken another brand new controller and i get the same errors. i am beginning to think it is the microcontroller that is not compatible with the software. i simply flashed a standard tasmota software on the controller and it works perfectly.
Errorlog new microcontroller: Turning the HotSpot On WiFi AP Started Initializing AP for credentials modification
SoftAP IP: WiFi AP Stopped 192.168.4WiFi AP Started .1 .........1Loading file /index.html 111111....................................................................................
rstrouse
commented
6 months ago That is very odd. When you reboot it while connected to the serial log do you still see that it cannot mount littlefs.
This is the sequence from your log above that indicates that it cannot initialize the filesystem.
[22:01:10]E (9) esp_littlefs: ./components/esp_littlefs/src/littlefs/lfs.c:1347:error: Corrupted dir pair at {0x0, 0x1}
[22:01:10]
[22:01:10]E (11) esp_littlefs: mount failed, (-84)
[22:01:10]E (14) esp_littlefs: Failed to initialize LittleFS
[22:01:10]Error mounting file systemIf you are not getting that then hard refresh your browser to make sure we are not just getting cache corruption from the browser. If this is chrome then hold down the control key and press f5 if it is Safari then you will need to clear the browser cache for 192.168.4.1.
Likely the reason why it is working fine with Tasmota is because it does not use the littlefs filesystem and therefore doesn't create a partition for it. In looking at those docs it creates a completely different filesystem.
technicsdj
commented
6 months ago holy shit dude you are right :D. i deleted the cache for the page with ctrl + f5 and then i flash the whole thing via web.esphome.io and close the serial log. now it works and it loads the index.html. thanks a lot, i will test it further and report back.
rstrouse
commented
6 months ago Awesome!
rstrouse
commented
6 months ago I am going to close this. If you have other problems open a new issue.
Hardware
ESP32
Firmware version
v2.4.1
Application version
v2.4.1
What happened? What did you expect to happen?
hello i have now tried to flash the latest firmware on my esp32 microcontroller. with the tasmota esp flasher i always get the error index.html not found. i have tried several flashers, but none of them work properly. with the esp flashtool, as described in the instructions, the esp controller does not even boot up. the bootled always just flashes. i have tried all the firmware versions offered with both flashers. what am i doing wrong? greetings and thanks
How to reproduce it (step by step)
Logs