Differences

This shows you the differences between two versions of the page.

--- wiki:loraloc_spf-5.1.0 [2018/08/29 10:59]
ghi removed
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Wirnet™ iBTS Packet Forwarder v5.1.0-klk2 - Instructions ======
-===== File structure =====
-The package installation creates several files in the system.\\
-These files are removed when uninstalling the package.
-{{ :images:spf2_folders_v5-1-0.png |}}
-The Packet Forwarder installation package creates common API files at runtime (internal usage) : \\
-{{ :wiki:spf2_folders_2.png | files are also removed when uninstalling (see below).}}
-\\
-===== Configuration =====
-This chapter describes how to configure the packet Forwarder through <fc #4682b4>**6 steps**</fc>.
-\\
-==== JSON files : informations and behaviour ====
-__Location :__ ''/user/spf2/etc''
-{{ :images:config_v5-1-0.png |}}
-The packet forwarder uses two configuration files ''config.json'' and ''local.json''. To simplify the configuration, instead of directly using files named this way, two symbolic links are used :
-   * **config.json** : Contains the LoRa, the gateway and the GPS parameters.
-   * **local.json** : Contains the calibration of the frontend. This file must not be modified, it is hardware dependent.
-The way the packet forwarder takes configuration files into account is the following:
-     - If there is a ''config.json'' parse it, look for the next file.
-     - If there is a ''local.json'' parse it. If some parameters are defined in both config and local configuration files, the local definition overwrites the global config definition.
-     - In our case the ''local.conf'' is automatically generated at boot time. It contains antenna configuration. Do not change this file.
-There are __two kinds of configuration__ files for the Wirnet™ iBTS product :
-   * **single_antenna** configuration.
-   * **dual_antenna** configuration.
-<note important>
-The default LoRa Radio-Frequency configuration is "Europe 868MHz". This can be changed after the package installation.
-</note>
-To check whether you have to use single or dual mode, read the chapter 4.6.2.4 of the [[wiki:resources#wirnet_ibts_installation_and_maintenance_v10| Installation manual. ]]
-<fc #4682b4>**Step 1**</fc><fc #4682b4> - Select the correct JSON file.</fc>
-\\
-<fc #4682b4>**Step 2**</fc><fc #4682b4> - Execute the following commands : </fc>
-    * <code bash>
-    rm config.json
-    # <config file> is the chosen JSON in first step
-    ln -s <selected_config_file> config.json</code>
-\\
-==== JSON files : configuration structure ====
-Structure of ''config.json file'' :
-{{:wiki:overview.png|}}
-In each configuration file, there are the following arrays :
-**SX1301 configuration** : that should contain the parameters for the Lora concentrator board (RF channels definition, modem parameters, etc).
-{{:wiki:sx1301.png|}}
-**gateway_configuration** : that should contain the gateway parameters (gateway MAC address, IP address of the server, keep-alive time, etc).
-{{:wiki:gateway.png|}}
-**gps_configuration**
-{{:wiki:gps.png|}}
-There are many configuration fields among these files, but most of them are by default correctly filled.
-\\
-==== Radio Frequencies configurations ====
-Each LoRaLoc module contains two SX1301. Each SX1301 can be configured to use 10 different frequencies. However, these channels need to be contained within a 2 Mhz bandwidth.
-  * ''chip_enable'' : enable/disable SX1301.
-  * ''chip_center_freq'' : is used to define the center frequency of the SX1301. All 10 channels will be around this particular frequency (+/- 1Mhz).
-  * ''chan_rx_freq'' : are used to define each channel frequencies.
-  * ''chip_rf_chain'' : define the rf chain used by the SX1301. The front-end board integrates two duplicated TX and Rx paths (RF1 path and RF2 path). Each TX/RX path is connected to one SMB antenna port, referenced as RF1 and RF2 (Installation manual 1.5.4.4 Front-end boards).
-<code>
-"SX1301_conf":[
- {
-    "chip_enable": true,
-    "chip_center_freq": 866000000,
-    "chip_rf_chain": 0,
-    "chan_multiSF_0": { "chan_rx_freq": 865500000, "spread_factor": "7-12" },
-    "chan_multiSF_1": { "chan_rx_freq": 865700000, "spread_factor": "7-12" },
-    "chan_multiSF_2": { "chan_rx_freq": 865900000, "spread_factor": "7-12" },
-    "chan_multiSF_3": { "chan_rx_freq": 866100000, "spread_factor": "7-12" },
-    "chan_multiSF_4": { "chan_rx_freq": 866300000, "spread_factor": "7-12" },
-    "chan_multiSF_5": { "chan_rx_freq": 866500000, "spread_factor": "7-12" },
-    "chan_multiSF_6": { "chan_rx_freq": 867100000, "spread_factor": "7-12" },
-    "chan_multiSF_7": { "chan_rx_freq": 867300000, "spread_factor": "7-12" },
-    "chan_LoRa_std" : { "chan_rx_freq": 867300000, "bandwidth": 250000, "spread_factor": 7 },
-    "chan_FSK"      : { "chan_rx_freq": 866900000, "bandwidth": 125000, "bit_rate": 50000 }
- },{
-    "chip_enable": true,
-    "chip_center_freq": 868000000,
-    "chip_rf_chain": 1,
-    "chan_multiSF_0": { "chan_rx_freq": 867500000, "spread_factor": "7-12" },
-    "chan_multiSF_1": { "chan_rx_freq": 867700000, "spread_factor": "7-12" },
-    "chan_multiSF_2": { "chan_rx_freq": 867900000, "spread_factor": "7-12" },
-    "chan_multiSF_3": { "chan_rx_freq": 868100000, "spread_factor": "7-12" },
-    "chan_multiSF_4": { "chan_rx_freq": 868300000, "spread_factor": "7-12" },
-    "chan_multiSF_5": { "chan_rx_freq": 868500000, "spread_factor": "7-12" },
-    "chan_multiSF_6": { "chan_rx_freq": 868700000, "spread_factor": "7-12" },
-    "chan_multiSF_7": { "chan_rx_freq": 868900000, "spread_factor": "7-12" },
-    "chan_LoRa_std" : { "chan_rx_freq": 868300000, "bandwidth": 250000, "spread_factor": 7 },
-    "chan_FSK"      : { "chan_rx_freq": 869100000, "bandwidth": 125000, "bit_rate": 50000 }
-}],
-</code>
-<fc #4682b4>**Step 3**</fc><fc #4682b4> - Update the JSON configuration file with correct parameters for radio frequencies.</fc>
-\\
-==== Antennas configuration ====
-To understand all antennas configuration possibilities read the chapter 4.6.2.4 of the Installation manual.
-  * Enable fields are used to enable or disable emission and reception of the antennas. In case you only have one antenna, disable both these values for one antenna :
-      * ''rx_enable''
-      * ''tx_enable''
-  * The following fields are used to calibrate the antennas. These values are overwritten by the ''local.json''. No need to change them.
-      * ''tx_lut''
-      * ''rssi_offset''
-      * ''rssi_offset_coeff_a''
-      * ''rssi_offset_coeff_b''
-<code>
-"rf_chain_conf":[
-        {
-            "rx_enable": true,
-            "tx_enable": true,
-            "rssi_offset": -202.5,
-            "rssi_offset_coeff_a": 20,
-            "rssi_offset_coeff_b": 2925,
-            "tx_lut":[
-                { "rf_power":  2, "fpga_dig_ ...
-                 ...
-                 ...                            }]
-        },{
-            "rx_enable": true,
-            "tx_enable": true,
-            "rssi_offset": -202.5,
-            "rssi_offset_coeff_a": 20,
-            "rssi_offset_coeff_b": 2925,
-            "tx_lut":[
-                { "rf_power": ...
-                 ...
-                 ...                          }]
-        }],
-</code>
-<fc #4682b4>**Step 4**</fc><fc #4682b4> - Update the JSON configuration file with correct parameters for antennas.</fc>
-\\
-==== Listen Before Talk configuration ====
-Listen Before Talk (LBT) is a technique used in radiocommunications whereby a radio transmitter first senses its radio environment before starting a transmission.
-This feature is mandatory in a few countries (such as Japan and Korea).
-''enable'': Enable or disable LBT.
-''rssi_target'': The RSSI threshold to detect if channel is busy or not (dBm).
-''rssi_shift'':** Do not change this value**, this is the value to be applied to RSSI to convert RSSI in dBm to register value.
-''freq_hz'': The LBT channel frequency in Hz. These frequencies needs to be the same as the one in the ''SX1301_conf'' array.
-<note important>
-By default the frequencies of these channels are different from the one in the ''SX1301_conf'' array. Make sure to change them.
-</note>
-''scan_time_us'': The LBT channel scan time to be used (only two available values: 128µs or 5ms).
-<code>
-"lbt_conf":{
-            "enable": true,
-            "rssi_target": -80, /* dBm */
-            "rssi_shift": 142,
-            "chan_cfg":[ /* 16 channels maximum */
-                { "freq_hz": 920600000, "scan_time_us": 5000 },
-                { "freq_hz": 920800000, "scan_time_us": 5000 },
-                { "freq_hz": 921000000, "scan_time_us": 5000 },
-                { "freq_hz": 921200000, "scan_time_us": 5000 },
-                { "freq_hz": 921400000, "scan_time_us": 5000 },
-                { "freq_hz": 921600000, "scan_time_us": 5000 },
-                { "freq_hz": 921800000, "scan_time_us": 5000 },
-                { "freq_hz": 923200000, "scan_time_us": 5000 },
-                { "freq_hz": 923400000, "scan_time_us": 5000 }
-            ]
-        },
-</code>
-<fc #4682b4>**Step 5**</fc><fc #4682b4> - Update the JSON configuration file with correct parameters for LBT.</fc>
-==== Gateway configuration ====
-  * ''server_address'' : Is the address of the server to which the packets will be forwarded.
-  * The following fields describe the ports used by the packet forwarder to communicate with the LoRa server
-       * ''serv_port_up''.
-       * ''serv_port_down''.
-  * ''stat_interval'': Is the period (in seconds) at which the statistics of the packet forwarder are logged.
-  * The following fields are Boolean that defines whether invalids packets should be forwarded to the server or not :
-       * ''forward_crc_valid''.
-       * ''forward_crc_error''.
-       * ''forward_crc_disabled''.
-  * ''keepalive_interval'': Is the period (in seconds) at which the packet forwarder will send a PUSH_DATA frame to the server.
-  * ''link_mote'': Is a field to observe debug mote's information.
-<code>
-  "gateway_conf": {
-    "gateway_ID": "00AEAEFFFE000000",
-    "server_address": "iotbeta.semtech.com",
-    "serv_port_up": 1690,
-    "serv_port_down": 1690,
-    "keepalive_interval": 10,
-    "stat_interval": 30,
-    "push_timeout_ms": 100,
-    "forward_crc_valid": true,
-    "forward_crc_error": false,
-    "forward_crc_disabled": false,
-    "link_mote": "00CC01AF"
-  },
-</code>
-<fc #4682b4>**Step 6**</fc><fc #4682b4> - Update the JSON configuration file with correct parameters for the gateway.</fc>
-\\
-=== Configuration example - Semtech's LoRa demonstrator: gateway configuration ===
-Send the following shell commands (debug probe or SSH connection) to configure the packet forwarder to work with the Semtech's LoRa Demonstrator LoRaWAN server [[http://iot.semtech.com]]:
-''<config_file>'' is the JSON file you have already defined to work on your gateway according to the [[wiki:loraloc_spf-4.0.0#json_filesinformations_and_behaviour | First step]].
-<code>
-sed -r -i -e "s;(\"server_address\":\ ).*$;\1\"iot.semtech.com\",;" /user/spf2/etc/<config_file>
-sed -r -i -e "s;(\"serv_port_up\":\ ).*$;\11690,;" /user/spf2/etc/<config_file>
-sed -r -i -e "s;(\"serv_port_down\":\ ).*$;\11690,;" /user/spf2/etc/<config_file>
-monit restart spf2
-</code>
-The initialization scripts installed on the gateway will open the firewall ports to allow the packet forwarder to communicate with the Semtech's LoRaWAN server.
-\\ \\
-===== Monitoring and maintenance =====
-==== Starting and stopping the packet forwarder ====
-<note warning>
-The Semtech's packet forwarder (process "spf2") will be restarted in loop until the access to the LoRaWAN server is correct.
-</note>
-=== Monit process ===
-Use the ''Monit'' process start or stop the packet forwarder.
-''Monit <start | stop | restart> <service>''
-  * Check whether packet forwarder process is present or not
-  * <code> ps ww | grep spf2 </code>
-  * If packet forwarder is not launched :
-  * <code>monit start spf2</code>
-  * If packet forwarder is launched :
-  * <code>monit stop spf2</code>
-  * Restart the packet forwarder :
-  * <code>monit restart spf2</code>
-\\
-==== Process and resources monitoring ====
-Once the packet forwarder is configured its status can be checked using ps command.
-<code>
-root     13220 S    /usr/bin/monit -c /etc/monitrc
-root      2744 S    {start_getty} /bin/sh /bin/start_getty 115200 ttymxc0
-root      2976 S    -sh
-root      2596 S    /sbin/watchdog -t 30 /dev/watchdog
-root      2740 S    {execute_spf2.sh} /bin/sh -e /user/spf2/bin/execute_spf2.sh
-root     52136 S    /user/spf2/bin/spf2 -g /dev/nmea1 -y
-root      2964 S    logger -p local1.notice -t spf2
-</code>
-For more detailed information with ''monit'' these commands can be used :
-<code>
-# monit -v : Gives basic information on the SPF2 process
-# ======================================================
-monit -v | grep -A 2 spf2
-Process Name          = spf2
- Pid file             = /var/run/packet_forwarder.pid
- Monitoring mode      = active
---
- Start program        = '/user/spf2/bin/execute_spf2.sh' timeout 30 s
- Stop program         = '/usr/bin/killall -q spf2' timeout 30 s
- Existence            = if does not exist then restart
-# monit status : Gives informations about resources consumption, pid files and monitoring status.
-# ===============================================================================================
-monit status | grep -A 18 spf2
-Process 'spf2'
-  status                       Running
-  monitoring status            Monitored
-  monitoring mode              active
-  on reboot                    nostart
-  pid                          1028
-  parent pid                   1026
-  uid                          0
-  effective uid                0
-  gid                          0
-  uptime                       13m
-  threads                      7
-  children                     0
-  cpu                          0.8%
-  cpu total                    0.8%
-  memory                       0.8% [1.9 MB]
-  memory total                 0.8% [1.9 MB]
-  data collected               Tue, 04 Jul 2017 07:42:59
-</code>
-\\
-==== Log monitoring ====
-__Location__ : ''/user/spf2/var/log''
-{{:wiki:log.png|}}
-While deploying packet forwarder on the Wirnet™ iBTS, the package installer configures syslogd to manage SPF logs in the ''/user/spf/var/log'' directory. This folder will contain activity traces of the packet forwarder. A logrotate feature is used to limit disk space used :
-  * maximum files : ''10''.
-  * maximum size per file : ''200Kb''.
-  * most recent file : ''spf2.log''
-  * less recent file : ''spf2.log.9''
-To survey the log files:
-<code>
-tail -f /user/spf2/var/log/spf2.log
-</code>
-\\
-==== Uninstall the packet forwarder ====
-Opkg packages (.ipk) can be removed thanks to dedicated procedure:
-[[wiki:sw_updates#package_removal|Software updates:package removal]].
-\\ \\
-===== Fine Timestamp decoding =====
-==== General informations ====
-Fine timestamps are the nanosecond accurate dates at which a packet are received by the gateway.
-Fine timestamps are generally used for Geolocalization algorithms.\\
-=== How it works? ===
-  - **//An end-device//** - sends a packet.
-  - **//The Gateway//**
-      * Receives the packet from the end-device.
-      * Retrieve the date at which it received the packet thanks to its GPS chip.
-      * Splits the date (e.g. 2017-10-23 13:37:45 186ms 118µs 527ns) in two parts :
-          * The <fc #cd5c5c>//**classic timestamp**//</fc>: contains second-accurate timestamp (e.g. 2017-10-23 13:37:45).
-          * The <fc #cd5c5c>//**nanosecond number**//</fc>: is the number of nanosecond elapsed since the <fc #cd5c5c>//**classic timestamp**//</fc>  (e.g. 186118527).
-      * Encrypts the <fc #cd5c5c>//**nanosecond number**//</fc> with an hardcoded AES key.
-  - **//The Packet Forwarder//**
-      * Retrieves the <fc #cd5c5c>//**classic timestamp**//</fc> and the <fc #cd5c5c>//**nanosecond number**//</fc>.
-      * Sends them to the LNS.
-  - **//The LNS//**
-      * Decrypts the <fc #cd5c5c>//**nanosecond number**//</fc>.
-      * Sums the <fc #cd5c5c>//**nanosecond number**//</fc> with the <fc #cd5c5c>//**classic timestamp**//</fc>.
-{{ :images:ftimestmp_scheme.png |}}
-\\ \\
-==== Requirements ====
-=== Obtaining the AES key(s) ===
-<fc #4682b4>**Step 1** - Retrieve the FPGA identifier(s).</fc>
-     * Connect to your Wirnet™ iBTS gateway.
-     * Type the following command: ''cat /tmp/sys_startup_status.json | grep "fpga_cid"''.
-     * This will display an output: ''"fpga_cid": "0x00F14086286FFF07",''.
-<fc #4682b4>**Step 2** - Contact Semtech and provide them the ''fpga_cid'' of each loraloc module (up to 4 ''fpga _cid'', depending on the product).</fc>
-{{ :images:products.png |}}
-=== GPS fix ===
-The GPS is used by the gateway to retrieve fine timestamps.
-GPS synchronization (Fix) can be monitored through NMEA frames and especially $GNGGA frames.
-command: ''cat/dev/nmea2'' \\
-parameters:
-  * 7th field - ''GPS fix'' 0=no fix, <fc #008000>**1**</fc>=fix GPS.
-  * 8th field - ''Connected satellites'' number of connected satellites.
-'' $GNGGA,132911.00,4809.08287,N,00135.18250,W,<fc #008000>**1**</fc>,04,4.47,96.1,M,47.7,M,,*69 ''
-A GPS fix value equal to ''1'' is required to use the fine timestamp feature.\\
-If Fix value is not equal to one, the following error will be displayed in the packet forwarder: \\
-''ERROR: [BRD0] timestamp is out of range!''.
-\\ \\
-==== Decyphering ====
-== JSON Message ==
-The packet received by the gateway is sent to the LNS in a JSON array as below:
-<code>
-[2017-10-23 15:38:13.439] [1508765865700627] JSON up [1] [CDC6]:
-{"rxpk":
-     [{"tmst":64679556,
-     "time":"2017-10-23T13:37:45.570488Z",
-     "brd":0,
-     "aesk":0,
-     "freq":868.100000,
-     "stat":1,
-     "modu":"LORA",
-     "datr":"SF12BW125",
-     "codr":"4/5",
-     "size":30,
-     "data":"gFr/ADAAGAIB3Z7VMLH56+YXOwKjMNBjojD0hj3D",
-     "rsig":[{
-          "ant":1,
-          "chan":21,
-          "rssic":-112,
-          "lsnr":-14.0,
-          "etime":"7xkP+6rs/F/Y845JaB5pnQ==",
-          "ftime":186118527,
-          "ft2d":-323,
-          "rfbsb":100,
-          "rs2s1":93,
-          "rssis":-127,
-          "rssisd":0,
-          "foff":-2091
-          }]
-     }]
-}
-</code>
-  * ''time'': <fc #cd5c5c>//**classic timestamp**//</fc>: ''"time":2017-10-23T13:37:45.570488Z''.
-  * ''etime'': <fc #cd5c5c>//**nanosecond number**//</fc> - **e**ncrypted **time**. ''"etime":"7xkP+6rs/F/Y845JaB5pnQ=="''.
-  * ''ftime'': decrypted <fc #cd5c5c>//**nanosecond number**//</fc>, this field is used for debug purposes. ''"ftime":"186118527"''.
-<note>the ''etime'' field can sometimes be missing due to a loss of GPS signal.</note>
-\\ \\
-=== Security key ===
-The AES Key provided by semtech is used to decypher the ''etime'' field.
-AES key:
-  * Algorithm: AES-ECB.
-  * Key length: 128 Bits.
-=== Decypher the data ===
-The timestamp is decyphered by the **Application server** of the LNS.\\
-Hereunder is an example of script that decrypts the <fc #cd5c5c>//**nanosecond number**//</fc> using OpenSSL.
-This example is presented as is. It is not written to cover every possible exception. It is up to the user to adapt it to its needs.
-<note important>
-To avoid an issue due to the ''nopad'' parameter in the script, use ''OpenSSL 1.1.0g 25 May 2017'' or greater. \\
-To check the version : ''OpenSSL version''.
-</note>
-The ''etime field'' is an hexadecimal value which has been base 64 encoded.
-There are 32 clock ticks each nanosecond. Therefore, to retrieve the number of nanosecond from the ''etime'' value, the value needs to be divided by 32.
-<file bash etime_dec.sh>
-#!/bin/bash
-#checking parameters
-if [[ $# -ne 2 ]];then
-    echo 'Usage : ./etime_dec.sh <etime value> <AES 128-ecb-key>'
-    exit
-fi
-ETIMEFIELD=$1
-AESKEY=$2
-# OpenSSL decyphering (convert from base64 to decimal, decypher, convert from bin to hex, remove trailing '0'
-RESULT=$(echo -n $ETIMEFIELD | base64 -d | openssl enc -d -aes-128-ecb -K $AESKEY -nopad | xxd -u -p | sed 's/^0\+/0x/')
-# Display data
-echo "etime decyphered = $RESULT"
-echo -n "etime real value = "
-printf "%d / 10^9 / 2^5\n" $RESULT | bc -l
-</file>
-=== example ===
-The following is an example of decyphering using the script mentionned above.
-For ''etime'' and ''ftime'' values refer to the previous JSON message:
-  * "etime":"7xkP+6rs/F/Y845JaB5pnQ==".
-  * "ftime":**186118527**.
-<code sh>
-chmod u+x etime_dec.sh
-dos2unix etime_dec.sh
-./etime_dec.sh 7xkP+6rs/F/Y845JaB5pnQ== 5FEAFD3647351BEB423F93CEF14A5DDB
-etime decyphered = 0x162FE2FEE
-etime real value = .18611852743750000000
-</code>
-Note that ''etime'' value and ''ftime'' are the same.
-\\ \\
-==== Debugging====
-In order to check if the application server works properly, its results can be compared to the ''ftime'' fields.
-To activate the ''ftime'' field the AES key provided by Semtech must be defined in the packet forwarder  configuration:
-  * location: ''/usr/spf2/etc/<config.json>''.
-  * field: ''"aes_key": "ABCDEF0123456789ABCDEF0123456789" # Default value''.
-\\ \\
-===== Compilation =====
-\\ \\
-<note tip>
-The pre-compiled packet forwarder spf2 v5.1.0 ( ''packet-forwarder-v2_5.1.0-klk2-5.1.0-klk1_klk_lpbs.ipk'' ) is available in the [[resources:resources_spfv2_v5.1.0|SPF v2 Resource]] wiki page.\\
-</note>
-SPF2 package is an ipk which install SPF2 on the board.\\
-This chapter describes the procedure to compile the packet forwarder and generate the IPK from the source file ''spf2-5.1.0-klk2.tar.gz'', available in the [[resources:resources_spfv2_v5.1.0|SPF v2 Resource]] wiki page.\\
-Procedure hereunder is dedicated to Linux operating systems (32 bits and 64 bits). There is no embedded compiler in Wirnet™ iBTS.
-==== Prerequisites ====
-=== Required packages / tools to build the SPF2: ===
-  * ''build-essential''\\
-  * ''tar''\\
-  * ''opkg-build'' (which can be downloaded from https://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/plain/opkg-build)
-Ensure that these tools are in the ''$PATH''.
-=== Required sources: ===
-  * ''spf2-5.1.0-klk2.tar.gz'' ([[resources:resources_spfv2_v5.1.0|SPFv2 5.1.0 Resources]])\\
-  * ''libloragw2-5.1.0-klk1.tar.gz'' ([[resources:resources_halv2_v5.1.0|HALv2 5.1.0 Resources]]])\\
-=== Required toolchain: ===
-Set up the environment as described in the [[wiki:toolchain|toolchain]] page.
-This build is using 2 sources packages (spf2 and libloragw2). To manage this specifity the ''pkg-config'' utility is used. In order to avoid issues, the toolchain sysroot is not used, please modify the toolchain environment file (use your own toolchain directory):
-<code>
-# cat << EOF >> /opt/toolchains/lpbs/environment-setup-cortexa9hf-neon-poky-linux-gnueabi
-unset PKG_CONFIG_SYSROOT_DIR
-EOF
-</code>
-Source the toolchain environment :
-<code bash>
-source /opt/toolchains/lpbs/environment-setup-cortexa9hf-neon-poky-linux-gnueabi
-</code>
-==== Library ====
-It is necessary to build and install the LoRa HAL in order to build the SPF2:
-  * Extract the sources
-Begin by extracting the sources and change directory (''libloragw2-5.1.0-klk1.tar.gz''
- from [[resources:resources_halv2_v5.1.0|HALv2 5.1.0 Resources]] page):
-<code>
-# tar xzf libloragw2-5.1.0-klk1.tar.gz
-# cd libloragw2-5.1.0-klk1/
-</code>
-  * Configure the build:
-<code>
-# ./configure --host=arm-poky-linux-gnueabi --prefix=/tmp/libloragw2
-checking for...
-...
-configure: creating ./config.status
-config.status: creating ...
-config.status: executing depfiles commands
-</code>
-  * Install the library:
-<code>
-# make install
-...
- /bin/mkdir -p '/tmp/libloragw2/lib'
- /usr/bin/install -c -m 644  libloragw2.a '/tmp/libloragw2/lib'
- ( cd '/tmp/libloragw2/lib' && arm-poky-linux-gnueabi-ranlib libloragw2.a )
- /bin/mkdir -p '/tmp/libloragw2/include'
- /usr/bin/install -c -m 644 libsx1301ar/inc/sx1301ar_hal.h libsx1301ar/inc/sx1301ar_aux.h libsx1301ar/inc/sx1301ar_dsp.h libsx1301ar/inc/sx1301ar_err.h libsx1301ar/inc/sx1301ar_gps.h libsx1301ar/inc/sx1301ar_lbt.h libsx1301ar/inc/sx1301ar_radio.h libsx1301ar/inc/sx1301ar_reg.h i2c_functions/i2c_linuxdev.h spi_functions/spi_linuxdev.h '/tmp/libloragw2/include'
- /bin/mkdir -p '/tmp/libloragw2/lib/pkgconfig'
- /usr/bin/install -c -m 644 libloragw2.pc '/tmp/libloragw2/lib/pkgconfig'
-</code>
-==== Build ====
-  * Extract the sources
-Begin by extracting the sources and change directory (''spf2-5.1.0-klk2.tar.gz'' from [[resources:resources_spfv2_v5.1.0|SPFv2 5.1.0 Resources]] page):
-<code>
-# tar xzf spf2-5.1.0-klk2.tar.gz
-# cd spf2-5.1.0-klk2/
-</code>
-  * Export the path:
-<code>
-# export PKG_CONFIG_PATH=/tmp/libloragw2/lib/pkgconfig
-</code>
-  * Configure the build:
-<code>
-# ./configure --host=arm-poky-linux-gnueabi --prefix=/user/spf2
-checking for...
-...
-checking for LORAGW2... yes
-...
-configure: creating ./config.status
-config.status: creating ...
-config.status: executing depfiles commands
-</code>
-  * Create the ipk package:
-<code>
-# make ipk
-...rm -rf vi
-  GEN      spf2_5.1.0-klk2_5.1.0-klk1_klk_lpbs.ipk
-</code>

Wirnet™ i-series

User Tools

Site Tools

Differences

Page Tools