Settings not saved ? #138

psailleko · 2023-10-31T19:14:36Z

psailleko
Oct 31, 2023

Hello,

i've succesfully compiled and flashed (at least it seems ^^, thanks revk ) s3 version on my ESP32-S3-MINI-1

Sadly, in the UI at 10.190.72.1 everything i set is not "saved" .. i've configured Wifi SSID/PASSHPRASE then clicked on Change Settings ..
unit seems to reboot then .. nothing changed, not connected to my good/stable working wifi.

Even the hostname or Timezone is not saved and revert do default settings.

Do you have an idea about this behavior ?

revk · 2023-11-01T02:08:30Z

revk
Nov 1, 2023
Maintainer

That is new to me! Can you get a serial monitor going at the same time. There may be some error to explain it.

0 replies

psailleko · 2023-11-01T12:45:28Z

psailleko
Nov 1, 2023
Author

I've tryed many adapters/os/settings and i cannot get any serial monitoring :x
If i boot in flash mode i have serial monitoring and i can flash other esp32 images and get a serial monitoring.

Does the S3 build include tx/rx console on the pcb top raw (T R + 0 G), or maybee a specific baudrate ?

12 replies

revk Nov 1, 2023
Maintainer

There is one other option. There are 4 pads which are USB directly that you can connect to. That should also work for flash and monitor.

psailleko Nov 1, 2023
Author

i will try the "make flash monitor" then use the 4 usb pads as a last resort.

As i need to disconnect/reconnect my usb jig after flash it is "normal" that i cannot see the boot console, the software is loaded way before i can reconnect with console

revk Nov 1, 2023
Maintainer

Not sure why you need to disconnect and reconnect? Should be it boots after flash and monitor shows it.

psailleko Nov 1, 2023
Author

make flash monitor
`root@dev:~/ESP32-Faikin/ESP32# make flash monitor
idf.py flash
Executing action: flash
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Running ninja in directory /root/ESP32-Faikin/ESP32/build
Executing "ninja flash"...
[1/1] cd /root/ESP32-Faikin/ESP32/build/bootloader/esp-idf/esptool_py && /root/.espressif...y --offset 0x8000 bootloader 0x0 /root/ESP32-Faikin/ESP32/build/bootloader/bootloader.bin
Bootloader binary size 0x3610 bytes. 0x49f0 bytes (58%) free.
[8/11] Generating binary image from built executable
esptool.py v4.7.dev2
Creating esp32s3 image...
Merged 2 ELF sections
Successfully created esp32s3 image.
Generated /root/ESP32-Faikin/ESP32/build/Faikin-unsigned.bin
[9/11] Generating signed binary image
espsecure.py v4.7.dev2
1 signing key(s) found.
Signed 1310720 bytes of data from /root/ESP32-Faikin/ESP32/build/Faikin-unsigned.bin. Signature sector now has 1 signature blocks.
Generated signed binary image /root/ESP32-Faikin/ESP32/build/Faikin.bin from /root/ESP32-Faikin/ESP32/build/Faikin-unsigned.bin
[10/11] cd /root/ESP32-Faikin/ESP32/build/esp-idf/esptool_py && /root/.espressif/python_e...ESP32/build/partition_table/partition-table.bin /root/ESP32-Faikin/ESP32/build/Faikin.bin
Faikin.bin binary size 0x141000 bytes. Smallest app partition is 0x1e0000 bytes. 0x9f000 bytes (33%) free.
[10/11] cd /root/esp/esp-idf/components/esptool_py && /usr/bin/cmake -D IDF_PATH=/root/es...ESP32-Faikin/ESP32/build -P /root/esp/esp-idf/components/esptool_py/run_serial_tool.cmake
esptool.py --chip esp32s3 -p /dev/ttyUSB0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 40m --flash_size keep 0x0 bootloader/bootloader.bin 0x10000 Faikin.bin 0x8000 partition_table/partition-table.bin 0xd000 ota_data_initial.bin
esptool.py v4.7.dev2
Serial port /dev/ttyUSB0
Connecting...
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded Flash 4MB (XMC), Embedded PSRAM 2MB (AP_3v3)
Crystal is 40MHz
MAC: 70:04:1d:cd:be:48
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00003fff...
Flash will be erased from 0x00010000 to 0x00150fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000d000 to 0x0000efff...
Compressed 13840 bytes to 9614...
Writing at 0x00000000... (100 %)
Wrote 13840 bytes (9614 compressed) at 0x00000000 in 0.5 seconds (effective 234.1 kbit/s)...
Hash of data verified.
Compressed 1314816 bytes to 844228...
Writing at 0x0014b9fb... (100 %)
Wrote 1314816 bytes (844228 compressed) at 0x00010000 in 22.4 seconds (effective 469.0 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 194...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (194 compressed) at 0x00008000 in 0.1 seconds (effective 424.6 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Writing at 0x0000d000... (100 %)
Wrote 8192 bytes (31 compressed) at 0x0000d000 in 0.1 seconds (effective 608.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Done
idf.py monitor
Executing action: monitor
Serial port /dev/ttyUSB0
Connecting.......................
/dev/ttyUSB0 failed to connect: Failed to connect to Espressif device: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
No serial ports found. Connect a device, or use '-p PORT' option to set a specific port.
make: *** [Makefile:55: monitor] Error 2
root@dev:~/ESP32-Faikin/ESP32#
`

