Anyone using Homekit? Need an answer about the IDF install. (SOLVED)

[fly135]

I've cloned the Homekit SDK. However it installed v3.0 of the IDF. The documentation says that I need to run a patch on v3.0. But MSYS32 doesn't have the patch command installed. It appears that the docs assume your dev machine is Linux, or you are a wiz at addons for msys. I searched for adding patch to MSYS32 but ended up finding mostly broken links.

The docs say that the patch isn't needed for v3.1. Is the solution as simple as cloning v3.1 IDF into the esp-idf directory in the Homekit SDK? We are using v3.1 for our development and would rather use it anyway.

John A

[fly135]

More info. Even though the HomeKit has a sub directory called esp-idf that is intended to hold the IDF, I already have the v3.1 IDF installed in a different directory with the appropriate $IDF_PATH. I compiled the accessory/fan example and it promptly crashed during wifi init in esp_wifi_init_internal, so there is no finding the reason why.

Do I also need to install the v3.1 IDF in the HomeKit directory? Is that likely why it crashed? If so then can I use that IDF install for all my builds that aren't Homekit?

The call to the wifi init is from hap_init, which apparently is also a binary.

John A

[fly135]

I moved the IDF v3.1 release into the esp-idf folder under esp-homekit-sdk, but it the accessory/fan app still crashes in the same way.

Code: Select all

.c 371 
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (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:0x3fff0018,len:4
load:0x3fff001c,len:6204
load:0x40078000,len:9828
load:0x40080000,len:6764
entry 0x40080350
I (29) boot: ESP-IDF esp_homekit_release_2.1.r2 2nd stage bootloader
I (29) boot: compile time 15:41:22
I (29) boot: Enabling RNG early entropy source...
I (35) qio_mode: Enabling default flash chip QIO
I (40) boot: SPI Speed      : 40MHz
I (45) boot: SPI Mode       : QIO
I (48) boot: SPI Flash Size : 4MB
I (53) boot: Partition Table:
I (56) boot: ## Label            Usage          Type ST Offset   Length
I (63) boot:  0 nvs              WiFi data        01 02 00009000 00004000
I (71) boot:  1 otadata          OTA data         01 00 0000d000 00002000
I (78) boot:  2 phy_init         RF data          01 01 0000f000 00001000
I (86) boot:  3 ota_0            OTA app          00 10 00010000 00180000
I (93) boot:  4 ota_1            OTA app          00 11 00190000 00180000
I (101) boot:  5 factory_nvs      WiFi data        01 02 00310000 00004000
I (108) boot: End of partition table
E (113) boot: ota data partition invalid and no factory, will try all partitions
I (121) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x284a4 (165028) map
I (179) esp_image: segment 1: paddr=0x000384cc vaddr=0x3ffc0000 size=0x03210 ( 12816) load
I (183) esp_image: segment 2: paddr=0x0003b6e4 vaddr=0x3ffc3210 size=0x00000 (     0) load
I (185) esp_image: segment 3: paddr=0x0003b6ec vaddr=0x40080000 size=0x00400 (  1024) load
I (195) esp_image: segment 4: paddr=0x0003baf4 vaddr=0x40080400 size=0x0451c ( 17692) load
I (210) esp_image: segment 5: paddr=0x00040018 vaddr=0x400d0018 size=0xac9bc (707004) map
I (422) esp_image: segment 6: paddr=0x000ec9dc vaddr=0x4008491c size=0x0aed4 ( 44756) load
I (439) esp_image: segment 7: paddr=0x000f78b8 vaddr=0x400c0000 size=0x00000 (     0) load
I (439) esp_image: segment 8: paddr=0x000f78c0 vaddr=0x50000000 size=0x00000 (     0) load
I (455) boot: Loaded app from partition at offset 0x10000
I (455) boot: Disabling RNG early entropy source...
I (457) cpu_start: Pro cpu up.
I (461) cpu_start: Single core mode
I (465) heap_init: Initializing. RAM available for dynamic allocation:
I (472) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (478) heap_init: At 3FFCA850 len 000157B0 (85 KiB): DRAM
I (484) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (491) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (497) heap_init: At 4008F7F0 len 00010810 (66 KiB): IRAM
I (503) cpu_start: Pro cpu start user code
I (73) cpu_start: Starting scheduler on PRO CPU.
Keystore initialised
Accessory is not Paired with any controller
Database initialised. Accessory Device ID: 97:C3:22:48:7C:81
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x4013d8a4  PS      : 0x00060b30  A0      : 0x8013d90c  A1      : 0x3ffcf600  
A2      : 0x00000054  A3      : 0x3ffca998  A4      : 0x3ffcf574  A5      : 0x00000000  
A6      : 0x00000011  A7      : 0xff000000  A8      : 0x00000000  A9      : 0x3ffc5b84  
A10     : 0x00000000  A11     : 0x00000004  A12     : 0x3ffcf574  A13     : 0x3ffca998  
A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000004  EXCCAUSE: 0x0000001c  
EXCVADDR: 0x00000054  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffb  

Backtrace: 0x4013d8a4:0x3ffcf600 0x4013d909:0x3ffcf620 0x4013d039:0x3ffcf650 0x400e73f3:0x3ffcf670 0x400e5c54:0x3ffcf6e0 0x400d3615:0x3ffcf710

Rebooting...

[fly135]

Got an immediate answer on Espressif GitLab. Maybe there is no activity on this forum for HomeKit because of the NDA. Not really sure if issues should be discussed here at all.

John A