WICED™ Studio Forum Discussions

Hello,

I opened an old program to update my electronic card by reinstalling WICED Studio 6.6.1.

When attempting to program my card with JTAG , I received the following error message:

"Making snip.scan-BCM943362WCD4.bin
Downloading Bootloader ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading DCT ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading Application ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Resetting target"

Could someone please explain the steps to install or test the setup correctly?

Hello,

I am trying to run the udp_transmit example included in the Wiced Studio SDK. 
This works fine if no changes are applied.

However, I would like to use the Ethernet interface instead of the Wi-Fi interface.

Unfortunately, I am having troubles running it.

Description

In order to use the Ethernet interface instead of the Wi-Fi one, I modified the "/43xxx_Wi-Fi/apps/snip/udp_transmit/wifi_config_dct.h" as follows:

#define WICED_NETWORK_INTERFACE   WICED_ETHERNET_INTERFACE

The target build command is:

snip.udp_transmit-CYW954907AEVAL1F-FreeRTOS-LwIP-debug download run

Problem

By running the application with this change, I get an exception in the Cypress board output terminal.

Starting WICED Wiced_006.006.001.0001
Platform CYW954907AEVAL1F initialised
Started FreeRTOS v9.0.0
WICED_core Initialized
Initialising LwIP v2.0.3
DHCP CLIENT hostname WICED IP
WLAN MAC Address : B8:D7:AF:4D:1E:D6
WLAN Firmware    : wl0: Jul 20 2020 00:08:56 version 7.15.168.149 (21d266a) FWID 01-d4dbc762
WLAN CLM         : API: 12.2 Data: 9.10.74 Compiler: 1.31.3 ClmImport: 1.36.3 Creation: 2020-07-20 00:01:06
=== EXCEPTION ===
Debug event (e.g. breakpoint)
DFSR : 0x00000000
DFAR : 0x00000000
IFSR : 0x00000002
IFAR : 0x004AED46
CPSR : 0x00000197
R0   : 0x00000003
R1   : 0x00000000
R2   : 0x00000000
R3   : 0x00000003
R4   : 0x04040404
R5   : 0x05050505
R6   : 0x06060606
R7   : 0x005356B0
R8   : 0x08080808
R9   : 0x09090909
R10  : 0x10101010
R11  : 0x11111111
R12  : 0x00000029
LR   : 0x004AED46
=================

After debugging, it pointed to a missing definition of "WICED_USE_ETHERNET_INTERFACE".

What I did then is to uncomment the "WICED_USE_ETHERNET_INTERFACE" definition in "wiced_defaults.h".

However, by doing so I get the following build error message:

Compiling WICED_LwIP_Interface 
WICED/network/LwIP/WICED/wiced_network.c: In function 'wiced_ip_driver_notify':
WICED/network/LwIP/WICED/wiced_network.c:933:24: error: implicit declaration of function 'platform_ethernet_start'; did you mean 'platform_hibernation_start'? [-Werror=implicit-function-declaration]
             result = ( platform_ethernet_start( ) == PLATFORM_SUCCESS ) ? WICED_SUCCESS : WICED_ERROR;
                        ^~~~~~~~~~~~~~~~~~~~~~~
                        platform_hibernation_start
WICED/network/LwIP/WICED/wiced_network.c:937:24: error: implicit declaration of function 'platform_ethernet_stop'; did you mean 'platform_tick_stop'? [-Werror=implicit-function-declaration]
             result = ( platform_ethernet_stop( ) == PLATFORM_SUCCESS ) ? WICED_SUCCESS : WICED_ERROR;
                        ^~~~~~~~~~~~~~~~~~~~~~
                        platform_tick_stop
cc1.exe: all warnings being treated as errors
tools/makefiles/wiced_elf.mk:232: recipe for target 'build/snip.udp_transmit-CYW954907AEVAL1F-FreeRTOS-LwIP-debug/Modules/./WICED/network/LwIP/WICED/wiced_network.o' failed
make.exe[1]: *** [build/snip.udp_transmit-CYW954907AEVAL1F-FreeRTOS-LwIP-debug/Modules/./WICED/network/LwIP/WICED/wiced_network.o] Error 1
make.exe[1]: *** Waiting for unfinished jobs....
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2

