Re: Ezloader example with an EZ-USB FX2 chip SOLVED

Subject: Re: Ezloader example with an EZ-USB FX2 chip SOLVED

From: philippe wicker <email@hidden>

Date: Wed, 9 Nov 2005 16:55:55 +0100

Delivered-to: email@hidden

Hello all,

I finally solved the firmware downloading to an EZ-USB FX2 chip. For people interested in the modifications to apply to the Ezloader sample code here is a summary of what have to be done:

1- use the address 0xE600 instead of 0x7F92 for the 8051 "reset" register (CPUCS for the FX2, USBCS for the anchor),

2- before loading the firmware, preload in the FX2 internal memory a loader firmware (file loader.c) available in the Cypress\ USB\Drivers\ezloader directory on your Windows development machine (part of the Cypress SDK). This loader enables the 8051 to handle vendor specific requests to load the external memory.

3- run this loader (by de-asserting the 8051 reset)

4- proceed to your firmware loading by following the steps:

a- download hex records targeting the **external** memory only,

b- reset the 8051 (gives back the control to the FX2 core),

c- download hex records targeting the **internal** memory only

d- de-assert the 8051 reset (gives back the control to your firmware). This firmware should disconnect and reconnect to the bus in order to force the re-numeration.

I'll try to package a clean code of the modified ezloader in a couple of weeks (taking some hollydays first :)). People interested in getting the code can contact me.

Regards

philippe wicker wrote:

Hello all,
I'm really new to USB programming and these are my first experiments. I'm trying to download a firmware into an EZ-USB FX2 chip using the Ezloader sample code. This chip is actually hosted by a Cypress evaluation board. The downloaded firmware contains descriptors for a class compliant midi device (this is at least what I assume....). I already changed the k8051_USBCS constant (0x7f92) with k8051_CPUCS (0xE600) which is I believe the correct register to address to manage the reset state for the FX2 8051. The downloading and "assert reset" and "de-assert reset" requests seems to complete successfully, but the "new" device doesn't show up in USBProber (USBProber still shows the Cypress default device 0x4b4/0x8613) and NewDeviceAdded loop body is not executed after the downloading.
Any idea about the problem? Should the "new" device automatically shows up in USBProber? As it is a class compliant midi device, do I need to load a driver (as is done by Ezloader)?
Thanks for any tips or pointers.
Regards
Philippe

_______________________________________________ Do not post admin requests to the list. They will be ignored. Usb mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/usb/email@hidden This email sent to email@hidden

References:
	>Ezloader example with an EZ-USB FX2 chip (From: philippe wicker <email@hidden>)
	>Re: Ezloader example with an EZ-USB FX2 chip (From: Jonathan Selby <email@hidden>)
	>Re: Ezloader example with an EZ-USB FX2 chip (From: philippe wicker <email@hidden>)