> Date: Thu, 04 Apr 2002 13:39:17 -0800 > From: Bernie Radecki <[EMAIL PROTECTED]> > Subject: [Linux-usb-users] Load EEPROM image file into EZUSB EEPROM > > I am developing a USB device using the Cypress AN2131Q EZUSB chip. > I can use the Linux executable 'ezdownload' to send the HEX formatted > execuatble to the EZUSB RAM via the proc file system. I have modified > the HEX formatted executable to be HEX formatted image file that I > want to load into the EEPROM on the EZUSB's i2C bus.
Probably simpler to use the current version of "fxload" for that. Soon to be released as RPMs etc, but meanwhile use CVS for the http://linux-hotplug.sourceforge.org project, module "fxload". > Can the default > EZUSB device handle that or do I need to have a special vendor request > in my code and set up a driver to send the bits so they can be shuffled > into the EEPROM? The default device doesn't handle such stuff, you need special firmware (which you probably have in hand) and a driver like fxload to talk to it. Use the "Vend_Ax" firmware from Cypress, it's in the developer kit from Cypress. With "fxload" a command like this doe the job for the EZ-USB FX: # fxload -D /proc/bus/usb/... -s vend_ax.hex -c 0 firmware.hex But since you're using the AnchorChips version, you'd need to tweak the ezusb_load_eeprom() routine, since that needs a third EEPROM format. You'll notice the FIXME there. :) I'd fix by adding an option taking a device type string, like "fx", "fx2", or "an2100", and using that instead of the boolean flag that's there now ("-2"). If you do that, please send the patches along to me. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