Is there a way to run this demo application with the Ethernet interface?

Thanks for your help!

when I read the register of CHIPCOMMON_SR_CONTROL1 to check if the firmware initialized sr engine, it failed, so I wondered how to enable or disable the sr feature, or the firmware initialize the sr feature itself?

Keep getting those errors when connecting bonded Cysmart to CYW20719:

Status : Connection Terminated Due to MIC Failure (0x3d)

Encryption Status Event: bd ( 5a 10 0c ef 51 aa  ) res 8109

The CYW20719 hardware is CYBT_413034_EVAL.

Clients are Samsung TAB E 7” and Tab A 8” tablets with Android 4.4.4, 5.0.1 and 6.0.1

This error happens:

1. Always if I pair let say Cysmart client1 on Android device 1 and disconnect, then pair another let say Cysmart client2 on Android device 2 and disconnect, RESET the CYW20719, then when return back to device1 and try to connect to CYW20719 (on Cysmart button on the right side shows ‘Paired’) so just click on the name of the CYW20719 a.k.a ‘Hello’ to reconnect and always (100%) will get ‘Connection Terminated Due to MIC Failure (0x3d)’.  So there is some logic to get error in this situation, because ‘hello_sensor’  code stores bonding info only for 1 bonding, but why this error will be MIC – isn’t MIC (message integrity check)  something similar to CRC?
2. Random – this is the most annoying problem, because it happens when only one Device is bonded and  only this device trying to reconnect – sometimes connect, sometimes fail with the same MIC failure error (0x3d). And I tried plenty of different devices and Android OS versions: 4.4.4, 5.0.1, 6.0.1 and happened only with CYW20719.

So I already rise this problem couple months ago, but haven’t receive any solution (neither on any of the bugs I reported so far ☹ ), but at least:

Do you have some sniffer tool that could capture raw packets (incl. MIC) in the communication client <> server so to compare what is the difference when reconnecting go smooth and when fail?

Either there is something wrong on the Cypresses BT stack side or something in the timing parameters/syncs in the connection ☹   The only clue I could guess – slower processors with Android have more MIC failures than faster ones ☹ , but when I try reconnecting bonded CC2540 from TI, don’t have any problems neither with Cysmart, nor nRf Connect or other BLE Android clients on the same Android devices that fails with CYW20719 ☹

….

17:29:09.988 1 hello_sensor_management_cback: 17

17:29:09.992 1 Advertisement State Change: 0

17:29:09.992 1 ADV stop

17:29:09.994 RCVD [1] Event from HCI.  Name: HCI_Encryption_Change   (Hex Code: 0x08  Param Len: 4)

17:29:09.994                                   Status : Connection Terminated Due to MIC Failure (0x3d)

17:29:09.994                        Connection Handle : 64 (0x0040)

17:29:09.994                        Encryption Enable : 0 (0x00)

17:29:09.996 1 hello_sensor_management_cback: c

17:29:10.003 1 Encryption Status Event: bd ( 5a 10 0c ef 51 aa  ) res 8109

17:29:10.007 1 encryp change bd ( 5a 10 0c ef 51 aa  ) res: 8109

17:29:10.010 RCVD [1] Event from HCI.  Name: HCI_Disconnection_Complete   (Hex Code: 0x05  Param Len: 4)

17:29:10.010                                   Status : Success (0x00)

17:29:10.010                        Connection Handle : 64 (0x0040)

17:29:10.010                                   Reason : 61 (0x3d)

17:29:10.010 Connection Terminated Due to MIC Failure

17:29:10.014 1 connection_down 5a 10 0c ef 51 aa  conn_id:1 reason:61

…

Infineon AIROC Wi-Fi/Bluetooth Combo STM32 Expansion Pack is an extension of the CMSIS-Pack standard established by Arm. The pack is compliant with the full CMSIS-Pack standard, with additional requirements/restrictions on the final pack to meet the STM standard.

This SW pack uses libraries from the Infineon ModusToolbox environment. 

