Wi-Fi Combo Forum Discussions
Hi Sir,
The development environment is based on Wiced SDK6.2.1
For the PAIRING_MODE issue, we have test and detail information and project list is in below, could you help to check?
After tested, SDK seems doesn`t support WICED12 for enable PAIRING_MODE,
Because the error message is mean : no function for wiced12 to execute pairing mode (no include file).
tried to add include function to wiced12 as below figure, and it can not compiler/warning download to module.You can see the compiler failed in the attached files about JPG ,TKS!
Show LessThere are a few interfaces we're not using in our design. Is there a list of what to do with unused inputs or I/O lines on SDIO, MII, S/PDIF, or USB interfaces? Are they internally pulled to safe / idle states, or do they need to be manually strapped? If they need to be tied, are resistors required or can we connect directly to VIO/GND? I realize this may depend on the signal / interface signal, but a list of what to do with unused signals would be very helpful.
Show LessHello
I was wondering if the CYW43353 supports the concurrent AP+STA mode for working as a Wi-Fi repeater. I can't find this information in neither the device datasheet nor this forum.
Best regards,
Eduard
Show LessAny tips and tricks to enable multi-threaded debugging in Wiced Studio?
With default configuration I cannot debug my application - the moment Wiced RTOS port calls the xTaskCreate() it is game over from debugging point of view.
I searched internet and I found this article:
FreeRTOS ARM Thread Debugging with Eclipse and GDB | MCU on Eclipse
It is nice, but wouldn't it be great if Wiced Studio by default has support to enable the multithreaded debugging?
What I need is:
1) see the threads in Eclipse debug window
2) Be able to suspend and resume thtreads
3) place a breakpoint in any thread
Show LessCYW43438是否支持蓝牙mesh?
I use Wiced Studio 6.4 and one of Cypress evaluation boards. My connection between PC and board is based on USB.
There is gdb debugger backend on Eclipse using OCD protocol to communicate with the board.
It works somehow, but about 25% of the attempts to start debug sessions were unsuccessfull:
At first only reboot of Windows helped but that was awful experience.
Until I realized that BCOM, sorry Cypress have done a driver for OCD called openocd-all-brcm-libftdi.exe.
When the error above happens go to your task manager and kill openocd-all-brcm-libftdi.
It will clear the error.
Show LessIt appears that there is a bit of a memory leak on my HTTPS web server and HTTPS client. The common link is TLS.
After repeated serving of web pages to a given client (via the web server) or periodically connecting to an external server (via the client), printing malloc_info shows the arena/uordblks/keepcost counting in one direction (and that direction is "up").
I see various threads on TLS memory leaks on this forum, but none that are recent, helpful or conclusive.
I was wondering if anyone has observed this recently, and if so, were there any debugging techniques that were hepful? Digging into the underbelly of TLS doesn't sound like a fun project...
Suggestions are welcome. Thanks!
Show LessAs I reported in a separate trouble report (see note, below), I observed that the HTTPS web server suffers from a memory leak using SDK6.2 when repeatedly serving pages to a client. When I revert to SDK6.0, the problem is gone.
So, starting with the SDK6.2 code environment, I imported the following code from SDK6.0 into it:
- Files in the directory: "mbedtls_open/"
- Individual files: wiced_tls.c, tls_types.h, wiced_tls.h
- I needed to edit the files x509_crt.cb and pkparse.c by replacing "strnstr" with "strnstrn".
With these changes, the build worked, and the memory leak was not present. So, it appears that code changes were made in the WICED files or the mdedtls code that caused the memory leak.
Is this of interest to the WICED development team, and if so, is this something that can be addressed? I think it is quite a major problem.
(Note: the previous trouble report with additional information is here: TLS Memory Leak on HTTPS Web Server and HTTPS Client (CYW943907AEVAL1F))
Show LessRegarding the document (Doc. No.: 002-20894 Rev. WICED™ Development Power Save System), WLAN firmware can wake up the application processor if it needs to communicate shown in 2.3.3. I would like to wake up from another device such as laptops, how can I wake up WLAN. Do I need to send specific message via WLAN?
Show LessHi,
we want to get the OTA2 functionality being integrated in our product. We are using 43438 module and an external MCU as host processor connected via SDIO. We also using an external SFLASH of 8MB connected via SPI. I read the OTA2 documentation and tried to apply all nescessary steps to our project setup.
Even though I do not fully understand how all the different pieces are pulled together to have everything at the right place in internal and external FLASH.
I am talking about the OTA2 bootloader, the factory reset OTA2 image, the fail-save app, the DCT, filesystem and the app itself. From the doc I read that there is a special memory map that has to be defined for this combination of internal and external FLASH. (ota2_image_defines.mk plus ota2_memory_with_bootloader.ld).
Even though I am a bit confused what part has to go at what location. I assume the following:
- internal FLASH of MCU holds:
* ota2_bootloader
* current app
- external SFLASH holds:
* factory reset OTA2 image
* fail-safe application
* app lookup table
* DCT1/2
* OTA2 extractor app
* filesystem
+ space reserved for saved DCT and extracted OTA image
Can someone confirm that this is correct and may have an example configuration how this has to configured?
Also when building, I am not sure what target to build to load all components correctly to start my system. Do I have to build/download the components separately?
If I am using one of the target configurations that have OTA2_SUPPORT enabled I get the following error:
"Illegal division by zero at ./tools/text_to_c/sector_count.pl line 50"
I assume that is cause by APP0 not being defined in the make environment, but I see no hint in the OTA2 doc that this has to be done somewhere explicitly.
If someone can provide some more details on how to setup OTA2 for our device combination that would be very helpful.
Thanks Andreas
Show Less