Micropython crashes when connecting to an unreachable Network

[EYEnet-GROUP]

Description

When trying to connect to a wifi-network which is not reachable the board crashes with the error message assertion "*q < pool->len" failed: file "../../py/qstr.c", line 198, function: find_qstr and becomes unresponsive. To regain access the board needs to be reset and sometimes unplugged and repowered. For debugging a message with the reason and status would be helpful. Sometimes the error occurs during the first run of the script even if a connection should be possible but does not return after resetting the board. Since the error occurs in the wlan.connect('<ssid>','<key>') call a potential try-catch would not automatically reconnect or retry to connect. As a countermeasure to include in your documentation the connect call should be placed in a for or while loop.

Code Size

No response

Implementation

I hope the MicroPython maintainers or community will implement this feature

Code of Conduct

Yes, I agree

[jaenrig-ifx]

Hi!

Can you share the code example generating the error?

[EYEnet-GROUP]

Ah, sorry. It is actually the WLAN.status() call causing the issue. The Psoc-port documentation states this function does not return the status constant contrary to the general micropython documentation. Also the constants in the network module to match the result with have not been implemented in the psoc-port. Hence the following example fails:

import network

class WifiConnect:

  ## Init Object with Wlan in station-mode
  def __init__(self):
    self.wlan = network.WLAN(network.STA_IF)

  ## try to connect or print the wlan status
  def connect(self):
    try:
      self.wlan.connect("somessid", "somepassword") ### Leave this setting to ensure connection is not possible ###
    except:
      self.printStatus()

  ## get and print wlan status
  def printStatus(self):
    status = self.wlan.status() ### Fails here ###
    print('Connection Status:')
    if(status == network.STAT_GOT_IP):
        print('Success')
    elif(status == network.STAT_IDLE):
        print('Idle')
    elif(status == network.STAT_CONNECTING):
        print('Connecting')
    elif(status == network.STAT_WRONG_PASSWORD):
        print('Password incorrect')
    elif(status == network.STAT_NO_AP_FOUND):
        print('No AP found')
    else:
        print('Failed for unknown reason')
      
wifi = WifiConnect()
wifi.connect()

Anyway the console-output of a failed connection-attempt results in something like ValueError: network sta connect error (with code: 137232422). The message appears to be the same for any fault but with different error codes. Sadly I could not find a documentation of the meaning of these codes.

[EYEnet-GROUP]

Using a simple example. I was able to deduct some error codes.

import network

wlan = network.WLAN(network.STA_IF)
wlan.connect("somessid", "somepassword")

137232422: WiFI not found/out of reach
33555494: Wrong password
33555439: Some different sort of Authentication problem

[jaenrig-ifx]

Hi @EYEnet-GROUP,

Correct, the status() function in our port does implement the connection status (passing no argument).
Those constants (STAT_GOT_IP, etc) are neither defined in our port, and therefore this error.

In some cases, we might have some API specialization/deviations from the general API. Thus, it is a good idea to start from the port specific docs.

Regarding the numeric error codes, these are coming from the psoc6 C libraries and they have not been translated to meaningful and clear error codes/messages in micropython. Currently it let you know that the connection() function is failing.

We will look into it and add it to our improvement list 👍

Thanks for your support!

[github-actions]

This issue is stale because it has been open more than 6 weeks with no activity. Please comment on this issue if it's still relevant or it will be closed automatically after 1 week.

[github-actions]

This issue is stale because it has been open more than 6 weeks with no activity. Please comment on this issue if it's still relevant or it will be closed automatically after 1 week.

[github-actions]

This issue is stale because it has been open more than 6 weeks with no activity. Please comment on this issue if it's still relevant or it will be closed automatically after 1 week.

[github-actions]

This issue is stale because it has been open more than 6 weeks with no activity. Please comment on this issue if it's still relevant or it will be closed automatically after 1 week.