WINC1500 never asserting IRQn

Log in or register to post comments
Go To Last Post
14 posts / 0 new
Author
Message
tinito
tinito's picture
Level: New Member
Joined: Wed. Apr 20, 2016
Posts: 1 View posts
#1
Posted by tinito: Wed. Apr 20, 2016 - 03:17 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

 

I'm porting the WINC1500 driver to our architecture, but I'm facing some problems I can't figure out.).

We are using a  a ATWINC1500-MR210PB module, and we started from the Atmel driver (we ported the nm_bsp_xxx.c and nm_bus_wrapper_xxx.c source files).

The SPI is working as expected (i.e., I can read the firmware revision register without problems), but the IRQn signal is always high, so the irq handler function is never called.

It doesn't look like hardware problem (the IRQ line has a weak pullup), but I can't find any documentation on how to port the driver and how communication actually should work (should the WINC1500 assert the IRQn signal? when?).

 

Any suggestion? Is there a complete porting guide?

 

 

Tags:

Wireless, 802.11/Wi-Fi
Top
gianluca.murrone
gianluca.murrone's picture
Level: New Member
Joined: Wed. Apr 27, 2016
Posts: 1 View posts
Posted by gianluca.murrone: Fri. Apr 29, 2016 - 08:54 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

 

do anybody can help me to port the same drivers (same chip, same channel) and make the chip works?

Any help would be apreciated

 

g

Top
Alex1986
Alex1986's picture
Level: New Member
Joined: Fri. Apr 15, 2016
Posts: 13 View posts
Posted by Alex1986: Thu. Jun 9, 2016 - 08:40 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi together,

 

i right now ported the WINC1500 MR210PA for an infineon controller.

First of all the SPI configuration must be:

  • Baud rate = 100000 (it is the same as for the samd21)
  • Shift direct = MSB first
  • No start bit
  • No stop bit
  • SPI_SCK PIN config: Push Pull output
  • SPI_MISO config: Pull down input
  • SPI_MOSI config: Push Pull output
  • SPI_SSN  config: Push Pull output

 

This configuration must be inserted in the "nm_bus_init" function in the "nm_bus_wrapper_samd21.c" module. Also the function "spi_rw, nm_bus_deinit, bus_reinit" must be adjusted.

 

The configuration for the external Interrupt "IRQN" is as following:

  • Input Pin
  • Pull-Up
  • Must trigger an interrupt by detecting a falling edge of the IRQN signal
  • The interrupt function is the "chip_isr" function 

 

All this must be done on the "nm_bsp_samd21.c" module in the function "nm_bsp_register_isr". Also the function "nm_bsp_interrupt_ctrl" must also be adjusted.

 

Also don't forget to configure the PINs RESET_N, CHIP_EN, WAKE in the module "nm_bsp_samd21.c" in the function "init_chip_pins" to be able to make a reset of the WINC1500 module. To be able to reset the WINC1500 module you also have to adjust the function "nm_bsp_reset" for your target system.

 

Adjust the UART configuration to be able to use the "printf".

 

The "conf_winc.h" file must also be adjusted, because here are some values which the software stack from the WINC1500 is needed. So don't forget to copy this file, too. Here you need to adjust the defines for your target system like "CONF_WINC_SPI_CLOCK" or "CONF_WINC_PRINTF".

 

The software stack which is needed for the WINC1500 on an other host controller consists of all the files which lies under the "wifi" (/src/ASF/components/wifi/) folder from the Atmel example projects.

I also copied the files from the folder "/src/ASF/sam0/utils/stdio".

 

For the Compiler you also need to define the following defines:

  • CONF_WINC_USE_SPI
  • BAUDRATE
  • MODULE_UART_INT
  • NM_EDGE_INTERRUPT (this define is importend for the IRQN control PIN)

 

I hope this help you to port the WINC1500 to an other host controller.

 

Best Regards.

 

Top
Taste Test
Taste Test's picture
Level: New Member
Joined: Mon. Aug 22, 2016
Posts: 3 View posts
Posted by Taste Test: Sun. Sep 18, 2016 - 02:14 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm not sure if this thread will get checked but ...

 

