Thread-topic: Downloading hex file to Cypress FX2LP
User-agent: Microsoft-Entourage/11.3.3.061214
on 3/22/07 12:09 PM, email@hidden at
email@hidden wrote:
> Date: Thu, 22 Mar 2007 10:21:14 -0700
> From: Tom Pratum <email@hidden>
> Subject: Downloading hex file to Cypress FX2LP
> To: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Hello all-
> A week or so ago I asked on the list about obtaining the hex file,
> after I obtained it I followed the outline that I found here to
> download the hex file to the board under the assumption that a FX2LP
> would respond as a FX2 would (note that my hex file does not appear
> to go into extended memory):
> - I write a 1 to address 0xE600 to assert reset and thus enable it
> to have firmware written to it.
> - I load the firmware as shown in the ez-loader example.
> - I de-assert the reset by writing zero to the same address.
> After I do this and run USB-Probe, I can see something clearly
> occurred, but now it says I have 60 interfaces where before the
> download I had 1, which puzzles me, but what do I know. In any case,
> after I implement part of the vendors software to test one function,
> I find that the device is obviously not responding. There are a
> couple of messages here in the archives about folks who have gotten
> this (downloading) to work, and some indication that more may be
> involved than what I have outlined. One person offered to send out
> the software used. However, I attempted contact and received no
> response (sort of like my usb project here).
> It is of course possible that my firmware hex file is no good, but I
> highly doubt that since it is in the vendors interest to get this to
> work; their application of course already works under Windows.
> So, my questions:
> - Is it necessary to do more than what I have outlined above to
> download the firmware to the FX2LP?
I don't think so, but I don't know the difference between the FX2LP & FX2.
> - Is anyone who is reading this message willing to send me a snippet
> of code that has worked for downloading to a FX2LP or FX2?
We're basically using the method in the Apple sample code. I suggest you
look at the device descriptor in hex and compare it with what you expect. It
is possible that the code you are using to parse the hex file and deliver it
to the device has an endian issue.
> I have another question that is somewhat unrelated, in the Windows
> version of the software, the pipes are addressed by their endpoint
> addresses (e.g. 0x01, 0x02, 0x86 in this case) using a
> DeviceIoControl statement whereas it appears that the IOUSB interface
> functions like WritePipe use the pipe number (e.g. 1 to number of
> pipes); is that just the way things are, or am I misunderstanding
> something.
That's just the way it is. Opening the interface interface gives you access
to the interface pipes, and Apple lets you access those using pipe
references. Pipes have endpoints.
> Thank you all very much for any help.
>
>
> Tom Pratum
_______________________________________________
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