It seems that the "Hard resetting via RTS pin" is not working ... it is why i need to unplug/replug to reset the board with new firmware, if i let it connected after flash the board seems to be in "stuck state" as i cannot reflash it, i need to disconnect/reconnect to use the new firmware or disconnect/reconnect with D0 shorted to ground to return in flash mode...

This is not normal ?

revk Nov 1, 2023
Maintainer

Ah ok, there is no RST on that connector, as I use a "tasmotiser" board for this (also on amazon) which power cycles on RST. I forget that this is not how your average USB works.

Ok the direct USB should totally solve that for you. The pins should be obvious.

psailleko · 2023-11-01T15:30:51Z

psailleko
Nov 1, 2023
Author

Well .... i'll give up for today ....

Soldered USB cable , rpi powered trough a bench power supply set at 5V 4A ...

The module reboot when console connect (go from flashing violet to white then red, i can see a little spike in current 0.7A instead of 0.5 when it happen) and console crash ..

I hope it's not a hardware production problem .. i have 20 of them :o

(off topic but i was very happy to see that WSL2 don't support serial ..... )

root@dev:~/ESP32-Faikin/ESP32# make monitor
idf.py monitor
Executing action: monitor
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Running idf_monitor in directory /root/ESP32-Faikin/ESP32
Executing "/root/.espressif/python_env/idf5.2_py3.11_env/bin/python /root/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyACM0 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 --revision 0 /root/ESP32-Faikin/ESP32/build/Faikin.elf -m '/root/.espressif/python_env/idf5.2_py3.11_env/bin/python' '/root/esp/esp-idf/tools/idf.py'"...
--- esp-idf-monitor 1.3.3 on /dev/ttyACM0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40048d1a
0x40048d1a: uart_rx_one_char in ROM

SPIWP:0xee
mode:DIO, clock div:2
load:0x3fce3810,len:0x48c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xa4c
load:0x403cc700,len:0x26d8
entry 0x403c986c
None
Waiting for the device to reconnectException in thread Thread-2 (_run_outer):
Traceback (most recent call last):
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 76, in run
    data = self.serial.read(self.serial.in_waiting or 1)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/serial/serialposix.py", line 595, in read
    raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 83, in run
    self.close_serial()
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 104, in close_serial
    self._disable_closing_wait_or_discard_data()
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 120, in _disable_closing_wait_or_discard_data
    buf = fcntl.ioctl(self.serial.fd, termios.TIOCGSERIAL, buf)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 5] Input/output error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.11/threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/stoppable_thread.py", line 47, in _run_outer
    self.run()
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 100, in run
    self.close_serial()
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 104, in close_serial
    self._disable_closing_wait_or_discard_data()
  File "/root/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages/esp_idf_monitor/base/serial_reader.py", line 120, in _disable_closing_wait_or_discard_data
    buf = fcntl.ioctl(self.serial.fd, termios.TIOCGSERIAL, buf)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 5] Input/output error

