On Wed, 18 Apr 2001, Sancho Dauskardt wrote:
> I don't know if there are actually EzUSB's around that have 'External RAM'
> (8051 addresses above 0x1B3F).
> If yes, there are at least 2 methods of sending firmware to this area:
> 1) Send down 'loader-firmware' that implements 0xA3 ANCHOR_LOAD_EXTERNAL
> command (the way Cypress/AnchorChips does it)
> 2) Send down 'loader-firmware' that takes complete 22 byte
> INTEL_HEX_RECORDS via some Bulk endpipe.
>
> Well, even if this turnes out to be a problem, just add some sort of
> PINTEL_HEX_RECORD give_firmware(usb_dev *dev,int *count);
> and let the driver do the download himself.
>
> Anybody seen how this works for a EzUSB-FX ?
I do only use the internal download, but according to the EZ-USB FX TRM
there is no way to access the external memory (XMEM which is not
on-chip) using control EP 0 of the _default USBcore_. While the 0xa0
(ANCHOR_LOAD_INTERNAL) request works identical, the 0xa1-0xaf request are
documented as "reserved - do not use for your application". I would expect
both your suggestions above to work for the FX too, except you might want
to use 0xb-something for request id. Of course you need to implement the
external memory as shared DATA/CODE if you are going to load code into it
for execution.
Martin
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