Is it possible to port the WINC1500 and not use the IRQN pin? I'm thinking of just simply polling the device and checking it in the main loop by constantly calling m2m_wifi_handle_events().

 

However, I also have another problem at the moment - I am having SPI communication issues. I am using an ATmega128 and have altered the base source files for the bus wrapper.

My scope says I am sending and receiving data ok on the bus, but I get constant read issues from the TWINC1500.

 

From nm_spi.c:

 

(APP)(ERR)[nm_spi_init][718][nmi spi]: Failed internal read protocol with CRC on, retyring with CRC off...

(APP)(ERR)[spi_data_read][365][nmi spi]: Failed data response read...(00)

(APP)(ERR)[spi_read_reg][604][nmi spi]: Failed data read...

(APP)(ERR)[nm_spi_init][721][nmi spi]: Failed internal read protocol...

 

 

I step through the board reset process and it's pulling the lines up and down correctly. I have also slowed the SPI clock right down and tried a variety of speeds.

The wave forms from the scope look like they are at the correct levels too.

 

Anyone have any suggestions? I can post a log of values sent and received over SPI if needed.

 

Edit:

(According to the software guide.)

To clarify, I send these bytes over the SPI bus in this order from the master --> 0xCA, 0x00, 0x10, 0x00, 0xCA

 

The response I expect is : 0xCA, 0x00, 0x00, 0xF3, 0xA0, 0x03 etc etc

 

Instead I get: 0x08, 0x07, 0x30, 0x00, 0x80, 0x00, 0x20

 

then a bunch of 0x00's while the master tries to send a soft reset command.

As far as I can tell, the slave's response is invalid as it should start with a 0xCA in response to the masters command, even if it's sending an error. I've tried looking to see what that sequence of values means but it appears to be just garbage, albeit consistent garbage (as in repeatable).

 

 

 

 

Last Edited: Mon. Sep 19, 2016 - 05:49 AM
Top
TronMCP
TronMCP's picture
Level: New Member
Joined: Thu. Feb 2, 2017
Posts: 1 View posts
Posted by TronMCP: Thu. Feb 2, 2017 - 03:10 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

 

I'm having the same issue with the not working IRQ.

I can communicate with the module over SPI without any problems.

I can e.g. read the firmware version (19.4.4) or the MAC Address.

 

But the IRQ line is never being pulled low by the device.

I tried station mode and AP mode. Command returns with OK, but no IRQ...

 

I don't know where to start searching for a solution.

Any ideas?

 

Michael

 

Top
Trony
Trony's picture
Level: New Member
Joined: Wed. Feb 9, 2005
Posts: 3 View posts
Posted by Trony: Wed. Feb 8, 2017 - 09:29 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'll answer my own question:

 

Even I can read out firmware version or MAC address , there's no IRQ or error return if

the SPI master clocks out HIGH levels for reading !!!!

I couldn't find any hint in the manual that the master need to clock out LOW levels on reading.

This is a strange behaviour.

 

But now I get an interrupt.

 

Michael

 

 

 

