WICED Studio Wi-Fi Combo

I am looking for any documentation or tutorials on creating a stand alone project outside of the Wiced Studio folder that can be stored in a git repository.  The expectation is that there would be the typical  .cproject and .project files as well as custom makefiles and that the project folder could be imported into Wiced Studio and built. Thank you.

Hello.

I bought CYW943907AEVAL1F.

I have to connect I2C interface (I use I2C_0 : pins 23, 25 of J6)

with intelligent battery that uses SMBus.

I have to read Battery Voltage.

For read the Battery Voltage I have to write a specific "command_code" and the read two words.

The Battery I2C address is 0001 011 ,

the "command_code" for read Voltage is 0x09 in mV.

The datasheet of the intelligent Battery states that you can read Word in this way

I write this routine :

/* i2c battery */

wiced_i2c_device_t i2c_battery;

/* setup 'i2c_battery' params */

i2c_battery.port = WICED_I2C_1;
i2c_battery.speed_mode = I2C_STANDARD_SPEED_MODE;
i2c_battery.flags = I2C_DEVICE_USE_DMA;
i2c_battery.address = 0x16 >> 1; // 0001 011 Smart Battery Data Specification V1.1 December 1998
i2c_battery.address_width = I2C_ADDRESS_WIDTH_7BIT;

/* init 'i2c_battery' i2c */

status = wiced_i2c_init ( &i2c_battery );

if ( status != WICED_SUCCESS )
{
WPRINT_APP_INFO( ("wiced_i2c_init 'i2c_battery' failed, status = %d\n", status) );
return;
}

uint8_t command_code = 0x09;

/* write command_code */

wiced_result = wiced_i2c_write ( &i2c_battery, WICED_I2C_START_FLAG, (void*)&command_code, 1U );

if ( wiced_result != WICED_SUCCESS )
{
WPRINT_APP_INFO( ("[##] wiced_i2c_write failed, status = %d\n", (int)wiced_result) );
return wiced_result;
}

/* read word */

wiced_result = wiced_i2c_read ( &i2c_battery, WICED_I2C_REPEATED_START_FLAG, (void*)&word, 2U );

if ( wiced_result != WICED_SUCCESS )
{
WPRINT_APP_INFO( ("[##] wiced_i2c_read failed, status = %d\n", (int)wiced_result) );
return wiced_result;

}

The code does't work because wiced_i2c_write fails with result 4 (WICED_ERROR).

The signals that I observe with scope are ...

What I'm wrong ?

The battery responds ACK for the Write command_code ...

We are performing EMC testing on our product which uses the CYW43907 WiFi combo chip on a WM-AN-BM-23 module.

We are doing the testing with the wl_tool provided and have not had problems until now. We are using Wiced Studio 6.2.

Our testing house is reporting a failure with an error of -20 which seems to be BCME_BADCHAN.
However we have not found this error code in the documentation, could you tell us where to look.

.\wl --serial (comport) chanspec -c 3 -b 2 -w 40 -s 1

They tried changing the channel, they get the same result.
43909B0.exe
They can transmit fine in the 5 Ghz band, eg using:

.\wl43909B0.exe --serial (comport) chanspec -c 38 -b 5 -w 40 -s

Is it possible that your team could provide insight into whether 802.11n 40 Mhz is supported in the 2.4 Ghz band and if so could you provide a bat file or at least provide the commands to transmit.

I try to mirigrate from 6.4 to 6.6 and this not working.

The new project (6.6) wut the same code were compiled but stuck in spi init funciton.

What I need to know to this mirigrate?

Since the following error occurred when the program was started, the problem has been resolved by taking the action described in [1].

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

  ** ERROR: WLAN: could not download clm_blob file

  ** FATAL ERROR: system unusable, CLM blob file not found or corrupted.

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

[1]Details of support

   When the Wi-Fi FW was updated, an error occurred due to an inconsistency between the placement of memory sectors managed by the application and the placement of external Flash.

  "RESOURCES_LOCATION ? = RESOURCES_IN_WICEDFS", the external Flash could not be updated, which resulted in the inconsistency.

   Changed the setting to "RESOURCES_LOCATION ? = By changing the configuration to "RESOURCES_IN_DIRECT_RESOURCES", the error will not occur.

   Because the build error occurred when the above settings were changed, added the following settings so that the LUT can be written to the external Flash.

   -----

   /tools/makefiles/standard_platform_targets.mk

   #ifeq ($(RESOURCES_LOCATION),RESOURCES_IN_WICEDFS)

   download: $(STRIPPED_LINK_OUTPUT_FILE) display_map_summary download_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,download_dct) APPS_LUT_DOWNLOAD

   #else

   #download: $(STRIPPED_LINK_OUTPUT_FILE) display_map_summary download_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,download_dct)

   #endif

   -----

