nRF9160DK and WINC1500 WiFi Module

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Thu, 07 Oct 2021 17:20:07 GMT

Hi Rod,

Great to hear you got the module working with the nRF52840 Dongle. What IO voltage are did you use between the two?

If you would like to keep trying to get the module working with nRF9160 I suggest the next thing to try is to make sure the two units have a corresponding IO voltage. Either make sure the WIFI dongle is configured to communicate at 3.0V, or make sure the nRF9160 DK is communicating at 3.3V. If you would like to make the nRF9160 DK communicate at 3.3V, supply 3.3V to the VI_REF pin after VDD is applied. This way the IO voltage is automatically set to the same voltage as VI_REF.

Best regards,

Håkon

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Fri, 01 Oct 2021 17:18:06 GMT

Hi Håkon,

I am simply using the sample code for the WINC1500. The only thing I have changed is the pinout. I have tried a number of different pin outs, my latest is shown below.

As I said, I did get the same code to work on the nRF52840 dongle; it works as planned so I think its a pin out problem. If you can suggest an alternative pinout, I will give it a go but as I got it to work elsewhere Im happy to close the ticket

Rod

&spi3 {
  compatible = "nordic,nrf-spim";
  status = "ok";
  sck-pin = <13>;
  mosi-pin = <11>;
  miso-pin = <12>;
  cs-gpios = <&gpio0 10 GPIO_ACTIVE_LOW>;

	winc1500@0 {
		status = "ok";
		compatible = "atmel,winc1500";
		reg = <0x0>;
		label = "winc1500";
		spi-max-frequency = <250000>;
		irq-gpios = <&gpio0 20 1>;
		reset-gpios = <&gpio0 24 1>;
		enable-gpios = <&gpio0 25 0>;
		
	};
};

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Thu, 30 Sep 2021 11:53:25 GMT

Hi Rod,

I see that enable-gpio is configured to P0.19. I am not sure whether I have interpreted things correctly, however, it could be worth a try to swap to another pin.

Have you made any modifications to the FW on nRF52840?

Would you be able to share some of your project code? I do not have the module but I could try to check the signals on my side.

Best regards,

Håkon

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Sun, 19 Sep 2021 19:03:52 GMT

Hi Håkon

Thanks for your suggestions. I have a couple of different revision boards; (1.0.0 and 0.8.3) and have compiled the code for them specifically as delayed above. The scan is still failing but it just seems to hang there as opposed to reporting an error.

I also have an nRF52840 dongle and I have connected the module up to this; this works as expected. So, I'm happy that my code and understanding of the connections are correct. BTW, I can leave the WAKE signal unconnected, and it works. There must be a pull up on the module.

So, I assuming its a "pin allocation" problem where I'm using a pin on the nRF9160DK that has been allocated to something else on the board. My overlay file is below. Can you see me using any pins I shouldn't?

Rod

&spi3 {
  compatible = "nordic,nrf-spim";
  status = "ok";
  sck-pin = <13>;
  mosi-pin = <11>;
  miso-pin = <12>;
  cs-gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;

	winc1500@0 {
		status = "ok";
		compatible = "atmel,winc1500";
		reg = <0x0>;
		label = "winc1500";
		spi-max-frequency = <250000>;
		irq-gpios = <&gpio0 16 1>;
		reset-gpios = <&gpio0 26 1>;
		enable-gpios = <&gpio0 19 0>;
		
	};
};

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Tue, 14 Sep 2021 14:19:55 GMT

Hi Rod,

Which board hw revision are you using? Have you tried specifying a specific board revision for nRF9160 DK? This will affect the behaviour and configuration of several pins.

When I check the Board controller firmware documentation it is mentioned that "In nRF9160 DK revisions earlier than v0.14.0, nRF9160 signals routed to other components on the DK are not simultaneously available on the DK connectors."

