Wifi(Wcnss) Memeory Setup error on Dragonboard 410C


#1

Hi,
I am compiling source of linux for 410C and having following issue on my console log so that my wcnss probe failed and due to that wifi on dragonboard 410c is not working.

can someone help me in this.

[ 1.873916] wcnss: IRIS Reg: 0x51120004
[ 1.910774] subsys-pil-tz a21b000.qcom,pronto: wcnss: loading from 0x00000000bbd00000 to 0x00000000bc2ff000
[ 1.916758] qcom_scm_call failed: func id 0x2000202, arginfo: 0x3, args: 0x6, 0xbbd00000, 0x5ff000, 0x0, ret: -2, syscall returns: 0xfffffff0, 0x0,0
[ 1.923745] subsys-pil-tz a21b000.qcom,pronto: wcnss: Memory setup error
[ 1.937266] /home/einfochips/Snapdragon_410C/kernel/drivers/soc/qcom/peripheral-loader.c: /home/einfochips/Snapdragon_410C/kernel/drivers/soc/qcom/
[ 1.980782] qcom_scm_call failed: func id 0x2000205, arginfo: 0x1, args: 0x6, 0x0, 0x0, 0x0, ret: -2, syscall returns: 0xffffffff, 0x0, 0x0
[ 1.986225] subsys-pil-tz a21b000.qcom,pronto: wcnss: Failed to bring out of reset
[ 1.998549] subsys-pil-tz a21b000.qcom,pronto: wcnss: Brought out of reset
[ 12.003555] timeout waiting for wcnss firmware ready indicator
[ 12.003703] wcn36xx-msm: probe of a000000.qcom,wcn36xx failed with error -11


#2

hi,

can you please provide more details about what you’ve done? How you compiled, which commit, which local changes, … and how you booted the kernel image that you built.

thanks


#3

hi,
I followed the steps as mentioned below.

git clone -n http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
cd kernel
git checkout -b kernel-15.06 ubuntu-qcom-dragonboard410c-15.06
export ARCH=arm64
export CROSS_COMPILE=<path to your GCC cross compiler>/aarch64-linux-gnu-
make defconfig
make -j4 Image dtbs

is also same as on mentioned in this link

thanks.


#4

hi ndec,
I did the above mentioned steps to compile the source of linux kernel.and i am compiling WCN36XX as module and load it using insmod but in that case my wifi module probe failed.

[ 1.910774] subsys-pil-tz a21b000.qcom,pronto: wcnss: loading from 0x00000000bbd00000 to 0x00000000bc2ff000
[ 1.916758] qcom_scm_call failed: func id 0x2000202, arginfo: 0x3, args: 0x6, 0xbbd00000, 0x5ff000, 0x0, ret: -2, syscall returns: 0xfffffff0, 0x0,0
[ 1.923745] subsys-pil-tz a21b000.qcom,pronto: wcnss: Memory setup error

while loading the firmware for wcnss module, it gives me Memory Setup error.
i don’t know why it’s giving me Memory setup error.

can you please help me in this.

thanks.


#5

hi,

i just realized there are 2 modules to load to get wlan to work:

insmod /<your module path>/wcn36xx-platform.ko
insmod /<your module path>/wcn36xx.ko

Could that be the problem?


#6

hi,

No, that is not the problem. I have inserted above both modules and test it also. but still it is giving same error.

I have also tested wlan with prebuilt boot image and see it’s kernel log as mentioned.

subsys-pil-tz a21b000.qcom,pronto: wcnss: loading from 0x000000008b600000 to 0x000000008bbe0000

and
my updated kenel log is mentioned below.
[ 1.882051] wcnss: IRIS Reg: 0x51120004
[ 1.923803] subsys-pil-tz a21b000.qcom,pronto: wcnss: loading from 0x000000008b600000 to 0x000000008bbff000
[ 1.968620] subsys-pil-tz a21b000.qcom,pronto: wcnss: Brought out of reset
[ 11.963548] timeout waiting for wcnss firmware ready indicator
[ 11.963719] wcn36xx-msm: probe of a000000.qcom,wcn36xx failed with error -11

I don’t know what’s problem is ??
can you help me in this .

thanks.


#7

Hi
I have the same problem.
I used the Debian SD Card image.
Did you have find the reason.
Could you help me.


#8

Sorry for commenting on an old thread - I am currently trying to get my wifi chip working and am having some success. However I only have the wcn36xx.ko file present in the lib/modules/version/kernel/drivers/net/wireless/ath/wcn36xx directory. How do I get the platform-tool.ko file to be there so that I can use the board’s wifi chip? Happy to make a new thread if thats the best way forward.


#9

since around ~June release, this module is no longer needed, nor available in our git tree. i think this discussion is going on another thread now, but just wanted to add this clarification here too.