Raspberry Pi - Revision history

Leo: /* GPIO */

2021-12-19T01:56:56Z

GPIO

← Older revision		Revision as of 01:56, 19 December 2021
Line 77:		Line 77:

	===GPIO===		===GPIO===
			[[File:Raspberry Pi GPIO Header.png\|alt=Raspberry Pi GPIO pins\|thumb\|453x453px\|Raspberry Pi GPIO pins]]
	GPIO (General Purpose Input/Output) pins can be interfaced using the GPIO Sysfs on the Linux kernel.		GPIO (General Purpose Input/Output) pins can be interfaced using the GPIO Sysfs on the Linux kernel.

Leo: /* Installing a RTC module */

2021-07-08T18:21:35Z

Installing a RTC module

← Older revision		Revision as of 18:21, 8 July 2021
Line 652:		Line 652:
	\|		\|
	\|}		\|}
	Enable i2c through <code>raspi-config</code>~~. Install the~~ <code>~~i2c-tools~~</code> ~~package with~~ <code>~~apt install i2c-tools~~</code>. ~~Then edit~~ <code>/boot/config.txt</code>:		Enable i2c through <code>raspi-config</code> or by editing <code>/boot/config.txt</code> and adding <code>dtparam=i2c_arm=on</code>.

			Enable the appropriate RTC overlay in <code>/boot/config.txt</code> depending on your RTC module.
	{\| class="wikitable"		{\| class="wikitable"
	!Model		!Model
Line 666:		Line 668:
	\|dtoverlay=i2c-rtc,ds3231		\|dtoverlay=i2c-rtc,ds3231
	\|}		\|}
	Reboot the Raspberry Pi. Check if the device is detected by scanning the i2c bus with <code>i2cdetect</code>:		Reboot the Raspberry Pi. Install the <code>i2c-tools</code> package with <code>apt install i2c-tools</code>. Check if the device is detected by scanning the i2c bus with <code>i2cdetect</code>:
	{{Highlight		{{Highlight
	\| code = # i2cdetect -y 1		\| code = # i2cdetect -y 1
Line 694:		Line 696:
	\| lang = terminal		\| lang = terminal
	}}		}}
	~~Finally, remove the fake hwclock package by running apt remove fake-hwclock.~~		Edit <code>/lib/udev/hwclock-set</code> and comment out: {{Highlight

	Edit <code>/lib/udev/hwclock-set</code> and comment out:
	{{Highlight
	\| code = if [ -e /run/systemd/system ] ; then		\| code = if [ -e /run/systemd/system ] ; then
	exit 0		exit 0
Line 709:		Line 708:
	#fi		#fi
	\| lang = text		\| lang = text
	}}		}}Other guides online suggest the uninstallation of fake-hwclock but this is unnecessary. Fake-hwclock basically writes the time to a file (typically <code>/etc/fake-hwclock.data</code>) during shutdown and then restores the time early in the boot process. Keeping the fake hwclock as a fallback option is good in case the RTC is unavailable.

	==Troubleshooting==		==Troubleshooting==

Leo: /* Installing a RTC module */

2021-07-08T04:53:49Z

Installing a RTC module

← Older revision		Revision as of 04:53, 8 July 2021
Line 633:		Line 633:
	*https://raspberrypi.stackexchange.com/questions/77905/raspberry-pi-3-model-b-dtoverlay-gpio-shutdown		*https://raspberrypi.stackexchange.com/questions/77905/raspberry-pi-3-model-b-dtoverlay-gpio-shutdown

	=== Installing a RTC module ===		===Installing a RTC module===
	The very cheap RTC modules that can be found on Ebay for Arduino are typically the DS1302, DS1307, or DS3231. These can be used as a RTC device on the Raspberry Pi, allowing it to retain its time after a reboot and without needing to use NTP.		The very cheap RTC modules that can be found on Ebay for Arduino are typically the DS1302, DS1307, or DS3231. These can be used as a RTC device on the Raspberry Pi, allowing it to retain its time after a reboot and without needing to use NTP.

