From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] [OT] trying to boot zedboard just to u-boot, having no luck
Date: Tue, 23 Apr 2019 07:03:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1904230702370.12061@localhost.localdomain> (raw)
In-Reply-To: <ac804dc5-2889-867a-669f-c7d442c2dbe0@monstr.eu>
On Tue, 23 Apr 2019, Michal Simek wrote:
> On 20. 04. 19 12:44, Robert P. J. Day wrote:
> >
> > i've asked on the meta-xilinx mailing list, and rummaged around the
> > net, and have failed to do something that should be straightforward --
> > i want to simply boot an avnet zedboard to a recent u-boot and stop
> > there; i have no need to go any further for the time being.
> >
> > i have no problem configuring and building u-boot using:
> >
> > $ make zynq_zed_defconfig
> >
> > and as a test, i've tried to download any pre-built SD card
> > images/files just to verify that the board boots, with absolutely no
> > luck. i've formatted and re-formatted SD cards, populated them with
> > allegedly working image files, checked and rechecked jumper settings
> > to boot from SD card, used minicom and picocom to connect to the UART
> > port ... all i ever see is the power LED come on, and never anything
> > else.
> >
> > if someone can point me at a recipe that is verified to work to get
> > u-boot up and running on this zedboard, i would be eternally grateful,
> > because i'm running out of ideas.
>
> I didn't try zed board for quite a long time.
> You can look at images distributed via http://zedboard.org/
> or petalinux bsp which should also run on zeboard.
actually, just resolved getting SD card to boot so apologies for the
interruption ... we're good here.
rday
prev parent reply other threads:[~2019-04-23 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 10:44 [U-Boot] [OT] trying to boot zedboard just to u-boot, having no luck Robert P. J. Day
2019-04-23 10:59 ` Michal Simek
2019-04-23 11:03 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1904230702370.12061@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=u-boot@lists.denx.de \
/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