Hi, sorry for the continuous strain of emails but I've tested writing and
reading something in location 0x3FF0 and it works properly. It seems that I
do have 16KB of memory. Or do I?
On Sun, Oct 21, 2012 at 11:52 AM, v01d <[email protected]> wrote:
> I meant, enumerates as high-speed, sorry.
>
>
> On Sun, Oct 21, 2012 at 11:52 AM, v01d <[email protected]> wrote:
>
>> Oh, damn.
>> But, if it enumerates as full-speed do you think it is a counterfeit chip
>> also?
>> I will try to run benchmarks, and see speeds.
>> Is there any way to discern the good and bad chips before buying?
>>
>> Thanks
>>
>>
>> On Sun, Oct 21, 2012 at 5:33 AM, Bert Vermeulen <[email protected]> wrote:
>>
>>> On 20/10/12 23:15, v01d wrote:
>>> > Hi,
>>> > I've been working on the Cypress FX2 chip (with the LCsoft board from
>>> > ebay) and I had a very hard time making it work (mainly, renumerate)
>>> > using any code that depended on fx2lib.
>>> > I've finally found some code based on gnuradio which didn't use fx2lib.
>>> > They developed their own base code and, provided you take some care
>>> when
>>> > compiling their code, it works perfectly.
>>> > I haven't been able to understand why fx2lib code does not work in the
>>> > same board.
>>>
>>> You should be aware that there's been a rash of counterfeits on the
>>> LCsoft boards on ebay -- got some bad ones myself. The chips are
>>> labelled correctly as the Cypress FX2LP, but are actually the older
>>> Cypress FX2. Among other things, it's a Full Speed-only (12Mb/s) USB
>>> chip. It also has 8K RAM instead of the FX2LP's 16K. However, fx2lafw
>>> doesn't run on it.
>>>
>>> It's perfectly possible to run code on it, if you don't require HS
>>> (which fx2lafw does) and don't try to use memory over 8K. Quite likely
>>> this is the case for the USRP firmware.
>>>
>>> So I think you've got a counterfeit.
>>>
>>> > I have submitted this issue to the fx2lafw github repo since it is
>>> > simple to reproduce in my case (I use compiled and precompiled firmware
>>> > and neither work) but I realize this may be a problem in fx2lib itself.
>>> > The thing is that the fx2lib code does not seem to be very active and
>>> > fx2lafw does, so maybe the devs here have more idea.
>>> > Also, I'm reporting this here in the interest of fixing fx2lib since it
>>> > looks like a fine library to base code on (I don't know if the gnuradio
>>> > has a very complete implementation of all FX2 functions).
>>>
>>> fx2lafw is a sub-project of sigrok, and this is the correct place to
>>> report problems for it. That github repo is just a random fork.
>>>
>>> fx2lib has some problems compiling with more recent versions of SDCC, so
>>> we fixed those
>>> (
>>> http://sigrok.org/gitweb/?p=sigrok-firmware-fx2lafw.git;a=history;f=fx2lib;hb=HEAD
>>> )
>>> and ship fx2lafw with that (stripped-down) version of fx2lib. However,
>>> we're not the official maintainers of fx2lib, the project does indeed
>>> appear to be abandoned.
>>>
>>>
>>> --
>>> Bert Vermeulen
>>> [email protected]
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Everyone hates slow websites. So do we.
>>> Make your web apps faster with AppDynamics
>>> Download AppDynamics Lite for free today:
>>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>>> _______________________________________________
>>> sigrok-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/sigrok-devel
>>>
>>
>>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
