From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] {Spam?} u-boot-usb DFU working but need some ideas
Date: Tue, 08 Feb 2011 11:40:47 +0100 [thread overview]
Message-ID: <m2wrla6c7k.fsf@ohwell.denx.de> (raw)
In-Reply-To: <201102052220.27750.korgull@home.nl> (Marcel's message of "Sat, 5 Feb 2011 22:20:27 +0100")
Hi Marcel,
> I finally got things working well with my SAM9G45 USB devcie controller and
> continued to implement DFU for it.
> I implemented it using the new gadget layer and should be compatible with the
> at91_udc driver.
Excellent, congratulations!
> I have managed to get DFU working in such way that it transfers the file to
> RAM. There's still a lot to do, but most things are in place and working
> well. Basically after transfer to RAM, a u-boot script can handle additional
> actions, so I'm in doubt about the following :
>
> The DFU implementation I used as a basis came from openmoko. This implements
> directly flashing the device.
> However, my thought is that it's much better to just write the file to RAM and
> let a script in u-boot handle what should happen with it (verify, boot, flash)
> The DFU spec seems to handle this with the bitManifestationTolentant bit, but
> the current dfu-utils don't use this bit (that can be updated of course, which
> I already did).
I am not too familiar with the DFU spec, but I agree with regards to the
scripting. I can envision usage scenarios where the downloaded files
are written to other storage media, so I would much rather leave that up
to the U-Boot script interpreter.
> About the way it currently works :
> 1) I start u-boot
> 2) I issue the dfuinit command (new)
> 3) the host can now download a file to RAM.
> Any thoughts on what would be the most preferred way to do this ?
This sequence sounds absolutely feasible. What exactly is your
question?
> Additionally I think I will implement this as a composite driver so that both
> (usb)CDC and DFU are available via USB. I have both working, but currently
> must select it at compile time.
> My current implementation basically is just DFU as it assumes the application
> (not u-boot) to be the firmware to be updated, so no need to switch on
> descriptor layer level.
>
> Any reply on this would be nice, even if my above thoughts are in line.
> I hope to be able to post my changes in 1-2 weeks. After that my time is
> extremely limited due to long time travel.
I'm really looking forward to getting DFU support into U-Boot - having
lobbyied for it quite a while :)
> If anyone is interested in helping me out posting the changes it would
> be very much appreciated.
What help do you need?
Cheers
Detlev
--
Emacs seems a more likely candidate to contain a mail system than the
mail system to contain an Emacs, so this is the way it was done.
-- Bernard S. Greenberg
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2011-02-08 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 21:20 [U-Boot] {Spam?} u-boot-usb DFU working but need some ideas Marcel
2011-02-08 10:40 ` Detlev Zundel [this message]
2011-02-10 7:46 ` Marcel
2011-02-10 8:04 ` Wolfgang Denk
2011-02-10 19:15 ` Marcel
2011-02-10 19:26 ` Wolfgang Denk
2011-02-11 18:30 ` Marcel
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=m2wrla6c7k.fsf@ohwell.denx.de \
--to=dzu@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