root@dev:~/ESP32-Faikin/ESP32# make monitor
idf.py monitor
Executing action: monitor
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Running idf_monitor in directory /root/ESP32-Faikin/ESP32
Executing "/root/.espressif/python_env/idf5.2_py3.11_env/bin/python /root/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyACM0 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 --revision 0 /root/ESP32-Faikin/ESP32/build/Faikin.elf -m '/root/.espressif/python_env/idf5.2_py3.11_env/bin/python' '/root/esp/esp-idf/tools/idf.py'"...
--- esp-idf-monitor 1.3.3 on /dev/ttyACM0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40048ee5
0x40048ee5: recv_packet in ROM

SPIWP:0xee
mode:DIO, clock div:2
load:0x3fce3810,len:0x48c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xa4c
load:0x403cc700,len:0x26d8
entry 0x403c986c
E (1065) httpd: httpd_server_init: error in listen (112)

5 replies

revk Nov 1, 2023
Maintainer

Ok the very end of that looks promising. Does it then do WiFi etc?

psailleko Nov 1, 2023
Author

Here the main window, in hostname i write test in SSID i put a good know working SSID and password
(i even created a really dumb network with dumb password for testing),
i'll set the hostname of my mosquitto server / user / pass then i click on change settings,
page seems to reload, i lost ping for a few seconds then ping OK again and i get the same page except that there is :

WiFi did not connect, try again. on top of Wifi not configured.

no logs in my opensense router about a dhcp request.
no logs about a connection attempt on my unifi wifi system
and none of the configured options remains, no test as hostname or others options ...
dark mode don't work either .. i set it to on, page refresh but led don't change and option reset to off

i will try with another pcb

revk Nov 1, 2023
Maintainer

Ok I can suggest some debug in the code maybe. Not at my desk. Maybe in a bit.

revk Nov 1, 2023
Maintainer

I assume 2.4GHz WiFi

revk Nov 1, 2023
Maintainer

If you just, say, change dark mode, no other setting, does that save?

psailleko · 2023-11-01T16:20:18Z

psailleko
Nov 1, 2023
Author

2.4GHz dedicated to domotic

For dark mode => i click on "Dark Mode" "On" then on "Change settings" :> webpage reload with message No Wifi SSID and "Dark Mode" is Off like before, no change on display, same webpage.

7 replies

revk Nov 1, 2023
Maintainer

Not sure of the http error but not surprised, I'd have to check reproducing it here. The fact it only logs that little is pretty sensible. You can enable a lot more logging if you want, obviously. But that looks like it is running, yes. The manual covers what the colours should mean.

psailleko Nov 1, 2023
Author

with the changes you provided:

fresh flash, change hostname and click on Change settings (no effect)
in make monitor :

E (42845) httpd_txrx: httpd_resp_send_err: error calling setsockopt : 22
E (48637) RevK: Length 114

while setting AP config : (ap name 9 chars lenght pass : 8 chars if it helps)

E (157581) RevK: Length 127

revk Nov 1, 2023
Maintainer

Ok it needs more debug lines adding through the various processing.

I can probably look tomorrow, but you can probably work out a few more levels of debug you could add.

psailleko Nov 1, 2023
Author

Thanks for your support

revk Nov 2, 2023
Maintainer

OK some more suggestions.

Use make menuconfig to make some changed.

Change logging: Component config --> Log output --> Default log verbosity to Info
Set the default WIFi: Component config --> RevK --> Default WiFi SSID / Default WiFi passphrase

