Software Forum Discussions
Browse the Community
ModusToolbox™
The ModusToolbox™ forum includes discussions regarding multi-platform development tools and a comprehensive suite of GitHub-hosted firmware libraries accompanied by thoroughly tested code example applications.
DAVE™
PSoC™ Creator & Designer
Discussion forum regarding PSoC Creator & Designer Software topics.
Wi-Fi Bluetooth for Linux
AURIX™ Development Studio
The AURIX™ Development Studio is a free of charge Integrated Development Environment (IDE) for the TriCore™-based AURIX™ microcontroller family. It is a comprehensive development environment, including Eclipse IDE, C-Compiler, Multi-core Debugger, Infineon low-level driver (iLLD), with no time and code-size limitations that enables editing, compiling, and debugging of application code. Combined with numerous code example projects, the IDE can be used to evaluate the powerful architecture of the AURIX™ microcontroller family. It supports Microsoft Windows 10 as a host operating system (OS).
Featured Discussions
When we are developing and debugging with a program, we often encounter situations where functions or variables are undefined.
But in our subsequent troubleshooting we found that the definitions and declarations were normal.
Then the occurrence of this error could be caused by a file naming problem.
If this is the case, check to see if the .h and .c in the code file are capitalized.
If you use uppercase .C or .H, please remove the file from the project, then change the file name format to lowercase in the file path folder and add it to the project again to compile it.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-Creator-Designer/PSoC-Creator-%E7%BC%96%E8%AF%91%E5%B7%A5%E7%A8%8B%E5%87%BA%E7%8E%B0%E6%9C%AA%E5%AE%9A%E4%B9%89%E7%9A%84%E6%8A%A5%E9%94%99/td-p/485788
Show LessHello,
We are using 1YN - CYW43439 with CYW4343A2_001.003.016.0031.0000.1YN.hcd firmware. We are experiencing the following error when we connect multiple Android devices.
[DEL] Device 75:52:F2:2E:99:A8 Galaxy M33 5G
[7F-40-50-E7-88-6C]# [ 4455.602130] Bluetooth: hci0: command 0x2006 tx timeout
[ 4457.682230] Bluetooth: hci0: command 0x200a tx timeout
[ 4459.762186] Bluetooth: hci0: command 0x2006 tx timeout
We tried the following but didn't help:
echo 0 > /sys/class/rfkill/rfkill0/state
echo 1 > /sys/class/rfkill/rfkill0/state
The problem is only solved when we reboot the system. Is there any other solution to this timeout problem such as reloading the device firmware? Can we force reload the firmware using `hcitool`?
Thanks for all the help!
Mesih
Show LessHello, ModusToolbox can't network to download information, using ModusToolbox_URL_Modifier_v1.7(IFX-TEST) didn't solve the problem, and following the PDF's procedure resulted in the following result.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/ModusToolbox/ModusToolbox-URL%E8%A7%A3%E5%86%B3modus%E8%81%94%E7%BD%91%E9%97%AE%E9%A2%98/td-p/487037
Show LessHi 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
Show LessI have a problem with backported FMAC driver when using SDIO interface.
When I try to restart the device, kernel crashes on wifi driver.
In backtrace there is description "use-after-free", see attached backtrace.
We are using v5.15.58-backports - 2023_1128 Release
1MW module (LBEE5HY1MW) with iMX6 cpu
Image is generated using Yocto with meta-freescale.
Kernel verion is 5.10.52
I think the problem is in this part of code
ifx-backports/v5.15.58-backports/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
Lines 5300 to 5303
if (bus->watchdog_tsk) {
send_sig(SIGTERM, bus->watchdog_tsk, 1);
kthread_stop(bus->watchdog_tsk);
bus->watchdog_tsk = NULL;
}
Why is the thread terminated twice?
I think that if the thread is terminated on a signal, then a subsequent call
kthread_stop(bus->watchdog_tsk);
can cause this issue.
Can someone please confirm this or explain why there is signal sending and also kthread_stop?
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
Show Lessv5.15.58-2023_0801
Release Date
2023-08-01
Description
This is Cypress's Linux brcmfmac driver and firmware support package.
Brcmfmac is an open-source driver project.
Files in this release:
* Backports package (cypress-backports-v5.15.58-2023_0801-module-src.tar.gz)
* Firmware/clm_blob files (cypress-firmware-v5.15.58-2023_0801.tar.gz)
* Cypress fmac patch files (cypress-patch-v5.15.58-2023_0801.tar.gz)
* Device tree files (cypress-devicetree-2023-08-01.tar.gz)
* hostapd/wpa_supplicant patch (cypress-hostap_2_10-2023_0801.tar.gz)
* Cypress customer patch (cypress-custom-patch-5.4.21.tar.gz)
* Cirrent Agent (cypress-cirrent-1.60.tar.gz)
* Documents (docs/)
* README
Checksum
sha256sum:
e41edde7c4c9db438b3cededfc204768f6751707ecc690fba686dd181dab0751 cypress-fmac-v5.15.58-2023_0801.zip
619923987ac95ef63721be3c6cfe1d2332b07a2a7aa65dbaf07f2a6b991d36cf cypress-backports-v5.15.58-2023_0801-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55 cypress-cirrent-1.60.tar.gz
d1d3fa91cf0767c26deec52dac64734e69faeefbb6306a6751052fb4f36439e8 cypress-custom-patch-5.4.21.tar.gz
8d852a022271dc7af6d08e8c0cf22db7fcfded592cdfcadc2f38b2ffdf2c4d33 cypress-devicetree-2023-08-01.tar.gz
cd4398905b4ffb43e4f4c051e5b2827c41d35edd509de6a80ec98e227941bf90 cypress-firmware-v5.15.58-2023_0801.tar.gz
9d687d1baabfcfba08b836271257d17ff0ea48d0af69f4a9250f78de21acdd45 cypress-hostap_2_10-2023_0801.tar.gz
2a5474d0c5eb6e0b619fc624f09f954ecf244d0ac215736926649bcd7819798e cypress-patch-v5.15.58-2023_0801.tar.gz
2023-08-04 Initial Post
I have installed ModusToolbox 3.2 and wanted to create my first application using the USB on a XMC4500.
But I did not get far as the USB (device or host) is not in the list of peripherials. Why does Infineon not support the USB?
Does anyone have a working USB example for the XMC4500? I have tried using the USB driver supplied in the ARM/Keil µVision pack, but that does not work correctly and after 6 months the Infineon support has given up and closed my support case.
Can anyone help?
Show LessHi guys,
It would be great if you could update PSoC Creator to be DPI-aware. It's actually really close already, so it shouldn't be too much work! Currently it's not declared as DPI-aware to Windows, so the whole thing appears blurry - not very professional! Forcing DPI-awareness, though, shows that most of your GUI sizing is already done with relative font sizes, so it's actually very close to a polished application. There are a couple of issues (e.g. icons seem to have hard-coded pixel sizes, listviews seem to have hard-coded pixel item heights) but I really don't think that fixing these up would take too much of your developers' time.
Laptops and tablets, particularly high-end ones (Microsoft's Surface Pro line and almost all of Apple's current models) are rapidly moving to high DPI displays, so this is only going to affect more and more users as time goes on.
Cheers
Jarrad
Show LessI 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?
Show Less