Broadcom BCM943364WCD1 C-SDK Setup Guide (v 1.0)
14
2.
Verify that the edited files (SSID, Appkey, IP address) are exactly
correct with no syntax errors, such as a missing quotation mark. The
Appkey must be exactly correct, the server hostname should be correct
(for IP addresses, type the IP address without “http”).
3.
Try to use a different version of either the WICED SDK or ThingWorx C-
SDK.
3.
The device is not visible via USB / Serial in
either a guest or host operating system
1.
Follow directions from your virtual machine provider to ensure that the
device is connected via serial in “pass-through” from the host computer.
2.
For problems with the host computer, make sure you have the WICED
drivers installed before connecting the device to your computer. Use
Windows and download/install the WICED 3.5.x .exe installer, which
includes serial drivers, from
https://community.broadcom.com/community/wiced-wifi/wiced-wifi-
documentation
4.
Cannot connect to the device via PuTTY or
another terminal program, or no console output
1.
Verify that the device is properly connected to the computer or virtual
machine you are attempting to view the console from.
2.
Verify that the proper USB serial drivers are installed.
3.
Verify that the baud rate of the serial connection is 115200.
4.
Verify that the SDK has compiled correctly on the device. Disconnect it
and reconnect it before trying again.
5.
Try an alternative terminal program, such as PuTTY or HyperTerminal.
5.
Cannot bind a Thing to the Broadcom Device in
Thingworx.
1.
Ensure that the Thing name you are creating is
exactly
the same as the
device’s ID in the ThingWorx Unbound Things page. The Thing name
can alternatively be customized if it is set to be an identifier in the
source code.
2.
Ensure the Thing you are creating is of the RemoteThing Template.
3.
Refer to ThingWorx support for further assistance.
6.
Device will not connect to ThingWorx server / is
not visible under “Unbound Things”.
1.
Check the “All” tab instead of the unbound things tab to confirm that the
device is not already bound to a Remote Thing.
2.
Double-check the connection settings in “
thingworx.c
”. Re-compile if
changes were necessary.
3.
Confirm that the wifi network is active and that the connection
parameters in “
wifi_config_dct.h
” are exactly correct. Switch to testing
on an unsecured wifi network if necessary. Ensure you have the latest
WICED SDK installed. Contact Broadcom if the device will not connect
to any WiFi network.
4.
Verify that no firewall or network configuration settings are preventing
the device from communicating with a remote ThingWorx server.
This is
a common problem.
5.
Test on a locally-hosted ThingWorx platform to rule out internet
connectivity issues.
