Software Forum Discussions

Hi Team,

We are finding a way to backport Cypress 4373 wireless chip on hardware with USB interface on linux kernel 4.9, after compiling the drivers we get: compat.ko, cfg80211.ko, brcmutil.ko, brcmfmac.ko.

Then, we inserted all modules in sequence (compat.ko, cfg80211.ko,brcmutil.ko and brcmfmac.ko)and got the error "

brcmfmac: brcmf_fw_alloc_request: Unknown chip BCM57005/42"

Then we  checked the source code and found out that it jumped to the timeout error here:

if (!brcmf_usb_ioctl_resp_wait(devinfo)) {
usb_kill_urb(devinfo->ctl_urb);
ret = -ETIMEDOUT;
} else {
memcpy(buffer, tmpbuf, buflen);
}

Here is the dmesg log:

[    2.111084] usb 1-2.2.1: new high-speed USB device number 5 using tegra-xusb
[    2.131786] usb 1-2.2.1: New USB device found, idVendor=04b4, idProduct=bd29
[    2.131792] usb 1-2.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.131796] usb 1-2.2.1: Product: Remote Download Wireless Adapter
[    2.131799] usb 1-2.2.1: Manufacturer: Cypress Semiconductor Corp.
[    2.131802] usb 1-2.2.1: SerialNumber: 000000000001

...

[ 271.579551] compat: loading out-of-tree module taints kernel.
[ 271.588325] Loading modules backported from Linux version v5.15.58-2023_1128-0-g4dfc3616ef88
[ 271.588331] Backport generated by backports.git v5.15.58-1-0-g42a95ce7
[ 297.827391] brcmfmac: brcmf_usb_probe: Enter 0x04b4:0xbd29
[ 297.832904] brcmfmac: brcmf_usb_probe: devinfo->ifnum=0
[ 297.838151] brcmfmac: brcmf_usb_probe: Broadcom high speed USB WLAN interface detected
[ 297.846076] brcmfmac: brcmf_usb_probe_cb: Enter brcmf_usb_probe_cb
[ 297.852296] brcmfmac: brcmf_usb_dlneeded: Enter brcmf_usb_dlneeded
[ 297.858482] brcmfmac: brcmf_usb_dlneeded: 814: id.chip=0xdead
[ 299.892668] brcmfmac: brcmf_usb_dl_cmd: brcmf_usb_dl_cmd:797: ret=-110
[ 299.899643] brcmfmac: brcmf_usb_dlneeded: 816: id.chip=0xdead, id.chiprev=0xffffff80
[ 299.907596] brcmfmac: brcmf_usb_dlneeded: 819: chipid=0xdead, chiprev=0xffffff80
[ 299.915104] brcmfmac: brcmf_usb_dlneeded: chip 57005 rev 0xffffff80
[ 299.921710] brcmfmac: brcmf_usb_dlneeded: brcmf_usb_dlneeded: return true
[ 299.928821] brcmfmac: brcmf_usb_probe_cb: brcmf_usb_probe_cb: bus->chip=57005, bus->chiprev=-128
[ 299.937957] brcmfmac: brcmf_usb_prepare_fw_request: brcmf_usb_prepare_fw_request: devinfo->bus_pub.devid=57005, devinfo->bus_pub.chiprev=-128
[ 299.950973] brcmfmac: brcmf_fw_alloc_request: brcmf_fw_alloc_request: chip=57005, chiprev=-128
[ 299.960190] brcmfmac: brcmf_chip_name: brcmf_chip_name: id=57005, rev=-128
[ 299.967423] brcmfmac: brcmf_fw_alloc_request: Unknown chip BCM57005/42
[ 299.974578] brcmfmac: probe of 1-2.2.1:1.0 failed with error -12
[ 299.980862] usbcore: registered new interface driver brcmfmac​

Please help

Thank you

Best

Phong

Hello,

I see the build warning as below in the latest MTB 3.2 version. Is this an issue that can be fixed by Infineon or else it is upto the ARM?

-I../mtb_shared/wifi-host-driver/release-v3.1.0/WiFi_Host_Driver/src/include -I../mtb_shared/wpa3-external-supplicant/release-v1.1.0/include -I../mtb_shared/wpa3-external-supplicant/release-v1.1.0
../mtb_shared/mbedtls/mbedtls-2.25.0/library/ssl_tls.c: In function 'ssl_calc_finished_tls_sha384':
../mtb_shared/mbedtls/mbedtls-2.25.0/library/ssl_tls.c:3267:5: warning: 'mbedtls_sha512_finish_ret' accessing 64 bytes in a region of size 48 [-Wstringop-overflow=]
3267 | finish( &sha512, padbuf );
| ^~~~~~~~~~~~~~~~~~~~~~~~~

Regards,

Karthik

I would like to use Modustoolbox to develop rt thread project and was trying to follow the guide https://community.infineon.com/t5/Knowledge-Base-Articles/Porting-RT-Thread-to-ModusToolbox/ta-p/664401

While the guide is awesome demonstrating rt thread works, It does not have enough details of steps and setup for me.

I tried creating a capsense project, import rt thread into the project, removed all unnecessary srcs. But I got stuck with many weird libc & toolchain errors with the default gcc-arm compiler on Linux, like time_t is unknown typename and false/true/bool is undefined.

This first error is kinda "fixed" by explicitly telling eclipse to include the newlib header dir. The second is not. It is really weird and the IDE can successful locate those headers.

Could anyone help me out with this?

Hello,

I want to read the 1YN Bluetooth transmit power and write to it. How can I do this with the `hcitool`?

I'm using CYW4343A2_001.003.016.0031.0000.1YN.hcd  firmware.

As far as I know CYW43439 has a maximum TX power of 8dB. If so is the following output wrong?

# hcitool -i hci0 cmd 0x08 0x004b
      LE Read Transmit Power (0x08|0x004b) ncmd 1
        Status: Success (0x00)
        Min Tx power: -16 dBm
        Max Tx power: 12 dBm

Thanks for all the help,

Mesih

Still getting used to the newer ModusToolbox apps, as we had used PSoC Creator for years. I created a new project based on the MPN using the BSP Assistant app. This project uses the CapSense library to create a touchpad. Using the CapSense Configurator app, I successfully assigned each of the Rows/Columns to a specific GPIO. This assignment was reflected in the Device Configurator app. However, now I would like to add a few more rows/columns to my touchpad. I labelled these GPIO in the "Pins" tab of the Device Configurator. However, these new GPIO don't appear in either the Device Configurator under the Peripherals>System>CapSense>MSC 0 Parameters window, nor do they appear in the CapSense Configurator under Scan Configuration> Pin. It almost seems like I am missing a step of either importing the Device Config to the CapSense Configurator or vice versa. 

Here you can see I have configured the pin at Port 5, Pin 6 same way as the others and named it E45:

But when I then go to the Peripherals tab and try to assign Row 7 to it, it does not appear in the drop-down list:

If I check the CapSense Configurator, it also does not appear in the drop-down list:

None of the rest of the GPIO that I added show up either. What am I doing wrong? 

Hi all,

Would anyone know the purpose of the 't_offset' parameter in the following function please ?  It is not documented the v4.0.6 App help.

    ENCODER_POSIF_GetRotorAngle ( ENCODER_POSIF_t *const HandlePtr, uint32_t t_offset )

Thanks very much