FAQ - Revision history

Dvdakker: /* How can I flash/erase the LoRa device ? */

2020-01-20T06:54:11Z

How can I flash/erase the LoRa device ?

← Older revision		Revision as of 06:54, 20 January 2020
Line 102:		Line 102:
	This script is invoked as follows:		This script is invoked as follows:

	<code>flash_lora <~~elf~~-file></code>		<code>flash_lora <bin-file></code>
	Where:		Where:
	* <code><~~elf~~-file></code> is the ~~ELF~~-image to flash to the device.		* <code><bin-file></code> is the BIN-image to flash to the device.

	Likewise, the <code>erase_lora</code> script can be used to erase the 'LoRa-'device. This script is invoked in exactly the same way as the <code>flash_lora</code> script, except that no ~~ELF~~-image file is specified.		'''Important''': the image needs to be in ''binary'' format (and not ELF).

			Likewise, the <code>erase_lora</code> script can be used to erase the 'LoRa-'device. This script is invoked in exactly the same way as the <code>flash_lora</code> script, except that no BIN-image file is specified.

	If you are not using one of the 'CoT'-images, you first need to install the '''[https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack J-Link Software And Documentation Pack]''' for your specific operating system. Once this package is installed you can add the <code>flash_lora</code> and <code>erase_lora</code> scripts to your image to make flashing and erasing the device a bit easier. These scripts can be found in the <code>/usr/local/bin</code> directory in any of the 'CoT' disk images.		If you are not using one of the 'CoT'-images, you first need to install the '''[https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack J-Link Software And Documentation Pack]''' for your specific operating system. Once this package is installed you can add the <code>flash_lora</code> and <code>erase_lora</code> scripts to your image to make flashing and erasing the device a bit easier. These scripts can be found in the <code>/usr/local/bin</code> directory in any of the 'CoT' disk images.

Dvdakker: /* How can I flash/erase the LoRa device ? */

2020-01-20T06:33:10Z

How can I flash/erase the LoRa device ?

← Older revision		Revision as of 06:33, 20 January 2020
Line 96:		Line 96:
	=== How can I flash/erase the LoRa device ? ===		=== How can I flash/erase the LoRa device ? ===

	The 'LoRa' device is basically a Giant Gecko [https://www.silabs.com/products/development-tools/mcu/32-bit/efm32-giant-gecko-starter-kit starter kit] equipped with an RFM95W LoRa module. (See [Node Specifications]). This module is equipped with an on-board [https://www.segger.com/products/debug-probes/j-link/ J-Link debugger], so debugging/programming/erasing this board is done in exactly the same way as it is for any other SiLabs MCU. (See [https://www.silabs.com/support/getting-started/microcontrollers/efm32-mcu here] for the offical 'Getting Started' guides.		The 'LoRa' device is basically a Giant Gecko [https://www.silabs.com/products/development-tools/mcu/32-bit/efm32-giant-gecko-starter-kit starter kit] equipped with an RFM95W LoRa module. (See [[Node Specifications]]). This module is equipped with an on-board [https://www.segger.com/products/debug-probes/j-link/ J-Link debugger], so debugging/programming/erasing this board is done in exactly the same way as it is for any other SiLabs MCU. (See [https://www.silabs.com/support/getting-started/microcontrollers/efm32-mcu here] for the offical 'Getting Started' guides.

	To make things a bit easier, all 'CoT' disk images already contain the necessary J-Link software as well as a few helper scripts.		To make things a bit easier, all 'CoT' disk images already contain the necessary J-Link software as well as a few helper scripts.
Line 102:		Line 102:
	This script is invoked as follows:		This script is invoked as follows:

	<code>flash_lora ~~<device>~~ <elf-file></code>		<code>flash_lora <elf-file></code>
	Where:		Where:
	* <code><elf-file></code> is the ELF-image to flash to the device.		* <code><elf-file></code> is the ELF-image to flash to the device.

Dvdakker: /* I have another JFed related question */

2018-05-09T10:40:46Z

I have another JFed related question

← Older revision		Revision as of 10:40, 9 May 2018
Line 40:		Line 40:
	See: [http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html]		See: [http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html]

	=== I have another JFed related question ===		=== I have another JFed-related question ===

	Take a look at the [http://doc.ilabt.iminds.be/jfed-documentation-5.9/ JFed documentation]. It's quite extensive and should answer most of your questions.		Take a look at the [http://doc.ilabt.iminds.be/jfed-documentation-5.9/ JFed documentation]. It's quite extensive and should answer most of your questions.

Dvdakker: /* Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? */

2018-05-09T10:40:06Z

Can I create an L2 (Ethernet) link between two CityLab testbed nodes ?

← Older revision		Revision as of 10:40, 9 May 2018
Line 22:		Line 22:
	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

	Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel). Please note however that this will only work if you are using one of the provided 'CoT' disk images (see [[Disk Images]]). More information can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]] ~~for more information~~.		Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel). Please note however that this will only work if you are using one of the provided 'CoT' disk images (see [[Disk Images]]). More information can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]].

	=== Can I create a native Ethernet link between two CityLab testbed nodes ? ===		=== Can I create a native Ethernet link between two CityLab testbed nodes ? ===