I can see that P0.00 and P0.01 are also in use by VCOM2. Try swapping these pins with a couple of other free pins. Or, if you have no pins available, you could try to disable routing for the VCOM2 pins by adding the following to the overlay of the board controller firmware. Then build and flash this to nrf9160dk_nrf52840. Make sure that the PROG/DEBUG switch on the DK is set to nRF52.

&vcom2_pins_routing {

        status = "disabled";
};

Frequency

Another thing to try is to lower the SPI frequency to 250000 in your overlay. This could help if you have long wires between the DK and the module.

If you have an oscilloscope available, recording using 250000 could also help clarify a few things.

Håkon

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Mon, 06 Sep 2021 14:57:45 GMT

Hi Håkon,

Yes, I had seen that and have tried various connections, +3V, unconnected and even 0V to see if I can see a change in behaviour. It didn't seem to change anything.

uart:~$ wifi scan
Scan request failed
[00:00:13.617,279] <err> wifi_winc1500: Failed to request scan
uart:~$

Rod

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Mon, 06 Sep 2021 14:12:44 GMT

Hi Rod,

Thank you for providing the details. So far I have only had a quick look. The first thing I stumbled into is this comment in the ATWINC1500B-IMU datasheet regarding the Wake pin:

Where at the DK is this pin connected? Is it connected to 3.0V or to 3.3V? What happens if you leave it unconnected?

Best regards,

Håkon

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Fri, 03 Sep 2021 14:26:05 GMT

Hi Håkon,

No problem, I understand that things take longer during vacation time.

I am using this module.

https://www.microchip.com/content/dam/mchp/documents/OTH/ProductDocuments/UserGuides/50002616A.pdf

Pin	    Signal	    nRF9160DK Connection
1	    ID_DATA	        -
2	    GND	            0V
3	    NC	            -
4	    NC	            -
5	    RESET_N	        P0.13
6	    WAKE	        +3.3V
7	    NC	            -
8	    NC	            -
9	    IRQN	        P0.16
10	    CHIP_EN	        P0.12
11	    I2C_SDA	        -
12	    I2C_SCK	        -
13	    UART_RX	        -
14	    UART_TX	        -
15	    SPI_SSN	        P0.18
16	    SPI_MOSI	    P0.19
17	    SPI_MISO	    P0.01
18	    SPI_SCK	        P0.00
19	    GND	            0V
20	    VCC	            +3.3V

You will see my overlay file in a previous comment.

I am using the NRF9160DK, with the I/o set to 3V.

Rod

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Fri, 03 Sep 2021 09:03:59 GMT

Hi Rod, sorry for the long delay.

How are you supplying the WiFi module? What are the IO voltages on the WiFi module and nRF9160 DK? Are they both configured to communicate at a corresponding level?

If you could share the schematics showing the SPI setup we could take a look.

Best regards,

Håkon

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Thu, 19 Aug 2021 15:34:44 GMT

Hi Pirun,

I have connected the reset signal and can see that its high. I am basing my overlay file on this example.

https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/net/wifi/boards/reel_board.overlay

my overlay file is this

&spi3 {
  compatible = "nordic,nrf-spim";
  status = "ok";
  cs-gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
  sck-pin = <0>;
  mosi-pin = <19>;
  miso-pin = <1>;

	winc1500@0 {
		status = "ok";
		compatible = "atmel,winc1500";
		reg = <0x0>;
		label = "winc1500";
		spi-max-frequency = <4000000>;
		irq-gpios = <&gpio0 16 1>;
		reset-gpios = <&gpio0 13 1>;
		enable-gpios = <&gpio0 12 0>;

//		irq-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
//		reset-gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
//		enable-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>;
	};
};

Im assuming that the power up sequence is handled by the driver, I just need to connect the right signals, which I believe I have.

Rod

RE: nRF9160DK and WINC1500 WiFi Module

pirun lee — Thu, 19 Aug 2021 14:33:43 GMT

HI Rod,

