The mangOH repository now uses a Legato 18.05.1 feature

1

Legato 18.05.0 introduced a feature enabling an MDEF file (defining a kernel module) to depend on another MDEF. What this means is that it’s now possible for us to accurately describe our kernel module dependencies in Legato instead of resorting to ugly naming hacks for our MDEF files. Previously we named the MDEF files with a numeric prefix to control the order that the modules were loaded in.

18.05.0 had a fairly critical defect that meant that the new kernel module dependency scheme wasn’t usable for us. The MDEF load: manual feature resulted in infinite loops. As a result, I held off until 18.05.1 until making use of the kernel module dependency feature.

What all this means for users of the mangOH repository is that you will now either need to build against 18.05.1 or newer or use a previous revision from the mangOH repository.

1 Like
2

Thank I understand now why I can’t build 15mn ago :slight_smile:

I have update to legato 18.05.1 and now ‘make red_wp76xx’ compile without error.

3

@dfrey

On wp7607 and MangOH red, I have boot loop and legato roll back after flashing the new update…

Legato 18.5.1 and new mangOH build.

4

I have try to reflash the WP76 with original firmware and clean legato

legato stop
rm -rf /mnt/flash/legato/*
reboot

reflash the new update but same result (bootloop and rollback)

:frowning:

5

Have the same issue when I flash only the legato build…
Strange no ?

6

I am very new to Legato platform.
After updating to the latest commit I get the below compile error:

mksys -t wp76xx --object-dir=build/red_wp76xx --output-dir=build/update_files/red mangOH.sdef
** Warning: Ignoring empty app specification
** Warning: Ignoring empty app specification
** Warning: Ignoring empty app specification
** ERROR:
/home/mangoh/mangOH/linux_kernel_modules/mangoh/mangoh_red_dv5.mdef:23:8: error: Unrecognized keyword ‘requires’.
Makefile:82: recipe for target ‘red_wp76xx’ failed
make: *** [red_wp76xx] Error 1

Kindly help.

Regards,
Devaiah

7

@devaiah

You must update legato. See user guides.

Take the version 18.05.1 and the mangOH build will work.

8

This is a message that I have reported in the legato Forum about “Legato” problems.

9

@Francis.duhaut Thanks a lot. It worked after updating Legato to the latest one.

My next task is to get MQTT up and running with a generic MQTT broker. Looks like it is a bit of work as current MQTT is designed to only work with Airwantage cloud. Not sure where to start.
Any pointers to help get started is much appreciated.

Thank you again for helping me resolve build issue!!

10

Did you try to flash the image in your device ?
With my wp7607 it doesn’t work.

Sorry I have no experience with MQTT I use AirVantage assetData but you will find information on this forum.

11

Yes I was able to flash it on my WP7608 mangOH red board.

I am using MQTT Client from use_paho_linux_version branch now. Still trying to understand how the system works :slight_smile:

12

Good what firmware do you use in your WP7608?

13

My Firmware version is: SWI9X07Y_02.16.02.00

14

I have the same firmware for a WP7607. I have try to reflash it but legato 18.05 don’t work with it.
It’s a first sample of WP76 I don’t if this the problem. I wait new sample next week.

15

When I reflash R8 firmware it works… I think my WP7607 is strange…

16

What software is using to flash the wp ? Swiflash or the .exe (windows

17

It looks like I botched the toolchains in the mangOH Dev using Legato 18.04.0 on Ubuntu 18.04 - r1 version of the VM and that may have started causing problems with Legato 18.05.0.

Look at the /opt/swi contents in the 18.04.0 VM:

mangoh@mangoh-vm:~$ ls -l /opt/swi/
total 12
drwxr-xr-x 3 root root 4096 May  9 18:46 y17-ext-SWI9X15Y_07.12.14.00
lrwxrwxrwx 1 root root   28 May  9 18:47 y17-ext-wp750x -> y17-ext-SWI9X15Y_07.12.14.00
lrwxrwxrwx 1 root root   28 May  9 18:46 y17-ext-wp85 -> y17-ext-SWI9X15Y_07.12.14.00
drwxr-xr-x 3 root root 4096 May  9 18:37 y22-ext-SWI9X06Y_02.14.04.00
drwxr-xr-x 3 root root 4096 May  9 18:33 y22-ext-SWI9X07Y_02.16.02.00
lrwxrwxrwx 1 root root   28 May  9 18:46 y22-ext-wp76xx -> y22-ext-SWI9X06Y_02.14.04.00
lrwxrwxrwx 1 root root   28 May  9 18:48 y22-ext-wp77xx -> y22-ext-SWI9X07Y_02.16.02.00

Now look at the /opt/swi contents in the 18.05.1 VM:

mangoh@mangoh-vm:~$ ls -l /opt/swi/
total 12
drwxr-xr-x 3 root root 4096 May  9 18:46 y17-ext-SWI9X15Y_07.12.14.00
lrwxrwxrwx 1 root root   28 May  9 18:47 y17-ext-wp750x -> y17-ext-SWI9X15Y_07.12.14.00
lrwxrwxrwx 1 root root   28 May  9 18:46 y17-ext-wp85 -> y17-ext-SWI9X15Y_07.12.14.00
drwxr-xr-x 3 root root 4096 Jun 25 18:36 y22-ext-SWI9X06Y_02.16.02.00
drwxr-xr-x 3 root root 4096 Jun 25 18:37 y22-ext-SWI9X07Y_02.16.02.00
lrwxrwxrwx 1 root root   28 Jun 25 18:28 y22-ext-wp76xx -> y22-ext-SWI9X07Y_02.16.02.00
lrwxrwxrwx 1 root root   28 Jun 25 18:37 y22-ext-wp77xx -> y22-ext-SWI9X06Y_02.16.02.00

I just updated the VM for 18.05.1 today. The mangoh.io website hasn’t been updated, but the direct link should work. The sha256 checksum for this download is 2017c93b4f37823ceafd8d70c1bb2ecd3a3a0995d324894d380d566fc4bedfbd.

Going back to the comparison of the two directories, the problem is that the y22-ext-wp76xx symlink points at a toolchain that was distributed with WP77 release 8 and the y22-ext-wp77xx symlink points at a toolchain that was distributed with WP76 release 9. Sorry about the mixup. You can either download the new VM or you can update the existing VM by doing the following:

  1. Delete the wp77 release 8 toolchain
  2. Install the wp77 release 9 toolchain
  3. sudo apt-get install libwebkitgtk-1.0-0 (this was a missing dependency of Developer Studio)
  4. Use repo to update Legato to 18.05.1
  5. Apply the patches for Legato 18.05.1 from ~/Legato_patches

If this sounds too complicated, just get the new VM :slight_smile:

18

@dfrey thank a lot for this update. I will try it this morning.

Francis.

19

@dfrey it work fine with my WP7607 !

Thank for the support.
Cheers

Francis

20

How can i update 18.05.1 legato version