Feat/jc esp32p4 m3 dev

[dvucinozd]

Description

This PR adds and hardens support for the Guiton JC-ESP32P4-M3-DEV board in esp-claw using the esp_board_manager workflow.

What changed

• Added/updated board definition files under:
  • application/edge_agent/boards/guiton/jc_esp32p4_m3_dev/
  • board_info.yaml
  • board_peripherals.yaml
  • board_devices.yaml
  • setup_device.c
  • sdkconfig.defaults.board
• Added optional OV5647 low-light tuning profile:
  • ov5647_low_light.json
• Updated board README to be upstream-ready (no local machine paths, reproducible validation command).
• Integrated and validated the board through Board Manager generation flow:
  • idf.py bmgr -c ./boards -b jc_esp32p4_m3_dev
• Stabilized runtime bring-up:
  • Disabled fs_spiffs device bring-up for this board profile (SD card FAT is primary storage).
  • Time-sync startup behavior was improved to wait for real STA connectivity before SNTP sync.
• Camera path improvements:
  • Updated OV5647 defaults and JPEG quality settings for better captured image quality.

Motivation / context

This board is a new hardware target and needed complete board metadata + stable runtime behavior before upstreaming.
The goal is reliable boot, Wi-Fi onboarding, camera availability, and clean board-manager generation with minimal local workarounds.

Related

• Related local branch work: feat/jc-esp32p4-m3-dev
• Board manager guide followed:
  • https://github.com/espressif/esp-gmf/blob/main/packages/esp_board_manager/docs/how_to_customize_board.md

Testing

Tested on physical JC-ESP32P4-M3-DEV hardware via COM3.

Validation performed

1. Board config generation:

   • idf.py bmgr -c ./boards -b jc_esp32p4_m3_dev
   • Result: peripherals/devices validated successfully.

2. Build:

   • idf.py build
   • Result: success.

3. Flash:

   • idf.py -p COM3 flash
   • Result: success.

4. Boot/runtime log checks:

   • Verified successful boot without reboot loop.
   • Verified STA obtains IP and app reaches prompt.
   • Verified Telegram polling path continues normally.
   • Verified camera initializes as /dev/video0.
   • Verified fs_spiffs mount failure logs are removed after disabling SPIFFS device init on this board profile.
   • Display remains intentionally headless-safe when LCD path is unavailable (init_skip behavior preserved).

Environment:

• ESP-IDF v5.5.4
• Windows host
• Real hardware (not emulated)

---

Checklist

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[CLAassistant]

All committers have signed the CLA.

[laride]

Thanks for the PR!

I noticed that this PR includes both support for a new development board and several core logic changes. To make the review process easier and keep the scope clearer, could you please split them into separate PRs?

[dvucinozd]

Will do. Thanks sub, 9. svi 2026. 14:41 laride ***@***.***> je napisao:

…

*laride* left a comment (espressif/esp-claw#53) <#53 (comment)> Thanks for the PR! I noticed that this PR includes both support for a new development board and several core logic changes. To make the review process easier and keep the scope clearer, could you please split them into separate PRs? — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN5G5QKASBDP4WX7VFUEAPT4Z4RORAVCNFSM6AAAAACYVGRLAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJSGU2DGMBZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>