Reflash. This should show a lot more debug, including trying to connect to WiFi and getting an IP.

psailleko · 2023-11-02T09:54:15Z

psailleko
Nov 2, 2023
Author

Heyy .. plenty of logs

but sadly no wifi connection, tested with my main domotic wifi and to be sure that it's not a range problem tested with my 2.4 access point dedicated to this test at 50 centimeters of the module : KO
(no sensible informations in logs) ^^

AS the AP mode is working we can exclude an antenna/wifi module problem .. ?

`root@dev:~/ESP32-Faikin/ESP32# make monitor
idf.py monitor
Executing action: monitor
Serial port /dev/ttyACM0
Connecting....
Detecting chip type... ESP32-S3
Running idf_monitor in directory /root/ESP32-Faikin/ESP32
Executing "/root/.espressif/python_env/idf5.2_py3.10_env/bin/python /root/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyACM0 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 --revision 0 /root/ESP32-Faikin/ESP32/build/Faikin.elf -m '/root/.espressif/python_env/idf5.2_py3.10_env/bin/python' '/root/esp/esp-idf/tools/idf.py'"...
--- esp-idf-monitor 1.3.3 on /dev/ttyACM0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x400490d5
0x400490d5: usb_uart_device_rx_one_char in ROM

I (1503) RevK: WiFi STA [test]
I (1508) RevK: Dynamic IP start
I (1509) phy_init: phy_version 620,ec7ec30,Sep 5 2023,13:49:13
I (1581) wifi:mode : sta (70:04:1d:cd:be:48)
I (1583) wifi:enable tsf
I (1586) RevK: STA Start
I (1595) gpio: GPIO[47]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1598) RevK: Up 1, Link down 1
W (1600) wifi:Haven't to connect to a suitable AP now!
I (1614) wifi:Set ps type: 0, coexist: 0

I (1615) Faikin: Trying X50
I (1616) gpio: GPIO[34]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1621) gpio: GPIO[48]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (2002) RevK: Up 2, Link down 1
W (2003) wifi:Haven't to connect to a suitable AP now!
I (3002) RevK: Up 3, Link down 2
W (3003) wifi:Haven't to connect to a suitable AP now!
I (4000) RevK: Up 4, Link down 3
W (4001) wifi:Haven't to connect to a suitable AP now!
I (4012) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
I (4014) wifi:state: init -> auth (b0)
I (4020) wifi:state: auth -> assoc (0)
I (4050) wifi:state: assoc -> run (10)
I (5000) RevK: Up 5, Link down 4
I (6000) RevK: Up 6, Link down 5
I (7000) RevK: Up 7, Link down 6
I (7075) wifi:state: run -> init (fc0)
I (7077) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
I (7080) RevK: STA Disconnect
I (8002) RevK: Up 8, Link down 7
W (8003) wifi:Haven't to connect to a suitable AP now!
I (9000) RevK: Up 9, Link down 8
W (9002) wifi:Haven't to connect to a suitable AP now!
I (9507) RevK: STA Disconnect
I (10002) RevK: Up 10, Link down 9
W (10003) wifi:Haven't to connect to a suitable AP now!
I (11001) RevK: Up 11, Link down 10
W (11003) wifi:Haven't to connect to a suitable AP now!
I (11933) RevK: STA Disconnect
I (12001) RevK: Up 12, Link down 11
W (12002) wifi:Haven't to connect to a suitable AP now!
I (12003) RevK: APSTA config mode start Faikin-70041DCDBE48
E (12007) httpd: httpd_server_init: error in listen (112)
I (12014) wifi:I (12014) RevK: Dummy DNS start
mode : sta (70:04:1d:cd:be:48) + softAP (70:04:1d:cd:be:49)
I (12023) wifi:Total power save buffer number: 8
I (12027) wifi:Init max length of beacon: 752/752
I (12031) wifi:Init max length of beacon: 752/752
I (12041) wifi:ifx:1, phymode(new:0x3, nvs:0x3)
I (12045) wifi:Total power save buffer number: 8
W (12052) wifi:Affected by the ESP-NOW encrypt num, set the max connection num to 10
I (12055) wifi:Total power save buffer number: 8
I (12059) esp_netif_lwip: DHCP server started on interface WIFI_AP_DEF with IP: 10.190.72.1
I (12065) RevK: AP Start
I (12070) RevK: AP Stop
I (12073) esp_netif_lwip: DHCP server started on interface WIFI_AP_DEF with IP: 10.190.72.1
I (12081) RevK: AP Start
I (12085) RevK: AP Stop
I (12091) esp_netif_lwip: DHCP server started on interface WIFI_AP_DEF with IP: 10.190.72.1
I (12096) RevK: AP Start
I (13002) RevK: Up 13, Link down 12
W (13005) wifi:Haven't to connect to a suitable AP now!
I (14000) RevK: Up 14, Link down 13
W (14002) wifi:Haven't to connect to a suitable AP now!
I (14789) RevK: STA Disconnect
I (15002) RevK: Up 15, Link down 14
W (15003) wifi:Haven't to connect to a suitable AP now!
I (16001) RevK: Up 16, Link down 15
W (16003) wifi:Haven't to connect to a suitable AP now!
I (17001) RevK: Up 17, Link down 16
W (17002) wifi:Haven't to connect to a suitable AP now!
I (17642) wifi:ap channel adjust o:1,1 n:11,2
I (17643) wifi:new:<11,0>, old:<1,1>, ap:<11,2>, sta:<11,0>, prof:1
I (17645) wifi:state: init -> auth (b0)
I (17650) wifi:state: auth -> assoc (0)
I (17679) wifi:state: assoc -> run (10)
I (18002) RevK: Up 18, Link down 17
I (19002) RevK: Up 19, Link down 18
I (20002) RevK: Up 20, Link down 19
I (20703) wifi:state: run -> init (fc0)
I (20704) wifi:new:<11,0>, old:<11,0>, ap:<11,2>, sta:<11,0>, prof:1
I (20707) RevK: STA Disconnect
I (21002) RevK: Up 21, Link down 20
W (21003) wifi:Haven't to connect to a suitable AP now!
I (22002) RevK: Up 22, Link down 21
W (22003) wifi:Haven't to connect to a suitable AP now!
I (23000) RevK: Up 23, Link down 22
W (23001) wifi:Haven't to connect to a suitable AP now!
I (23561) RevK: STA Disconnect
I (24001) Faikin: Trying S21
I (24002) RevK: Up 24, Link down 23
W (24004) wifi:Haven't to connect to a suitable AP now!
I (24004) gpio: GPIO[34]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (24014) gpio: GPIO[48]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (25001) RevK: Up 25, Link down 24
W (25002) wifi:Haven't to connect to a suitable AP now!
I (26001) RevK: Up 26, Link down 25
W (26002) wifi:Haven't to connect to a suitable AP now!
I (26416) wifi:new:<11,2>, old:<11,0>, ap:<11,2>, sta:<11,0>, prof:1
I (26418) wifi:state: init -> auth (b0)
I (26424) wifi:state: auth -> assoc (0)
I (26432) wifi:state: assoc -> run (10)
I (27001) RevK: Up 27, Link down 26
I (28002) RevK: Up 28, Link down 27
I (29002) RevK: Up 29, Link down 28
I (29453) wifi:state: run -> init (fc0)
I (29454) wifi:new:<11,0>, old:<11,2>, ap:<11,2>, sta:<11,0>, prof:1
I (29458) RevK: STA Disconnect
I (30002) RevK: Up 30, Link down 29
W (30003) wifi:Haven't to connect to a suitable AP now!
I (31002) RevK: Up 31, Link down 30
W (31003) wifi:Haven't to connect to a suitable AP now!
I (32000) RevK: Up 32, Link down 31
W (32002) wifi:Haven't to connect to a suitable AP now!
I (32311) RevK: STA Disconnect
I (33001) RevK: Up 33, Link down 32
W (33002) wifi:Haven't to connect to a suitable AP now!
I (34002) RevK: Up 34, Link down 33
W (34003) wifi:Haven't to connect to a suitable AP now!
I (35000) RevK: Up 35, Link down 34
W (35001) wifi:Haven't to connect to a suitable AP now!
I (35166) wifi:new:<11,2>, old:<11,0>, ap:<11,2>, sta:<11,0>, prof:1
I (35168) wifi:state: init -> auth (b0)
I (35174) wifi:state: auth -> assoc (0)
I (35221) wifi:state: assoc -> run (10)
I (36002) RevK: Up 36, Link down 35
I (37002) RevK: Up 37, Link down 36
I (38002) RevK: Up 38, Link down 37
I (38251) wifi:state: run -> init (fc0)
I (38253) wifi:new:<11,0>, old:<11,2>, ap:<11,2>, sta:<11,0>, prof:1
I (38256) RevK: STA Disconnect
I (39002) RevK: Up 39, Link down 38
W (39003) wifi:Haven't to connect to a suitable AP now!
I (40001) RevK: Up 40, Link down 39
W (40002) wifi:Haven't to connect to a suitable AP now!
I (41000) RevK: Up 41, Link down 40
W (41001) wifi:Haven't to connect to a suitable AP now!
I (41111) RevK: STA Disconnect
I (42002) RevK: Up 42, Link down 41
W (42003) wifi:Haven't to connect to a suitable AP now!
I (43000) RevK: Up 43, Link down 42
W (43002) wifi:Haven't to connect to a suitable AP now!
I (43964) wifi:new:<11,2>, old:<11,0>, ap:<11,2>, sta:<11,0>, prof:1
I (43967) wifi:state: init -> auth (b0)
I (43973) wifi:state: auth -> assoc (0)
I (44001) RevK: Up 44, Link down 43
I (44008) wifi:state: assoc -> run (10)
I (45002) RevK: Up 45, Link down 44
I (46002) RevK: Up 46, Link down 45
I (46502) Faikin: Trying X50¬Tx
I (46504) gpio: GPIO[34]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (46506) gpio: GPIO[48]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (47002) RevK: Up 47, Link down 46
I (47030) wifi:state: run -> init (fc0)
I (47032) wifi:new:<11,0>, old:<11,2>, ap:<11,2>, sta:<11,0>, prof:1
I (47035) RevK: STA Disconnect
I (48001) RevK: Up 48, Link down 47
W (48002) wifi:Haven't to connect to a suitable AP now!
I (49000) RevK: Up 49, Link down 48
W (49002) wifi:Haven't to connect to a suitable AP now!
`

