Skip to content

About the SDK

The following is an overview of the files installed in the SDK installation path.

Directory Organization

Here's the xPico 600 SDK directory structure and descriptions of what's inside.

C:/xPico600 is the installation directory in Windows. The installer automatically places the SDK here.

xPico600/build contains platform.make, which includes the compile flags and tells the compiler which flags to apply to your project when you build it.

xPico600/custom contains the code for your custom includes, modules, and projects.

custom/includes contains your custom H files.

custom/module contains the custom module's C files and bom/cfiles.make, which specifies which C files to included for this module when you build the project. See Creating Modules for more information.

custom/project contains Makefile (the same for all projects) and modules.make, which specifies which modules to include when you build the project. See Building Projects for more information.

xPico600/env contains env.make.

xPico600/html contains the html files for the Developer Reference.

xPico600/lantronix contains Lantronix-provided modules, includes, and libraries.

xPico600/rules contains build templates and resources for the build process.

xPico600/toolchain contains files for tools and other resources.

xPico600/work contains built projects and the ROM file after you build them from thecustom/project/project_name directory.

xPico600/MinGW-shell is a shortcut to the SDK's command line/shell application.

Build Environment

The build environment is entirely contained within the SDK files and initiated when you run the make command. You don't need to use any additional tools to create projects that make use of either the Lantronix-provided, or your own, custom modules, includes, and libraries.

Notes Regarding Secure Boot

If your device has Secure Boot enabled without an OEM Key programmed, then you must use the signed MTL rom.

If your device has Secure Boot enabled with an OEM Key programmed, then you must sign the unsigned MTL rom with your private key and use the resulting rom.

If your device does not have Secure Boot enabled, you can use either the signed or unsigned MTL roms.