Basically you can just check the commands in the wlan_ioctl function
in esp32_wlan.c to see what's implemented.  But not much going on
there for the moment.
You can connect to access points.  Commands are given in the README.txt file
wapi psk wlan0 mypassword 1
wapi essid wlan0 myssid 1
You can also set these from menuconfig.

> Also, I'm trying to scan and I get:

That's because SIOCSIWSCAN isn't handled by the driver.
We have a branch internally to improve the driver and add more
features (SIOCSIWSCAN being one of them), I don't know when this one
will be submitted though.

On Thu, Feb 4, 2021 at 11:55 PM Matias N. <mat...@imap.cc> wrote:
>
> Thanks, now the interface appears.
> What functionality is currently supported? Can I connect to WPA2 AP? Can I 
> create an AP?
>
> Also, I'm trying to scan and I get:
>
> nsh> wapi scan wlan0
> ioctl(SIOCSIWSCAN): 25
> ERROR: Process command (scan) failed.
>
> Thanks,
> Matias
>
> On Thu, Feb 4, 2021, at 19:36, Abdelatif Guettouche wrote:
> > It could be because there are some issues with getting the paramters from
> > the flash.  Please try disabling Save Paramters from the Wifi Configuration
> > menu.
> >
> > On Thu, Feb 4, 2021, 11:32 PM Matias N. <mat...@imap.cc> wrote:
> >
> > > Hi,
> > > I'm trying to test WiFi support on ESP32 DevKitC (I used wapi config) and
> > > it does not seem to work. I get this:
> > >
> > > rst:0x1 (POWERON_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:0x3fff0030,len:4
> > > load:0x3fff0034,len:6924
> > > load:0x40078000,len:13272
> > > load:0x40080400,len:3604
> > > entry 0x40080670
> > > I (29) boot: ESP-IDF v4.3-dev-1901-g178b122c1 2nd stage bootloader
> > > I (29) boot: compile time 17:16:52
> > > I (29) boot: chip revision: 1
> > > I (33) boot_comm: chip revision: 1, min. bootloader chip revision: 0
> > > I (40) boot.esp32: SPI Speed      : 40MHz
> > > I (45) boot.esp32: SPI Mode       : DIO
> > > I (49) boot.esp32: SPI Flash Size : 2MB
> > > I (54) boot: Enabling RNG early entropy source...
> > > I (59) boot: Partition Table:
> > > I (63) boot: ## Label            Usage          Type ST Offset   Length
> > > I (70) boot:  0 nvs              WiFi data        01 02 00009000 00006000
> > > I (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000
> > > I (85) boot:  2 factory          factory app      00 00 00010000 00100000
> > > I (93) boot: End of partition table
> > > I (97) boot_comm: chip revision: 1, min. application chip revision: 0
> > > I (104) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020
> > > size=0x0c22c ( 49708) map
> > > I (132) esp_image: segment 1: paddr=0x0001c254 vaddr=0x3ffb81e0
> > > size=0x0181c (  6172) load
> > > I (135) esp_image: segment 2: paddr=0x0001da78 vaddr=0x40080000
> > > size=0x00400 (  1024) load
> > > I (139) esp_image: segment 3: paddr=0x0001de80 vaddr=0x40080400
> > > size=0x02198 (  8600) load
> > > I (151) esp_image: segment 4: paddr=0x00020020 vaddr=0x400d0020
> > > size=0x59678 (366200) map
> > > I (296) esp_image: segment 5: paddr=0x000796a0 vaddr=0x40082598
> > > size=0x08718 ( 34584) load
> > > I (317) boot: Loaded app from partition at offset 0x10000
> > > I (317) boot: Disabling RNG early entropy source...
> > > esp32_rng_initialize: Initializing RNG
> > > esp_nvs_get_blob: INFO: No file /mnt/esp/wifi/wifi.misc.log
> > > esp_nvs_set_blob: ERROR: Failed to set open /mnt/esp/wifi/wifi.misc.log
> > > W (85) wifi:nvs_log_init, osi_nvs_set_blob fail, key=log ret=ffffffff
> > >
> > > esp_wifi_init: ERROR: Failed to initialize WiFi error=-1
> > > esp_wifi_adapter_init: ERROR: Failed to initialize WiFi error=-1
> > > ERROR: Failed to initialize WiFi
> > >
> > > NuttShell (NSH) NuttX-10.0.1
> > > nsh> ifconfig
> > > nsh> ifup wlan0
> > > ifup wlan0...OK
> > > nsh> ifconfig
> > > nsh>
> > >
> > > I have used bootloader and partitions bin from
> > > https://github.com/saramonteiro/esp32_binaries_nuttx
> > >
> > > Thanks,
> > > Matias
> > >
> >

Reply via email to