• Infineon GitHub landing space - https://github.com/Infineon/stm32-connectivity/releases
• Infineon AIROC Wi-Fi/BT STM32 Expansion Pack v1.4.0 – https://github.com/Infineon/stm32-connectivity/releases/download/release-v1.4.0/Infineon.Connectivit...
• Infineon AIROC Connectivity STM32 User Guide v1.4.0 – https://github.com/Infineon/stm32-connectivity/blob/release-v1.4.0/Documentation/STM32ConnectivityEx...

What's Included?

• Infineon AIROC Wi-Fi / Bluetooth Combo Release for STM32H7xx, H5xx, U5xx & L5xx MCUs family

What Changed?

v1.4.0

• Added STM32H5xx support
• PAL improvements and fixes
• New Examples added for STM32H747I-DISCO and STM32U575I-EV
• Wi-Fi offload - TCP/IP Keepalive offload

Supported STM32 Boards and MCU

• STM32H747I-DISCO Discovery kit and STM32H7xx
• NUCLEO-H563ZI board and STM32H5xx
• STM32U575I-EV Evaluation board and STM32U5xx
• STM32L562E-DK kit and STM32L5xx

Supported Connectivity Modules

Infineon's CYW43xxx Wi-Fi-BT combo chip family:

• CYW43012
• CYW43439 / CYW43438 / CYW4343W
• CYW4373 / CYW4373/E

Example apps inside the Pack

Wi-Fi Scan Example

This example initializes the Wi-Fi device and starts a Wi-Fi scan without any filter and prints the
results on the serial terminal.

Refer to Projects/STM32H747I-DISCO/Applications/wifi_scan/readme.txt for more details

Wi-Fi Onboarding with Bluetooth LE Example

This example demonstrates a simultaneous usage of Wi-Fi and BLE functionality of CYW43xxx combo
devices. It uses BLE on the combo device to help connect the Wi-Fi to the AP.

Refer to Projects/STM32H747I-DISCO/Applications/ble_wifi_onboarding/readme.txt for more details

Azure RTOS NetXDuo Wi-Fi UDP echo server

This application provides an example of Azure RTOS/NetXDuo stack usage. It shows how to develop a
NetX UDP server to communicate with a remote client using the NetX UDP socket API.

BLE Hello Sensor Example

This code example demonstrates the implementation of a simple Bluetooth Stack functionality in GAP
Peripheral role. During initialization the app registers with LE stack to receive various notifications
including bonding complete, connection status change and peer write.

Refer to Section BLE Hello Sensor Example in STM32 connectivity expansion pack user guide for more details.

Wi-Fi TCP keepalive offload

The TCP keepalive offload feature of the Low Power Assistant (LPA) improves the power consumption
of your connected system by reducing the time the Host needs to stay awake to support a TCP keepalive
request. This example describes how to enable TCP keepalive offload and configure four different
sockets for TCP keepalive that can be incorporated into your project from LPA Middleware.

Refer to Projects/STM32H747I-DISCO/Applications/wifi_tko/readme.txt for more details.

Compatible Software

Future release - v1.5.0

• Add Infineon Wi-Fi 6/6E combo chip (CYW55573 - 2x2 Wi-Fi 6/6E, CYW55513 - 1x1 Wi-Fi 6/6E) support.
• TCPKA keepalive (payload) offload with multiple sessions.
• Wake-on-WLAN - wowlpf support for remote wake-up.
• TLS over TKO
• MQTT keepalive

More information

• README.md
• STM32 Connectivity Expansion Pack User Guide
• Cypress Semiconductor, an Infineon Technologies Company
• Infineon GitHub
• ModusToolbox

Hello.

I have the sequent problem:

I have developed a board with CYW943907 and an FPGA.

I have to store FPGA configuration file (1.5Mbyte of size) in the external FLASH (8MByte of size).

I read WICED-Resource-Filesystem.pdf and I understand that I can put the FPGA configuration file in resources/apps/<MY_APP>/fpgaConfig.bin.

I can read fpgaConfig.bin with resource_get_readonly_buffer and I'm happy.

But my problem is that in the future it might be possibile to update this file but I cannot find any resource_write_readonly_buffer API to do this operation.

I'm not sure but I understand that OTA can only update APP and not resource.

Can some one help me ?

