WP7601 update fails - no redSensorToCloud

IoT Modules WP Series
1

I’m running a VirtualBox VM under Windows 10 Pro.

mangoh@mangoh-vm:~/mangOH$ uname -a
Linux mangoh-vm 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
mangoh@mangoh-vm:~/mangOH$

I’m targeting a MangOH Red with a WP7601-1. I can run make red_wp76xx, and update without problems,

mangoh@mangoh-vm:~/mangOH$ update ~/mangOH/build/update_files/red/mangOH.wp76xx.update 192.168.2.2
Applying update from file '/home/mangoh/mangOH/build/update_files/red/mangOH.wp76xx.update' to device at address '192.168.2.2'.
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Applying update: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
SUCCESS
Done
mangoh@mangoh-vm:~/mangOH$

but the test suggested in the documentation,

If redSensorToCloud is listed, the install worked.

fails, as redSensorToCloud is not listed.

mangoh@mangoh-vm:~/mangOH$ ssh root@192.168.2.2
root@swi-mdm9x28-wp:~# app status
[running] atAirVantage
[running] atQmiLinker
[running] atService
[running] audioService
[running] avcService
[running] cellNetService
[running] dataConnectionService
[running] fwupdateService
[running] gpioService
[running] modemService
[running] portService
[running] positioningService
[running] powerMgr
[running] qmiAirVantage
[running] secStore
[stopped] smsInboxService
[stopped] spiService
[stopped] tools
[stopped] voiceCallService
[stopped] wifi
[stopped] wifiApTest
[stopped] wifiClientTest
[running] wifiService
[stopped] wifiWebAp
root@swi-mdm9x28-wp:~#

I’ve tried installing the WP76xx_Release12_VERIZON firmware and WP76xx_Release12_GENERIC_GCF firmware, but get the same results with both.

The documentation offers no guidance in the event that the procedure fails, so I’m at a loss as to what else to do next.
Thanks,

-Nick

P.S.

cm info:
    root@swi-mdm9x28-wp:~# cm info
    Device:                        WP7601-1
    IMEI:                          351709090110645
    IMEISV:                        6
    FSN:                           WC748385480810
    Firmware Version:              SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
    Bootloader Version:            SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
    MCU Version:                   002.011
    PRI Part Number (PN):          9907596
    PRI Revision:                  001.003 
    Carrier PRI Name:              GENERIC
    Carrier PRI Revision:          002.056_000
    SKU:                           1103728
    Last Reset Cause:              Reset, User Requested
    Resets Count:                  Expected: 32	Unexpected: 2
    root@swi-mdm9x28-wp:~#
2

Please run “logread -f” on the WP7601-1 when installing mangOH.wp76xx.update to check if there are errors.

FYI, mangOH has it’s own dedicated forum, https://forum.mangoh.io/, where you’ll find a lot of useful information.

3

Thanks. Since I’m a new user, I can’t upload the results (~1,400 lines). Here’s a “grep -v INFO” on the output instead (66 lines):

