AIROC™ Wi-Fi MCUs Forum Discussions

I don't see Code Examples in ModusToolbox to read and write to external Flash for the CYW943907-EVAL.  Have any of the WICED code examples been converted to MTB and available to customers?  Seem like the community posts for external memory is for WICED IDE.

Scott

Can someone provide high-level instructions on how to interface a PSoC (e.g. PSoC 63) with a WiFi module (e.g. CY43439)?

Is this WiFi-host-driver agnostic to the hardware interface like SPI or SDIO? 

https://github.com/Infineon/wifi-host-driver

I see an example code on the CY8CKIT-062-WiFi-BT that uses a PSoC 62 to implements a webserver using wifi. This kit uses the Murata module (LBEE5KL1DX-883). Its not clear whether it is using UDBs or something else. Also, not clear whether its using SDIO or SPI.  I'm somewhat confused. Can someone please explain.

Thank you.

What is the proper way to add multiplexing capability for pins on CYW43907 radio module using ModusToolbox?

I believe I need to add a line in the file: mtb_shared/mtb-hal-cat4/release-v0.5.0/COMPONENT_CAT4/source/cyhal_pin_package.c that connects GPIO_23 to PIN_PWM_5 per table 13 in the CYW43907 datasheet Rev L. However, I don’t understand the format to add that line of code.

There’s currently only one line for PIN_PWM_5 in cyhal_pin_package.c at line 231 of  {5, 0, PIN_PWM_5, PIN_MUX_SEL_1},

I want to add another line that allows a connection from GPIO_23 to PIN_PWM_5 via PIN_MUX_SEL_3.

What do the first two values in the line of code represent?

Here’s what I know of the format :  {<some number_A>, <some_number_B>, <pin_name>, <mux input column from Table 13 of CYW43907 datasheet>},

Greg

Hi,

Using the console app running on the CYW954907AEVAL1F evaluation kit, I'm trying to configure an AP on channel 38 (5Ghz band) with a 40Mhz bandwidth using the following command :

start_ap WW101WPA open DUMMY_KEY 38 40 no_wps 192.168.2.1 255.255.255.0

Everything seems to be correcty setup :

> status
WICED Version  : Wiced_006.006.001.0001
Platform       : CYW954907AEVAL1F
Driver & FW    : 7.15.168.149 (21d266a) FWID 01-d4dbc762
CLM            : API: 12.2 Data: 9.10.74 Compiler: 1.31.3 ClmImport: 1.36.3 Creation: 2020-07-20 00:01:06
MAC Address    : D4:53:83:C2:3E:78

STA Interface  : Down
AP Interface
   MAC Address : D6:53:83:C2:3E:78
   chanspec    : 0xd826
   SSID        : WW101WPA
   Channel     : 38
   Bandwidth   : 40
   IP Addr     : 192.168.2.1
   Gateway     : 0.0.0.0
   Netmask     : 255.255.255.0
P2P Interface  : Down
Ethernet Interface  : Down
>

 But using a laptop with wifi 802.11ac/n, I see the AP is on channel 36 !

Any idea ? I've tried following commands without any success too :

stop_ap
set_preferred_association_band 1
wifi_powersave 0
wl down
sleep 100
wl nmode 1
wl mimo_bw_cap 1
sleep 100
wl up
sleep 100
start_ap WW101WPA open DUMMY_KEY 38 40 no_wps 192.168.2.1 255.255.255.0

For info :

> wl chan_info
Channel 1       B Band
Channel 2       B Band
Channel 3       B Band
Channel 4       B Band
Channel 5       B Band
Channel 6       B Band
Channel 7       B Band
Channel 8       B Band
Channel 9       B Band
Channel 10      B Band
Channel 11      B Band
Channel 36      A Band
Channel 40      A Band
Channel 44      A Band
Channel 48      A Band
Channel 52      A Band, RADAR Sensitive, Passive
Channel 56      A Band, RADAR Sensitive, Passive
Channel 60      A Band, RADAR Sensitive, Passive
Channel 64      A Band, RADAR Sensitive, Passive
Channel 100     A Band, RADAR Sensitive, Passive
Channel 104     A Band, RADAR Sensitive, Passive
Channel 108     A Band, RADAR Sensitive, Passive
Channel 112     A Band, RADAR Sensitive, Passive
Channel 116     A Band, RADAR Sensitive, Passive
Channel 120     A Band, RADAR Sensitive, Passive
Channel 124     A Band, RADAR Sensitive, Passive
Channel 128     A Band, RADAR Sensitive, Passive
Channel 132     A Band, RADAR Sensitive, Passive
Channel 136     A Band, RADAR Sensitive, Passive
Channel 140     A Band, RADAR Sensitive, Passive
Channel 144     A Band, RADAR Sensitive, Passive
Channel 149     A Band
Channel 153     A Band
Channel 157     A Band
Channel 161     A Band
Channel 165     A Band
>

Dear Community