Good afternoon. I am facing HTTPS speed issue on CYW943907AEVAL1F platform.
When downloading a file via HTTPS, the speed drops almost 8 times, relative to HTTP (without encryption).
Interestingly, the chip has a crypto core.
Perhaps someone has already worked on this issue?
I'm attaching the test results.

Greetings,

We're having an issue connecting to SOME of our prototype hardware via Seger JLINK  SWD mode.  It works fine on some boards but not others.  While I cannot yet rule out some manufacturing defect - if there is one its not revealed in a 3d x-ray of the PCBA.

Our problem is described in this thread [CYW43907] MCU JTAG Connect Fail but the answer is not very helpful other than we may be looking in the wrong direction.

To be clear, we're using a Murata 1GC module.

Build options are: JTAG=jlink-native JLINK_PATH="/usr/bin/" JLINK_EXE="JLinkExe" JLINK_INTERFACE=SWD download download_apps

Build machine is linux based - but replicated on a Windows 10 platform (with appropriate changes in above for windows machines.

Error text is:

****** Error: Cortex-A/R (connect): Failed to temporarily halting CPU for reading CP15 registers.

Cannot connect to target.

I've tried using JLinkExe from the command line, on a working target:

sean_fendt@ssf:~/src/tf0001$ JLinkExe -device CYW43907 -if SWD -speed 4000
SEGGER J-Link Commander V6.52e (Compiled Oct 16 2019 12:19:21)
DLL version V6.52e, compiled Oct 16 2019 12:19:11

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled May 17 2019 09:50:41
Hardware version: V9.30
S/N: 59304943
License(s): GDB
VTref=3.354V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "CYW43907" selected.


Connecting to target via SWD
Found SW-DP with ID 0x5BA02477
CoreSight AP[0]: 0x44770002, APB-AP
ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-008BBC14 Cortex-R4
Found Cortex-R4 r1p4
4 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0
Data endian: little
Main ID register: 0x411FC144
I-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
TCM Type register: 0x00010001
MPU Type register: 0x00000800
System control register:
  Instruction endian: little
  Level-1 instruction cache disabled
  Level-1 data cache disabled
  MPU enabled
  Branch prediction enabled
Memory zones:
  [0]: Default (Default access mode)
  [1]: APB-AP (AP0) (DMA like acc. in AP0 addr. space)
Cortex-R4 identified.
J-Link>q

And on a non-working target:

sean_fendt@ssf:~/src/tf0001$ JLinkExe -device CYW43907 -if SWD -speed 4000
SEGGER J-Link Commander V6.52e (Compiled Oct 16 2019 12:19:21)
DLL version V6.52e, compiled Oct 16 2019 12:19:11

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled May 17 2019 09:50:41
Hardware version: V9.30
S/N: 59304943
License(s): GDB
VTref=3.353V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "CYW43907" selected.


Connecting to target via SWD
Found SW-DP with ID 0x5BA02477
CoreSight AP[0]: 0x44770002, APB-AP
ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-008BBC14 Cortex-R4
Found Cortex-R4 r1p4
4 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0
Found SW-DP with ID 0x5BA02477
CoreSight AP[0]: 0x44770002, APB-AP
ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-008BBC14 Cortex-R4
Found Cortex-R4 r1p4
4 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0

****** Error: Cortex-A/R (connect): Failed to temporarily halting CPU for reading CP15 registers.

Found SW-DP with ID 0x5BA02477
CoreSight AP[0]: 0x44770002, APB-AP
ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-008BBC14 Cortex-R4
Found Cortex-R4 r1p4
4 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0
Found SW-DP with ID 0x5BA02477
CoreSight AP[0]: 0x44770002, APB-AP
ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-008BBC14 Cortex-R4
Found Cortex-R4 r1p4
4 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0

****** Error: Cortex-A/R (connect): Failed to temporarily halting CPU for reading CP15 registers.

Cannot connect to target.
J-Link>q

I have the feeling something is on the edge of working, but so far I don't know what.  Extensive experiments with strapping, reset timing, etc has not been revealing.  Any thoughts on things to check would be helpful.

Hi,

As title. How to build ClientControl source code in WICED Studio SDK??

If anyway to modify and build custom ClientControl tool  based on code in WICED Studio?

Thanks.

Austin