Rock3/Ubuntu - Revision history

Naoki at 02:02, 7 February 2023

2023-02-07T02:02:33Z

RadxaYuntian at 03:36, 29 September 2022

2022-09-29T03:36:11Z

Nascs at 03:22, 25 August 2022

2022-08-25T03:22:25Z

Nascs at 03:40, 23 August 2022

2022-08-23T03:40:52Z

Ken: /* UART */

2022-05-13T07:42:09Z

‎UART

Stephen: /* Test RTC Device */

2022-05-08T15:40:23Z

‎Test RTC Device

Stephen: /* Test RTC Device */

2022-05-08T15:38:18Z

‎Test RTC Device

Stephen: /* Test RTC Device */

2022-05-08T15:34:59Z

‎Test RTC Device

Ken: /* Test RTC Device */

2022-05-06T02:40:37Z

‎Test RTC Device

Stephen: /* Common Hardware Interfaces, I2C, PWM, SPI, UART, CAN, etc */

2022-04-24T14:01:20Z

‎Common Hardware Interfaces, I2C, PWM, SPI, UART, CAN, etc

@@ Line 11: / Line 11: @@
 === Introduction to ROCK 3 Ubuntu ===
-This guide is available for official ROCK 3 (ROCK 3 A, Radxa CM3, etc) Ubuntu images.
+This guide is available for official ROCK 3 (ROCK 3A, Radxa CM3, etc) Ubuntu images.
 ROCK 3 Ubuntu server  is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, BT, AI and so on.

@@ Line 13: / Line 13: @@
 This guide is available for official ROCK 3 (ROCK 3 A, Radxa CM3, etc) Ubuntu images.
-ROCK 3 Ubuntu server  is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.
+ROCK 3 Ubuntu server  is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, BT, AI and so on.
 ROCK 3 Ubuntu server uses '''systemd''' to manage system.
@@ Line 557: / Line 557: @@
 * Test WIFI perpormance by tool iperf3.
-=== Bluetooth ===
+=== BT ===
 <div class="bs-example bs-example-tabs">
@@ Line 570: / Line 570: @@
              <div class="tab-pane active" id="3a-bt">
-=== 3A Bluetooth ===
+=== 3A BT ===
 Table of wireless modules supported on ROCK 3A.
@@ Line 639: / Line 639: @@
   root@rock3a:~# apt-get install -y broadcom-wifibt-firmware intel-wifibt-firmware
-Below is the example of testing Broadcom modules bluetooth.
+Below is the example of testing Broadcom modules BT.
-*Check Bluetooth service.
+*Check BT service.
   root@rock3a:~# systemctl status bluetooth
-*Run Bluetooth service if the Bluetooth service is inactive.
+*Run BT service if the BT service is inactive.
   root@rock3a:~# systemctl start bluetooth
-*Check Bluetooth device.
+*Check BT device.
   root@rock3a:~# hciconfig
   hci0:   Type: Primary  Bus: UART
@@ Line 652: / Line 652: @@
          RX bytes:850 acl:0 sco:0 events:58 errors:0
          TX bytes:2814 acl:0 sco:0 commands:58 errors:0
-*Example: Connect to Bluetooth Speaker.
+*Example: Connect to BT Speaker.
 *Install pulseaudio packages.
   root@rock3a:~# apt-get install -y pulseaudio-module-bluetooth pulseaudio
@@ Line 672: / Line 672: @@
              <div id="3b-bt" class="tab-pane">
-=== 3B Bluetooth ===
+=== 3B BT ===
 Table of wireless modules supported on ROCK 3B.
@@ Line 694: / Line 694: @@
             <div id="3c-bt" class="tab-pane">
-==== Bluetooth for ROCK 3C ====
+==== BT for ROCK 3C ====
 Table of wireless modules supported on ROCK 3C.

