From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 0/9] Convert Pico-Pi i.MX7D to DM
Date: Fri, 15 Feb 2019 12:50:21 +0100 [thread overview]
Message-ID: <20190215125021.4a4f6340@jawa> (raw)
In-Reply-To: <CAOMZO5CphrwgVsZSz+43y0DvLFaDy1hxvvRPo0rJxsJ3Qx528g@mail.gmail.com>
Hi Fabio,
> Hi Lukasz,
>
> On Wed, Jan 23, 2019 at 7:01 PM Joris Offouga
> <offougajoris@gmail.com> wrote:
>
> > Hi Lukasz,
> >
> > > Please check if malloc pool size (in Kconfig) is large enough to
> > > handle DFU requests.
> > The dfu request is smaller than the size of malloc pool size
> > >
> > > Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c
> > > and share output.
> >
> > This is a log when dfu failed :
> >
> > blk_find_device: if_type=6, devnum=0: usdhc at 30b40000.blk, 6, 2
> > blk_find_device: if_type=6, devnum=0: usdhc at 30b50000.blk, 6, 1
> > blk_find_device: if_type=6, devnum=0: usdhc at 30b60000.blk, 6, 0
> > Request would exceed designated area!
Please carefully check the eMMC partition size (as defined in
dfu_alt_info) and the size of sent data.
This error happens when one wants to write bigger file than the
reported space on the partition.
Please look at drivers/dfu/dfu_mmc.c Line: 44
> > dfu_write_buffer_drain: Write error!
> > #Deferred dfu_flush() failed!reset_config:
> > unbind function 'dfu'/9ef6e678
> > g_dnl_unbind: calling usb_gadget_disconnect for controller
> > 'ci_udc'
>
> Do you have any idea on this issue, please?
>
> This DFU bug is one of the items that is blocking the DM conversion of
> this board.
>
> Thanks
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190215/0019c5f8/attachment.sig>
next prev parent reply other threads:[~2019-02-15 11:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 22:38 [U-Boot] [RFC 0/9] Convert Pico-Pi i.MX7D to DM Joris Offouga
2019-01-22 9:47 ` Lukasz Majewski
2019-01-23 21:01 ` Joris Offouga
2019-02-15 11:22 ` Fabio Estevam
2019-02-15 11:50 ` Lukasz Majewski [this message]
2019-02-16 11:06 ` Offouga Joris
2019-02-16 12:17 ` Fabio Estevam
2019-02-16 12:33 ` Fabio Estevam
2019-02-16 12:33 ` Joris Offouga
2019-02-16 12:46 ` Fabio Estevam
2019-02-16 13:02 ` Joris Offouga
2019-02-16 13:58 ` Fabio Estevam
2019-02-16 14:38 ` Joris Offouga
2019-02-16 14:42 ` Fabio Estevam
2019-02-16 14:52 ` Joris Offouga
2019-02-16 14:54 ` Fabio Estevam
2019-02-16 15:14 ` Joris Offouga
2019-02-16 15:25 ` Fabio Estevam
2019-02-16 15:41 ` Joris Offouga
2019-02-16 15:43 ` Fabio Estevam
2019-02-19 19:24 ` Offouga Joris
2019-02-19 20:22 ` Fabio Estevam
2019-02-28 20:38 ` Fabio Estevam
2019-02-28 22:06 ` Offouga Joris
2019-03-09 22:21 ` Offouga Joris
2019-03-10 14:24 ` Fabio Estevam
2019-03-10 18:35 ` Joris Offouga
[not found] <1548019059-10918-1-git-send-email-offougajoris@gmail.com>
2019-02-14 12:27 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2019-01-20 21:18 Joris Offouga
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=20190215125021.4a4f6340@jawa \
--to=lukma@denx.de \
--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