From: Tim Sander <tim@krieglstein.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Xilinx Zed Board resets with Master
Date: Fri, 28 Mar 2014 16:20:34 +0100 [thread overview]
Message-ID: <1869748.2O04FD8Mds@dabox> (raw)
In-Reply-To: <816b3167-aaae-4653-818b-fb063ad7c2c9@TX2EHSMHS019.ehs.local>
Hi Michal
> On 03/27/2014 05:32 PM, Tim Sander wrote:
> > Hi Michal
> >
> > Am Donnerstag, 27. M?rz 2014, 14:17:41 schrieb Michal Simek:
> >>>>>> Please check and may be you can try u-boot-dtb.elf.
> >>>>>
> >>>>> Mh, don't know how to create this kind of file?
> >>>>
> >>>> Jagan maybe knows more but I don't think u-boot-dtb.elf is generated.
> >>>> Just u-boot-dtb.bin is generated which should be copied as data file
> >>>> in xmd and not sure if binary file can be directly used for bootgen.
> >
> > If adding the dtb file in the boot.bif file is not the right way and no
> > elf file with dtb is generated: What is the right way to generate an
> > image for use with the SD-Card?
>
> you can just use static u-boot configuration.
I assume you mean static configuration a config with OF_CONTROL disabled.
Ok, i have tried to boot that with bootgen. That does not work.
Loading that into memory and booting it from within the debugger works
though. In both cases with or without OF_CONTROL enabled.
> I have never tried to add dtb as partition to boot.bin.
> If you want to use this dtb driver u-boot I would suggest you
> to look at u-boot SPL which should be able to handle binary formats
> with dtbs.
So my main focus is to test CONFIG_ARMV7_NONSEC to boot linux in
normal mode. I wanted to test recent mainline with that. So focusing on
u-boot SPL is to far off my targets. So i am happy with hardware debugger
loadeing for the time beeing.
Getting back to CONFIG_ARMV7_NONSEC. This is unfortunatly not working with the
Zynq. Currently the board switches to monitor mode but when the u-boot
switches to normal mode it jumps to PC:0xc (LR:0x10) which seems like a data
abort exeption or some other secure mode violation exception?
Is there a good way to find out what happened? I am currently stuck with this
and my local FAE has also no idea. Attached is a patch which at least works
until the return from the monitor mode.
Best regards
Tim
next prev parent reply other threads:[~2014-03-28 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 8:08 [U-Boot] Xilinx Zed Board resets with Master Tim Sander
2014-03-27 8:21 ` Michal Simek
2014-03-27 8:50 ` Jagan Teki
2014-03-27 10:33 ` Tim Sander
2014-03-27 12:01 ` Michal Simek
2014-03-27 12:05 ` Michal Simek
2014-03-27 12:11 ` Jagan Teki
2014-03-27 13:17 ` Michal Simek
2014-03-27 16:32 ` Tim Sander
2014-03-27 16:46 ` Michal Simek
2014-03-28 15:20 ` Tim Sander [this message]
2014-04-01 13:20 ` Michal Simek
2014-04-03 9:27 ` Tim Sander
2014-04-03 9:28 ` Michal Simek
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=1869748.2O04FD8Mds@dabox \
--to=tim@krieglstein.org \
--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