- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Support,
I am evaluating the module CYW943907AEVAL1F. I am using the WICED IDE version 6.0.1.5.
I am using the target as "snip.tcp_client-CYW943907AEVAL1F-ThreadX-NetX download run" in the make target after double-clicking on the clean(steps mentioned in the Quick Start Guide).
But this process is taking a too long time(~3-4 minutes). Is there any other way to download the created binary(.elf) file to the module through any command-line or any other software(in Windows PC)? so that time for loading the code into the module can be reduced.
Thanks
Milan
Solved! Go to Solution.
- Tags:
- wiced
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are using FTDI-JTAG, it can be slow. Now WICED supports native J-Link for Murata Type1GC (CYW43907 based module on that platform). So if you can use native J-Link instead of FTDI, it can be much faster.
You can check this makefile for the configuration: 43xxx_Wi-Fi\tools\makefiles\wiced_toolchain_common.mk
# User can assign specific JLINK_PATH & JLINK_EXE manually:
# ex :
# [Win32]
# test.console-CYW943907AEVAL1F JTAG=jlink-native JLINK_PATH="../../../../Program\ Files\ \(x86\)/SEGGER/JLink_V630c/" JLINK_EXE="Jlink.exe" download run
#
# [Linux]
# test.console-CYW943907AEVAL1F JTAG=jlink-native JLINK_PATH="/opt/SEGGER/JLink/" JLINK_EXE="JLinkExe" download run
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
There is no other way of programming the board using USB, you will have to use WICED to program the board
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are using FTDI-JTAG, it can be slow. Now WICED supports native J-Link for Murata Type1GC (CYW43907 based module on that platform). So if you can use native J-Link instead of FTDI, it can be much faster.
You can check this makefile for the configuration: 43xxx_Wi-Fi\tools\makefiles\wiced_toolchain_common.mk
# User can assign specific JLINK_PATH & JLINK_EXE manually:
# ex :
# [Win32]
# test.console-CYW943907AEVAL1F JTAG=jlink-native JLINK_PATH="../../../../Program\ Files\ \(x86\)/SEGGER/JLink_V630c/" JLINK_EXE="Jlink.exe" download run
#
# [Linux]
# test.console-CYW943907AEVAL1F JTAG=jlink-native JLINK_PATH="/opt/SEGGER/JLink/" JLINK_EXE="JLinkExe" download run