1 reply

revk Nov 2, 2023
Maintainer

It looks like it connects, authenticates, associates, and then, err, disconnects. I have never seen that before!!!

To be honest I have no clue what that is...

There are options to enable a lot of WiFi debug if you want to try that. You may have to set the log level to debug. Worth a try maybe, it may say why it disconnects.

psailleko · 2023-11-02T11:33:21Z

psailleko
Nov 2, 2023
Author

I've enabled wifi debug and i can see handshake happening but fails ..

I will try with another AP from another brand (even if i already have many esp things on this network)

3 replies

revk Nov 2, 2023
Maintainer

I don't think we do anything special that would break it, honest. Good luck.

psailleko Nov 2, 2023
Author

I agree, thanks for your time, i hope i will find the culprit ^^

psailleko Nov 3, 2023
Author

Hi,

i've just flashed a "demo ap sketch" from ESP and ... it works as a client for my wifi network

Waiting for the device to reconnect.....
I (246) boot: Loaded app from partition at offset 0x10000I (523) wifi_init: WiFi IRAM OP enabled
I (523) wifi_init: WiFi RX IRAM OP enabled
I (533) phy_init: phy_version 601,98f2a71,Jun 29 2023,09:58:12
I (583) wifi:mode : sta (f4:12:fa:98:33:1c)
I (583) wifi:enable tsf
I (583) wifi station: wifi_init_sta finished.
I (693) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (693) wifi:state: init -> auth (b0)
I (1433) wifi:state: auth -> assoc (0)
E (1443) wifi:Set status to INIT
I (1443) wifi:state: assoc -> init (1e10)
I (1443) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (1443) wifi station: retry to connect to the AP
I (1443) wifi station: connect to the AP fail
I (2153) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:1
I (2153) wifi:state: init -> auth (b0)
I (6493) wifi:state: auth -> init (200)
I (6493) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
I (6503) wifi station: retry to connect to the AP
I (6503) wifi station: connect to the AP fail
I (7713) wifi:new:<11,0>, old:<6,0>, ap:<255,255>, sta:<11,0>, prof:1
I (8773) wifi:state: init -> auth (b0)
I (8773) wifi:state: auth -> assoc (0)
I (8783) wifi:state: assoc -> run (10)
I (8823) wifi:connected with UBERUBER, aid = 3, channel 11, BW20, bssid = fa:92:bf:24:f3:6b
I (8823) wifi:security: WPA2-PSK, phy: bgn, rssi: -71
I (8843) wifi:pm start, type: 1

