roc-rk3308-cc: add

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>
This commit is contained in:
Trevor Woerner 2024-01-17 01:07:59 -05:00
parent cc2d078806
commit 09ead816cd
4 changed files with 27 additions and 12 deletions

24
README
View File

@ -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:

View File

@ -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"

View File

@ -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"

View File

@ -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"