Wi-Fi Combo Forum Discussions
text.format{('custom.tabs.no.results')}
Found what appears to be an issue with sleeping for very long periods (> (65535/32768*16) seconds).
stop_mode_power_down_hook() calls a function platform_rtc_enter_powersave(), which has the following code:
/* Change the clocking state of the RTC, so it ticks every 1.25ms while cpu is sleeping - 800Hz clock */
stm32f2_rtc_change_clock( ¤t_clock_state, CLOCKING_EVERY_1p25MSEC );
This code changes the RTC divider input to tick ever 1.25 millisecond instead of every 1 second. Because the RTC WKUP divider is set to CK_SPRE_CLOCK_SOURCE_SELECTED, (basically the result of all the RTC clock dividers, the WKUP clock ticks every 1.25 ms.
The way I noticed this is as follows:
I had a loop that delay for 600s. The delay still functioned correctly, but the MCU would wake approximately every 800 ms.
Doing the math, (600 * 1.25e-3) = 750 ms. Which is pretty close to my observed wakeup frequency. When I removed the stm32f2_rtc_change_clock() call, the RTC only woke up at the appropriate time.
Show LessThis is my second question in the forum, and I just had to come back to ask my question because the response time and the treatment I received was amazing.
Now comes my question. From what I've seen all your wifi modules come embedded with an internal ARM microcontroller or microprocessor (ARM11 and ARMCR4). This makes me think that all of them probably just work with something like AT commands (in my previous question someone answered me that CYW43362 comes programmed to accept AT commands).
My question now is, is it possible for me to run the TCP stack (like lwip) on an external microcontroller? I mean that the internal microcontroller would not have a TCP stack it would just work as a radio, not knowing what it's sending or receiving.
Also, an extra question. The wiced sdk is supposed to be used to program the internal microcontroller or the external microcontroller? It seems to be used to program the exteranl (I haven't looked at the source code because it didn't download/install correctly on my PC)
Show LessHi,
We use WICED SDK 3.5.2 to implement an IoT device which communicated with our backend through Azure IoT Hub (MQTT over TLS).
Since today morning, all our devices went dark. Looking more closely in the WICED application what I can observe is that after a few iterations of SSL handshake, a call to function ssl_handshake_client_async() results to a crash and a restart of the application.
The problem is easy to reproduce, since the only think you need is to target the secure_mqtt sample application to an active Azure IoT Hub instance. Please find attached the log from the execution and crash of the secure_mqtt example project.
If you want a live Azure IoT Hub instance to try it out, I am happy to assist.
I must note that other MQTT clients, like MQTT.fx, operate as expected.
Thanks,
Stavros.
Show LessI have been studying Cypress' wi-fi modules because I want to develop my own application.
I learned that the Amazon Dash Button uses a 850101 (I think it's from USI) module which consists of a cyw43362 (formerly bcm43362) wi-fi module with an integrated cortex m3 microcontroller, and it also uses an external cortex m3 microcontroller. I saw that there are many people hacking the device in order to play with it (thus having a $5 wi-fi enabled board), but when they program it they never say which microcontroller they are programming; the external or the microcontroller internal to the wi-fi chipset.
From what I've read everything made me believe that in order to develop my own board and application I'd need to:
- buy 850101 (or similar) module, which would come programmed, or buy a cyw43362 (there are 2 more, but I'm interested in this one) and then program it with the default program
- buy an external microcontroller (I don't want to use the one inside the module because it doesn't have enough resources for what I want it to do) and connect it to the wi-fi module via SDIO or SPI
- buy passive components and connector
- buy sma antenna for the 850101 (or similar)
I tried installing the SDK (I didn't download 3.7, I downloaded 4.0.7)and taking a look at the source but it doesn't even let me open the zip files for the SDK, so I have no idea what I'm dealing with.
From there I'd have to program the external microcontroller to send commands to the module. The thing is that I don't know how to go on from here:
- Do I need a TCP/IP stack like lwip? is there a port available for lwip for this device?
- If it doesn't need a tcp/ip stack then it means that the device already knows how to send and receive packets, and for that I'd need a set of commands. Does it run on AT commands or is there a document where I can get that info?
- Considering that everything is readily available, can I run a web server with websockets? Can I use REST? Can I use MQTT? Do I need to develop everything myself?
- Does CYW43362 come ready for use with an external microcontroller?
- Is there an API for OTA? I saw somewhere on the site that OTA2 was available for SDK3.7
I readthis document and it made me think that what I want to do is possible, I just can't find the information as on how to procceed.
Show LessHi,
I need to confirm what is the version of iperf supported on WICED SDK 4.0 so the compliance tester can use the same version on PC/Access Point side.
Can anyone help?
Thanks
Show LessHi,
I want to display the data from uart to the webpage(client) via tcp connection. once data has been received wifi module(server) will transmit data to the webpage(client).
If no data has been received for more than 2 minutes(i.e. wifi module is idle) tcp serever(wifi module) is getting disconnected and webpage is showing could not connect to server.
What i have done is iam receiving the data from uart (i don't know the size of the data iam receiving so i have given that wiced_uart_receive_bytes in while condition which receives 1 character till end of string is reached, once it reaches the end of the string iam breaking that loop)after that iam checking for tcp accept and iam trying to send the data........y it is happening ??? how can i make the server not to get disconnected after sometime....please help me...
And how can I change the ThreadX/NetX_Duo to lwIP.....
Thank you!!!
Show LessHi.
I am trying to use the WICED's web socket API. I see that in the web socket library, the default port is set to port 80.
Also, I need some example apps for web socket.
Please help.
Thanks!
Regards,
Manish
Show LessGiven the snip/tcp_server example, how can we learn that the client has gone.
For example a phone client connects to the server and then the WLAN link is shut off on the phone.
The socket continues to wait in wiced_tcp_receive (or timeout if set) but I can find no way to learn that the client is gone.
If the client does a clean disconnect, the server loops back around to wiced_tcp_accept.
How do I make it do this when the WLAN link is shutoff (and similar unplanned disconnects from client)?
Using 3.0.1 or 3.1.0
Show LessHi.
I want to check if the firmware download is good .
So I found the openOCD command 'verify_image'.
I tested each bootloader, DCT, and Application image.
The result is a bootloader, and the application image is normal.
But DCT is not normal.
Can not see the DCT image?
Show Less