shahpiyushv
commented
2 years ago @eos1d3 , I just tried this with esp idf v4.4 release and esp-rainmaker master branch on an esp32s3. Erased the flashed and then used idf.py flash monitor. I get this output
I (697) esp_claim: Initialising Assisted Claiming. This may take time.
I (1007) esp_claim: Private key already exists. No need to re-initialise it.
I (1057) esp_rmaker_node: Node ID ----- 84F7038005F4
I (1057) esp_rmaker_ota: OTA state = 2
I (1057) esp_rmaker_ota_using_params: OTA enabled with Params
I (1057) esp_rmaker_time_service: Time service enabled
I (1067) esp_rmaker_time: Initializing SNTP. Using the SNTP server: pool.ntp.org
I (1077) app_insights: Enable CONFIG_ESP_INSIGHTS_ENABLED to get Insights.
I (1077) esp_rmaker_core: Starting RainMaker Work Queue task
I (1087) esp_rmaker_work_queue: RainMaker Work Queue task started.
W (1087) BT_INIT: esp_bt_mem_release not implemented, return OK
I (1097) esp_claim: Waiting for assisted claim to finish.
I (1107) wifi_prov_scheme_ble: BT memory released
I (1107) app_wifi: Starting provisioning
I (1117) phy_init: phy_version 302,3ddfab3,Dec 3 2021,14:39:12
I (1167) wifi:mode : sta (84:f7:03:80:05:f4)
I (1177) wifi:enable tsf
W (1177) BT_INIT: esp_bt_controller_mem_release not implemented, return OK
I (1177) BT_INIT: BT controller compile version [6881869]
I (1177) BT_INIT: Bluetooth MAC: 84:f7:03:80:05:f6
I (1187) protocomm_nimble: BLE Host Task Started
I (1197) NimBLE: GAP procedure initiated: stop advertising.
I (1197) NimBLE: GAP procedure initiated: advertise;
I (1207) NimBLE: disc_mode=2
I (1207) NimBLE: adv_channel_map=0 own_addr_type=0 adv_filter_policy=0 adv_itvl_min=256 adv_itvl_max=256
I (1217) NimBLE:
I (1227) wifi_prov_mgr: Provisioning started with service name : PROV_77d8bb
I (1227) app_wifi: Provisioning started
I (1237) esp_rmaker_local: Event 1
I (1237) app_wifi: Scan this QR code from the ESP RainMaker phone app for Provisioning.
█▀▀▀▀▀█ ▄▄█ ▄█▄▄█▀▄▄▀█▄ █▀▀▀▀▀█
█ ███ █ ▀▄ ▄ ██▀█▄ ▀▄▄ █ ███ █
█ ▀▀▀ █ █▀█ █▀███ █▄ █▀▀█ █ ▀▀▀ █
▀▀▀▀▀▀▀ █ █▄▀ ▀ ▀▄▀ █▄█ █ ▀▀▀▀▀▀▀
█▀ ▀ ▄▀▀▄▄ ██▀▄▀█▄ ▄█ ▀ ▄█▀▀▄▀▀▄
▀██▀▄▀▀█▀▄▄██▄█▄ ▀██▀█ ▄▄ ▄█ █
▄▀ █ ▀█▄▄▀█ ▀▀ ▀█▄ █▄█▄▀█ ▄▄ ▀█
█▄██▀ ▀ ▄▀▀█ █ █▀ █▀▀█▀ ▄█ █▄
█▄▀▄█▀ ▄▄▄ █▄▄ █▀█▀██ ▄█▀ ▀▀▄ ▀
▀▄█▄██▀ █ ▀█▀▀ ▀█▄▄▀██ ▄ █▄▄▄ ▀█
▄▄█▀█▀▀▄ █▄ ▀▀▀█▄▀▀▀▀▀▄█ ▄▄ █ ▄▄
▀██▀▄▄▀ ▀▄▀ █▄▄▀▀▀▀█▄▀▄▀█ ▄▄ ▀▀
▀ ▀ ▀▀ ██ ▄█▀ ▀▀▀▄▀██ █▀▀▀█▀ ▄▄
█▀▀▀▀▀█ ▀█▄ █▄█ ▀█ ▄ █▀▀█ ▀ ██ █
█ ███ █ ▄█▄▀▀▄█ █▀▀▀ ██ ▀████▀ ▄█
█ ▀▀▀ █ ▄█ ▄▄▀▀▄▀█▀▄▄▄█ ▀ ▄▀█▀▀▀
▀▀▀▀▀▀▀ ▀ ▀▀ ▀ ▀ ▀ ▀ ▀▀ ▀
I (1437) app_wifi: If QR code is not visible, copy paste the below URL in a browser.
https://rainmaker.espressif.com/qrcode.html?data={"ver":"v1","name":"PROV_77d8bb","pop":"4eaddc87","transport":"ble"}
I (1457) app_wifi: Provisioning Started. Name : PROV_77d8bb, POP : 4eaddc87So, it is hard to tell what the problem could be. Can you double check that your flash was erased before you flashed the firmware. Can you double check that your partition table is right? It is printed on boot-up
I (46) boot: Partition Table:
I (49) boot: ## Label Usage Type ST Offset Length
I (57) boot: 0 sec_cert unknown 3f 06 0000d000 00003000
I (64) boot: 1 nvs WiFi data 01 02 00010000 00006000
I (72) boot: 2 otadata OTA data 01 00 00016000 00002000
I (79) boot: 3 phy_init RF data 01 01 00018000 00001000
I (87) boot: 4 ota_0 OTA app 00 10 00020000 00190000
I (94) boot: 5 ota_1 OTA app 00 11 001b0000 00190000
I (101) boot: 6 fctry WiFi data 01 02 00340000 00006000
I (109) boot: End of partition table
eos1d3
MahendraDnkTech
ESP-IDF version: Release 4.4 ESP device: ESP32-S3 LED_Light example
There are errors after Assisted Claiming:
BTW, there are some warnings during compilation:
PS: Try using r
ainmaker.py claimto write claiming dat to the chip, it seems the data is ignored and problem is still the same.