# After several times of reboots, Legato EthLink ECM not available

**URL:** <https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943>\
**Category:** Legato Application Framework\
**Created:** [January 10, 2020, 10:48am UTC](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943 "2020-01-10T10:48:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AE\_1](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@AE\_1](https://forum.legato.io/u/AE_1)\
**Post date:** [January 10, 2020, 10:48am UTC](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943/1 "2020-01-10T10:48:40Z")

</div>

Hello all,

in our application, we reboot the modul (WP7607-1 Legato 19.02.0) if there is no network connection after a timeout. After several times of reboots, we see strange things.

1. sometimes we see Legato framework is NOT running
2. sometimes we see the Legato EthLink ECM not available on device manager. Only DM Port is availabe. It seems the modul goes into download-mode. Any idea to fix this point?

---

<div class="post-metadata">

**Author:** ![lotam](https://avatars.discourse-cdn.com/v4/letter/l/958977/32.png) [@lotam](https://forum.legato.io/u/lotam)\
**Post date:** [January 10, 2020, 1:04pm UTC](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943/2 "2020-01-10T13:04:09Z")

</div>

Hi AE\_1,  
The behavior you observed could be related to the boot loop detection feature of Legato.  
You can find similar log:

> [@Disable boot loop detection](https://forum.legato.io/t/disable-boot-loop-detection/3483/1):
>
> Hi, One of our demo units that uses the mangOH Red stopped working in the field. On inspecting the log, we found that the Legato framework didn’t start because of a ‘boot loop’. Jan 6 00:00:34 swi-mdm9x28 user.info Legato: INFO | \_UNKNOWN\_[644]/framework T=main | LE\_FILENAME GetStatus() 1034 | Status of system 'current' is 'good'. Jan 6 00:00:34 swi-mdm9x28 user.info Legato: INFO | \_UNKNOWN\_[644]/framework T=main | LE\_FILENAME FindNewestSystemIndex() 1287 | System 'current' is OK. Jan …

It is designed feature to avoid continues unexceptional reset/crash, if you want to stop this feature, please remove the bootCount file during system init.

> rm /legato/bootCount

Or you should enhance your reboot mechanism, I understand you want to retry and recover from situation of no network connection… but if it is network/coverage issue it may fall into boot loop without help…  
Personally, I would prefer radio on/off or restart app instead of system reboot.

Hope it helps.