Apr  2 20:02:05 swi-mdm9x28-wp authpriv.info dropbear[11500]: Child connection from 192.168.2.3:59223
Apr  2 20:02:05 swi-mdm9x28-wp authpriv.notice dropbear[11500]: Auth succeeded with blank password for 'root' from 192.168.2.3:59223
Apr  2 20:02:27 swi-mdm9x28-wp authpriv.info dropbear[11500]: Exit (root): Disconnect received
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | atAirVantage[927]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.debug Legato:  DBUG | atQmiLinker[936]/atQmiLinker T=main | atForward.c ReleaseQmiClient() 324 | Releasing qmi client 0x3
Apr  2 20:02:27 swi-mdm9x28-wp user.debug Legato:  DBUG | atQmiLinker[936]/atQmiLinker T=main | atForward.c ReleaseQmiClient() 333 | Successfully released qmi client 0x3
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | portDaemon[1021]/portDaemon T=main | le_port.c CloseSessionEventHandler() 1785 | SessionRef (0x7f57dce4) has been closed
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | atServerDaemon[946]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.emerg Legato: *EMR* | portDaemon[1021]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (portDaemon.portDaemon.le_atServer:2527056ddcf5218c3a18f8b922a25fd2).
Apr  2 20:02:27 swi-mdm9x28-wp user.emerg Legato: *EMR* | qmiAirVantage[1049]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (qmiAirVantage.qmiAirVantage.le_atServer:2527056ddcf5218c3a18f8b922a25fd2).
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | atClientDaemon[945]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | supervisor[901]/supervisor T=main | app.c app_SigChildHandler() 3981 | Process 'portDaemon' in app 'portService' faulted: Restarting process.
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | supervisor[901]/supervisor T=main | proc.c proc_Start() 1239 | Process 'portDaemon' cannot be started because framework is shutting down.
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | supervisor[901]/supervisor T=main | app.c app_SigChildHandler() 3987 | Could not restart process 'portDaemon' in app 'portService'.
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | supervisor[901]/supervisor T=main | app.c app_SigChildHandler() 3981 | Process 'qmiAirVantage' in app 'qmiAirVantage' faulted: Restarting process.
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | supervisor[901]/supervisor T=main | proc.c proc_Start() 1239 | Process 'qmiAirVantage' cannot be started because framework is shutting down.
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | supervisor[901]/supervisor T=main | app.c app_SigChildHandler() 3987 | Could not restart process 'qmiAirVantage' in app 'qmiAirVantage'.
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | audioDaemon[955]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | avcDaemon[965]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | modemDaemon[1011]/modemDaemon T=main | le_sms.c CloseSessionEventHandler() 2181 | SessionRef (0x7f61ad74) has been closed
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | posDaemon[1030]/posDaemon T=main | le_gnss.c CloseSessionEventHandler() 1079 | SessionRef (0x7f581364) has been closed
Apr  2 20:02:27 swi-mdm9x28-wp user.err Legato: =ERR= | posDaemon[1030]/posDaemon T=main | le_pos.c PosCloseSessionEventHandler() 1117 | SessionRef (0x7f5812d4) has been closed
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | cellNetService[974]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.crit Legato: *CRT* | dcsDaemon[983]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:27 swi-mdm9x28-wp user.debug Legato:  DBUG | wifiService[1068]/daemon T=main | le_wifiClient.c CloseSessionEventHandler() 478 | sessionRef 0x7f57ce84 GetFirstSessionRef (nil)
Apr  2 20:02:27 swi-mdm9x28-wp user.debug Legato:  DBUG | wifiService[1068]/framework T=main | le_wifiClient_server.c CleanupClientData() 148 | Client 0x7f57ce84 is closed !!!
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | fwupdateDaemon[992]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | gpioService[1002]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | rSimDaemon[1012]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | modemDaemon[1011]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | posDaemon[1030]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | powerManagerService[1039]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | secStore[1058]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.crit Legato: *CRT* | wifiService[1068]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:28 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[901]/supervisor T=main | frameworkDaemons.c ShutdownNextDaemon() 399 | Killing framework daemon 'watchdog'.
Apr  2 20:02:28 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[901]/supervisor T=main | frameworkDaemons.c ShutdownNextDaemon() 399 | Killing framework daemon 'updateDaemon'.
Apr  2 20:02:29 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[901]/supervisor T=main | frameworkDaemons.c ShutdownNextDaemon() 399 | Killing framework daemon 'configTree'.
Apr  2 20:02:29 swi-mdm9x28-wp user.crit Legato: *CRT* | configTree[914]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:29 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[901]/supervisor T=main | frameworkDaemons.c ShutdownNextDaemon() 399 | Killing framework daemon 'logCtrlDaemon'.
Apr  2 20:02:29 swi-mdm9x28-wp user.crit Legato: *CRT* | logCtrlDaemon[913]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:29 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[901]/supervisor T=main | frameworkDaemons.c ShutdownNextDaemon() 399 | Killing framework daemon 'serviceDirectory'.
Apr  2 20:02:29 swi-mdm9x28-wp user.crit Legato: *CRT* | serviceDirectory[912]/framework T=main | LE_FILENAME TermSignalHandler() 643 | Terminated
Apr  2 20:02:29 swi-mdm9x28-wp user.err Legato: =ERR= | _UNKNOWN_[839]/framework T=main | LE_FILENAME GetStatus() 1279 | Failed to read status of system '2' (No such file or directory).
Apr  2 20:02:29 swi-mdm9x28-wp user.notice root: update-ld-cache: Updating ld.so.cache using [/legato/systems/current/lib]...
Apr  2 20:02:29 swi-mdm9x28-wp user.notice root: update-ld-cache: Updating /etc/ld.so.cache ...
Apr  2 20:02:29 swi-mdm9x28-wp user.notice root: update-ld-cache: Removing stale mount [/etc/ld.so.cache]...
Apr  2 20:02:29 swi-mdm9x28-wp user.err Legato: =ERR= | _UNKNOWN_[839]/framework T=main | LE_FILENAME GetStatus() 1279 | Failed to read status of system 'current' (No such file or directory).
Apr  2 20:02:29 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[13052]/framework T=main | LE_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name 'framework.FsFileRefPool'. This will become illegal in future releases.
Apr  2 20:02:29 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[13052]/framework T=main | LE_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name 'framework.hashMap_refFsFileRefM'. This will become illegal in future releases.
Apr  2 20:02:30 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13065]/framework T=main | LE_FILENAME le_ref_CreateMap() 149 | Map name 'refconfigTreeWdog_ServerHandlers' truncated to 'refconfigTreeWdog_ServerHandler'.
Apr  2 20:02:30 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13066]/framework T=main | LE_FILENAME le_ref_CreateMap() 149 | Map name 'refupdateDaemonWdog_ServerHandlers' truncated to 'refupdateDaemonWdog_ServerHandl'.
Apr  2 20:02:30 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13066]/framework T=main | LE_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name '.le_cfg_ClientData'. This will become illegal in future releases.
Apr  2 20:02:30 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13066]/framework T=main | LE_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name '.le_cfg_ClientThreadData'. This will become illegal in future releases.
Apr  2 20:02:30 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13066]/framework T=main | LE_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name 'framework.hashMap_refle_cfg_Cli'. This will become illegal in future releases.
Apr  2 20:02:31 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13067]/framework T=main | LE_FILENAME le_ref_CreateMap() 149 | Map name 'refconfigTreeWdog_ClientHandlers' truncated to 'refconfigTreeWdog_ClientHandler'.
Apr  2 20:02:31 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[13067]/framework T=main | LE_FILENAME le_ref_CreateMap() 149 | Map name 'refupdateDaemonWdog_ClientHandlers' truncated to 'refupdateDaemonWdog_ClientHandl'.
Apr  2 20:02:31 swi-mdm9x28-wp user.err kernel: [ 5246.405045] bmi160: version magic '3.18.44 preempt mod_unload ARMv7 p2v8 ' should be '3.18.122 preempt mod_unload ARMv7 p2v8 '
Apr  2 20:02:31 swi-mdm9x28-wp user.err kernel: [ 5246.416419] bmi160: version magic '3.18.44 preempt mod_unload ARMv7 p2v8 ' should be '3.18.122 preempt mod_unload ARMv7 p2v8 '
Apr  2 20:02:31 swi-mdm9x28-wp user.crit Legato: *CRT* | supervisor[13052]/supervisor T=main | kernelModules.c ExecuteCommand() 248 | /sbin/insmod exited with error code 8.
Apr  2 20:02:31 swi-mdm9x28-wp user.err Legato: =ERR= | supervisor[13052]/supervisor T=main | kernelModules.c installModules() 1074 | Error in installing module bmi160.ko. Restarting system ...
Apr  2 20:02:31 swi-mdm9x28-wp user.emerg Legato: *EMR* | supervisor[13052]/supervisor T=main | supervisor.c framework_Reboot() 696 | Supervisor going down to trigger reboot.
Apr  2 20:02:33 swi-mdm9x28-wp daemon.info init: starting pid 13079, tty '': '/etc/init.d/rcK'
Apr  2 20:02:33 swi-mdm9x28-wp user.emerg Legato: *EMR* | _UNKNOWN_[839]/framework T=main | LE_FILENAME RunCurrentSystem() 1740 | System will reboot now !
Apr  2 20:02:33 swi-mdm9x28-wp user.warn kernel: [ 5248.106892] startSystem (1173) used greatest stack depth: 4428 bytes left

