This is not a problem with the Anaren. I have three boards with BCM20736S parts installed and none of them will communicate over the radio link when I load applications from the 2.2.1 SDK. I need guidance on how to debug this problem, please.
Thanks in advance,
Can you confirm this works on the TAG3 board that we support here on the forum?
This will give us a common "gold" platform to use for t-shooting. We have had users in the past report that code designed for the 20736 does not run on the 20737 and vice versa, but internally, our developers are not sure how this could occur. One or two of the users experimented with the platform files for each and ended up resolving the issue.
With the exception of the RSA libraries that are only loaded if used, the two parts are identical.
I cannot find a source for TAG3. I checked Mouser, Avnet, Digikey...
Is this the same as the board that comes with BCM92073X_LE_KIT ? ... or point me to the source for a TAG3.
Ok, I have one on order.
I received the TAG3 board, but it turns out that it uses the BCM20737 part. I was hoping to compare my operation of the BCM20736S to a board with the same part, since that is what appears not to work in my case.
In the meantime I was able to get the stock speed_test app working on my board, but for reasons I do not understand. The app pairs and is then able to communicate fine with the provided Windows SpeedTest.exe app. The trick was that I had to setup and use a make target using BCM920736 rather than BCM920736TAG_Q32. Why would this be required?
speed_test-BCM920736 download - WORKS!
speed_test-BCM920736TAG_Q32 download - DOES NOT WORK
Any ideas why the 2nd make target would work for everything else, but not support BLE pairing and connection?
The 20737 on the tag3 is a SoC (chip) whereas you are using the SIP module flavour on your board. How did it fail? Did you include the crystal warm-up fix?
ENTRY "PMU Crystal Warm up Time"
"Crystal warm up time" = 5000
1 of 1 people found this helpful
As far as described above, yes.
But the work around (also described above) was to use BCM920736 instead of the suggested alternative.
"speed_test-BCM920736TAG_Q32 download" - DOES NOT WORK
"speed_test-BCM920736 download" - WORKS