ci: attach each board's firmware ELF to releases

A crash log on a release build couldn't be decoded: the release had only
the .bin files, and the ELF was a 5-day CI artifact of other runs.  The
panic in #31 names "ELF file SHA256: f85f409205c11d1b" and no copy of that
file exists.

Each release now gets SomfyController.ino.<chip>.elf.zip, built in the
same job as the .bin it decodes.  Beside the ELF is its .sha256: the .bin
embeds that hash, and the panic prints its first digits, so a log shows
which build it came from.  The bug report form asks for the whole panic
and says how to decode it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
cjkas 2026-10-29 18:53:45 +01:00
parent 1c66c310bd
commit 8600c5e811
2 changed files with 33 additions and 1 deletions

View file

@ -67,7 +67,12 @@ body:
id: logs
attributes:
label: "Logs"
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
description: |
Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
> After a crash, include the whole panic: the `Guru Meditation Error` line, the `Backtrace:` line and the `ELF file SHA256:` line.
> Each release has a `SomfyController.ino.<chip>.elf.zip` that decodes the backtrace:
> `xtensa-esp32s3-elf-addr2line -pfiaC -e SomfyController.ino.esp32s3.elf <backtrace addresses>`
> (`riscv32-esp-elf-addr2line` on the C3, C5 and C6).
render: bash
validations:
required: false