Dvdakker: /* When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work */

2018-05-09T10:39:47Z

When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work

← Older revision		Revision as of 10:39, 9 May 2018
Line 16:		Line 16:
	=== When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work ===		=== When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work ===

	At this point, the CityLab Testbed ''only'' supports ''gre-tunnel'' and ''egre-tunnel'' links between nodes. Starting from JFed 5.9, the ''gre-tunnel'' link type is automatically selected for you but this is not the case for older versions of JFed GUI. In that case you need to set the link type manually. More information on how to do this can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]]		At this point, the CityLab Testbed ''only'' supports ''gre-tunnel'' and ''egre-tunnel'' links between nodes. Moreover, the ''egre-tunnel'' link type only works with the 'CoT' disk images ([[GRE_Tunnels#EGRE-tunnels only work with 'CoT' disk images\| more information]] here).

			Starting from JFed 5.9, the ''gre-tunnel'' link type is automatically selected for you but this is not the case for older versions of JFed GUI. In that case you need to set the link type manually. More information on how to do this can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]]

	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

Dvdakker: /* Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? */

2018-05-07T14:42:44Z

Can I create an L2 (Ethernet) link between two CityLab testbed nodes ?

← Older revision		Revision as of 14:42, 7 May 2018
Line 20:		Line 20:
	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

	Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel). ~~See~~ [[GRE Tunnels#Creating Links between nodes through the JFed interface\|~~this page~~]] for more information.		Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel). Please note however that this will only work if you are using one of the provided 'CoT' disk images (see [[Disk Images]]). More information can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]] for more information.

	=== Can I create a native Ethernet link between two CityLab testbed nodes ? ===		=== Can I create a native Ethernet link between two CityLab testbed nodes ? ===

Dvdakker: /* Testbed Usage */

2018-05-07T13:44:54Z

Testbed Usage

← Older revision		Revision as of 13:44, 7 May 2018
Line 20:		Line 20:
	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

	Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel).		Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel). See [[GRE Tunnels#Creating Links between nodes through the JFed interface\|this page]] for more information.

			=== Can I create a native Ethernet link between two CityLab testbed nodes ? ===

			Not at this point, but it is on the TODO list.

	=== Why do I get a 'network connection' error when I try to start a test ? ===		=== Why do I get a 'network connection' error when I try to start a test ? ===

Dvdakker: /* Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? */

2018-05-07T13:42:51Z

Can I create an L2 (Ethernet) link between two CityLab testbed nodes ?

← Older revision		Revision as of 13:42, 7 May 2018
Line 20:		Line 20:
	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

	Yes, ~~but unfortunately it is not yet possible~~ to ~~do this through the~~ JFed ~~interface. Check the [[~~GRE ~~Tunnels#Manually setting up EGRE~~-~~tunnels\|~~GRE ~~Tunnels]] page for more information on how to do this once the test has started~~.		Yes, you can. Set the type of your link to ''egre-tunnel'' in JFed and an Ethernet-in-IP GRE tunnel will be automatically created (instead of an IP-in-IP GRE tunnel).

	=== Why do I get a 'network connection' error when I try to start a test ? ===		=== Why do I get a 'network connection' error when I try to start a test ? ===

Dvdakker: /* When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work */

2018-05-07T13:40:35Z

When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work

← Older revision		Revision as of 13:40, 7 May 2018
Line 16:		Line 16:
	=== When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work ===		=== When I create links between two nodes in the CityLab testbed in the JFed interface I either get an error or the link doesn't work ===

	At this point, the CityLab Testbed ''only'' supports ''gre-tunnel'' links between nodes. Starting from JFed 5.9, the ~~correct~~ link type is automatically selected for you but this is not the case for older versions of JFed GUI. In that case you need to set the link type manually ~~to 'gre-tunnel'~~. More information on how to do this can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]]		At this point, the CityLab Testbed ''only'' supports ''gre-tunnel'' and ''egre-tunnel'' links between nodes. Starting from JFed 5.9, the ''gre-tunnel'' link type is automatically selected for you but this is not the case for older versions of JFed GUI. In that case you need to set the link type manually. More information on how to do this can be found [[GRE Tunnels#Creating Links between nodes through the JFed interface\|here]]

	=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===		=== Can I create an L2 (Ethernet) link between two CityLab testbed nodes ? ===

Dvdakker: /* Testbed Usage */

2018-05-03T12:07:02Z

Testbed Usage

← Older revision		Revision as of 12:07, 3 May 2018
Line 29:		Line 29:

	Under normal circumstances this should not be required. All nodes have a public IPv4 and IPv6 address and inbound SSH-connections are allowed by our firewall. The only reason you may have to enable the ''JFed SSH Proxy'' is if your host network blocks outgoing SSH-connections to the CityLab nodes.		Under normal circumstances this should not be required. All nodes have a public IPv4 and IPv6 address and inbound SSH-connections are allowed by our firewall. The only reason you may have to enable the ''JFed SSH Proxy'' is if your host network blocks outgoing SSH-connections to the CityLab nodes.

			=== How can I create a custom disk image ? ===

			See: [http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html http://doc.ilabt.iminds.be/ilabt-documentation/diskimage.html]

	=== I have another JFed related question ===		=== I have another JFed related question ===