/home/MY_USER_NAME/...are stripped from final FW binary? Thank you.
mos build --clean --local --platform=ESP8266is stuck at
Docker arguments: run --name mos_build_ ...again. This is my 2nd build today, I had terminate a previous build and restart the build. The last time the mos build stuck at docker was about a week ago when using mos latest '74. Now with mos release 2.19.1 , same issue. Is this related to docker limitation of 200 container pull per 6 hr?
currently the mos build local on mac os mojave stuck at
for the last hour. CTRL-C and rebuild, restart docker and rebuild, clean and rebuild.. stuck at the above line. Is mos under some maintanence schedule?
Hi, I try to upgrade my project to Mongoose-OS v2.19.1 and get this error wiht local build:
Generating esp32.project.ld LD /home/mark_wahlberg/git/my-app/build/objs/my-app.elf /opt/Espressif/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/mark_wahlberg/git/my-app/build/objs/mosapp/libmosapp.a(mgos_freertos_core_dump.c.o):(.text.mgos_freertos_core_dump+0x20): undefined reference to `mgos_freertos_extract_regs' /opt/Espressif/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/mark_wahlberg/git/my-app/build/objs/mosapp/libmosapp.a(mgos_freertos_core_dump.c.o): in function `mgos_freertos_core_dump': /home/mark_wahlberg/git/my-app/deps/freertos/src/mgos_freertos_core_dump.c:40: undefined reference to `mgos_freertos_extract_regs' collect2: error: ld returned 1 exit status make: *** [/home/mark_wahlberg/git/my-app/build/objs/my-app.elf] Error 1 /opt/Espressif/esp-idf/make/project.mk:563: recipe for target '/home/mark_wahlberg/git/my-app/build/objs/my-app.elf' failed make: Leaving directory '/app'
Does anyone have a clue for me?
@hoffmann-m In the current version of esp-idf (4.2-r1),
mgos_freertos_extract_regs definition is protected by CONFIG_ESP32_ENABLE_COREDUMP_TO_UART.
In previous versions there was simply a
Hi all, any idea what could I check if my OTA via HTTP GET is not working (and it was working 3 weeks ago).
I use a Google Cloud Storage bucket to store the fw.zip file, and generate a V4 signed key URL to download it, which is passed onto the mgos_ota_http_start function. The mgos_ota_http_start function receives the URL but does not start the OTA process - just seems stuck.
[Mar 11 10:06:49.741] mgos_ota_http_clien:270 Update URL: https://randomstorage.storage.googleapis.com/fw.zip?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=... [Mar 11 10:06:49.869] mg_ssl_if_mbedtls.c:35 0x3fff6354 ciphersuite: TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256 [Mar 11 10:06:50.442] SW ECDSA verify curve 3 hash_len 32 sig_len 71 [Mar 11 10:06:55.666] SW ECDH curve 3 [Mar 11 10:07:00.587] mgos_mongoose.c:66 New heap free LWM: 6864
I am happy to share more of the code, but since it once was reliably working, I firmly believe that the issue is with credentials or something. I would appreciate your help, as I am really confused and disappointed that something that worked is not working after 2 weeks.
mg_use_cert()function. Every call fail with:
heap integrity broken: free links don't match: 788 -> 868, but 868 -> 0.