Closed lida2003 closed 8 months ago
It works.
Hope there is a good solution. But it can be tested now!
diff --git a/main/main.c b/main/main.c
index 5101b0e..0583fce 100644
--- a/main/main.c
+++ b/main/main.c
@@ -168,7 +168,7 @@ void init_wifi(void) {
ESP_ERROR_CHECK(esp_wifi_set_protocol(WIFI_IF_AP, WIFI_PROTOCOL_11B));
ESP_ERROR_CHECK(esp_wifi_set_config(WIFI_IF_AP, &wifi_config));
wifi_country_t wifi_country = {.cc = "XX", .schan = 1, .nchan = 13, .policy = WIFI_COUNTRY_POLICY_MANUAL};
- ESP_ERROR_CHECK(esp_wifi_set_country(&wifi_country));
+ //ESP_ERROR_CHECK(esp_wifi_set_country(&wifi_country));
ESP_ERROR_CHECK(esp_wifi_start());
esp_netif_ip_info_t ip;
my ESP32 board stucks now also in this boot loop.... I also wanted to reflash mine, but esptool stucks always on SYNC, and also idf.py -p COM10 flash
wont connect. I connected with putty to the COM Port and there, when I press and hold the boot button and press the second button the esp boot loop stops and displays
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download
But when I close putty and try again with esptool or idf.py I cant connect. The same when I replug the USB port and redo the key sequence... no luck...
But however, my Idea was to change the line above your commented line to my country code DE....
EDIT: Damn!, got it running... maybe I released the boot button before the second one on my tests with esptool/idf.py Maybe it was because it was still connected to the Flightcontroller... dont know....
But now I flashed with the changed Country Code DE.
It should be problem with flashing. The code is OK and I have got this running without problem except that line(It can be commented, no problem.) Maybe the API(esp_wifi_set_country) should be checked or debuged. As ESP_ERROR_CHECK is very strict macro.
Fixed with release v1.2 - updated country code and esp-idf version to 4.4.6
I just use idf 4.3.5 + latest firmware(default), compile and flash, it reboots.
Any idea?