There seem to be plenty of errors. Are any of them helpful in figuring out what went wrong?
Thanks again,

-Nick

4

These are fine as the apps and services are killed and then updated when you install the new mangOH system. After the modem resets, the new system will be active.

In your sdef, are you sure you are including redSensorToCloud? mangOH includes a couple of commands “dr” and “twitter”, see if they work from the command line.

Could you help me understand what you are testing?

5

Hi @anon56110884.

Thanks - I’m going through the fresh-out-of-the-box MangOH-Red installation instructions.
So, I really have no idea what is what at this point. This is the second unexpected (by the documentation) failure I’ve run across. The first (reported here: Make red_wp76xx error: Couldn’t find component ‘periodicSensor’) was that make red_wp76xx failed.
The solution was to modify the mangOH.sdef file by commenting out the line
$MANGOH_ROOT/apps/locationService/location
I’ve posted the same question over on the mangoh forum (Build red_WP76xx fails).

-Nick

6

Hi @nburkitt
If you can explain what you are trying to test out or achieve, we can provide relevant information. For example, if you just trying to start a data session or send a SMS, you do not need to install mangOH. If you are trying to use some peripherals, then you may need something else. Would you be able to explain. Thanks

7

Hi @anon56110884.

I’m working through the “Getting Started” procedure provided here. Its ultimate purpose is to set up the development environment, and prepare the MangOH-Red board and Sierra Wireless modem so that I can then use it for my purposes.
Since no part of the procedure originated with me, I can’t tell you in any detail what its specific intent is. Every line of code, every downloaded file, every instruction, was provided by Sierra Wireless.
I’m basically walking through a canned tutorial, and my results don’t match those expected by the tutorial.
Thanks,

