# Wifi wl18xx is not running **URL:** \ **Category:** Build your own\ **Created:** [May 2, 2018, 12:10pm UTC](https://mangoh.discourse.group/t/wifi-wl18xx-is-not-running/1374 "2018-05-02T12:10:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Souhail](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Souhail](https://mangoh.discourse.group/u/Souhail)\ **Post date:** [May 2, 2018, 12:10pm UTC](https://mangoh.discourse.group/t/wifi-wl18xx-is-not-running/1374/1 "2018-05-02T12:10:26Z")
Hello, I am working on a project that uses the WP7607 module with the WL18xx ti chip. I defined GPIO\_40 and GPIO\_41 in order to activate and deaactivate the wifi and BLE. For the MSM\_WIFI\_IRQ\_GPIO I defined GPIO\_38 (SWIMCU\_GPIO\_TO\_SYS(2)) to manage the irq signal. Since I am not using the GPIOexpander neither an i2c hub, I tried to activate the wifi with the following script : #!/bin/sh export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin ti\_wifi\_start() { # Add mdev rule for crda grep crda /etc/mdev.conf \> /dev/null if [? -ne 0]; then echo "\$COUNTRY=.. root:root 0660 \*/sbin/crda" \>\> /etc/mdev.conf fi lsmod | grep wlcore \>/dev/null if [? -ne 0]; then # Set IOT0\_RESET = 1 (WP GPIO2) [-d /sys/class/gpio/gpio41] || echo 41 \>/sys/class/gpio/export echo out \>/sys/class/gpio/gpio41/direction echo 1 \>/sys/class/gpio/gpio41/value modprobe wlcore || exit 127 modprobe wlcore\_sdio || exit 127 modprobe wl18xx || exit 127 fi sleep 5 ifconfig -a | grep wlan0 \>/dev/null if [? -ne 0] ; then echo "Failed to start TI wifi"; exit 127 fi ifconfig wlan0 up \>/dev/null if [? -ne 0] ; then echo “Failed to start TI wifi”; exit 127 fi } ti\_wifi\_stop() { ifconfig | grep wlan0 \>/dev/null if [? -eq 0]; then ifconfig wlan0 down fi lsmod | grep wlcore \>/dev/null if [? -eq 0]; then rmmod wl18xx || exit 127 rmmod wlcore\_sdio || exit 127 rmmod wlcore || exit 127 ``` # Reset IOT0_GPIO4 = 0 (WP GPIO8) echo 0 >/sys/class/gpio/gpio41/value fi ``` } case “$1” in start) ti\_wifi\_start ;; stop) ti\_wifi\_stop ;; restart) ti\_wifi\_stop ti\_wifi\_start ;; \*) exit 1 ;; esac exit 0 However, after running this script, the modules: wl18xx, wlcore\_sdio, wlcore mac 80211 and cfg80211 were loaded however the wlan0 interface is not created. Hereaftre are the log when running the scripts : Jan 6 00:53:47 swi-mdm9x28 user.debug kernel: [3225.258026] gpio\_sync\_ri: RI owner is Modem Jan 6 00:53:47 swi-mdm9x28 user.debug kernel: [3225.258053] gpio\_map\_name\_to\_num: find GPIO 204 Jan 6 00:53:47 swi-mdm9x28 user.debug kernel: [3225.258063] export\_store: Export GPIO: 204 Jan 6 00:53:47 swi-mdm9x28 user.err kernel: [3225.258438] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:18) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090 Jan 6 00:53:47 swi-mdm9x28 user.debug kernel: [3225.279907] gpio\_sync\_ri: RI owner is Modem Jan 6 00:53:47 swi-mdm9x28 user.debug kernel: [3225.279928] gpiod\_export: sierra–find GPIO,chipdev = -833663984,chipngpio = 5,chipbase = 200 Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352165] cfg80211: Calling CRDA to update world regulatory domain Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352316] cfg80211: World regulatory domain updated: Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352329] cfg80211: DFS Master region: unset Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352339] cfg80211: (start\_freq - end\_freq @ bandwidth), (max\_antenna\_gain, max\_eirp), (dfs\_cac\_time) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352351] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352362] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352373] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352383] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352394] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352405] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352415] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Jan 6 00:53:47 swi-mdm9x28 user.info kernel: [3225.352426] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Jan 6 00:56:00 swi-mdm9x28 user.info Legato: INFO | modemDaemon[687]/modemDaemon T=main | le\_mrc.c SignalStrengthIndHandlerFunc() 654 | Signal Strength Ind Handler called with RAT.2 and ss.-105 Jan 6 00:58:39 swi-mdm9x28 user.info Legato: INFO | modemDaemon[687]/modemDaemon T=main | le\_mrc.c SignalStrengthIndHandlerFunc() 654 | Signal Strength Ind Handler called with RAT.2 and ss.-104 Comparing this log to that that I obtained from the mangoh board it is clear that it misses the next lines related the the mmc interface : Jan 6 00:39:06 swi-mdm9x28 user.warn kernel: [115.472161] sdhci\_msm 7864900.sdhci: card claims to support voltages below defined range Jan 6 00:39:06 swi-mdm9x28 user.warn kernel: [115.524852] mmc0: queuing unknown CIS tuple 0x91 (3 bytes) Jan 6 00:39:06 swi-mdm9x28 user.info kernel: [115.527371] mmc0: new high speed SDIO card at address 0001 Jan 6 00:39:07 swi-mdm9x28 user.info kernel: [116.075196] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) Jan 6 00:39:07 swi-mdm9x28 user.info kernel: [116.157324] wlcore: loaded Jan 6 00:39:12 swi-mdm9x28 user.info kernel: [120.994600] wlcore: PHY firmware version: Rev 8.2.0.0.212 Jan 6 00:39:12 swi-mdm9x28 user.info kernel: [121.056066] wlcore: firmware booted (Rev 8.9.0.0.17) Jan 6 00:39:12 swi-mdm9x28 user.info Can you help me with this issue please. Best regards, ---
**Author:** ![Souhail](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@Souhail](https://mangoh.discourse.group/u/Souhail)\ **Post date:** [May 7, 2018, 12:08pm UTC](https://mangoh.discourse.group/t/wifi-wl18xx-is-not-running/1374/2 "2018-05-07T12:08:51Z")
The previous behavior was in fact related to a hardware issue. Now, it works very well.