Smart Home Automation Forum

Pages: 1 2

Hi,

I bought a KC868-16A about one year ago and did some tests but I never used it because I didn't have time.
Now I want to finish my project, but the board has stopped responding completely.

I connected it via USB to get the logs:

Code:
ELF file SHA256: d62704405

Rebooting...

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:7112

load:0x40078000,len:15624

load:0x40080400,len:4

load:0x40080404,len:3876

entry 0x4008064c

[0;32mI (29) boot: ESP-IDF 5.1.5 2nd stage bootloader[0m

[0;32mI (29) boot: compile time Jan 18 2025 19:20:33[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (33) boot: chip revision: v3.1[0m

[0;32mI (37) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (42) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (46) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (51) boot: Enabling RNG early entropy source...[0m

[0;32mI (56) boot: Partition Table:[0m

[0;32mI (60) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (67) boot:  0 otadata          OTA data         01 00 00009000 00002000[0m

[0;32mI (75) boot:  1 phy_init         RF data          01 01 0000b000 00001000[0m

[0;32mI (82) boot:  2 app0             OTA app          00 10 00010000 001c0000[0m

[0;32mI (90) boot:  3 app1             OTA app          00 11 001d0000 001c0000[0m

[0;32mI (97) boot:  4 nvs              WiFi data        01 02 00390000 0006d000[0m

[0;32mI (105) boot: End of partition table[0m

[0;32mI (109) esp_image: segment 0: paddr=001d0020 vaddr=3f400020 size=1d6ech (120556) map[0m

[0;32mI (161) esp_image: segment 1: paddr=001ed714 vaddr=3ffb0000 size=025e4h (  9700) load[0m

[0;32mI (165) esp_image: segment 2: paddr=001efd00 vaddr=40080000 size=00318h (   792) load[0m

[0;32mI (167) esp_image: segment 3: paddr=001f0020 vaddr=400d0020 size=4c58ch (312716) map[0m

[0;32mI (288) esp_image: segment 4: paddr=0023c5b4 vaddr=40080318 size=09bfch ( 39932) load[0m

[0;32mI (305) esp_image: segment 5: paddr=002461b8 vaddr=50000000 size=00020h (    32) load[0m

[0;32mI (310) boot: Loaded app from partition at offset 0x1d0000[0m

[0;32mI (311) boot: Disabling RNG early entropy source...[0m

[0;32m[I][logger:120]: Log initialized[0m

[0;35m[C][safe_mode:136]: Unsuccessful boot attempts: 10[0m

[1;31m[E][safe_mode:148]: Boot loop detected[0m

[1;31m[E][component:420]: safe_mode set Error flag: unspecified[0m

[0;32m[I][app:089]: Running through setup()[0m

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000c04d:0x3ffbb670 0x40083db2:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

ELF file SHA256: d62704405

Rebooting...

[...]

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000bfed:0x3ffbb640 0x40085b1f:0x3ffbb650 0x40083a46:0x3ffbb670 0x40083da6:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

etc.

I disconnected everything (only left power and USB-C) and it still crashes.

I flashed it with the Kincony firmware but no response.
The serial log via USB is now:

Code:
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:6652

ho 0 tail 12 room 4

load:0x40078000,len:15052

load:0x40080400,len:3836

entry 0x4008069c

[0;32mI (29) boot: ESP-IDF v4.4.7 2nd stage bootloader[0m

[0;32mI (29) boot: compile time 15:12:15[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (32) boot: chip revision: v3.1[0m

[0;32mI (36) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (41) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (45) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (50) boot: Enabling RNG early entropy source...[0m

[0;32mI (55) boot: Partition Table:[0m

[0;32mI (59) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (66) boot:  0 nvs              WiFi data        01 02 00009000 00026000[0m

[0;32mI (74) boot:  1 phy_init         RF data          01 01 0003f000 00001000[0m

[0;32mI (81) boot:  2 factory          factory app      00 00 00040000 003b0000[0m

[0;32mI (89) boot: End of partition table[0m

[0;32mI (93) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=102078h (1056888) map[0m

[0;32mI (484) esp_image: segment 1: paddr=001420a0 vaddr=3ffb0000 size=0339ch ( 13212) load[0m

[0;32mI (489) esp_image: segment 2: paddr=00145444 vaddr=40080000 size=0abd4h ( 43988) load[0m

[0;32mI (508) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a7ca8h (687272) map[0m

[0;32mI (757) esp_image: segment 4: paddr=001f7cd0 vaddr=4008abd4 size=05228h ( 21032) load[0m

[0;32mI (773) boot: Loaded app from partition at offset 0x40000[0m

[0;32mI (774) boot: Disabling RNG early entropy source...[0m

[0;32mI (785) cpu_start: Multicore app[0m

[0;32mI (785) cpu_start: Pro cpu up.[0m

[0;32mI (786) cpu_start: Starting app cpu, entry point is 0x40081278[0m

[0;32mI (0) cpu_start: App cpu up.[0m

[0;32mI (805) cpu_start: Pro cpu start user code[0m

[0;32mI (806) cpu_start: cpu freq: 240000000[0m

[0;32mI (806) cpu_start: Application information:[0m

[0;32mI (810) cpu_start: Project name:     KC868_A16[0m

[0;32mI (815) cpu_start: App version:      v2.2.20[0m

[0;32mI (820) cpu_start: Compile time:     Apr  2 2026 15:12:09[0m

[0;32mI (826) cpu_start: ELF file SHA256:  b7c54ce742331a6d...[0m

[0;32mI (832) cpu_start: ESP-IDF:          v4.4.7[0m

[0;32mI (837) cpu_start: Min chip rev:     v0.0[0m

[0;32mI (842) cpu_start: Max chip rev:     v3.99 [0m

[0;32mI (847) cpu_start: Chip rev:         v3.1[0m

[0;32mI (852) heap_init: Initializing. RAM available for dynamic allocation:[0m

[0;32mI (859) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM[0m

[0;32mI (865) heap_init: At 3FFC5190 len 0001AE70 (107 KiB): DRAM[0m

[0;32mI (871) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM[0m

[0;32mI (877) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM[0m

[0;32mI (884) heap_init: At 4008FDFC len 00010204 (64 KiB): IRAM[0m

[0;32mI (891) spi_flash: detected chip: generic[0m

[0;32mI (895) spi_flash: flash io: dio[0m

[0;32mI (900) cpu_start: Starting scheduler on PRO CPU.[0m

[0;32mI (0) cpu_start: Starting scheduler on APP CPU.[0m

[0;32mI (914) main: [APP] Startup..[0m

[0;32mI (917) main: [APP] Free memory: 223808 bytes[0m

[0;32mI (922) main: [APP] IDF version: v4.4.7[0m

[0;32mI (985) NVS: save default system config.[0m

[0;32mI (991) NVS: save default network config.[0m

[0;32mI (997) NVS: save default tuya config.[0m

[0;32mI (1002) NVS: save default protocol config.[0m

[0;32mI (1009) NVS: save default input config.[0m

[0;32mI (1012) NVS: save default output config.[0m

[0;32mI (1017) NVS: save default name config.[0m

[0;32mI (1025) NVS: save default state.[0m

[0;32mI (1029) NVS: save default config.[0m

[0;32mI (1035) NVS: save default config.[0m

[0;32mI (1039) NVS: save default config.[0m

[0;32mI (1155) NVS: save default config.[0m

[0;32mI (1370) NVS: init nvs finish.[0m

[0;31mE (6371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (6371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (6371) task_wdt: Tasks currently running:[0m

[0;31mE (6371) task_wdt: CPU 0: main[0m

[0;31mE (6371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (6371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

[0;31mE (6371) task_wdt: Print CPU 1 backtrace[0m

Backtrace: 0x40085585:0x3FFB1190 0x40082C75:0x3FFB11B0 0x4000BFED:0x3FFC8550 0x4008CC92:0x3FFC8560 0x400F16BF:0x3FFC8580 0x400F16CB:0x3FFC85B0 0x400D4E16:0x3FFC85D0 0x4008AE18:0x3FFC85F0

[0;31mE (11371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (11371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (11371) task_wdt: Tasks currently running:[0m

[0;31mE (11371) task_wdt: CPU 0: main[0m

[0;31mE (11371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (11371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

etc.

Any idea why the watchdog is not reset?

What is your advice?

Kind regards

Vincent

which board you are using?
which firmware you downloaded?
please take photo with all details.

(04-13-2026, 01:51 AM)admin Wrote: [ -> ]which board you are using?
which firmware you downloaded?
please take photo with all details.

Thanks for your reply.

It is a Kincony KC868-A16 REV:1.6
I flashed KCS_KC868_A16_V2.2.20.zip from this thread https://www.kincony.com/forum/showthread.php?tid=9205
Here is a picture:
[attachment=9590]

Vincent

take a photo of your esp download tool screen. i want to see how you set.

(04-13-2026, 11:10 PM)admin Wrote: [ -> ]take a photo of your esp download tool screen. i want to see how you set.

I just did the procedure again:
[attachment=9592]

[attachment=9593]

[attachment=9594]

[attachment=9595]

Vincent

it's correct. after you downloaded firmware, re power on of board. connect with ethenret cable to router.
whether can use kincony scan device tool found the board?

I connected an Ethernet cable and powered the board again:
[attachment=9603]

I started the Scan Device Tool:
[attachment=9602]

I clicked "StartMonitorPort":
[attachment=9604]

Then clicked on "SCAN" and nothing appears on the left...

I think it is normal, because the log shows the board is still rebooting in a loop every 4-5 seconds due to a watchdog being triggered.
Can the ESP32 module be faulty ? Can I buy a new one and replace it ?

Which one should I select ? https://nl.aliexpress.com/item/1005005563638711.html

Vincent

you can try to replace ESP32 module, chose "ESP32-WROOM-32E-N4".

OK, I ordered a new module.
I'll let you know...

Vincent

Pages: 1 2

vdeconinck

admin

vdeconinck

admin

vdeconinck

admin

vdeconinck

admin

vdeconinck

admin