We can learn SPI master is sending correct signal from your capture while not connecting WINC1500.

SPIM is trying to reset module.

#define CMD_RESET				0xcf

	case CMD_RESET:							/* reset */
		bc[1] = 0xff;
		bc[2] = 0xff;
		bc[3] = 0xff;
		len = 5;
		break;

However you can't get anything when WINC1500 connected.

It seems that bus has been pulled down by WINC1500.

I would suggest that you check the power sequence of WINC1500.

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Thu, 19 Aug 2021 13:51:09 GMT

Hi Pirun,

I am working at home today so don't have access to a proper analyser. I do have one of these

https://hobbycomponents.com/testing/243-hobby-components-usb-8ch-24mhz-8-channel-logic-analyser

They are cheap and cheerful but do seem to have problems with loading on the line. When I connect the probes with the WINC1500 connected, it seems to struggle to pick up the signals correctly.

I did however, manage to capture the following with the WINC1500 module removed, so obviously I won't get any data back but can see the clock, chips select and MOSI data.

Rod

RE: nRF9160DK and WINC1500 WiFi Module

pirun lee — Thu, 19 Aug 2021 10:07:07 GMT

Hi Rod,

The message is just warning. It is caused by this Kconfig.

config WINC1500_DRV_USE_OLD_SPI_SW
	bool "Use old SPI access method in the vendor HAL"
	help
	  This option, when enabled, causes USE_OLD_SPI_SW
	  setting to be passed to vendor HAL.

You can't generate zephyr.hex if there is any compile time error.

Can you use logic analyze to observe SPI communication?

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Thu, 19 Aug 2021 09:37:31 GMT

Hey Pirun,

I enabled debug and am indeed seeing error messages as you detailed above; suggesting the SPI interface is at fault. I have double checked the connections and overlay file and they all look good to me.

You will see in my build output above, Im seeing a build error around the SPI read.

[74/307] Building C object zephyr/CMak...ifi/winc1500/driver/source/nmspi.c.obj
/opt/nordic/ncs/v1.6.1/modules/hal/atmel/asf/common/components/wifi/winc1500/driver/source/nmspi.c:746:14: warning: 'spi_data_read' defined but not used [-Wunused-function]
  746 | static sint8 spi_data_read(uint8 *b, uint16 sz,uint8 clockless)
      |              ^~~~~~~~~~~~~
[300/307] Linking C executable zephyr/zephyr_prebuilt.elf

as this is occurring during build, would this suggest a config error on my part? Even if my connections were wrong, I wouldnt expect to se an error during build

Rod

RE: nRF9160DK and WINC1500 WiFi Module

pirun lee — Thu, 19 Aug 2021 04:34:18 GMT

Hi Rod,

Please check if your wiring is correct.
You can also enable debug of winc1500 driver.

Under zephyr folder.

diff --git a/drivers/wifi/winc1500/wifi_winc1500_config.h b/drivers/wifi/winc1500/wifi_winc1500_config.h
index 8c8cd6b4c5..77eb154c4b 100644
--- a/drivers/wifi/winc1500/wifi_winc1500_config.h
+++ b/drivers/wifi/winc1500/wifi_winc1500_config.h
@@ -60,7 +60,9 @@
---------------------------------
*/
#include <stdio.h>
-#define CONF_WINC_DEBUG (0)
+#define CONF_WINC_DEBUG (1)
+#define M2M_LOG_LEVEL M2M_DBG
#define CONF_WINC_PRINTF printf

If your SPI wiring is incorrect.

You will see bunch error message like this.