-Nick

8

I’m having the exact same experience as Nick, I have an active thread on the mangOH forum as I’ve yet to get my Red board working out of the box after several days thanks firstly to a broken git repository now the Legato update process fails.

I’m predominately a hardware engineer evaluating the platform for a commercial application. I like the specs of the WP76xx in fact they seem the perfect device for me, but the software so far scores 0/10.

I’m sure the mangOH/Legato thing will sort itself out, but meanwhile is it necessary to use it or is it possible to develop native apps for the Linux kernel? I will be needing most of the peripherals incl WWAN,GPS,Audio (line out not voice call), GPIO, SD storage and UART.

9

@nburkitt, it looks like the modem’s Linux does not match with the toolchain version with which your mangoH was compiled with. With every release, we provide modem firmware, Linux and Legato and a toolchain to cross compile your applications with. All components can be changed, but the application should be compiled with the toolchain that matches the Linux component installed on the modem.

I checked with R12 and I was able to install mangOH successfully. I’ve detailed the steps below. I’m using a new tool called “Leaf” that pulls in all the required components for a specific release. Leaf installation directions are at https://docs.legato.io/latest/toolsLeaf.html. I used a PC with Ubuntu 18.04 X86 with all latest updates as my build machine. VBox will also work.

Once you install Leaf, please follow the below steps (my workspace is “legatoWorkSpace”). I’ve truncated command responses and I picked R12 stable package and so my profile name for use with Leaf is "WP76_R12_Stable"

a:legatoWorkSpace$ leaf search -t wp76xx -t stable
image
a:legatoWorkSpace$ leaf setup WP76_R12_Stable -p swi-wp76_3.0.0
[7/7] Installing swi-wp76_3.0.0
Run install steps for swi-wp76_3.0.0.
Clone mangOH Repo
a:legatoWorkSpace$ git clone --recursive git://github.com/mangOH/mangOH
a:legatoWorkSpace$ cd mangOH/
Start a shell in your selected profile to compile mangOH. This will setup the required environment variables etc
a:mangOH$ leaf shell
Leaf Shell /bin/bash started in Leaf environment.
(lsh:WP76_R12_Stable) a:mangOH$make red_wp76xx

Now that mangOH is built, ensure that the modem has the correct firmware package that matches your build setup.
NOTE1: I’m using scp to copy the firmware bundle onto the modem and then I’m installing it from there using fwupdate
NOTE2: Make sure to install the “full” package
Switching to modem’s Linux shell

root@swi-mdm9x28-wp:~# scp user@192.168.2.3:/home/user/.leaf/./wp76-image_3.0.0/9999999_9907256_SWI9X07Y_02.18.05.00_00_ATT_002.040_002-full.spk .
user@192.168.2.3’s password:
9999999_9907256_SWI9X07Y_02.18.05.00_00_ATT_002.040_002-full.spk 100% 62MB 1.1MB/s 00:57

