Wi-Fi Combo Forum Discussions

Hi,

Is it possible to get the Received Signal Strength Indication (RSSI) of individual packets received in monitoring mode, i.e. Probe Request, Beacon, etc ?

I've searched the community pages, and I've found questions regarding this dating back to 2015. However, I haven't found any solutions.

Any help is much appreciated.

I'm running:

WICED version: Wiced_006.002.001.0002

Chip: CYW43907

/Jesper

I have a custom built binary provided by Cypress in collaboration with our chip supplier that was generated for our implementation of WICED which was version 3.5.2. It's basically the regular version of the firmware, except it has the mfgtest mode enabled. We use this in production firmware since we are using a custom package BCM43341, and need to be able to set the TX power of the chip. Would it be possible to continue using this binary if we were to upgrade our SDK to 6.2.1? If not, what would be the latest version we could upgrade to/is there a custom build we can get again based off the latest SDK?

Thanks,

   Alex

Problem: TCP keepalive support does not seem to be enabled in shipped NetX libraries

Description: I have tested this with multiple SDK versions, for example 6.1. On a HTTP long-poll connection, calling wiced_tcp_enable_keepalive() on the socket seems to have no effect, as verified by Wireshark capture. No keepalive packets are being sent with any combination of
- keepalive interval, tried 3, 10 , 30 and 60 seconds
- setting keepalive before connecting the socket, after connecting the socket.

- And of course, wiced_tcp_enable_keepalive itself returns WICED_TCPIP_UNSUPPORTED, even though it sets nx_tcp_socket_keepalive_timeout on the Netx socket.
- NetX User guide excplictly states that the library needs to be compiled with NX_ENABLE_TCP_KEEPALIVE, which defaults to off.

There are some very old threads on the forums where a custom built NetX library seem to have resolved the issue: How can I use(or change) the <TCP Keep Alive Option>?

Is it possible to provide keepalive-enabled versions of the libraries in SDKs ? Would need this for multiple versions of the SDK releases

I want to add some c++ files in wiced 6.1. Just to check that for c++ compilation,I renamed (apps/snip/)scan.c to scan.cpp and modified scan.mk ,and I found that it fails to compile.

Please let me know the correct way to add and compile c++ files in WICED 6.1.

What I tried is below :

1. Renamed (apps/snip/)scan.c to (apps/snip/)scan.cpp

2. Updated Makefile as following :

*****************************************************************************************************************************

scan.mk

NAME := App_Scan

$(NAME)_SOURCES := scan.cpp

*****************************************************************************************************************************

3.Make Command : snip.scan-XYZ-FreeRTOS-LwIP-SDIO

Build Error

*****************************************************************************************************************************

make.exe[1]: *** No rule to make target 'apps/snip/scan/scan.c', needed by 'build/snip.scan-XYZ-FreeRTOS-LwIP-SDIO/Modules/apps/snip/scan/scan.o'.  Stop.

make.exe[1]: *** Waiting for unfinished jobs....

Building Bootloader

Finished Building Bootloader

make: *** [main_app] Error 2

Makefile:349: recipe for target 'main_app' failed

*****************************************************************************************************************************

Note : It compiles properly without above changes.i.e if compiled as c file.

This is follow up from the earlier EAP/PEAP debug sessions

Occurs every time.

When in local processor memory the connections do not fail.

The error is 1006.

  RESULT_ENUM( prefix, NOT_AUTHENTICATED, 1006 ), /**< Not authenticated */

Dear Cypress technical team

We are developing the WLAN system beased on CYW43907 module.
Now we are working on the radio certificatoin for Japan TELEC.
But we found the issue on 11b-14ch during the test (using Cypress WL tool).

According with TELEC Japan 14ch spec,
Spreading Rate of RF Spectrum
14ch    >= 10
1-13ch  >=5

However, current CYW43907 shows the following result.
14ch  = 6.43  (should be more than 10)
1-13ch = around 6.43    ---> This is OK

In order to get 14ch Spreading Rate more than 10,
we need to get your support ASAP.

Please help!!

I am using the RFCOMM server example from the WICED studio. The RFCOMM server is paired with a Bluetooth client application on an Android phone. The log of HCI messages on the Android indicates that the ACL 2 & 3 Mbps modes are marked as disabled in the LMP feature notification message sent from WICED reference board to the Android phone. It appears that those two modes, the  2 Mbps and 3 Mbps (EDR) features are not turned on by default. I am experiencing a low throughput with the RFCOMM. So I need to turn on the 2 & 3 Mbps features. I know that the BT stack can change the rate (increase or decrease)  based on the RF environment but in this case it should be able to support the higher rates ( at least 2 Mbps) since the client and the server are two feet apart and there are not a lot interferences around them. What configuration table (or parameters) I need to add to the WICED's RFCOMM server example so it flags the 2 Mbps & 3 Mbps (EDR) modes as enabled?

Thanks.

From the monitoring tools I see in an  RFCOMM connection between the WICED and an Android phone, the RFCOMM server on the WICED grants only 1 credit but when I monitored an RFCOMM link between two Android phones I see that the server on one of the Android phone is granting 6 credits to the other Android phone. More credit means more back to back transmission; 6 credit corresponds to the transmission of 6 packets back to back. More back to back transmission can improve the overall throughput.

A credit represents the number of packets that a device can send at a time. Each packet transmission uses a credit, when the credit reaches zero the receiver must grant more credit in order to enable the transmitter to send more packets.

Since the RFCOMM is a credit based protocol what parameter needs to be modified in the WICED studio to increase the RFCOMM credit? Certainly there is an upper limit for the credit, but currently it is set to 1.  There should be some room to tune it higher than 1.

The Android phones are using the Broadcom Wifi/BT chips which is similar to the Cypress reference design.

Thanks.