[2] Confirmation

   There is a confirmation of the behavior when the software with "RESOURCES_IN_DIRECT_RESOURCES" is updated against the module with "RESOURCES_IN_WICEDFS" set.

   It works with the current configuration, but I'm not sure how WICED affects it, so I'm asking.

1. If you set "RESOURCES_IN_DIRECT_RESOURCES", the filesystem will be included in the application and no inconsistency will occur?

2. Update "RESOURCES_IN_DIRECT_RESOURCES" software to "RESOURCES_IN_WICEDFS" module.

  If I update the software again in this state, is it correct that "FR_APP" will not be destroyed when updating to APP0 because the LUT of the external flash will not be changed?

Hi,

I am working with a CYW4343W and WICED Version: Wiced_006.004.000.0061

My Central application is behving as expected for most of the time, scanning for and connecting to a BLE Server, performing Service and Characteristic discovery, writing to the Server's CCCD, pairing and bonding etc. However, if I leave it to run for a few hours it will intermittently receive the BLE management callback event BTM_ENABLED_EVT with a value of WICED_TIMEOUT for p_event_data->enabled.status.

I have found that ignoring these WICED_TIMEOUT events ultimately results in one the of subsequent calles to a WICED BLE API function such as wiced_bt_gatt_send_discover() etc not returning, after which my application will hang awaiting the API call to return.

My short-term solution is to reset my device whenever the application receives BTM_ENABLED_EVT with a value of WICED_TIMEOUT. However, I would like to know what is the recommended procedure for handling such errors, please?

Also, what are the most likely causes of the BTM_ENABLED_EVT with a value of WICED_TIMEOUT, please?

Regards,

R

Hello,

Is there a way to accomplish the following using the existing library features?:

- Once a BLE peripheral is bonded to a central, it will not accept connections from any other device except the one we're bonded with. The bonded central can connect and disconnect as needed, but all other central devices would not be allowed to connect at any time.

- The bonded central device may support any of the valid BLE addressing schemes (private static/resolvable static etc. we can't control this part)

- I am implementing this on the  MurataType1LD module: (CYW43438) + STM32 (ARM Cortex-M4F) 

Hi everyone,

I encountered the same problem as written in

https://community.cypress.com/t5/WICED-Studio-Wi-Fi-Combo/how-to-add-ST-link-support-in-WICED/m-p/72316
I am trying to program an Inventek ISM4343-WMB-L54 module (mounted on a custom PCB) with ST-link/v2 programmer from Wiced 6.2. I downloaded the Wiced patch from the Inventek website, walked through the solution here:

https://broadcomwiced-v8.hosted.jivesoftware.com/community/software-forums/wiced-wifi/wiced-wifi-forums/blog/2018/10/10/adding-st-link-support-in-wiced
I also added these rows to my platform.mk file as suggested on the forums

HOST_OPENOCD := scripts/target/stm32f4x_stlink

JTAG        := scripts/interface/stlink-v2

and still geting the same OpenOCD errors as in the first link. 

(the ST-link/V2 is recognised as a libusbK device - driver updated with Zadig)

The last entry form openocd_log.txt is the following:

Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
./tools/OpenOCD/stm32f4x.cfg:1: Error: Can't find swj-dp.tcl
in procedure 'script'
at file "embedded:startup.tcl", line 60
at file "./tools/OpenOCD/stm32f4x.cfg", line 1
Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Error: An adapter speed is not selected in the init script. Insert a call to adapter_khz or jtag_rclk to proceed.

Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Error: An adapter speed is not selected in the init script. Insert a call to adapter_khz or jtag_rclk to proceed.

I am really stuck with this problem, your help would be much appreciated.

Best regards,

nmate1988

Hello,

we have to build up a test board for our customer which shall be equipped with a Murrata Type 1PS (Type 1PS | LBWA1UZ1PS | Murata Manufacturing Co., Ltd.) module. This module includes your Cypress CW54907 chipset.

For the project we just have to proof that the chip is working. So our goal is to get a connection to a known network and command a ping request.

Do you provide any standard pre-compiled application which we can use as a so called network controller offering the ability to issue commands by a serial interface e.g. UART? If yes, can you provide us any documents which give us an impression about the complexity of such an interface.

Best regards,
Mario

In the system_monitor_thread_main, the comment mentions the capability of monitoring for bus/token timeout but I do not see any implementation of  this. Is there a simple/easy method to implement this and can it be done with the CYW43907?

I have some rare lock up conditions around failures where the WLAN core or internal bus has stopped working/responding. This issue seems to be amplified when Aruba AP's issue deauth messages either during roaming or prior to an AP going offline/rebooting. One example, I have tracked down that a join command permanently blocked until power cycling.