(APP)(ERR)[spi_cmd_complete][568][nmi spi]: Failed cmd response, cmd (ca), resp (ff)
(APP)(ERR)[spi_read_reg][1068][nmi spi]: Failed cmd, read reg (0000e824)...
(APP)(ERR)[spi_read_reg][1086]Reset and retry 10 e824
(APP)(ERR)[spi_cmd_complete][568][nmi spi]: Failed cmd response, cmd (ca), resp (ff)
(APP)(ERR)[spi_read_reg][1068][nmi spi]: Failed cmd, read reg (0000e824)...
(APP)(ERR)[spi_read_reg][1086]Reset and retry 9 e824
(APP)(ERR)[spi_cmd_complete][568][nmi spi]: Failed cmd response, cmd (ca), resp (ff)
(APP)(ERR)[spi_read_reg][1068][nmi spi]: Failed cmd, read reg (0000e824)...
(APP)(ERR)[spi_read_reg][1086]Reset and retry 8 e824
(APP)(ERR)[spi_cmd_complete][568][nmi spi]: Failed cmd response, cmd (ca), resp (ff)
(APP)(ERR)[spi_read_reg][1068][nmi spi]: Failed cmd, read reg (0000e824)...

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Wed, 18 Aug 2021 14:53:57 GMT

Hey Pirun,

Thanks for your reply. I have updated the west.yml file and ran west update. I can now see the atmel HAL.

I enable CONFIG_WIFI=y and CONFIG_WIFI_WINC1500=y and rebuild.It now builds without the "wifi errors" I was seeing previously. Although I am seeing an SPI error.

