From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Test failures in u-boot/master on NVIDIA HW with recent push
Date: Thu, 17 Jan 2019 19:42:17 -0500 [thread overview]
Message-ID: <20190118004217.GJ27429@bill-the-cat> (raw)
In-Reply-To: <8c6f43eb-c436-e000-35e0-df73dabe652a@wwwdotorg.org>
On Thu, Jan 17, 2019 at 05:34:57PM -0700, Stephen Warren wrote:
> Tom,
>
> The recent set of patches pushed to u-boot/master cause DFU failures on both
> Jetson TK1 and Jetson TX1 (i.e. all platforms where I run the DFU test) with
> the following in the log:
>
> host:
> dfu-util -a 0 -U /var/lib/jenkins/workspace/u-boot-denx_uboot-master-test-py/U_BOOT_BOARD/jetson-tk1/build/u-boot/jetson-tk1/dfu_readback.bin
> -p 3-2.3
>
> target:
> ** Reading file would overwrite reserved memory **
> dfu: Read error!
> dfu_read: Failed to fill buffer
> Tegra124 (Jetson TK1) #
>
> I noticed some lmb fixes in the list, so I guess it's due to that.
So.. intentional! Adding in Simon here, but I think the short answer is
that you need to change where you're saying the file goes in memory.
FWIW I run the DFU test on my dra7xx_evm and it's passing.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190117/9f0ef999/attachment.sig>
next prev parent reply other threads:[~2019-01-18 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 0:34 [U-Boot] Test failures in u-boot/master on NVIDIA HW with recent push Stephen Warren
2019-01-18 0:42 ` Tom Rini [this message]
2019-01-18 0:50 ` Stephen Warren
2019-01-18 1:15 ` Tom Rini
2019-01-18 6:29 ` Stephen Warren
2019-01-18 8:04 ` Simon Goldschmidt
2019-01-22 8:12 ` Simon Goldschmidt
2019-01-23 18:20 ` Stephen Warren
2019-01-23 20:39 ` Simon Goldschmidt
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=20190118004217.GJ27429@bill-the-cat \
--to=trini@konsulko.com \
--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