You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(9) |
May
(20) |
Jun
(1) |
Jul
|
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(25) |
Feb
(1) |
Mar
(14) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(8) |
Nov
(14) |
Dec
(3) |
2012 |
Jan
|
Feb
(13) |
Mar
(17) |
Apr
(32) |
May
(22) |
Jun
(35) |
Jul
(56) |
Aug
(16) |
Sep
(8) |
Oct
(26) |
Nov
(30) |
Dec
(29) |
2013 |
Jan
(23) |
Feb
(19) |
Mar
(9) |
Apr
(39) |
May
(30) |
Jun
(23) |
Jul
(33) |
Aug
(7) |
Sep
(13) |
Oct
(40) |
Nov
(91) |
Dec
(43) |
2014 |
Jan
(59) |
Feb
(37) |
Mar
(28) |
Apr
(43) |
May
(37) |
Jun
(21) |
Jul
(56) |
Aug
(43) |
Sep
(44) |
Oct
(102) |
Nov
(31) |
Dec
(48) |
2015 |
Jan
(111) |
Feb
(114) |
Mar
(36) |
Apr
(59) |
May
(19) |
Jun
(17) |
Jul
(13) |
Aug
(36) |
Sep
(24) |
Oct
(43) |
Nov
(66) |
Dec
(39) |
2016 |
Jan
(41) |
Feb
(33) |
Mar
(21) |
Apr
(54) |
May
(48) |
Jun
(34) |
Jul
(42) |
Aug
(73) |
Sep
(31) |
Oct
(115) |
Nov
(41) |
Dec
(48) |
2017 |
Jan
(31) |
Feb
(32) |
Mar
(23) |
Apr
(20) |
May
(70) |
Jun
(26) |
Jul
(17) |
Aug
(22) |
Sep
(15) |
Oct
(14) |
Nov
(20) |
Dec
(4) |
2018 |
Jan
(45) |
Feb
(27) |
Mar
(16) |
Apr
(54) |
May
(30) |
Jun
(50) |
Jul
(25) |
Aug
(5) |
Sep
(7) |
Oct
(60) |
Nov
(75) |
Dec
(21) |
2019 |
Jan
(18) |
Feb
(14) |
Mar
(17) |
Apr
(15) |
May
(17) |
Jun
(9) |
Jul
(12) |
Aug
(11) |
Sep
(22) |
Oct
(30) |
Nov
(19) |
Dec
(18) |
2020 |
Jan
(29) |
Feb
(12) |
Mar
(54) |
Apr
(51) |
May
(50) |
Jun
(50) |
Jul
(34) |
Aug
(29) |
Sep
(54) |
Oct
(77) |
Nov
(26) |
Dec
(16) |
2021 |
Jan
(71) |
Feb
(22) |
Mar
(63) |
Apr
(15) |
May
(23) |
Jun
(30) |
Jul
(23) |
Aug
(15) |
Sep
(5) |
Oct
(12) |
Nov
(7) |
Dec
(5) |
2022 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(5) |
May
(9) |
Jun
(13) |
Jul
(7) |
Aug
(34) |
Sep
(22) |
Oct
(5) |
Nov
(31) |
Dec
(33) |
2023 |
Jan
(15) |
Feb
(3) |
Mar
(9) |
Apr
(20) |
May
(50) |
Jun
(6) |
Jul
(6) |
Aug
(6) |
Sep
(4) |
Oct
(7) |
Nov
(7) |
Dec
(6) |
2024 |
Jan
(8) |
Feb
(10) |
Mar
(8) |
Apr
(2) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(6) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Federico C. <fed...@ce...> - 2020-01-05 16:23:36
|
Hello, You need the firmware for the Cypress IC inside your device. Take a look at this wiki page: https://sigrok.org/wiki/Mcupro_Logic16_clone In the above page there is a link to pre built binaries Additional information on the firmware itself: https://sigrok.org/wiki/Fx2lafw Best Regards On 2020-01-05 16:08, Dmitry Katsubo via sigrok-devel wrote: > Dear Sigrok develoeprs, > > I would like to use latest PulseView v0.4.1 with this Saleae Logic 16 > clone [1] (looks exactly the same as "black" mod on page Noname > XL-LOGIC16-100M [2]). > > I have downloaded drivers from Saleae website [3] and installed them. > After that when I select "Saleae Logic 16" from driver list and press > "Scan for devices", PulseViewis is able to detect Saleae Logic16: > > Unfortunately when I press OK, it shows the error "Failed to open > device. generic/unspecified error": > > Is there any chance to make it working? > > Thanks in advance! > > -- > With best regards, > Dmitry > > > Links: > ------ > [1] https://www.aliexpress.com/item/32613420798.html? > [2] https://sigrok.org/wiki/Noname_XL-LOGIC16-100M > [3] > https://downloads.saleae.com/logic/1.2.29/Logic+1.2.29+Win+64+Standalone.zip > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel -- Federico Cerutti |
From: Dmitry K. <dm...@ma...> - 2020-01-05 15:08:17
|
Dear Sigrok develoeprs, I would like to use latest PulseView v0.4.1 with this Saleae Logic 16 clone <https://www.aliexpress.com/item/32613420798.html?> (looks exactly the same as "black" mod on page Noname XL-LOGIC16-100M <https://sigrok.org/wiki/Noname_XL-LOGIC16-100M>). I have downloaded drivers from Saleae website <https://downloads.saleae.com/logic/1.2.29/Logic+1.2.29+Win+64+Standalone.zip> and installed them. After that when I select "Saleae Logic 16" from driver list and press "Scan for devices", PulseViewis is able to detect Saleae Logic16: Unfortunately when I press OK, it shows the error "Failed to open device. generic/unspecified error": Is there any chance to make it working? Thanks in advance! -- With best regards, Dmitry |
From: Hans-Åke L. <han...@gm...> - 2020-01-05 14:56:57
|
Hi, I am trying to find the source code for attenload. The link to source seems to be broken from http://sdaaubckp.sourceforge.net/attenload/ I am trying to make an interface from sigrok to my ATTEN ADS2202 DSO. Regards Hans-Åke |
From: Uwe H. <uw...@he...> - 2019-12-26 00:33:34
|
Hi everyone, we're happy to announce the libsigrok 0.5.2 release! This is a "minor" release without incompatible C API changes, but lots of new hardware support and bugfixes, USB HID and Bluetooth/BLE support. For the full details please see the NEWS file and blog post: https://www.sigrok.org/blog/libsigrok-052-released The tarball is available for download here: https://sigrok.org/download/source/libsigrok/libsigrok-0.5.2.tar.gz Cheers, Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |
From: Soeren A. <so...@ap...> - 2019-12-21 16:37:33
|
Hello Marc, It's unfortunate that you apparently feel that the help that was given was unhelpful. While I wasn't involved in the discussion at hand, I'd like to point out that we do welcome all contributors and generally try to help them as much as time permits. We don't ever want you to feel like you can't ask questions, so your response is a little concerning for me. I would like to know whether you have any suggestions for us on how we can avoid this situation in the future. If you don't want to share this publicly for one reason or another, you can also mail me directly. All the best, -Soeren On Sat, 2019-12-21 at 15:57 +0000, Marc Jacobi wrote: > Yeah I stopped. > I was not enjoying the "type of help" I received and was not looking > forward to asking more questions - so I went to do something > different. > Do with the code what you will... > Marc > From: Gerhard Sittig <ger...@gm...> > Sent: Saturday, December 21, 2019 2:21 PM > To: sig...@li... < > sig...@li...> > Subject: Re: [sigrok-devel] Where/how to contribute an exporter > > On Thu, 2019-09-26 at 05:28 +0000, Marc Jacobi wrote: > > > > Thanks for the pointers. Looks like 'output' is the right place. > > > > I though that interfacing with this would be handy: > > https://wavedrom.com/ > > > > Basically a JSON format. > > Hi Marc! > > Got silent here and in your github repo. > > https://github.com/obiwanjacobi/libsigrok > > The mailing list is good for putting something "on record", or > looking up stuff after months or years have passed. If you are > looking for higher interaction or deeper discussions on > development, IRC could be a better fit. > > Hope you overcame past obstacles, and can continue development? > It's apparent that you have an interest in getting this format > supported by the project, and further improve existing support. :) > > > I have massaged the version that you came up with, to reduce the > remaining amount of work for the maintainer to accept it into the > mainline code base. The resulting version is here: > > > https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 > git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 > > This should work as well as your implementation did, just fit > into the project's style a little better. You were almost there. > Just an issue of rather high a memory consumption remains, which > can get addressed later. > > I have also started a wiki page for the wavedrom file format. As > of now it's rather stupid and mostly empty. You may want to fill > in some more useful information, see the other file format pages > for ideas what to put there. You find the other pages by starting > at the file formats page. > > https://sigrok.org/wiki/Input_output_formats > https://sigrok.org/wiki/File_format:Wavedrom > > > Thank you for starting the output file format support, and I hope > you keep contributing to the project. > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Gerhard S. <ger...@gm...> - 2019-12-21 16:24:51
|
On Sat, 2019-12-21 at 14:21 +0100, Gerhard Sittig wrote: > > I have massaged the version that you came up with, to reduce the > remaining amount of work for the maintainer to accept it into the > mainline code base. The resulting version is here: > > https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 > git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 Good news everyone! Your output module and the additional adjustment got accepted, and will be part of tomorrow's downloads after the nightly build pick up that implementation. Enjoy! virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. |
From: Marc J. <obi...@ho...> - 2019-12-21 15:57:54
|
Yeah I stopped. I was not enjoying the "type of help" I received and was not looking forward to asking more questions - so I went to do something different. Do with the code what you will... Marc ________________________________ From: Gerhard Sittig <ger...@gm...> Sent: Saturday, December 21, 2019 2:21 PM To: sig...@li... <sig...@li...> Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Thu, 2019-09-26 at 05:28 +0000, Marc Jacobi wrote: > > Thanks for the pointers. Looks like 'output' is the right place. > > I though that interfacing with this would be handy: > https://wavedrom.com/ > > Basically a JSON format. Hi Marc! Got silent here and in your github repo. https://github.com/obiwanjacobi/libsigrok The mailing list is good for putting something "on record", or looking up stuff after months or years have passed. If you are looking for higher interaction or deeper discussions on development, IRC could be a better fit. Hope you overcame past obstacles, and can continue development? It's apparent that you have an interest in getting this format supported by the project, and further improve existing support. :) I have massaged the version that you came up with, to reduce the remaining amount of work for the maintainer to accept it into the mainline code base. The resulting version is here: https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 This should work as well as your implementation did, just fit into the project's style a little better. You were almost there. Just an issue of rather high a memory consumption remains, which can get addressed later. I have also started a wiki page for the wavedrom file format. As of now it's rather stupid and mostly empty. You may want to fill in some more useful information, see the other file format pages for ideas what to put there. You find the other pages by starting at the file formats page. https://sigrok.org/wiki/Input_output_formats https://sigrok.org/wiki/File_format:Wavedrom Thank you for starting the output file format support, and I hope you keep contributing to the project. virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. _______________________________________________ sigrok-devel mailing list sig...@li... https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Gerhard S. <ger...@gm...> - 2019-12-21 13:21:37
|
On Thu, 2019-09-26 at 05:28 +0000, Marc Jacobi wrote: > > Thanks for the pointers. Looks like 'output' is the right place. > > I though that interfacing with this would be handy: > https://wavedrom.com/ > > Basically a JSON format. Hi Marc! Got silent here and in your github repo. https://github.com/obiwanjacobi/libsigrok The mailing list is good for putting something "on record", or looking up stuff after months or years have passed. If you are looking for higher interaction or deeper discussions on development, IRC could be a better fit. Hope you overcame past obstacles, and can continue development? It's apparent that you have an interest in getting this format supported by the project, and further improve existing support. :) I have massaged the version that you came up with, to reduce the remaining amount of work for the maintainer to accept it into the mainline code base. The resulting version is here: https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 This should work as well as your implementation did, just fit into the project's style a little better. You were almost there. Just an issue of rather high a memory consumption remains, which can get addressed later. I have also started a wiki page for the wavedrom file format. As of now it's rather stupid and mostly empty. You may want to fill in some more useful information, see the other file format pages for ideas what to put there. You find the other pages by starting at the file formats page. https://sigrok.org/wiki/Input_output_formats https://sigrok.org/wiki/File_format:Wavedrom Thank you for starting the output file format support, and I hope you keep contributing to the project. virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. |
From: Candid M. <can...@gm...> - 2019-12-18 12:18:40
|
Hi! This is the patch for the TCS3472x decoder (I2C protocol). Include captures. I2C pins are: * SDA -> D2 * SCL -> D3 Sorry for the previous error. I got thing messed up moving files between directories. Let me know any problem. Candid Moe |
From: Geert S. <sta...@st...> - 2019-12-17 22:29:13
|
On Tue, Dec 17, 2019 at 04:36:24PM -0300, Candid Moe wrote: > Hi! > > I'm sending a patch to add support for the TCS3472x color sensor. > > Let me know any problem. Working on it ;-) > Yours > > Candid Moe > > > > >From c8555149ca47033ffac396d71f51a223a99ffb22 Mon Sep 17 00:00:00 2001 > From: Candid Moe <can...@gm...> > Date: Tue, 17 Dec 2019 16:32:57 -0300 > Subject: [PATCH] Add TCS3472x decoder > > --- > decoders/tcs3472x/__init__.py | 26 ++++++++++++++++++++++++++ > decoders/tcs3472x/pd.py | 26 ++++++++++++++++++++++++++ > 2 files changed, 52 insertions(+) > create mode 100644 decoders/tcs3472x/__init__.py > create mode 100644 decoders/tcs3472x/pd.py > > diff --git a/decoders/tcs3472x/__init__.py b/decoders/tcs3472x/__init__.py > new file mode 100644 > index 0000000..66ef29f > --- /dev/null > +++ b/decoders/tcs3472x/__init__.py > @@ -0,0 +1,26 @@ > +## > +## This file is part of the libsigrokdecode project. > +## > +## Copyright (C) 2019 Candid Moe <can...@gm...> > +## <snip/> > +''' > +TCS3472x is a color light-to-digital converter with IR filter. > + > +This decoder is compatible with the whole TCS3472x family. > +''' > + > +from .pd import Decoder > diff --git a/decoders/tcs3472x/pd.py b/decoders/tcs3472x/pd.py > new file mode 100644 > index 0000000..66ef29f > --- /dev/null > +++ b/decoders/tcs3472x/pd.py > @@ -0,0 +1,26 @@ > +## > +## This file is part of the libsigrokdecode project. > +## > +## Copyright (C) 2019 Candid Moe <can...@gm...> > +## <snip/> > +''' > +TCS3472x is a color light-to-digital converter with IR filter. > + > +This decoder is compatible with the whole TCS3472x family. > +''' > + > +from .pd import Decoder > -- > 2.17.1 > Both files look the same to me. Either use symlink or provide two diffent files. Lurker Back into lurk mode |
From: Candid M. <can...@gm...> - 2019-12-17 19:44:33
|
Hi! Some captures for the TCS3472x decoder (I2C). Protocol I2C: * SCL is D3 * SDA is D2 Let me know any problem. Candid Moe. |
From: Candid M. <can...@gm...> - 2019-12-17 19:36:36
|
Hi! I'm sending a patch to add support for the TCS3472x color sensor. Let me know any problem. Yours Candid Moe |
From: Federico C. <fed...@ce...> - 2019-12-17 03:42:01
|
Hello, Thanks a lot for coming my way. Today it was confirmed to me that I can't post any material from this work online. If you want I could buy blank cards myself and sniff in the future, so that you don't need to buy a reader for this sole purpose. I've fixed the unused variable and the case issue on github. Thanks a lot for spotting them! If you confirm I can post the sniffs later on, I'll proceed with the pull request. Thanks, On 2019-12-15 23:51, Uwe Hermann wrote: > Hi, > > On Sun, Dec 15, 2019 at 05:47:46PM +0100, Federico Cerutti wrote: >> Hello, >> I have written a simple protocol decoder for the Siemens/Infineon SLE >> 4418/28/32/42 memory card family. >> You can check it out here: https://github.com/ceres-c/SLExx-Sigrok >> >> I'm writing this email to ask if it would be possible get the decoder >> in >> Sigrok without a sniff or if someone else could, maybe, sniff another >> system >> using this kind of cards. Unluckily, I can't post my own sniffs >> because I >> have signed a NDA about the system. > > We usually prefer to have .sr files and some tests in the sigrok-test > repo for regression testing etc., but in this case I think we can make > an exception, yeah. > > It seems it's easy enough to get reader hardware and some blank SLE4442 > cards from ebay, so I can probably grab a few sample captures later... > > >> Of course I'm open to suggestions/scoldings about my current code. > > Upon a quick look, the decoder looks fine, please send a GitHub pull > request (https://github.com/sigrokproject/libsigrokdecode). > > Minor comments: The "id" and "outputs" values should be all-lowercase, > directory name of the PD should be "sle44xx" as well. self.out_bitrate > looks unused, can be dropped. > > > Cheers, Uwe. -- Federico Cerutti |
From: Uwe H. <uw...@he...> - 2019-12-15 22:51:55
|
Hi, On Sun, Dec 15, 2019 at 05:47:46PM +0100, Federico Cerutti wrote: > Hello, > I have written a simple protocol decoder for the Siemens/Infineon SLE > 4418/28/32/42 memory card family. > You can check it out here: https://github.com/ceres-c/SLExx-Sigrok > > I'm writing this email to ask if it would be possible get the decoder in > Sigrok without a sniff or if someone else could, maybe, sniff another system > using this kind of cards. Unluckily, I can't post my own sniffs because I > have signed a NDA about the system. We usually prefer to have .sr files and some tests in the sigrok-test repo for regression testing etc., but in this case I think we can make an exception, yeah. It seems it's easy enough to get reader hardware and some blank SLE4442 cards from ebay, so I can probably grab a few sample captures later... > Of course I'm open to suggestions/scoldings about my current code. Upon a quick look, the decoder looks fine, please send a GitHub pull request (https://github.com/sigrokproject/libsigrokdecode). Minor comments: The "id" and "outputs" values should be all-lowercase, directory name of the PD should be "sle44xx" as well. self.out_bitrate looks unused, can be dropped. Cheers, Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |
From: Federico C. <fed...@ce...> - 2019-12-15 17:27:17
|
Hello, I have written a simple protocol decoder for the Siemens/Infineon SLE 4418/28/32/42 memory card family. You can check it out here: https://github.com/ceres-c/SLExx-Sigrok I'm writing this email to ask if it would be possible get the decoder in Sigrok without a sniff or if someone else could, maybe, sniff another system using this kind of cards. Unluckily, I can't post my own sniffs because I have signed a NDA about the system. Of course I'm open to suggestions/scoldings about my current code. Thanks, -- ---------- Federico Cerutti |
From: Candid M. <can...@gm...> - 2019-12-14 17:24:16
|
Hi I upload this decoder for the TCS3472x chip to GitHub <https://github.com/SantoRemedio/TCS3472x-Decoder> I made it for my own use, and I need your comments to make it useful for developer at large. Thanks in advance. Candid Moe. |
From: Thomas W. <si...@t-...> - 2019-12-13 21:43:48
|
From: Thomas Weißschuh <th...@t-...> This allows `sigrok-cli --continuous` to work when running without a tty. For example as a system service. It is also easier to use in scripts by connecting the input to /dev/null. An exit can still be triggered with signals. --- anykey.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/anykey.c b/anykey.c index b1ac9ef..efb2021 100644 --- a/anykey.c +++ b/anykey.c @@ -58,6 +58,9 @@ void add_anykey(struct sr_session *session) { GIOChannel *channel; + if (!isatty(STDIN_FILENO)) + return; + #ifdef _WIN32 stdin_handle = GetStdHandle(STD_INPUT_HANDLE); @@ -90,6 +93,9 @@ void add_anykey(struct sr_session *session) */ void clear_anykey(void) { + if (!isatty(STDIN_FILENO)) + return; + if (watch_id != 0) { g_source_remove(watch_id); watch_id = 0; -- 2.24.1 |
From: Uwe H. <uw...@he...> - 2019-12-11 22:17:16
|
Hi everyone, we're happy to announce the libsigrokdecode 0.5.3 release! This is a bugfix release without incompatible C API changes. It does include a number of bugfixes in various PDs, as well as a bunch of new decoders (backported from git HEAD). This release features 109 decoders in total. For the full details please see the NEWS file and blog post: https://www.sigrok.org/blog/libsigrokdecode-053-released The tarball is available for download here: https://sigrok.org/download/source/libsigrokdecode/libsigrokdecode-0.5.3.tar.gz Cheers, Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |
From: Soeren A. <so...@ap...> - 2019-12-01 09:40:05
|
Hello Helge, Your suggested change has been performed by gsi on Oct 11th: https://sigrok.org/w/index.php?title=Protocol_decoder_HOWTO&type=revision&diff=14507&oldid=13616 Thanks! -Soeren On Fri, 2019-10-11 at 10:09 +0200, Helge Kruse wrote: > Hi, > > In the Protocol_decoder_HOWTO page we can read: > > On Linux systems, this name follows the XDG base directory > specification, which by default resolves to > ~/.local/share/libsigrokdecode/decoders. > > It would be useful to add information for Windows 10 operation > system. > I propose this: > > On Windows systems, additional decoders are read from > %ProgramData%\libsigrokdecode\decoders. > > > Best regards, > Helge > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Soeren A. <so...@ap...> - 2019-12-01 09:37:33
|
Hello Jessy, A microcontroller is best suited to do this in realtime because a PC doesn't have a native SPI interface. While sigrok does intend to be able to do signal analysis in realtime, the python bindings need a little love to be user-friendly. For this reason, C or C++ are the preferred languages at the moment, even though python does work. For this reason, I suggest you check out https://micropython.org/ instead. If that doesn't work for you, checking out the libsigrok python bindings is still an option. All the best, -Soeren On Wed, 2019-10-02 at 14:20 +0300, Jessy Martiano wrote: > Hi all, > I need to analyze data of SPI protocol on real time > Do you have any APi in Python in preference that can help me ? > Thanks > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Soeren A. <so...@ap...> - 2019-12-01 09:07:15
|
Hello Reginald, As no one has reponded yet, I'll leave whatever I know about this. First off, pattern generation is definitely on our wish list. Unfortunately however, no one yet worked on the parts that we need to make it happen. Right now, the "session bus" that libsigrok uses is transporting data in one direction only: device driver->libsigrok->client In order to make pattern generation work, we would need the other direction, which isn't hard, but must be implemented first. Then, we need hardware that supports this. The FX2 is an obvious candidate, but the fx2lafw we use doesn't yet have such a feature. Someone has to add it. Afterwards, we must extend the fx2lafw libsigrok driver with the feature. Once that's done, we need to teach sigrok-cli and PV about this feature and make it accessible to the user. Each part isn't hard by itself, it's just time-consuming and no one worked on it so far. So yeah, unfortunately sigrok can't offer you this feature at this time. The FX2 however is from my point of view the ideal platform for this. All the best, -Soeren On Sat, 2019-11-23 at 17:26 +0000, Reginald Beardsley via sigrok-devel wrote: > Hi, > > I'm new to using sigrok, though I've been aware of it for many > years. I recently bought some FX2LP boards to use with it. I also > have a wide variety of small MCU dev boards. > > Does this capability exist? I've not been able to learn anything in > my searches. > > I'm involved with the HPIB-USB FW, AR488, and want to build a > dedicated test system for verifying bus timing. However, the > FX2LP can only provide 1 mA of drive per pin whereas the ATMEGA 328P > and 2560 SMD chips provide up to 40 mA per pin and 200 mA total > source/sink. I'm not committed to any particular chip, so any dev > board that is well supported as an LA and pattern generator is fine. > > I'd like to be able to generate patterns with and without timing > errors to test whatever I use for the test system. I also want to be > able to replay an LA trace through the PG. > > I'm looking for recommendations for the best dev board platform for > both LA and PG functionality. I'm not interested in COTS LA and PG > products. > > I have an HP 16702B and a 16500C, so I have professional level tools > for verifying sigrok performance on whatever I use. Though I know as > much about using them as I do sigrok. I just bought them. > > Thanks, > Reg > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Riccardo C. <ric...@gm...> - 2019-11-29 20:55:24
|
Hi, I'm writing a simulator to simulate the Bluetooth LE link layer. The simulator is written in Python, but I guess the language doesn't really matter here. I would like to show on a GUI when certain things happen, for example when a packet is transmitted. Since the simulator is realtime, I thought that using PulseView would be nice. So basically, I would like to use Sigrok/PulseView without any HW probe, and instead "simulate" it. Could someone please give me some hints on where to start? thanks! Riccardo |
From: Soeren A. <so...@ap...> - 2019-11-29 20:23:31
|
Hi Benedikt, I saw that the current state of your HD44780 branch doesn't yet send the image out using OUTPUT_BINARY. Can you add this maybe? -Soeren On Sat, 2019-11-23 at 15:16 +0100, Soeren Apel wrote: > Uwe, Gerhard and I are discussing the issue on IRC, so > I suggest you join whenever you have time so we can discuss the > details > of how we can make it happen. > > It's just a little easier than email :) > > -Soeren > > On Sat, 2019-11-23 at 14:38 +0100, Soeren Apel wrote: > > Hello Benedikt, > > > > > Yes, I would be interested. That sounds interesting and very > > > useful. > > > It will require a lot of work in nearly all parts of sigrok i > > > guess, > > > and sigrok-test for example. > > > > Great! Honestly I don't think it would be too much work. > > > > As I understand it, we only need to add a new annotation type > > (maybe > > SRD_OUTPUT_IMAGE_%s with %s being the image format) to > > libsigrokdecode > > and have your PD emit it. > > > > libsigrok itself is unaffected and honestly I don't know if sigrok- > > test > > needs to verify that the image output is correct. I mean I guess > > there > > would be a benefit to do so but that could be done later if > > desired. > > > > -Soeren > > > > > > > > What I have in mind is something very similar to > > > > https://eleif.net/HD44780.html - anytime your PD's > > > > DisplaySimulator > > > > changes the output string, it could generate such an image, > > > > send > > > > it > > > > out > > > > as a new type of annotation and PV could display it in various > > > > ways. > > > > > > > > Image generation could be done using e.g. > > > > http://github.com/Solomoriah/gdmodule or > > > > http://python-pillow.org > > > > , > > > > whichever has less dependencies and is easier to integrate into > > > > the > > > > MXE > > > > build for Windows. > > > > > > > > -Soeren > > > > > > This solution would solve the problem with the custom caracters > > > too. > > > > > > Benedikt > > > > > > > > > > On Sat, 2019-11-23 at 12:08 +0100, Benedikt Otto wrote: > > > > > Hi, > > > > > > > > > > > > > > > under https://github.com/BenediktO/libsigrokdecode.git > > > > > > > > > > I uploaded the HD44780 decoder I am developing under the > > > > > branch > > > > > add_hd44780. > > > > > > > > > > I hope that I made less errors than with the 7-segment > > > > > decoder. > > > > > > > > > > The decoder supports LCDs with the common configurations from > > > > > 1x8 > > > > > to > > > > > 4x20. On top it supports both possible charsets, for some > > > > > (japanese) > > > > > characters i was not able to find a unicode representation. > > > > > > > > > > It provides a simulated display that displays the current > > > > > content > > > > > of > > > > > the > > > > > display. > > > > > > > > > > Note that it supports both 4 and 8 bit mode, but since i only > > > > > have an > > > > > 8 > > > > > bit logic analyzer, I was not able to really test the 8bit > > > > > mode. > > > > > > > > > > Custom characters are displayed as "CC%d" with %d in range(0, > > > > > 8). > > > > > > > > > > In the sigrok-dumps repository are already some example > > > > > files, > > > > > that i > > > > > generated with an Arduino and various displays. The Arduino > > > > > sketches > > > > > are > > > > > based on the example Sketches of the LiquidCrystal library. I > > > > > could > > > > > verify that the displayed output is exactly the same as the > > > > > predicted > > > > > output of the decoder. > > > > > > > > > > Except for the (rarely used) read command of the display all > > > > > commands > > > > > are supported and tested. > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Benedikt > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > sigrok-devel mailing list > > > > > sig...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > > _______________________________________________ > > sigrok-devel mailing list > > sig...@li... > > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Uwe H. <uw...@he...> - 2019-11-24 17:29:05
|
Hi, On Sat, Sep 21, 2019 at 12:14:14AM +0000, Patrick Dorion wrote: > Hello, > > so I was happy today because I got my new LHT00SU1 in the mail, but unfortunately it doesn’t work… at least not out of the box… > > I connect it to USB, and in Windows 10’s Device Manager it shows as an unknown USB device, I open Sigrok, search for the device using fx2lafw, but nothing shows-up in the box… Nothing gets detected as a serial device, either, so I have no open COM ports… > > I’d rather not install the Chinese applications, so I haven’t tested with the USBee software yet… > > Am I missing something? Do I have to return it? This might also have been a bug that's been fixed a while ago. Please retry the latest nightly PulseView build: - Install PulseView - Use Zadig to assign the WinUSB driver to the device (as per wiki) - Start PulseView, it should automatically detect a "CWAV USBee AX" or such automatically and it will be in the device drop-down. Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |
From: Uwe H. <uw...@he...> - 2019-11-24 17:22:38
|
Hi, On Tue, Oct 01, 2019 at 08:37:43PM +1000, A/Prof Chris Andrews wrote: > I have a 15" MACBOOK PRO. > > I am using the LHT00SU1 Oscilloscope and Logic Analyzer connect via USB. > > This is a no-name brand, and is a clone of the CWAV USBee AX-PRO. > > The general advice is that it is used with Pulseview, using the driver > fx2lafw. > > I have downloaded Pulseview and am setting it up. It loads well, and runs, > however when I come to "select device" I select fx2lafw as the driver and > then ask to scan USB ports for my device. There is no response from the scan > for anything such as CWAV, USBee, AX-Pro, or the like, or any generic > response. > > Does anyone have any experience with setting up this device or a CWAV device > with Pulseview? I think this might have been caused by a bug that was fixed a while ago. Please try the latest nightly, it should work out of the box: - "open PulseView-NIGHTLY.dmg" - CTRL-Click the PulseView icon, select "Open" (or such) - PulseView will automatically find a "CWAV USBee AX" and it'll appear in the device drop-down. Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |