Wifi won't connect on certain boards

[petersen1]

I have an Adafruit Feather ESP32 and three DFRobot Firebeetle ESP32. While all the wifi examples I try work flawlessly on the Adafruit ESP32, none of them work for any of the Firebeetles. So there must be a systematic difference, I just can't figure out what the problem is. Wifi scanning for example works flawlessly.

I flashed the wifi example:
https://github.com/espressif/esp-idf/bl ... ple_main.c

DFRobot log:

Code: Select all

I (30) boot: ESP-IDF v4.0-dev-804-g70b2c86ff 2nd stage bootloader
I (30) boot: compile time 17:44:09
I (39) boot: Enabling RNG early entropy source...
I (39) boot: SPI Speed      : 40MHz
I (40) boot: SPI Mode       : DIO
I (44) boot: SPI Flash Size : 8MB
I (48) boot: Partition Table:
I (52) boot: ## Label            Usage          Type ST Offset   Length
I (59) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (67) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (74) boot:  2 factory          factory app      00 00 00010000 00100000
I (82) boot: End of partition table
I (86) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x14148 ( 82248) map
I (124) esp_image: segment 1: paddr=0x00024170 vaddr=0x3ffb0000 size=0x02f40 ( 12096) load
I (129) esp_image: segment 2: paddr=0x000270b8 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _WindowOverflow4 at /Users/clemens/workspace/epaper/esp-idf/components/freertos/xtensa_vectors.S:1778

I (131) esp_image: segment 3: paddr=0x000274c0 vaddr=0x40080400 size=0x08b50 ( 35664) load
I (154) esp_image: segment 4: paddr=0x00030018 vaddr=0x400d0018 size=0x6723c (422460) map
0x400d0018: _stext at ??:?

I (304) esp_image: segment 5: paddr=0x0009725c vaddr=0x40088f50 size=0x06f70 ( 28528) load
0x40088f50: rcUpdateTxDone at ??:?

I (326) boot: Loaded app from partition at offset 0x10000
I (326) boot: Disabling RNG early entropy source...
I (327) cpu_start: Pro cpu up.
I (330) cpu_start: Application information:
I (335) cpu_start: Project name:     wifi_station
I (341) cpu_start: App version:      v4.0-dev-804-g70b2c86ff-dirty
I (347) cpu_start: Compile time:     Jun 13 2019 17:48:08
I (353) cpu_start: ELF file SHA256:  3148b8e6032dd3d8...
I (359) cpu_start: ESP-IDF:          v4.0-dev-804-g70b2c86ff-dirty
I (366) cpu_start: Starting app cpu, entry point is 0x40081080
0x40081080: call_start_cpu1 at /Users/clemens/workspace/epaper/esp-idf/components/esp32/cpu_start.c:265

I (0) cpu_start: App cpu up.
I (377) heap_init: Initializing. RAM available for dynamic allocation:
I (384) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (390) heap_init: At 3FFB8DF8 len 00027208 (156 KiB): DRAM
I (396) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (402) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (409) heap_init: At 4008FEC0 len 00010140 (64 KiB): IRAM
I (415) cpu_start: Pro cpu start user code
I (433) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (456) wifi station: ESP_WIFI_MODE_STA
I (476) wifi: wifi driver task: 3ffc0674, prio:23, stack:3584, core=0
I (476) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (476) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (536) wifi: wifi firmware version: ec61a20
I (536) wifi: config NVS flash: enabled
I (536) wifi: config nano formating: disabled
I (536) wifi: Init dynamic tx buffer num: 32
I (546) wifi: Init data frame dynamic rx buffer num: 32
I (546) wifi: Init management frame dynamic rx buffer num: 32
I (556) wifi: Init management short buffer num: 32
I (556) wifi: Init static rx buffer size: 1600
I (566) wifi: Init static rx buffer num: 10
I (566) wifi: Init dynamic rx buffer num: 32
W (596) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration
I (736) phy: phy_version: 4100, 2a5dd04, Jan 23 2019, 21:00:07, 0, 2
I (746) wifi: mode : sta (24:0a:c4:a6:ba:d8)
I (756) wifi station: wifi_init_sta finished.
I (756) wifi station: connect to ap SSID:1 password:123456
I (876) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (1856) wifi: state: init -> auth (b0)
I (2856) wifi: state: auth -> init (200)
I (2856) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (2866) wifi station: retry to connect to the AP
I (2866) wifi station: connect to the AP fail
I (4916) wifi station: retry to connect to the AP
I (4916) wifi station: connect to the AP fail
I (5036) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (5036) wifi: state: init -> auth (b0)
I (6036) wifi: state: auth -> init (200)
I (6036) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (6036) wifi station: retry to connect to the AP
I (6046) wifi station: connect to the AP fail
I (8096) wifi station: retry to connect to the AP
I (8096) wifi station: connect to the AP fail
I (8216) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (8216) wifi: state: init -> auth (b0)
I (9216) wifi: state: auth -> init (200)
I (9216) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (9216) wifi station: retry to connect to the AP
I (9216) wifi station: connect to the AP fail
I (11266) wifi station: connect to the AP fail

[fivdiAtESP32]

The DFRobot log shows the following:

Code: Select all

I (756) wifi station: connect to ap SSID:1 password:123456

Are the SSID and password for the access point really 1 and 123456? Or did you forget to modify the code and set the SSID and password to the correct values?

[WiFive]

If you are using the same binary on both boards it would suggest a hardware issue. Dfrobot uses a clone of wroom32 but adafruit uses official wroom32 and the boards have different power supply components.

[petersen1]

The ssid and password are not the issue.

I am using the same binary for all boards. I noticed just now that the DFRobots work when I go really close to the WiFi station. Like laying the board right on top of it. Then it connects. Move 20cm away and it does not connect anymore. Weird. It is the same with all three DFRobot boards I have.