tal 16 MiB
Patch attached, for clarity.
>From bda546ffdc5b0a25ee554d75f963d1c0570f3f7e Mon Sep 17 00:00:00 2001
From: Simon South
Date: Tue, 10 Nov 2020 12:49:27 -0500
Subject: [PATCH] rockchip: Pinebook Pro: Fix SPI flash
As per a suggestion by Alper Nebi Yasak.
---
arch/arm/dts/rk3399
Simon South writes:
> Has anyone managed to get the built-in keyboard of the Pinebook Pro
> working with U-Boot?
>
> Even using the latest code, having USB started makes the U-boot
> console feel sluggish while pressing keys on the keyboard produces no
> result.
To follow up o
but if your build works that would at least point to something I've
missed in my setup.
--
Simon South
si...@simonsouth.net
thing up correctly
and then the controller just does nothing. In GNU/Linux, everything
works fine. Very strange.
--
Simon South
si...@simonsouth.net
fferent about my unit.
--
Simon South
si...@simonsouth.net
driver works on other
platforms, so it seems to me this could be something specific to
Rockchip's implementation not yet reflected in the code.
Has anyone found a solution to this?
--
Simon South
si...@simonsouth.net
Add a call to rk3328_configure_cpu() during initialization to set the
CPU-clock frequency.
Signed-off-by: Simon South
---
arch/arm/include/asm/arch-rockchip/cru_rk3328.h | 3 +++
drivers/clk/rockchip/clk_rk3328.c | 2 ++
2 files changed, 5 insertions(+)
diff --git a/arch/arm
es make it straightforward to set a
higher clock rate at compile time for systems like the ROCK64 that run
reliably at higher frequencies.
Tested on my ROCK64.
Simon South (1):
clk: rockchip: rk3328: Configure CPU clock
arch/arm/include/asm/arch-rockchip/cru_rk3328.h | 3 +++
drivers/clk/rockchip/cl
Fix a typo that caused incorrect values to be loaded into the DRAM
controller's deskew registers.
Signed-off-by: Simon South
---
drivers/ram/rockchip/sdram_rk3328.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ram/rockchip/sdram_rk3328.c
b/drivers/ram/roc
Fix a pair of tests in phy_dll_bypass_set() that used incorrect units
for the DDR frequency, causing the DRAM controller to be misconfigured
in most cases.
Signed-off-by: Simon South
---
drivers/ram/rockchip/sdram_rk3328.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a
cases the "mtest" memory-test command runs indefinitely
without error, and I can boot into NetBSD successfully without the
kernel hanging or panicking.
[1] https://lists.denx.de/pipermail/u-boot/2019-September/384076.html
Simon South (2):
ram: rk3328: Use correct frequency units in fu
existing implementation of snprintf(), its buffer-size
parameter is ignored.
Signed-off-by: Simon South
---
lib/tiny-printf.c | 16
1 file changed, 16 insertions(+)
diff --git a/lib/tiny-printf.c b/lib/tiny-printf.c
index ebef92fc9f..62e6381961 100644
--- a/lib/tiny-printf.c
Signed-off-by: Simon South
---
common/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/Kconfig b/common/Kconfig
index 28d5e9a0cc..d9ecf79e0a 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -764,7 +764,7 @@ config SPL_LOG_CONSOLE
line number are
a few bytes by having the existing
sprintf() and snprintf() functions call vsnprintf() when it's
available. I haven't made this change only because it isn't how the
existing code is written (printf() could call vprintf(), and
snprintf() could call sprintf(), yet neither do) and I assum
/rk3328_ddr_333MHz_v1.16.bin
[2] https://lists.denx.de/pipermail/u-boot/2019-September/384076.html
[3]
https://gitlab.denx.de/u-boot/u-boot/blob/8b1ceb0ac1aa1746c6751d698ce7a012a236fa65/doc/README.rockchip
--
Simon South
si...@simonsouth.net
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
--
Simon South
si...@simonsouth.net
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
image to a microSD card with
zcat obj/releasedir/evbarm/binary/gzimg/arm64.img.gz | sudo dd
bs=32768 of=/dev/mmcblk0 skip=512 seek=512
and build and install U-Boot as in my previous email.
[1] https://netbsd.org/docs/current/index.html
[2] https://netbsd.org/docs/guide/en/chap-build.
t exists in U-Boot and at least one
group of ROCK64s in the world.
At the moment I'm still trying to identify what's different in the
closed-source loader that causes it not to have this issue. Anyone have
any thoughts?
[1] https://forum.pine64.org/showthread.php?tid=7387
--
Simon So
On 2019-09-19 4:56 a.m., Simon South wrote:
I've been unable so far to boot NetBSD on my PINE64 ROCK64 (v2.0,
Rockchip RK3328) using U-Boot built with its own TPL...
This definitely seems memory-related: After enabling the "mtest" command
(patch attached) and running the memor
328...
02080070: 0400 0b00 0100 0300....
=> fdt addr ${kernel_addr_r}
=>
--
Simon South
si...@simonsouth.net
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
I still see the "FDT_ERR_BADMAGIC" messages from U-Boot.
Applying Elaine's patches for RK805 support makes no difference.
Complete log attached.
--
Simon South
si...@simonsouth.net
U-Boot TPL 2019.10-rc3-00361-ga9fa70b7b7-dirty (Sep 21 2019 - 07:45:04)
LPDDR3
Trying to boot from BOOTROM
Re
On 2019-09-20 1:27 p.m., Simon South wrote:
I'm going to apply Elaine's patches and see if that changes things.
Unfortunately no; other than this line now appearing in the output:
PMIC: RK8050 (on=0x10, off=0x04)
nothing seems to have changed. Either the machine hangs o
nx.dtb
89522 rk3399-gru-kevin.dtb
85495 rk3399-gru-bob.dtb
80312 rk3399-firefly.dtb
78519 rk3399-ficus.dtb
68842 rk3399-evb.dtb
53513 rk3328-rock64.dtb
52150 rk3328-roc-cc.dtb
51134 rk3328-evb.dtb
19 file(s), 2 dir(s)
=>
--
Simon South
s
Boot for the RK805, which makes me think this isn't taking
place currently. And while NetBSD includes its own RK805 driver it is
likely assuming this setup has already happened ("regulator-boot-on") by
the time the kernel starts and does not need to be done again.
Does this s
t; shows additional entries for the S/PDIF and MMC
controllers, and when booting with Rockchip's TPL a (possibly spurious)
"Initializing UCLASS_EFI" message is output, but otherwise they're the same.
I've attached the two capture logs in case anyone is curious.
-
are output only when the
U-Boot TPL is used.
--
Simon South
si...@simonsouth.net
DDR version 1.16 20190528
ID:0x805 Y
In
LPDDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
U-Boot SPL 2019.10-rc3-00361-ga9fa70b7b7 (Sep 20 2019 - 04:55:01 -0400)
Tryi
#x27;s only
when using U-Boot's own TPL that the kernel panics shortly after starting.
Can you think of what the difference might be between the two TPLs?
--
Simon South
si...@simonsouth.net
___
U-Boot mailing list
U-Boot@lists.denx.de
https
spl/u-boot-spl.bin >> idbloader.img
In either case I install on the microSD card with
sudo dd if=idbloader.img of=/dev/sdb seek=64
sudo dd if=u-boot.itb of=/dev/sdb seek=16384
Does this look right?
--
Simon South
si...@simonsouth.net
__
000 aarch64_start() at ffc0183c
netbsd:aarch64_start+0x103c
[ 1.000] cpu0: End traceback...
Stopped in pid 0.1 (system) at netbsd:cpu_Debugger+0x4:ret
db{0}>
--
Simon South
si...@simonsouth.net
___
U-Boot mailing list
29 matches
Mail list logo
