Raspberry and ROS - Revision history

Jca: /* Start Raspberry */

2023-07-06T08:43:42Z

Start Raspberry

← Older revision		Revision as of 10:43, 6 July 2023
Line 48:		Line 48:
	TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0		TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


			In this case, the IP4 is 10.197.217.175.

	If you don't get an IP, the wifi may not be set correctly.		If you don't get an IP, the wifi may not be set correctly.

	~~in this case, the IP4 is 10.197.217.175.~~

	=== Wifi connect ===		=== Wifi connect ===

2023-07-06T08:43:21Z

Start Raspberry

← Older revision		Revision as of 10:43, 6 July 2023
Line 50:		Line 50:

	If you don't get an IP, the wifi may not be set correctly.		If you don't get an IP, the wifi may not be set correctly.

			in this case, the IP4 is 10.197.217.175.

	=== Wifi connect ===		=== Wifi connect ===

2023-07-06T08:41:51Z

Start Raspberry

← Older revision		Revision as of 10:41, 6 July 2023
Line 23:		Line 23:

	If everything is configured as above, then you just need to figure out the IP.		If everything is configured as above, then you just need to figure out the IP.
			On a Linux computer, you can find the Raspberry IP address using (if on the same local net):

			sudo apt install net-tools nmap
			nmap -sP 192.168.2.0/24

	else		else

	You need a screen and keyboard.		You need a screen and keyboard.
	~~Connect to the network to get an IP and for updating and date/time.~~

	~~Find your IP address using:~~		Log on to the Raspberry Pi

	~~sudo apt install net-tools nmap~~		$ ifconfig
	~~ifconfig~~		eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
			...
			lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
			...
			wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
			inet 10.197.217.175 netmask 255.255.252.0 broadcast 10.197.219.255
			inet6 fe80::f620:b431:69cc:44f4 prefixlen 64 scopeid 0x20<link>
			ether dc:a6:32:f4:0e:a4 txqueuelen 1000 (Ethernet)
			RX packets 486 bytes 41505 (40.5 KiB)
			RX errors 0 dropped 0 overruns 0 frame 0
			TX packets 421 bytes 43403 (42.3 KiB)
			TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

	~~Or from another computer on the same local net (if your local net is 192.168.2.XX)~~

	~~nmap -sP 192~~.~~168.2.0/24~~		If you don't get an IP, the wifi may not be set correctly.

	=== Wifi connect ===		=== Wifi connect ===

2023-05-16T18:00:11Z

Command line upload to Teensy

← Older revision		Revision as of 20:00, 16 May 2023
Line 314:		Line 314:
	====Command line upload to Teensy====		====Command line upload to Teensy====

	A command line upload utility, that do not use any graphics is available here: https://github.com/PaulStoffregen/teensy_loader_cli		A command line upload utility, that does not use any graphics is available here: https://github.com/PaulStoffregen/teensy_loader_cli .
			This can be an advantage if the Teensy is accessed through SSH.

	I would normally put such utilities in a GIT directory		I would normally put such utilities in a GIT directory

2023-05-16T17:58:24Z

Compile and upload

← Older revision		Revision as of 19:58, 16 May 2023
Line 309:		Line 309:
	''Press the (red) power button on the Regbot board (to maintain power while the processor is reprogrammed)''		''Press the (red) power button on the Regbot board (to maintain power while the processor is reprogrammed)''
	make upload		make upload

			(PS! For drone_ctrl, the code compiles on Raspberry, but the processor fails to start. The same code compiles and runs fine from the PC.)

	====Command line upload to Teensy====		====Command line upload to Teensy====

2023-05-16T17:55:34Z

Command line upload to Teensy

← Older revision		Revision as of 19:55, 16 May 2023
Line 333:		Line 333:
	This makes the command ''teensy_loader_cli'', but it needs to know which processor the HEX code is intended for, so make a script		This makes the command ''teensy_loader_cli'', but it needs to know which processor the HEX code is intended for, so make a script

			cd <directory with compiled HEX code>
			ln -s ~/git/teensy_loader_cli/teensy_loader_cli .
	nano upload.bash		nano upload.bash

Line 338:		Line 340:

	#!/bin/bash		#!/bin/bash
	./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex		~/git/teensy_loader_cli/teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex

	if the HEX code is in ''regbot.hex'' and Teensy is ''4.1'', else modify. See also https://www.pjrc.com/teensy/loader_cli.html for more details.		if the HEX code is in ''regbot.hex'' and Teensy is ''4.1'', else modify. See also https://www.pjrc.com/teensy/loader_cli.html for more details.
Line 345:		Line 347:

	chmod +x upload.bash		chmod +x upload.bash

			And execute when needed (and press button on Teensy, when requested).

			./upload.bash

	=== Initialize the ROS environment ===		=== Initialize the ROS environment ===

2023-05-16T17:40:44Z

Command line upload to Teensy

← Older revision		Revision as of 19:40, 16 May 2023
Line 340:		Line 340:
	./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex		./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex

	if the HEX code is in regbot.hex and Teensy is 4.1, else modify. See also https://www.pjrc.com/teensy/loader_cli.html for more details.		if the HEX code is in ''regbot.hex'' and Teensy is ''4.1'', else modify. See also https://www.pjrc.com/teensy/loader_cli.html for more details.

	Make the new script executable:		Make the new script executable:

2023-05-16T17:40:20Z

Command line upload to Teensy

← Older revision		Revision as of 19:40, 16 May 2023
Line 340:		Line 340:
	./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex		./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex

	if the Teensy is 4.1, else ~~see~~ https://www.pjrc.com/teensy/loader_cli.html for more details.		if the HEX code is in regbot.hex and Teensy is 4.1, else modify. See also https://www.pjrc.com/teensy/loader_cli.html for more details.

	Make the new script executable:		Make the new script executable:

2023-05-16T17:35:16Z

Rename host to match robot

← Older revision		Revision as of 19:35, 16 May 2023
Line 448:		Line 448:
	ln -s /etc/init.d/robobot_rename_test.sh /etc/rc2.d/s99robobot_rename		ln -s /etc/init.d/robobot_rename_test.sh /etc/rc2.d/s99robobot_rename

	The script		The script is then executed when the Raspberry boots, and if the hostname does not match that of the Teensy, then the hostname is modified.

	=== Clone the just installed image ===		=== Clone the just installed image ===

2023-05-16T17:32:38Z

Command line upload to Teensy

← Older revision		Revision as of 19:32, 16 May 2023
Line 331:		Line 331:
	make		make

	This makes the command teensy_loader_cli, but it needs to know which processor the HEX code is intended for, so make a script		This makes the command ''teensy_loader_cli'', but it needs to know which processor the HEX code is intended for, so make a script

	nano upload.bash		nano upload.bash
Line 342:		Line 342:
	if the Teensy is 4.1, else see https://www.pjrc.com/teensy/loader_cli.html for more details.		if the Teensy is 4.1, else see https://www.pjrc.com/teensy/loader_cli.html for more details.

			Make the new script executable:

			chmod +x upload.bash

	=== Initialize the ROS environment ===		=== Initialize the ROS environment ===