We are currently developing a product using SPIL BCM4390 based module, SB-WM-N03. However, we found that the EVB boards we have cannot associate AP properly. We have tried both with 3.1.2 SDK and 3.3.1 however, both showed failures.
We also tried with BCM43362 module and it worked OK. We tested this with IP time AP without Security enabled.
If we turned this to AP mode, it works OK.
I am wondering if there is anyone experienced this issue before. It seems that the issue is very basic functionality.
Hope to have some clarification from BRCM.
With both 3.1.2 and 3.3.1, the BCM4390 works fine to associate AP for us.
Did you test it with snip code?
Maybe you need to describe more detail about how you test it.
Thanks for your comment.
Yes, we used snip code.
We will share more details as we try to gather more data point.
What we just found out that it works when the AP is set to 11b/g mode but it does not work when it is set to 11/b/g/n mixed mode.
IPtime AP N704-0v3
Channel Bandwidth: 20/40MH
Channel: Channel 1
Mode: B,G,N mixed
Does it work if you set your AP to 20MHZ only?
In our test, BCM4390 does not work with 20/40 Mix (or Auto) case.
I'm also confused why it does not work in 20/40 Mix.
BTW, can you confirm again if BCM43362 works with 20/40 Mix case?
I want to know if the 20/40 Mix isssue is BCM4390 only or not.
I just did the "20/40 mixed" test on both BCM43362 and BCM4390 myself and
found BCM43362 works but BCM4390 does not work.
So can someone help to fix the "20/40 mixed" for BCM4390?
Note, I test on both sdk-3.1.2 and sdk-3.3.1 and get the same result.
Thanks for your comment.
As you commented, our test also showed this mixed mode failure.
We contacted our disty and asked for an official FW fix for this issue.
Perhaps, you can do the same to your disty folks.
We have contacted the disty for this issue but still don't get the fix so far.
As far as I know, obewen already got the fix, which means the
fix is available.
Can someone help?
How long is "soon"? We are experiencing the same problem here and it is obviously a roadblock for us.
I've checked with the software team and am advised that SDK3.3.1 has all the current fixes integrated. Can you please retest with 3.3.1 and advise if you still see this issue.
We do not support 40MHz operation in the 2.4GHz band as this is not required for Wi-Fi Alliance interoperability certification.
What I meant is that if the AP is set up for mixed mode (20/40MHz), it does not work. If we change it to 20MHz only, 4390 can connect to it. We are using SDK 3.3.1.