thanks Scott and jyijyi for the responses.
Yes, the Mirage Wl18xx card uses 1.8v for SDIO lines.
In our custom board, we had connected the MDM SDIO lines, which is 2.85 v directly to the Mirage SDIO lines. This broke the mirage module.
Was able to get the MDM SDIO lines to 1.8v after changing in the DTSI file.
In the MangoH red board, there is a level translator before connecting SDIO to the Mirage.
So currently in our custom board, we have added a level translator.
Thanks for the responses.
Could you please indicate how you modify the DTSI file so that other people can be benefited from this?
Thanks!
qcom,init-voltage = <2850000>;
qcom,init-voltage = <1800000>;
status = "okay";
};
};
&sdhc_2 {
vdd-supply = <&sdcard_ext_vreg>;
qcom,vdd-voltage-level = <2850000 2850000>;
qcom,vdd-voltage-level = <1800000 1800000>;
qcom,vdd-current-level = <15000 400000>;
vdd-io-supply = <&mdm9607_l13>;
qcom,vdd-io-voltage-level = <1800000 2850000>;
qcom,vdd-io-voltage-level = <1800000 1800000>;
qcom,vdd-io-current-level = <200 50000>;
#address-cells = <0>;I’m sorry, but I having a problem finding the files that you referenced that you changed. In my setup i’m using MangOH red and WP7611. I’m wondering if I need to change the voltage level also.
Looking at logread after executing ‘wifi client start’ I get the following:
swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | WIFI_START
Jan 5 19:28:54 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | mangOH red board
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360308] cfg80211: Calling CRDA to update world regulatory domain
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360590] cfg80211: World regulatory domain updated:
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360609] cfg80211: DFS Master region: unset
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360622] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360641] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360658] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360673] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360688] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360704] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360720] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360735] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jan 5 19:28:54 swi-mdm9x28-wp user.info kernel: [ 4622.360751] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Jan 5 19:28:55 swi-mdm9x28-wp user.warn kernel: [ 4623.368676] sdhci_msm 7864900.sdhci: card claims to support voltages below defined range
Jan 5 19:28:55 swi-mdm9x28-wp user.warn kernel: [ 4623.425735] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
Jan 5 19:28:55 swi-mdm9x28-wp user.info kernel: [ 4623.428275] mmc0: new high speed SDIO card at address 0001
Jan 5 19:28:56 swi-mdm9x28-wp user.err kernel: [ 4624.195551] wlcore: ERROR couldn't get hw info
Jan 6 01:28:56 swi-mdm9x28-wp daemon.info : process '/usr/sbin/run_getty.sh' (pid 12342) exited. Scheduling for restart.
Jan 6 01:28:56 swi-mdm9x28-wp daemon.info : starting pid 19903, tty '': '/usr/sbin/run_getty.sh'
Jan 5 19:28:56 swi-mdm9x28-wp user.notice root: run_getty.sh: ttyHSL0 reserved for CONSOLE
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | Failed to start TI wifi, interface does not exist.
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | Hardware is absent, perform clean up
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | mangOH red board
Jan 5 19:28:59 swi-mdm9x28-wp user.warn Legato: -WRN- | wifiService[1930]/daemon T=main | pa_wifi_client.c pa_wifiClient_Start() 519 | WiFi card is not inserted
Jan 5 19:28:59 swi-mdm9x28-wp user.warn Legato: -WRN- | wifiService[1930]/daemon T=main | le_wifiClient.c le_wifiClient_Start() 821 | Unable to start WIFI client; return code: -1
Jan 5 19:28:59 swi-mdm9x28-wp user.debug kernel: [ 4628.042843] gpio_map_name_to_num: find GPIO 76
Jan 5 19:28:59 swi-mdm9x28-wp user.debug kernel: [ 4628.043646] gpio_map_name_to_num: find GPIO 38
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1045]/supervisor T=main | proc.c proc_SigChildHandler() 2079 | Process 'wifi@0' (PID: 19842) has exited with exit code 1.
Jan 5 19:28:59 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[1930]/framework T=main | le_wifiClient_server.c CleanupClientData() 163 | Client 0x7f56c2c8 is closed !!!
Jan 5 19:28:59 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[1930]/framework T=main | le_wifiClient_server.c CleanupClientData() 185 | Found session ref 0x7f56c3e8; does not match
Jan 5 19:28:59 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[1930]/framework T=main | le_wifiAp_server.c CleanupClientData() 163 | Client 0x7f56c238 is closed !!!
Jan 5 19:29:00 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[1045]/supervisor T=main | app.c app_SigChildHandler() 4067 | Process 'wifi@0' in app 'wifi' faulted: Ignored.
Jan 5 19:29:00 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1045]/supervisor T=main | app.c app_StopComplete() 4764 | app 'wifi' has stopped.
Jan 5 19:29:00 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1045]/supervisor T=main | apps.c DeactivateAppContainer() 374 | Application 'wifi' has stopped.You can test with FW R13 first
Hi, I can try this, but is there any special settings needed for the UARTs to make the Talon Wifi card work?
Currently, I finally succeeded in rebuilding the yocto image as above but I have the same results. When I type ‘wifi client start’, all the lights on the wifi card come on, but then shut off after about 5 seconds and I get the error statement in my post from November 24.
Are these lines below from the console log the rootcause of my issue?
Jan 5 19:28:55 swi-mdm9x28-wp user.warn kernel: [ 4623.368676] sdhci_msm 7864900.sdhci: card claims to support voltages below defined range
Jan 5 19:28:55 swi-mdm9x28-wp user.warn kernel: [ 4623.425735] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
Jan 5 19:28:55 swi-mdm9x28-wp user.info kernel: [ 4623.428275] mmc0: new high speed SDIO card at address 0001
Jan 5 19:28:56 swi-mdm9x28-wp user.err kernel: [ 4624.195551] wlcore: ERROR couldn’t get hw info
Jan 6 01:28:56 swi-mdm9x28-wp daemon.info : process ‘/usr/sbin/run_getty.sh’ (pid 12342) exited. Scheduling for restart.
Jan 6 01:28:56 swi-mdm9x28-wp daemon.info : starting pid 19903, tty ‘’: ‘/usr/sbin/run_getty.sh’
Jan 5 19:28:56 swi-mdm9x28-wp user.notice root: run_getty.sh: ttyHSL0 reserved for CONSOLE
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | Failed to start TI wifi, interface does not exist.
Jan 5 19:28:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[1930] | Hardware is absent, perform clean up
It seems that my mangoh board doesn’t think the wifi card is plugged in.
How is it in FW R13???
For our requirement on custom board, building yocto image and flashing was required as we had missed having 1.8v Level translator between mdm and TI module.
Else the base FW and yocto image was working on the MangoH red board.
My suggestion would be, first check for the GPIO lines.
With the above logs, the sdio high speed device is detected, but wlcore is unable to get hw info. Please also probe the SDIO lines and check for voltage levels and if data flow is happening.
Hi,
I would test this on R13, but I don’t see a firmware build provided on source sierra website for the WP7611 chip that I’m using.
i wonder if you can still download the generic FW to it.
So I got another wifi card from a team-mate at my company and it seems that after install and same firmware flash, everything is working fine. So maybe I received a bad wifi IOT card.