ESPSomfy-RTS/.github/ISSUE_TEMPLATE/BUG-REPORT.yaml
cjkas dfb003d2f7 build: add the ESP32-P4 (#29)
For boards such as Waveshare's ESP32-P4-WIFI6-POE-ETH: WiFi through the
board's ESP32-C6 on SDIO (esp-hosted), Ethernet on the P4's RMII MAC with
an IP101.  Not tested on a device: no P4 board was at hand.

- platformio.ini: env esp32p4 (esp32-p4_r3, chip v3.01+) and esp32p4es
  (esp32-p4, the esp32p4_es libraries, chips before v2.0).  An image runs
  on one of the two only, so each has its own release files, chip models
  "p4" and "p4es".  Both keep the OTA slot: at level 2 they leave about
  128 KB of it.
- Ethernet clock mode: stored as eth_clock_id_t in the ESP32's numbering
  and translated by name, like the PHY id.  The P4's eth_clock_mode_t is
  the IDF's emac_rmii_clock_mode_t, whose 0 is a deprecated default; only
  clock in (GPIO 50) translates there.
- P4 Ethernet defaults: the Waveshare wiring (IP101 as TLK110, address 1,
  MDC 31, MDIO 52, reset 51), board type 8.  The ESP32's put MDIO on an
  SDIO pin.
- Settings take pins up to GPIO 54, the P4's last, instead of 48.
- Radio defaults: SPI 32/33/27, CSN 46 (the framework's Waveshare
  variant), TX 2, RX 3.
- Web UI: a Waveshare ESP32-P4-ETH preset, the P4's clock mode, pin lists
  up to GPIO 54 without the pins the C6 link, Ethernet, USB and UART0 use.
- CI builds and releases both, with their ELFs; bootloader at 0x2000.
- ADR 0003: amended.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 19:41:39 +01:00

78 lines
No EOL
2.3 KiB
YAML

name: "🐛 Bug Report"
description: Create a new ticket for a bug.
labels: [
"bug"
]
body:
- type: dropdown
id: browsers
attributes:
label: "Hardware"
description: |
> What type of hardware is ESPSomfy RTS installed on?
> Information available at System > Firmware > Hardware : XXX
multiple: true
options:
- ESP32
- ESP32-S3
- ESP32-S2
- ESP32-C3
- ESP32 WT32-ETH01
- Olimex ESP32-PoE/EVB
- LilyGO T-Internet POE
- wESP POE
- Other
validations:
required: true
- type: input
validations:
required: true
attributes:
label: Firmware version
placeholder: v2.3.0
description: |
> Information available at System > Firmware > Firmware : v X.x.x
- type: input
validations:
required: true
attributes:
label: Application version
placeholder: v2.3.0
description: |
> Information available at System > Firmware > Application : v X.x.x
- type: textarea
id: description
attributes:
label: "What happened? What did you expect to happen?"
description: Please enter an explicit description of your issue
placeholder: Short and explicit description of your incident...
validations:
required: true
- type: textarea
id: reprod
attributes:
label: "How to reproduce it (step by step)"
description: Please enter an explicit description of your issue
value: |
1. Go to...
2. Click on...
...
render: bash
validations:
required: true
- type: textarea
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.
> 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, C6 and P4).
render: bash
validations:
required: false