when you download the SDK, you should also download some image:
/home/owner/leaf/leaf-data/swi-wp76_4.7.0/wp76-image
This is my profile setup now:
but when i try to compile with “OCTANE=0 make yellow” i receive this error:
/home/gianmaria/myWorkspace/leaf-data/ManYel_1/mangOH-yellow-wp77xx-toolchain/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
is not a full path to an existing compiler tool.
Tell CMake where to find the compiler by setting either the environment
variable “CC” or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.
Maybe my installation is missing something…
thanks,
Gianmaria
I mean download the image to your module to upgrade to 19.11.5
Done. Now I 've:
root@swi-mdm9x28-wp:~# legato version
19.11.5_af513c997e3c908d4e38447669e4c988
root@swi-mdm9x28-wp:~# cm info
Device: WP7702
IMEI: 352653090194176
IMEISV: 6
FSN: 4L931388970810
Firmware Version: SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
Bootloader Version: SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
MCU Version: 002.015
PRI Part Number (PN): 9909138
PRI Revision: 001.001
Carrier PRI Name: GENERIC
Carrier PRI Revision: 001.071_001
SKU: 1104405
Last Reset Cause: Power Down
Resets Count: Expected: 318 Unexpected: 0
root@swi-mdm9x28-wp:~#
I will start app check to see if it fixed the networking problems… and will get back to you.
Thanks
gian
But still you need to compile the mangoh source with this sdk
All done. Works and is stable. Yes i recompiled everything following your instructions.
this post contains a lot of useful information at moment.
thanks a lot.
Gian
Correction. Problem is still present. I’m start thinking it’s related to insufficient power.
I suspected this since first problems and so i used a MacBook powerAc to power it on…
but maybe there is some limitations in hardware, maybe the usb port is not capable to give enough power to the modem during high consumption/transmission.
I have to wait for the prototype of the product, where i will have only the modem and the accelerometer and some other stuff (a led, the sim, the gps antenna).
It’s so courious as there is no log and no info on reset cause, or at least it seems that the reset was software requested… “Resets Count: Expected: 325 Unexpected: 0”.
gianmaria
Finally i have some logs. This are printed on console before reboot. It seems that the reboot is system requested for some reason… but i dont understand nothing in this logs… it’s not clear at all for me.
console.pdf (60.3 KB)
Do you see reset when not running mangoh layer?
what do you mean? When I just use the device with firmware uploaded from sierra e no mangoh build loaded on the device? No… no reset, but no accelerometer also… as you can read in previous posts.
PS: another consolelog here…
console2.pdf (41.5 KB)
Maybe reboot reason is here… in first lines of log:
an 6 04:08:25 swi-mdm9x28-wp user.crit Legato: CRT | watchdog[1142]/watchdogDaemon T=main | watchdog.c WatchdogHandleExpiry() 488 | Mandatory watchdog double fault on process [audioService][audioDaemon]
Jan 6 04:08:25 swi-mdm9x28-wp user.emerg Legato: EMR | watchdog[1142]/le_pa_wdog T=main | pa_wdog.c pa_wdog_Shutdown() 72 | Watchdog expired. Restart device.
Jan 6 04:08:25 swi-mdm9x28-wp user.emerg Legato: EMR | supervisor[1062]/supervisor T=main | frameworkDaemons.c fwDaemons_SigChildHandler() 523 | Framework daemon ‘watchdog’ has exited with code 1
But… hell… i dont use at all audioService.
gian
Audio is still there when you running without mangoh layer…
Wondering if you just add the bmi driver to the legato framework without running extra app, you can modify the sdef in mangoh source to exclude extra app and driver
E.g.
Ok… we can try if you help me. I will post here the edited version of yellow.sdef and shared.sdef. I will remove everything i dont need. Just the essentials.
Gian
Hello,
4 days ago, i created a new device image using swicwe following instruction here:
this image is super stable and i dont have any problem with the device… it continued to worl for 4 days sending data, and without any reboot. Naturally i dont have a working BMI160 but i simulated the signals sent from accelerometer.
Now I’m thinking to continue on this way and recompile the base linux system including the BMI160 drivers, but i dont know how to make some simple steps… In my experience with linux recompilation (android 8, 9 , 10 ) i had access to the make menuconfig to include what i need in the kernel, and than editing DTS files to specify where on the I2C bus devices are placed. But with this platform I’m a little bit lost… can you point me to the right direction?
In my final product… I will not have anything of mangoh, except wp7702, bmi160 and rtclock, so a custom build is perfect for me.
Regards,
Gianmaria
Didn’t you modify the yellow.sdef and shared.sdef and remove everything you don’t need?
Yes i did, but didnt try the compiled version. That’s cause i think that my final product will be so far from mango yellow… but i can give a try now if you want to know what happen .
Will be back to you with results…
gianmaria
find attached the yellow.sdef and shared .sdef I’m using.
Gian
yellow.sdef (2.7 KB)
shared.sdef (1.0 KB)
No way. It reboots… there must be something in the yellow build that resets the device in some way.
Some results till here:
- Using yellow build (latest legato and SWI version), the device reboots randombly, expecially if network reception is low, but it can be just a case.
- Using default SWI firmware or repacked fimware version using components from sierra, the devices never reboots. Even with low network coverage nor in case network is completly lost and reaquired. Network data goes up and system works perfetly.
- The power source is excluded, I’m using a powerbank right now, and in case (2) it’s stable.
Next step is to add the BMI160 to the kernel following this:
https://docs.legato.io/18_09/getStartedKO.html
rebuild the linux and legato platform then repack everything with swicwe and see what happen. Naturally starting from official sierra stuff.
Right?
Gian
You need to figure out which line deleted makes the reboot
Another way maybe just add the bmi driver in legato framework
I think there is some sort of watchdog rebooting the device, but the reason can’t be investigated cause nothing were logged.
Can you help me to just include the bmi160 in legato?
Regards
Gianmaria