[zb4osgi-changeset] [scm] ZigBee 4 OSGi repository change: r600 - in /projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL: README zigbee/Makefile.cross
scm-notify at zb4osgi.aaloa.org
scm-notify at zb4osgi.aaloa.org
Wed Jan 16 12:04:22 CET 2013
Author: andrea.ranalli
Date: Wed Jan 16 12:04:22 2013
New Revision: 600
Log:
small changes
Modified:
projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/README
projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/zigbee/Makefile.cross
Modified: projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/README
==============================================================================
--- projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/README (original)
+++ projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/README Wed Jan 16 12:04:22 2013
@@ -1,4 +1,3 @@
-<<<<<<< .mine
Gateway Abstraction Layer (GAL) - A standard ZigBee Gateway Device implementation
Copyright 2008-2013 TELECOM ITALIA S.p.A. - http://www.telecomitalia.it
Part of this computer programs(s) may be used, reproduced, stored in any retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, under the Apache License 2.0 with the implicit approval of TELECOM ITALIA.
@@ -277,301 +276,3 @@
libcurl HTTP option application timeout (in seconds) - Note: for remote connection between GW and IPHA insert a value higher than 1. Set to zero to completely disable caching This is a libcurl setting that the new gateway could not use in case the developer decide to manage the HTTP communication in a different way.
--------------------------------------------------------
txPeriod Select the txPeriod used during the Performance tests Obsolete setting used for performance tests, not needed anymore.
-=======
-Gateway Abstraction Layer (GAL) - A standard ZigBee Gateway Device implementation
-Copyright 2008-2013 TELECOM ITALIA S.p.A. - http://www.telecomitalia.it
-Part of this computer programs(s) may be used, reproduced, stored in any retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, under the Apache License 2.0 with the implicit approval of TELECOM ITALIA.
-
-*****************************
-***** I - Introduction ******
-*****************************
-
-This software is called Gateway Abstraction Layer (GAL), and it implements a standard ZigBee Gateway Device. It is released by TELECOM ITALIA S.p.A. (www.telecomitalia.it) and the code may be used, reproduced, stored in any retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, under the Apache License 2.0 with the implicit approval of TELECOM ITALIA.
-
-The software uses the following open source software developed by 3rd parties:
-- libupnp (current release 1.6.15). This product uses software downloaded at Sourceforge (http://sourceforge.net/projects/pupnp/files/pupnp/libUPnP%201.6.15/libupnp-1.6.15.tar.bz2/download ) licensed under the BSD License.
-- curl (current release 7.27.0). This product uses software developed Sourceforge (http://curl.haxx.se/download/curl-7.27.0.tar.gz) licensed under the MIT License.
-- tinyxml (release 2.5.3). This product uses software developed at Sourceforge (http://sourceforge.net/projects/tinyxml/files/tinyxml/2.5.3/tinyxml_2_5_3.tar.gz/download )licensed under the zlib/libpng License.
-- iniparser (release 3.1). This product uses software developed and licensed under the MIT License, freely downloadable at http://ndevilla.free.fr/iniparser/iniparser-3.1.tar.gz
-
-Also, part of this software is based on the specification provided by the ZigBee Alliance (http://www.zigbee.org), licensed under ZigBee specific license for non-member of the ZigBee Alliance.
-
-License Summary:
- - Apache License 2.0
- - ZigBee Non-Member License
-
-Note: shttpd (release 1.42) is a software downloaded on 2008 from http://sourceforge.net/projects/shttpd/files/shttpd/1.42/shttpd-1.42.tar.gz/download and later on modified by Telecom Italia. The project has been ported to a new project called mongoose (current release 3.1), licensed under the MIT License (but not used by GAL at the moment). The owner of the original project, Sergey Lyubka, has copyrighted the code with "THE BEER-WARE LICENSE" (Revision 42): "Sergey Lyubka wrote this file. As long as you retain this notice you can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return". based on this, the shttpd project modified by Telecom Italia can be distributed together with the GAL's source code.
-
-*****************************
-***** II - References *******
-*****************************
-
-For any information related on the usage and the installation of this code please contact Andrea Ranalli (andrea.ranalli at telecomitalia.it) or Nicola Portinaro (nicola.portinaro at telecomitalia.it).
-
-
-*****************************
-*** III - Installation ******
-*****************************
-
-This short guide will describes how to configure the environment in order to use the GAL using a cygwin environment. However, any other Unix-based system can be used (clearly some steps shall be skipped or slightly edited to fit the target operating system).
-
------ Downloading phase -----
-
-1) Please download the latest version of cygwin from www.cygwin.com, the install it by including all the following packages (please note that the releases are based on Cygwin DLL 1.7.7-1, but more update versions could be available):
-
-automake wrapper (4-10) and 1.11.1-1
-autoconf wrapper (10-1) and 2.68-1
-gcc-g++ 3.4.4-999
-openssl-devel 0.8.8r-1
-libcurl-dlevel 7.19.6-1
-[all their dependencies]
-
-Note: “libcurl-dlevel 7.19.6-1” could be avoid to be installed if we decide to configure and use the local folder 'curl' (it is recommented to use the local folder for linux O.S.)
-
-2) Download the latest release of GAL from the repository (https://svn.aaloa.org/projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL is the currently path available but this could be changed in the future) and copy the whole folder into cygwin's user home folder (or wherever you like).
-
-3) Download the open source software developed by 3rd parties companies:
-- libupnp-1.6.15 - http://sourceforge.net/projects/pupnp/files/pupnp/libUPnP%201.6.15/libupnp-1.6.15.tar.bz2/download
-- curl-7.27.0 - http://curl.haxx.se/download/curl-7.27.0.tar.gz
-- tinyxml-2.5.3 - http://sourceforge.net/projects/tinyxml/files/tinyxml/2.5.3/tinyxml_2_5_3.tar.gz/download
-- iniparser-3.1 - https://github.com/ndevilla/iniparser/archive/master.zip
-
-4) Unpack each of the above files and put them into GAL's subfolders, according to their name. Please be aware to maintain the Makefile.cross file present in each of those subfolders. For the tinyxml folder, please substitute also the makefile file. Finally, just for the iniparser, be aware that the files dictionary.h and iniparser.h has been changed to support the cross compilation for the C++ environment. In particular, the following lines has been added at the beginning and at the end of each file:
-
- #ifdef __cplusplus
- extern "C" {
- #endif
-
- #ifdef __cplusplus
- }
- #endif
-
------ Automatic installation -----
-
-If you're lucky enough and if all the files have been properly downloaded and put in the right folders, starting from the gal root directory and typing the following commands should be enough:
-. setup.bash
-gal_cygwin //here "gal_something" could be typed, depending on your O.S. (please verify it inside the setup.bash file)
-cd linuxgal
-make -f Makefile.cross genmake
-cd ..
-make all
-(make distclean)
-(make all)
-
-The output generated by the previous commands is the gal file, present in linuxgal for debugging, and another gal present in [...]/fs/usr/ti/bin, that has been stripped and that shall be used as executable file for a trial. The macro called 'galfs' brings you where the files has been installed:
-bin -> exe gal
-lib -> librerie
-etc -> config.ini
-
-Please note that:
-- In zigbee/Makefile.cross, the user could set the EMBER_STACK_PROFILE according to the ZigBee or ZigBeePRO stack required
-- To enable/disable the debug, go to linuxgal/Makefile.cross and add/remove the following line in the "config" section:
-
- --enable-debug \ --with-debug-flags=RB:SB:DA:MESSAGE:SA:RESTSERVER:XMLMSGCOMPOSER:GALZB:XMLMSGPARSER
-
------ Manual installation -----
-
-If this is the first time that the GAL has been downloaded, it shall be compiled all the following packages:
- - go to "libupnp" folder and run "make clean" and "make"
- - go to "initparser" folder and run "make clean" and "make"
- - go to "\http\shttpd\src" folder and run "make" (for cygwin type "SSL_VER=0.9.8 make cygwin")
- - go to "tinyxml\src" folder and run "make clean" and "make"
-
-Once those steps are accomplished, you're ready to compile the GAL, focusing on the two main folder, "linuxgal" and "zigbee".
- - linuxgal contains all the main files responsible to compile and execute the gal
- - zigbee contains all the file needed to setup the ZigBee or ZigBeePRO stack
-
-A list of the command that shall be execute is reported below:
-
-export EMBER_STACK_PROFILE=1 //CHOOSE THE EMBER STACK PROFILE: 1=ZigBee or 2=ZigBeePRO
-cd zigbee/
-make clean
-make
-cd ..
-cd linuxgal
-make clean
-aclocal
-autoheader
-automake -a
-autoconf
-./configure --enable-zigbee-pro --with-local-libs=.. --with-upnp-cflags=-I/usr/local/include/upnp --with-upnp-libs=/usr/local/lib OR
-./configure --enable-zigbee-pro --with-local-libs=.. --with-upnp-cflags=-I/usr/local/include/upnp --with-upnp-libs=/usr/local/lib --enable-debug --with-debug-flags=RB:SB:DA:MESSAGE:SA:RESTSERVER:XMLMSGCOMPOSER:GALZB:XMLMSGPARSER
-make
-
-
------ Typical errors -----
-
-Some useful commands that could be used to solve some initial problems are:
-make distclean - It will clean everything and force the execution of configure scripts when 'make all' is issued again
-ldd gal.exe - This is useful to figure out which dll are needed to let the gal work properly and what is still missing
-make -f Makefile.cross clean all install - Command needs to compile after modifies made in "linuxgal" or "zigBee" folders
-
-If some error occurs in "make config" or "make all", this is probably due to the fact that the curl library are not found yet by the GAL (that means they're not compiled yet). To fix this problem, launch again "make config" and "make all" and this second time it should work (alternatively run "make -f Makefile.cross all install" in linuxgal).
-
-The most typical error that a user could encounter is the wrong path for the upnp library so it must be checked first if this library is installed correctly and where it has been placed. Under the linux O.S., for example, a valid path that could be used is:
-./configure --enable-zigbee-pro --with-local-libs=.. --with-upnp-cflags=-I/usr/include/upnp --with-upnp-libs=/usr/lib
-This one will fix issues relater to the wrong position of the upnp library
-Another typical problem is related to the curl library, and for this case a useful path could be:
-./configure --enable-zigbee-pro --with-local-libs=../libs --with-upnp-cflags=-I/usr/include/upnp --with-curl-cflags=-I/usr/include/curl --with-curl-libs=/usr/lib --enable-debug
-Also, if not present, the file libcurl.so under /usr/lib shall be created using a soft link (ln -s libcurl.so.4 libcurl.so)
-
-Finally, when the gal is executed it needs to know the correct path for the upnp library. Two alternative ways to reach this goal are:
- a) use the export command: export LD_LIBRARY_PATH=[...]/trunk/targets/freescale/fs/usr/ti/lib (use the "pwd" command to find the right path...)
- b) copy the whole content of [...]/trunk/targets/freescale/fs/usr/ti/lib in /usr/lib
-
-
-*****************************
-******* IV - Usage **********
-*****************************
-
-The easiest way to run a GAL is by tipying the following path:
-gal.exe -s on -c config.ini 'zigbee:///dev/com9?dongle=ezsp'
-where:
- - gal.exe is the result of the previous step (the compiling phase)
- - config.ini is the file containing precious information regarding the configuration of the ZigBee network (like channel, panId, extendedPanID, security, etc...)
- - 'zigbee:///dev/com9?dongle=ezsp' specify at which port your dondle is installed and that you're using a Ember firmware (called EZSP: Ember ZigBee Serial Protocol)
-
-For the Linux OS the Teleesis dongle could be found using the path 'zigbee:///dev/ttyUSB0?dongle=ezsp'.
-To run a Freescale dongle type ./gal -c config.ini 'zigbee:///dev/ttyUSB0?dongle=freescale'
-To run the GAL using the MicroSD type instead ./gal -c config.ini "zigbee:///dev/com8?dongle=microSD&speed=115200"
-
-
-*****************************
-*** V - Stack firmware ******
-*****************************
-
-Depending on the dongle used, there are different firmware that could be used. In this short tutorial we will describe only where to find the firmware for the Ember/SiliconLabs and Freescale dongles. Other stack vendors are supported as well, but they have not been updated since a while.
-
-a) Freescale
-Freescale released a software called BeeStack, that can be defined as a firmware specifically released for ZigBee dongles.
-First of all it is recommended to download the latest driver of the USB dongle from http://www.ftdichip.com/Drivers/VCP.htm, and then download the Test Tool software (currently at the revision 12) from Freescale’s website). This latter tool will allow the user to test single API and to eventually load a firmware (later on it will be introduced a tool, FlexLoader, released by the company CEDACa gateway/module manufaturer , that will do this job).
-The first thing to do is to open Test Tool, then go to "Communication setting" -> "Add Internal" and specify the COM assigned to the dongle by Windows . Then we shall check at which baud rate the firmware works (generally 115.200), select the correct value and inserting a Length equals to 1. Finally we can connect to the dongle using "View" -> "Command Console". To verify that everything works, we could create for example a ZigBee network inserting those 4 commands:
-• ZTC-CPU_Reset.Request (optional)
-• ZTC-ModeSelect.Request
-• ZTC-WriteExtAddr.Request
-• ZTC-StartNwkEx.Request
-All those commands generate a log with useful “Tx” and “Rx” line that can help us to log and debug what is happening.
-Another important file to get is the official documentation, present in one of the folder of Test Tool, where the developer can get a manual reference that explains how to use the APIs.
-
-To install a new firmware, we need to request to Freescale an updated binary file, since they are periodically update based on different Telecom Italia’s requirement, or just due to bug fixing. However, it is possible that, especially at the beginning, Telecom Italia (or the company CEDAC) will provide that firmware that is typically labeled as “BlackBox_combo_StdSecLinkKey_20120914.bin”. To update a new firmware the tool “FlexLoader” previously just cited needs to be downloaded from CEDACthe hardware manufacturer of the gateway (e.g. CEDAC/FlexGrid). The usage of this tool is quite simple, and here we report some cases:
-• To flash from zero and with a new MacAddress:
-FlexLoader.exe -brd key -prot hw -mac 00:11:22:33:44:55:66:77 myFile.bin
-• To flash a new firmware but maintain the previous Mac Address just launch
-FlexLoader -brd key -prot ztctlc my_binary.bin
-• Finally, if we want to maintain the MacAddress but we want to erase the NotVolatileMemory:
-FlexLoader -brd key -prot ztctlc -nvm erase my_binary.bin
-
-b) Ember/Silicon Labs (EZSP)
-The Ember Company has been recently acquired by Silicon Labs and thus wherever in this document the word “Ember” is found, a probable translation to the new company could be applied. Once registered to the Ember’s support web site, it is possible to download the latest release of the EM260 firmware. In particular, we are looking for the file named “em260-uart-rts-cts-with-serial-bootloader.hex”, present in the subdirectory \em260\build\em260-images of the “Ember-stack-Z3.4.x.x-em260-dev.exe” setup file .
-Finally, we are able to install the EZSP (Ember ZigBee Serial Protocol) firmware into a Telegesis dongle:
-1. Get a Telegesis dongle and connect its SIF port to the Ember Breakout board
-2. Open "InSight Desktop" tool (another tool that you can download from the Ember website) and upload the selected hex file and leave unchecked the option “Include bootloader image in upload”
-3. Set the correct baud rate by open a DOS windows, go to C:\Program Files\Ember\xIDE_EM250\SIF\bin, and launch the following two commands:
-em2xx_patch -sid 192.168.1.10 -Override -Mfg @0080=0x0008 (0x0008 means 19.2kbps)
-em2xx_read -sid 192.168.1.10 -Mfg 0x80 (use to verify that the token has been correctly written)
-where the appropriate speed can be choose selecting one of the following values:
-Value Speed (kbps)
-0x0008 19.2
-0x000A 38.4
-0x000C 57.6
-0x000F 115.2
-0x0010 230.4
-
-Please note that the "sid" option is the IP Address where the Ember Breakout board is located. To find out this parameter go to Insight Desktop and then locate the field "IP address" under the breakout board selected to do this job. Alternatively, it is easier to buy an Insight USB Link and use the following commands:
-cd "C:\Program Files\Ember\InSight USB Link"
-EM2USBLoad.exe -Run -Override em260-uart-xon-xoff-with-serial-bootloader.hex
-EM2USBPatch.exe -Override -Mfg @0080=0x000F
-EM2USBRead.exe -Mfg 0x80
-
-*****************************
-***** VI - Config.ini *******
-*****************************
-
-The current Telecom Italia’s gateway (GAL) has a useful configuration file (config.ini) which is quite important to allow the user/administrator to configure ad hoc settings before to start the gateway . In order to simplify the understanding and settings of all those variables, we will report a description for each of those parameters, followed by an important section that describes in more details what that variable stand for and how/why/if implement it.
-
----------------------------------------------------------
-Variable - Description - Implementation status
----------------------------------------------------------
-Platform Hardware platform desired: integration (0), zsdio/EZSP/Freescale/MicroSD (1) Since the gateway shall support different stack vendors, a variable is probably needed to do some specific calls due to the different internal architectures. Clearly this is a development-specific variable so it could be not inserted.
----------------------------------------------------------
-autostart Autostart the ZigBee network: 0 to disable (it will wait for a StartGatewayDevice command), 1 to enabled This in an important variable useful to automatically call the StartGatewayDevice procedure using the default parameters stored in the configuration file, enabling the gateway to startup without wait any external interaction.
----------------------------------------------------------
-startupMode Three possible scenario to startup the network:
-#0 - StartupSetMode=0x18 (CommissioningMode) AND StartupControlMode=0x00 (Association) --> To be used the first time, when the network is created
-#1 - StartupSetMode=0x00 (use NVM) AND StartupControlMode=0x04 (SilentStart) --> To be used at running time
-#2 - StartupSetMode=0x18 (CommissioningMode) AND StartupControlMode=0x04 (SilentStart) --> To be used for TC Replacement Depending of the stack vendor that will be supported, specific startup settings could be necessary: the user/administrator of the gateway shall have the possibility to decide if startup the network using a brand new ZigBee setting (commissioning mode) or if recycle an existing setting. This second part could differs from the current GAL and thus it shall be considered with attention: all the main ZigBee setting like channel radio, extendedPANId, PANId, DeviceType, etc
shall we stored in a configuration file together with an image file of the current status of the stack vendor’s memory. It shall thus be possible to reused any time a configuration before a crash, using a Not-Volatile-Memory (NVM) if it is supported by the stack, or by “flashing” those setting in a way that the node does not start a new network.
----------------------------------------------------------
-localRegToDAnnce
- Enable a local registration to device announcement events (1 to enable, 0 to disable)
- The new gateway shall have this requirements always enabled so this variable can be eliminated. The target here is to be sure that any time a new node joins the network, an announcement event shall be generated to inform the upper level about this event.
----------------------------------------------------------
-keepAliveThreshold
- Specify how long to wait (in seconds) before to start polling each node to verify if they're still alive ('0' to disable) Please refer to paragraph 7.38.3.
----------------------------------------------------------
-keepAliveNumberOfAttempt
- Once keepAliveThreshold is reached, GAL tries to ping the node for 'keepAliveNumberOfAttempt' before considering it dead Please refer to paragraph 7.38.3.
----------------------------------------------------------
-forcePingTimeout Specify in seconds a timeout before to force the gateway to send a ping (MGMT_LQI_Req) to the nodes (0 to disable) Please refer to paragraph 7.2 8.4.
----------------------------------------------------------
-autoDiscoveryUnknownNodes
- Automatic discovery unknown nodes before sending or after receiving a message (1 to enable, 0 to disable) This is an important feature: every time the gateway receives messages from nodes that has not been yet recognized/included in the neighbors table entry shall be polled in order to find out more information (in particular all those details needed by the gateway to have a valid entry into its database)
----------------------------------------------------------
-gwStatusChanged_DefaultURIListener [Optional] "Callback URI listener" address. It represent the "GW Status Changed event" default URI Listener This is a development-specific variable inserted to inform an external application about the status of the gateway and its possible changes. It is an important feature but it could be implemented using API commands (a registration to this event would be enough)
----------------------------------------------------------
-apscMaxWindowSize
- APS level parameters (required for fragmentation services) This is a variable that solve a specific need (fragmentation) and thus probably needs to be maintained.
----------------------------------------------------------
-apsInterframeDelay APS level parameters (required for fragmentation services) This is a variable that solve a specific need (fragmentation) and thus probably needs to be maintained.
----------------------------------------------------------
-debugEnabled (HTTPServerDL, HTTPSessionContextDL, RESTClientDL, RESTBrokerDL, DiscoveryAgentDL, ManagementAgentDL, LocalNodeDL) To enable debug messages select "1" (0 to disable)
-Printing levels for class debugging - 0 (DEBUGGING), 1 (TEST), 3 (PRODUCTION) This is a typical variable used for debugging purpose: it allows the developer to decide what to print and which specific classes to enable. The current gateway has 3 different debug levels, but at the end only two of them are mainly used.
----------------------------------------------------------
-DeviceType Device Type (0 =Current device type; 1=Coordinator; 2=Router; 3=End Device) Fundamental setting to decide if the gateway shall be a coordinator or router (end device is not a standard setting anymore)
----------------------------------------------------------
-ChannelMask Default Channel Mask [valid range: 11 - 26] ZigBee channel mask: an optional feature could be to insert a mask or an “OR” symbol to allow multiple channel choice, useful in case we are a router able to join any channel or a coordinator that shall create a network where the noise is the lowest.
----------------------------------------------------------
-PANId ZigBee Network PANId ('0xFFFF' = generate random value) Typical ZigBee setting (optionally it could be generated randomly)
----------------------------------------------------------
-ExtendedPANId Extended PAN Id (big-endian order) Typical ZigBee setting (optionally it could be generated randomly)
----------------------------------------------------------
-StartUpControl StartupControl (0=Association; 1=Orphan Rejoin; 2=Network Rejoin; 3=Find and Rejoin; 4=Silent Start) Typical ZigBee setting
----------------------------------------------------------
-SecurityLevel SecurityLevel (0=Disabled, 5=Enabled) This variable is not needed anymore since all the ZigBee PRO stack shall mandatory support the security
----------------------------------------------------------
-freescaleMACAddressValue MAC Address mode: 0=use manufacture address (stored within the dongle), 1= generate random address Any gateway shall be produced with a specific and not-editable IEEE Address, but if the stack vendor allows changing it this setting could be used.
----------------------------------------------------------
-networkKey Default Network Key Typical ZigBee setting (optionally it could be generated randomly)
----------------------------------------------------------
-preconfiguredLinkKey Default Trust Center Link Key - 'ZigBeeAlliance09' Typical ZigBee setting (optionally it could be generated randomly)
----------------------------------------------------------
-DefaultEndPoint Default End Point This setting shall be expanded. In ZigBee an endpoint is linked with a SimpleDescriptor and thus this part shall be changed so that the user can specify the default simple descriptor to be used.
----------------------------------------------------------
-TCKeyTableSize (IEEEAddressXX, TCLinkKeyXX) TCKeyTableSize - Zero to disable the TrustCenterLinkKeytable - Note: maximum number of entries is 12 for Ember, 9 for Freescale Typical ZigBee setting. If the gateway is a coordinator, this feature gives the possibility to specify special security requirements for ad hoc nodes.
----------------------------------------------------------
-IEEE_ADDRESS Insert the Trust Center IEEE Address Trust Center setting that could be reviewed.
----------------------------------------------------------
-JOINREQUESTPROCESSING Decide if the local ACL Conf shall be used (INSERT true) or if the WSN-C access is required (INSERT false) Trust Center setting that could be reviewed.
----------------------------------------------------------
-LEAVENOTIFICATIONPROCESSING Decide if process locally the leave notifications without warning the WSN-C (SELECT true). Otherwise insert false Trust Center setting that could be reviewed.
----------------------------------------------------------
-ACLFILENAME File name containing the Access Control List Trust Center setting that could be reviewed.
----------------------------------------------------------
-NETWORKKEY The network master key, 16-bytes long Trust Center setting that could be reviewed.
----------------------------------------------------------
-APPSECURITYTIMEOUTPERIOD The Security Timeout period (expressed in milliseconds) Trust Center setting that could be reviewed.
----------------------------------------------------------
-UseDefaultNWKRootURI Decide if the Network Root URI can be obtained by appending the net/default' suffix (SELECT 1), or by appending the net/<ExtendedPANId>' suffix (SELECT 0) This setting could be avoided (unless it is required to certify a gateway device as standard) and keep by default the “/net/default” path since so far the gateway has been thought to be used only for one network at time.
----------------------------------------------------------
-HelloMsgNotifyPeriod, HelloMsg_WSNCAttached_NotifyPeriod
- Gateway Descriptor Asynchronous notification period (expressed in seconds), respectively before and after a WSN-C is attached. Note: This is like an "Hello" message to the WSN-C platform address This is an obsolete setting that could be implemented into a new API to periodically inform an application (registered to this event) about the status of the gateway. See also ‘gwStatusChanged_DefaultURIListener’ since this is a similar feature that could be implemented in a unique API.
----------------------------------------------------------
-serverPorts Port server where to receive REST commands This is an important setting since it specifies where the gateway expects to receive REST commands.
----------------------------------------------------------
-Ssl, sslCertFile, httpDigestAuth, httpDigestAuthPwdFile RESTServer parameters
- Development-specific settings that depending on the new architecture could be avoided to be inserted.
----------------------------------------------------------
-httpOptTimeout
- libcurl HTTP option application timeout (in seconds) - Note: for remote connection between GW and IPHA insert a value higher than 1. Set to zero to completely disable caching This is a libcurl setting that the new gateway could not use in case the developer decide to manage the HTTP communication in a different way.
---------------------------------------------------------
-txPeriod Select the txPeriod used during the Performance tests Obsolete setting used for performance tests, not needed anymore.
->>>>>>> .r598
Modified: projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/zigbee/Makefile.cross
==============================================================================
--- projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/zigbee/Makefile.cross (original)
+++ projects/zb4osgi/sandbox/telecomItalia/initialContribution/GAL/zigbee/Makefile.cross Wed Jan 16 12:04:22 2013
@@ -1,6 +1,6 @@
include ../Makefile.rules
-export BUILD_EZSP=Y
+#export BUILD_EZSP=Y
export BUILD_FREESCALE=y
# to chose to be compatible with ZigBee 2006, otherwise Zigbee 2004
More information about the Commit
mailing list