Could you please give some clarifications on the setting of the listen_interval (wiced_wifi_set_listen_interval and wiced_wifi_set_listen_interval_assoc) ?
The documentation states that the first function should communicates the listen_interval to the AP. This seems to be true, but only during the association. If I change the listen_interval after that, the function does not communicate the new value to the connected AP, even though the change is effective.
Why is that ? Is there a problem with updating the listen_interval while connected ? How can I let the AP knows that I want to change / changed the listen_interval without disconnecting ?
Thanks for your support.
In my application I need to know what beacon period and DTIM interval are set for the AP that my device (CYW4343W in Type1DX with WICED 6.6) is connected to.
I'm calling wiced_get_bss_info to achieve that. Most of the time, it works fine, however, for some unknown reason it sometimes starts to fail and then fails continuously with the error code 2014 (Buffer too short).
What are the possible reasons for such error for this function ? How can I prevent that ? Is there any other way to get the beacon / DTIM information ?
Thanks for your support.
We uses Murata Type1LD and recently found an issue with 'malloc'. 'malloc' fails to allocate space even though heap has plenty of space. We checked heap status and it shows as below,
sbrk heap size: 206916
sbrk current free: 163832
malloc arena: 43084
malloc allocated: 42300
malloc free: 784
It seems like malloc does not uses all the available heap space (163KB free). We would like to know whether there is any way to configure Wiced (via ld file or any other method) to use all available heap space in malloc. It seems like Wiced uses FreeRTOS 'heap_3' implementation. Any help on this is highly appreciated
In our application, we connect to wifi AP and do stuffs. If we got some issues like request http error or disconnect with mqtt broker, we will retry to connect again. Incase retry not success we will disconnect with wifi AP and retry to connect current wifi AP again or connect the another wifi AP.
But sometime we got stuck forever in wiced_leave_ap.
I use CYW54907 with Wiced studio 6.6.Show Less
We are using Cypress Murata 1MW Wi-Fi + BT combo module in i.Mx8MP &
i.MX8M mini Dev. Kit. and Android11.0.0_1.0.0 (5.4.47 kernel)
We are facing issue with Wi-Fi(5GHz and 2.4GHz) throughput values.
Getting below throughput values in 5GHz,
Transmit - 120MB/s
Received - 150MB/s
Getting below throughput values in 2.4GHz,
Transmit - 25MB/s
Received - 30MB/s
NOTE: From kernel side we are getting expected throughput values, but in android side we are getting very low throughput values.
Is there any source code changes is required from android layer side?
We have used Wiced SDK for Type 1LD development. Wiced doesn't supports LWM2M protocol. We are trying to port an open source LWM2M implementation like Wakaama/Anjay to Wiced SDK. But it seems like the mbedtls module available with Wiced /type 1ld have been tweaked at many places (compared to open source version). This creates a lot of issues in the UDP/TCP layer. We know that Wiced /type 1ld uses mbedtls to support many built in modules (like WiFi). Hence it is not possible to tweak or replace the Wiced /type 1ld mbedtls version. At this point, we think that it might not be possible to port an open source LWM2M implementation to Wiced SDK.Show Less
I have followed this instructions for DEBUGGING in my CYW9443907AEVAL1F
but I cannot see all the threads in my window, is there any option to this?
Hello, I followed this link to debug with my CYW9443907AEVAL1F:
And I followed all the instructions there in the word file to debug with GDB
It seems like it try but the log says that it cannot read the registers
I'm going to attach the complete log., Does anybody knows what its wrong?
Also I saw a comment in that post about doing a target with the debug option, I made this:
test.console-CYW943907AEVAL1F-debug JTAG=jlink-native JLINK_PATH="C:/Program\ Files\ \(x86\)/SEGGER/JLink_V720/" JLINK_EXE="JLink.exe" JLINK_DEVICE=CYW43907 JLINK_SPEED=auto JLINK_INTERFACE=JTAG JLINK_AUTO_CONNECT=1 download debug
But in this case I got an error like this
warning: File "C:\Documents\WICED-Studio-6.6\43xxx_Wi-Fi\.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
line to your configuration file "$HOME/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "$HOME/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
.gdbinit_attach:1: Error in sourced command file:
localhost:3333: No connection could be made because the target machine actively refused it.
But when I set that instruction in gdbinit file, when I run again the target, WICED STUDIO will override it and delete that instruction, does anybody knows how add it?
Thanks and regards
Hello, I have a CYW943907AEVAL1F board and I have an issue:
I'm testing the last version of SDK: 220.127.116.11 and with "test.console-CYW943907AEVAL1F download run" target. I'm testing with peap protocol.
And I have WWD_NOT_KEYED as result:
TLS handshake failed with error = 
Join result 1007:
Supplicant result = 
And in the freeradius side I can see only a "Send Accept Challenge" but I dont get an "Send access acept".
1.- What things do I have to modified in order to test it with peap protocol?
2.- The first step in the user guide says that we need to configure the certificates, is it needed for peap? if yes, which one?
I already tried to replace WIFI_USER_CERTIFICATE_STRING with CA.pem and server.pem and it doesnt work.
3.- If it's needed a certificate, is there a way to avoid it in code?
4.- I saw a variable named eap_identity and I set to "testing" which is my user, is that correct? Or how can I set that variable?
I started poking around to see if I can get my build files packaged up so we can use them during manufacturing. It looks like the normal build command doesn't create build/$project/APP.bin, but we use that to jlink flash controllers during manufacturing. I started poking around to see how it gets pulled in and it looked like adding either "download" or "package" should build it. I confirmed it happens during download (but that tries to actually use jlink and download to a device). I noticed just adding "package" doesn't do anything. After digging in more I noticed it was setup like this:
$(QUIET)$(ECHO) Created package successfully
$(RELEASE_PACKAGE): create_package_descriptor \
$(STRIPPED_LINK_OUTPUT_FILE) display_map_summary \
package_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,package_dct) package_app package_apps
in tools/makefiles/standard_platform_targets.mk, but RELEASE_PACKAGE isn't defined anywhere. If I pass in something defining it on the make line, I get the next issue:
make: *** No rule to make target `create_package_descriptor',
I can't find any info on create_package_descriptor. I was wondering if this was meant to be removed and/or if I'm even going about this the right way. I'm currently using WICED-Studio-18.104.22.168 but I also tried on WICED-Studio-6.6.1 and saw the same issue. Any help or guidance would be appreciated.