I (8843) wifi:set rx beacon pti, rx_bcn_pti: 0, bcn_timeout: 25000, mt_pti: 0, mt_time: 10000
I (8903) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (10343) wifi:<ba-add>idx:0 (ifx:0, fa:92:bf:24:f3:6b), tid:0, ssn:1, winSize:64
I (11843) esp_netif_handlers: sta ip: 192.168.1.99, mask: 255.255.252.0, gw: 192.168.1.1
I (11843) wifi station: got ip:192.168.1.99
I (11843) wifi station: connected to ap SSID:ultrauberapname password:nononononononono
I (11853) main_task: Returned from app_main()

I will try to reflash this particular PCB with the Faikin code as now i know that "it works" with my network and not a hardware issue on the pcb :)

i've followed this tutorial :
https://esp32tutorials.com/esp32-esp-idf-connect-wifi-station-mode-example/

psailleko · 2023-11-07T22:10:12Z

psailleko
Nov 7, 2023
Author

Hi, i've retryed with your last modification on the github repo and ... it works ^^

I needed to copy paste bleenv.c and .h to esp32/main and disable bt things in menuconfig to succesfully compile but ...
now it works

1 reply

revk Nov 8, 2023
Maintainer

That sounds odd, they should be linked to a submodule. But if you got it working, well done.

