This repository contains the SDK for firmware development for
SGW OEM Modules and Boards such as F1 product family.
You can start directly building your own multi-connectivity embedded project
from here.
These are a quick references to contents of the SDK.
- Getting Started
- Change Log
- SDK Framework
- Connectivity Features
- Services
- F1 Platform Specific Services.
- Tools.
The SDK offers the following features:
-
Multi-connectivity support such as WiFi, BLT, LTE-M and LoRa at both levels micropython or C/C++.
-
Modern I2C Bridge Architecture providing unified I2C device management, where C/C++ drivers seamlessly coordinate with MicroPython I2C for hardware peripherals like fuel gauges and IO expanders.
-
Easy building; the build system is capable of driving the whole environment preparation burdens in a single command such as; fetching and downloading the external dependencies, required installations, building and image generation and flashing.
-
The feasibility to develop your project either in micropython or in C/C++ or both together.
-
A micropython binding layer (a lite interface) to couple/decouple your newly developped micropython C modules. By this layer, you can build your own component in C language and bind it to the micropython so that the micropython application can utilize it.
-
Generic C-Libraries such as:
- Featural logging library, to start easily trace your application.
- Auto-generation State-machine.
- Different utilities functionalities.
-
Test engine to build your own test suite and run the existing test suites.
You have F1 based board. Then follow the following steps to get started with development on F1 platform.
This SDK provides a powerful builder to tackle the firmware building and the configuration management of the SDK components and underlying externally used libraries or other platforms.
-
clone the SDK repository
git clone https://github.com/sg-wireless/sg-sdk.git -
change directory to the cloned repository
cd sg-sdk -
run the help command to start constituting your target build command
./fw_builder.sh --help, and you will get the following output or similar to it.The Firmware SDK Builder CLI This is the main build system command line interface for the SDK build system. The available options are grouped mainly in three categories: * hardware options the required options for platform and board selection. * software options the required options to select certain build variants and specifying the user project main directory. * build system options the actual build commands such as build and flash synopsis: --------- builder.py [--help] --board BOARD [--variant VARIANT] [--defs DEFS...] [COMMAND] [--port PORT...] [--project-dir PROJECT-DIR] [--custom-version-string CUSTOM-VERSION-STRING] [--clean] [--erase] [--flash] [--install-target INSTALL-TARGET...] [--quiet-install] [--secure] --board BOARD The target hardware platform board. SGW3101-F1W-OEM SGW3131-F1WS-OEM SGW3201-F1L-OEM SGW3201-F1L-StarterKit SGW3231-F1LS-OEM SGW3401-F1C-OEM SGW3401-F1C-StarterKit SGW3431-F1CS-OEM SGW3501-F1-EVB SGW3501-F1-OEM SGW3501-F1-StarterKit SGW3531-F1S-OEM [--variant VARIANT] *micropython* build with micropython support native build for C/C++ application only [COMMAND] *build* To only build the firmware image clean To clean the built artifacts flash To build and flash the connected board(s) erase To erase the whole flash config To open the configuration menu env To open the environment for idf.py / cmake [--port PORT...] Flashing port(s) [--project-dir DIR] User/example project folder [--clean] Clean before building [--erase] Erase device flash after building [--flash] Flash firmware after building [--secure] Enable secure boot and flash encryption -
Create a directory for your application development anywhere, and we will refer to your application path by
<user-app-dir>. -
Create the basic CMakeLists.txt in your application directory with the following contents:
__sdk_add_component( user_app_component SRCS "${CMAKE_CURRENT_LIST_DIR}/*.c" MPY_MODS "${CMAKE_CURRENT_LIST_DIR}/*.c" LOGS_DEFS "${CMAKE_CURRENT_LIST_DIR}/*.c" INCS_PRIV # any required includes by your application ) __sdk_add_micropython_frozen_manifest( # add your micropython manifest files here to be added as a frozen code # within micropython building )
-
To build your project application with micropython support for the board SGW3501 and having lora and lte feature supported, issue this command:
./fw_builder.sh \ --board SGW3501-F1-StarterKit \ # board F1 StarterKit --project-dir <user-app-dir> \ # application directory <user-app-dir>For the first time, the following actions will be carried on by the builder and it will take additional time.
- the 3rd party repository will be cloned specifically the micropython and esp-idf repos.
- the esp-idf installation procedure will be tackled by the SDK FW builder
- then start building the whole project.
To build without micropython support and the whole application development will be natively in C language, use the following command
./fw_builder.sh \ --board SGW3501-F1-StarterKit \ # board F1 StarterKit --project-dir <user-app-dir> \ # application directory <user-app-dir> --variant native # build only for C application -
Connect your development board and start flashing. We will be refering to the board usb port by
<board-port>. Then issue this command:./fw_builder.sh \ --board SGW3501-F1-StarterKit \ # board F1 StarterKit --project-dir <user-app-dir> \ # application directory <user-app-dir> --variant native # build only for C application flash --port <board-port> # flash to a board port <board-port>
Now you are ready and your application is running onto the board.
For more detailed guides on specific topics, see the tables below.
| Module | Description | Documentation |
|---|---|---|
| LoRa | LoRa connectivity stack | Overview · WAN · RAW · Callback · Certification |
| Ctrl Client | Ctrl platform client service | User API |
| FW Version | Firmware versioning structure | README |
| I2C Bridge | MicroPython I2C bridge for C drivers | README · Examples |
| Module | Description | Documentation |
|---|---|---|
| System Info | Board, version, flash, and eFuse info | sysinfo.md |
| System Inspection | Runtime system inspection | sys_inspect.md |
| NVS Interface | Non-volatile storage key-value access | nvs_if.md |
| eFuse Interface | Read factory-provisioned board identity | efuse_if.md |
| Fuel Gauge | BQ27421 battery monitoring | fuel_gauge.md |
| RGB LED | WS2812B addressable LED control | rgbled.md |
| IO Expander | PCAL6408A GPIO expander | ioexp.md |
| CAN Bus | CAN interface | can.md |
| LTE-M | LTE-M cellular connectivity | LTE Main · modlte API · UART Guard |
| Safeboot | Safe boot recovery mechanism | safeboot.md |
| FUOTA | Firmware Update Over The Air | mod_fuota.md |
| Topic | Description | Documentation |
|---|---|---|
| SDK Builder | Main build system usage | builder.md |
| Build Commands | Common commands and mpremote usage | COMMANDS.md |
| Build System | Component registration and internals | BUILD_SYSTEM.md |
| Config Manager | Firmware configuration management | config-mgr.md |
| App Development | Application project development guide | fw_app_prj.md |
| Security | Secure boot and flash encryption | SECURITY.md |
| Logging | SDK logging system integration | LOGGING.md |
| LTE Events | LTE event handler system | LTE_EVENTS.md |
| Test Engine | Test suite framework | readme.md |