NCS and Atmel WINC1500

RE: NCS and Atmel WINC1500

dario.sortino — Mon, 03 Apr 2023 07:37:11 GMT

In the end the error code was due to an incorrect FW version running on the WINC. Updating it solved the issue!
Thank everyone!

RE: NCS and Atmel WINC1500

Øyvind — Thu, 23 Mar 2023 09:59:09 GMT

The error codes printed should errno codes, found in errno.h.

#define EIO 5           /**< I/O error */

From zephyr\drivers\wifi\winc1500\wifi_winc1500_config.h there is an option to enable more debug information

#define CONF_WINC_DEBUG				(0)

change to 

#define CONF_WINC_DEBUG				(1)

Perhaps this can provide more information on the issue.

RE: NCS and Atmel WINC1500

dario.sortino — Thu, 23 Mar 2023 08:41:11 GMT

What about the Error code -5? I see that it originates from the wifi_mgmt_event_handler when it requests a connection.

RE: NCS and Atmel WINC1500

Øyvind — Wed, 22 Mar 2023 15:26:36 GMT

Happy to hear that you got it working!

Unfortunately, I'm not able to tell how debugging the WINC1500 works. You will need to contact the Zephyr community on Discord or Microchip directly.

RE: NCS and Atmel WINC1500

dario.sortino — Wed, 22 Mar 2023 13:24:58 GMT

Turned out that I connected erroneously a PIN.

I can communicate with the WINC and successfully scan the APs. I still fail to connect to my TestAP, so the question remains: can I go deeper in showing logs that can help me understand whats going on? Or what approach can I follow?

RE: NCS and Atmel WINC1500

dario.sortino — Wed, 22 Mar 2023 10:15:52 GMT

Good to know, I also was able to make it work.

By adding the following lines

CONFIG_SHELL_BACKEND_RTT=y
CONFIG_UART_CONSOLE=n
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG=y

I am also able to interact with the Wifi Shell via RTT in my custom board.

Now, the wifi scan command results in

In the meanwhile that I'll debug the correct wiring of the WINC1500 module, is there a way to see deeper level of debug (SPI for example)

RE: NCS and Atmel WINC1500

Øyvind — Wed, 22 Mar 2023 09:35:19 GMT

Hello again,
Tested this on my side using nRF Connect SDK v2.3.0 with your overlay, and added hal_atmel as described in the ticket you refer to.

There seems to be missing configurations, the following worked for me running the wifi sample:

CONFIG_WIFI=y
CONFIG_NETWORKING=y
CONFIG_WIFI_WINC1500=y
CONFIG_WIFI_WINC1500_REGION_EUROPE=y

Please note that the Winc1500 is not a part of Nordic Semiconductors products, and we would encourage you to use our new WiFi companion IC, the nRF70 series. The nRF7002 is designed to be used alongside Nordic’s existing nRF52® and nRF53® Series Bluetooth Systems-on-Chip (SoCs), and nRF91® Series cellular IoT Systems-in-Package (SiPs). The nRF7002 can also be used in conjunction with non-Nordic host devices.

Kind regards,
Øyvind

RE: NCS and Atmel WINC1500

Øyvind — Tue, 21 Mar 2023 12:42:44 GMT

Hello,

I will have a look into your case and discuss with my colleague Sigurd from the ticket you are referring to.

Kind regards,
Øyvind

RE: NCS and Atmel WINC1500

dario.sortino — Tue, 21 Mar 2023 10:58:08 GMT

Wanted to add that it doesn't relate to the http_client sample mentioned in the issue, but also for example with the zephyr/wifi sample, or custom applications