# Damaged MangOH?

**URL:** <https://mangoh.discourse.group/t/damaged-mangoh/4949>\
**Category:** mangOH Yellow\
**Created:** [July 30, 2020, 9:23pm UTC](https://mangoh.discourse.group/t/damaged-mangoh/4949 "2020-07-30T21:23:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![camilomesas](https://avatars.discourse-cdn.com/v4/letter/c/9de0a6/32.png) [@camilomesas](https://mangoh.discourse.group/u/camilomesas)\
**Post date:** [July 30, 2020, 9:23pm UTC](https://mangoh.discourse.group/t/damaged-mangoh/4949/1 "2020-07-30T21:23:15Z")

</div>

I have had some strange intermittent results from the MangOH for a while - like not being able to read the light sensor - but now after some manhandling, frequent reboots and reprogramming through octave, it seems to be in a bad state. I wouldn’t say bricked but it isn’t looking good.

When the MangOH is powered on it boots and reports the fact (POWER\_ON action in recent changes) but it never gets as far as running its edge action. In fact it seems like it reboots constantly…

Is there a way to factory reset the board so it can take its config from the cloud on a clean basis? I haven’t done anything risky to the board on the command line apart from “cm radio rat GSM”

Do I have any options other than to switch to another device?

Key errors from the console include:

[16.009263] i2c-msm-v2 78b8000.i2c: msm\_bus\_scale\_register\_client(mstr-id:86):0xc (ok)  
[16.051964] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x081343c8 OPER:0x00000090  
[16.066794] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x081343c8 OPER:0x00000090  
[…]  
[21.915569] usb 1-1: clear tt 2 (9031) error -71  
[21.927430] usb 1-1: clear tt 2 (9031) error -71  
[22.614953] usb 1-1.3: failed to read gpios  
Finished Legato start Sequence  
[…]  
[24.448002] adm\_callback: cmd = 0x10322 returned error = 0x16  
[24.452718] adm\_callback: ADM map error, resuming  
[24.457559] adm\_memory\_map\_regions: DSP returned error[ADSP\_ERR\_MAX]  
[24.468182] adm\_map\_cal\_data: map did not work! cal\_type 0 ret -68  
starting DNS forwarder and DHCP server: dnsmasq… 24.481334] map\_memory: map\_cal failed, cal type 10, ret = -19!  
[24.489592] adm\_alloc\_cal: cal\_utils\_alloc\_block failed, ret = -19, cal type = 10!  
[24.514577] call\_allocs: alloc failed!  
[…]  
starting DNS forwarder and DHCP server: dnsmasq… [25.052393] usb 1-1.3: failed to read gpios  
[25.076017] swimcu\_active\_time\_attr\_store: invalid input -1  
done.  
run\_getty.sh: ttyHSL1 reserved for CONSOLE

Poky (Yocto Project Reference Distro) 2.5.3 swi-mdm9x28-wp /dev/ttyHSL1

swi-mdm9x28-wp login: [26.272300] usb 1-1.3: failed to read gpios  
[27.056681] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv\_addr:0x55 MSTR\_STS:0x001363c8 OPER:0x00000010  
[27.071521] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv\_addr:0x55 MSTR\_STS:0x001363c8 OPER:0x00000010  
[27.094454] 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  
[27.109378] 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  
[27.142893] rtc-pcf85063 8-0051: hctosys: unable to read the hardware clock  
[27.492299] usb 1-1.3: failed to read gpios  
[28.712387] usb 1-1.3: failed to read gpios  
[29.932359] usb 1-1.3: failed to read gpios  
[31.158194] usb 1-1.3: failed to read gpios  
[31.248629] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[31.263845] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[31.945423] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[31.963070] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[32.400178] usb 1-1.3: failed to read gpios  
[32.496862] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[32.519766] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:14) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x001363c8 OPER:0x00000090  
[33.398566] Freezing of tasks aborted after 0.004 seconds  
[33.620627] Freezing of tasks aborted after 0.014 seconds  
[33.625052] usb 1-1.3: failed to read gpios  
[33.846496] Freezing of tasks aborted after 0.044 seconds  
[34.844346] usb 1-1.3: failed to read gpios

---

<div class="post-metadata">

**Author:** ![camilomesas](https://avatars.discourse-cdn.com/v4/letter/c/9de0a6/32.png) [@camilomesas](https://mangoh.discourse.group/u/camilomesas)\
**Post date:** [July 31, 2020, 4:19pm UTC](https://mangoh.discourse.group/t/damaged-mangoh/4949/2 "2020-07-31T16:19:09Z")

</div>

I managed to replace the firmware with the latest by downloading the file, scp to /tmp and installing manually. Now the mangoh doesn’t sync with Octave, and reboots sporadically. It is still running the edge action so it has retrieved that from somewhere even if it isn’t able to sync fully. But it seems very broken.

Is there any advice to test or recover it?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [July 31, 2020, 4:33pm UTC](https://mangoh.discourse.group/t/damaged-mangoh/4949/3 "2020-07-31T16:33:23Z")

</div>

Are you running it off a laptop? Are you set to GSM only mode?

---

<div class="post-metadata">

**Author:** ![camilomesas](https://avatars.discourse-cdn.com/v4/letter/c/9de0a6/32.png) [@camilomesas](https://mangoh.discourse.group/u/camilomesas)\
**Post date:** [July 31, 2020, 7:15pm UTC](https://mangoh.discourse.group/t/damaged-mangoh/4949/4 "2020-07-31T19:15:54Z")

</div>

Hi @asyal, it is running off a dedicated PSU and has a battery. It was set to rat GSM but I set it back to AUTO.

The console works on the second USB port, the board isn’t up for long so connecting over the network/usb is usually short lived.
