This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Cannot get wl1271 module after making menuconfig on AM/DM37x EVM

Other Parts Discussed in Thread: WL1271

Hi,

I'm new to this forum. I'm trying to see the SDIO messages between the processor and the WL1271 module on AM/DM37x EVM platform. In the "wl1271_sdio_raw_write" function I was waiting to see "sdio write ... " logs when I open the debug level DEBUG_SDIO. But I could not see them, I see "WL1271: data" logs only.

I have noticed that when I have build the kernel there were no object file other than "wl12xx_platform_data", so I have changed the ".config" file after loading "tisdk_am37x-evm_defconfig" structure by using: "make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- menuconfig" and in order to active "wl12xx" in the driver, I have activated cfg80211 and mac80211 modules also.

Then I have compiled the code using "make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- uImage" and I have noticed that "wl12xx" files as long as cfg80211 and mac80211 files are also built.

I transferred the resultant file(uImage) to tftpboot directory and run the code from there. But I have ended up with errors:

cfg80211: disagrees about version of symbol wireless_send_event 

cfg80211: Unknown symbol wireless_send_event (err -22) 

 

And when I'm trying to activate my wlan interface, I cannot start it (Even the LEDs on the daughter card doesnot ON)with error:

root@am37x-evm:~# ifconfig wlan0 up

ifconfig: SIOCSIFFLAGS: Cannot assign requested address                        

 

I would appreciate anyhelp.

Best regards.

 

 

  • I don't know anything about the wireless net subsystem. I can comment about the error. I think that happens when two modules are not compatible. The version of cfg80211 module that you built is not compatible with the version of wext-core module. The wext-core module has the wireless_send_event() function. Probably because a loadable module version wext-core.ko exists in the /lib/modules directory on the target filesystem. That version probably was built from earlier code or in a different version of Linux. It sounds like you are using built-in modules rather than loadable modules, ie uImage only. Loadables modules would require to repopulate the /lib/modules directory. Maybe try setting "cfg80211 wireless extensions compatibility" to 'y' in the menuconfig. Or set it to 'n' to avoid pulling in wext-core entirely.