Line 680:		Line 680:
	\| lang = text		\| lang = text
	}}		}}
	The address 68 should show UU if the kernel is using ~~it as a RTC~~ device. You may now write the time to the RTC with <code>hwclock</code>:		The address 68 should show UU if the kernel has a driver using the device. You can confirm this by looking for the rtc kernel module having been loaded by running <code>lsmod \| grep rtc</code>. With the RTC in place and configured, you may now write the time to the RTC with <code>hwclock</code>:
	{{Highlight		{{Highlight
	\| code = ## If this device has never been set, you will get an error when attempting to read the time:		\| code = ## If this device has never been set, you will get an error when attempting to read the time:

Leo: rtc

2021-07-08T04:50:18Z

rtc

@@ Line 633: / Line 633: @@
 *https://raspberrypi.stackexchange.com/questions/77905/raspberry-pi-3-model-b-dtoverlay-gpio-shutdown
-<br />
+=== Installing a RTC module ===
 ==Troubleshooting==
 ===Wifi on Raspberry Pi 3 B+ stops working===

Leo: /* Miscellaneous */

2021-07-07T00:40:12Z

Miscellaneous

← Older revision		Revision as of 00:40, 7 July 2021
Line 196:		Line 196:

	===Getting Temperature and Voltage===		===Getting Temperature and Voltage===
	To get the SoC temperature, frequency, and voltages:		To get the SoC temperature, frequency, and voltages from <code>vcgencmd</code>. This command has as of 2021 moved from <code>/opt/vc/bin</code> to <code>/usr/bin</code> and might be in your path.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	$ /opt/vc/bin/vcgencmd measure_temp		$ /opt/vc/bin/vcgencmd measure_temp

Leo: /* Raspberry Pi OS (Raspbian) */

2021-07-07T00:36:17Z

Raspberry Pi OS (Raspbian)

← Older revision		Revision as of 00:36, 7 July 2021
Line 55:		Line 55:
	The default username and password is {{code\|pi}} and {{code\|raspberry}}.		The default username and password is {{code\|pi}} and {{code\|raspberry}}.

	To update the default keyboard, edit <code>/etc/default/keyboard</code> or run the <code>~~raspbi~~-config</code> tool.		To update the default keyboard, edit <code>/etc/default/keyboard</code> or run the <code>raspi-config</code> tool.
	===FreeBSD===		===FreeBSD===
	FreeBSD is supported on the Raspberry Pi. See https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi		FreeBSD is supported on the Raspberry Pi. See https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi

Leo: /* Arch Linux */

2020-11-26T17:10:32Z

Arch Linux

← Older revision		Revision as of 17:10, 26 November 2020
Line 6:		Line 6:
	*Raspberry Pi 2: http://archlinuxarm.org/os/ArchLinuxARM-rpi-2-latest.tar.gz		*Raspberry Pi 2: http://archlinuxarm.org/os/ArchLinuxARM-rpi-2-latest.tar.gz
	*Raspberry Pi 3: http://archlinuxarm.org/os/ArchLinuxARM-rpi-3-latest.tar.gz		*Raspberry Pi 3: http://archlinuxarm.org/os/ArchLinuxARM-rpi-3-latest.tar.gz
	*Raspberry Pi 4: http://archlinuxarm.org/os/ArchLinuxARM-rpi-4-latest.tar.gz		*Raspberry Pi 4: http://archlinuxarm.org/os/ArchLinuxARM-rpi-4-latest.tar.gz (32bit) http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-aarch64-latest.tar.gz (64bit)

	With <code>fdisk</code>, setup the two boot and root partitions on your SD card:		With <code>fdisk</code>, setup the two boot and root partitions on your SD card:

	#Boot: ~~100MB~~ (of type <code>c</code>, W95 FAT32 (LBA))		#Boot: 250MB (of type <code>c</code>, W95 FAT32 (LBA))
	#Root: The rest of the capacity for your OS and Data		#Root: The rest of the capacity for your OS and Data

Line 16:		Line 16:
	# fdisk /dev/sdcard		# fdisk /dev/sdcard
	## Set up the SD card partitions		## Set up the SD card partitions
	## Commands are: o, n, p, [enter], +~~100M~~, t, c, n, p, 2, [enter], [enter], w		## Commands are: o, n, p, [enter], +250M, t, c, n, p, 2, [enter], [enter], w
	# mkfs.vfat /dev/sdcard1		# mkfs.vfat /dev/sdcard1
	# mkfs.ext4 /dev/sdcard2		# mkfs.ext4 /dev/sdcard2
Line 590:		Line 590:
	}}		}}

	=== Power Button ===		===Power Button===
	You can load the gpio-shutdown overlay and use two of the GPIO pins to make a power button. Such a power button can be used to safely shutdown the Pi physically.		You can load the gpio-shutdown overlay and use two of the GPIO pins to make a power button. Such a power button can be used to safely shutdown the Pi physically.
	{{Highlight		{{Highlight
Line 630:		Line 630:
	See also:		See also:

	* https://www.instructables.com/Raspberry-Pi-Power-Button/		*https://www.instructables.com/Raspberry-Pi-Power-Button/
	* https://raspberrypi.stackexchange.com/questions/77905/raspberry-pi-3-model-b-dtoverlay-gpio-shutdown		*https://raspberrypi.stackexchange.com/questions/77905/raspberry-pi-3-model-b-dtoverlay-gpio-shutdown

	<br />		<br />

Leo: added raspberry pi power button section

2020-10-14T23:46:22Z

added raspberry pi power button section

@@ Line 590: / Line 590: @@
 }}
-== Troubleshooting ==
+                ACTION!="REMOVE", SUBSYSTEM=="input", KERNEL=="event*", \
-=== Wifi on Raspberry Pi 3 B+ stops working ===
+                        SUBSYSTEMS=="platform", DRIVERS=="gpio-keys", \
 Running OctoPi 0.17.0 on Raspbian Buster (10) over Wifi and it stopped responding after a while.  After plugging in a wired connection and taking a look at the logs, I see:

Leo at 23:48, 11 September 2020

2020-09-11T23:48:18Z

← Older revision		Revision as of 23:48, 11 September 2020
Line 591:		Line 591:


			== Troubleshooting ==
			=== Wifi on Raspberry Pi 3 B+ stops working ===
			Running OctoPi 0.17.0 on Raspbian Buster (10) over Wifi and it stopped responding after a while. After plugging in a wired connection and taking a look at the logs, I see:

			{{highlight\|lang=text\|code=
			[Fri Sep 11 23:31:44 2020] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
			[Sat Sep 12 00:08:00 2020] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
			[Sat Sep 12 00:08:00 2020] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
			[Sat Sep 12 00:29:24 2020] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
			[Sat Sep 12 00:29:27 2020] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
			[Sat Sep 12 00:29:27 2020] brcmfmac: brcmf_cfg80211_disconnect: error (-110)
			[Sat Sep 12 00:29:29 2020] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
			[Sat Sep 12 00:29:32 2020] brcmfmac: brcmf_set_pmk: failed to change PSK in firmware (len=0)
			[Sat Sep 12 00:29:40 2020] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
			[Sat Sep 12 00:29:40 2020] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar returned err = -110
			[Sat Sep 12 00:29:42 2020] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
			[Sat Sep 12 00:29:42 2020] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
			[Sat Sep 12 00:29:42 2020] brcmfmac: power management disabled
			[Sat Sep 12 00:29:45 2020] brcmfmac: brcmf_cfg80211_set_power_mgmt: error (-110)
			[Sat Sep 12 00:29:47 2020] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
			[Sat Sep 12 00:29:50 2020] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
			[Sat Sep 12 00:29:52 2020] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
			[Sat Sep 12 00:29:55 2020] brcmfmac: brcmf_run_escan: error (-110)
			[Sat Sep 12 00:29:55 2020] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
			[Sat Sep 12 00:29:58 2020] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
			}}

			The fix that is suggested is to run <code>rpi-update</code> and update the firmware.

	{{Navbox Linux}}		{{Navbox Linux}}

Leo: /* Miscellaneous */

2020-08-31T06:14:38Z

Miscellaneous

← Older revision		Revision as of 06:14, 31 August 2020
Line 248:		Line 248:
	\|}		\|}

			I have had issues with the Raspberry Pi showing that it has been throttled at least once since power on (0x50000) or is constantly throttled (0x50005) despite having a good power supply. It turns out that not all cables are created equal and most cables in my possession have a high resistance which limits the current that is available to the Raspberry Pi. With the same good power supply, about half of the cables I have resulted in 0x50000 while nearly the other half resulted in 0x50005. Only 2 consistently resulted in the Raspberry Pi receiving sufficient power with no throttled flags being set.

	See Also: https://elinux.org/RPI_vcgencmd_usage		See Also: https://elinux.org/RPI_vcgencmd_usage