@@ Line 563: / Line 563: @@
              <li class="active" data-toggle="tab">[http://wiki.radxa.com/Nav_Tabs#3a-bt ROCK 3A]</li>
               <li data-toggle="tab"> [http://wiki.radxa.com/Nav_Tabs#3b-bt ROCK 3B]</li>
              <li data-toggle="tab">[http://wiki.radxa.com/Nav_Tabs#cm3io-bt CM3 IO]</li>
          </ul>
@@ Line 690: / Line 691: @@
              </div>  <!--  id="3b-bt" end-->
              <div id="cm3io-bt" class="tab-pane">

← Older revision		Revision as of 03:40, 23 August 2022
Line 97:		Line 97:

	* ROCK 3A has one 40-pin expansion header. To control them, see [[rock3/hardware/rock3a-gpio \| ROCK 3A GPIO ]].		* ROCK 3A has one 40-pin expansion header. To control them, see [[rock3/hardware/rock3a-gpio \| ROCK 3A GPIO ]].
		+
		+
		+	=== <span id="leds">LEDS </span> ===
		+
		+	<div class="bs-example bs-example-tabs">
		+	<ul id="tabeth" class="nav nav-tabs nav-justified nav-tabs" style="margin:0;">
		+	<li class="active" data-toggle="tab">[http://wiki.radxa.com/Nav_Tabs#leds-3a ROCK 3A]</li>
		+	<li data-toggle="tab"> [http://wiki.radxa.com/Nav_Tabs#leds-3b ROCK 3B]</li>
		+	<li data-toggle="tab"> [http://wiki.radxa.com/Nav_Tabs#leds-3c ROCK 3C]</li>
		+	<li data-toggle="tab">[http://wiki.radxa.com/Nav_Tabs#leds-cm3io CM3 IO]</li>
		+	</ul>
		+	</div>
		+	<div id="tabeth" class="tab-content">
		+
		+	<div class="tab-pane active" id="leds-3a">
		+
		+	</div> <!-- id="leds-3a" end-->
		+
		+	<div id="leds-3b" class="tab-pane">
		+
		+	</div> <!-- id="leds-3b" end-->
		+	<div id="leds-3c" class="tab-pane">
		+	The two leds are configured as LED class devices, you can control them via /sys/class/leds/
		+
		+	Green: Flash twice per second after the kernel booting, it's called heartbeat.
		+
		+	Blue: On when there is power
		+
		+	You can change the behaviour of each LED by using the echo command on their trigger property.
		+	root@rock-3c:/home/rock# echo none > /sys/class/leds/user-led1/trigger
		+	root@rock-3c:/home/rock# echo default-on > /sys/class/leds/user-led1/trigger
		+	root@rock-3c:/home/rock# echo timer > /sys/class/leds/user-led1/trigger
		+	root@rock-3c:/home/rock# echo heartbeat > /sys/class/leds/user-led1/trigger
		+
		+	You can use cat on the trigger property to list all the available values.
		+	root@rock-3c:/home/rock# cat /sys/class/leds/user-led1/trigger
		+	none rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock
		+	kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock mmc1 mmc2 mmc0 timer oneshot disk-activity disk-read disk-write ide-disk mtd
		+	nand-disk [heartbeat] backlight gpio cpu cpu0 cpu1 cpu2 cpu3 activity default-on transient flash torch panic netdev rfkill0 rfkill1
		+
		+
		+	</div> <!-- id="leds-3c" end-->
		+	<div class="tab-pane active" id="leds-cm3io">
		+
		+	</div> <!-- id="leds-cm3io" end-->
		+
		+	</div>
		+

	=== <span id="common_hardware_interface">Common Hardware Interfaces, I2C, PWM, SPI, UART, CAN, etc</span> ===		=== <span id="common_hardware_interface">Common Hardware Interfaces, I2C, PWM, SPI, UART, CAN, etc</span> ===

← Older revision		Revision as of 07:42, 13 May 2022
Line 132:		Line 132:

	==== UART ====		==== UART ====
		+	System default enable uart2-m0 (/dev/ttyS2) to be debug console.
		+
		+	overlays=rk3568-fiq-debugger-uart2m0
		+
		+	If you want to enable uart2-m0 (/dev/ttyS2) to be normal console, modify item "rk3568-uart2-m0" to the "overlays=" line.
		+
		+	overlays=rk3568-uart2-m0

	==== CAN ====		==== CAN ====

@@ Line 169: / Line 169: @@
 ROCK 3A is equipped with one RTC IC hym8563.
-Firstly, plug in [[rock3/hardware/rtc | RTC battery]], power on ROCK 3A.
+Firstly, plug in [[rock3/hardware/rtc | RTC battery]] to give power to RTC IC. Please note that we should keep the RTC battery in the RTC connector.
 And confirm that the rtc hym8563 device is created.
@@ Line 194: / Line 196: @@
 We see that rtc runs about 10 minutes also. That's good.
 ===Test Audio Player===

@@ Line 169: / Line 169: @@
 ROCK 3A is equipped with one RTC IC hym8563.
-Firstly, plug in [[rock3/hardware/rtc | RTC battery]], power on ROCK 3A. And confirm that the rtc hym8563 device is created.
+Firstly, plug in [[rock3/hardware/rtc | RTC battery]], power on ROCK 3A.
   root@rock3a:~# dmesg | grep rtc
@@ Line 184: / Line 186: @@
   root@rock3a:~# poweroff
-and then disconnect the power supply
+and then remove the power adapter.
 Finally, 10 minutes later we power on ROCK 3A via Type-C Port and check the rtc clock.
@@ Line 192: / Line 194: @@
 We see that rtc runs about 10 minutes also. That's good.
 ===Test Audio Player===

@@ Line 170: / Line 170: @@
   root@rock3a:~# dmesg | grep rtc
-  [    0.749597] rk808-rtc rk808-rtc: registered as rtc0
+  [    1.128345] rk808-rtc rk808-rtc: registered as rtc0
-  [    0.751404] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:02 UTC (1501837202)
+  [    1.130163] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:05 UTC (1501837205)
-Secondly, use the following commands to set the system time and synchronize it to rtc.
+Secondly, use the following commands to set the system time and synchronize it to rtc1.
   root@rock3a:~# date -s "2021-08-17 20:00:00"
-  root@rock3a:~# hwclock -w
+  root@rock3a:~# hwclock -w -f /dev/rtc1
-  root@rock3a:~# hwclock -r
+  root@rock3a:~# hwclock -r -f /dev/rtc1
 -08-17 20:00:04.745124+00:00
   root@rock3a:~# poweroff
@@ Line 185: / Line 186: @@
 Finally, 10 minutes later we power on ROCK 3 A via Type-C Port and check the rtc clock.
-  root@rock3a:~# hwclock -r
+  root@rock3a:~# hwclock -r -f /dev/rtc1
 -08-17 20:10:14.745124+00:00

@@ Line 104: / Line 104: @@
 '''Warning: Remember there is only one line including item "overlays=" in file /boot/uEnv.txt.'''
-To enable I2C, PWM, SPI, UART, CAN, etc, please see '''RK3566/RK3568 Available Overlay (ROCK 3A, ROCK 3B, Radxa CM3)''' part of [[Device-tree-overlays | Device Tree Overlays]].
+To enable I2C, PWM, SPI, UART, CAN, etc, please see '''RK3566/RK3568 Available Overlay (ROCK 3A, ROCK 3B, Radxa CM3)''' part of [[rock3/Ubuntu/device-tree-overlays | Device Tree Overlays]].
 <div class="bs-example bs-example-tabs">