Top
wouter_minjauw
wouter_minjauw's picture
Level: New Member
Joined: Fri. Aug 11, 2017
Posts: 1 View posts
Posted by wouter_minjauw: Fri. Aug 11, 2017 - 01:31 PM (Reply to #4)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I ported the driver to an MSP430 microcontroller, and one of the problems I encountered was that sometimes a NULL pointer was given as the SPI transmit or receive buffer. If a null pointer is given as the transmit buffer, simply send 0x00's, otherwise you may get 'unpredictable outcomes'. Don't know if this helps you...

Top
Scratliner
Scratliner's picture
Level: New Member
Joined: Wed. Aug 23, 2017
Posts: 4 View posts
Posted by Scratliner: Wed. Aug 23, 2017 - 06:10 PM (Reply to #4)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey Taste Test,

do you have solved your problem with the wifi module from atmel?

because i have the same problems with the module. i have send with the ATSAMD21 over SPI the Info Bytes 0xCA... and i became the same answer. How do you solve it?

Top
avngers92
avngers92's picture
Level: Wannabe
Joined: Thu. Apr 14, 2016
Posts: 71 View posts
Location: brooks
Posted by avngers92: Thu. Sep 14, 2017 - 09:07 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The IRQ pin configuration is done in conf_winc.h and in nm_bsp_samd21.h. The interrupt should be configured as falling edge. the power up sequence of the ATWINC1500 should be as per the section 9.3 Power-Up/Down Sequence and this is controlled by the CHIP_EN,RESETN and WAKE lines. These GPIOs are also configured in conf_winc.h

 

Attachment(s): 

PDF icon Atmel-XXXXX-WINC1500-SPI_Porting_Guide.pdf
Top
DejanSpasovski
DejanSpasovski's picture
Level: New Member
Joined: Wed. Oct 31, 2018
Posts: 1 View posts
Posted by DejanSpasovski: Wed. Oct 31, 2018 - 03:16 PM (Reply to #6)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Michael. Can you please explain how exactly you solved your problem with the IRQ on winc1500. I am having the same problem, I get the firmware version and other communication seems to work well but I do not have interrupt from winc1500. Confirmed with an oscilloscope.

What do you mean by "the master need to clock out LOW levels on reading. " Please share this knowledge as I am stuck here. I know this was a long time ago but I appreciate it very much if you can give me some clues for where I am getting it wrong. 

Also if anyone else have overcome this problem Please send some hints??

 

Regards 

​​​​​​​Dejan

Top
jwhellen
jwhellen's picture
Level: New Member
Joined: Wed. Dec 18, 2013
Posts: 4 View posts
Posted by jwhellen: Mon. Sep 21, 2020 - 08:56 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm  aware that this is an old post but it is still relevant. I do have the same problem, that is, the IRQN is not asserted. Communication with the WINC1500 seems OK. Does anyone now how to solve it?

 

The firmware version is 19.6.1 

 

Thanks Wim

Top
jwhellen
jwhellen's picture
Level: New Member
Joined: Wed. Dec 18, 2013
Posts: 4 View posts
Posted by jwhellen: Mon. Sep 21, 2020 - 09:46 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jwhellen wrote:

I'm  aware that this is an old post but it is still relevant. I do have the same problem, that is, the IRQN is not asserted. Communication with the WINC1500 seems OK. Does anyone now how to solve it?

 

The firmware version is 19.6.1 

 

Thanks Wim

 

The interrupt is working when scanning for AP. I was trying to use Direct WIFI using the call to m2m_wifi_p2p. I assume this is not supported anymore? Is there a workaround ?

Top
Saidevaraj
Saidevaraj's picture
Level: New Member
Joined: Fri. Sep 18, 2020
Posts: 1 View posts
Posted by Saidevaraj: Mon. Sep 21, 2020 - 12:20 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

I am trying AP scan program using ATWINC1510 with MSP432. Under HIF layer sends the request to the WINC chip section - step 3, after i sent 0x150400 in nm_read_reg_with_ret i got DMA address as E8F20 address instead of  0x037AA0. After that it comes like "Failed data response read c3 4 0" followed by "Failed block data write...".  I have ported all driver files from SAMD21, i changed BSP_INIT, nm_bus_wrapper_samd21.c, conf_winc.c files.

For chip id response i got as

Chip ID 1503a0
13301361 13301361 102
Firmware ver   : 19.6.1 Svnrev 16761
Firmware Build May 23 2018 Time 14:39:16
Firmware Min driver ver : 19.3.0
Driver ver: 19.6.1 

Could you plzz say what mistake i have done.

Top
jwhellen
jwhellen's picture
Level: New Member
Joined: Wed. Dec 18, 2013
Posts: 4 View posts
Posted by jwhellen: Thu. Sep 24, 2020 - 06:49 AM (Reply to #13)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I really have no idea. I use the latest ASF (xdk-asf-3.48.0\common\components\wifi\winc1500\host_drv) and updated the bsp files (incl wrapper) to support a general STM32 processor. I don't look at individual register and stuff. Used the wifi API as is. 

 

Sorry.

Top