Yocto Project Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-rockchip][PATCH] roc-rk3308-cc: add
Date: Wed, 17 Jan 2024 01:13:53 -0500	[thread overview]
Message-ID: <20240117061353.30123-1-twoerner@gmail.com> (raw)

The T-Firefly ROC-RK3308-CC is a miniature and compact main board which is
equipped with a cost-effective RK3308 Core Processor and a high-performance
CODEC.

Features:
- Rockchip RK3308, 64-bit, quad-core, Arm Cortex-A35 processor @ 1.3GHz
- 100M ethernet
- PoE
- USB 2.0 and Type-C (OTG and power)
- 802.11 b/g/n WiFi and Bluetooth 4.2

https://en.t-firefly.com/product/rocrk3308cc

Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 README                                      | 24 +++++++++++----------
 conf/machine/roc-rk3308-cc.conf             | 12 +++++++++++
 recipes-bsp/u-boot/u-boot%.bbappend         |  2 +-
 recipes-kernel/linux/linux-yocto_%.bbappend |  1 +
 4 files changed, 27 insertions(+), 12 deletions(-)
 create mode 100644 conf/machine/roc-rk3308-cc.conf

diff --git a/README b/README
index 48cb952a3b09..80ba592eb812 100644
--- a/README
+++ b/README
@@ -36,6 +36,7 @@ Status of supported boards:
 		rock-pi-s
 		rock-5a
 		roc-rk3328-cc
+		roc-rk3308-cc
 	builds:
 		marsboard-rk3066
 		radxarock
@@ -43,17 +44,18 @@ Status of supported boards:
 
 Notes:
 -----
-	The latest ddr initializer for the rk3308 platform (currently only
-	used by the rock-pi-s machine) does not output diagnostic messages
-	to uart0. This causes a bunch of gibberish to be printed to the
-	console window which only becomes legible once the linux kernel
-	starts. I.e. the console output of the ddr initialization routine,
-	as well as u-boot is lost. An older version of this same binary
-	blob does, however, support output to uart0 (making its diagnostic
-	messages as well as u-boot available on the console). By default
-	the build assumes the user would like to see these message and be
-	able to have the option to interact with u-boot. Iow: for the
-	rock-pi-s an older version of rkbin is used.
+	The latest ddr initializer for the rk3308 platform does not output
+	diagnostic messages to uart0. This causes a bunch of gibberish to
+	be printed to the console window which only becomes legible once
+	the linux kernel starts. I.e. the console output of the ddr
+	initialization routine, as well as u-boot is lost. An older
+	version of this same binary blob does, however, support output to
+	uart0 (making its diagnostic messages as well as u-boot available
+	on the console). By default the build assumes the user would like
+	to see these message and be able to have the option to interact
+	with u-boot.
+
+	IOW: for rk3308-based devices, an older version of rkbin is used.
 
 	If, however, the user would prefer to use the latest binary ddr
 	initializer from rkbin, simply set:
diff --git a/conf/machine/roc-rk3308-cc.conf b/conf/machine/roc-rk3308-cc.conf
new file mode 100644
index 000000000000..839e73c41f06
--- /dev/null
+++ b/conf/machine/roc-rk3308-cc.conf
@@ -0,0 +1,12 @@
+# Copyright (C) 2024  Trevor Woerner
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+#@TYPE: Machine
+#@NAME: roc-rk3308-cc
+#@DESCRIPTION: T-Firefly ROC-RK3308-CC SBC
+#https://en.t-firefly.com/product/rocrk3308cc
+
+require include/rk3308.inc
+
+UBOOT_MACHINE = "roc-cc-rk3308_defconfig"
+KERNEL_DEVICETREE = "rockchip/rk3308-roc-cc.dtb"
diff --git a/recipes-bsp/u-boot/u-boot%.bbappend b/recipes-bsp/u-boot/u-boot%.bbappend
index 3e59e46c646f..dce4f32d356a 100644
--- a/recipes-bsp/u-boot/u-boot%.bbappend
+++ b/recipes-bsp/u-boot/u-boot%.bbappend
@@ -1,6 +1,6 @@
 # various machines require the pyelftools library for parsing dtb files
 DEPENDS:append = " python3-pyelftools-native"
-DEPENDS:append:rock-pi-s = " u-boot-tools-native"
+DEPENDS:append:rk3308 = " u-boot-tools-native"
 DEPENDS:append:rock-pi-4 = " gnutls-native"
 
 EXTRA_OEMAKE:append:px30 = " BL31=${DEPLOY_DIR_IMAGE}/bl31-px30.elf"
diff --git a/recipes-kernel/linux/linux-yocto_%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend
index b0efa0d0c130..a9223301dde1 100644
--- a/recipes-kernel/linux/linux-yocto_%.bbappend
+++ b/recipes-kernel/linux/linux-yocto_%.bbappend
@@ -17,6 +17,7 @@ COMPATIBLE_MACHINE:nanopi-r2s = "nanopi-r2s"
 COMPATIBLE_MACHINE:nanopi-m4b = "nanopi-m4b"
 COMPATIBLE_MACHINE:rock-pi-s = "rock-pi-s"
 COMPATIBLE_MACHINE:roc-rk3328-cc = "roc-rk3328-cc"
+COMPATIBLE_MACHINE:roc-rk3308-cc = "roc-rk3308-cc"
 
 SRC_URI:append = " file://rockchip-kmeta;type=kmeta;name=rockchip-kmeta;destsuffix=rockchip-kmeta"
 SRC_URI:append:nanopi-r4s = " file://nanopi-r4s.scc"
-- 
2.43.0.76.g1a87c842ece3



                 reply	other threads:[~2024-01-17  6:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240117061353.30123-1-twoerner@gmail.com \
    --to=twoerner@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox