Make fails with mangOH red + wp7603

mangOH Red
1

I just received my new mangOH rec + wp7603 and I am setting it up according to the mangOH_Red_GSG_(Windows).pdf (Rev 5 9/11/18) guide. Everything went ok until I reached section “5. Build the mangOH Distribution” where I got some errors while executing the “make wp76xx” instruction.

After looking in the forum I was able to figure I needed to follow the procedure described in https://github.com/mangOH/mangOH/blob/master/README.md so I followed all the instructions in the README.md file. I get all the way to the step where I “make red_wp76xx”; here I get the following error message:

/home/mangoh/mangOH/apps/RedSensorToCloud/redSensorToCloud.adef:30:4: error: Binding to non-existent server app ‘avcService’.
Makefile:102: recipe for target ‘red_wp76xx’ failed

Below is a complete transcript of the console output for “make red_wp76xx”. I will appreciate any assistance with this issue.

mangoh@mangoh-vm:~/mangOH$ LEGATO=1 make red_wp76xx
make -C /home/mangoh/workspace/legato framework_wp76xx
make[1]: Entering directory '/home/mangoh/workspace/legato'
Building Legato for target 'wp76xx'
Makefile:127: build/wp76xx/.config.mk: No such file or directory
  KSET      /home/mangoh/workspace/legato/.config.wp76xx - TARGET_WP76XX
  KCONFIG   /home/mangoh/workspace/legato/.config.wp76xx
  GEN       build/wp76xx/.config.mk
Building Legato for target 'wp76xx'
  GEN       version
  GEN       build/wp76xx/framework/include/le_config.h
  MAKE      tools
make[2]: Entering directory '/home/mangoh/workspace/legato'
Using ninja installed at: /usr/bin/ninja
  GEN       /home/mangoh/workspace/legato/build/tools/build.ninja
Tools arch: x86_64
  NPM       languageServer
  MAKE      mkPatch
make[3]: Entering directory '/home/mangoh/workspace/legato/framework/tools/mkPatch'
make[3]: '/home/mangoh/workspace/legato/bin/mkPatch' is up to date.
make[3]: Leaving directory '/home/mangoh/workspace/legato/framework/tools/mkPatch'
  NINJA     /home/mangoh/workspace/legato/build/tools/build.ninja
ninja: no work to do.
make[2]: Leaving directory '/home/mangoh/workspace/legato'
  GEN       sources.md5
  GEN       package.properties
  GEN       build/wp76xx/config.sh
  MAKE      framework
make[2]: Entering directory '/home/mangoh/workspace/legato'
  GEN       /home/mangoh/workspace/legato/build/wp76xx/framework/build.ninja
  NINJA     /home/mangoh/workspace/legato/build/wp76xx/framework/build.ninja
[67/67] Dynamic linking liblegato
  CCLD      /home/mangoh/workspace/legato/build/wp76xx/framework/bin/startSystem
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/supervisor
[67/67] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/serviceDirectory
[5/5] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/logCtrlDaemon
[16/16] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/configTree
[30/30] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/watchdog
[40/40] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/updateDaemon
[64/64] Linking C executable
  MAKE      targetTools
make[3]: Entering directory '/home/mangoh/workspace/legato'
  CMAKE     /home/mangoh/workspace/legato/build/wp76xx/framework/lib/libjansson.so
  MAKE      /home/mangoh/workspace/legato/build/wp76xx/framework/lib/libjansson.so
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/config
[15/15] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/log
[3/3] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/sdir
[9/9] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/inspect
[3/3] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/xattr
[3/3] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/appStopClient
[3/3] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/app
[27/27] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/update
[19/19] Linking C executable
  MKEXE     /home/mangoh/workspace/legato/build/wp76xx/framework/bin/sbtrace
[11/11] Linking C executable
  MKAPP     devMode
[36/36] Packaging app
make[3]: Leaving directory '/home/mangoh/workspace/legato'
  GEN       md5
make[2]: Leaving directory '/home/mangoh/workspace/legato'
make[1]: Leaving directory '/home/mangoh/workspace/legato'
# NOTE: When using leaf, these TOOLCHAIN_X variables aren't needed.
TOOLCHAIN_DIR=/opt/swi/SWI9X07Y_02.28.03.03/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi \
TOOLCHAIN_PREFIX=arm-poky-linux-gnueabi- \
mksys -t wp76xx --object-dir=build/red_wp76xx --output-dir=build/update_files/red_wp76xx red.sdef
** ERROR:
/home/mangoh/mangOH/apps/RedSensorToCloud/redSensorToCloud.adef:30:4: error: Binding to non-existent server app 'avcService'.
Makefile:102: recipe for target 'red_wp76xx' failed
make: *** [red_wp76xx] Error 1
mangoh@mangoh-vm:~/mangOH$
2

I have seen that before, but it went away, and I’m not sure what I did to fix it. But, I know that I have updated to the latest Legato 19.04 recently. What version of Legato are you using?

3

@luisvi70, I’m assuming you are using Legato AF 19.04. If so this is an known issue with this version of the AF framework, see this post https://forum.legato.io/t/migrate-from-legato-18-09-0-to-19-02-0/4368/7?u=dbeckwith

4

@jchitty I followed the instructions in https://github.com/legatoproject/legato-af/blob/master/README.md and when I check the version file in my ~/workspace/legato directory I see 19.01.0-265-g846a5ba9. Can you point me to instructions on how to update to legato 19.04?

@dbeckwith I will review the information you indicate in the referenced post. But as you can see above it seems I am using legato AF version 19.01.

5

@luisvi70 My understanding is the problem you are experiencing is a result of the Legato AF moving to use KConfig which started in 19. Did you try the command recommended in the post I linked? It works for me on 19.02 and 19.04.

Darren

6

@dbeckwith I can confirm that the procedure described in your referenced post solved the issue I reported. Thanks for the support.

7

@luisvi70 No problem, glad I was able to help.

If it’s not too much trouble can you mark the above reply as a solution so others can benefit.

Darren