Am 13.09.2012 08:06, schrieb Peter Stuge:
> 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
That's part of why we've ordered it ;)
>> 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.
Well, the example used the "--samples" option, which is neither
supported in the tarball release nor in the git head. So if at any point
in time the option WAS supported I'm wondering why it ever got removed.
Thus I concluded the option was never supported and thus the example
could not have worked.
You see, I was more guessing on this, but my conclusion seems quite
reasonable to me ;)
>> Here is a list of what I've come across with and how I worked around
>> 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
> 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.
I'm at war with git. There are way too many versioning systems out there
and I've come to find that git is the least usable under the popular
ones. Just my opinion, but therefore I just know how to clone and pull ;)
Anyway, I appended the patch to the mail, hoping that mailman does not
prune it or does whatever with it (I'm also at war with mailman *g).
>> 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
> 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
I've already answered on that one, but accidently just replied to Bert
instead to the whole list. And I wrote it at home last night, so I don't
have access to that post at the moment. I'll repost it today evening.
> 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.
I'm always open for supporting open source software and I'm investing a
lot of effort into these. As you could see I tried to fix things on my
own and scanned a bit over the code to understand what's going on there.
But right now I'm at the point where things should just work with little
I need the measurements for my master thesis and I don't think I should
spend too many time fixing things, what I need are pragmatic solutions ;)
So I don't know how much time I can effort writing or fixing code but if
there is anything I can test for you, let me know it.
>> 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.
See above ;)
> 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