# WP7607-1 - Failed to start TI wifi

**URL:** <https://forum.legato.io/t/wp7607-1-failed-to-start-ti-wifi/4096>\
**Category:** Legato Application Framework\
**Created:** [February 8, 2019, 10:48am UTC](https://forum.legato.io/t/wp7607-1-failed-to-start-ti-wifi/4096 "2019-02-08T10:48:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ben.o](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@ben.o](https://forum.legato.io/u/ben.o)\
**Post date:** [February 8, 2019, 10:48am UTC](https://forum.legato.io/t/wp7607-1-failed-to-start-ti-wifi/4096/1 "2019-02-08T10:48:34Z")

</div>

Hello,

I’m using a WP7607-1 on a mangOH green board.

The firmware and legato version are from [WP76xx Firmware Release 10.1.1](https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-latest-release-components/).

I have a [WL1835MOD board](http://www.ti.com/tool/WL1835MODCOM8B) wired to the IOT0 interface of the mangOH board.

My issue is that sometimes (~5% of the time) after a reboot I cannot use my [WL1835MOD board](http://www.ti.com/tool/WL1835MODCOM8B). The rest of the time it works properly and I can use it to set my WiFi Access point.

```
root@swi-mdm9x28-wp:~# ifup -v wlan0
/etc/init.d/tiwifi start
Failed to start TI wifi

```

The problem is that I don’t really know what is happening from this error and the only workaround I know is to reboot, which is not ideal.

Does somebody know what could lead `/etc/init.d/tiwifi` script to fail?

Thanks for your help,  
Best regards,  
Ben

---

<div class="post-metadata">

**Author:** ![ben.o](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@ben.o](https://forum.legato.io/u/ben.o)\
**Post date:** [February 8, 2019, 11:43am UTC](https://forum.legato.io/t/wp7607-1-failed-to-start-ti-wifi/4096/2 "2019-02-08T11:43:56Z")

</div>

I think I might have been able to identify the issue. The problem looks like sometimes the wifi modules will be started.  
The wifi starting script will think that everything is already configured but it wouldn’t be the case, just the modules would be there, the GPIOs won’t be configured. This would lead the `ifup` to fail.

When I’m in a failure state, if I check the wlcore related module started I see the following:

```
root@swi-mdm9x28-wp:/dev# lsmod | grep wlcore
wlcore_sdio 5544 0 - Live 0xbf0de000
wlcore 205233 1 wl18xx, Live 0xbf09c000
mac80211 290854 2 wl18xx,wlcore, Live 0xbf042000
cfg80211 264915 3 wl18xx,wlcore,mac80211, Live 0xbf000000

```

In this case, the `/etc/init.d/tiwifi start` command will see that wlcore modules are started because `lsmode | grep wlcore` will return 0 and won’t go through the GPIOs configuration.

I managed to recover by calling `/etc/init.d/tiwifi stop`, which would remove the modules, then go through my configuration again that will call `/etc/init.d/tiwifi start`.

I think as a workaround I’d call `/etc/init.d/tiwifi stop` at startup to set the system in a state the `start` expects it to be.

Why does the GPIO config get skipped if the modules are loaded?

Thanks,  
Best regards,  
Ben

---

<div class="post-metadata">

**Author:** ![plu](https://avatars.discourse-cdn.com/v4/letter/p/e19b73/32.png) [@plu](https://forum.legato.io/u/plu)\
**Post date:** [February 21, 2019, 12:26pm UTC](https://forum.legato.io/t/wp7607-1-failed-to-start-ti-wifi/4096/3 "2019-02-21T12:26:54Z")

</div>

Hi @ben.o,  
an investigation is opened internally, I’ll keep you inform on any progress  
best regards