Watt@Watt-Macbook-Pro WINC1500 % sh build_app.sh
[0/1] Re-running CMake...
Including boilerplate (Zephyr base (cached)): /opt/nordic/ncs/v1.6.1/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500
-- Using NCS Toolchain 1.6.0 for building. (/opt/nordic/ncs/v1.6.0-rc2/toolchain/cmake)
-- Zephyr version: 2.6.0-rc1 (/opt/nordic/ncs/v1.6.1/zephyr), build: v2.6.0-rc1-ncs1
-- Found west (found suitable version "0.11.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160, Revision: 0.7.0
-- Cache files will be written to: /Users/Watt/Library/Caches/zephyr
-- Found dtc: /opt/nordic/ncs/v1.6.0-rc2/toolchain/bin/dtc (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/opt/nordic/ncs/v1.6.0-rc2/toolchain)
-- Found BOARD.dts: /opt/nordic/ncs/v1.6.1/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/nrf9160dk_nrf9160.overlay
-- Generated zephyr.dts: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/device_extern.h
Parsing /opt/nordic/ncs/v1.6.1/zephyr/Kconfig
Loaded configuration '/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/.config'
Configuration saved to '/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/.config'
Kconfig header saved to '/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/autoconf.h'
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build
[1/1] cd /Users/Watt/Documents/ZEPHYR_...ncs/v1.6.1/zephyr/cmake/pristine.cmake
Including boilerplate (Zephyr base): /opt/nordic/ncs/v1.6.1/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500
-- Using NCS Toolchain 1.6.0 for building. (/opt/nordic/ncs/v1.6.0-rc2/toolchain/cmake)
-- Zephyr version: 2.6.0-rc1 (/opt/nordic/ncs/v1.6.1/zephyr), build: v2.6.0-rc1-ncs1
-- Found Python3: /opt/nordic/ncs/v1.6.0-rc2/toolchain/bin/python3 (found suitable exact version "3.8.2") found components: Interpreter 
-- Found west (found suitable version "0.11.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160, Revision: 0.7.0
-- Cache files will be written to: /Users/Watt/Library/Caches/zephyr
-- Found dtc: /opt/nordic/ncs/v1.6.0-rc2/toolchain/bin/dtc (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/opt/nordic/ncs/v1.6.0-rc2/toolchain)
-- Found BOARD.dts: /opt/nordic/ncs/v1.6.1/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/nrf9160dk_nrf9160.overlay
-- Generated zephyr.dts: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/device_extern.h
Parsing /opt/nordic/ncs/v1.6.1/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v1.6.1/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_defconfig'
Merged configuration 'prj.conf'
Configuration saved to '/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/.config'
Kconfig header saved to '/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/v1.6.0-rc2/toolchain/bin/arm-none-eabi-gcc
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build
Make Complete

/Users/Watt/Documents/ZEPHYR_Code/nRF9160DK/New_Code/WINC1500/build
[1/307] Preparing syscall dependency handling

[74/307] Building C object zephyr/CMak...ifi/winc1500/driver/source/nmspi.c.obj
/opt/nordic/ncs/v1.6.1/modules/hal/atmel/asf/common/components/wifi/winc1500/driver/source/nmspi.c:746:14: warning: 'spi_data_read' defined but not used [-Wunused-function]
  746 | static sint8 spi_data_read(uint8 *b, uint16 sz,uint8 clockless)
      |              ^~~~~~~~~~~~~
[300/307] Linking C executable zephyr/zephyr_prebuilt.elf

[307/307] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      128416 B         1 MB     12.25%
            SRAM:       42624 B        88 KB     47.30%
        IDT_LIST:          0 GB         2 KB      0.00%
Parsing hex file.
Erasing page at address 0x0.
Erasing page at address 0x1000.
Erasing page at address 0x2000.
Erasing page at address 0x3000.
Erasing page at address 0x4000.
Erasing page at address 0x5000.
Erasing page at address 0x6000.
Erasing page at address 0x7000.
Erasing page at address 0x8000.
Erasing page at address 0x9000.
Erasing page at address 0xA000.
Erasing page at address 0xB000.
Erasing page at address 0xC000.
Erasing page at address 0xD000.
Erasing page at address 0xE000.
Erasing page at address 0xF000.
Erasing page at address 0x10000.
Erasing page at address 0x11000.
Erasing page at address 0x12000.
Erasing page at address 0x13000.
Erasing page at address 0x14000.
Erasing page at address 0x15000.
Erasing page at address 0x16000.
Erasing page at address 0x17000.
Erasing page at address 0x18000.
Erasing page at address 0x19000.
Erasing page at address 0x1A000.
Erasing page at address 0x1B000.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Erasing page at address 0x1E000.
Erasing page at address 0x1F000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.
Applying system reset.
Run.

When I try to run wifi scan I get an error,

uart:~$ wifi scan
Scan request failed
[00:00:12.786,285] <err> wifi_winc1500: Failed to request scan
uart:~$

Rod

RE: nRF9160DK and WINC1500 WiFi Module

pirun lee — Tue, 17 Aug 2021 04:19:16 GMT

Hi Rod,

The compile error is caused by lacking of HAL of ATMEL WINC1500.

It doesn't include in nRF Connect SDK.

Please add ATMEL module in nrf/west.yml.

Then west update again to pull winc1500 related code.

Here is sample for you.

--- a/west.yml
+++ b/west.yml
@@ -102,7 +102,12 @@ manifest:
remote: zephyrproject
path: modules/lib/openthread
revision: f460532d4afa5d49feba241e5dc31c56123d31a8
-
+ - name: hal_atmel
+ remote: zephyrproject
+ path: modules/hal/atmel
+ revision: master
+ groups:
+ - hal

You can check if there is hal of atmel.

The second error " <err> net_if: There is no network interface to work with!" is caused by commenting out CONFIG_WIFI=y.
Once you have HAL of ATMEL, please add back CONFIG_WIFI=y and CONFIG_WIFI_WINC1500=y.

RE: nRF9160DK and WINC1500 WiFi Module

RodWatt — Tue, 10 Aug 2021 18:49:01 GMT

Thanks Håkon, no problem, thanks for keeping me posted

Rod

RE: nRF9160DK and WINC1500 WiFi Module

helsing — Tue, 10 Aug 2021 13:08:59 GMT

Hi Rod, thank you for this request. I am just letting you know I will be looking into this. Several team members are on summer vacation at the moment, so please expect a delayed reply.

Best regards,

Håkon