Hi Markus,

Markus Engel wrote:
> today we got hands on the Asix Sigma2. We especially ordered it
> because of the support of sigrok.

Cool! It's a good piece of hardware and the vendor is very much worth
supporting!


> While I fully understand that open source software, supporting a wide 
> range of different hardware types, can be incomplete at some points,
> I'm a bit disappointed that even the "Usage Example" in the wiki does
> not work at all

I understand that.


> (and maybe did never).

I think it did, but sigrok is still a youngish project so there are
some violent changes here and there. I'm glad that you got in touch
with the community quickly though, so that you don't have to waste
time figuring out everything on your own.


> Here is a list of what I've come across with and how I worked around 
> problems:
> 
> 1) after doing anything with sigrok-cli (e.g. scanning devices) I get a 
> double free.
> This is because of asix-sigma.c:427 where ftdi_free is called instead of 
> ftdi_deinit

Are you comfortable with using git? If so, submitting a patch with
this fix should literally take only seconds. If not, please say so,
then I guess that someone else may produce the patch. In that case,
it would be helpful if you at least send the output of git diff for
your fixed file.


> 2) I always get a "sigrok-cli only supports one device for capturing." 
> even if I specify exactly one device using the "-d" option.
> This is because run_session tries to find all devices (which will return 
> the demo dummy device and the sigma in my case) and checks whether this 
> device list is greater than one, ignoring the "-d" option.

Stupid bug. I think Bert may fix this one.


> 3) The example uses the "--samples 5000000" option but the hwcaps of 
> your driver does not enlist SR_HWCAP_LIMIT_SAMPLES, so all you get is
> "Failed to configure sample limit.".

Maybe Bert too? :)


> 4) Finally I tried "sigrok-cli -d 0:samplerate=10m --time 1000 -O bits 
> -p 1-4"
> but the effect was more or less equivalent to "sleep 1". When I give an 
> "-o outfile" option I'm left with an empty file.
..
> I'm missing some log messages saying that samples are actually
> transferred.

Bert mentioned triggers. I'm not sure what the situation is wrt.
triggers in the asix-sigma driver. Is there a trigger button on the
Sigma2? If not, perhaps try using a few different clock or trigger
methods.

Note that sigrok so far has been tested significantly more with
mind-numbingly stupid FX2 streaming data acquisition hardware,
and not as much with actual logic analyzers like the ASIX products.

This means that there are a few wrinkles, but the underpinnings are
very much in place in sigrok to make it work excellently with actual
LAs, and I think if you have a serious usecase for the Sigma2 then
investing a few days of development effort into sigrok will be
incredibly rewarding - more is not going to be needed to make it
work really great also with the Sigma2.


> So my questions are: Have I done anything wrong? Is there maybe ANY
> revision I should check which at least captures some samples?

You've done nothing wrong, I think the code is just slightly
bitrotten from lack of testing - but the core is quite solid
and fresh, so since you have hardware in hand you are in the
best position to fix the issues.

I understand that you actually just want to use sigrok, but this is a
small project in terms of developers and that's simply not how such
projects work. Sorry. :\ But even if small, this community is really
fantastic - you'll have lots of fun if you stay in touch. Also feel
free to come hang out on freenode #sigrok.


//Peter

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to