Tool/software:
Hello,
I'm currently integrating the latest CC33XX-LINUX-MPU into our Yocto scarthgap build and am having a few problems.
The 1.0.0.4 release loads fine, and I can start the AP and STA modes fine. (Bluetooth doesn't work via either SDIO or UART, but that's for another thread.)
The 1.0.0.6 release crashes at boot, with the same device tree and Kconfig settings.
Is the cc33xx driver qualified for use with the Linux 6.6 LTS kernel and tested regularly with it? Release notes indicate that the driver is qualified for Kernel 6.1 only?
[ 12.826499] cc33xx_sdio mmc0:0001:2: Using SDIO in-band IRQ
[ 12.856198] Bluetooth: [bt sdio] BLE SDIO init module
[ 12.933236] Bluetooth: [bt sdio] PROBE vendor=0x97, device=0x4077, class=255, fn=1 0xffff6ffe4673c000
[ 12.946232] Bluetooth: [bt sdio hci] btti_hci_add_sdio_dev
[ 12.951943] Bluetooth: [bt sdio hci] Starting work thread...
[ 12.963383] Bluetooth: [bt sdio hci] work thread is started
[ 12.969151] Bluetooth: [bt sdio hci] work thread is sleeping...
[ 12.969200] Bluetooth: [bt sdio] TI cc33xx BLE-over-SDIO driver is up and running!
[ 13.449492] wlcore: cc33xx_probe :: Start
[ 13.456126] ------------[ cut here ]------------
[ 13.460764] WARNING: CPU: 1 PID: 298 at /net/mac80211/main.c:630 ieee80211_alloc_hw_nm+0x98/0x5e8
[ 13.469656] Modules linked in: fsl_jr_uio cc33xx(+) caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic btti_sdio btti cc33xx_sdio at24 caam secvio error imx_rpmsg_tty rpmsg_char g_ether fuse
[ 13.492740] CPU: 1 PID: 298 Comm: (udev-worker) Not tainted 6.6.23-lts-next-g24413fb66c42 #1
[ 13.505449] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 13.505454] pc : ieee80211_alloc_hw_nm+0x98/0x5e8
[ 13.528318] lr : wlcore_alloc_hw+0x30/0x478 [cc33xx]
[ 13.533327] sp : ffff8000839d37e0
[ 13.533330] x29: ffff8000839d37e0 x28: ffffa15b8c88c01c x27: 0000000000000000
[ 13.558632] x26: ffff8000839d3bb0 x25: ffff6ffe4f60c128 x24: 000000000000002d
[ 13.565770] x23: ffffa15bb4c60f38 x22: 0000000000008000 x21: ffffa15b8c87f000
[ 13.565777] x20: ffff6ffe4e423000 x19: 0000000000000000 x18: 0000000000000000
[ 13.590383] x17: 0000000000000000 x16: ffffa15bb3dd3324 x15: 0000ffffba2dee38
[ 13.622095] x14: 0000753304f844e8 x13: 000000000000025f x12: 0000000000000002
[ 13.629235] x11: 0000000000000000 x10: 0000000000000a60 x9 : ffff8000839d35f0
[ 13.636372] x8 : ffff6ffe46b1d480 x7 : ffff6ffe47275a00 x6 : 0000000000000000
[ 13.636379] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffffa15b8c8655f8
[ 13.636386] x2 : 0000000000000000
[ 13.675223] x1 : 0000000000000000 x0 : 0000000000001e58
[ 13.675230] Call trace:
[ 13.701383] ieee80211_alloc_hw_nm+0x98/0x5e8
[ 13.701398] wlcore_alloc_hw+0x30/0x478 [cc33xx]
[ 13.727475] cc33xx_probe+0xa4/0xe4 [cc33xx]
[ 13.746462] platform_probe+0x68/0xc8
[ 13.758036] really_probe+0x148/0x2b0
[ 13.761700] __driver_probe_device+0x78/0x12c
[ 13.766058] driver_probe_device+0xd8/0x15c
[ 13.770243] __driver_attach+0x90/0x19c
[ 13.770249] bus_for_each_dev+0x7c/0xdc
[ 13.786689] driver_attach+0x24/0x30
[ 13.790264] bus_add_driver+0xe8/0x1f8
[ 13.794013] driver_register+0x5c/0x124
[ 13.794019] __platform_driver_register+0x28/0x34
[ 13.810807] cc33xx_driver_init+0x24/0x1000 [cc33xx]
[ 13.815812] do_one_initcall+0x80/0x1c8
[ 13.819650] do_init_module+0x58/0x1e0
[ 13.846328] load_module+0x1d10/0x1d74
[ 13.850079] init_module_from_file+0x88/0xcc
[ 13.854351] __arm64_sys_finit_module+0x1dc/0x2e4
[ 13.859056] invoke_syscall+0x48/0x110
[ 13.881133] el0_svc_common.constprop.0+0xc0/0xe0
[ 13.885842] do_el0_svc+0x1c/0x28
[ 13.889159] el0_svc+0x40/0xe4
[ 13.892217] el0t_64_sync_handler+0x120/0x12c
[ 13.919505] el0t_64_sync+0x190/0x194
[ 13.923169] ---[ end trace 0000000000000000 ]---
[ 13.927913] wlcore: ERROR could not alloc ieee80211_hw
[ 13.933077] wlcore: ERROR can't allocate hw
[ 13.955584] cc33xx_driver: probe of cc33xx.1.auto failed with error -12
