Wi-Fi Combo Forum Discussions
Hello,
I have the following:
- WICED SDK 6.1
- SEGGGER J-link Base
- Ubuntu 16.04
I'm building the following make target snip.scan-BCM43362WCD4. We have a custom board with the USI module WM-N-BM-14, I'd like to know if there are some significant changes required in the platform files.
We are seeing the following issues:
Unable to debug with WICED Studio, I see the following error (using the following 43xxx_Wi-Fi_Debug_Linux64 debug with JTAG device: J-Link) :
Using Ozone, and the snip-gpio-BCM43362WCD4.elf. I see that the target in-consistently hits the WDT ISR.
Show LessMAKEFILE MAKECMDGOALS=snip.scan-MurataType1LD-FreeRTOS-LwIP-SDIO OTA2_SUPPORT is disabled
Building Bootloader
In file included from ././WICED/WWD/include/RTOS/wwd_rtos_interface.h:44:0,
from WICED/platform/GCC/time_newlib.c:39:
c:\users\20118776\documents\wiced-studio-6.1.2.uccc\43xxx_wi-fi\tools\arm_gnu\lib\include\stdint.h:9:26: fatal error: stdint.h: No such file or directory
# include_next <stdint.h>
^
compilation terminated.
make.exe[3]: *** [build/waf.bootloader-NoOS-MurataType1LD/Modules/WICED/platform/GCC/time_newlib.o] Error 1
make.exe[3]: *** Waiting for unfinished jobs....
WICED/platform/GCC/mem_newlib.c:40:19: fatal error: errno.h: No such file or directory
#include <errno.h>
^
compilation terminated.
make.exe[3]: *** [build/waf.bootloader-NoOS-MurataType1LD/Modules/WICED/platform/GCC/mem_newlib.o] Error 1
arm-none-eabi-gcc.exe: warning: ./tools/ARM_GNU/bin/Win32/../../lib/include-fixed: linker input file unused because linking not done
arm-none-eabi-gcc.exe: warning: ./tools/ARM_GNU/bin/Win32/../../lib/include-fixed: linker input file unused because linking not done
make.exe[2]: *** [main_app] Error 2
make.exe[1]: *** [bootloader] Error 2
tools/makefiles/standard_platform_targets.mk:87: recipe for target 'bootloader' failed
Makefile:349: recipe for target 'main_app' failed
make: *** [main_app] Error 2
Show LessHi,
I am getting the following error when i am building Wifi sample application on Mac OS High Sierra. "OpenOCD failed ...."
I am trying to build for the target CYW54907 Evaluation kit. OpenOCD drivers are installed. I tried changing the FTDI.kext, but no positive. Has any body gone through this problem?
Regards,
PC
Show LessDear:
Our product need 2 wifi combo which need PCIE or USB interface and not same,can you give me some advices?
Also linux driver need support.
Thanks!
min li
Show LessUsing CYW943907AEVAL1F with Wiced Studio 6.2.1.2.
I am following the instructions in "CYW943907AEVAL1F Evaluation Kit User Guide, Doc. No. 002-18703 Rev. **"
- when I start debug with "43xxx-Wi-Fi_Debug_Windows." as the UG says, I get the following errors
!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2018-12-20 18:40:30.207
!MESSAGE Error with command: C:\tempwork\WICED-Studio-6.2\43xxx_Wi-Fi\tools\ARM_GNU\Win32\bin\arm-none-eabi-gdb.exe --version
!STACK 0
java.io.IOException: W
at org.eclipse.cdt.utils.spawner.SpawnerInputStream.read0(Native Method)
at org.eclipse.cdt.utils.spawner.SpawnerInputStream.read(SpawnerInputStream.java:66)
at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.readStream(LaunchUtils.java:380)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getGDBVersion(LaunchUtils.java:329)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.getGDBVersion(GdbLaunchDelegate.java:312)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:154)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:109)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:97)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
- When I look at debug configurations, "43xxx-Wi-Fi_Debug_Windows." is listed as "GDB Hardware Debugging". When I look at installation details I see "L-Link Debugging" and "OpenOCD debugging", but no GDB (HW) Debugging? Is this expected?
- "WICED-Studio-6.2\43xxx_Wi-Fi\tools\ARM_GNU\Win32\bin\arm-none-eabi-gdb.exe" does exist, I checked
Any ideas?
Show Lesshi.
I tried to install PDL to E drive (USB memory), and it was succeeded.
PDLSetup_2.1.0_3-26-18.exe
But after removing the USB memory, and I tried to reinstall PDL to C drive, a fatal error (fatal.png) occurred.
It occurred on "repairing" PDF, so I guess some setting remains somewhere.
How do i repair it and reinstall PDL to C drive ?
thank you.
Show LessHello,
I am evaluating the cypress CYW943907AEVAL1F module. And I am using the SDK version 6.0.1.5. I am using a tcp_client example and tried to connect to the Cisco AP. I am not able to connect to the AP neither in security mode nor in the open mode. I took the wireless captures and observed the basic association process also did not start. then I used the snip. scan example from the SDK to see whether the AP is updated in scan list and not seen the AP in the list. But I was able to connect the same AP in 5 GHz with open and WPA2 security.
Moreover, Mobile devices were able to connect to the same Cisco AP in 2.4 GHz so the AP seems to be proper in connection wise.
I am attaching the captures here FYR. As per the captures, probe response was seen every time for the probe request from the cypress module.
Can anyone please explain me this behavior.
Thanks
Akash
Show LessHello, what are the default hardware settings for the PSoC 6 CY8CKIT-062 WIFI BT KIT. The embedded DEMO program is not running. Is a W10 USB driver needed to recognize the KIT on the USB Port .........
Status:
1) When Power is applied, DEMO program does not run. TFT Display is blank and white.
2) When KIT is connected ot W10 USB Port, DEMO program does not run. TFT Display is blank and white.
What can be done next ?
Show Less- How should I use the CYW43438WCD1 bluetooth module?
- Do I need another MCU to run the BT stack like blueZ?
- Can the MCU of the EVB supports both WIFI and BT?
- Tks!