Hello,
I am trying out the “MUX Control” on https://github.com/mangOH.
I am facing an error message when executing mux (line command).
error message "mux: error while loading shared libraries: /legato/apps/23…/read-only/bin/…/lib/liblegato.so: file too short."
Anybody facing the same problem?
muxCtrlService is running but legato console showing error message when started
“Process Legato swi-mdm9x15WP8548…/muxCtrlService/muxCtrlService has 1 missing bindings:
Missing binding:
Client Id:
muxCtrlService.muxCtrlService.muxCtrl.mangoh_gpioPinUart1enable
Protocol Id:a814…
Service Id:.mangoh_gpioExp1Pin10”
You just need to do repo sync to get the latest version of all of the mangOH repositories and then build and deploy to your target. If this doesn’t solve your problem, please let me know.
It seem that le_wifiClient.api is missing. Can’t find it on any of the directory using “find . -name “le_wifiClient.api””
Temporarily comment out all “wifi” entry from “mangoh.sdef”.
Ran into another problem. After “update system.wp85.update 192.168.2.2”, mangOH restarted but after ssh into mangOH and do a “app status”, the apps seem to be the original apps (without any of the extra apps, mux control, GPIOExpander etc).
Did a “find -name “gpioEx*”” on top directory of the mangOH and found;
./legato/apps/xxxxxxxxxxxxxxxxxx/read-only/bin/gpioExpanderService
./legato/apps/xxxxxxxxxxxxxxxxxx/read-only/bin/gpioExpanderDemo
./mnt/flash/legato/apps/xxxxxxxxxxxxxxxxxx/read-only/bin/gpioExpanderService
./mnt/flash/legato/apps/xxxxxxxxxxxxxxxxxx/read-only/bin/gpioExpanderDemo
Did “legato version” on mangOH;
16.01.2_61a9587639c822a6838ad62e6297c
The WiFi API files are moving from mangOH/apps/WiFi into legato/interfaces in the upcoming release of Legato. It looks like the APIs were already deleted from mangOH/WiFi on the master branch. This should have been done on a separate branch. I am still thinking about what the best solution is, but I will try to figure something out today.
Hello David,
“make wp85” seem to to be working but the second problem is still there (mangOH with original apps, no extra)
Noticed mangOH reset several time before actually came alive.
Found a few log files titled “syslog-gpioExpanderService-gpioExpanderService-14xxxxx” in /mnt/legato_logs.
Below are the last few lines of the log.
May 18 02:34:50 swi-mdm9x15 user.info Legato: INFO | arduinoBridge[638]/bridgeComponent T=main | bridge.c mangoh_bridge_start() 625 | bridge started(0)
May 18 10:34:52 swi-mdm9x15 user.info Legato: INFO | gpioService[646]/sysfsGpio T=main | gpioSysfsUtils.c gpioSysfs_SessionCloseHandlerFunc() 1090 | Releasing GPIO 2
May 18 10:34:52 swi-mdm9x15 user.info Legato: INFO | supervisor[562]/supervisor T=main | proc.c proc_SigChildHandler() 1354 | Process ‘gpioExpanderService’ (PID: 751) has exited with exit code 1.
May 18 10:34:52 swi-mdm9x15 user.err Legato: =ERR= | supervisor[562]/supervisor T=main | system.c system_IsGood() 65 | Unknown system status found, ‘tried 4’, assuming a bad system.
May 18 10:34:52 swi-mdm9x15 user.emerg Legato: EMR | supervisor[562]/supervisor T=main | proc.c proc_SigChildHandler() 1393 | Process ‘gpioExpanderService’ reached fault limit while system in probation. Device will be rebooted.
I used the same firmware as you have and was able to download the system update file.
Could you try to redownload your firmware but follow steps below:
Please note that you need to know the SKU# of the module you are using and download the firmware accordingly.
So how do you know the SKU:
a. in a terminal on the mangOH, run microcom -E /dev/ttyAT
Then enter AT!ENTERCND=“A710” followed by AT!SKU?. Then CTRL+X to get out of the AT command mode.
b. then download the appropriate customer configuration. Please note that this process is only complete when you see the word "Enter…"
Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure.
c. then download Carrier Configuration. Please note that this process is only complete when you see the word "Enter…"
Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure.
Hello Ashish,
I had checked and downloaded the correct firmware.
SKU 1102816
I download the fw again and did the flashing again according to your instruction.
Did “app status” and still displaying the original apps (without the gpioExtender, muxControl, …).
Also remove the ~/mangOH directory and did the whole git clone according to my previous post. Not working too.
Can you let me know all jumpers and switches settings?
Trying to remove item from mangoh.sdef.
It seem that wifiService, wifiClienTest.adef, wifiApTest.adef, wifiWebAp.adef, wifi.adef, arduinoBridge.adef, dataRouter.adef and mqttClient.adef ok.
The problem related to gpioExpanderService.adef, gpioExpanderDemo.adef, muxCtrlService.adef and muxCtrlTools.adef.
Changed gpioExpanderService.adef; sandboxed -> true, start -> manual.
mangoh.sdef revert back to original mangoh.sdef.
“app status” shown as expected.
“app start gpioExpanderService” caused mangoh to reboot and gpioExpanderService stopped after reboot. ???
Hi CSLE
Do you now see all the apps when you do app status?
Can you try NOTto make the change you did on gpioExpanderService.adef; sandboxed -> true, start -> manual? Keep the original settings.
For jumper, please install CN900 but this should not affect the problem you see as it is used to allow for interrupt capabilities of the GPIO expander.
cheers,
Ashish
Restarted from beginning again from my previous post.
1)…11)
My mangOH unit will be reset for 4 times (output from UART) and all extra apps from mangOH appeared when I did “app status”. This is first time I manage to get this, strange!
Appear that gpioExpanderService has stopped. Trying to “app start gpioExpanderService” again but failed.
From “logread -f” terminal, it show some error messages(in highlight).
