From: Vagrant Cascadian <vagrant@debian.org>
To: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Subject: Re: cannot boot from microSD card on aarch64 machine
Date: Wed, 02 Mar 2022 10:19:20 -0800 [thread overview]
Message-ID: <871qzkfc9j.fsf@contorta> (raw)
In-Reply-To: <87h78g1qu5.fsf@mdc-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
On 2022-03-02, Ricardo Wurmus wrote:
> I got myself a rockpro64 board.
...
> So I then decided to build my own system and install a new u-boot onto
> the microSD card. Here’s the system I built:
...
> (bootloader (bootloader-configuration
> (bootloader u-boot-rockpro64-rk3399-bootloader)
> ;; SD card/eMMC (SD priority) storage
> (target "/dev/mmcblk1")))
You need to leave a pretty generous gap at the partition table of your
microSD, either a GPT partition table with various partitions for the
various u-boot bits:
http://opensource.rock-chips.com/wiki_Partitions
or an MBR partition table with the first partition starting at sector
32768, and the previous sectors empty.
Otherwise, the u-boot installation may clobber parts of your partition
table or vice-versa.
Also, if you have a different u-boot installed to SPI or eMMC, those
will take priority over microSD on most rockchip platforms.
> (kernel linux-libre)
> (kernel-arguments
> (list "console=ttyS2")) ; UART2 connected on the Pi2 bus
I assume you're using a serial console. The rockchip platforms usually
default 1500000 for baud ... usually I use:
screen /dev/ttyUSB0 1500000
Oh, now that I think about it, you might also want to set the speed for
your console in kernel-arguments:
(kernel-arguments
(list "console=ttyS2,1500000"))
> Does it perhaps install the u-boot files at the wrong offsets? How
> would I begin to debug this?
It is also entirely possible something is wrong with rockpro64 u-boot
offsets or u-boot itself ... been a while since I've tested.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-03-02 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 11:37 cannot boot from microSD card on aarch64 machine Ricardo Wurmus
2022-03-02 17:19 ` Efraim Flashner
2022-03-02 18:45 ` Ricardo Wurmus
2022-03-02 18:19 ` Vagrant Cascadian [this message]
2022-03-02 18:52 ` Ricardo Wurmus
2022-04-06 22:26 ` Denis 'GNUtoo' Carikli
2022-03-29 21:45 ` Ricardo Wurmus
2022-03-16 14:34 ` Maxim Cournoyer
2022-03-29 21:35 ` Ricardo Wurmus
2022-03-30 4:49 ` Maxim Cournoyer
2022-04-02 1:10 ` Vagrant Cascadian
2022-04-02 16:15 ` Ricardo Wurmus
2022-04-02 22:51 ` Vagrant Cascadian
2022-04-03 5:08 ` Ricardo Wurmus
2022-04-05 20:32 ` Vagrant Cascadian
2022-04-06 8:50 ` Ricardo Wurmus
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=871qzkfc9j.fsf@contorta \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.