On 20/03/12 23:58, Joel Holdsworth wrote:
> First, I wanted to ask about how I should implement triggering in
> fx2lafw? The triggering code in saleae-logic is quite simple, and
> could easily be copied to fx2lafw. Uwe mentioned that we needed a
> more general abstraction for soft-triggering. I agree that such a
> thing would be desirable, but I'm not sure if it's a good solution
> right now.
> For now I could copy-paste the saleae soft triggering into the
> fx2lafw driver. Of course, copy and paste is bad, but then how badly
> do we need the saleae driver? Could it be dropped altogether? If
> fx2lafw works just as well, and supports all the same features,
> would it not be easier to drop it altogether, and reduce the
> maintenance burden? Then we wouldn't have to bother trying to figure
> out an elegant abstraction.
Certainly the intention is to drop the "saleae-logic" driver in favor of
the fx2lafw driver. After we have a release, I want to see about this.
As regards triggering: the long-term plan is to have a pluggable
"transform" framework that libsigrok can use. Some more details and
planned modules are listed here:
However that's long term: I'm spending all of my time working on analog
support at the moment, and there are a ton of drivers that need writing
after that. So please just copy-paste the software triggering that's in
the saleae-logic driver for now.
> It seems to me that sigrok needs to have a snapshot release. It's
> been over a year, and there are some infrastructure changes that I
> think need to be made. This includes adding support for analog, as
> well as soft-triggers. It seems to me that it would be best to let
> the code calm down, do a release before this more radical work
> begins. What's left to do for the release?
Yes, I absolutely agree. Uwe has been planning a release for ages, and
it keeps getting put off. This is not a good situtation.
Uwe, you need to to this, or I need to, but it needs getting done. No
more delays, or tweaks to comments etc please.
We've let things slip to the point where we haven't done a release in a
year, and it's shameful.
> Second, I've been looking into the possibility of doing JTAG on the
> Fx2. It seems there is an Fx2 based device on the market called
> ulink, and OpenOCD already has a driver for this by means of and
> open source firmware called OpenULINK
>With the appropriate modifications to the PID/VID list in OpenOCD, it
> should be possible to make any unbuffered Fx2 device do JTAG.
While this is interesting, I don't really see how that's useful to the
sigrok project. JTAG is one of the very few things not within the scope
of sigrok ;-)
>This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
A misspelling that a three-year old could catch, in an ad for a
Microsoft product automatically added to an open source project's
mailing list post.
This is, I think, a new low even for sourceforge. Anyone know of a
better mailing list provider?