From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dfu: fix some issues with reads/uploads
Date: Fri, 30 May 2014 14:59:10 -0600 [thread overview]
Message-ID: <5388F11E.5080906@wwwdotorg.org> (raw)
In-Reply-To: <20140530102857.414614cc@amdc2363>
On 05/30/2014 02:28 AM, Lukasz Majewski wrote:
...
> I've tested if raw u-boot can be downloaded and uploaded via DFU. The
> u-boot size is 1MiB precisely.
>
> Corresponding dfu_alt_info entry:
> "u-boot raw 0x80 0x800;" \
...
> 2. Upload (raw):
>
> dfu-util -a0 -U u-boot-mmc.bin_target
> It exits immediately and I can only see the file size of 0.
>
> So obviously we have regression here. However, since I didn't covered
> this case in my tests I don't know when it was broken.
Hmmm. I tested with that exact value of dfu_alt_info and got back an
exactly 1MB file with either the dfu-util packaged in Ubuntu 12.10, or
with the latest git tree of dfu-util. Can you investigate why you're
getting back a 0-length file? Perhaps there's some error condition, so
dfu-util exits before any data is downloaded, or perhaps when
dfu_get_medium_size_mmc() is called, either lba_size or lba_blk_size is
0 (neither should be...)
Thanks.
next prev parent reply other threads:[~2014-05-30 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 23:59 [U-Boot] [PATCH] dfu: fix some issues with reads/uploads Stephen Warren
2014-05-22 10:20 ` Lukasz Majewski
2014-05-22 17:06 ` Stephen Warren
2014-05-30 8:28 ` Lukasz Majewski
2014-05-30 20:59 ` Stephen Warren [this message]
2014-06-02 6:14 ` Lukasz Majewski
2014-06-02 15:52 ` Stephen Warren
2014-06-03 7:51 ` Lukasz Majewski
2014-06-10 17:53 ` Stephen Warren
2014-06-12 7:17 ` Lukasz Majewski
2014-06-12 15:25 ` Stephen Warren
2014-06-20 15:16 ` Lukasz Majewski
-- strict thread matches above, loose matches on Subject: below --
2014-06-10 21:25 Stephen Warren
2014-06-10 21:27 ` Stephen Warren
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=5388F11E.5080906@wwwdotorg.org \
--to=swarren@wwwdotorg.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 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.