You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After solving the container issue i am running into another one while patching the firmware.
After the webserial way failed to read the firmware i dumped it using esptool.py and patched the firmware the "old" way, but i was running into the "Ameise" bug and could not get the box to connect to any cloud.
I reverted back to my backup and factory reset the box. After updating the firmware i tried the webserial method on a different PC and this time it successfully read the firmware, but patching failed.
Relevant log from the container:
INFO |handler_api.c:1117:file_save_start_suffix| Writing to '/teddycloud/data/firmware/ESP32_d48afca6cd2c_2.bin'
INFO |server_helpers.c:0484:multipart_handle| Received file 'ESP32_d48afca6cd2c'
INFO |handler_api.c:1180:handleApiESP32UploadFirmware| Received new file:
INFO |handler_api.c:1181:handleApiESP32UploadFirmware| '/teddycloud/data/firmware/ESP32_d48afca6cd2c_2.bin'
INFO |handler_api.c:1354:handleApiESP32PatchFirmware| Patch firmware
INFO |handler_api.c:1375:handleApiESP32PatchFirmware| Patch hostnames 'teddyone.grossesser.com'
INFO |handler_api.c:1400:handleApiESP32PatchFirmware| Request for '/teddycloud/data/firmware/ESP32_d48afca6cd2c_2.bin'
INFO |esp32.c:1737:esp32_inject_ca| Writing CA into '/teddycloud/data/firmware/cert_d48afca6cd2c//ca.der'
INFO |esp32.c:1754:esp32_inject_ca| Convert CA certificate...
INFO |esp32.c:1792:esp32_inject_ca| Injecting CA into '/teddycloud/data/firmware/patched_d48afca6cd2c.bin'
INFO |esp32.c:1380:esp32_get_partition| Search for partition 'assets'
ERROR|esp32.c:1414:esp32_get_partition| Partition 'assets' not found
ERROR|esp32.c:1637:esp32_fat_inject| Asset partition not found
ERROR|esp32.c:1795:esp32_inject_ca| Failed to patch image
ERROR|handler_api.c:1428:handleApiESP32PatchFirmware| Failed to generate and inject CA
WARN |server_helpers.c:0806:httpServerUriNotFoundCallback| >> 404 /api/esp32/patchFirmware
The interesting bit is: If i dump the firmware using esptool.py and use the old method it does find the assets partition and produces a flashable firmware.
Unfortunately this one also fails to connect...
But i think it does try to connect:
INFO |handler_cloud.c:0041:handleCloudTime| >> respond with current time
INFO |mqtt.c:0685:mqtt_init_box| Skipping client 'Toniebox' (cn: 'default')
WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
INFO |cloud_request.c:0178:web_request| Cloud requests generally blocked in settings
ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
INFO |cloud_request.c:0178:web_request| Cloud requests generally blocked in settings
ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
INFO |cloud_request.c:0178:web_request| Cloud requests generally blocked in settings
ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Any suggestions?
The text was updated successfully, but these errors were encountered:
After solving the container issue i am running into another one while patching the firmware.
After the webserial way failed to read the firmware i dumped it using esptool.py and patched the firmware the "old" way, but i was running into the "Ameise" bug and could not get the box to connect to any cloud.
I reverted back to my backup and factory reset the box. After updating the firmware i tried the webserial method on a different PC and this time it successfully read the firmware, but patching failed.
Relevant log from the container:
The interesting bit is: If i dump the firmware using esptool.py and use the old method it does find the assets partition and produces a flashable firmware.
Unfortunately this one also fails to connect...
But i think it does try to connect:
Any suggestions?
The text was updated successfully, but these errors were encountered: