Wi-Fi Combo Forum Discussions
Hello,
I'm currently working with a project updated with 6.1 version of WICED and I have an old problem of memory :
Module WICED 5.2 :
And now with version 6.1 I have this result :
To resolve problem of resource size I tried this method but wifi functions don't work : additional modules occupies lot of memory space after an upgrade
Can some one help me out to understand how to fix this problem ?
Show LessHello,
I used in version 5.0 of wiced bt_smartbridge function for my BLE application.
I read it's deprecated on WICED 6.x, can you tell me if there is something similar to demo/bt_smartbridge to devellop a new program ? (Scan and connect to BLE devices) ?
Thank you.
Show LessCan CYW43907 support 802.11R roaming?
Thanks
I figured out that the application is stored in internal flash in 43438 device. But during OTA update, the wiced_ota_server reads the chunk of data and calls sflash write related functions to copy it to flash. Now the question is where is the application written, in internal flash or in external flash?
1. The DCT_APP0_INDEX points to which location?
2. How does the processor decide on the location w=from which it has to fetch the application?
3. How is the application written to internal/external flash?
Partial answer to 3: The sflash write app is used to write application to external flash.
My question is whether the same APIs are used to access internal flash.
Your response will be highly appreciated!!!
Thanks.
Show LessHey I am working on Industrial temperature monitoring system in which I am using long distance wire communication by interfaing with raspberry Pi showing output on Pi Display, but instead of using long bulky wire I wanted to make it wireless. For making Wireless Communication I am using Adafruit WICED WiFi Feather to get connected with PI Display, I am searching for the best way how should I communicate wireless with raspberry Pi?
I have already tested monitoring system using Thermocouple connected with current loop recevier interface with Raspberry PI directly with distance wiring
Your suggestion on this will be very helpful
Show LessWe've observed a deadlock in sys_sem_new() using WICED SDK 3.3.1
The problem stems from an interaction between the heap semaphore used by malloc_lock()/mallock_unlock() to guard the heap structures against concurrent access, and the critical section used in sys_sem_new(), where the code in the critical section also tries allocating from the heap.
The sequence of events looks like this:
- some thread A, starts to perform a heap allocation
- as part of the allocation, it acquires the heap mutex
- before thread A releases the mutex, another thread S starts a call to
sys_sem_new()
. Thread S starts a critical section, stopping all interrupts and task switching. Thread A still owns the heap mutex, but makes no progress. - thread S then attempts to allocate heap for the new semaphore. It blocks waiting for the heap mutex to be available, but this is never available since it's acquired by thread A, which cannot make any progress until the critical section is exited.
- thread S only exits the critical section after it's acquired the semaphore owned by thread A
This is the typical cyclic graph of resource acquisition between threads that causes a deadlock.
A trivial fix is to call malloc_lock()/malloc_unlock() around the critical section in sys_sem_new(). This will ensure that the thread has the heap mutex before entering a critical section, so is guaranteed not to block in the critical section when allocating memory.
Show LessWe are using CYW43438, and I want to know what content should be burned to the OTP while manufacturing.
I searched google and only found the application note - OTP Programming and NVRAM Development in SDIO Mode
It describes how to create and burn a CIS structure to OTP by using command wl cisdump or dump by wl cisdump.
But when I dump the whole OTP using the command wl otpdump, I found that CIS structure was just a part of the whole OTP content, there are more content before and after it which was NOT described in the document above (see below which dumped from CYW43362).
Are there any more documents describe about it ?
Thanks.
Show Less
Hello All!
I have a http post request thread that pops from a queue and posts its contents to a server. I notice that my queue gets full pretty quickly and I start losing the packets to be sent, or have increased latency. Increasing my queue size will not help with the latency part as that depends on how quickly the send thread is able to process the message. Can I create multiple threads that make the HTTP post request? Is that a good idea or should I look at speeding up my existing thread?
Another question I had is how to disable forever ble_observe. Using 0 as an argument to the function puts it into forever scan mode, how can I stop it?
Show Less