Wi-Fi Combo Forum Discussions
There hasn't been a WICED SDK update in more than a year. The version of MBEDTLS is quite old. I was wondering if there are any plans to update MBEDTLS on a future release? Thanks.
Show LessOn a factory fresh board with a Murata 1GC installed on it (CYW43907 chip) and a blank SPI EEPROM, is anything other than the WICED SDK and a JTAG interface needed to put all the software/firmware (incl. Murata WIFI fw) on the board and have it boot?
Put another way, if a factory fresh board is connected only via JTAG to the WICED SDK (via the appropriate dongle, such as on the EVAL board), is that enough to boot it and have it run regular software?
Thanks!
Show LessHi,
I am working on Murata 1LD board in Wiced_Studio. It has an on board external flash of 2MB. OTA update is implemented and the downloaded stripped.elf file is nearly 2MB. I came across 3 partitions in external flash DCT_APP0_INDEX, DCT_APP1_INDEX and DCT_APP2_INDEX
Can you tell me the size of each partition?
My new requirement is to download first OTA to DCT_APP0_INDEX. When next OTA happens it should be downloaded in DCT_APP1_INDEX and so on. Can you give me a clue on how to proceed?
Thanks,
Binsy M S
Folks,
How do you connect to a CYW4343W using a PIN please? There is vague mentions of PINs in both the source code and the sketchy documentation, but I can't fathom how you set the device up so that when the phone attempts to connect to the CYW4343W, the phone has to enter a PIN for the connection to succeed.
I have set up our device in the hello_sensor style and I can connect, read and write data etc, but now I need to set it up so the phone enters the PIN to communicate.
The PIN will be the same in every device (at least to start with) and we have no user interface whatsoever, hence the need for each device to have the same PIN.
I can't even see any example code to wade through.
I could do with some explicit instructions as to how this works. I'm assuming you have to set up somerthing when advertising.
Many thanks.
Show LessHello,
in order to obtain the CE marking for our product, which is based on CYW43907 SoC (module 1GC), we need to pass some RF tests to be compliant with the ETSI 301 893 V2.1.1 standard (we don't use the 2.4Ghz band).
As the module is already pre-certified (I have already got the reports from Murata), only a subset of the RF certification process has to be done.
Especially, the RF laboratory has listed these tests:
- RF output power (5.4.4)
- Transmitter unwanted emissions (5.4.5/5.4.6)
- Receiver spurious emissions (Radiated, 5.4.7)
To be able to perform these tests, a dedicated WLAN firmware is used, as well as a tests application, mfg_tests (+ wl43909B0.exe PC utility).
Some scripts to be used with the wl utility can be found on the WICED SDK directory, but the "WICED Development System Manufacturing Test User Guide" documentation is somewhat light.
So, could you provide the wl commands to use to be able to pass the required tests?
The RF lab asks to transmit at full power on each used channel, and with all supported modulations.
In case of output power being too high, I suppose that we can use the txpwr1 wl command to reduce the TX power output to pass the RF test, but how can we set the new value permanent on the final product with the operational WLAN firmware?
Also, to disable the 2.4Ghz band, we use the command wwd_wifi_change_band(1), is it enough?
Thank you.
Show LessI have the following question about filesystem.bin
-What data is included?
It would be helpful if you could tell me the target folders as well.
-How will it be used?
-If "RESOURCES_LOCATION ?= RESOURCES_IN_DIRECT_RESOURCES" is set, will the usage be the same?
Show LessHi.
I'm programming with an application that needs to store a little bit of data (~1KiB). I decided to play with DCT, but according to the documentation of:
> Ensure that this function is only called occasionally, otherwise the flash memory wear may result.
So I wonder the exact life of the so-called flash memory, and the rough definition of "occasionally". However I did not find any documentation or posts about this. As a result I come to the community. Thanks.
消息编辑者为:Chuigda Whitegive
Show LessThe actual Bluetooth problem we see is that the BT Connection fails after sometime. I remember this worked
fine with the WICED 6.2.1 now we have 6.4.0 or it can be something else.. The problem seems to be
this message: bt_rfcomm_server_conn_cback unhandled code=0x10
Where 0x10 stand for (defined in wiced_bt_rfcomm.h):
WICED_BT_RFCOMM_PEER_CONNECTION_FAILED, /**< Peer Connection Failed */
> BT stops communicating after receiving an Unhandled Management Event 0x21 which is defined as: BTM_LPM_STATE_LOW_POWER
The rest seems to work fine, but we need t overcome this issue.
Show Less
I'm trying to track down an issue where my units are being "bricked" during OTA update (ota, not ota 2.)
Running Wiced 3.7.0.7 on a custom board, with an ST32F205 micro and a USI BM13 SIP.
I can reproduce it with the Firefox browser, but not in Chrome. Have had some reports of Chrome having the same issue, but can't reproduce.
With Firefox, instead of it uploading 1024 byte chunks as expected, it uploads two smaller chunks to the same chunk index, like:
Writing chunk 34 of size 742 from offset 33792
Writing chunk 34 of size 282 from offset 34534
Writing chunk 35 of size 742 from offset 34816
Writing chunk 35 of size 282 from offset 35558
Writing chunk 36 of size 742 from offset 35840
Writing chunk 36 of size 282 from offset 36582
Writing chunk 37 of size 742 from offset 36864
Writing chunk 37 of size 282 from offset 37606
Writing chunk 38 of size 742 from offset 37888
Writing chunk 38 of size 282 from offset 38630
Writing chunk 39 of size 742 from offset 38912
Writing chunk 39 of size 282 from offset 39654
Writing chunk 40 of size 742 from offset 39936
Writing chunk 40 of size 282 from offset 40678
This results in the microcontroller firmware having corrupted memory, with a number of bytes showing as 0xFF starting from even addresses, spaced every 1024 bytes.
Chrome will show the chunk size as 1024 bytes and one write to each chunk index, and works fine in testing.
Has anyone experienced this before? Or have any ideas as to why Firefox and Chrome behave differently?
Show LessWe are using CYW43907 chip in STA Mode. we are using WICED studio version 6.4 with Free RTOS + LwIP.
Rarely Some times , we observe wiced_tcp_connect() returning the error code '17'. What does this error code means ?
Show Less