Can you please provide the current recommendations for software tool development (WICED or ModusTool) for the following CYW54907 Murata modules?  The WICED software tool development is now NRFD (not recommended for new designs).  Thank you

Type 1PS (LBWA1UZ1PS-241) = CYW54907 WiFi Only

Type 1QP (LBEE5WQ1QX-277) = CYW54907 WiFi and CYW20707 BLE

Hi,

We uses Wiced SDK for Type 1LD development. Wiced doesn't supports LWM2M protocol. We are trying to port an open source LWM2M implementation like Wakaama/Anjay to Wiced SDK. But it seems like the mbedtls module available with Wiced have been tweaked at many places (compared to open source version). This creates a lot of issues in the UDP/TCP layer. We know that Wiced uses mbedtls to support many built in modules (like WiFi). Hence it is not possible to tweak or replace the Wiced mbedtls version. At this point, we think that it might not be possible to port an open source LWM2M implementation to Wiced SDK. It will be helpful if anybody could comment on our inferences

regards

SR

I am unable to get a HAL timer to interrupt on the CYW943907AEVAL1F evaluation kit. Here is my development configuration.


Operating System is Windows 10 Pro.
Eval Hardware CYW943907AEVAL1F Eval kit Has the Murata LBWA1UZ1GC Wifi module containing a Cypress CYW43907 processor.
IDE ModusToolbox V2.4.0.
Embedded RTOS FreeRTOS.
Embedded Application Based on ModusToolbox any cloud TCP_Server example.


I have three tasks running and want to be able to configure a HAL timer (type cyhal_timer_t ) to interrupt once every millisecond. I have added the code to my application that is shown in snippet 2 here: Hardware Abstraction Layer (HAL) (infineon.github.io)

I have tried various timer_cfg parameters and some times I can get it to initialize correctly and sometimes not. I have never been able to get it to actually call the isr_timer() function. I am able to get the LPTimer snippet 2 example to work: Hardware Abstraction Layer (HAL) (infineon.github.io)

The ModusToolbox Hello_World example uses the HAL timer and it is able to interrupt. The difference between it and my application is I am using FreeRTOS. What does it take to get the HAL timer to work when using FreeRTOS? 

We met problem on implement unqiue factory reset DCT

according "WICED-AN800-R-Factory-Programming.pdf" WICED-Studio6.6.1.1

copy factory_reset_dct.c; temp_control_dct.c .h; and mfg folder. detail see attachment

>make snip.apsta-CYW943907AEVAL1F download download_apps run It can success work.

make the unqiue DCT 001

>make snip.apsta-CYW943907AEVAL1F factory_reset_dct apps/snip/apsta/mfg/0001.txt

download it to DCT location 0x8000 .\tools\OpenOCD\Win32\openocd-all-brcm-libftdi.exe -s >.\tools\OpenOCD\scripts -f ./tools/OpenOCD/CYW9WCD1EVAL1.cfg -f ./tools/OpenOCD/BCM4390x.cfg -f apps/waf/sflash_write/sflash_write.tcl -c "sflash_write_file build/snip.apsta-CYW943907AEVAL1F/factory_reset/factory_reset_dct_0001.bin 0x00008000 CYW943907AEVAL1F-P103-SoC.43909 0 43909" -c shutdown >> build/openocd_log.txt 2>&1

Then reset the board. found the application can startup, but the DCT contect is incorrect. So where is my mistake? What is the correct step?

Thanks！

Max

I am trying out this cyw43907 example https://github.com/Infineon/mtb-example-cyw43907-tcp-client

Have a CYW43907AEEVAL1F board.
lsusb shows it as ..
Bus 020 Device 039: ID 0a5c:43fa Broadcom Corp. WICED Eval Board

I am trying to program the board and running into this error.

```
Programming target device...
Open On-Chip Debugger 0.11.0+dev-4.3.0.1746 (2021-09-16-15:53)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
adapter speed: 100 kHz
adapter srst delay: 10
jtag_ntrst_delay: 10
Error: no device found
Error: unable to open ftdi device with vid 04b4, pid f900, description '*', serial '*' at bus location '*'
** OpenOCD init failed **
shutdown command invoked
make[1]: *** [qprogram] Error 1
make: *** [secondstage_build] Error 2

```

I am wondering whether this error is because I have an old verion os CYW43907AEEVAL board?

Is there a process to Load Pre-Compiled Firmware code into a CYW43xxx based kit?

Is this as simple as a MAKE command that skips the compile?  "<code location> download run"

If the kit is pre-programmed to accept an OTA, the firmware can be loaded Over The Air without any special hardware .

If the kit is NOT programmed to accept an OTA is there a way to load a .hex file directly into the kit (Ideally without first purchasing a debug probe).

I understand how to program the kit using a debug probe.

I also understand how to program a kit using WICED during the compile process via a MAKE with download command.

I want to distribute pre-compiled code, to protect the IP to the extent someone can't reverse compile. Does Infineon offer a "Programmer" or "Batch File commands" that can program a WiFi kit through the kit's USB programming  and debug port by using a simple USB connection to a PC?

Greg