AIROC™ Wi-Fi MCUs Forum Discussions
We are trying to build ota2_example on WICED 6.6 with CYW43907
First We lookde at WICED_OTA2.pdf in the install directory.
However, it does not exaplain the detail steps. So, we looke into
However, in the step 5. there are the following messages. after sending "get_update"
> get_update 192.168.11.161/udpate_image.bin
> 0024 02:48:05.645 PLAYER_EVENT_GET_UPDATE !
0025 02:48:05.649 ota2_test_get_update() wiced_ota2_service_init() bg_service:0x533a88 Download the OTA Image file - get it NOW!
Joining : Buffalo-A-D250
Successfully joined : Buffalo-A-D250
0026 02:48:10.688 wiced_ota2_service_get_the_update() wiced_ota2_service_wget_update(header) failed!
0027 02:48:10.699 wiced_ota2_service_get_the_update() ota2_service_connect() failed (list)!
0028 02:48:10.707 OTA2: wiced_ota2_service_get_the_update() FAILED check if timers started!
0029 02:48:11.010 wiced_ota2_service_get_the_update() wiced_ota2_service_wget_update(header) failed!
0030 02:48:11.021 wiced_ota2_service_get_the_update() ota2_service_connect() failed (list)!
0031 02:48:11.028 OTA2: wiced_ota2_service_get_the_update() FAILED check if timers started!
0032 02:48:11.036 PLAYER_EVENT_STOP_TIMED_UPDATE called ota2_test_stop_timed_update()! 0
0033 02:48:11.044 OTA2: wiced_ota2_service_deinit() Bad arg!
0034 02:48:11.050 PLAYER_EVENT_STOP_TIMED_UPDATE called ota2_test_stop_timed_update()! 5
0035 02:48:11.058 PLAYER_EVENT_STOP_TIMED_UPDATE Download failed! 5
Also, in the step 6, it passes 100% and does not stops
Regarding the step 7. DCT structure Update for OTA. Is this Bin file(OTA2 image file) included the DCT and updated at the same time?
If there is better explanation page or documents, please advice it
Show Less
dear
the TSSI can not execute ,how to fix it.
OS:windows 11
TSSI ver:3.14
error log
TSSI Calibration Ver3.14
Detected the equipment :
LitePoint,IQXEL,IQXL13311,1.27.0
Please input serial number:COM4
OPEN RS232 port : COM4
Traceback (most recent call last):
File "TSSI.py", line 2709, in <module>
IndexError: list index out of range
[14044] Failed to execute script TSSI
james
Show Less
Dear Infineon Team
I am using modustoolbox 3.0 for CYW954907AEVAL1F EVK.
I want to implement UDP server using ethernet in CYW954907AEVAL1F EVK.
Is there an example code implemented with CYW954907AEVAL1F EVK in Modustoolbox?
Thanks,
Jacob Choi
Hi,
I am using modustoolbox 3.0 for CYW43907 Soc based product. I would like to use Threadx RTOS for our project.
Does modustoolbox 3.0 support Threadx RTOS ? Becuase i am not finding Threadx RTOS option in Library Manager of
CYW43907 Soc. and similarly some of the peripheral also missing in HAL drivers for CYW43907 .
Please let me know how to add missing HAL drivers which are not present for CYW43907 in modustoolbox 3.0 and how to integrate Threadx RTOS for the same.
Documents and tutorials will be helpful.
Thanks,
Lokraj
__PRESENT
Show LessHi,
We are using 43909 WLAN Chip with HOST Variant BCM43907. We upgraded the Wiced firmware from 6.4 to 6.6 recently. After Wiced Upgradation we are facing an issue with Debug print not coming after WLAN is loaded.
Scenario:
1. Initially Debug print coming good.
2. Once WLAN Firmware is loaded. Debug print stop working or not coming on debug console.
Please suggest us how to figure out the issue.
__PRESENT
Show Less
The BGA package used for CYW43353 has some designated keepout areas for top layer copper. I was hoping there might be a DXF available of this detail so that i can transpose it for checks against my layout.
CYW43353LIUBG 145 ball WLBGA (4.87 mm × 5.413
mm, 0.4 mm pitch)
Dual-band 2.4 GHz and 5 GHz WLAN + BT 4.1 for
Automotive and Industrial Applications
Hi,
I am working on a CYW43907 custom board that is battery powered. Very rarely I experience an issue that the CYW43907 gets stuck and cannot be reset using the reset pin (REG_ON signal). The only way to recover from this state is to cut the power which means to physically disconnect the battery.
After doing sniff of the communication between the MCU and the SFLASH on the quad SPI bus I discovered that the MCU reads a few bytes from the SFLASH (at addresses 0x00, 0x0C, 0x00, 0x0C, 0x10, 0x18, 0x14 in this order) and then stops. After pulling the reset line it does the same again. The data that is read from the SFLASH is correct and the signal looks OK on an oscilloscope.
When the issue occurs I tried starting a debugging session in the WICED IDE. The MCU stays in the reset handler and does not execute any instructions. However, it is possible to read registers and memory which means that the JTAG interface is working.
My guess is that the MCU gets stuck in the ROM (first stage) bootloader which is supposed to load the application (second stage) bootloader from the SFLASH. Is there any reason for the ROM bootloader to stop before loading the firmware from the SFLASH? Is there anything else that can be tested or measured in order to find the cause of the problem?
Thanks, Krystof
Show LessHi,
Could someone tell me how to acquire "A peak saturated power output (in watts)" for AW-CU544?
Shoudl I look into CYW43439 datasheet?
I need to know "A peak saturated power output (in watts)" to evaluate the following equation.
[Psat>505.62 W*GHz2/fGHz^2]
The above equation is from the document below.
Commerce Control List Supplement No. 1 to Part 774 Category 3—page 12
https://www.bis.doc.gov/index.php/documents/regulations-docs/2334-ccl3-8/file
b.12.a. A peak saturated power output (in watts), Psat, greater than 505.62 divided by the maximum operating frequency (in GHz) squared [Psat>505.62 W*GHz2/fGHz^2] for any channel;
Show Less
Hi,
One of my customers has been very happy with WICED design based module ( CYW43438 + STM32F4xx ) but a time comes for seriously start considering a newer design.
Would it be possible to retain the current WICED APP+FW binary but replace CYW43438 with CYW43439?
Or should they move on to some newer designs like AW-CU544 ( P64 + CYW43439 ) and develop a new binary for it on MTB?
Show Less