Starting out with the FX30S and questions abound

IoT Gateways FX30
2

Hi Mark,

  1. There is no one “best” method for FX30/FX30S development setup. It really depends on what you need to develop.

If you only need to develop a Legato application, then Developer Studio would be quickest and easiest. You would need to ensure you’re using the correct toolchain and building for the correct target.

If you want to modify the kernel or root file system, then you’ll likely want to use the Yocto build. (but be aware there is a way to build kernel modules via Legato as well).

As far as I know, the legato-spm tool is not up to date with the R14.0.4.002 FX30 release.

The mangOH tutorials are specific for the mangOH boards so they won’t apply directly to the FX30. We do have plans to release an Application Note to clarify some of the issues you’re experiencing with the FX30 build.

  1. The correct version to use for the FX30S is referenced by the link you provided, R14.0.4.002 with Legato version 16.10.1.m3. Note, this version of Legato is actually a maintenance branch off version 16.10.3 even though it appears to be based off 16.10.1.

Download the Source code tarfile and the Legato tarfile. Extract the Source tarfile first, then extract the Legato tarfile into main directory of the Source code. If all is done correctly, you should see a bunch of folders such as kernel, lk, meta-columbia-x and a legato folder as well (You might need to rename the legato folder to just “legato”).

You can also insert your Legato application into the legato folder of the Yocto build and have it as part of the Legato image. You can browse through the legato folders for the right location.

  1. To build the image, just type “make”
    The binary image generated is a CWE file located at:
    build_bin/tmp/deploy/images/swi-mdm9x15/

Look for “boot-yocto-legato_wp85.cwe”. This image will contain the bootloader, kernel, RFS and Legato. The Legato image only is “legato-image.wp85.cwe”. You can also install the swicwe tool (https://source.sierrawireless.com/resources/airprime/software/swicwe/) to parse the CWE files and view their contents.

To replace openSSL, try modifying the recipe:
poky/meta/recipes-connectivity/openssl/openssl.inc

Note however, it’s not good practice to edit existing recipes, it would be preferable to create an openssl.bbappend file in your own custom layer.

BR,
Chris