Wi-Fi Combo Forum Discussions
Dear All,
I downloaded the package for BCM94343W_AVN from GitHub - CloudConnectKits/WICED-SDK-3.5.2_Platform_Files: BCM94343W_AVN platform files to add to WICED-SDK-3.5.2 in orde… and was able to download the custom build application and run. But, when I run the snip.https_server application, see that there is failure in TLS connection.
Any specific configuration need to be enabled or configured for this to work correctly.
Please find the logs from the system and request to recommend for configurations.
Thanks and regards,
Gupta
>>>>>>>>>>>>>>>>>>>>>>>LOGS for BOOTING>>>>>>>>>>>>>>>>>
Starting WICED v3.5.2
Platform BCM94343W_AVN initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp2
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : B0:38:29:3D:39:71
WLAN Firmware : wl0: Nov 25 2015 12:57:14 version 7.45.45.1 (r602358) FWID 01-1920c040
Connect to the network
Joining : 4CE67640E08C
Successfully joined : 4CE67640E08C
Obtaining IPv4 address via DHCP
DHCP CLIENT hostname WICED IP
IPv4 network ready IP: 192.168.11.58
Setting IPv6 link-local address
IPv6 network ready IP: FE80:0000:0000:0000:B238:29FF:FE3D:3971
Read the certificate Key from DCT
Start HTTPS server
Get IPv4 address
Server ready at 192.168.11.58
Error starting TLS connection
Error starting TLS connection
Error starting TLS connection
Error starting TLS connection
Error starting TLS connection
Show LessI am trying to build snips provided in wiced v3.5.2 for the platform BCM9WCD1AUDIO (SPIL platform - SSB-WM-N02 EVM board). When trying to build for WICED 3.5.2, I get the following build error for all the snips provided as a part of this wiced version for this specific platform. (Though the default platforms provided with WICED 3.5.2 builds successfully.)
Has anyone tried building this platform (BCM9WCD1AUDIO/SPIL-SSB-WM-N02) for Wiced 3.5.2?
Build string:
snip.stdio-BCM9WCD1AUDIO-FreeRTOS-LwIP-debug JTAG=Olimex_ARM-USB-TINY-H download run
Build Error I get for this platform:
Show Less
16:25:44 **** Build of configuration Default for project WICED-SDK ****
"C:\\Users\\user\Documents\\WICED\\WICED-SDK-3.5.2\\WICED-SDK\\make.exe" snip.stdio-BCM9WCD1AUDIO-FreeRTOS-LwIP-debug JTAG=Olimex_ARM-USB-TINY-H download run
MAKEFILE MAKECMDGOALS=snip.stdio-BCM9WCD1AUDIO-FreeRTOS-LwIP-debug download run OTA2_SUPPORT is disabled
make.exe[1]: *** No rule to make target 'WICED/WWD//wwd_ap.c', needed by 'build/snip.stdio-BCM9WCD1AUDIO-FreeRTOS-LwIP-debug/Modules/./WICED/WWD//wwd_ap.o'. Stop.make.exe[1]: *** Waiting for unfinished jobs....make: *** [main_app] Error 2Makefile:220: recipe for target 'main_app' failed
16:25:50 Build Finished (took 5s.834ms)
Hi,
Using IOT Starter Kit based on BCM4343W.
We are planning to run the WICED Sdk 3.5.2(MFI certified) on this platform, to make use of the extensive libraries the SDK provides.
we are trying to run the WICED SDK on the STM32F407VG(Discovery board). We were able to flash the bootloader, DCT and the application images using the STlink JTAG. When the system boots, the bootloader is running, but the app is not getting called from the bootloader code. I would appreciate, if you can help us with this situation.
We have followed the same steps as per below link, but not able run the Application Code.
https://community.broadcom.com/thread/2869?q=STM32F407VG%20Discovery%20board?
I am attaching pdf document which explains the steps that we followed to bring up the STM discovery board.
I am attaching logs that we get while building and flashing.
Kindly help on the solution for the situation mentioned.
Regards,
Jagadish
Show Lessfollowed the quick start guide.
renamed my working make target from "snip.bluetooth.ble_proximity_reporter-BCM943341WCD1 download run" to "snip.bluetooth.ble_proximity_reporter-BCM943341WCD1-debug download"
clicked "snip.bluetooth.ble_proximity_reporter-BCM943341WCD1-debug download" and am able to see app build and download on console:
snip_bluetooth_ble_proximity_reporter-BCM943341WCD1-debug
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
:
----------------------------------+---------+---------|
TOTAL (bytes) | 657236 | 53084 |
----------------------------------|---------|---------|
Downloading Bootloader ...
No changes detected
Download complete
Downloading DCT ...
No changes detected
Download complete
Downloading Application ...
No changes detected
Download complete
Build complete
Making .gdbinit
However when I click the green bug icon I get the following prompt :
The selection cannot be launched, and there are no recent launches.
Show LessI am able to receive raw wifi packets which include all the fields in the ieee80211_header_t structure via wwd_wifi_enable_monitor_mode().
Is there a way to *send* raw wifi packets where I specify the fields in the ieee80211_header_t structure and send it?
I have found things like wiced_cooee.c that appear to dance around that capability but I cannot find an example where it is actually done.
I am using the BCM43341WCD1 evaluation kit as my platform currently.
Roger
Show LessWiced Version: 3.1.2.
I am using self signed certificates generated with OpenSSL for a server I want to connect with a WICED Wi-Fi module. On certain certificates I get an error while loading/parsing the certificate with wiced_tls_init_root_ca_certificates. The result error code is 3035.
Further investigation has shown that this problem is depending on how start and expiration date is set during generation of the certificate.
Not working example:
openssl req -new \
-config etc/root-ca.conf \
-out ca/root-ca.csr \
-keyout ca/root-ca/private/root-ca.key
openssl ca -selfsign \
-config etc/root-ca.conf \
-in ca/root-ca.csr \
-out ca/root-ca.crt \
-extensions root_ca_ext \
-startdate 20150101120000Z -enddate 20160101110000Z
Results in this not working certificate:
-----BEGIN CERTIFICATE-----
MIIDXDCCAkSgAwIBAgIBBDANBgkqhkiG9w0BAQUFADA9MQswCQYDVQQGEwJDSDEO
MAwGA1UECgwFRXJnb24xCzAJBgNVBAsMAkVTMREwDwYDVQQDDAhFcmdvbiBFUzAi
GA8yMDE1MDEwMTEyMDAwMFoYDzIwMTYwMTAxMTEwMDAwWjA9MQswCQYDVQQGEwJD
SDEOMAwGA1UECgwFRXJnb24xCzAJBgNVBAsMAkVTMREwDwYDVQQDDAhFcmdvbiBF
UzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMktBPphlQqgd7/3oQ6S
bnB68E/O8p8OR07AHeleBlOPr6qzcGmLpTJiREaw2FYK5OuEVvlwqd7IHzm4P3l5
khLMBRCSSq3tgOV/+5RJUd1CeH26Tur6jIJdZWkF9AbrxIJVhTeFp0vp5SbFUI6+
mCC5cybeNsytcDL8T1UvabIJvJpZrl3+s2kfLDsD77k5q8Ic+l4xUIhQKKbK4piA
no6+OUdmqBMWq3xz9PZeuu/ZclHKl9HbP5vzZ9reHZYUQiF01T4fEVp7gt8I6JYK
EWlFa5bTgOTrIIllINOlamj4EABALrLJG94k4E1tLO46Zn8ZF6sfsHDM3VXVoWl0
TpcCAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQFMAMBAf8wHQYD
VR0OBBYEFMJ/8+Bs9yh3k+7D4Sy2E/vjXvgzMB8GA1UdIwQYMBaAFMJ/8+Bs9yh3
k+7D4Sy2E/vjXvgzMA0GCSqGSIb3DQEBBQUAA4IBAQCZ1FnebQY1ARj/sCA7jf/F
KzzX7ZmCYV1Wmkvt+g7BSmubcHgXNiDU2KCDeXt3oxz4P/Pwpnz3WxxaeU/NbCF4
GKCrpgy4myYcAch4AyUw1IkesfQZ55VAPYufCS9DHka3kj+OVXRv8tbyvZfKNXuF
Rx41IBvkCKSGLXL9CQExUxZD7VoKwQfNhwoh6b7MAIq478gSXb9LcunWkXIdj0ks
vbHjZTxv+0Jd7I2NctYuu3szyXRV0puTFewjBDYBgMrIn8ZpVsGZvI7fc6/t/9sE
a9JbZECun8rKSWZ57KPfJ2sAMCfA158casUVdkCel2+ioWKOnlCdTD0Yt0H34+6U
-----END CERTIFICATE-----
But if the expiration is set in days with the following command:
openssl ca -selfsign \
-config etc/root-ca.conf \
-in ca/root-ca.csr \
-out ca/root-ca.crt \
-extensions root_ca_ext \
-days 365
Results in this working certificate:
-----BEGIN CERTIFICATE-----
MIIDWDCCAkCgAwIBAgIBBjANBgkqhkiG9w0BAQUFADA9MQswCQYDVQQGEwJDSDEO
MAwGA1UECgwFRXJnb24xCzAJBgNVBAsMAkVTMREwDwYDVQQDDAhFcmdvbiBFUzAe
Fw0xNTA0MjQxMzE4MTZaFw0xNjA0MjMxMzE4MTZaMD0xCzAJBgNVBAYTAkNIMQ4w
DAYDVQQKDAVFcmdvbjELMAkGA1UECwwCRVMxETAPBgNVBAMMCEVyZ29uIEVTMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyS0E+mGVCqB3v/ehDpJucHrw
T87ynw5HTsAd6V4GU4+vqrNwaYulMmJERrDYVgrk64RW+XCp3sgfObg/eXmSEswF
EJJKre2A5X/7lElR3UJ4fbpO6vqMgl1laQX0BuvEglWFN4WnS+nlJsVQjr6YILlz
Jt42zK1wMvxPVS9psgm8mlmuXf6zaR8sOwPvuTmrwhz6XjFQiFAopsrimICejr45
R2aoExarfHP09l6679lyUcqX0ds/m/Nn2t4dlhRCIXTVPh8RWnuC3wjolgoRaUVr
ltOA5OsgiWUg06VqaPgQAEAusskb3iTgTW0s7jpmfxkXqx+wcMzdVdWhaXROlwID
AQABo2MwYTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4E
FgQUwn/z4Gz3KHeT7sPhLLYT++Ne+DMwHwYDVR0jBBgwFoAUwn/z4Gz3KHeT7sPh
LLYT++Ne+DMwDQYJKoZIhvcNAQEFBQADggEBABqlLoN1sKtRaETHw+kkNcSkEqp2
EB0wPFuQAtJWdfCuM17nhK5GpJiAhT/jfVu+TnfGkLi8Pp+x4kuTeClPS23NgOy4
OH6C30Zr+uRSmjwgpdA6fSGjB8rBGrGq2PlEu/8bQuYKcLbdY3upI74CvWxvNdyj
mz6F8ygcq7ksOhsh/1bvpoTDqzV04xCCeE9jwYOvh7/TZBGGugFH5KArQf15vOk/
FwCAsxtG6DJaRpMsd40X6LoPOVUTNnMYO6ZZyenhReNj1YviA5RzHWit/DTGa08p
GoNFkHs782zb0a+zLoI+Q/FiWWA//QkVjlMoSOj/Oh+oLhuAp96dT8x5OuI=
-----END CERTIFICATE-----
Is this a known issue. Other tools say both certificate are perfectly valid:
Certificate Decoder - Decode certificates to view their contents
Attached you also find the root-ca.conf file, to replay the examples from above.
Thanks and BR
Gert
Show Less