Dears.

We are using GX3 to implement “ethernet to usb new module”.

This module is HW-implemented in USB 2.0 Only (Vbus, D+, D-) and When this module is hooked up to the computer,

PC device driver “Cypress GX3 Superspeedto Gigabit Ethernet BridgeController” is brought it up successfully in Network Adapter, device manager as the following. Then, when I tried to run “GX3 EEPROM configuration Utility” and press the "program" button to write configuration paramters like Mac address anD so on to the EEPROM, it pops up the error like “Open Device Fail”.

Could you tell me what happened inside of it ? Please give us any tips to get through it.

Thanks,

WonjinHan.

Dear Infineon team,

We are going to get the SIG certification using the 89820.

But current SIG certification needs to use the TCRL 2019-2.

We've got almost part of the evidence for the Stack QDID. But certification company request the evidence of below item.

We've referenced the QDID #115853.

Could you let me know how to get the evidence of this item?

Regards,

Wayne

Hello.

I'm using CYW943907AEVAL1F.

I load "snip/sd_filesystem" code.

I put on uSD receptacle this model of uSD Scheda MicroSD PRO Endurance - 2018 (128GB) | Samsung IT

This uSD is a 128GB, interface UHS-I, Class 10.

Line 375 of "sd_filesystem.c" calls "wiced_filesystem_mount .. WICED_FILESYSTEM_HANDLE_FILEX" fails.

I dont' understand, in datasheet "002-14829 Rev. *K" page 18 I read UHS-I modes are supported.

Hello,

I am trying to test the bluetooth functionality of the CYW54591 chipset on the NVIDIA Jetson Nano (running Linux 4.9).  The PCIE (WiFi) interface is working as expected but I am not able to 'attach' to the UART interface of the m.2 module that I am testing.  I've tried different hciattach commands, such as:

hciattach /dev/ttyTHS2 any 921600 noflow

but I am not able to find one that successfully finishes initialization.  Is there an 'hciattach' command that should work for the CYW54591?

I don't see any drivers specifically for the bluetooth in the driver package that I downloaded for WiFi:

https://community.cypress.com/t5/Resource-Library/Cypress-Linux-WiFi-Driver-Release-FMAC-2020-09-25/ta-p/251089

is there another package that contains the bluetooth drivers for the chip?

Thanks for your help

From what I'm able to understand the "Bootloader application validation" option checks an 8bit checksum. This is not enough for my application since I need a proper CRC. The problem is that with an error in the flash there is a 1/256 chance of not detecting the error.

Is there a way to change this to a CRC16?

If there isn't a built-in option is there an example or application note explaining how to do this?

Basically, I would need to insert a CRC into the metadata as a linker step and then replace the "checksum check" in the bootloader with a CRC.

Hi,

I'm using Wiced 6.6.

The structure type 'wiced_ip_address_t' is defined in 'wiced_tcip.h', but this file include 'wiced_network.h', in which,  'wiced_ip_address_t' is defined again. 😅 This will trigger the type redifination under C99.

So, if you include 'wiced_network.h', and forward delclare 'wiced_ip_address_t' in it, why 'typedef' it again in 'wiced_tcpip.h‘????

Hi,

where can I find the most recent version of wl_tool ?

I have downloaded the one from this post but it seems to not integrate all the commands (phy_watchdog is missing for example).

Where can I download a more recent version?

Thanks,

I have a bootloader where I set the bootloader version parameter to 0xabcd. I enter the bootloader using the bootloader command and then I check the meta data using the get metadata command, I get the right bootloader version 0xabcd. I then flash the chip with a new bootloadable using the bootloader and I reset the chip. After the chip resets, it enter the bootloader and doesn't exit until I send it a command. However when I send it enter bootloader using the bootloader command and then I check the meta data using the get metadata command, I get the wrong bootloader version. Is this expected behavior or am I missing something?

I've been experimenting with the PSOC 6 BLE Pioneer kit to come up to speed on Cypress parts and the PSOC Creator IDE. I read that the chip has a floating point unit, and I was searching through the options in the IDE to see how to enable floating point operations in hardware (but didn't find anything). I searched the forum and came across a post from a few years ago that outlined a manual process for setting the compiler flags and linking the libraries, but it seemed somewhat involved and not user friendly. I wanted to know if this issue has been addressed in the latest version of PSOC creator 4.4, and if so, how do I access it? If it hasn't been addressed, I would assume that enabling the FPU is discouraged for some reason. Are there library compatibility issues I should be aware of? In a worst-case scenario, are there intrinsic functions available to access the FPU instructions?