On Wed, 18 Apr 2001, Adam J. Richter wrote:
> I have updated my little ezusb_load program, simplifying it
> and its input syntax. There no longer is a length count in each line,
> numbers no longer have a leading "0x" in front of them, and all
> numbers are hexadecimal. This makes the firmware files much easier
> to read. I am calling this version 0.2.
Did some short testing: works fine with usb-ohci, usb-uhci, uhci and
CY3671 development board (EZ-USB FX) as device. Did only try to load some
test firmware - not for the different serial devices (no hardware here).
Furthermore, haven't tried how it cooperates with hotplugging
("dontcare" for me).
Some thoughts:
- dropping the length count isn't a good idea IMHO, since you've just
lost one of the last chances for validation. Even a simple error like
missing newline or conversion error isn't discovered anymore and you are
feeding crap into the device.
- As was already said by Brad, I'd also prefer the thing to accept intel
hex input: standard format, checksum-protected, most tools will provide
this anyway
- The tool should be prepared to accept 32 byte chunks for download, as
this is what sdcc/asxxxx use for example.
- Don't start any download before all data has been verified
- I think the 0xa0 request type indicator is redundant and should be
dropped. If other request types are needed (whitehead e.g.) the device
is no longer simple type and the driver will probably need to do other
stuff like deciding which part to load when - simple userland tool will
break sooner or later.
- probably making the "keep mcu in reset during download" feature to be
selected via command line.
I've attached the tool which I'm currently using for this purpose for
whatever it might be useful for.
Martin
intel hex to ezusb loader
