ESP Insights: A remote diagnostics/observability framework for connected devices
Apache License 2.0
101
stars
27
forks
source link
We could not find the firmware image to cross-reference this log entry. Please upload a firmware image to get cross-referenced information for this log entry. #45
I'm having an issue similar to a couple of closed issues on this board (e.g. #33 and #40), using ESP-IDF release v5.3 on an esp32s3.
My device is connected to insights, and metrics etc. is all working OK but for every log message I get the error: "We could not find the firmware image to cross-reference this log entry. Please upload a firmware image to get cross-referenced information for this log entry."
In my log output I see on boot that I have ELF file SHA256: 8a776829b..., and in the insights dashboard the uploaded firmware is reporting as 8a776829bfc0f0a1 so I think that's OK. The only error message I get in my logs related to insights is esp_insights: Failed to enable insights_cmd_resp, not sure if that's relevant?
I've attached a few screenshots so you can see all the firmware versions and hashes are aligned.
I'm having an issue similar to a couple of closed issues on this board (e.g. #33 and #40), using ESP-IDF release v5.3 on an esp32s3.
My device is connected to insights, and metrics etc. is all working OK but for every log message I get the error: "We could not find the firmware image to cross-reference this log entry. Please upload a firmware image to get cross-referenced information for this log entry."
In my log output I see on boot that I have ELF file SHA256: 8a776829b..., and in the insights dashboard the uploaded firmware is reporting as 8a776829bfc0f0a1 so I think that's OK. The only error message I get in my logs related to insights is esp_insights: Failed to enable insights_cmd_resp, not sure if that's relevant?
I've attached a few screenshots so you can see all the firmware versions and hashes are aligned.