root@swi-mdm9x28-wp:~# fwupdate download 9999999_9907256_SWI9X07Y_02.18.05.00_00_ATT_002.040_002-full.spk

NOTE: Modem will reset here and then re-enumerate. The expected outputs are below. Note Legato’s hash.

root@swi-mdm9x28-wp:~# cm info
Device: WP7603
IMEI: 357409080109061
IMEISV: 5
FSN: U3801285440510
Firmware Version: SWI9X07Y_02.18.05.00 000000 jen[ 44.294766] 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:0x0c1300c8 OPER:0x00000090
kins 2018/07/19 17:40:21
Bootloader Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
MCU Version: 002.011
PRI Part Number (PN): 9906965
PRI Revision: 002.003
Carrier PRI Name: ATT
Carrier PRI Revision: 002.040_002
SKU: 1103194
Last Reset Cause: Reset, User Requested
Resets Count: Expected: 41 Unexpected: 1
root@swi-mdm9x28-wp:~# legato version
18.10.3_0b50331a9f4d0ecc0fd816c2a1300436
root@swi-mdm9x28-wp:~#

From the Leaf shell install the compiled mangOH update file using update.

(lsh:WP76_R12_Stable) a:mangOH$ update build/update_files/red/mangOH.wp76xx.update 192.168.2.2
Applying update from file ‘build/update_files/red/mangOH.wp76xx.update’ to device at address ‘192.168.2.2’.
SUCCESS
Done
(lsh:WP76_R12_Stable) a:mangOH$

Once mangOH is installed, if you check legato’s version, the hash is different, even though the version is the same, indicating that Legato system on the modem was updated along with mangOH.
root@swi-mdm9x28-wp:~# legato version
18.10.3_40e4f213bd74a24514c6f15ed0a78bee

From the modem’s Linux shell, check the applications and you can start and run redSensorToCloud.
root@swi-mdm9x28-wp:~# app status
[running] atAirVantage
[running] atQmiLinker
[running] atService
[running] audioService
[running] avcService
[running] battery
[running] cellNetService
[running] dataConnectionService
[running] dataHub
[running] devMode
[running] fwupdateService
[running] gpioService
[running] ledService
[running] modemService
[running] portService
[running] positioningService
[running] powerMgr
[running] qmiAirVantage
[stopped] redSensorToCloud
[running] secStore
[stopped] smsInboxService
[stopped] spiService
[stopped] tools
[stopped] voiceCallService
[stopped] wifi
[stopped] wifiApTest
[stopped] wifiClientTest
[running] wifiService
[stopped] wifiWebAp
root@swi-mdm9x28-wp:~# app status redSensorToCloud
[stopped] redSensorToCloud
root@swi-mdm9x28-wp:~# app start redSensorToCloud
root@swi-mdm9x28-wp:~# cm data
Index: 1
APN: broadband
PDP Type: IPV4V6
Connected: yes
Interface: rmnet_data0
Family[IPv4]: inet
IP[IPv4]: 10.5.246.43
Gateway[IPv4]: 10.5.246.44
Dns1[IPv4]: 172.26.38.1
Dns2[IPv4]: N/A
Family[IPv6]: inet6
IP[IPv6]: 2600:380:6c53:8a00:dc10:5fb4:b085:6786
Gateway[IPv6]: 2600:380:6c53:8a00:d432:da64:efa2:bb78
Dns1[IPv6]: fc00:a:a::300
Dns2[IPv6]: N/A
root@swi-mdm9x28-wp:~# app status redSensorToCloud
[running] redSensorToCloud

You can edit “mangOH.sdef” to enable the different services you need, rebuild mangOH and install it.

Please update if you are able to install and run mangOH.

10

@sciscitatio, we’re hoping Leaf simplifies the SW installation/management portion. Please have a look. Thanks.

11

@anon56110884 - Thanks for the effort, but I’ve already returned my MangOH Red board. You’ve built a system that’s obviously too complicated for you to support. A development board needs to work out of the box. A week and half of “try this, update that, redo something else” after discovering that the officially documented process is broken tells me that it’s’ far too risky to try to build a product on this platform.

-Nick