WINC1500 19.4.4 FW Won't Connect on WPA2

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Background: I’ve been working with the SAMW25H18-MR210PB module and I’ve hit a wall.  Hoping someone has some insight into what might be wrong.  I got it to connect to our WPA2 WIFI network and download the OTA firmware update, so now the WINC is running the latest firmware version, 19.4.4.  My ASF WINC driver version is 19.3.0, ASF version 3.31.  According to the version checks in the ASF, this combination should be acceptable.

 

Problem: After updating the WINC’s firmware, it will no longer to connect to my WPA-2 WIFI network; the same network it previously connected to in order to perform the OTA update.  Atmel’s sample project(s) also will not connect.  The WINC either returns (via wifi call-back) M2M_ERR_AUTH_FAIL, or it just gets stuck (returns nothing and becomes unresponsive).  Access Point mode appears to work – I’m able to connect to the WINC with my smart phone.  The WINC will also connect to an open (unsecured) access point.  But connecting to a secure access point just doesn’t work at all.  Note that no certificate update was done, although I don’t think those certs have anything to do with WPA-2 authentication.

 

Any suggestions where I might look?  What might be wrong?  Is there something new/changed that maybe I'm not doing or doing wrong?

Regarding the firmware: Anyone know what’s the difference between m2m_ota_2b0.bin and m2m_ota_3a0.bin, and how would I know which one to use?

I used m2m_ota_2b0.bin.  One document I found leads me to think that maybe I should have used 3a0, but how would I know?

 

This topic has a solution.
Last Edited: Mon. Oct 17, 2016 - 09:04 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am using 19.4.4 firmware with no issues.  My suggestion would be to try the latest driver library.  The difference in the bin files are the m2m_ota_3a0.bin is used with the rev A hardware.  If your module is fairly modern you should use m2m_ota_2b0.bin

John Malaugh

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John, thank you for taking the time to post.  I appreciate it.  I just checked my ASF source code against the latest ASF stand-alone archive (V3.32.0.48) that can be downloaded from Atmel.  The driver version in that ASF source is also 19.3.0.  All the WINC driver files are identical except for blanks and one comment.  So I don't think that's it.  I'm convinced that either something went wrong during the OTA upgrade, or I'm doing something wrong.  With regard to initialization and connecting, did you do anything different from how Atmel's example code works?  Regarding the hardware rev A or B, our module was purchased this year, so I'm going to assume it's Rev B.

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

For anyone else out there who may be trying to figure this out, here is the answer regarding Rev A versus Rev B WINC1500 chips.

 

Chip ID 1502b1 is Rev A

Chip ID 1503a0 is Rev B

 

Now that I know, it makes sense: the file name follows the chip id.

 

I have solved the problem of the original post. Loading the correct firmware file (3A0) onto Rev B WINC has solved the problem.  It now connects on WPA2 as before.

 

Last Edited: Mon. Oct 17, 2016 - 09:04 PM