Settings not saved ? #138

psailleko Oct 31, 2023

Replies: 7 comments · 29 replies

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

revk Nov 1, 2023 Maintainer

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 1, 2023 Maintainer

psailleko Nov 1, 2023 Author

revk Nov 2, 2023 Maintainer

psailleko Nov 2, 2023 Author

revk Nov 2, 2023 Maintainer

psailleko Nov 2, 2023 Author

revk Nov 2, 2023 Maintainer

psailleko Nov 2, 2023 Author

psailleko Nov 3, 2023 Author

psailleko Nov 7, 2023 Author

revk Nov 8, 2023 Maintainer

psailleko
Oct 31, 2023

Replies: 7 comments 29 replies

revk
Nov 1, 2023
Maintainer

psailleko
Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko
Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

revk Nov 1, 2023
Maintainer

revk Nov 1, 2023
Maintainer

psailleko
Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko Nov 1, 2023
Author

revk Nov 1, 2023
Maintainer

psailleko Nov 1, 2023
Author

revk Nov 2, 2023
Maintainer

psailleko
Nov 2, 2023
Author

revk Nov 2, 2023
Maintainer

psailleko
Nov 2, 2023
Author

revk Nov 2, 2023
Maintainer

psailleko Nov 2, 2023
Author

psailleko Nov 3, 2023
Author

psailleko
Nov 7, 2023
Author

revk Nov 8, 2023
Maintainer